Germanische Nationalmuseum Nuremberg
The following DTDs have been designed for use at the Germanische Nationalmuseum Nuremberg in collaboration with ICS-FORTH on a CRM base. They reflect three stages of documentation:
The basic information connecting the identification of the acquisition and the inventarization process (DTD-English version) (DTD-German version)
The administration of the objects (DTD-English version) (DTD-German version)
The scholarly and scientific description of the object (DTD-English version) (DTD-German version)
[See the associated Style Sheets: (CSS-English version) (CSS-German version)]
The latter will be varied according to the documentation needs of the different departments/ disciplines in the museum. All three conform with the CIDOC Information Categories, and can be mapped directly to the CRM.
They are an example of good practice of the use of the CRM. DTDs as data entry formats must be closer to the individual user's conceptualization than the overarching ontology. They must further express consistency constraints to assist data validation. They need not, in all parts, fulfill the finest level of detail avalable in the CRM, but can be on a coarser or finer level. Finally they must support a reasonable representation during data entry.
Here, e.g., for the object history the preference was given to more free text representation. The DTD merely maintains the integrity of dates, places and participants in events, but does not go into specific roles. A grouping of the information into logical documentation units has been done in order to suggest to the user which information to provide. This grouping has no semantic role wrt the object, therefore it has no equivalent in the CRM. These are nice examples that demonstrate, why the CRM is NOT and should not be a documentation format.
The DTDs are available in German and English. The associated Style Sheets (CSS-English version, CSS-German version) contain :before statements, which are not supported by Microsoft Internet Explorer. They can be seen with the XMetal Editor. Alternatively, an XSL file can be used to put a text before an element.
Germanische Nationalmuseum Nuremberg The following DTDs have been designed for use at the Germanische Nationalmuseum Nuremberg in collaboration with ICS-FORTH on a CRM base. They reflect three stages of documentation:The basic information connecting the identification of the acquisition and the inventarization process (DTD-English version) (DTD-German version)The administration of the objects (DTD-English version) (DTD-German version)The scholarly and scientific description of the object (DTD-English version) (DTD-German version) [See the associated Style Sheets: (CSS-English version) (CSS-German version)]The latter will be varied according to the documentation needs of the different departments/ disciplines in the museum. All three conform with the CIDOC Information Categories, and can be mapped directly to the CRM. They are an example of good practice of the use of the CRM. DTDs as data entry formats must be closer to the individual user's conceptualization than the overarching ontology. They must further express consistency constraints to assist data validation. They need not, in all parts, fulfill the finest level of detail avalable in the CRM, but can be on a coarser or finer level. Finally they must support a reasonable representation during data entry. Here, e.g., for the object history the preference was given to more free text representation. The DTD merely maintains the integrity of dates, places and participants in events, but does not go into specific roles. A grouping of the information into logical documentation units has been done in order to suggest to the user which information to provide. This grouping has no semantic role wrt the object, therefore it has no equivalent in the CRM. These are nice examples that demonstrate, why the CRM is NOT and should not be a documentation format. The DTDs are available in German and English. The associated Style Sheets (CSS-English version, CSS-German version) contain :before statements, which are not supported by Microsoft Internet Explorer. They can be seen with the XMetal Editor. Alternatively, an XSL file can be used to put a text before an element.
การแปล กรุณารอสักครู่..
