Let's develop an open-source media archive standard

[der Mouse]

>> I'm tempted to say that we should leave copy protection hacks out of
>> the spec for now, but if it was extensible, that would be great.
> Yes, copy protection will defintely be able to be described naturally
> in the specification I have in mind.  The spec should be able to
> define several layers of bit storage: logical (files, directories,
> etc.), byte (e.g. tracks, sectors), and raw (bit streams).  In this
> way, copy protection schemes can be preserved by storing the image in
> the raw format.

Some copy protection schemes.

What about copy-protection schemes that work by damaging the media to
the point where it doesn't _have_ a bit stream at a particular place?

As you say, maybe not in V1.0, but something to keep in mind.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse at rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B