Section 7

Namespace

(move here section 5.1.1)

Correspondence between the informal ontology and the RDF representation

The following table gives the correspondence between the core properties as described in section REF and the RDF vocabulary given below.

Unless stated otherwise, atomic values are represented by literals while complex values are represented by resources. It follows that, in the general case, properties with complex values are represented by object properties, while properties with simple values are represented by datatype properties. Attributes in complex values are represented by properties of the resource representing the complex value; depending on their semantics, they are represented by datatype or object properties.

The RDF ontology also introduces a number of classes corresponding to the domains and ranges of the corresponding property.

Identification
identifier ma:identifier or (1)
title ma:title
title.title (value of the ma:title property)
title.type (2)
language ma:hasLanguage (3)
locator ma:locator
Creation
contributor ma:hasContributor
contributor.identifier ma:contributorIs (3)
contributor.role (2)
creator ma:hasCreator
creator.identifier ma:creatorIs
createDate ma:creationDate
createDate.date (value of the ma:creationDate property)
createDate.type (2)
location ma:hasRelatedLocation (see location.name)
location.name (URI or rdfs:label) (4)
location.longitude ma:locationLongitude
location.latitude ma:locationLatitude
location.altitude ma:locationAltitude
location.coordinateSystem ma:locationCoordinateSystem
Content description
description ma:description
keyword ma:hasKeyword (3)
genre ma:hasGenre (3)
rating ma:hasRating
rating.value ma:ratingValue
rating.identifier ma:isProvidedBy
rating.type ma:hasRatingScheme
rating.min ma:ratingScaleMin
rating.max ma:ratingScaleMax
Relational
relation ma:isRelatedTo (see relation.identifier)
relation.identifier (URI or rdfs:label) (4)
relation.relation (2)
collection ma:isMemberOf (3)
Rights
copyright (5)
copyright.copyright ma:copyright
copyright.identifier ma:isCopyrightedBy
policy ma:hasPolicy (see policy.policy)
policy.policy (URI or rdfs:label) (4)
policy.type (2)
Distribution
publisher ma:hasPublisher o ma:publisherIs (6)(3)
targetAudience ma:hasTargetAudience
targetAudience.identifier ma:hasClassificationScheme
targetAudience.classification ma:hasClassification
Fragment
fragment ma:hasFragment
fragment.identifier (URI pointed by the ma:hasFragment property)
fragment.role (2)
namedFragment ma:hasFragment
namedFragment.identifier (URI pointed by the ma:hasFragment property)
namedFragment.label ma:fragmentName
Technical Properties
frameSize (5)
frameSize.width ma:frameWidth
frameSize.height ma:frameHeight
frameSize.unit ma:frameSizeUnit
compression ma:audioCompression / ma:videoCompression (7)
duration ma:duration
format ma:format
samplingRate ma:samplingRate
frameRate ma:frameRate
averageBitRate ma:averageBitRate
numTracks ma:numberOfTracks
numTracks.number (value of the ma:numberOfTracks property)
numTracks.type (2)
(1)

The URI of the RDF node is the identifier.

(2)

Different values of this attribute should be represented by subproperties of the original property; the ontology provides such subproperties for the most common cases.

(3)

If the value is a string, the RDF property should point to a blank node with that string as its rdfs:label; if the value is a URI, the RDF property should point to a resource with that URI.

(4)

The pattern is the same as (3), but the value to consider is that of an attribute of the complex value.

(5)

This property has no direct correspondence; the properties corresponding to the attributes of the complex value apply directly to the media resource.

(6)

The RDF ontology uses an intermediate resource to represent the publisher role; the publisher's URI is therefore referenced through the chain of those two properties.

(7)

Depending on the type of track it applies to.

RDF ontology

(insert or reference here the RDF document)