guidelines-tracker-tool.html 25 KB

Raw Blame History Permalink

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
    "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
  <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  <title>Guidelines for Using W3C Last Call Tracker Tool</title>
  <style type="text/css">
  .example { background-color: #eee; border: solid green; border-width: 2px; padding: 0.5em;}
  .normative { background-color: #f8e691; border: solid red; border-width: 2px;padding: 0.5em; }
  </style>
  <link rel="stylesheet" type="text/css"
  href="http://www.w3.org/StyleSheets/TR/base">
</head>

<body>
<h1>Guidelines for Using W3C Last Call Tracker Tool.</h1>

<p>This document summerize the procedure for processing, responding and
tracking Media Annotation Last Call comments using <a
href="http://www.w3.org/2006/02/lc-comments-tracker/42786/">W3C Tracker
tool.</a></p>

<p>Steps:</p>
<ol>
  <li><a href="#L2196">The staff contact collects the Media Annotation API Last
    call comments</a> (sent to <a
    href="http://lists.w3.org/Archives/Public/public-media-annotation/">public-media-annotation@w3.org)</a></li>
  <li><a href="#L2201">People are assigned comments by chair</a></li>
  <li><a href="#L2205">Draft a WG Note</a></li>
  <li><a href="#L2232">Draft a proposal response</a></li>
  <li><a href="#Resolution">Resolution approved by MA WG</a></li>
  <li><a href="#L1730">Final resolution ready.</a></li>
  <li><a href="#L2238">Resolution implemented</a></li>
  <li><a href="#L2254">Send responses to commenter</a></li>
  <li><a href="#L2269">Commenter approves resolution</a></li>
  <li><a href="#L2284">Commenter rejects resolution</a></li>
  <li><a href="#L2315">Generate the Disposition of comments.</a></li>
</ol>

<p>Useful:</p>
<ul>
  <li><a href="#View">View comments</a></li>
  <li><a href="#Searching">Search comments</a></li>
  <li><a href="#comment">Add a new comment</a></li>
  <li>Editing a comment</li>
  <li><a href="#Send">Send replies to comments</a></li>
  <li><a href="#Dispositio">Disposition of Comments</a></li>
</ul>

<p><a href="#Issues">Issues/Bugs</a></p>
<hr>

<p></p>

<h2>0 - Specific Last Call Tracker Tool for each specification</h2>

<p>There are two Last Call Tracker Tools, one for each specification; API and
Ontology:</p>

<p>- API for Media Resource 1.0: <a
href="http://www.w3.org/2006/02/lc-comments-tracker/42786/WD-mediaont-api-1.0-20100608/">http://www.w3.org/2006/02/lc-comments-tracker/42786/WD-mediaont-api-1.0-20100608/</a></p>

<p>- Ontology for Media Resource 1.0: <a
href="http://www.w3.org/2006/02/lc-comments-tracker/42786/WD-mediaont-10-20100608/">http://www.w3.org/2006/02/lc-comments-tracker/42786/WD-mediaont-10-20100608/</a></p>

<p>This allows tracking comment wrt to the proper Specification.</p>

<p></p>

<p>The following guidelines are provided for the API specification. The same
process applies to the Ontology specification (using the Ontology Last Call
Tracker Tool and proper links. </p>

<p></p>

<h2><a name="L2196" id="L2196">1- The staff contact collects the Media
Annotation API Last Call comments</a></h2>

<p>For each Media Annotation API Last Call comment sent to <a
href="http://lists.w3.org/Archives/Public/public-media-annotation/">public-media-annotation@w3.org</a><a
href="http://lists.w3.org/Archives/Public/www-smil/index.html"></a>, the staff
contact makes a new entry in the Tracker tool, using the "<a
href="http://www.w3.org/2006/02/lc-comments-tracker/42786/WD-mediaont-api-1.0-20100608/add">Add
a new comment</a>" link in the menu at the right of the page.<br>
When a message includes multiple comments, the message may be split into
multiple entries in the Tracker tool, to ease response by the WG.</p>

<p>The staff contact fills the following fields for each comment:</p>
<ul>
  <li>"<strong>URI of the message</strong>" from the <a
    href="http://lists.w3.org/Archives/Public/public-media-annotation/">public-media-annotation@w3.org</a>
    mailing archives.</li>
  <li>"<strong>Comment sent on behalf of</strong>" field with the name for
    example of a WG.</li>
  <li>"<strong>Comment</strong>" field. You may import the whole comment
    message or include partial text comment using one of the two
  checkboxes.</li>
  <li>"<strong>Short name for this comment</strong>" field (optional) but
    recommended ;-)</li>
  <li>"<strong>Section of the document concerned</strong>" field.</li>
  <li>Then, the staff contact clicks the "<strong>Add a new comment</strong>"
    button.</li>
</ul>

<p>The tracker tool sets automatically the following fields:</p>
<ul>
  <li>"<strong>ID number</strong>" field (<code>LC-xxxx</code>).</li>
  <li>"<strong>Name of the commenter</strong>" field</li>
  <li>"<strong>Email of the commenter</strong>" field</li>
  <li>"<strong>Status</strong>" field initially set to "<code>Open"</code></li>
  <li>"<strong>Assigned to</strong>" field initially set to
    "<code>Nobody"</code></li>
  <li>"<strong>Type</strong>" field initially set to
  "<code>Substantive"</code></li>
  <li>"<strong>Message-ID</strong>" field (Message-ID from the initial message
    sent to archives)</li>
</ul>

<h2><a name="L2201" id="L2201">2 - People are assigned comments by
chair</a></h2>

<p>The Chair assigns each comment to a WG Participant. If you are assigned
comments, you are committed to draft a response to the comment. You are now the
editor of the response to that comment.</p>

<p>The Chair fills the following fields for each comment:</p>
<ul>
  <li>"<strong>Assigned to</strong>" field with the name of a WG participant,
    from the drop down menu list.</li>
  <li>Then, the chair submits the comment using "<strong>Submit</strong>"
    button.</li>
</ul>

<h2><a name="L2205" id="L2205">3 - Draft a WG Note</a></h2>

<p>Any WG Participant may add proposal, remarks, statement, to help the editor
of the response drafting a response. <br>
For example these can be initial remarks given by the WG during a telecon or a
F2F meeting. <br>
The "<strong>WG Notes</strong>" field provides hints discussed during the F2F
to help editor draft the response.</p>

<p>The WG Participant fills the following fields for the comment:</p>
<ul>
  <li>"<strong>Status</strong>" field updated to "<code>Pending"</code></li>
  <li>"<strong>WG Notes"</strong> field updated with your statement.</li>
  <li>If the comment is related to another comment, use the <strong>"Related
    issues"</strong> field to link to it. (if multiple related comments, use
    space separated ids).</li>
  <li>Then, the WG Participant submits the comment using "<strong>Submit as
    Proposal</strong>" button.</li>
</ul>

<p>Note: When the WG Participant submits the comment using "<strong>Submit as
Proposal</strong>" button, the "<strong>Status</strong>" field is automatically
updated to "<code>Proposal</code>".</p>

<h2><a name="L2232" id="L2232">4 - Draft the proposed resolution</a></h2>

<p>The editor drafts a proposed resolution using suggestions from the "WG
Notes" field which provides hints discussed during the F2F and using Minutes of
the last F2F for detailed discussions and resolutions)</p>

<p>The editor fills the following fields for the comment:</p>
<ul>
  <li>"<strong>Status</strong>" field updated to
    <code>"<code>Proposal"</code></code></li>
  <li>"<strong>Type</strong>" field updated to
    "<code>editorial,typo,question,general,undefined,substantive</code>". (by
    default the type is set to "<code>substantive</code>").</li>
  <li>"<strong>Resolution</strong>" field with your proposed resolution. The
    editor must also copy and send the drafted resolution for approval by the
    WG to the group mailing list; public-media-annotation@w3.org</li>
  <li>Then, the editor submits the comment using "<strong>Update</strong>"
    button.</li>
</ul>

<p>Note: In your response, draft only the technical solution. No need to write
name of the commenter, formulate courtesy, introduction, date of review, etc.
The Track tool will do it automatically. <a href="#Example">See response
example.<br>
</a>The "<strong>WG Notes</strong>" is not included in the response to
commenter. Only the "<strong>Resolution</strong>" field is included.</p>

<h2>5 - <a name="Resolution" id="Resolution">Resolution approved by MA
WG</a></h2>

<p>If you have received remarks from the WG about your proposed resolution,
update the "<strong>Resolution</strong>" field.<br>
If you didn't get any objection to your proposed resolution from the WG within
48 hrs, your technical proposal is approved by the WG.</p>

<p>The Editor fills the following fields for each comment:</p>
<ul>
  <li>"<strong>Status</strong>" field updated to :<br>
    - "<code>Resolved-yes</code>" if the resolution is equal to the commenter's
    request.<br>
    - "<code>Resolved-partial</code>" if the resolution partially fulfills the
    commenter's request.<br>
    - "<code>Resolved-no</code>" if the resolution does not fulfills the
    commenter's request.</li>
  <li>"<strong>Resolution</strong>" field updated with input from the WG. The
    editor must also copy and send the revised resolution to the group mailing
    list; public-media-annotation@w3.org</li>
  <li>The editor updates the comment using "<code>Update</code>" button.</li>
</ul>

<p>Note: Once the "<strong>Status</strong>" field is updated to any of the 3
above "Resolved" status and Updated, the comment will then include new
"<strong>Resolution status</strong>" and "<strong>Response status</strong>"
sections, allowing to track advancement of resolution, spec editing and status
of response.</p>

<h2><a name="L1730" id="L1730">6 - Final resolution ready</a></h2>

<p>The resolved resolution might need some more wording for public
consumption.</p>

<p>The Editor fills the following fields for the comment:</p>
<ul>
  <li>"<strong>Resolution</strong>" field updated with final wording.</li>
  <li>"<strong>Resolution status:</strong>" checkbox "<code>Response
    drafted</code>" checked.</li>
  <li>The editor updates the comment using "<code>Update</code>" button.</li>
</ul>

<h2><a name="L2238" id="L2238">7 - Resolution implemented</a></h2>

<p>Fore each comment, the WG participant assigned the response to comment (the
editor) must make sure the necessary edits in the SMIL CR version are done. If
the editor of the response to comment is not the editor of the Section of the
document to be updated, he must coordinate with proper spec editor (s) of the
section which are impacted with the resolution. He will track and verify that
the spec has been correctly updated.</p>
<ul>
  <li>"<strong>Resolution status:</strong>" checkbox "<code>Resolution
    implemented"</code> checked.</li>
  <li>The editor updates the comment using "<code>Update</code>" button.</li>
</ul>

<h2><a name="L2254" id="L2254">8 - Send responses to commenter</a></h2>

<p>The staff contact sends the responses with the tracker tool using the "<a
href="http://www.w3.org/2006/02/lc-comments-tracker/42786/WD-mediaont-api-1.0-20100608//replies">Send
replies to comments</a>" link, in the menu at the right of the page and,</p>
<ul>
  <li>Enters a deadline date by which commenters are asked to reply (allow a
    maximum of 10 days).</li>
  <li>Provides an optional URI of the updated specification</li>
  <li>May preview the final responses sent to commenters, if necessary</li>
  <li>The staff contact sends the comment using "<code>sending replies</code>"
    button.</li>
</ul>

<p>When comments are sent, the tracker tool will automatically check the
"<strong>Response status:</strong>" checkbox to "<code>Reply sent to
commenter"</code></p>

<p>Note: Tracker tool sends only the response to commenters when both
"<strong>Resolution status:</strong>" checkboxes "<code>Response
drafted</code>" and "<code>Resolution implemented</code>" are checked.<br>
</p>

<p>Note: The response includes all necessary info generated automatically by
tracker tool e.g. the name of commenter, formulate courtesy, introduction, date
of review, etc. <a href="#Example">See response example</a></p>

<h2><a name="L2269" id="L2269">9 - Commenter approves resolution</a></h2>

<p>When the commenter has sent a mail to public-media-annotation@w3.org
approving the WG response, the staff contact updates the comment for following
field:</p>
<ul>
  <li>"<strong>Response status</strong>" checkbox <code>"Commenter approved
    disposition"</code> checked.</li>
  <li>The staff contact updates the comment using "<code>Update</code>"
  button.</li>
</ul>

<p>The comment is now considered processed and closed.</p>

<h2><a name="L2284" id="L2284">10 - Commenter rejects resolution</a></h2>

<p>When the commenter has sent a mail to public-media-annotation@w3.org
rejecting the WG response, the staff contact updates the comment for following
field:</p>
<ul>
  <li>"<strong>Response status</strong>" checkbox <code><code>"Commenter
    objected to disposition"</code> checkbox.</code> checked.</li>
  <li>The staff contact updates the comment using "<code>Update</code>"
  button.</li>
</ul>

<p>When a resolution is rejected by a commenter, the WG should attempt to
satisfy the reviewer. In order to do so, the WG should discuss solutions on the
public mailing list www-smil@w3.org. Once a new proposal satisfies the
reviewer, the editor must proceed with</p>

<p>- Step 5 <a href="#Resolution">Resolution approved by MA WG<br>
</a>- Step 6 <a href="#L2238">Resolution implemented</a></p>

<p></p>

<p>Note: For each objection, the WG should attempt to satisfy the reviewer. If
no agreement is reached, the objection will be discussed during the Transition
meeting with the Director. See <a
href="http://www.w3.org/2005/08/online_xslt/xslt?xmlfile=http://www.w3.org/2005/08/01-transitions.html&amp;xslfile=http://www.w3.org/2005/08/transitions.xsl&amp;docstatus=cr-tr">Organize
Transition to CR.</a></p>

<p><em>Issue: What happens if at this phase the WG review its resolution to
satisfy the commenter and therefore updates the resolution field ? How can we
resend it to the commenter with tracker ?</em></p>

<h2><a name="L2315" id="L2315">11 - Generate the Disposition of
comments</a></h2>

<p>The Disposition of comments document is generated automatically by tracker
tool ;-)</p>

<p>This document is to be used in the meeting with the W3C Director for
Transition request to CR. <br>
It allows showing evidence that the document has received wide review and that
that issues have been formally addressed. <a
href="http://www.w3.org/2005/08/online_xslt/xslt?xmlfile=http://www.w3.org/2005/08/01-transitions.html&amp;xslfile=http://www.w3.org/2005/08/transitions.xsl&amp;docstatus=cr-tr">See
Organize Transition to CR.</a></p>

<p>1- In the "Commenter" column:</p>

<p>This column provides:<br>
- Comment number, linking to the edit mode page of the comment <br>
- Commenter's name, linking to the email of the commenter<br>
</p>

<p>2- In the "WG decision" column:</p>

<p>This column provides the WG resolution as sent to the commenter.</p>

<p>- <span style="color: #FF0000">red</span> indicates that the Working Group
didn't agree with the comment; "<strong>Status</strong>" field set to
"<code>Resolved-no</code>"<br>
- <span style="color: #008040">green</span> indicates that the Working Group
agrees with the comment; "<strong>Status</strong>" field set to
"<code>Resolved-yes</code>"<br>
- <span style="color: #FFFF00">yellow</span> indicates an in-between situation;
"<strong>Status</strong>" field set to "<code>Resolved-partial</code>"</p>

<p>3- In the "Commenter reply" column:</p>

<p>This column provides the Commenter reply as sent to the public list.</p>

<p>- <span style="color: #FF0000">red</span> indicates the commenter objected
to the WG resolution, ["<strong>Response status</strong>" checkbox
<code>"Commenter approved disposition"</code> was checked] by Staff Contact.<br>
- <span style="color: #008040">green</span> indicates approval from the
commenter ["<strong>Response status</strong>" checkbox <code>"Commenter
objected to disposition"</code> was checked] by Staff Contact.<br>
- <span style="color: #FFFF00">yellow</span> indicates the commenter didn't
respond to the request for feedback.</p>

<p><a
href="http://www.w3.org/2006/02/lc-comments-tracker/37584/mwbp-cr/doc">See
example of Disposition of comments</a> for the Mobile Web Best Practices
Working Group</p>

<h2><a name="Misc" id="Misc">Useful</a></h2>

<h3><a name="View" id="View">View comments</a></h3>

<p>Tracker tool offers 2 different views of the list of comments:</p>

<p id="detailed-list">1- The <a
href="http://www.w3.org/2006/02/lc-comments-tracker/42786/WD-mediaont-api-1.0-20100608/">detailed
editable view list </a>", available from the menu at the right of the page.</p>

<p>It provides an extended list of comments. Comments are showed 20 by page on
multiple pages if there is a large amount of comments.</p>

<p>For each comment it shows all fields, (Status, ID, Type, Assigned to, WG
Notes, Resolution).</p>

<p>It offers filtering capabilities for following fields:</p>
<ul>
  <li><strong>Type</strong>: [<code>all, substantive, editorial, typo,
    question, general comment, undefined]</code></li>
  <li><strong>Status</strong> : [<code>all, open, proposal, pending,
    resolved-yes, resolved-no,resolved-partial, other]</code></li>
</ul>

<p>There is also a very handy "<strong>Quick acces to</strong>" allowing to
reach the editing mode of a particular comment for editing.</p>

<p>Note: Comments are ordered by Type, and the section they refer to.</p>

<p id="short-list">2- The <a
href="http://www.w3.org/2006/02/lc-comments-tracker/42786/WD-mediaont-api-1.0-20100608/status">status
of comments view list</a>, hidden from the menu, but very usefull. It is a
summerized view where each comment is listed on a single line with following
links:</p>

<p id="short-list1">- The ID links to the "Edit comment LC-xxxx" page.<br>
- The commenter's name links to his comment archived in the public mailing
list<br>
- Section links to the section concerned by the comment <br>
- Type: [ <code>substantive, editorial, typo, question, general comment,
undefined]</code><br>
- Status : [<code>open, proposal, pending,
resolved-yes,resolved-no,resolved-partial, other]</code></p>

<p>Note: Comments are ordered by Type, and the section they refer to.</p>

<h3><a name="Searching" id="Searching">Searching comments</a></h3>

<p>Tracker tool offers searching functionnality, using the "<a
href="http://www.w3.org/2006/02/lc-comments-tracker/42786/WD-mediaont-api-1.0-20100608/search/">Search
comments</a>" link in the menu at the right of the page.</p>

<p>You can search in the list of comments by following fields:</p>
<ul>
  <li><strong>Type</strong>: [<code>any, substantive, editorial, typo,
    question, general comment, undefined]</code></li>
  <li><strong>Status</strong>: [<code>any, open, proposal, pending,
    resolved-yes, resolved-no,resolved-partial, other]</code></li>
  <li><strong>Resolution status</strong> : [<code>including, excatly of,
    excluding</code>] with following checkboxes: <br>
    [<code>Response drafted</code>] [<code>Resolution implemented</code>]
    [<code>Reply sent to commenter]</code></li>
  <li><strong>Response status</strong> :] with following checkboxes: <br>
  </li>
  <li>[<code>No response from Commenter yet</code>] [<code>Commenter approved
    disposition</code>] [<code>Commenter objected to disposition]</code></li>
  <li><strong>Commenter</strong> : [<code>any, or a commenter name from the
    list</code>]</li>
  <li><strong>On behalf of</strong> : [<code>any, or a WG name or commenter
    name from the list]</code></li>
  <li><strong>On section</strong> : [<code>any, or a section in the
  list</code>]</li>
  <li><strong>Assigned to</strong> : [<code>any, or a WG participants name from
    the list</code>]</li>
  <li><strong>Comment containing the keyword</strong> : [string]</li>
  <li><strong>WG Notes containing the keyword</strong> : [string]</li>
  <li><strong>Resolution containing the keyword</strong>: [string]</li>
  <li><strong>Show results as</strong>" [<code><a href="#short-list">list</a>,
    <a href="#detailed-list">editable entries]</a></code></li>
</ul>

<h3 id="comment">Add a new comment</h3>

<p>The Tracker tool allows add comments using the "<a
href="http://www.w3.org/2006/02/lc-comments-tracker/42786/WD-mediaont-api-1.0-20100608//add">Add
a new comment</a>" link in the menu at the right of the page.<br>
When a comment includes multiple comment items, the comment sent may be split
into multiple entries in the Tracker tool, to ease response by the WG.</p>

<p>Following fields should be filled:</p>
<ul>
  <li>"<strong>URI of the message</strong>" from to <a
    href="http://lists.w3.org/Archives/Public/public-media-annotation/">public-media-annotation@w3.org</a>
    mailing archives.</li>
  <li>"<strong>Comment sent on behalf of</strong>" field with the name for
    example of a WG.</li>
  <li>"<strong>Comment</strong>" field. You may import the whole comment
    message or include partial text comment using one of the two
  checkboxes.</li>
  <li>"<strong>Short name for this comment</strong>" field (optional) but
    recommended ;-)</li>
  <li>"<strong>Section of the document concerned</strong>" field.</li>
  <li>Then, the staff contact clicks the "<strong>Add a new comment</strong>"
    button.</li>
</ul>

<p>The tracker tool sets automatically the following fields:</p>
<ul>
  <li>"<strong>ID number</strong>" field (<code>LC-xxxx</code>).</li>
  <li>"<strong>Name of the commenter</strong>" field</li>
  <li>"<strong>Email of the commenter</strong>" field</li>
  <li>"<strong>Status</strong>" field initially set to "<code>Open"</code></li>
  <li>"<strong>Assigned to</strong>" field initially set to
    "<code>Nobody"</code></li>
  <li>"<strong>Type</strong>" field initially set to
  "<code>Substantive"</code></li>
  <li>"<strong>Message-ID</strong>" field (from the initial message sent to
    archives)</li>
</ul>

<h3 id="Send">Send replies to comments</h3>

<p>The tracker tool sends replies using the "<a
href="http://www.w3.org/2006/02/lc-comments-tracker/42786/WD-mediaont-api-1.0-20100608/replies">Send
replies to comments</a>" link, in the menu at the right of the page and,</p>
<ul>
  <li>Enters a date by which commenters are asked to reply (allow a maximum of
    10 days).</li>
  <li>Provides an optional URI of the updated specification</li>
  <li>May preview the final responses sent to commenters.</li>
</ul>

<p>When comments are sent, the tracker tool will automatically change the
"<strong>Response status</strong>" checkbox to "<code>Reply sent to
commenter"</code></p>

<p>Note: Tracker tool sends only the response to commenters when both
"<strong>Resolution status</strong>" checkboxes "<code>Response drafted</code>"
and "<code>Resolution implemented</code>" are checked.<br>
</p>

<p>Note: The response includes all necessary info generated automatically by
tracker tool e.g. the name of commenter, formulate courtesy, introduction, date
of review, etc. See response example</p>

<h3 id="Dispositio">The Disposition of comments</h3>

<p>Tracker tool generated automatically, using the "<a
href="guidelines-tracker-tool.html/doc">Disposition of comments</a> " link in
the menu at the right of the page.</p>

<p>It builds a HTML table with all comments.</p>

<p>This document will be used in the meeting with the W3C Director for
Transition request to CR. <br>
It will allow to show evidence that the document has received wide review and
that that issues have been formally addressed. See Organize Transition to
CR.</p>

<p>For more info, refer to <a href="#L2315">Generate Disposition of
comments</a> above section.</p>

<p><strong><a name="Example" id="Example">Example of LC comment response
generated by Tracker:</a></strong></p>

<div class="example">
<p>From LC comments LC-1959<br>
Subject: Re: [LC comment API] ....<br>
In-Reply-To: &lt;17543298765@example.com&gt;<br>
Cc: public-media-annotation@w3.org</p>

<p>Dear John,</p>

<p>The Media Annotations Working Group has reviewed the comments you sent [1]
on the Last Call Working Draft [2] of the API for Media Resource 1.0 published
on 08 June 2010. Thank you for having taken the time to review the document and
to send us comments!</p>

<p>The Working Group's response to your comment is included below.</p>

<p>Please review it carefully and let us know by email at
public-media-annotation@w3.org if you agree with it or not before [<em>deadline
date inserted here</em>]. In case of disagreement, you are requested to provide
a specific solution for or a path to a consensus with the Working Group. If
such a consensus cannot be achieved, you will be given the opportunity to raise
a formal objection which will then be reviewed by the Director during the
transition of this document to the next stage in the W3C Recommendation
Track..</p>

<p>Thanks,</p>

<p>For the Media Annotations Working Group,<br>
Thierry Michel,<br>
W3C Team Contact</p>

<p>1. http://www.w3.org/mid/17543298765@example.com<br>
2. http://www.w3.org/TR/2010/WD-mediaont-api-1.0-20100608</p>

<p>=====</p>

<p>Your comment on [API for Media Resource 1.0] ....<br>
</p>

<p>[<em>COMMENT from the comment field is inserted here</em>]<br>
</p>

<p>Working Group Resolution:</p>

<p>[<em>WG RESOLUTION from the Resolution field is inserted here</em>]</p>
</div>

<h3><a name="Issues" id="Issues">Issues/Bugs:</a></h3>

<p>TBD.</p>
<hr>

<p><a href="mailto:tmichel@w3.org">Thierry Michel</a>, Media Annotations WG
Team Contact</p>

<p><span class="small">Last revised $Date: 2010/09/15 15:18:31 $ by $Author tmichel
$</span></p>
</body>
</html>