manifest schema

[Bruce D'Arcus <bdarcus@gmail.com>]

While it's fresh in my mind, below is the current manifest schema.

I stand corrected; the fact that the manifest:encryption-data element 
is an immediate child of manifest:file-entry makes it not valid RDF. I 
think it would need an rdf:parseType="Resource" attribute to make it 
valid (and then maybe have some rules about foreign elements and/or 
attributes).

=====

start = manifest

manifest = element manifest:manifest { file-entry+ }

file-entry =
   element manifest:file-entry { file-entry-attlist, encryption-data? }

file-entry-attlist &= attribute manifest:full-path { xsd:string }

file-entry-attlist &=
   attribute manifest:size { xsd:nonNegativeInteger }?

file-entry-attlist &= attribute manifest:media-type { xsd:string }

encryption-data =
   element manifest:encryption-data {
     encryption-data-attlist, algorithm, key-derivation
   }

encryption-data-attlist &=
   attribute manifest:checksum-type { xsd:string }

encryption-data-attlist &=
   attribute manifest:checksum { xsd:base64Binary }

algorithm = element manifest:algorithm { algorithm-attlist, empty }

algorithm-attlist &= attribute manifest:algorithm-name { xsd:string }

algorithm-attlist &=
   attribute manifest:initialisation-vector { xsd:base64Binary }

key-derivation =
   element manifest:key-derivation { key-derivation-attlist, empty }

key-derivation-attlist &=
   attribute manifest:key-derivation-name { xsd:string }

key-derivation-attlist &= attribute manifest:salt { xsd:base64Binary }

key-derivation-attlist &=
   attribute manifest:iteration-count { xsd:nonNegativeInteger }

======