W3C

Ontology for Media Object 1.0

W3C Working Draft 17 March 2009

This version:
http://www.w3.org/TR/2009/WD-mediaont-1.0-20090317
Latest version:
http://www.w3.org/TR/mediaont-1.0
Editor:
@@@, @@@@

Abstract

This specification defines an ontology for cross-community data integration of information related to media objects on the Web. The purpose of the ontology is to help circumventing the profileration of video metadata formats by providing partial mappings between the existing formats.

Status of this Document

This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.

This is the First Public Working Draft of the Ontology for Media Object 1.0 specification. It has been produced by the Media Annotations Working Group, which is part of the W3C Video on the Web Activity.

Please send comments about this document to public-media-annotation@w3.org mailing list (public archive).

Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

Table of Contents

1 Introduction
    1.1 Purpose of this specification
    1.2 Formats in scope
    1.3 Formats out of scope
2 Terminology and Identifiers
    2.1 Terminology
    2.2 Identifiers of formats
3 Property value types definitions
    3.1 Basic property value types
        3.1.1 URI
        3.1.2 Date
4 Property definition
    4.1 Description of approach for the property definitions
    4.2 Property mapping table

Appendices

A References
B References (Non-Normative)
C Acknowledgements (Non-Normative)


1 Introduction

This section is informative.

1.2 Formats in scope

In this specification the following formats related to media objects on the Web have been taken into account .

Note:

This specification is based on a review of existing formats and the properties they provide. This review does not aim to be complete, and this specification does not aim to cover all properties defined in these formats. The choice of properties is motivated by their wide usage.

Editorial note  
This list needs to be brought in sync with the mapping table.

1.3 Formats out of scope

The following formats have been decided to be out of scope for this specification.

Editorial note  
This list needs to be brought in sync with the mapping table.

2 Terminology and Identifiers

This section is normative.

2.1 Terminology

The keywords MUST, MUST NOT, SHOULD and SHOULD NOT are to be interpreted as defined in RFC 2119.

[Definition: Media Entity]

A media entity is either a conceptual object (for example the play Hamlet by Shekespeare) or a concrete object: a media file of one interpretation of Hamlet, possibly online and possibly identified by a URL. These two types are respectively refered to by the terms of resource and representation in the W3C RDF Schema vocabulary. We adopt here this terminology in order to be consistent with the terminological choices of the W3C Media Fragments Working Group, which is closely related to our own activity. Another way of expressing this difference and thus the variety of media entities taken into account in this Working Group is the notions of Work and Item in FRBR (Note: FRBR also considers two other "intermediate" entity status between a Work and an Item).

[Definition: Property]

A property is an element from an existing metadata format for describing media entities on the web, or an element from the core vocabulary defined in this Working Group. For example, the Dublin Core creator element and the Media Ontology creator element are properties. A property links a Media Entity with a value: dc:creator links a given representation with the value of its creator (Dublin Core specifies: "Examples of a Creator include a person, an organization, or a service.", this value can be specified as a simple string or as the URI representing the creator. The set of properties selected to be part of the Media Ontology Core vocabulary is listed in section 4 Property definition.

[Definition: Resource]

A resource is an abstract concept, from which representation(s) can be derived: the general notion of the play Hamlet by Shakespeare for example, a "picture of a sunset", a concerto for violins etc.

[Definition: Representation]

A representation is a time-dependent document, or part of document, identifiable by a URI. For example: a portion of raw data of a video, an image, an audio, a text, any other time-aligned data or a composition of them.

[Definition: Mapping]

The notion of Mapping refers to the description of relations between elements of metadata shemas; in our case the mapping concerns the Vocabularies "in scope", and the properties of the core vocabulary of the Media Ontology. These Mappings are presented in section 4.2 Property mapping table.

[Definition: Property value types]

Property value types are the types of values used in a property. Property value types are defined in sec. 3 Property value types definitions. They are relying mostly on XML Schema data types XML Schema 2.

3 Property value types definitions

3.1 Basic property value types

3.1.1 URI

URI "Uniform Resource Identifier" are defined in RFC 3986. In this specification the term URI is used since it is well known. However the term is used as meaning IRIs "Internationalized Resource Identifiers (IRIs)" RFC 3987, that is URIs which may contain non-escaped characters other than ASCII. The data type is anyURI .

4 Property definition

This section is normative.

A References

[Dublin Core]
DCMI Metadata Terms. January 2008. Available at http://dublincore.org/documents/2008/01/14/dcmi-terms/ . The latest version of DCMI Metadata Terms is available at http://dublincore.org/documents/dcmi-terms/ .
[EXIF2.2]
EXIF 2.2. Specification by JEITA, April 2002. Available at http://www.exif.org/Exif2-2.PDF .
[HTML 5]
Hickson, I., and D. Hyatt. HTML 5. A vocabulary and associated APIs for HTML and XHTML. W3C Working Draft, June 2008. Available at http://www.w3.org/TR/2008/WD-html5-20080610/ . The latest version of HTML 5 is available at http://www.w3.org/TR/html5/ .
[MWG Guidelines Image]
Guidelines for handling image metadata, version 1.0.. Metadata Working Group, September 2008. Available at http://www.metadataworkinggroup.com/pdf/mwg_guidance.pdf .
[ID3]
ID3 tag version 2.3.0. February 1999. Available at http://www.id3.org/id3v2.3.0 .
[IPTC]
IPTC Standard Photo Metadata 2008. IPTC Core Specification Version 1.1, IPTC Extension Specification Version 1.0, Document Revision 2, June 2008. Available at http://www.iptc.org/std/photometadata/2008/specification/IPTC-PhotoMetadata-2008.pdf
[Media RSS]
Yahoo! Media RSS Module - RSS 2.0 Module. March 2008. Available at http://search.yahoo.com/mrss .
[MPEG 7]
MPGE 7 tbd.
[MPEG 21]
MPGE 21 tbd.
[RFC 3986]
Berners-Lee, T., R. Fielding, L. Masinter. Uniform Resource Identifier (URI): Generic Syntax. RFC 3986, January 2005. Available at http://www.ietf.org/rfc/rfc3986.txt
[RFC 3987]
Dürst, M. and M. Suignard. Internationalized Resource Identifiers (IRIs). RFC 3987, January 2005. Available at http://www.ietf.org/rfc/rfc3987.txt.
[XML Schema 2]
Biron, P. V. and A. Malhotra. XML Schema Part 2: Datatypes Second Edition. W3C Recommendation, October 2004. Available at http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/ . The latest version of XML Schema Part 2 is available at http://www.w3.org/TR/xmlschema-2/ .
[XMP]
XMP Specification Part 2 - Standard Schemas. Adobe, 2008. Available at http://www.adobe.com/devnet/xmp/pdfs/XMPSpecificationPart2.pdf .
[YouTube Data API Protocol]
YouTube Data API Protocol. April 2008. Available at http://code.google.com/intl/en/apis/youtube/2.0/reference.html .

B References (Non-Normative)

tbd

C Acknowledgements (Non-Normative)

This document is the work of the W3C Media Annotations Working Group.

Members of the Working Group are (at the time of writing, and by alphabetical order): Werner Bailer (K-Space), Tobias Bürger (University of Innsbruck), Eric Carlson (Apple, Inc.), Pierre-Antoine Champin ((public) Invited expert), Jaime Delgado (Universitat Politècnica de Catalunya), Jean-Pierre EVAIN ((public) Invited expert), Ralf Klamma ((public) Invited expert), WonSuk Lee (Electronics and Telecommunications Research Institute (ETRI)), Véronique Malaisé (Vrije Universiteit), Erik Mannens (IBBT), Hui Miao (Samsung Electronics Co., Ltd.), Thierry Michel (W3C/ERCIM), Michele Minno (Asemantics S.R.L.), Frank Nack (University of Amsterdam), Soohong Daniel Park (Samsung Electronics Co., Ltd.), Silvia Pfeiffer (W3C Invited Experts), Chris Poppe (IBBT), Víctor Rodríguez (Universitat Politècnica de Catalunya), Felix Sasaki (W3C/Keio), David Singer (Apple, Inc.), Joakim Söderberg (ERICSSON), Thai Wey Then (Apple, Inc.), Ruben Tous (Universitat Politècnica de Catalunya), Raphaël Troncy (CWI), Vassilis Tzouvaras (K-Space), Davy Van Deursen (IBBT).

The people who have contributed to http://lists.w3.org/Archives/Public/public-media-annotation/ are also gratefully acknowledged.