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.
312 lines
11 KiB
312 lines
11 KiB
<?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>Media Annotations WG -- 01 Mar 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="Media Annotations WG" 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>- DRAFT -</h1>
|
|
|
|
<h1>Media Annotations WG</h1>
|
|
|
|
<h2>01 Mar 2011</h2>
|
|
|
|
<p>See also: <a href="http://www.w3.org/2011/03/01-mediaann-irc">IRC log</a></p>
|
|
|
|
<h2><a name="attendees" id="attendees">Attendees</a></h2>
|
|
|
|
<div class="intro">
|
|
<dl>
|
|
<dt>Present</dt>
|
|
<dd>joakim, mari-carmen, thierry, werner, pierre-antoine</dd>
|
|
<dt>Regrets</dt>
|
|
<dd>felix, jean-pierre, florian</dd>
|
|
<dt>Chair</dt>
|
|
<dd>joakim</dd>
|
|
<dt>Scribe</dt>
|
|
<dd>wbailer</dd>
|
|
</dl>
|
|
</div>
|
|
|
|
<h2>Contents</h2>
|
|
<ul>
|
|
<li><a href="#agenda">Topics</a>
|
|
<ol>
|
|
<li><a href="#item01">action items</a></li>
|
|
<li><a href="#item02">lc2 for ontology document</a></li>
|
|
<li><a href="#item03">revision of api doc</a></li>
|
|
<li><a href="#item04">metadata files for rdf test suite</a></li>
|
|
<li><a href="#item05">next f2f</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"><<cite>tmichel</cite>> can you hear me ?</p>
|
|
|
|
<p class="irc"><<cite>jsderber</cite>> no</p>
|
|
|
|
<p class="irc"><<cite>tmichel</cite>> yes I am calling with SIP</p>
|
|
|
|
<p class="irc"><<cite>jsderber</cite>> Can you hear us?</p>
|
|
|
|
<p class="irc"><<cite>tmichel</cite>> seems you can't hear me.</p>
|
|
|
|
<p class="irc"><<cite>tmichel</cite>> Yes we should discuss the the F2F
|
|
in Sophia.</p>
|
|
|
|
<p class="irc"><<cite>tmichel</cite>> I will reconnect ...</p>
|
|
|
|
<p class="irc"><<cite>tmichel</cite>> yes I hear you 100%</p>
|
|
|
|
<p class="irc"><<cite>tmichel</cite>> seems the mic does not work ...</p>
|
|
|
|
<p class="irc"><<cite>tmichel</cite>> let me try to fix it</p>
|
|
|
|
<p class="irc"><<cite>tmichel</cite>> please proceed ...</p>
|
|
|
|
<p class="irc"><<cite>scribe</cite>> scribe: wbailer</p>
|
|
|
|
<p class="phone">next meeting: mar 8</p>
|
|
|
|
<h3 id="item01">action items</h3>
|
|
|
|
<p class="phone">close actio-302</p>
|
|
|
|
<p class="phone">close action-302</p>
|
|
|
|
<p class="irc"><<cite>trackbot</cite>> ACTION-302 Check out the
|
|
consistency in the property names in the Ontology document's table closed</p>
|
|
|
|
<p class="phone">this is done by changes after F2F</p>
|
|
|
|
<p class="phone">actions 2404 and 2418 refer to ontology doc</p>
|
|
|
|
<p class="irc"><<cite>tmichel</cite>> no objections</p>
|
|
|
|
<p class="phone">close action-334</p>
|
|
|
|
<p class="irc"><<cite>trackbot</cite>> ACTION-334 Check if comment 2404
|
|
is in the document closed</p>
|
|
|
|
<p class="phone">close action-343</p>
|
|
|
|
<p class="irc"><<cite>trackbot</cite>> ACTION-343 Check if comment 2418
|
|
is in the document closed</p>
|
|
|
|
<p class="phone">360 is pending</p>
|
|
|
|
<p class="irc"><<cite>jsderber</cite>> we wait for you to come back!</p>
|
|
|
|
<p class="irc"><<cite>tmichel</cite>> Is there anyone else using SIP
|
|
today ?</p>
|
|
|
|
<p class="irc"><<cite>jsderber</cite>> we can hear you, but there is a
|
|
buzz</p>
|
|
|
|
<p class="phone">status on 365: made changes to api doc to add references to
|
|
html5 element</p>
|
|
|
|
<p class="phone">close action-365</p>
|
|
|
|
<p class="irc"><<cite>trackbot</cite>> ACTION-365 Respond to the email in
|
|
the archive 2419, from Paul Cotton closed</p>
|
|
|
|
<p class="irc"><<cite>pchampin</cite>> +1</p>
|
|
|
|
<p class="phone">leave 402 and 403 open</p>
|
|
|
|
<p class="phone">on 403: add a more general statement that URI is to be
|
|
returned whenever possible</p>
|
|
|
|
<h3 id="item02">lc2 for ontology document</h3>
|
|
|
|
<p class="irc"><<cite>tmichel</cite>> Move to 2nd Last Call the Ontology
|
|
draft ? No objections ?</p>
|
|
|
|
<p class="irc"><<cite>tmichel</cite>> Resolution is to publish the
|
|
Ontology for Media Resources 1.0 as a 2nd Last Call. </p>
|
|
|
|
<h3 id="item03">revision of api doc</h3>
|
|
|
|
<p class="phone">status see <a
|
|
href="http://lists.w3.org/Archives/Public/public-media-annotation/2011Mar/0001.html">http://lists.w3.org/Archives/Public/public-media-annotation/2011Mar/0001.html</a></p>
|
|
|
|
<p class="irc"><<cite>jsderber</cite>> the plan is to have a draft ready
|
|
before next telecon</p>
|
|
|
|
<p class="irc"><<cite>jsderber</cite>> There are three (new) issues that
|
|
has to solved</p>
|
|
|
|
<p class="irc"><<cite>jsderber</cite>> This will be discussed next
|
|
meeting!</p>
|
|
|
|
<p class="irc"><<cite>tmichel</cite>> schema could be an external file
|
|
for validation ...</p>
|
|
|
|
<p class="phone"><cite>pchampin:</cite> put json schema in annex, in different
|
|
format as examples to make clear</p>
|
|
|
|
<p class="phone"><cite>joakim:</cite> developers often prefer examples</p>
|
|
|
|
<h3 id="item04">metadata files for rdf test suite</h3>
|
|
|
|
<p class="irc"><<cite>tmichel</cite>> felix email</p>
|
|
|
|
<p class="irc"><<cite>tmichel</cite>> <a
|
|
href="http://lists.w3.org/Archives/Public/public-media-annotation/2011Feb/0092.html">http://lists.w3.org/Archives/Public/public-media-annotation/2011Feb/0092.html</a></p>
|
|
|
|
<p class="irc"><<cite>jsderber</cite>> <a
|
|
href="http://lists.w3.org/Archives/Public/public-media-annotation/2011Feb/0090.html">http://lists.w3.org/Archives/Public/public-media-annotation/2011Feb/0090.html</a></p>
|
|
|
|
<p class="irc"><<cite>jsderber</cite>> To answer the question from Felix,
|
|
is it mandatory to have all mappings?</p>
|
|
|
|
<p class="irc"><<cite>jsderber</cite>> Werner: my strategy is to have as
|
|
many as possible</p>
|
|
|
|
<p class="irc"><<cite>pchampin</cite>> mine too</p>
|
|
|
|
<p class="irc"><<cite>tmichel</cite>> l if you have an image you probably
|
|
can not use video properties ...</p>
|
|
|
|
<p class="phone"><cite>pchampin:</cite> goal for ID3 was to have all properties
|
|
as possible, might be more difficult for other formats</p>
|
|
|
|
<p class="irc"><<cite>pchampin</cite>> maybe we should aim at having for
|
|
each format a small set of example covering the whole mapping table</p>
|
|
|
|
<p class="phone"><cite>thierry:</cite> was not sure what to answer, we should
|
|
try to use as many properties as possible<br />
|
|
... not all properties might be useful together in one file<br />
|
|
... having a file with only 2-3 properties would not be right</p>
|
|
|
|
<p class="phone"><cite>pchampin:</cite> files should cover the whole mapping
|
|
table, trying to achieve this with as few files as possible<br />
|
|
... otherwise mappings cannot be fully tested</p>
|
|
|
|
<p class="irc"><<cite>tmichel</cite>> should use a set of files to covert
|
|
all the properties for each format</p>
|
|
|
|
<p class="phone"><cite>joakim:</cite> not possible to have all properties in
|
|
one file, if properties are mutually exclusive for different media types</p>
|
|
|
|
<p class="irc"><<cite>jsderber</cite>> PA: most important is to have as
|
|
realisitc exampples as possible</p>
|
|
|
|
<p class="phone"><cite>joakim:</cite> several files are necessary to cover
|
|
mapping table</p>
|
|
|
|
<p class="irc"><<cite>jsderber</cite>> I was kicked out, coming
|
|
back...</p>
|
|
|
|
<p class="phone"><cite>thierry:</cite> there are formats like dublin core that
|
|
lack several properties<br />
|
|
... files should cover all properties, for which the corresponding mapping
|
|
table defines a mapping</p>
|
|
|
|
<p class="irc"><<cite>pchampin</cite>> +1</p>
|
|
|
|
<p class="irc"><<cite>tmichel</cite>> I agree with PA. files should cover
|
|
the mapping table properties that are appropriate</p>
|
|
|
|
<p class="irc"><<cite>tmichel</cite>> I will answer Felix</p>
|
|
|
|
<p class="phone"><cite>joakim:</cite> thierry to answer felix's question</p>
|
|
|
|
<p class="phone"><cite>thierry:</cite> table in wiki</p>
|
|
|
|
<p class="irc"><<cite>tmichel</cite>> <a
|
|
href="http://www.w3.org/2008/WebVideo/Annotations/wiki/Format_mapping_review">http://www.w3.org/2008/WebVideo/Annotations/wiki/Format_mapping_review</a></p>
|
|
|
|
<p class="phone"><cite>thierry:</cite> needs to be more complex to cover
|
|
several files for a format<br />
|
|
... have several lines per format<br />
|
|
... will ask silvia for example file again<br />
|
|
... apple will provide files, maybe they need help with rdf</p>
|
|
|
|
<p class="phone"><cite>pchampin:</cite> question regarding similar/related
|
|
properties<br />
|
|
... as examples are going to be used in test cases<br />
|
|
... people would expect their implementations to produce the same RDF<br />
|
|
... but nothing is specified for related properties or values of subtypes<br />
|
|
... subtypes are on purpose unspecified<br />
|
|
... so other implementations might not exactly comply with these examples when
|
|
implementations make other choices<br />
|
|
... makes automatic comparison against example files impossible</p>
|
|
|
|
<p class="irc"><<cite>pchampin</cite>> well, not impossible, but
|
|
tricky</p>
|
|
|
|
<p class="phone">use the same set of examples image, video) for all formats</p>
|
|
|
|
<p class="phone"><cite>thierry:</cite> use a few resources and then convert to
|
|
different formats</p>
|
|
|
|
<p class="irc"><<cite>jsderber</cite>> yes</p>
|
|
|
|
<h3 id="item05">next f2f</h3>
|
|
|
|
<p class="phone"><cite>proposed:</cite> june 28-29, sophia, france</p>
|
|
|
|
<p class="phone">[adjourned]</p>
|
|
|
|
<p class="irc"><<cite>mcsuarez</cite>> bye</p>
|
|
</div>
|
|
|
|
<h2><a name="ActionSummary" id="ActionSummary">Summary of Action Items</a></h2>
|
|
<!-- Action Items -->
|
|
[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/03/01 17:40:19 $
|
|
</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)
|
|
|
|
Succeeded: s/eg/use the same set of examples /
|
|
Found Scribe: wbailer
|
|
Inferring ScribeNick: wbailer
|
|
Present: joakim mari-carmen thierry werner pierre-antoine
|
|
Regrets: felix jean-pierre florian
|
|
Got date from IRC log name: 01 Mar 2011
|
|
Guessing minutes URL: <a href="http://www.w3.org/2011/03/01-mediaann-minutes.html">http://www.w3.org/2011/03/01-mediaann-minutes.html</a>
|
|
People with action items: </pre>
|
|
[End of <a
|
|
href="http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm">scribe.perl</a>
|
|
diagnostic output] </div>
|
|
</body>
|
|
</html>
|