Olaf's explanation is better than mine. Maybe we should add something
like this to the documentation.
> Hi Barbara!
> I would like to find an answer for some points. I write below your
> remarks and questions.
> Barbara Sierman wrote:
>> Hello all,
>> During the last months we at the KB in Holland studied the Premis Data
>> Dictionary. In our e-Depot we use metadata, but when we started with the
>> e-Depot the Premis Data Dictionary did not exist. So a comparison was
>> made between the Premis data elements and our e-Depot system (DIAS from
>> IBM). Our DIAS system will be upgraded to the next version so it is a
>> good opportunity to study the data model . Most of the Premis elements
>> will be relevant for us too. However some questions were left and I
>> would like your opinion on the following:
>> 1. Premis definition of Representation: a set of files, including
>> structural metadata, needed for a complete and reasonable rendition of
>> an Intellectual Entity.
>> DIAS principle is 1 object = 1 AIP. If an object has a relation with
>> other objects the relevant information in the bibliographical metadata
>> will create the Intellectual Entity. So Representation Information will,
>> as far as we know now, always concern one object.
>> 3. Representation: creatingApplication
>> In my opinion this element belongs to the File section and not to the
>> Representation section, as it is the Application that created the file,
>> despite the representation of the file.
> It is more or less a question how you define an object/a representation
> and which kind of objects you use. A represenatation is a bunch of files
> and structural metadata for a "complete and reasonable rendition of an
> Intellectual Entity".
> The given example of a FlashMX represenation might confuse, because
> often it is available in one single flash file. But it might also
> consist of several files and a central flash file with structural and
> other information for the coordniation of the rendition.
> You might want to record that this representation was composed and
> compiled with one installation of FlashMX in version XYZ, because
> failures and bugs do happen and maybe they occur only within one
> installed version.
> Another reason are format changes. You have to know about the context
> and relations to reconstruct things. Even if you are able to render some
> files independently of that central flash file, you might not be able to
> reconstruct the impression of the dynamic of the presentation, might not
> know about the completeness and the context of the used files. It is
> essential to know how things are embedded and used and that they are
> part of one representation. That gets even more important if you don not
> know about the internal structure of (proprietary) formats.
> This information might also be important for other complex objects, too.
>> 6. One practical point: I numbered all the elements (1, 1.1, 1.1.1 etc),
>> which make them easier to trace in the Dictionary.
> I think a numbering scheme could be very helpfull for other users, too.
> Can you send it out to the wiki as a basis for a discussion?
>> I look forward to your reactions and will thank you very much in
>> Kind regards,
>> Barbara Sierman
>> Digital Preservation Officer
>> Koninklijke Bibliotheek
>> PO Box 90407
>> 2509 LK Den Haag, The Netherlands
>> +31 70 3140109
>> [log in to unmask]