The ContentVersion of the CPL seems ideally suited for affixing the ISAN to the DCP. unfortunately the ContentVersion allows only the use of a single identifier wich is inappropriate in many situations.
In the near term, and until CPL specifications are amended for allowing multiple identifiers in the ContentVersion, the use of the CPL’s extension mechanism ExtensionMetadataList is priviledged.
Consequently, the following convention for carrying the ISAN in the DCP is proposed :
<ExtensionMetadataList>
<ExtensionMetadata scope="http://isan.org/ISAN/DCP2019">
<Name>ISAN</Name>
<PropertyList>
<Property>
<Name>ISAN content identifier</Name>
<Value>urn:isan:0123-1230-3210-2310-1-1234-1234-X</Value>
</Property>
</PropertyList>
</ExtensionMetadata>
</ExtensionMetadataList>
Comments
0 comments
Please sign in to leave a comment.