I agree in all what Hans had to say except for how data would be stored. This is supposed
to be an archive format which would in my view preclude getting data from the outside
world. My only other concern as I have stated before was that data should not be an
integral part of the media. If a device happens to be a tape drive, the data on the tape
still separates into "file" type data and overhead data required for the tape
physical format. Enbedding the "file" tyupe data inside of the physical format
makes the data inaccessible without special knowledge.
best regards, Steve Thatcher
-----Original Message-----
From: Hans Franke <Hans.Franke(a)siemens.com>
Sent: Aug 12, 2004 9:30 AM
To: "General Discussion: On-Topic and Off-Topic Posts"
<cctalk(a)classiccmp.org>
Subject: Re: archive file format exmaple
I'm not so sure about having the actual data
within the archive element;
I'd rather have it afterwards.
I would prefer an aproach where both ways are possible, includeing
a third wich allows to put the data even into another file. In the
CCDD definition almost every element (except META) may be empty and
have a HREF attribute pointing to it's content:
A take header record could have it's data included:
<DATA SIZE="80" ENCODING="CHAR" FILLER="
">HDR2U020480204841 00</DATA>
or just point to the data
<DATA HREF="#DB1"/>
<DATA SIZE="80" ENCODING="CHAR" FILLER=" "
ID="DB1">HDR2U020480204841 00</DATA>
which of course may even be in another file:
<DATA
HREF="http://cc-archive.org/~hans/mytapes/T43782.xml#DB1"/>