media-fragments-wg.html 19.7 KB

Raw Blame History Permalink

<?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 Fragments 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/" shape="rect"><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/" shape="rect"><img
src="http://www.w3.org/Icons/interaction" alt="Interaction Domain" /> </a> </p>

<h1 id="title">Media Fragments Working Group Charter</h1>

<p class="mission">The <strong>mission</strong> of the <a
href="/2008/WebVideo/Fragments/">Media Fragments Working Group</a>, part of the
Video in the Web Activity, is to address temporal and spatial media fragments
in the Web using Uniform Resource Identifiers (URI).</p>

<div class="noprint">
<p class="join"><a href="http://www.w3.org/2004/01/pp-impl/42785/join">Join the
Media Fragments 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">31 January 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"
        shape="rect">public</a></td>
    </tr>
    <tr>
      <th rowspan="1" colspan="1">Initial Chairs</th>
      <td rowspan="1" colspan="1">Erik Mannens, Raphaël Troncy </td>
    </tr>
    <tr>
      <th rowspan="1" colspan="1">Initial Team Contact <br />
        (FTE %: 30)</th>
      <td rowspan="1" colspan="1">Yves Lafon </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 URI-based mechanisms for uniquely
identifying temporal and spatial fragments for media objects in the Web, such
as video, audio, and images. The Group will investigate the several
possibilities in the URI syntax, such as URI fragment identifier or query
parameters, to address a region of a media object and the impact at the
application level.</p>

<p>In order to make video a first-class object on the World Wide Web, one
should be able to identify temporal and spatial regions. Having global
identifiers for arbitrary media segments/fragments would allow substantial
benefits, including in linking, bookmarking, caching and indexing. For example,
one should be able to point to the 20th second of the video news report,
bringing you directly to a specific news item within the report. Another
example is the ability to identify individuals or objects that are featured in
the video. None of the existing solutions (such as MPEG-21 or temporal URI) is
fully satisfactory or provides a general unique resource identifier for video
clips independently of the format in use. The <a
href="http://www.w3.org/2007/08/video/report.html#Deep_linking_into_Video_content">report
from the Video on the Web workshop</a> contains a summary of the current
situation but it is expected that the Group will analyze past attempts as well.
In addition, such mechanisms are also applicable for audio objects (temporal
dimension), and images (spatial dimension). In response, the Media Fragments
Working Group will investigate the existing solutions and approaches, such as
MPEG-21, SVG, SMIL, or temporal URI.</p>

<p>The Group will focus on developing a mechanism to uniquely identify a
temporal fragment within an audio or video object, that is independent of the
underlying audio or video codec in use, and will also investigate the delivery
of the requested resource to allow full or partial media retrieval using at
least the HTTP protocol. Furthermore, the Group will provide the partial
mapping between the developed URI syntax and the various ways of defining in
XML or URI a temporal or a spatial region in W3C Recommendations such as SVG
and SMIL.</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>Provide an URI-based mechanism to identify and link into video, audio,
    and images content, as well as recommendations for delivery of partial
    content.</li>
  <li>Production of stable documents addressing the work items listed in the <a
    href="#deliverables">Deliverables</a> section.</li>
  <li>Test suites for each deliverable with conformance criteria</li>
  <li>Availability of at least two implementations of each deliverable with
    conformance criteria, as demonstrated by an implementation report
    (summarizing implementation status against the relevant test suite) for
    each testable class of product, including user agents</li>
</ul>

<div>
<h3>Out of Scope</h3>

<p>This Working Group is not chartered to provide indirect mechanisms for
temporal and spatial fragments, such as using XML descriptions. It will,
however, recommend a mapping between the mechanisms existing in SVG and SMIL,
and the developed URI syntax.</p>
</div>

<div>

<h2 id="deliverables">Deliverables</h2>

<p>The Deliverables are divided in two phases, to allow rapid deployment of
temporal and simple spatial media fragment URIs. Note that work on the second
phase will depend on the success of the first Recommendation and will
necessitate Director's approval for the charter extension for its
completion.</p>

<p>The <strong>first phase</strong> will include:</p>
<ul>
  <li>A W3C Working Group Note for use cases and requirements for constructing
    temporal media fragment URIs for audio and video content, and simple
    spatial media fragment URIs for still images.</li>
  <li>A W3C Recommendation for constructing simple spatial and temporal media
    fragment URIs (Media Fragments 1.0). This would also include delivery
    considerations.</li>
</ul>

<p>The <strong>second phase</strong> will include:</p>
<ul>
  <li>A W3C Working Group Note for use cases and requirements for constructing
    spatio-temporal media fragment URIs for video content (including complex
    spatial regions for still images).</li>
  <li>A W3C Recommendation for constructing spatio-temporal media fragment URI
    (Media Fragments 2.0)</li>
</ul>

<div id="ig-other-deliverables">
<h3>Other Deliverables</h3>
<ul>
  <li>Comprehensive implementation test suite for the specification.</li>
  <li>Implementation and interoperability reports.</li>
  <li>Analysis of existing solutions and approaches and their shortcomings</li>
  <li>Analysis of constraints for creating a spatio-temporal URI specification
    on top of the existing URI standard (http://www.ietf.org/rfc/rfc3986.txt),
    e.g. fragment and query addressing, media types, protocol schemes, and URI
    templates</li>
  <li>Tutorial or primer resources (if suitable and if resources are
  available).</li>
  <li>Mapping of the identifier mechanism to and from SMIL, SVG and HTML media
    objects.</li>
  <li>Propose a new charter for follow on work on spatial and temporal media
    fragments.</li>
</ul>
</div>

<div>
<h3>Milestones</h3>

<p>In the interest of producing of delivering the easiest and most achievable
work within a small timeline, the Group will focus at producing the first phase
first. Depending on the success of the Group, the charter will need to get
extended in order to complete the second phase.</p>

<p><strong>Note:</strong> See changes from this initial schedule on the <a href="/2008/WebVideo/Fragments/">group home page</a>.</p>

<table class="roadmap" width="80%">
  <caption>Milestones</caption>
  <tfoot>
    <tr>
      <td colspan="6" rowspan="1">Note: The group will document significant
        changes from this initial schedule on the group home page.</td>
    </tr>
  </tfoot>
  <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">Use cases and requirements for Media Fragments 1.0</th>
      <td class="WD1" rowspan="1" colspan="1">November 2008</td>
      <td class="LC" rowspan="1" colspan="1">December 2008</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">Media Fragments 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">November 2009</td>
      <td class="REC" rowspan="1" colspan="1">January 2010</td>
    </tr>
    <tr>
      <th rowspan="1" colspan="1">Use cases and requirements for Media Fragments 2.0</th>
      <td class="WD1" rowspan="1" colspan="1">November 2009</td>
      <td class="LC" rowspan="1" colspan="1">January 2010</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">Media Fragments 2.0</th>
      <td class="WD1" rowspan="1" colspan="1">November 2009</td>
      <td class="LC" rowspan="1" colspan="1">March 2010</td>
      <td class="CR" rowspan="1" colspan="1">July 2010</td>
      <td class="PR" rowspan="1" colspan="1">November 2010</td>
      <td class="REC" rowspan="1" colspan="1">January 2011</td>
    </tr>
  </tbody>
</table>

<p><em>Note:</em> The Use Cases and Requirements will evolve in phases to
follow the phases of the Recommendation.</p>
</div>

<div>
<h3 id="timeline">Timeline View Summary</h3>
<ul>
  <li>August 2008: First teleconference</li>
  <li>October 2008: First face-to-face meeting</li>
  <li>November 2008: FPWD Use Cases and Requirements (Phase 1)</li>
  <li>December 2008: LC for Use Cases and Requirements (Phase 1)</li>
  <li>January 2009: Second face-to-face meeting</li>
  <li>February 2009: FPWD for Media Fragments 1.0</li>
  <li>March 2009: Third face-to-face meeting</li>
  <li>June 2009: LC for Media Fragments 1.0</li>
  <li>September 2009: CR for Media Fragments 1.0</li>
  <li>November 2009: FPWD Use Cases and Requirements (Phase 2) and Media
    Fragments 2.0, and PR for Media Fragments 1.0</li>
  <li>January 2010: REC for Media Fragments 1.0 and LC for Use Cases and
    Requirements (Phase 2)</li>
  <li>January 2010: LC for Media Fragments 2.0</li>
  <li>March 2010: Third face-to-face meeting</li>
  <li>July 2010: CR for Media Fragments 2.0</li>
  <li>November 2010: PR for Media Fragments 2.0</li>
  <li>January 2011: REC for Media Fragments 2.0</li>
</ul>
</div>
</div>

<div class="dependencies">
<h2 id="coordination">Dependencies and Liaisons</h2>

<p>As part of the Video in the Web Activity, the Media Fragment Working Group
will be represented in the Hypertext Coordination Group. </p>

<h3>Dependencies with W3C Groups</h3>
<dl>
  <dt>Synchronized Multimedia (SYMM) Working Group</dt>
    <dd>The Synchronized Multimedia Integration Language (SMIL) allows authors
      to describe the temporal behavior of a multimedia presentation, associate
      hyperlinks with media objects and describe the layout of the presentation
      on a screen.</dd>
  <dt>Scalable Vector Graphics (SVG) Working Group</dt>
    <dd>The Scalable Vector Graphics language allows authors to describe
      two-dimensional vector and mixed vector/raster graphics. It includes
      support for multimedia: audio, video and animation.</dd>
  <dt>HTML Working Group</dt>
    <dd>The HTML 5 specification is intended to provide a semantic-level markup
      language and associated semantic-level scripting APIs for authoring
      accessible pages on the Web ranging from static documents to dynamic
      applications. It includes media elements to present audio data, or video
      and audio data.</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>

<h3>Liaisons with W3C Groups</h3>
<dl>
  <dt>Protocols and Formats Working Group</dt>
    <dd>The PFWG looks at the formal Web technologies (protocols, formats,
      etc.) from an accessibility perspective. </dd>
  <dt>Hypertext Coordination Group</dt>
    <dd>The purpose of this group is to identify technical areas where
      different working groups may overlap, encourage discussion, and to
      coordinate their work. </dd>
  <dt>Technical Architecture Group (TAG)</dt>
    <dd>W3C has created the TAG to document and build consensus around
      principles of Web architecture. This Group published several materials
      related to URIs, such as <cite><a
      href="http://www.w3.org/2001/tag/doc/hash-in-url">Usage Patterns For
      Client-Side URL parameters</a></cite>.</dd>
  <dt>uri@w3.org mailing list</dt>
    <dd>While the URI Activity has been closed, this mailing list remains in
      effect and should be kept in the loop.</dd>
  <dt>public-sweo-ig@w3.org mailing list </dt>
    <dd>While the Semantic Web Education and Outreach (SWEO) Interest Group has
      been closed this mailing list remains in effect and should be kept in the
      loop. The <a href="http://www.w3.org/TR/cooluris">Cool URIs for the
      Semantic Web</a> is one of the Interest Group Notes produced by the SWEO
      Group.</dd>
</dl>

<div>
<h3>External Groups</h3>
<dl>
  <dt>Internet Engineering Task Force (IETF)</dt>
    <dd>The IETF is a large open international community of network designers,
      operators, vendors, and researchers concerned with the evolution of the
      Internet architecture and the smooth operation of the Internet. This
      organisation is responsible for RFC 3986 (URI), RFC 3987 (IRI), RFC 2326
      (RTSP), RFC 2912 (Media Features for MIME Content), and for discussion
      around video, audio, and image media types. </dd>
  <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-4 and MPEG-21. </dd>
  <dt>The Society of Motion Picture and Television Engineers (SMPTE) </dt>
    <dd>This organization was founded to advance theory and development in the
      motion imaging field. Among others, it produced the "SMPTE STANDARD for
      Television, Audio and Film - Time and Control Code" (SMPTE 12M). </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>
</dl>
</div>
</div>

<div class="participation">
<h2 id="participation">Participation</h2>

<p>To be successful, the Media Fragments Working Group is expected to have 7 or
more active participants for its duration. Effective participation to the Media
Fragments Working Group is expected to consume one work day per week for each
participant until Last Call; two days per week for editors. The Media Fragments
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"
shape="rect">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-fragment@w3.org.</p>

<p>Information about the group (deliverables, participants, face-to-face
meetings, teleconferences, etc.) is available from the Media Fragments 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"
shape="rect">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" shape="rect">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/" shape="rect">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/" shape="rect">W3C Patent Policy
Implementation</a>.</p>
</div>

<h2 id="about">About this Charter</h2>

<p>This charter for the Media Fragments Working Group has been created
according to <a href="http://www.w3.org/Consortium/Process/groups#GAGeneral"
shape="rect">section 6.2</a> of the <a
href="http://www.w3.org/Consortium/Process" shape="rect">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>Change notes:</p>

<ul>
<li>December 2008: Edited in place in to correct
the inconsistencies between the milestones and the timeline view summary.</li>
<li>10 February 2010: Charter extended to 31 January 2011.</li>
</ul>

<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"
shape="rect">Copyright</a>© 2008 <a href="http://www.w3.org/"
shape="rect"><acronym title="World Wide Web Consortium">W3C</acronym> </a>
<sup>®</sup>( <a href="http://www.csail.mit.edu/" shape="rect"><acronym
title="Massachusetts Institute of Technology">MIT</acronym> </a>, <a
href="http://www.ercim.org/" shape="rect"><acronym
title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym>
</a>, <a href="http://www.keio.ac.jp/" shape="rect">Keio</a>), All Rights
Reserved.</p>

<p>$Date: 2010/02/10 13:33:39 $</p>
</div>
</div>
</body>
</html>