You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
427 lines
18 KiB
427 lines
18 KiB
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.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>Media Annotations Working Group</title>
|
|
<link rel="stylesheet" href="http://www.w3.org/2005/10/w3cdoc.css"
|
|
type="text/css" media="screen" />
|
|
<link rel="stylesheet" type="text/css"
|
|
href="http://www.w3.org/Guide/pubrules-style.css" />
|
|
<link rel="stylesheet" type="text/css"
|
|
href="http://www.w3.org/2006/02/charter-style.css" />
|
|
</head>
|
|
|
|
<body>
|
|
|
|
<div id="template">
|
|
<ul id="navbar" style="font-size: small">
|
|
<li><a href="#scope">Scope</a></li>
|
|
<li><a href="#deliverables">Deliverables</a></li>
|
|
<li><a href="#coordination">Dependencies and Liaisons</a></li>
|
|
<li><a href="#participation">Participation</a></li>
|
|
<li><a href="#communication">Communication</a></li>
|
|
<li><a href="#decisions">Decision Policy</a></li>
|
|
<li><a href="#patentpolicy">Patent Policy</a></li>
|
|
<li><a href="#about">About this Charter</a></li>
|
|
</ul>
|
|
|
|
<p><a href="http://www.w3.org/"><img alt="W3C" height="48"
|
|
src="http://www.w3.org/Icons/w3c_home" width="72" /></a> <a class="domainlogo"
|
|
href="http://www.w3.org/Interaction/"><img
|
|
src="http://www.w3.org/Icons/interaction" alt="Interaction Domain" /></a></p>
|
|
|
|
<h1 id="title">Media Annotations Working Group Charter</h1>
|
|
|
|
<p class="mission">The <strong>mission</strong> of the <a
|
|
href="/2008/WebVideo/Annotations/">Media Annotations Working Group</a>, part of
|
|
the Video in the Web Activity, is to provide an ontology designed to facilitate
|
|
cross-community data integration of information related to media objects in the
|
|
Web, such as video, audio and images.</p>
|
|
|
|
<div class="noprint">
|
|
<p class="join"><a href="http://www.w3.org/2004/01/pp-impl/42786/join">Join the
|
|
Media Annotations Working Group</a>.</p>
|
|
</div>
|
|
|
|
<table class="summary-table">
|
|
<tbody>
|
|
<tr id="Duration">
|
|
<th rowspan="1" colspan="1">End date</th>
|
|
<td rowspan="1" colspan="1">30 June 2011</td>
|
|
</tr>
|
|
<tr>
|
|
<th rowspan="1" colspan="1">Confidentiality</th>
|
|
<td rowspan="1" colspan="1">Proceedings are <a
|
|
href="http://www.w3.org/2005/10/Process-20051014/comm.html#confidentiality-levels">public</a></td>
|
|
</tr>
|
|
<tr>
|
|
<th rowspan="1" colspan="1">Initial Chair</th>
|
|
<td rowspan="1" colspan="1">Soohong Daniel Park, Joakim Söderberg</td>
|
|
</tr>
|
|
<tr>
|
|
<th rowspan="1" colspan="1">Initial Team Contact <br />
|
|
(FTE %: 20)</th>
|
|
<td rowspan="1" colspan="1">Thierry Michel</td>
|
|
</tr>
|
|
<tr>
|
|
<th rowspan="1" colspan="1">Usual Meeting Schedule</th>
|
|
<td rowspan="1" colspan="1">Teleconferences: Weekly <br />
|
|
Face-to-face: 3-4 per year</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
|
|
<div class="scope">
|
|
<h2 id="scope">Scope</h2>
|
|
|
|
<p>This Group is chartered to provide a simple ontology to support
|
|
cross-community data integration of information related to media objects on the
|
|
Web, as well as an API to access the information. This ontology would help
|
|
circumventing the current profileration of video metadata formats by providing
|
|
full or partial translation and mapping between the existing formats.</p>
|
|
|
|
<p>Anticipating the increase in online video and audio in the upcoming years,
|
|
it will become progressively more difficult for viewers to find the content
|
|
using current search tools. Unlike hypertext documents, it is more complex and
|
|
sometimes impossible to deduce meta information about a medium, such as its
|
|
title, author, or creation date. An ontology would provide a common set of
|
|
terms to define the basic metadata needed for media objects. There has been a
|
|
proliferation of media metadata formats. For example, an image could
|
|
potentially contain EXIF, IPTC and XMP information. There are several metadata
|
|
solutions for media related content, including MPEG-7, IPTC, iTunes XML, Yahoo!
|
|
MediaRSS, Video sitemaps, CableLabs VOD Metadata Content, TV-ANytime (ETSI TS
|
|
102 822 series), EBU Core Metadata Set, and XMP (see also <a
|
|
href="http://www.w3.org/2005/Incubator/mmsem/XGR-vocabularies/">Multimedia
|
|
Vocabularies on the Semantic Web</a> and the <a
|
|
href="http://www.w3.org/2007/08/video/report.html#Metadata">report from the
|
|
Video on the Web workshop</a>). The goal of this Group is to develop a
|
|
<strong>simple lingua franca</strong> common ontology between the existing
|
|
standards, and define a roadmap for future extension of the ontology. It is not
|
|
expected that the Group will focus on "low level" metadata in its first phase.
|
|
The intent is to help publishers to harmonize metadata information encoded in
|
|
different languages but also to help developers with the lack of syntactic and
|
|
semantic interoperability. Ultimately, users of the ontology should also be
|
|
able to take advantage of Semantic Web technologies, such as the <a
|
|
href="http://www.w3.org/TR/rdf-sparql-query/">SPARQL Query Language for
|
|
RDF</a>. The Group should look at the documents produced by the <a
|
|
href="http://www.w3.org/2005/Incubator/mmsem/">W3C Multimedia Semantics
|
|
Incubator Group</a> as a starting point and survey the existing metadata
|
|
formats to focus on a specific set. The Group will start by focusing on
|
|
discrete/finite simple video objects and will then expand at a later stage into
|
|
streamed video, image, and audio.</p>
|
|
|
|
<p>The Group should explore a minimal approach for specifying proper copyright
|
|
licensing, which may require separate terms for specifying the holder of the
|
|
copyright and the licensing terms.</p>
|
|
|
|
<p>The Group will also develop a specification for an application programming
|
|
interface (API) to access metadata information. At the minimum, the Group will
|
|
provide a simple client-side readonly ECMAScript API. The Group should also
|
|
consider making the underlying media metadata available to a browser ECMAScript
|
|
API in some <strong>simple</strong> RDF form, especially as a number of the
|
|
underlying data formats permit full RDF. Such access should be able to operate
|
|
on metadata elements defined in future versions of the simple common ontology;
|
|
that is, it should not be designed such that extensions are required when the
|
|
common ontology is extended.</p>
|
|
|
|
<p>The Group may hold Workshops, Interoperability Meetings, and other events as
|
|
required to fulfill its mission.</p>
|
|
|
|
<h3>Success Criteria</h3>
|
|
<ul>
|
|
<li>Abilitity to convert core metadata information from one metadata standard
|
|
to an other</li>
|
|
<li>Development of a set of requirements and competency questions to
|
|
determine the scope of the ontology and to test the fulfillment of the
|
|
requirements and coverage of the ontology.</li>
|
|
<li>Production of stable documents addressing the work items listed in the <a
|
|
href="#deliverables">Deliverables</a> section.</li>
|
|
<li>Availability of at least two implementations mapping the ontology
|
|
developed by the Group with two other existing metadata standards, as
|
|
demonstrated by an implementation report (summarizing implementation status
|
|
against the relevant test suite) for each testable class of product,
|
|
including user agents</li>
|
|
<li>Availability of at least two implementations for the API
|
|
specification(s).</li>
|
|
<li>Demonstrate that the "most commonly used" metadata items in use by the
|
|
industry are mapped by the ontology.</li>
|
|
</ul>
|
|
|
|
<div>
|
|
<h3>Out of Scope</h3>
|
|
|
|
<p>Full coverage of all metadata elements in EXIF, IPTC, XMP, MPEG-7, and
|
|
similar broad vocabularies, is out of scope, as well as signal related
|
|
descriptors.</p>
|
|
</div>
|
|
</div>
|
|
|
|
<div>
|
|
<h2 id="deliverables">Deliverables</h2>
|
|
|
|
<div id="rec-deliverables">
|
|
<h3>W3C Technical Reports</h3>
|
|
<ul>
|
|
<li>A W3C Working Group Note for use cases and requirements for the Media
|
|
Ontology</li>
|
|
<li>A W3C Recommendation describing a <em>simple</em> ontology for
|
|
representating a set of concepts often associated with media objects.</li>
|
|
<li>A W3C Recommendation for an application programming interface (API) to
|
|
access metadata information.</li>
|
|
<li>A W3C Working Group Note for mapping the ontology to existing standards
|
|
and solutions.</li>
|
|
</ul>
|
|
</div>
|
|
|
|
<div id="ig-other-deliverables">
|
|
<h3>Other Deliverables</h3>
|
|
<ul>
|
|
<li>Collection of a corpus of metadata to demonstrate the mapping and
|
|
translation.</li>
|
|
<li>Implementation and interoperability reports.</li>
|
|
<li>Tutorial or primer resources (if suitable and if resources are
|
|
available).</li>
|
|
<li>Propose eventually a new charter for follow on work.</li>
|
|
</ul>
|
|
</div>
|
|
|
|
<h3>Milestones</h3>
|
|
|
|
<table class="roadmap" width="80%">
|
|
<caption>Milestones</caption>
|
|
<tbody>
|
|
<tr>
|
|
<th rowspan="1" colspan="1">Specification</th>
|
|
<th rowspan="1" colspan="1"><acronym
|
|
title="First Working Draft">FPWD</acronym></th>
|
|
<th rowspan="1" colspan="1"><acronym
|
|
title="Last Call Working Draft">LC</acronym></th>
|
|
<th rowspan="1" colspan="1"><acronym
|
|
title="Candidate Recommendation">CR</acronym></th>
|
|
<th rowspan="1" colspan="1"><acronym
|
|
title="Proposed Recommendation">PR</acronym></th>
|
|
<th rowspan="1" colspan="1"><acronym
|
|
title="Recommendation">Rec</acronym></th>
|
|
</tr>
|
|
<tr>
|
|
<th rowspan="1" colspan="1">Ontology for Media Object Use Cases and
|
|
Requirements</th>
|
|
<td class="WD1" rowspan="1" colspan="1">October 2008</td>
|
|
<td class="LC" rowspan="1" colspan="1">March 2009</td>
|
|
<td class="CR" rowspan="1" colspan="1"></td>
|
|
<td class="PR" rowspan="1" colspan="1"></td>
|
|
<td class="REC" rowspan="1" colspan="1"></td>
|
|
</tr>
|
|
<tr>
|
|
<th rowspan="1" colspan="1">Ontology for Media Object 1.0</th>
|
|
<td class="WD1" rowspan="1" colspan="1">February 2009</td>
|
|
<td class="LC" rowspan="1" colspan="1">June 2009</td>
|
|
<td class="CR" rowspan="1" colspan="1">September 2009</td>
|
|
<td class="PR" rowspan="1" colspan="1">December 2009</td>
|
|
<td class="REC" rowspan="1" colspan="1">January 2010</td>
|
|
</tr>
|
|
<tr>
|
|
<th rowspan="1" colspan="1">API for Media Object 1.0</th>
|
|
<td class="WD1" rowspan="1" colspan="1">February 2009</td>
|
|
<td class="LC" rowspan="1" colspan="1">June 2009</td>
|
|
<td class="CR" rowspan="1" colspan="1">September 2009</td>
|
|
<td class="PR" rowspan="1" colspan="1">December 2009</td>
|
|
<td class="REC" rowspan="1" colspan="1">January 2010</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
<!--
|
|
<div class="should">
|
|
<h3 id="timeline">Timeline View Summary</h3>
|
|
<p class="toadd">TODO</p>
|
|
<ul class="example">
|
|
<li>September 2008: First teleconference</li>
|
|
<li>October 2008: First face-to-face meeting</li>
|
|
<li>October 2008: Requirements and Use Cases for Ontology</li>
|
|
<li>October 2008: FPWD for FooML</li>
|
|
<li>: Requirements and Use Cases for BarML</li>
|
|
<li>Month YYYY: FPWD FooML Primer</li>
|
|
</ul>
|
|
</div>
|
|
-->
|
|
</div>
|
|
|
|
<div class="dependencies">
|
|
<p>Note: the Working Group homepage contains an <a
|
|
href="http://www.w3.org/2008/WebVideo/Annotations/#Schedule">updated
|
|
schedule</a>.</p>
|
|
|
|
<h2 id="coordination">Dependencies and Liaisons</h2>
|
|
|
|
<p>As part of the Video in the Web Activity, the Media Annotation Working Group
|
|
will be represented in the Hypertext Coordination Group. </p>
|
|
|
|
<h3>Dependencies with W3C Groups</h3>
|
|
<dl>
|
|
<dt>Semantic Web Deployment Working Group</dt>
|
|
<dd>The mission of this Working Group is to provide guidance in the form of
|
|
W3C Technical Reports on issues of practical RDF development and
|
|
deployment practices in the areas of publishing vocabularies, OWL usage,
|
|
and integrating RDF with HTML documents.</dd>
|
|
<dt>Semantic Web Coordination Group</dt>
|
|
<dd>The Semantic Web Coordination Group serves as an advisory forum for the
|
|
W3C Semantic Web Activity. Assuming the Semantic Web Deployment and
|
|
POWDER Working Groups finish in December 2008, the Coordination Group
|
|
will be use a fallback to ensure proper dependencies with the Semantic
|
|
Web Activity. </dd>
|
|
<dt>Scalable Vector Graphics Working Group (SVG)</dt>
|
|
<dd>SVG is a language for describing two-dimensional graphics and graphical
|
|
applications in XML. </dd>
|
|
<dt>Web Applications (WebApps) Working Group</dt>
|
|
<dd>The mission of this Group is to develop standard APIs for client-side
|
|
Web Application development. </dd>
|
|
<dt>HyperText Markup Language (HTML) Working Group</dt>
|
|
<dd>The mission of the HTML Working Group is to continue the evolution of
|
|
HTML (including classic HTML and XML syntaxes). </dd>
|
|
</dl>
|
|
|
|
<h3>Liaisons with W3C Groups</h3>
|
|
<dl>
|
|
<dt>Protocol for Web Description Resources (POWDER) Working Group</dt>
|
|
<dd>The POWDER Working Group is specifying a protocol for publishing
|
|
descriptions of (e.g. metadata about) Web resources using RDF, OWL, and
|
|
HTTP.</dd>
|
|
<dt>Protocols and Formats Working Group</dt>
|
|
<dd>The PFWG looks at the formal Web technologies (protocols, formats,
|
|
etc.) from an accessibility perspective. </dd>
|
|
</dl>
|
|
|
|
<div>
|
|
<h3>External Groups</h3>
|
|
<dl>
|
|
<dt>ISO/IEC JTC-1/SC-29 WG 11 Moving Picture Experts Group (MPEG)</dt>
|
|
<dd>This group is developing standards for coded representation of digital
|
|
audio and video, including MPEG-7 and MPEG-21. </dd>
|
|
<dd></dd>
|
|
<dt>The Internet Captioning Forum (ICF)</dt>
|
|
<dd>This organization addresses the technical challenges presented by
|
|
online video repurposed from broadcast or other previously captioned
|
|
sources, as well as video created specifically for the Web.</dd>
|
|
<dt>International Press Telecommunications Council (IPTC)</dt>
|
|
<dd>The International Press Telecommunications Council (IPTC), developing
|
|
technical standards for improved news exchange that are used by virtually
|
|
every major news organization in the world, such as IPTC Metadata for XMP
|
|
(IPTC4XMP).</dd>
|
|
<dt>European Broadcasting Union Metadata Advisory Group (P/MAG)</dt>
|
|
<dd>The European Broadcasting Union has been developing metadata
|
|
specifications related to radio, camcorders, news. </dd>
|
|
<dt>International Telecommunication Union (ITU) IPTV Focus Group</dt>
|
|
<dd>The mission of FG IPTV is to coordinate and promote the development of
|
|
global IPTV standards taking into account the existing work of the ITU
|
|
study groups as well as Standards Developing Organizations, Fora and
|
|
Consortia. </dd>
|
|
<dt>IPTV Forum Japan</dt>
|
|
<dd>The mission of the IPTV Forum Japan is to improve the deployement of
|
|
IPTV services. </dd>
|
|
<dt>International Imaging Industry Association (I3A)</dt>
|
|
<dd>I3A is a forum for development and advancement of open standards within
|
|
the imaging industry.</dd>
|
|
<dt>Picture Licensing Universal System (PLUS)</dt>
|
|
<dd>The PLUS Coalition is an international non-profit initiative on a
|
|
mission to simplify and facilitate the communication and management of
|
|
image rights.</dd>
|
|
<dt>Universal Photographic Digital Imaging Guidelines (UPDIG)</dt>
|
|
<dd>UPDIG is a a working group of digital imaging professionals and allied
|
|
trade groups and manufacturers, dedicated to promoting worldwide
|
|
standards in the commercial application of digital imaging. </dd>
|
|
</dl>
|
|
</div>
|
|
</div>
|
|
|
|
<div class="participation">
|
|
<h2 id="participation">Participation</h2>
|
|
|
|
<p>To be successful, the Media Annotations Working Group is expected to have 10
|
|
or more active participants for its duration. Effective participation to Media
|
|
Annotations Working Group is expected to consume one work day per week for each
|
|
participant; two days per week for editors. The Media Annotations Working Group
|
|
will allocate also the necessary resources for building Test Suites for each
|
|
specification.</p>
|
|
|
|
<p>Participants are reminded of the <a
|
|
href="http://www.w3.org/2005/10/Process-20051014/groups.html#good-standing">Good
|
|
Standing requirements</a> of the W3C Process.</p>
|
|
</div>
|
|
|
|
<div class="communication">
|
|
<h2 id="communication">Communication</h2>
|
|
|
|
<p>This group primarily conducts its work on the public mailing list
|
|
public-media-annotation@w3.org.</p>
|
|
|
|
<p>Information about the group (deliverables, participants, face-to-face
|
|
meetings, teleconferences, etc.) is available from the Media Annotations
|
|
Working Group home page.</p>
|
|
</div>
|
|
|
|
<div class="decisions">
|
|
<h2 id="decisions">Decision Policy</h2>
|
|
|
|
<p>As explained in the Process Document (<a
|
|
href="http://www.w3.org/Consortium/Process/policies#Consensus">section
|
|
3.3</a>), this group will seek to make decisions when there is consensus. When
|
|
the Chair puts a question and observes dissent, after due consideration of
|
|
different opinions, the Chair should record a decision (possibly after a formal
|
|
vote) and any objections, and move on.</p>
|
|
|
|
<p>This charter is written in accordance with <a
|
|
href="http://www.w3.org/Consortium/Process/policies#Votes">Section 3.4,
|
|
Votes</a> of the W3C Process Document and includes no voting procedures beyond
|
|
what the Process Document requires.</p>
|
|
</div>
|
|
|
|
<div class="patent">
|
|
<h2 id="patentpolicy">Patent Policy</h2>
|
|
|
|
<p>This Working Group operates under the <a
|
|
href="http://www.w3.org/Consortium/Patent-Policy-20040205/">W3C Patent
|
|
Policy</a> (5 February 2004 Version). To promote the widest adoption of Web
|
|
standards, W3C seeks to issue Recommendations that can be implemented,
|
|
according to this policy, on a Royalty-Free basis.</p>
|
|
|
|
<p>For more information about disclosure obligations for this group, please see
|
|
the <a href="http://www.w3.org/2004/01/pp-impl/">W3C Patent Policy
|
|
Implementation</a>.</p>
|
|
</div>
|
|
|
|
<h2 id="about">About this Charter</h2>
|
|
|
|
<p>This charter for the Media Annotations Working Group has been created
|
|
according to <a
|
|
href="http://www.w3.org/Consortium/Process/groups#GAGeneral">section 6.2</a> of
|
|
the <a href="http://www.w3.org/Consortium/Process">Process Document</a>. In the
|
|
event of a conflict between this document or the provisions of any charter and
|
|
the W3C Process, the W3C Process shall take precedence.</p>
|
|
|
|
<p>This charter has been extended on July 7, 2010 until June 30, 2011 (<a
|
|
href="http://lists.w3.org/Archives/Member/w3c-ac-members/2010JulSep/0000.html">announcement</a>);
|
|
at this time, the end date, team contact, and chairs information were updated
|
|
in this document. </p>
|
|
|
|
<p></p>
|
|
<hr />
|
|
<address>
|
|
Philippe Le Hégaret, <a href="mailto:plh@w3.org">plh@w3.org</a>
|
|
</address>
|
|
|
|
<p class="copyright"><a rel="Copyright"
|
|
href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>©
|
|
2008 <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.</p>
|
|
|
|
<p>$Date: 2010/07/07 21:11:14 $</p>
|
|
</div>
|
|
</body>
|
|
</html>
|