PREMIS Metadata profile

PREMIS Metadata profile

Preservation characteristics of digital objects in the CSH metadata model are expressed in a PREMIS v3.0-based schema. This document describes the CSH-PREMIS preservation profile. This profile is level 3 PREMIS-conformant--the semantic units described in this profile are internally implemented to be consistent with the PREMIS entities. The profile has modified the obligation of entities to be Mandatory (M) instead of Optional (O). Such changes are documented in the Obligation column of the table.


PREMIS


S. NoLabelPropertyRangeUsageObligationVocab schemaSyntax schemaExampleComments
1Objectpremis.objectObjectThis element contains information about the PREMIS object entity.1



2Eventpremis.eventListEventThis element contains information about the PREMIS event entity. Event instances are bundled in a list.0-n




Object

Objects may either be individual scanned folios or groupings of scanned folios (for example, registers or microfilm rolls). For details, please see the documentation for the premis.object.objectCategory property.

S. NoLabelPropertyRangeUsageObligationVocab schemaSyntax schemaExampleComments
1Object Identifier

premis.object

.objectIdentifer

ObjectIdentifierA container for the object identifier elements1



2Object Category

premis.object

.objectCategory


A value that indicates the type of this object. Scanned documents will be recorded as "file". Virtual groupings of scanned documents (for example, all files belonging to a register or all files belonging to a microfilm roll) will be recorded as "intellectual entity".1

Controlled vocabulary available at: http://id.loc.gov/search/?q=&q=cs%3Ahttp%3A%2F%2Fid.loc.gov%2Fvocabulary%2Fpreservation%2FobjectCategory

one of {intellectual entity, bitstream, file, representation}





3Object characteristics

premis.object

.objectCharacteristics

objectCharacteristicsA container to describe characteristics of this object1



4Original name

premis.object

.originalName


The path on the hard drive as received from the scanning company. This path will include the name of the hard drive.1




ObjectIdentifier

S. NoLabelPropertyRangeUsageObligationVocab schemaSyntax schemaExampleComments
1Object id type

premis.object.objectIdentifer

.objectIdentiferType


Type of the identifier code. This information should include sufficient detail about the program, module, and version that was used to create this identifier, separated using semi-colons.1



2Object id value

premis.object.objectIdentifer

.objectIdentifierValue


The unique identified assigned to this object, which was generated using the mechanism described in Object id type.1




ObjectCharacteristics

S. NoLabelPropertyRangeUsageObligationVocab schemaSyntax schemaExampleComments
1fixity

premis.object

.objectCharacteristics.fixity

FixityAn element that records the message digest for conducting future fixity checks on this object.1
 Literal

2size

premis.object

.objectCharacteristics.size


Size of the file as stored on the disk in bytes.1
number (no commas or separators)

3format

premis.object

.objectCharacteristics.format

FormatAn element that describes the encoding format for this document.1




Fixity

S. NoLabelPropertyRangeUsageObligationVocab schemaSyntax schemaExampleComments
1Message digest algorithm

premis.object.objectCharacteristics

.fixity.messageDigestAlgorithm

The program, algorithm, and version that was used to create the message digest recorded in this element.
1



2Message digest

premis.object.objectCharacteristics

.fixity.messageDigest

The resulting message digest generated for this object using the mechanism described in Message digest algorithm.
1




Format

S. NoLabelPropertyRangeUsageObligationVocab schemaSyntax schemaExampleComments
1Format designation

premis.object.objectCharacteristics

.format.formatDesignation

FormatDesignation

PREMIS container for the format name and version

PREMIS 3.0 Data

1

PREMIS 3.0 data dictionary lists all format properties as optional. However, this has the potential to record empty format instances. To prevent such occurrences, this document changes the obligation for formatDesignation to be mandatory.






FormatDesignation

S. NoLabelPropertyRangeUsageObligationVocab schemaSyntax schemaExampleComments
1Format name

premis.object.objectCharacteristics

.format.formatDesignation.formatName


 A mime type that describes the format of the file described by this object. The file should ideally be in a recognized preservation format.1List of IANA-recognized media type from the list located at:  https://www.iana.org/assignments/media-types/media-types.xhtml
 image/tiff
2Format version

premis.object.objectCharacteristics

.format.formatDesignation.formatVersion


 A version descriptor for the file encoding used by the file in this object.0-1






Event

NOTE: All constituent event objects (the components of which are listed below) will be enumerated in a list called eventList within each metadata record. This is a deviation from full compliance with PREMIS, but is necessitated by limitations of our database software (MongoDB), which does not allow records to have multiple fields with the same field name. 

S. No.LabelPropertyRangeUsageObligationVocab schemaSyntax schemaExampleComments
1Event Identifier

premis.event

.eventIdentifier

EventIdentifierA designation used to identify the Event uniquely within the preservation repository system.1



2Event Type

premis.event

.eventType


A categorization of the nature of the Event1

Event type controlled vocabulary


ingestion,

migration


3Event Date Time

premis.event

.eventDateTime


The single date and time, or date and time range, at or during which the Event occurred. 1Extended Date-Time format: EDTF (LoC)

20050704T071530-0500 [July 4, 2005 at 7:15:30 a.m. EST]

2006-07-16T19:20:30+01:00

20050705T0715-0500/20050705T0720-0500 [from 7:15 a.m. EST to 7:20 a.m. EST on July 4, 2005]

2004-03-17 [March 17, 2004, only the date is known]

Recommended practice is to record the most specific time possible and to designate the time zone.
4Event Detail Information

premis.event

.eventDetailInformation

EventDetailInformation
0-n


Additional information about the Event.
5Event Outcome Information

premis.event

.eventOutcomeInformation

EventOutcomeInformation
0-1


Information about the outcome of the Event
6Linking Agent Identifier

premis.event

.linkingAgentIdentifier

LinkingAgentIdentifier
0-1


Identification of one or more Agents associated with the Event.


EventIdentifier

S. No.LabelPropertyRangeUsageObligationVocab schemaSyntax schemaExampleComments
1Event identifier type

premis.event.eventIdentifier

.eventIdentifierType


Type of the identifier code. This information should include sufficient detail about the program, module, and version that was used to create this identifier, separated using semi-colons. A designation of the domain within which the Event identifier is unique.1



2Event identifier value

premis.event.eventIdentifier

.eventIdentifierValue


The unique value generated for this event within the scope of the identifier type.1

070a365f-8f9b-4071-a33e-9e569253f7eb


EventType

Sources used to compose the following set of terms: LoC Vocab, PBWorks, Chicago Lib and other vocabs, project-specific considerations.

S. No.LabelVocabulary Term (metadata)EventDetailExtension EntityDefinition/descriptionLinkComment
1Accessionaccession
Inclusion of a digital record in a tracked inventory, for example, inclusion of the record in a database of tracked documents.

2Capturecapture
First inclusion of a digital record in a preservation environment.

3Creationcreation
Digitization of a physical record

4Filename changefilenameChangeCSHEventDetailFileSourceDestination

Change of filename of a digital record, for example, as effected by a "rename" or "move" command in the operating system.

This event must include the filename after the change and may include the name prior to the change.



5Fixity checkfixityCheck

Comparison of the current message digest of the record with a known message digest, calculated using the same method as the one used to generate the known message digest.

This event should record the outcome.



6Format identificationformatIdentification

Identification of the file format used to encode the digital record via a known service such as JHove or via examination of the file extension.

This event should record the method used for identification.



7Identifier assignmentidentifierAssignmentCSHEventDetailIdentifierAssignment

Assignment of a unique identifier to a digital record.

This event should record the identifier assigned.



8Message digest calculationmessageDigestCalculationCSHEventDetailMessageDigestCalculation

Computation and storage of a message digest for this digital record for future fixity checks.

This event must record both: the method used for calculating the message digest and the message digest generated.



9Metadata extractionmetadataExtraction (propertyExtraction)

CSHEventDetailMetadataExtraction

Extraction of metadata from the digital record.

This event should record the metadata extracted from the record.



10Metadata modificationmetadataModification

CSHEventDetailMetadataModification

Modification of metadata associated with the record.

This event should record the affected fields (or properties) as well as their values before and after the modification.



11ReplicationreplicationCSHEventDetailFileSourceDestination

Copying digital record from one disk location to another, for example, as effected by a "copy" command in the operating system.

This event should record the location (path) of the file prior to and after the operation.




12MigrationmigrationCSHEventDetailMigration

The act of transforming an object from one file format(s) into another file format(s).

Migration events should always create a new object. This term is narrower than the OAIS definition.





EventDetailInformation

NOTE: All eventDetailInformation objects will be enumerated in a list called eventDetailInformationList within event object. This is a deviation from full compliance with PREMIS, but is necessitated by limitations of our database software (MongoDB), which does not allow records to have multiple fields with the same field name.

S. No.LabelPropertyRangeUsageObligationVocab schemaSyntax schemaExampleComments
1Event Detail

premis.event.eventDetailInformation

.eventDetail


Additional information about the Event. PREMIS specifies that multiple details should be recorded in independent eventDetailInformation containers rather than merely repeating the eventDetail element/attribute.0-1

  • Object permanently withdrawn on the request of the Library of Virginia
  • Program="python"; version="3.6"

2Event Detail Extension

premis.event.eventDetailInformation

.eventDetailExtension

Event detail extension (An entity corresponding to the EventDetailExtension Entity field in the EventType controlled vocabulary table)Specific details about the event. These details vary by event type. The value of this property will be an object that is identified in the EventType controlled vocabulary.0-n



EventDetailExtension

CSHEventDetailMessageDigestCalculation

S. NoLabelPropertyRangeUsageObligationVocab schemaSyntax schemaExampleComments
1Programming Language

premis.event.eventDetailInformation

.eventDetailExtension.programmingLanguage


The name of the programming language using which the event was executed.

Must specify the version number of the language/interpreter/compiler.

0-1

  • Python 3.4.3

2Method

premis.event.eventDetailInformation

.eventDetailExtension.method


The exact name of the method (i.e. a function in a programming language) used for carrying out an event; preferably qualified/prefixed with the name of the module/library in which the method is defined.0-1

  • uuid.uuid4()
  • hashlib.md5()

3Algorithm

premis.event.eventDetailInformation

.eventDetailExtension.algorithm


The name of the algorithm using which the event was executed.

Should specify the version of the algorithm if that information is available/relevant.

0-1

  • UUID v4

4Message Digest

premis.event.eventDetailInformation

.eventDetailExtension.messageDigest


The checksum generated as part of the event.

Applies only to the messageDigestCalculation event

0-1

d41d8cd98f00b204e9800998ecf8427e


CSHEventDetailIdentifierAssignment

S. NoLabelPropertyRangeUsageObligationVocab schemaSyntax schemaExampleComments
1Programming Language

premis.event.eventDetailInformation

.eventDetailExtension.programmingLanguage


The name of the programming language using which the event was executed.

Must specify the version number of the language/interpreter/compiler.

0-1

  • Python 3.4.3

2Method

premis.event.eventDetailInformation

.eventDetailExtension.method


The exact name of the method (i.e. a function in a programming language) used for carrying out an event; preferably qualified/prefixed with the name of the module/library in which the method is defined.0-1

  • uuid.uuid4()
  • hashlib.md5()

3Algorithm

premis.event.eventDetailInformation

.eventDetailExtension.algorithm


The name of the algorithm using which the event was executed.

Should specify the version of the algorithm if that information is available/relevant.

0-1

  • UUID v4

4ID Assigned

premis.event.eventDetailInformation

.eventDetailExtension.idAssigned


The id generated specific to the event. Applies only to the identifierAssignment
event

0-1

  • aa93198e-0adb-4377-98a5-0eee796d8ec6


CSHEventDetailFileSourceDestination

S. No.LabelPropertyRangeUsageObligationVocab schemaSyntax schemaExampleComments
1Source

premis.event.eventDetailInformation

.eventDetailExtension.source


The absolute path of the source file. Applies only to the following events:

  • replication
  • filenameChange
0-1



2Destination

premis.event.eventDetailInformation

.eventDetailExtension.destination


The absolute path of the destination file. Applies only to the following events:

  • replication
  • filenameChange
0-1



CSHEventDetailMetadataExtraction

S. NoLabelPropertyRangeUsageObligationVocab schemaSyntax schemaExampleComments
1Programming Language

premis.event.eventDetailInformation

.eventDetailExtension.programmingLanguage


The name of the programming language using which the event was executed.

Must specify the version number of the language/interpreter/compiler.

0-1

  • Python 3.4.3

2Method

premis.event.eventDetailInformation

.eventDetailExtension.method


The exact name of the method (i.e. a function in a programming language) or the software and version used for carrying out the event; preferably qualified/prefixed with the name of the module/library in which the method is defined.0-1

  • ImageMagick - identify, version xyz


3Extracted Metadata

premis.event.eventDetailInformation

.eventDetailExtension.extractedMetadata


The metadata extracted from the record. For textual metadata: the details formatted and as stored in the database. For visual metadata, a pointer (path/URL) to the file.

0-1




CSHEventDetailMetadataModification

S. No.LabelPropertyRangeUsageObligationVocab schemaSyntax schemaExampleComments
1Before

premis.event.eventDetailInformation

.eventDetailExtension.before


The metadata properties and values before the modification (may be empty when a new property is added).

0-1



2After

premis.event.eventDetailInformation

.eventDetailExtension.after


The metadata properties and values after the modification (may be empty when a property is deleted)

0-1




CSHEventDetailMigration

S. No.LabelPropertyRangeUsageObligationVocab schemaSyntax schemaExampleComments
1FileType

premis.event.eventDetailInformation

.eventDetailExtension.fileType



0-1



2FileSize

premis.event.eventDetailInformation

.eventDetailExtension.fileSize



0-1



3ImageWidth

premis.event.eventDetailInformation

.eventDetailExtension.imageWidth








4ImageHeight

premis.event.eventDetailInformation

.eventDetailExtension.imageHeight








5FileName

premis.event.eventDetailInformation

.eventDetailExtension.fileName






































EventOutcomeInformation

S. No.LabelPropertyRangeUsageObligationVocab schemaSyntax schemaExampleComments
1Event outcome

premis.event.eventOutcomeInformation

.eventOutcome


A categorization of the overall result of the Event in terms of success, partial success, or failure.

A coded way of representing the outcome of an Event may be useful for machine processing and reporting. If, for example, a fixity check fails, the Event record provides both an actionable and a permanent record.

1Project-specific controlled vocabulary

00 [a code meaning “action successfully completed”]

CV-01 [a code meaning “checksum validated”]


Recommended practice is to use a controlled vocabulary that a system can act upon automatically. Because this is inherently a local vocabulary, there is no general one available. More detail about the outcome may be recorded in eventOutcomeDetail.

Recommended practice is to daefine Events with sufficient granularity that each Event has a single outcome.

2Event outcome detail

premis.event.eventOutcomeInformation

.eventOutcomeDetail

EventOutcomeDetailNote

A detailed description of the result or product of the Event.

An Event outcome may be sufficiently complex that a coded description is not adequate to document it.


0-1


This may be used to record all error and warning messages issued by a program involved in the Event or to record a pointer to an error log.

If the Event was a validity check (e.g., profile conformance) any anomalies or quirks discovered would be recorded here.

All subunits of this semantic unit are optional. At least one subunit (i.e. eventOutcomeDetailNote and/or eventOutcomeDetailExtension) must be present if this container is included.

EventOutcome

Based on project-specific considerations.

S. No.LabelVocabulary Term (metadata)Definition/descriptionLinkComment
1SuccesssuccessUsed when the outcome of the associated event was a success

2FailurefailureUsed when the outcome of the associated event was a failure


EventOutcomeDetailNote

S. No.LabelPropertyRangeUsageObligationVocab schemaSyntax schemaExampleComments
1Event Outcome Detail Note

premis.event.eventOutcomeInformation

.eventOutcomeDetail.eventOutcomeDetailNote


Additional information about the Event outcome.1



LinkingAgentIdentifier

S. No.LabelPropertyRangeUsageObligationVocab schemaSyntax schemaExampleComments
1Linking agent identifier type

premis.event.linkingAgentIdentifier

.linkingAgentIdentifierType


A descriptor for the agent type that is related to this event. 1Agent Type Controlled vocabulary (organization, person, program, role)

LCNAF

SAN

DLC

URI

local


2Linking agent identifier value

premis.event.linkingAgentIdentifier

.linkingAgentIdentifierValue


The value identifying the agent that is related to this event.1

92-79971

Owens, Erik C.

234-5676

MH-CS

info:lccn/n78890351


3Linking agent role

premis.event.linkingAgentIdentifier

.linkingAgentRole


The role played by the agent in this event.0-1Values from the controlled vocabulary available at: http://id.loc.gov/vocabulary/preservation/eventRelatedAgentRole.

authorizer

implementer

validator

executing program




Additional Resources

Common standards/vocabularies for preservation:http://id.loc.gov/preservationdescriptions/
PREMIS 3.0 schema: http://www.loc.gov/standards/premis/premis.xsd

THIS PAGE IS IN PROGRESS

It may be best, since the registers exist as aggregate items (intellectually existing as the sum of all scanned pages and not a single digital object) to have preservation metadata operate at the same level as technical: for the single object only. Unlike a complex representation- ie, a website which is dependent on multiple files, pages, and formats- the registers do not have separate identifiable preservation requirements from any given part of themselves; their relationships are hasPart and isPartOf, not necessarily dependencies in and of themselves. It might be better to do the description at the register/aggregate level- complimentary to the item-level descriptive metadata- than at the preservation level. I'm still thinking it through.


This is a hierarchical listing of the semantic units included in the Data Dictionary. The information in parentheses following each semantic unit indicates whether the element is Mandatory (M) or Optional (O), followed by whether it is Repeatable (R) or Not repeatable (NR). Some semantic units in the Object section are further divided by the types of representation, file, and bitstream. Where not qualified, the designations apply to all three types. Where qualified, only the types listed are applicable.

1. Object: <file>

1.1    objectIdentifier (M, R)
        1.1.1    objectIdentifierType (M, NR) <local>
        1.1.2    objectIdentifierValue (M, NR) <normalized_file_name.tif>
1.2    objectCategory (M, NR) <file>
1.3    preservationLevel (O, R) [Intellectual Entity, Representation, File]
        1.3.1    preservationLevelType (O, NR) [Intellectual Entity, Representation, File]
        1.3.2    preservationLevelValue (M, NR) [Intellectual Entity, Representation, File]
        1.3.3    preservationLevelRole (O, NR) [Intellectual Entity, Representation, File] <controlled vocabulary is available for this value, but no other preservationLevel components?>
        1.3.4    preservationLevelRationale (O, R) [Intellectual Entity, Representation, File]
        1.3.5    preservationLevelDateAssigned (O, NR) [Intellectual Entity, Representation, File]
1.4    significantProperties (O, R) <as these are digitized items, this may include more "content" terms- structure, page width, etc- than "format" terms- hyperlinks, behavior: each new property requires a new significantProperties entry>
        1.4.1    significantPropertiesType (O, NR)
        1.4.2    significantPropertiesValue (O, NR)
        1.4.3    significantPropertiesExtension (O, R)
1.5    objectCharacteristics (M, R) [File, Bitstream]
        1.5.1    compositionLevel (O, NR) [File, Bitstream] <If an item is a compressed or encrypted version of another item, this value indicates how many steps backward must be made to recreate the original: so if File A is first compressed into File B and then File B is encrypted into File C, File C has a composition level of 2, indicating 2 decodings (decryption then decompression) must occur before the original file/object (File A) can be recovered. Possibly applicable to derivatives, if we decide to treat them as objects in themselves. Since the scans we have are the "original" digital objects, however, I'm not sure that we need to record the compression level of (for instance) images here, since it is not a question of decompressing them into a previous file. Compression occurred at creation, and should in those cases be noted in the descriptive metadata.>
        1.5.2    fixity (O, R) [File, Bitstream]
                   1.5.2.1    messageDigestAlgorithm (M, NR) [File, Bitstream] <SHA-1>
                   1.5.2.2    messageDigest (M, NR) [File, Bitstream] <algorithm result returned>
                   1.5.2.3    messageDigestOriginator (O, NR) [File, Bitstream] <Agent, whether a text string referring to a person or the Archive as a whole; or an agentIdentifierValue- taken from the Event listing, linked to an Agent record (a pointer, in other words), which could be a person, institution, or software.>
        1.5.3    size (O, NR) [File, Bitstream] <file size in bytes>
        1.5.4    format (M, R) [File, Bitstream] <the most specific applicable format of the file: where multiple formats/versions are equally specific and correct, this can be repeated>
                   1.5.4.1    formatDesignation (O, NR) [File, Bitstream] <usually, either this value or formatRegistry is used: one of the two is required>
                        1.5.4.1.1    formatName (M, NR) [File, Bitstream] <image/tiff/if there is a more specific level it goes here (e.g., geotiff)>
                        1.5.4.1.2    formatVersion (O, NR) [File, Bitstream] <version of said format, if applicable>
                   1.5.4.2    formatRegistry (O, NR) [File, Bitstream] <given that we are not dealing with Weird File Types, and in the interests of greater data interoperability, I recommend this value over formatDesignation>
                        1.5.4.2.1    formatRegistryName (M, NR) [File, Bitstream] <where the format is registered: e.g., PRONOM>
                        1.5.4.2.2    formatRegistryKey (M, NR) [File, Bitstream] <fmt/353 (the basic registry for TIFF files)>
                        1.5.4.2.3    formatRegistryRole (O, NR) [File, Bitstream] <in this case, "specification" (see controlled vocabulary)>
                   1.5.4.3    formatNote (O, R) [File, Bitstream] <any additional information, if required: generally used in speculative cases ("we think this is the format/version")>
        1.5.5    creatingApplication (O, R) [File, Bitstream]
                   1.5.5.1    creatingApplicationName (O, NR) [File, Bitstream]
                   1.5.5.2    creatingApplicationVersion (O, NR) [File, Bitstream]
                   1.5.5.3    dateCreatedByApplication (O, NR) [File, Bitstream]
                   1.5.5.4    creatingApplicationExtension (O, R) [File, Bitstream]
        1.5.6    inhibitors (O, R) [File, Bitstream]
                   1.5.6.1    inhibitorType (M, NR) [File, Bitstream]
                   1.5.6.2    inhibitorTarget (O, R) [File, Bitstream]
                   1.5.6.3    inhibitorKey (O, NR) [File, Bitstream]
        1.5.7    objectCharacteristicsExtension (O, R) [File, Bitstream]
1.6    originalName (O, NR) [Intellectual Entity, Representation, File]
1.7    storage (O, R) [Representation, File, Bitstream]
        1.7.1    contentLocation (O, NR) [Representation, File, Bitstream]
                   1.7.1.1    contentLocationType (M, NR) [Representation, File, Bitstream]
                   1.7.1.2    contentLocationValue (M, NR) [Representation, File, Bitstream]
        1.7.2    storageMedium (O, NR) [Representation, File, Bitstream]
1.8    signatureInformation (O, R) [File, Bitstream]
        1.8.1    signature (O, R) [File, Bitstream]
                   1.8.1.1    signatureEncoding (M, NR) [File, Bitstream]
                   1.8.1.2    signer (O, NR) [File, Bitstream]
                   1.8.1.3    signatureMethod (M, NR) [File, Bitstream]
                   1.8.1.4    signatureValue (M, NR) [File, Bitstream]
                   1.8.1.5    signatureValidationRules (M, NR) [File, Bitstream]
                   1.8.1.6    signatureProperties (O, R) [File, Bitstream]
                   1.8.1.7    keyInformation (O, NR) [File, Bitstream]
        1.8.2    signatureInformationExtension (O, R) [File, Bitstream]
1.9    environmentFunction (O, R) [Intellectual Entity of type environment]
        1.9.1      environmentFunctionType (M, NR) [Intellectual Entity of type environment]
        1.9.2      environmentFunctionLevel (M, NR) [Intellectual Entity of type environment]
1.10  environmentDesignation (O, R) [Intellectual Entity of type environment]
        1.10.1     environmentName (M, NR) [Intellectual Entity of type environment]
        1.10.2     environmentVersion (O, NR) [Intellectual Entity of type environment]
        1.10.3      environmentOrigin (O, NR) [Intellectual Entity of type environment]
        1.10.4     environmentDesignationNote (O, R) [Intellectual Entity of type environment]
        1.10.5      environmentDesignationExtension (O, R) [Intellectual Entity of type environment]
1.11  environmentRegistry (O, R) [Intellectual Entity of type environment]
        1.11.1     environmentRegistryName (M, NR) [Intellectual Entity of type environment]
        1.11.2     environmentRegistryKey (M, NR) [Intellectual Entity of type environment]
        1.11.3     environmentRegistryRole (O, NR) [Intellectual Entity of type environment]
1.12  environmentExtension (O, R) [Intellectual Entity of type environment]
1.13  relationship (O, R)
       1.13.1  relationshipType (M, NR)
       1.13.2  relationshipSubType (M, NR)
       1.13.3  relatedObjectIdentifier (M, R)
                 1.13.3.1  relatedObjectIdentifierType (M, NR)
                 1.13.3.2  relatedObjectIdentifierValue (M, NR)
                 1.13.3.3  relatedObjectSequence (O, NR)
       1.13.4  relatedEventIdentifier (O, R)
                 1.13.4.1  relatedEventIdentifierType (M, NR)
                 1.13.4.2  relatedEventIdentifierValue (M, NR)
                 1.13.4.3  relatedEventSequence (O, NR)
       1.13.5  relatedEnvironmentPurpose (O, R) [Representation, File, Bitstream]
       1.13.6  relatedEnvironmentCharacteristic (O, NR) [Representation, File, Bitstream]
1.14  linkingEventIdentifier (O, R)
        1.14.1  linkingEventIdentifierType (M, NR)
        1.14.2  linkingEventIdentifierValue (M, NR)
1.15  linkingRightsStatementIdentifier (O, R)
        1.15.1  linkingRightsStatementIdentifierType (M, NR)
        1.15.2  linkingRightsStatementIdentifierValue (M, NR)