08-mediaann-minutes.html 11.9 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" lang="en">
<head>
  <title>SV_MEETING_TITLE -- 08 Feb 2011</title>
  <link type="text/css" rel="STYLESHEET"
  href="http://www.w3.org/StyleSheets/base.css" />
  <link type="text/css" rel="STYLESHEET"
  href="http://www.w3.org/StyleSheets/public.css" />
  <link type="text/css" rel="STYLESHEET"
  href="http://www.w3.org/2004/02/minutes-style.css" />
  <meta content="SV_MEETING_TITLE" name="Title" />
  <meta content="text/html; charset=UTF-8" http-equiv="content-type" />
</head>

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

<h1>MAWG meeting minutes</h1>

<h2>08 Feb 2011</h2>

<p>See also: <a href="http://www.w3.org/2011/02/08-mediaann-irc">IRC log</a></p>

<h2><a name="attendees" id="attendees">Attendees</a></h2>

<div class="intro">
<dl>
  <dt>Present</dt>
    <dd>Thierry, Pierre-Antione, Courtney, Werner, Wonsuk, Joakim</dd>
  <dt>Regrets</dt>
  <dt>Florian, Mari Carmen, Daniel, Jean-Pierre, Felix.</dt>
  <dt>Chair</dt>
    <dd>Thierry</dd>
  <dt>Scribe</dt>
    <dd>Joakim</dd>
</dl>
</div>

<h2>Contents</h2>
<ul>
  <li><a href="#agenda">Topics</a>
    <ol>
      <li><a href="#item01">definiton of compression/format attributes:</a></li>
      <li><a href="#Publish">Publication of Ontology spec to 2nd Last
      Call</a></li>
    </ol>
  </li>
  <li><a href="#ActionSummary">Summary of Action Items</a></li>
</ul>
<hr />

<div class="meeting">
<p class="phone"></p>

<p class="phone"></p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; this is pchampin on the phone</p>

<p class="irc">&lt;<cite>tmichel</cite>&gt; sound is really bad</p>

<p class="phone">it's like you speak though a filter</p>

<p class="irc">&lt;<cite>tmichel</cite>&gt; Any volunteer to scribe?</p>

<p class="phone">wonsuk pls mute</p>

<p class="irc">&lt;<cite>tmichel</cite>&gt; <a
href="http://www.w3.org/2011/01/25-mediaann-minutes.html">http://www.w3.org/2011/01/25-mediaann-minutes.html</a></p>

<p class="irc">&lt;<cite>tmichel</cite>&gt; Minutes from 25/01 are approved</p>

<p class="irc">&lt;<cite>scribe</cite>&gt; Scribe: Joakim</p>

<p class="phone"><cite>Actions:</cite></p>

<h3 class="phone"><strong>Open actions:</strong></h3>

<p class="irc">&lt;<cite>tmichel</cite>&gt; Joakim's voice is ok</p>

<p class="phone">close action-368</p>

<p class="irc">&lt;<cite>trackbot</cite>&gt; ACTION-368 Improve description
text for ma:compression and ma:format closed</p>

<h3>Definiton of compression/format attributes:</h3>

<h3 id="item01"></h3>

<p class="irc">&lt;<cite>pchampin</cite>&gt; +1</p>

<p class="phone">Werner; we have examples of subtitles</p>

<p class="phone">close action-399</p>

<p class="irc">&lt;<cite>trackbot</cite>&gt; ACTION-399 Change from string to
string and/or URI in the ontology document closed</p>

<p class="phone">close action-398</p>

<p class="irc">&lt;<cite>trackbot</cite>&gt; ACTION-398 Send reminder email to
group to review ontology document closed</p>

<p class="phone">close action-401</p>

<p class="irc">&lt;<cite>trackbot</cite>&gt; ACTION-401 Implement Felix's
comment in the spec closed</p>

<p class="phone">close action-391</p>

<p class="irc">&lt;<cite>trackbot</cite>&gt; ACTION-391 Add subtitles example -
lc comment 2403 closed</p>

<p class="phone"><cite>Thierry:</cite> We are done with the comments for both
specs</p>

<p class="phone">we have received comments from Marie-Carmen which has been
included</p>

<p class="phone">comments from Werner will be included this afternoon</p>

<p class="phone"><cite>Werner:</cite> should we include the DFXP mappings, we
have the information?</p>

<p class="phone">OK, Werner will provide the mapping table, and Thierry will
include it</p>

<p class="phone"><cite>Thierry:</cite> Once we have the edits,shall we push the
ont doc to LC?<br />
 ... suggest to give extra 24h hours for people who did not join the group to
vote for publication</p>

<p class="phone"><cite>PA:</cite> how about the discussion on definiton of
compression/format attributes</p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; joakim: I'm not an expert
regarding format/compression</p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; ... first part of the track was
about the possible merging of format and compression.</p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; ... As we voted previously on
having both, we keep them.</p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; ... The second part is about
allowing strings as values or enforce URIs.</p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; werner: enforcing URIs has the
advantage of being more precise,</p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; ... but practically, this raises
problems with underlying formats that don't provide a URI.</p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; ... e.g. dublin-core</p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; ... David agrees to that point for
descriptive metadata,</p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; ... but thinks we can be more
stricy for technical metadata.</p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; ... He is assuming that the API
would access the actual media resource,</p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; ... and could therefore extract
the correct URI for compression.</p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; ... But we have a use case where
only an external source for metadata is available.</p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; ... We could add in the spec that
if the media resource is available, a URI must be returned.</p>

<p class="phone"><cite>PA:</cite> if we stick to URI, we must say which URI's
to use</p>

<p class="phone"><cite>Werner:</cite> we could come up with schemes to use,
but, there will be many</p>

<p class="phone"><cite>PA:</cite> we dont' want to commit to one particualr
scheme. We should be flexible enough, to map any metadata</p>

<p class="phone">but, if that precies information exists, it should be
returned</p>

<p class="irc">&lt;<cite>tmichel</cite>&gt; compression (attName="compression",
attValue="URI" | "String")</p>

<p class="phone">(attName="compression", attValue="URI#Name")</p>

<p class="irc">&lt;<cite>tmichel</cite>&gt; The Dublin Core uses a String</p>

<p class="phone"><cite>PA:</cite> If we make URI mandatory, there will be some
implementations that doesn't return anything</p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; ... if they lack the information
to make the URI</p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; ... so enforcing URIs will only
reduce the amount of info available.</p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; ... We should rather *encourage*
implementers to return a URI whenever they can</p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; ... but *allow* them to return
only a string.</p>

<p class="irc">&lt;<cite>tmichel</cite>&gt; The resolution is:</p>

<p class="irc">&lt;<cite>tmichel</cite>&gt; compression (attName="compression",
attValue="URI" | "String")</p>

<p class="phone"><cite>Thierry:</cite> Do we agree to what is in the spec?</p>

<p class="irc">&lt;<cite>tmichel</cite>&gt; +1</p>

<p class="irc">&lt;<cite>wbailer_</cite>&gt; +1</p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; ... anyway, users wanting precise
information will ignore strings and consider only URIs</p>

<p class="phone">+1</p>

<p class="irc">&lt;<cite>wonsuk</cite>&gt; +1</p>

<p class="irc">&lt;<cite>tmichel</cite>&gt; Resolution is to leave the spec as
is with:</p>

<p class="irc">&lt;<cite>tmichel</cite>&gt; compression (attName="compression",
attValue="URI" | "String")</p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; RESOLUTION: keep the spec as it
is, regarding compression: implenters can return either URI or String</p>

<p class="irc">&lt;<cite>tmichel</cite>&gt; Thierry to send email to the Group
if people want to object before tomorrow before moving to 2nd LC</p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; multiple values are still
possible, and implementers are *encouraged* to return a URI whenever they
can.</p>

<p class="phone"><cite>Thierry:</cite> add a note to implementers in the API
spec ?</p>

<p class="phone"><cite>Werner:</cite> It's an API issue, it knows if it can
retrieve the information</p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; +1</p>

<p class="phone"><cite>Thierry:</cite> We will have something in the API spec
to encourage implementers to return a URI</p>

<p class="phone">Wonsuk!</p>
<a name="action01" id="action01"></a>

<p class="irc">&lt;<cite>scribe</cite>&gt; <strong>ACTION:</strong> wonsuk for
compression, implementers are encouraged to return a URI [recorded in <a
href="http://www.w3.org/2011/02/08-mediaann-minutes.html#action01">http://www.w3.org/2011/02/08-mediaann-minutes.html#action01</a>]</p>

<p class="irc">&lt;<cite>trackbot</cite>&gt; Created ACTION-403 - For
compression, implementers are encouraged to return a URI [on WonSuk Lee - due
2011-02-15].</p>

<p></p>

<h3><a name="Publish" id="Publish">Publish the Ontology for Media Resources
specification as a 2nd LC</a></h3>

<p class="irc">&lt;<cite>tmichel</cite>&gt; After incorporation of Werner
updates and the Timed text mapping table ...</p>

<p class="irc">&lt;<cite>tmichel</cite>&gt; Does the Group votes to move to 2nd
last call</p>

<p class="irc">&lt;<cite>tmichel</cite>&gt; OK to publish 2nd LC ?</p>

<p class="irc">&lt;<cite>tmichel</cite>&gt; +1</p>

<p class="phone">+</p>

<p class="irc">&lt;<cite>wonsuk</cite>&gt; +1</p>

<p class="irc">&lt;<cite>wbailer_</cite>&gt; +1</p>

<p class="irc">&lt;<cite>pchampin</cite>&gt; +1</p>

<p class="phone"><cite>Resolution:</cite> The group agrees to publish the
Ontology for Media Resources specification as a 2nd LC.</p>

<p class="phone">Thierry will finish the editing work today ! Publication
should happen on thrursday. Thierry will announce it to the group and leave 14
hours for objections.</p>

<p></p>

<p class="phone">Next meeting in California ! Have a nice trip.</p>
</div>

<h2><a name="ActionSummary" id="ActionSummary">Summary of Action Items</a></h2>
<!-- Action Items -->
<strong>[NEW]</strong> <strong>ACTION:</strong> wonsuk for compression,
implementers are encouraged to return a URI [recorded in <a
href="http://www.w3.org/2011/02/08-mediaann-minutes.html#action01">http://www.w3.org/2011/02/08-mediaann-minutes.html#action01</a>]<br
/>
 <br />
[End of minutes]<br />

<hr />
<address>
  Minutes formatted by David Booth's <a
  href="http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm">scribe.perl</a>
  version 1.135 (<a href="http://dev.w3.org/cvsweb/2002/scribe/">CVS
  log</a>)<br />
  $Date: 2011/02/09 07:28:56 $
</address>

<div class="diagnostics">
<hr />

<h2>Scribe.perl diagnostic output</h2>
[Delete this section before finalizing the minutes.]<br />

<pre>This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20
Check for newer version at <a href="http://dev.w3.org/cvsweb/~checkout~/2002/scribe/">http://dev.w3.org/cvsweb/~checkout~/2002/scribe/</a>

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: jsderber
Found Scribe: Joakim
Default Present: +39.538.5.aaaa, wbailer, +2105800aabb, pchampin, +39.538.5.aacc
Present: Thierry Florian Pierre-Antione Courtney Werner Wonsuk Joakim

WARNING: No meeting title found!
You should specify the meeting title like this:
&lt;dbooth&gt; Meeting: Weekly Baking Club Meeting

Got date from IRC log name: 08 Feb 2011
Guessing minutes URL: <a href="http://www.w3.org/2011/02/08-mediaann-minutes.html">http://www.w3.org/2011/02/08-mediaann-minutes.html</a>
People with action items: are compression encouraged for implementers wonsuk

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.
</pre>
[End of <a
href="http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm">scribe.perl</a>
diagnostic output] </div>
</body>
</html>