Child pages
  • Technical Metadata Application Profile

This wiki space is deprecated

This wiki space is now deprecated. The wiki for Samvera (formerly the Hydra Project) is now to be found here: Samvera

Skip to end of metadata
Go to start of metadata

 

This is a baseline application profile for technical metadata properties attached to binary objects in a repository.

For specific formats (image, video, web archive) other properties will be useful. In general, we encourage reusing existing vocabularies, particularly those vocabularies that are both actively maintained and those that are already used by this profile.

Namespaces

 

Properties

Property name: ebucore:filename

 

URI

http://www.ebu.ch/metadata/ontologies/ebucore/ebucore#filename

Label

File Name

Definition

The name of the file containing the Resource.

Subproperty of

 

Equivalent property

nfo:fileName, premis:hasOriginalName

Domain

ebucore:Resource

Range

xsd:string

Obligation & Occurrence

Required (Minimum: 1, Maximum: 1)

Example

yul-269695.OBJ.pdf

Comment

 

 

Property name: ebucore:fileSize

 

URI

http://www.ebu.ch/metadata/ontologies/ebucore/ebucore#fileSize

Label

File Size

Definition

to provide the size of a MediaResource in bytes.

Subproperty of

 

Equivalent property

nfo:fileSize, dct:extent, premis:hasSize

Domain

ebucore:Resource

Range

xsd:integer

Obligation & Occurrence

Required (Minimum: 1, Maximum: 1)

Example

709162

Comment

 

 

Property name: rdfs:label

 

URI

http://www.w3.org/2000/01/rdf-schema#label

Label

Label

Definition

Descriptive label

Subproperty of

 

Equivalent property

 

Domain

 

Range

xsd:string

Obligation & Occurrence

Recommended (Minimum: 0, Maximum: 1)

Example

Unmodified original

Comment

 

 

Property name: ebucore:dateCreated

 

URI

http://www.ebu.ch/metadata/ontologies/ebucore/ebucore#dateCreated

Label

Date Created

Definition

The date of creation of the media resource.

Subproperty of

dct:date

Equivalent property

nfo:fileCreated, dct:created

Domain

ebucore:Resource

Range

 

Obligation & Occurrence

Recommended (Minimum: 0, Maximum: 1)

Example

2013-11-29T13:56:46-04:00

Comment

 

 

Property name: premis:hasMessageDigest

 

URI

http://www.loc.gov/premis/rdf/v1#hasMessageDigest

Label

File Hash

Definition

The output of the message digest algorithm.

Subproperty of

 

Equivalent property

ebucore:hash, nfo:hasHash

Domain

premis:Fixity

Range

xsd:string

Obligation & Occurrence

Recommended (Minimum: 0, Maximum: n)

Example

7c9b35da4f2ebd436f1cf88e5a39b3a257edf4a22be3c955ac49da2e2107b67a1924419563

Comment

 

 

Property name: premishash:md5

URIhttp://id.loc.gov/vocabulary/preservation/cryptographicHashFunctions/md5
LabelMD5 checksum
DefinitionThe MD5 checksum of the file content
Subproperty of 
Equivalent property 
Domain 
Range 
Obligation & OccurrenceOptional (Minimum: 0, Maximum: 1)
Example

d3b07384d113edec49eaa6238ad5ff00

CommentSee the PREMIS crypographic hash functions for recording other types of checksums.

 

Property name: rdf:type

 

URI

http://www.w3.org/1999/02/22-rdf-syntax-ns#type

Label

File Format Type

Definition

Category or Genre of the File

Subproperty of

 

Equivalent property

 

Domain

rdf:Resource

Range

pcdm:Document

Obligation & Occurrence

Recommended (Minimum: 0, Maximum: 1)

Example

pcdm:Presentation

Comment

 

 

Property name: ebucore:hasMimeType

 

URI

http://www.ebu.ch/metadata/ontologies/ebucore/ebucore#hasMimeType

Label

Has Mime Type

Definition

 

Subproperty of

 

Equivalent property

dct:format, pronom:internetMediaType

Domain

 

Range

xsd:string

Obligation & Occurrence

Recommended (Minimum: 0, Maximum: 1)

Example

application/pdf

Comment

Another possible equivalent property could be premis:hasFormatName.

 

Property name: ebucore:dateModified

 

URI

http://www.ebu.ch/metadata/ontologies/ebucore/ebucore#dateModified

Label

Date Modified

Definition

To indicate the date at which the media resource has been modified.

Subproperty of

dct:modified

Equivalent property

nfo:fileLastModified, dct:modified

Domain

 

Range

 

Obligation & Occurrence

Optional (Minimum: 0, Maximum: 1)

Example

2013-11-29T13:56:46-04:00

Comment

 

 

Property name: pronom:puid

 

URI

 

Label

File Format

Definition

Pronom ID to uniquely identify file format

Subproperty of

 

Equivalent property

premis:hasFormatName + premis:hasFormatVersion

Domain

 

Range

xsd:string

Obligation & Occurrence

Optional (Minimum: 0, Maximum: 1)

Example

fmt/20

Comment

Here the equivalent property should be premis:hasFormatRegistryKey.

 

Property name: sweetjpl:hasByteOrder

 

URI

http://sweet.jpl.nasa.gov/2.2/reprDataFormat.owl#hasByteOrder

Label

Byte Order

Definition

 

Subproperty of

 

Equivalent property

 

Domain

 

Range

sweetjpl:ByteOrder

Obligation & Occurrence

Optional (Minimum: 0, Maximum: 1)

Example

http://sweet.jpl.nasa.gov/2.2/reprDataFormat.owl#LittleEndian

Comment

 

Distinguishing Between Archival Objects and Derivatives

Detailed Technical Metadata Captured as XML

If you are using a detailed technical metadata, such as FITS output, and you have a NonRdfSource repository Object, the following recommendation conforms to PCDM structure:

      • The PCDM documentation suggests using a hasRelatedFile property for these types of files
      • Use the iana:describes / iana:describedBy properties to link such "related" files to their source files. E.g.:

        <> a pcdm:Object ;
             pcdm:hasFile </some/source/file> ;
             pcdm:hasRelatedFile </some/fits/xml/output> .

        </some/source/file> a pcdm:File .

        </some/fits/xml/output> a pcdm:File ;
             iana:describes </some/source/file> .

 

 

  • No labels

8 Comments

  1. Unknown User (escowles@ucsd.edu)

    For describing how different files relate to the parent object, there are at least two options that have been mentioned:

    • rdfs:label: used here to record "Unmodified original"
    • dams:use: the property used by UCSD, currently conflating use with mime type/category, but with the intention of moving towards the Sufia practice of having the value be "content", "thumbnail", "extracted text", etc.

    We should expand the description of rdfs:label here to explicitly cover the use property scenario.  We should also discuss values used by various implementations to see if we can come up with a common vocabulary for this.

  2. Specification of the range xsd:dateTime seems like a restriction on ebucore:dateTime which is simply specified as a sub-property of http://purl.org/dc/elements/1.1/modified which refines http://purl.org/dc/elements/1.1/date which has literal range with just a recommendation to use the W3C datetime values. IMO, the tighter restriction is fine but this should perhaps be noted a feature of this profile and not inherent in ebucore:dateTime.

    If the range is xsd:dateTime then the example is invalid. I think there should be a 'T' in the middle, not a space, ie. "2015:04:15T14:48:03-04:00" to follow http://www.w3.org/TR/xmlschema11-2/#dateTime.

  3. I don't think we want to be more restrictive than what ebucore itself states. Using ebucore:dateTime for the range on the date-related properties seems to be the correct thing to do.

    1. ebucore:dateTime is not a class/range, it is a generalized property of which ebucore:dateCreated and ebucore:dateModified are sub-properties.

      The range of these properties is just literal (following from sub-property relationships end at http://dublincore.org/documents/dcmi-terms/#terms-date) and not xsd:dateTime (as suggested above). If there is not the willingness to be more restrictive then perhaps at least a note recommending best-practice use of a date compatible with xsd:dateTime would still be helpful?

      1. My comment above is not correct because there isn't actually any definition of an ebucore:dateTime as far as I can see (that appears only in the draft above as far as I can tell). However, within the ebucode ontology [1] they define ebucore:dateCreated and a sub-property of dc:date (where dc stands for dcterms) and then say define dc:date to have a range of xsd:dateTime:

        ebucore:dateCreated a owl:DatatypeProperty ;
        rdfs:comment "The date of creation of the Resource."@en ;
        rdfs:label "Creation date/time"@en ;
        rdfs:subPropertyOf dc:date ;
        owl:equivalentProperty <http://www.w3.org/ns/ma-ont#creationDate> .
        dc:date a owl:DatatypeProperty ;
        rdfs:comment "A date associated with the BusinessObject, Resource or Contact/Person."@en ;
        rdfs:label "date"@en ;
        rdfs:range xsd:dateTime .

        I don't think that is kosher because that is not the definition at http://dublincore.org/documents/dcmi-terms/#terms-date which says:

        [1] -  looking that the n3 of the ebucore ontology seems much easier than the ontology viewer: http://lov.okfn.org/dataset/lov/vocabs/ebucore/versions/2015-01-11.n3 . I guess that must be on the ebu site somewhere but did not find it. 

         

  4. The latest version of the EBUCore RDF Ontology as RDF/XML is available from the Annex B: EBUCore and Semantic Web section of the EBU Core Metadata Set publication (PDF) within EBUCore's Metadata Specification site. Like the n3 version, that also says that ebucore:dateCreated is a subProperty of dc:date, not ebucore:dateTime.

    A range is not specified for ebucore:dateCreated but to follow what dc:date recommends as best practice is to use the W3CDTF profile of ISO 8601, which is a string and would be an example along the lines of what you are describing, including the "T." To be current with ebucore's dateCreated property, we should change the subProperty to dc:date and the example to 2013-11-29T13:56:46-04:00 to match the W3CDTF profile and be clearer about month/day order. We can also include a comment regarding the recommendation to use the W3CDTF profile.

  5. Why are size and filename required? This seems like duplicate information because Fedora is already storing that when you set Content-Length and Content-Disposition/filename.

  6. If the "pronom" namespace is unpublished, how are predicates therefrom getting called out here?!?!