Hi list,

while reviewing the Data dictionary for a metadata mapping I found
another issue for the update of the data dictionary in the semantic unit
fixity. Fixity is not expressable on the represenation level, only at
the file level. But it should be, because one would not like to use
fixity on the file level for that file, which is the representation.
Even though it might be just a file, the information for the
representation should be recorded for practical reasons in a separate
representation section of a different structure. The missing
applicability of fixity on the representation restricts some
implementations.

This gives a bit mor background information, the argument against using
fixity on representation level it in the usage notes says:
"Representation level: It could be argued that if a representation
consists of a single file, or if all the files comprised by a
representation are combined (e.g., zipped) into a single file, then a
fixity check could be performed on the representation. However, in
both cases the fixity check is actually being performed on a file,
which in this case happens to be coincidental with a representation."

This change may also have side effects on the semantic unit:
objectCharacteristics and other subunits like compositionLevel.


Olaf

-- 
---------------------------------------------------------
Goettingen State and University Library
Olaf Brandt
Project kopal 
Tel.: +49-551-39-7805
Email: [log in to unmask]
http://www.sub.uni-goettingen.de/
http://kopal.langzeitarchivierung.de/