Overview.html 48.2 KB

Raw Blame History Permalink

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
      "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-us" lang="en-us">
<head>
  <meta http-equiv="content-type" content="text/html; charset=UTF-8" />
  <title>Ontology for Media Resource 1.0</title>
  <style type="text/css">
 /**/
code           { font-family: monospace; }
div.constraint,
div.issue,
div.note,
div.notice     { margin-left: 2em; }
ol.enumar      { list-style-type: decimal; }
ol.enumla      { list-style-type: lower-alpha; }
ol.enumlr      { list-style-type: lower-roman; }
ol.enumua      { list-style-type: upper-alpha; }
ol.enumur      { list-style-type: upper-roman; }
dt.label       { display: run-in; }
li, p           { margin-top: 0.3em;
                 margin-bottom: 0.3em; }
 .diff-chg       { background-color: yellow; }
 .diff-del       { background-color: red; text-decoration: line-through;}
 .diff-add       { background-color: lime; }
table          { empty-cells: show; }
table caption {
        font-weight: normal;
        font-style: italic;
        text-align: left;
        margin-bottom: .5em;
}
div.issue {
  color: red;
}
 .rfc2119 {
  font-variant: small-caps;
}
div.exampleInner pre { margin-left: 1em;
                       margin-top: 0em; margin-bottom: 0em}
div.exampleOuter {border: 4px double gray;
                  margin: 0em; padding: 0em}
div.exampleInner { background-color: #d5dee3;
                   border-top-width: 4px;
                   border-top-style: double;
                   border-top-color: #d3d3d3;
                   border-bottom-width: 4px;
                   border-bottom-style: double;
                   border-bottom-color: #d3d3d3;
                   padding: 4px; margin: 0em }
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
                    margin: 4px}
div.boxedtext {
   border: solid #bebebe 1px;
   margin: 2em 1em 1em 2em;
 }
span.practicelab {
   margin: 1.5em 0.5em 1em 1em;
   font-weight: bold;
   font-style: italic;
 }
span.practicelab   { background: #dfffff; }
 span.practicelab {
   position: relative;
   padding: 0 0.5em;
   top: -1.5em;
 }
p.practice
{
   margin: 1.5em 0.5em 1em 1em;
 }
@media screen {
 p.practice {
   position: relative;
   top: -2em;
   padding: 0;
   margin: 1.5em 0.5em -1em 1em;
}
}
/**/ </style>
  <link rel="stylesheet" type="text/css"
  href="http://www.w3.org/StyleSheets/TR/W3C-WD.css" />
</head>

<body>

<div class="head">
<p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home"
alt="W3C" height="48" width="72" /></a></p>

<h1><a name="title" id="title"></a>Ontology for Media Resource 1.0</h1>

<h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Working Draft 18 June
2009</h2>
<dl>
  <dt>This version:</dt>
    <dd><a
      href="http://www.w3.org/TR/2009/WD-mediaont-10-20090618">http://www.w3.org/TR/2009/WD-mediaont-10-20090618</a></dd>
  <dt>Latest version:</dt>
    <dd><a
      href="http://www.w3.org/TR/mediaont-10">http://www.w3.org/TR/mediaont-10</a></dd>
  <dt>Editors:</dt>
    <dd>WonSuk Lee, Electronics and Telecommunications Research Institute
    (ETRI)</dd>
    <dd>Tobias Bürger, University of Innsbruck</dd>
    <dd>Felix Sasaki, Potsdam University of Applied Sciences</dd>
    <dd>Véronique Malaisé, VU University of Amsterdam</dd>
    <dd>Florian Stegmaier, University of Passau</dd>
    <dd>Joakim Söderberg, Ericsson</dd>
</dl>

<p class="copyright"><a
href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2009 <a
href="http://www.w3.org/"><acronym
title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a
href="http://www.csail.mit.edu/"><acronym
title="Massachusetts Institute of Technology">MIT</acronym></a>, <a
href="http://www.ercim.org/"><acronym
title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
<a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a
href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
<a
href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>
and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document
use</a> rules apply.</p>
</div>
<hr />

<div>
<h2><a name="abstract" id="abstract"></a>Abstract</h2>

<p>This document defines the Ontology for Media Resource 1.0, a core vocabulary
to describe media resources on the Web. It is defined based on a common set of
properties which covers basic metadata to describe media resources. Further it
defines semantics-preserving mappings between elements from existing formats.
The ontology is supposed to foster the interoperability among various kinds of
metadata formats currently used to describe media resources on the Web.</p>
</div>

<div>
<h2><a name="status" id="status"></a>Status of this Document</h2>

<p><em>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 <a href="http://www.w3.org/TR/">W3C technical reports index</a> at
http://www.w3.org/TR/.</em></p>

<p>This is the <a
href="http://www.w3.org/2005/10/Process-20051014/tr.html#first-wd">First Public
Working Draft</a> of the Ontology for Media Resource 1.0 specification. It has
been produced by the <a
href="http://www.w3.org/2008/WebVideo/Annotations/">Media Annotations Working
Group</a>, which is part of the <a href="http://www.w3.org/2008/WebVideo/">W3C
Video on the Web Activity</a>. The Working Group expects to advance this
specification to <a
href="http://www.w3.org/2004/02/Process-20040205/tr.html#RecsW3C">Recommendation</a>
Status.</p>

<p>Please send comments about this document to <a
href="mailto:public-media-annotation@w3.org">public-media-annotation@w3.org</a>
mailing list (<a
href="http://lists.w3.org/Archives/Public/public-media-annotation/">public
archive</a>).</p>

<p>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. </p>

<p>This document was produced by a group operating under the <a
href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C
Patent Policy</a>. W3C maintains a <a
href="http://www.w3.org/2004/01/pp-impl/42786/status">public list of any patent
disclosures</a> 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 <a
href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
Claim(s)</a> must disclose the information in accordance with <a
href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
6 of the W3C Patent Policy</a>.</p>
</div>

<div class="toc">
<h2><a name="contents" id="contents"></a>Table of Contents</h2>

<p class="toc">1 <a href="#introduction">Introduction</a><br />
    1.1 <a href="#purpose">Purpose of this specification</a><br />
    1.2 <a href="#formats-in-scope">Formats in scope</a><br />
    1.3 <a href="#formats-out-of-scope">Formats out of scope</a><br />
2 <a href="#Terminology">Terminology</a><br />
3 <a href="#property-value-types-definitions">Property value type
definitions</a><br />
    3.1 <a href="#basic-property-value-types">Basic property value
types</a><br />
        3.1.1 <a href="#uri-value-type">URI</a><br />
        3.1.2 <a href="#date-value-type">Date</a><br />
    3.2 <a href="#complex-property-value-types">Complex property value
types</a><br />
4 <a href="#property-definition">Property definition</a><br />
    4.1 <a href="#core-property-definitions">Core property
definitions</a><br />
        4.1.1 <a href="#property-approach">Description of the approach
followed for the property definitions</a><br />
        4.1.2 <a href="#core-property-lists">Core properties</a><br />
    4.2 <a href="#property-mapping-table">Property mapping table</a><br />
        4.2.1 <a href="#rationale_mapping_table">Rationale regarding
the mapping table</a><br />
            4.2.1.1 <a href="#semantic-level-mappings">Semantic
Level Mappings</a><br />
            4.2.1.2 <a href="#syntactic-level-mappings">Syntactic
Level Mappings</a><br />
            4.2.1.3 <a href="#mapping-expression">Mapping
expression</a><br />
        4.2.2 <a href="#mapping-table">The mapping table</a><br />
</p>

<h3><a name="appendices" id="appendices"></a>Appendices</h3>

<p class="toc">A <a href="#references">References</a><br />
B <a href="#idinform-div1114292296">References</a> (Non-Normative)<br />
C <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br />
</p>
</div>
<hr />

<div class="body">

<div class="div1">
<h2><a name="introduction" id="introduction"></a>1 Introduction</h2>

<p><em>This section is informative.</em></p>

<p>This document introduces the Ontology for Media Resource 1.0, a core
vocabulary to describe <a title="media resource" href="#media-resource">media
resources</a>, mostly targeted to media resources on the Web. It is defined
based on a common set of <a title="property" href="#property">properties</a>
which covers basic metadata to describe <a title="media resource"
href="#media-resource">media resources</a>. For example <em>creator</em> is a
common property that is supported in several existing metadata formats, and is
therefore part of the core vocabulary defined by the Ontology. Further, the
Ontology defines mappings between elements from existing formats and our list
of properties. Ideally, the mappings should be semantics-preserving, but this
is not achieved with the first version of the Ontology (Media Ontology 1.0),
because of the difference in nature of the properties in the mapped
vocabularies their extension is not exactly overlapping. For example the <a
title="property" href="#property">property</a><em>dc:creator </em> from
<cite><a href="#dc">Dublin Core</a></cite> and the <a title="property"
href="#property">property</a><em>exif:Artist </em> defined in <cite><a
href="#exif">EXIF</a></cite> are both mapped to the property <em>creator</em>
of our Ontology, but the extension of the property in the exif vocabulary (the
set of values that the property can refer to) is more specific than the one of
Dublin Core. Mapping back and forth with our ontology as reference will hence
induce a certain loss of semantics. This is inevitable if we want to achieve a
certain amount of interoperability. </p>

<p>The Ontology, with the properties definition and mappings, provides the
basic information needed by targeted applications (see <a
href="http://www.w3.org/TR/2009/WD-media-annot-reqs-20090119/">Use Cases and
Requirements for Ontology and API for Media Object 1.0</a>) for supporting the
interoperability among the various kinds of metadata formats related to <a
title="media resource" href="#media-resource">media resources</a>, and
particularly media resources on the Web. In addition, the ontology will be
accompanied by an API that provides uniform access to all elements defined by
the ontology. </p>

<p>The initial version of this document contains only a limited set of
properties with their corresponding mappings to the vocabularies listed in
section <a href="#formats-in-scope"><b>1.2 Formats in scope</b></a>.
Nevertheless it is being published with the aspiration to gather wide feedback
on the general direction of the Working Group. In particular we would like to
encourage feedback on section <a href="#property-definition"><b>4 Property
definition</b></a>.</p>

<div class="div2">
<h3><a name="purpose" id="purpose"></a>1.1 Purpose of this specification</h3>

<p>This specification defines an ontology for cross-community data integration
of information related to <a title="media resource"
href="#media-resource">media resources</a>, with a particular focus on media
resources on the Web. The purpose of the ontology is to help circumventing the
current proliferation of video metadata formats by providing full or partial
translation and <a title="mapping" href="#mapping">mapping</a> towards existing
formats. </p>
</div>

<div class="div2">
<h3><a name="formats-in-scope" id="formats-in-scope"></a>1.2 Formats in
scope</h3>

<p>The following table lists the formats that were selected by the working
group as in-scope, along with the identifiers which are used as prefixes to
identify them in this specification.</p>

<div class="note">
<p class="prefix"><b>Note:</b></p>

<p>This specification is based on a review of existing formats and the <a
title="property" href="#property">properties</a> 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.</p>
</div>

<table border="1" width="100%">
  <tbody>
    <tr>
      <td align="center">Identifier</td>
      <td align="center">Format</td>
      <td align="center">Example</td>
      <td align="center">Reference</td>
    </tr>
    <tr>
      <td>cl11</td>
      <td>CableLabs 1.1</td>
      <td>cl11:Writer_Display</td>
      <td><cite><a href="#cablelabs1">Cablelabs 1.1</a></cite></td>
    </tr>
    <tr>
      <td>cl20</td>
      <td>CableLabs 2.0</td>
      <td>cl20:Producer</td>
      <td><cite><a href="#cablelabs2">Cablelabs 2.0</a></cite></td>
    </tr>
    <tr>
      <td>dig35</td>
      <td>DIG35</td>
      <td>dig35:ipr_name/ipr_person@description='Image Creator'</td>
      <td><cite><a href="#dig35">DIG35</a></cite></td>
    </tr>
    <tr>
      <td>dc</td>
      <td>Dublin Core</td>
      <td>dc:creator</td>
      <td><cite><a href="#dc">Dublin Core</a></cite></td>
    </tr>
    <tr>
      <td>ebucore</td>
      <td>EBUCore</td>
      <td>ebuc:creator</td>
      <td><cite><a href="#ebucore">EBUCore</a></cite></td>
    </tr>
    <tr>
      <td>pmeta</td>
      <td>EBU P-Meta</td>
      <td>pmeta:Contribution</td>
      <td><cite><a href="#ebup">EBU P-META</a></cite></td>
    </tr>
    <tr>
      <td>exif</td>
      <td>EXIF 2.2</td>
      <td>exif:Artist</td>
      <td><cite><a href="#exif">EXIF</a></cite></td>
    </tr>
    <tr>
      <td>frbr</td>
      <td>FRBR</td>
      <td>frbr:Person</td>
      <td><cite><a href="#frbr">FRBR</a></cite></td>
    </tr>
    <tr>
      <td>id3</td>
      <td>ID3</td>
      <td>id3:TCOM </td>
      <td><cite><a href="#id3">ID3</a></cite></td>
    </tr>
    <tr>
      <td>iptc</td>
      <td>IPTC</td>
      <td>iptc:Creator</td>
      <td><cite><a href="#iptc">IPTC</a></cite></td>
    </tr>
    <tr>
      <td>it</td>
      <td>iTunes</td>
      <td>it:©ART</td>
      <td><cite><a href="#itunes">iTunes</a></cite></td>
    </tr>
    <tr>
      <td>lom21</td>
      <td>LOM 2.1</td>
      <td>lom21:LifeCycle/Contribute/Entity</td>
      <td><cite><a href="#lom">LOM</a></cite></td>
    </tr>
    <tr>
      <td>ma</td>
      <td>Core properties of MA WG</td>
      <td>ma:creator</td>
      <td><a href="#property-definition"><b>4 Property definition</b></a></td>
    </tr>
    <tr>
      <td>media</td>
      <td>Media RDF</td>
      <td>media:Recording</td>
      <td><cite><a href="#mediardf">Media RDF</a></cite></td>
    </tr>
    <tr>
      <td>mrss</td>
      <td>Media RSS</td>
      <td>mrss:credit@role='author'</td>
      <td><cite><a href="#mediarss">Media RSS</a></cite></td>
    </tr>
    <tr>
      <td>mets</td>
      <td>METS</td>
      <td>mets:agency</td>
      <td><cite><a href="#mets">METS</a></cite></td>
    </tr>
    <tr>
      <td>mpeg7</td>
      <td>MPEG-7</td>
      <td>mpeg7:CreationInformation/Creation/Creator/Agent</td>
      <td><cite><a href="#mpeg7">MPEG-7</a></cite></td>
    </tr>
    <tr>
      <td>nmix</td>
      <td>NISO MIX</td>
      <td>nmix:ImageCreation/ImageProducer</td>
      <td><cite><a href="#mix">MIX</a></cite></td>
    </tr>
    <tr>
      <td>qt</td>
      <td>Quicktime</td>
      <td>qt:©dir</td>
      <td><cite><a href="#quictime">QuickTime</a></cite></td>
    </tr>
    <tr>
      <td>media</td>
      <td>SearchMonkey Media</td>
      <td>media:type</td>
      <td><cite><a href="#mediamonkey">MediaMonkey</a></cite></td>
    </tr>
    <tr>
      <td>dms</td>
      <td>DMS-1</td>
      <td>dms:Participant/Person</td>
      <td><cite><a href="#dms">DMS-1</a></cite></td>
    </tr>
    <tr>
      <td>tva</td>
      <td>TV-Anytime</td>
      <td>tva:CredistsList/CredistItem</td>
      <td><cite><a href="#tvanytime">TV-Anytime</a></cite></td>
    </tr>
    <tr>
      <td>txf</td>
      <td>TXFeed</td>
      <td>txf:author</td>
      <td><cite><a href="#txfeed">TXFeed</a></cite></td>
    </tr>
    <tr>
      <td>vra40</td>
      <td>VRA Core 4.0</td>
      <td>vra40:agent</td>
      <td><cite><a href="#vra">VRA</a></cite></td>
    </tr>
    <tr>
      <td>xmp</td>
      <td>XMP</td>
      <td>xmpDM:composer</td>
      <td><cite><a href="#xmp">XMP</a></cite></td>
    </tr>
    <tr>
      <td>yt</td>
      <td>YouTube Data API Protocol</td>
      <td>yt:author</td>
      <td><cite><a href="#youtube-data-api">YouTube Data API
      Protocol</a></cite></td>
    </tr>
  </tbody>
</table>
</div>

<div class="div2">
<h3><a name="formats-out-of-scope" id="formats-out-of-scope"></a>1.3 Formats
out of scope</h3>

<p>The following formats have been decided to be out of scope for this
specification.</p>
<ul>
  <li><p><cite><a href="#mpeg21">MPEG-21</a></cite></p>
  </li>
</ul>
</div>
</div>

<div class="div1">
<h2><a name="Terminology" id="Terminology"></a>2 Terminology</h2>

<p><em>This section is normative.</em></p>
<dl>
  <dt class="label">[<a name="media-resource" id="media-resource"
  title="media resource">Definition</a>: <b>Media Resource</b>]</dt>
    <dd><p>Any Resource (as defined by [<cite><a href="#rfc3986">RFC
      3986</a></cite>]) related to a media content. Note that [<cite><a
      href="#rfc3986">RFC 3986</a></cite>] points out that a resource may be
      retrievable or not. Hence, this term encompasses the abstract notion of a
      movie (e.g. Notting Hill) as well as the binary encoding of this movie
      (e.g. the MPEG-4 encoding of Notting Hill on my DVD), or any intermediate
      levels of abstraction (e.g. the director's cut or the plane version of
      Notting Hill). Although some ontologies (FRBR, BBC) define concepts for
      different such levels of abstraction, our ontology does not commit to any
      classification of media resources.</p>
    </dd>
  <dt class="label">[<a name="property" id="property"
  title="property">Definition</a>: <b>Property</b>]</dt>
    <dd><p>A property is an element from an existing metadata format for
      describing <a title="media resource" href="#media-resource">media
      resources</a>, or an element from the core vocabulary defined in this
      Working Group. For example, the <cite><a href="#dc">Dublin
      Core</a></cite><em>creator</em> element and the Media Ontology
      <em>creator</em> element are properties. A property links a <a
      title="media resource" href="#media-resource">Media Resource</a> with a
      value: <em>dc:creator</em> 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 <a href="#property-definition"><b>4 Property
      definition</b></a>.</p>
    </dd>
  <dt class="label">[<a name="mapping" id="mapping"
  title="mapping">Definition</a>: Mapping]</dt>
    <dd><p>The notion of Mapping refers to the description of relations between
      elements of metadata schemas; in our case the mapping concerns the
      Vocabularies "in scope", and the <a title="property"
      href="#property">properties</a> of the core vocabulary of the Media
      Ontology. These Mappings are presented in section <a
      href="#property-mapping-table"><b>4.2 Property mapping table</b></a>.</p>
    </dd>
  <dt class="label">[<a name="property-value-types" id="property-value-types"
  title="property value types">Definition</a>: Property value types]</dt>
    <dd><p>Property value types are the types of values used in a <a
      title="property" href="#property">property</a>. Property value types are
      defined in sec. <a href="#property-value-types-definitions"><b>3 Property
      value type definitions</b></a>. They are relying mostly on XML Schema
      data types [<cite><a href="#xmlschema2">XML Schema 2</a></cite>].</p>
    </dd>
</dl>
</div>

<div class="div1">
<h2><a name="property-value-types-definitions"
id="property-value-types-definitions"></a>3 Property value type definitions</h2>

<div class="div2">
<h3><a name="basic-property-value-types"
id="basic-property-value-types"></a>3.1 Basic property value types</h3>

<div class="div3">
<h4><a name="uri-value-type" id="uri-value-type"></a>3.1.1 URI</h4>

<p>URI "Uniform Resource Identifier" is defined in [<cite><a
href="#rfc3986">RFC 3986</a></cite>]. 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)" [<cite><a href="#rfc3987">RFC
3987</a></cite>], that is URIs which may contain non-escaped characters other
than ASCII. The data type is <a
href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#anyURI">anyURI</a> .
</p>
</div>

<div class="div3">
<h4><a name="date-value-type" id="date-value-type"></a>3.1.2 Date</h4>

<p>A <code>Date</code> value is represented using the XML Schema <a
href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#dateTime">dateTime</a>
data type.</p>
</div>
</div>

<div class="div2">
<h3><a name="complex-property-value-types"
id="complex-property-value-types"></a>3.2 Complex property value types</h3>

<table border="1" summary="Editorial note">
  <tbody>
    <tr>
      <td align="left" valign="top" width="50%"><b>Editorial note</b></td>
      <td align="right" valign="top" width="50%"> </td>
    </tr>
    <tr>
      <td colspan="2" align="left" valign="top">TBD</td>
    </tr>
  </tbody>
</table>
</div>
</div>

<div class="div1">
<h2><a name="property-definition" id="property-definition"></a>4 Property
definition</h2>

<p><em>This section is normative.</em></p>

<div class="div2">
<h3><a name="core-property-definitions" id="core-property-definitions"></a>4.1
Core property definitions</h3>

<div class="div3">
<h4><a name="property-approach" id="property-approach"></a>4.1.1 Description of
the approach followed for the property definitions</h4>

<p>The following information is available for each property:</p>
<ul>
  <li><p>rough description of purpose</p>
  </li>
  <li><p><a href="#property-value-types-definitions">property value
    types</a></p>
  </li>
  <li><p><a title="mapping" href="#mapping">mappings</a> to existing formats</p>
  </li>
</ul>
</div>

<div class="div3">
<h4><a name="core-property-lists" id="core-property-lists"></a>4.1.2 Core
properties</h4>

<table border="1" summary="Editorial note">
  <tbody>
    <tr>
      <td align="left" valign="top" width="50%"><b>Editorial note</b></td>
      <td align="right" valign="top" width="50%"> </td>
    </tr>
    <tr>
      <td colspan="2" align="left" valign="top">This core list of properties is
        neither closed, nor pretend to be exhaustive and that the group still
        looks at rationale for including properties to be considered in the
        final list of properties. In addition this table will be elaborated for
        the types and further information.</td>
    </tr>
  </tbody>
</table>
This list of core properties has been defined by making an initial set of
mapping propositions from the list of <a href="#formats-in-scope">vocabularies
in scope</a> to <cite><a href="#xmp">XMP</a></cite> as a pivot vocabulary. From
this original mapping table, it has been checked which of the properties were
supported by most of the vocabularies, and which ones were judged useful by the
members of the group present at the <a
href="http://www.w3.org/2008/WebVideo/Annotations/wiki/Meeting_Agenda_%28In_Progress%29">Face
to Face meeting in Barcelona</a>. A list of properties by a cross validation
between the member's opinion and the popularity of the properties across the
vocabularies has been selected in order to get some level of objectiveness.

<table border="1" width="100%">
  <tbody>
    <tr>
      <td align="center">Name</td>
      <td align="center">Type</td>
      <td align="center">Description</td>
    </tr>
    <tr>
      <td>ma:contributor</td>
      <td>tbd</td>
      <td>A pair identifying the contributor and the nature of the
        contribution. E.g. actor, cameraman, director, singer, author, artist
        (Note: subject see addition of contributor type)</td>
    </tr>
    <tr>
      <td>ma:creator</td>
      <td>tbd</td>
      <td>The authors of the resource (listed in order of precedence, if
        significant)</td>
    </tr>
    <tr>
      <td>ma:description</td>
      <td>tbd</td>
      <td>A textual description of the content of the resource</td>
    </tr>
    <tr>
      <td>ma:format</td>
      <td>tbd</td>
      <td>MIME type of the resource (wrapper, bucket media types)</td>
    </tr>
    <tr>
      <td>ma:identifier</td>
      <td>tbd</td>
      <td>A URI identifies a resource; which can be either a "Resource"
        (abstract concept) or a "Representation" (instance/file). See <a
        href="http://www.w3.org/TR/2009/WD-media-frags-reqs-20090430/#uc4">4.4
        Annotating Media Fragments</a></td>
    </tr>
    <tr>
      <td>ma:language</td>
      <td>tbd</td>
      <td>Specify a language used in the resource, Recommended best practice is
        to use a controlled vocabulary such as [<cite><a href="#rfc4646">RFC
        4646</a></cite>]</td>
    </tr>
    <tr>
      <td>ma:publisher</td>
      <td>tbd</td>
      <td>Examples of a Publisher include a person, an organization, or a
        service. Typically, the name of a Publisher should be used to indicate
        the resource</td>
    </tr>
    <tr>
      <td>ma:relation</td>
      <td>tbd</td>
      <td>A pair identifying the resource and the nature of the realtionship.
        E.g. transcript, original_work</td>
    </tr>
    <tr>
      <td>ma:keyword</td>
      <td>tbd</td>
      <td>An unordered array of descriptive phrases or keywords that specify
        the topic of the content of the resource</td>
    </tr>
    <tr>
      <td>ma:title</td>
      <td>tbd</td>
      <td>The title of the document, or the name given to the resource</td>
    </tr>
    <tr>
      <td>ma:genre</td>
      <td>tbd</td>
      <td>Genre of the resource</td>
    </tr>
    <tr>
      <td>ma:createDate</td>
      <td>tbd</td>
      <td>The date and time the resource was originally created. (for
        commercial purpose there might be an annotation of publication
      date)</td>
    </tr>
    <tr>
      <td>ma:rating</td>
      <td>tbd</td>
      <td>A pair identifying the rating person or organization and the rating
        (real value)</td>
    </tr>
    <tr>
      <td>ma:collection</td>
      <td>tbd</td>
      <td>A name of the collection from which the resources originates</td>
    </tr>
    <tr>
      <td>ma:duration</td>
      <td>tbd</td>
      <td>The actual duration of the resource</td>
    </tr>
    <tr>
      <td>ma:copyright</td>
      <td>tbd</td>
      <td>The copyright statement. Identification of the copyrights holder (DRM
        is out of scope for MAWG)</td>
    </tr>
    <tr>
      <td>ma:location</td>
      <td>tbd</td>
      <td>A location associated with the resource. Can be the depicted location
        or shot location</td>
    </tr>
    <tr>
      <td>ma:compression</td>
      <td>tbd</td>
      <td>Compression type used, e.g. H264. Note: possible to use extended mime
        type, see [<cite><a href="#rfc4281">RFC 4281</a></cite>]</td>
    </tr>
    <tr>
      <td>ma:frameSize</td>
      <td>tbd</td>
      <td>The frame size. For example: w:720, h: 480</td>
    </tr>
    <tr>
      <td>ma:targetAudience</td>
      <td>tbd</td>
      <td>A pair identifying the issuer of the classification (agency) and the
        classification. E.g. parental guide, targeted geographical region</td>
    </tr>
    <tr>
      <td>ma:locator</td>
      <td>tbd</td>
      <td>A URI at which the resource can be accessed (e.g. a URL, or a DVB
      URI)</td>
    </tr>
  </tbody>
</table>
</div>
</div>

<div class="div2">
<h3><a name="property-mapping-table" id="property-mapping-table"></a>4.2
Property mapping table</h3>

<div class="div3">
<h4><a name="rationale_mapping_table" id="rationale_mapping_table"></a>4.2.1
Rationale regarding the mapping table</h4>

<p>As a first step to build the Media ontology, a set of commonly supported
properties by the aforementioned vocabularies has been listed. This list,
henceforth referred to as "Core Media Properties list", is the basis for
vocabularies matching. Its namespace is "ma", for Media Annotation. We provide
a first set of mapping propositions between the vocabularies taken into account
and this list. These mappings have double nature: semantic and syntactic. </p>

<div class="div4">
<h5><a name="semantic-level-mappings" id="semantic-level-mappings"></a>4.2.1.1
Semantic Level Mappings</h5>

<p>The mappings are "one way" so far, i.e. the semantics is of a relationship
between one or more items from the vocabulary considered and one or more
property from our list. For example, in <cite><a href="#xmp">XMP</a></cite>,
both <em>xmpDM:copyright</em> and <em>dc:rights</em> (as part of the XMP
standard) are mapped to <em>ma:copyright</em>; in <cite><a
href="#exif">EXIF</a></cite>, the Copyright property is mapped to
<em>ma:copyright</em>. No semantic relationships can be inferred between the
properties in <cite><a href="#xmp">XMP</a></cite> and in <cite><a
href="#exif">EXIF</a></cite> from these mappings. This "Core Media Properties
list" can be considered as the minimal requirement for describing media
content. The mappings that have been taken into account have different
semantics: the properties of the different vocabularies can be </p>
<ul>
  <li><p>Exact matches: the semantics of the two properties are equivalent in
    most of the possible contexts. For example, <em>ma:title</em> matches
    exactly <em>vra:title</em>.</p>
  </li>
  <li><p>More specific: the property of the vocabulary taken into account has a
    semantic that takes into account only a subset of the possibilities
    expressed by the property defined in this Working Group. For example in
    <cite><a href="#dig35">DIG35</a></cite>, <em>ipr_names@description</em> and
    <em>ipr_person@description</em> are more specific than the property
    <em>ma:publisher</em> to which it is mapped.</p>
  </li>
  <li><p>More generic: the inverse of the above, the property of the vocabulary
    taken into account has a semantic that is broader than the property defined
    in this Working Group. For example, the <cite><a
    href="#dig35">DIG35</a></cite><em>location</em> is more general than the
    <em>ma:location</em>.</p>
  </li>
  <li><p>Related: the two properties are related in a way that is relevant for
    some use cases, but this relation has no defined semantics. For example, in
    <cite><a href="#mediarss">Media RSS</a></cite>, <em>media:credit</em> is
    related to <em>ma:creator</em>.</p>
  </li>
</ul>
This list of relations between vocabularies (or informal mappings) and the
"Core Media Properties list" is published as a table; its purpose is to get
feedback from the communities that are currently using the different
vocabularies: the people or companies actually using the different vocabularies
could proof-read our interpretation of the vocabularies and comment on the
proposed mappings. </div>

<div class="div4">
<h5><a name="syntactic-level-mappings"
id="syntactic-level-mappings"></a>4.2.1.2 Syntactic Level Mappings</h5>

<p>Syntactic level mappings declare the correspondence between two semantically
equivalent properties but with a different syntactic expression. It's most
evident case is the date formatting, but some others may appear. </p>

<table border="1" summary="Editorial note">
  <tbody>
    <tr>
      <td align="left" valign="top" width="50%"><b>Editorial note</b></td>
      <td align="right" valign="top" width="50%"> </td>
    </tr>
    <tr>
      <td colspan="2" align="left" valign="top">Currently the mapping table for
        most of the formats does not contain information about syntactic
        mapping, but this information will be added in the following
      version.</td>
    </tr>
  </tbody>
</table>
</div>

<div class="div4">
<h5><a name="mapping-expression" id="mapping-expression"></a>4.2.1.3 Mapping
expression</h5>

<p>The mapping expression corresponds to the concrete implementation or
representation of the mappings defined in the previous paragraph, both at a
semantic level and at syntactic one. </p>

<p>In the context of the W3C Semantic Web activity, <a
href="http://www.w3.org/TR/2009/CR-skos-reference-20090317/">SKOS</a> (acronym
for Simple Knowledge Organization System) is currently a Candidate
Recommendation that defines a vocabulary for representing Knowledge
Organization Systems (i.e. vocabularies) and relationships amongst them. In <a
href="http://www.w3.org/TR/2009/CR-skos-reference-20090317/">SKOS</a> the
mapping properties that we take into account in the mapping table are expressed
as: <em>skos:exactMatch</em>, <em>skos:narrowMatch</em>,
<em>skos:broaderMatch</em> and <em>skos:relatedMatch</em>. Some more fine
grained definition of the properties has still to be done: we need to agree on
the properties' names, define their formal properties (if they are symmetric,
etc) and the type of value expected, to enhance more efficient concrete
mappings, in the API. </p>
</div>
</div>

<div class="div3">
<h4><a name="mapping-table" id="mapping-table"></a>4.2.2 The mapping table</h4>

<table border="1" summary="Editorial note">
  <tbody>
    <tr>
      <td align="left" valign="top" width="50%"><b>Editorial note</b></td>
      <td align="right" valign="top" width="50%"> </td>
    </tr>
    <tr>
      <td colspan="2" align="left" valign="top">Here to put the mapping table
        in some form</td>
    </tr>
  </tbody>
</table>

<p>The following mappings are established between various multimedia metadata
formats with core vocabulary of MA WG as pivot. This list of formats is not
closed, nor pretend to be exhaustive and that the group still looks at
rationale for including and excluding formats to be considered in the final
mapping table;</p>
<ul>
  <li><p><a href="mapping_table.htm#table0">Summary</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table1">XMP</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table2">ID3</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table3">iTunes</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table4">QT</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table5">SearchMonkey</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table6">MediaRDF</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table7">LOM</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table8">METS</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table9">EXIF</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table10">CableLabs 1.1</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table11">CableLabs 2.0</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table12">DIG35</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table13">MIX</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table14">FRBR</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table15">MediaRSS</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table16">TXFeed</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table17">YouTube</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table18">VRA</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table19">IPTC</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table20">TVA</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table21">EBUCore</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table22">EBUP</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table23">MPEG7</a></p>
  </li>
  <li><p><a href="mapping_table.htm#table24">SMTPD</a></p>
  </li>
</ul>
</div>
</div>
</div>
</div>

<div class="back">

<div class="div1">
<h2><a name="references" id="references"></a>A References</h2>
<dl>
  <dt class="label"><a name="cablelabs1"></a>[Cablelabs 1.1] </dt>
    <dd><a
      href="http://www.cablelabs.com/specifications/MD-SP-VOD-CONTENT1.1-I05-060831.pdf"><cite>CableLabs
      VOD Content Specification Version 1.1</cite></a>. Available at
      http://www.cablelabs.com/specifications/MD-SP-VOD-CONTENT1.1-I05-060831.pdf
      . </dd>
  <dt class="label"><a name="cablelabs2"></a>[Cablelabs 2.0] </dt>
    <dd><a
      href="http://www.cablelabs.com/specifications/MD-SP-VOD-CONTENT2.0-I02-070105.pdf"><cite>CableLabs
      VOD Content Specification Version 2.0</cite></a>. Available at
      http://www.cablelabs.com/specifications/MD-SP-VOD-CONTENT2.0-I02-070105.pdf
      . </dd>
  <dt class="label"><a name="dig35"></a>[DIG35] </dt>
    <dd><a
      href="http://www.bgbm.org/TDWG/acc/Documents/DIG35-v1.1WD-010416.pdf"><cite>DIG35
      Specification - Metadata for Digital Image</cite></a>. April 2001.
      Available at
      http://www.bgbm.org/TDWG/acc/Documents/DIG35-v1.1WD-010416.pdf . </dd>
  <dt class="label"><a name="dms"></a>[DMS-1] </dt>
    <dd><a href="http://www.smpte.org/standards"><cite>DMS-1</cite></a> (SMPTE
      380M-2004). April 2001. Available at http://www.smpte.org/standards .
    </dd>
  <dt class="label"><a name="dc"></a>[Dublin Core] </dt>
    <dd><a
      href="http://dublincore.org/documents/2008/01/14/dcmi-terms/"><cite>DCMI
      Metadata Terms</cite></a>. January 2008. Available at
      http://dublincore.org/documents/2008/01/14/dcmi-terms/ . The <a
      href="http://dublincore.org/documents/dcmi-terms/">latest version of DCMI
      Metadata Terms</a> is available at
      http://dublincore.org/documents/dcmi-terms/ . </dd>
  <dt class="label"><a name="ebucore"></a>[EBUCore] </dt>
    <dd><a href="http://tech.ebu.ch/docs/tech/tech3293-2008.pdf"><cite>EBUCore
      v.1.0</cite></a>. December 2008. Available at
      http://tech.ebu.ch/docs/tech/tech3293-2008.pdf . </dd>
  <dt class="label"><a name="ebup"></a>[EBU P-META] </dt>
    <dd><a href="http://tech.ebu.ch/docs/tech/tech3295v2.pdf"><cite>EBU P-META
      2.0 Metadata Library</cite></a>. July 2007. Available at
      http://tech.ebu.ch/docs/tech/tech3295v2.pdf . </dd>
  <dt class="label"><a name="exif"></a>[EXIF] </dt>
    <dd><a href="http://www.exif.org/Exif2-2.PDF"><cite>EXIF 2.2</cite></a>.
      Specification by <a href="http://www.jeita.or.jp/">JEITA</a>, April 2002.
      Available at http://www.exif.org/Exif2-2.PDF . </dd>
  <dt class="label"><a name="frbr"></a>[FRBR] </dt>
    <dd><cite>FRBR</cite> TBD . </dd>
  <dt class="label"><a name="html5"></a>[HTML 5] </dt>
    <dd>Hickson, I., and D. Hyatt. <a
      href="http://www.w3.org/TR/2008/WD-html5-20080610/"><cite>HTML 5. A
      vocabulary and associated APIs for HTML and XHTML</cite></a>. W3C Working
      Draft, June 2008. Available at
      http://www.w3.org/TR/2008/WD-html5-20080610/ . The <a
      href="http://www.w3.org/TR/html5/">latest version of HTML 5</a> is
      available at http://www.w3.org/TR/html5/ . </dd>
  <dt class="label"><a name="lom"></a>[LOM] </dt>
    <dd><a
      href="http://ltsc.ieee.org/wg12/files/LOM_1484_12_1_v1_Final_Draft.pdf"><cite>Draft
      Standard for Learning Object Metadata</cite></a>. July 2002. Available at
      http://ltsc.ieee.org/wg12/files/LOM_1484_12_1_v1_Final_Draft.pdf . </dd>
  <dt class="label"><a name="mix"></a>[MIX] </dt>
    <dd><a href="http://www.loc.gov/standards/mix/"><cite>MIX 1.0</cite></a>.
      Available at http://www.loc.gov/standards/mix/ . </dd>
  <dt class="label"><a name="mwg_guidance_image"></a>[MWG Guidelines Image]
  </dt>
    <dd><a href=""><cite>Guidelines for handling image metadata, version
      1.0.</cite></a>. Metadata Working Group, September 2008. Available at
      http://www.metadataworkinggroup.com/pdf/mwg_guidance.pdf . </dd>
  <dt class="label"><a name="id3"></a>[ID3] </dt>
    <dd><a href="http://www.id3.org/Developer_Information"><cite>ID3 tag
      version 2.4.0</cite></a>. February 1999. Available at
      http://www.id3.org/Developer_Information . </dd>
  <dt class="label"><a name="iptc"></a>[IPTC] </dt>
    <dd><a
      href="http://www.iptc.org/std/photometadata/2008/specification/IPTC-PhotoMetadata-2008.pdf"><cite>IPTC
      Standard Photo Metadata 2008</cite></a>. 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
    </dd>
  <dt class="label"><a name="newsml"></a>[IPTC NewsML] </dt>
    <dd><a href="http://www.iptc.org/cms/site/"><cite>IPTC
      NewsML-G2</cite></a>. Available at http://www.iptc.org/cms/site/ . </dd>
  <dt class="label"><a name="itunes"></a>[iTunes] </dt>
    <dd><a href="http://connect.apple.com/"><cite>iTunes Metadata
      Specification</cite></a>. Available at http://connect.apple.com/ . </dd>
  <dt class="label"><a name="mediamonkey"></a>[MediaMonkey] </dt>
    <dd><a
      href="http://developer.yahoo.com/searchmonkey/smguide/searchmonkey-media-details.html"><cite>MediaMonkey
      Media</cite></a>. Available at
      http://developer.yahoo.com/searchmonkey/smguide/searchmonkey-media-details.html
      . </dd>
  <dt class="label"><a name="mets"></a>[METS] </dt>
    <dd><a href="http://www.loc.gov/standards/mets/"><cite>Metadata Encoding
      &amp; Transmission Standard 1.7</cite></a>. Available at
      http://www.loc.gov/standards/mets/ . </dd>
  <dt class="label"><a name="mediardf"></a>[Media RDF] </dt>
    <dd><a href="http://digitalbazaar.com/media/video"><cite>Media
      RDF</cite></a>. Available at http://digitalbazaar.com/media/video . </dd>
  <dt class="label"><a name="mediarss"></a>[Media RSS] </dt>
    <dd><a href="http://video.search.yahoo.com/mrss"><cite>Yahoo! Media RSS
      Module - RSS 2.0 Module</cite></a>. March 2008. Available at
      http://video.search.yahoo.com/mrss . </dd>
  <dt class="label"><a name="mpeg7"></a>[MPEG-7] </dt>
    <dd><a
      href="http://www.chiariglione.org/mpeg/working_documents/mpeg-07/schema_def/cd.zip"><cite>Information
      technology — Multimedia content description interface — Part 10:
      Schema definition</cite></a>. Available at
      http://www.chiariglione.org/mpeg/working_documents/mpeg-07/schema_def/cd.zip
      . </dd>
  <dt class="label"><a name="mpeg21"></a>[MPEG-21] </dt>
    <dd><cite>MPGE 21</cite> tbd. </dd>
  <dt class="label"><a name="quictime"></a>[QuickTime] </dt>
    <dd><a
      href="http://developer.apple.com/documentation/QuickTime/QTFF/QTFFChap2/qtff2.html#//apple_ref/doc/uid/TP40000939-CH204-BBCCFFGD"><cite>Movie
      Atoms of QuickTime File Format Specification</cite></a>. September 2007.
      Available at
      http://developer.apple.com/documentation/QuickTime/QTFF/QTFFChap2/qtff2.html#//apple_ref/doc/uid/TP40000939-CH204-BBCCFFGD
      . </dd>
  <dt class="label"><a name="rfc2119"></a>[RFC 2119] </dt>
    <dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>RFC 2119: Key words
      for use in RFCs to Indicate Requirement Levels</cite></a>. Internet
      Engineering Task Force, 1997. </dd>
  <dt class="label"><a name="rfc3986"></a>[RFC 3986] </dt>
    <dd>Berners-Lee, T., R. Fielding, L. Masinter. <a
      href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource
      Identifier (URI): Generic Syntax</cite></a>. RFC 3986, January 2005.
      Available at http://www.ietf.org/rfc/rfc3986.txt </dd>
  <dt class="label"><a name="rfc3987"></a>[RFC 3987] </dt>
    <dd>Dürst, M. and M. Suignard. <a
      href="http://www.ietf.org/rfc/rfc3987.txt"><cite>Internationalized
      Resource Identifiers (IRIs)</cite></a>. RFC 3987, January 2005. Available
      at http://www.ietf.org/rfc/rfc3987.txt. </dd>
  <dt class="label"><a name="rfc4281"></a>[RFC 4281] </dt>
    <dd>Gellens, R., Singer, D., and P. Frojdh. <a
      href="http://www.ietf.org/rfc/rfc4281.txt"><cite>The Codecs Parameter for
      "Bucket" Media Types</cite></a>. RFC 4281, November 2005. Available at
      http://www.ietf.org/rfc/rfc4281.txt. </dd>
  <dt class="label"><a name="rfc4646"></a>[RFC 4646] </dt>
    <dd>Phillips, A., Ed. and M. Davis, Ed. <a
      href="http://www.rfc-editor.org/rfc/rfc4646.txt"><cite>Tags for
      Identifying Languages</cite></a>. RFC 4646, September 2006. Available at
      http://www.rfc-editor.org/rfc/rfc4646.txt. </dd>
  <dt class="label"><a name="smpte"></a>[SMPTE] </dt>
    <dd><a
      href="http://www.smpte-ra.org/mdd/RP210v11-pub-20080415.2048.xls"><cite>SMPTE
      Metadata</cite></a>. Available at
      http://www.smpte-ra.org/mdd/RP210v11-pub-20080415.2048.xls . </dd>
  <dt class="label"><a name="txfeed"></a>[TXFeed] </dt>
    <dd><a
      href="http://clearerchannel.org/docs/tx_metadata_standard_0_9.pdf"><cite>TXFeed
      standard 0.9</cite></a>. December 2007. Available at
      http://clearerchannel.org/docs/tx_metadata_standard_0_9.pdf . </dd>
  <dt class="label"><a name="tvanytime"></a>[TV-Anytime] </dt>
    <dd><cite>ETSI 102 822-3-1 V1.4.1</cite>. November 2007. Broadcast and
      On-line Services: Search, select, and rightful use of content on personal
      storage systems("TV-Anytime"). Part 3: Metadata, Sub-part 1: Phase 1 -
      Metadata schemas . </dd>
  <dt class="label"><a name="vra"></a>[VRA] </dt>
    <dd><a href="http://www.vraweb.org/projects/vracore4/index.html"><cite>VRA
      Core 4.0</cite></a>. Available at
      http://www.vraweb.org/projects/vracore4/index.html . </dd>
  <dt class="label"><a name="xmlschema2"></a>[XML Schema 2] </dt>
    <dd>Biron, P. V. and A. Malhotra. <a
      href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>XML
      Schema Part 2: Datatypes Second Edition</cite></a>. W3C Recommendation,
      October 2004. Available at
      http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/ . The <a
      href="http://www.w3.org/TR/xmlschema-2/">latest version of XML Schema
      Part 2</a> is available at http://www.w3.org/TR/xmlschema-2/ . </dd>
  <dt class="label"><a name="xmp"></a>[XMP] </dt>
    <dd><a
      href="http://www.adobe.com/devnet/xmp/pdfs/XMPSpecificationPart2.pdf"><cite>XMP
      Specification Part 2 - Standard Schemas</cite></a>. Adobe, 2008.
      Available at
      http://www.adobe.com/devnet/xmp/pdfs/XMPSpecificationPart2.pdf . </dd>
  <dt class="label"><a name="youtube-data-api"></a>[YouTube Data API Protocol]
  </dt>
    <dd><a
      href="http://code.google.com/intl/en/apis/youtube/2.0/reference.html"><cite>YouTube
      Data API Protocol</cite></a>. April 2008. Available at
      http://code.google.com/intl/en/apis/youtube/2.0/reference.html .</dd>
</dl>
</div>

<div class="div1">
<h2><a name="idinform-div1114292296" id="idinform-div1114292296"></a>B
References (Non-Normative)</h2>

<p>tbd</p>
</div>

<div class="div1">
<h2><a name="acknowledgments" id="acknowledgments"></a>C Acknowledgements
(Non-Normative)</h2>

<p>This document is the work of the <a
href="http://www.w3.org/2008/WebVideo/Annotations/">W3C Media Annotations
Working Group</a>.</p>

<p>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), 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 (Potsdam University of
Applied Sciences), 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). </p>

<p>The people who have contributed to <a
href="http://lists.w3.org/Archives/Public/public-media-annotation/">discussions
on public-media-annotation@w3.org</a> are also gratefully acknowledged. </p>
</div>
</div>
</body>
</html>