Another abandoned server code base... this is kind of an ancestor of taskrambler.
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.
 
 
 
 
 
 

509 lines
19 KiB

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang='en' xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<meta name="generator" content=
"HTML Tidy for Linux (vers 6 November 2007), see www.w3.org" />
<title>MAWG Telco -- 05 Oct 2010</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="MAWG Telco" 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>MAWG Telco</h1>
<h2>05 Oct 2010</h2>
<p>See also: <a href=
"http://www.w3.org/2010/10/05-mediaann-irc">IRC log</a></p>
<h2><a name="attendees" id="attendees">Attendees</a></h2>
<div class="intro">
<dl>
<dt>Present</dt>
<dd>doug, thierry, joakim, werner, daniel, (irc),
veronique</dd>
<dt>Regrets</dt>
<dd>florian, felix, wonsuk, raphael</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">previous minutes</a></li>
<li><a href="#item02">next meeting</a></li>
<li><a href="#item03">comments from doug</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>shepazu</cite>&gt; hi, tmichel, I've
sent in my responses, and I can join the MAWG telcon today (in
a few minutes, right?)</p>
<p class='irc'>&lt;<cite>shepazu</cite>&gt; tmichel?</p>
<p class='irc'>&lt;<cite>joakim</cite>&gt; <a href=
"http://www.w3.org/2010/10/05-mediaann-minutes.html">http://www.w3.org/2010/10/05-mediaann-minutes.html</a></p>
<p class='irc'>&lt;<cite>joakim</cite>&gt; <a href=
"http://www.w3.org/2010/09/28-mediaann-minutes.html">http://www.w3.org/2010/09/28-mediaann-minutes.html</a></p>
<p class='irc'>&lt;<cite>scribe</cite>&gt; scribenick:
wbailer</p>
<h3 id="item01">previous minutes</h3>
<p class='phone'>accepted</p>
<h3 id="item02">next meeting</h3>
<p class='phone'>schedules for oct. 12</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; Hello Doug</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; no one from the API
team ...</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; too bad we had Doug
today ...</p>
<h3 id="item03">comments from doug</h3>
<p class='irc'>&lt;<cite>shepazu</cite>&gt; <a href=
"http://www.w3.org/TR/2010/WD-mediaont-api-1.0-20100608/">http://www.w3.org/TR/2010/WD-mediaont-api-1.0-20100608/</a></p>
<p class='phone'><cite>doug:</cite> make sure to look at right
version<br />
... previous comment still holds for the current version<br />
... don't think that browser vendors will implement all the 32
interfaces in the spec</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; LC comment from
Doug</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; <a href=
"http://www.w3.org/2006/02/lc-comments-tracker/42786/WD-mediaont-api-1.0-20100608/2406">
http://www.w3.org/2006/02/lc-comments-tracker/42786/WD-mediaont-api-1.0-20100608/2406</a></p>
<p class='phone'><cite>doug:</cite> approach is very java-like,
very verbose, strongly typed<br />
... same solution as proposed at last tpac an even before group
started: only 1 or 2 methods only for getting metadata<br />
... generic methods instead of typed interfaces</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; should have only
one ot two methods allowing to get the metadata generecly</p>
<p class='phone'><cite>doug:</cite> there is generic
getProperty, but different interfaces for return types</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; doug: what is the
goal of all these interfaces ?</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; Doug: I was
confused, with earlier draft. But now it seems fine.</p>
<p class='phone'><cite>doug:</cite> specific return types are
not necessary<br />
... to get data in a generic way will not work with strongly
typed return types<br />
... it's more java and not usual for javascript developers used
to json structures<br />
... could be name value pairs<br />
... should not be described as interfaces<br />
... generic json style object should be the goal<br />
... dicussion on filtering results at last tpac<br />
... eg getting all titles, filter for subtitles, episode titles
etc<br />
... or filter for certain format<br />
... not sure how to do that with a generic array<br />
... document states its for both client and server side
use<br />
... not clear how it could be used on a server</p>
<p class='phone'><cite>joakim:</cite> api exposed as web
service, to be called from client</p>
<p class='phone'><cite>doug:</cite> shared ontology is
useful<br />
... not sure if designing for both client and server is good
approach<br />
... focus on client<br />
... metadata for media file can be remote<br />
... important to clarify what is meant by the interfaces<br />
... should clarify that people are not expected to implemented
multiple different interfaces</p>
<p class='phone'><cite>joakim:</cite> there are 3
questions:</p>
<p class='phone'>1. what is meant by interfaces</p>
<p class='phone'>2. less strong typing of return types</p>
<p class='phone'>3. filtering results by subproperties</p>
<p class='phone'><cite>doug:</cite> if you do not talk about
interfaces, the question of whether all need to be implemented
disappears<br />
... if application supports ontology, it should be possible to
retrieve all the values<br />
... are there properties that there are more problematic than
others?</p>
<p class='phone'><cite>joakim:</cite> here is an example for
title in 3.5.2.1<br />
... returning a specific subtype of title</p>
<p class='phone'><cite>doug:</cite> json format as return
format would make things easier to understand<br />
... need to look more closely to this</p>
<p class='phone'><cite>joakim:</cite> could you propose an
example?</p>
<p class='phone'><cite>doug:</cite> json looks ok, but maybe
not with a more complex example<br />
... makes more sense to have a json style repsonse format<br />
... plan to talk to Cameron McCormack about whether is the
correct use of webidl for this purpose<br />
... scenario: mp3 with album title, song title, annotations in
id3<br />
... plus annotations in xmp with the 2 titles<br />
... expect to get 4 titles, 2 from id3, 2 from xmp<br />
... expect to be able to filter to just get the xmp<br />
... in addition, get creation date of metadata and author of
metadata<br />
... using same set of properties for meta-metadata seems to be
solution</p>
<p class='phone'>needs to be described in the document</p>
<p class='phone'><cite>doug:</cite> each piece has to contain
where it comes from<br />
... either on the high-level structure or as a nested
structure<br />
... on high-level, it would be useful to all titles and
authors<br />
... but to filter by annotation, and not go down to specific
properties and then filter<br />
... meta-metadata should be part of return data<br />
... rather than overloading getProperty, return values first
and filter results<br />
... append filters to narrow results</p>
<p class='irc'>&lt;<cite>joakim</cite>&gt; I was thrown out
from zakim</p>
<p class='phone'><cite>doug:</cite> will draw up a few
scenarios, and put together what I expect the api to return</p>
<p class='phone'><cite>joakim:</cite> people at sony ericsson
were interested in having provenance of metadata</p>
<p class='phone'><cite>doug:</cite> would like to talk to
browser vendors more deeply, not sure if possible in time<br />
... currently not sure that all common use case are covered by
the api<br />
... will draw up scenario and wg to decide whether its covered
by the spec</p>
<p class='phone'><cite>thierry:</cite> set up specific telecon
with api doc editors and doug at a time more convenient for
doug<br />
... possible time tuesday 13:00 utc (15:00 cest)</p>
<p class='phone'><cite>joakim:</cite> anything urgent about LC
status?</p>
<p class='phone'><cite>thierry:</cite> thought about scheduling
2nd LC, in order to manage before tpac<br />
... seems very difficult to achieve<br />
... goal should be to finalise docs a tpac</p>
<p class='irc'>&lt;<cite>daniel</cite>&gt; I think we may can
not catch up the proposed schedule. There are still so many
open issues...</p>
<p class='phone'><cite>thierry:</cite> to avoid 3rd LC<br />
... before tpac we should have a good idea what has already
implemented from lc comments<br />
... some commenters want to see editors draft</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; LC Comments</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; =====</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; Agreed: Commenter
approved disposition</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; ******</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; -- LC Comment -2389
on Media Ontology spec</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; -- LC Comment -2403
on Media Ontology spec</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; -- LC Comment -2404
on Media Ontology spec</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; -- LC Comment -2410
on Media API spec Jo Rabin</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; On going:</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; *********</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; * LC Comment -2394
on Media API spec (timeless :need to read more-travelling)</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; ** LC Comment -2419
on Media API spec (need to respond to unsolved issues)</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; <a href=
"http://lists.w3.org/Archives/Public/public-media-annotation/2010Sep/0243.html">
http://lists.w3.org/Archives/Public/public-media-annotation/2010Sep/0243.html</a></p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; ** LC Comment -2418
on Media Ontology spec (need to respond to 3 unsolved issues)
see to do</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; <a href=
"http://lists.w3.org/Archives/Public/public-media-annotation/2010Sep/0242.html">
http://lists.w3.org/Archives/Public/public-media-annotation/2010Sep/0242.html</a></p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; * LC Comment -2393
on Media Ontology spec (deasagree for speex or VP8 and
codec)</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; * LC Comment -2395
on Media API spec(deasagree for speex or VP8 and codec)</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; * LC Comment -2394
on Media API spec (Doug)</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; <a href=
"http://lists.w3.org/Archives/Public/public-media-annotation/2010Oct/0020.html">
http://lists.w3.org/Archives/Public/public-media-annotation/2010Oct/0020.html</a></p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; Doug kind of agree
... should make this statement more clear.</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; LC Comment -2405 on
Media Ontology spec (Doug)</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; satisfied by our
response but would like to see it in the spec.</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; Confused by your
solution around the "ma" prefix, and would like to</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; see it in
writing.</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; ---------</p>
<p class='phone'><cite>thierry:</cite> we have comments with
disagreement for commenters</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; No response
yet:</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; ************</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; LC Comment -2398 on
Media Ontology spec (jose)</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; LC Comment -2411 on
Media Ontology spec (Karen)</p>
<p class='irc'>&lt;<cite>tmichel</cite>&gt; LC Comment -2414 on
Media Ontology spec (Pling)</p>
<p class='phone'><cite>thierry:</cite> shall we ask person who
drafted original repsonse to look into this?</p><a name=
"action01" id="action01"></a>
<p class='irc'>&lt;<cite>scribe</cite>&gt;
<strong>ACTION:</strong> chris to respond to unsolved issues of
lc 2419 [recorded in <a href=
"http://www.w3.org/2010/10/05-mediaann-minutes.html#action01">http://www.w3.org/2010/10/05-mediaann-minutes.html#action01</a>]</p>
<p class='irc'>&lt;<cite>trackbot</cite>&gt; Created ACTION-318
- Respond to unsolved issues of lc 2419 [on Chris Poppe - due
2010-10-12].</p><a name="action02" id="action02"></a>
<p class='irc'>&lt;<cite>scribe</cite>&gt;
<strong>ACTION:</strong> thierry to draft repsonse to open
issues in lc 2395 [recorded in <a href=
"http://www.w3.org/2010/10/05-mediaann-minutes.html#action02">http://www.w3.org/2010/10/05-mediaann-minutes.html#action02</a>]</p>
<p class='irc'>&lt;<cite>trackbot</cite>&gt; Created ACTION-319
- Draft repsonse to open issues in lc 2395 [on Thierry Michel -
due 2010-10-12].</p><a name="action03" id="action03"></a>
<p class='irc'>&lt;<cite>scribe</cite>&gt;
<strong>ACTION:</strong> veronique to draft response for open
issues in lc 2418 [recorded in <a href=
"http://www.w3.org/2010/10/05-mediaann-minutes.html#action03">http://www.w3.org/2010/10/05-mediaann-minutes.html#action03</a>]</p>
<p class='irc'>&lt;<cite>trackbot</cite>&gt; Sorry, couldn't
find user - veronique</p><a name="action04" id="action04"></a>
<p class='irc'>&lt;<cite>scribe</cite>&gt;
<strong>ACTION:</strong> thierry to draft repsonse for open
issues in lc 2392 [recorded in <a href=
"http://www.w3.org/2010/10/05-mediaann-minutes.html#action04">http://www.w3.org/2010/10/05-mediaann-minutes.html#action04</a>]</p>
<p class='irc'>&lt;<cite>trackbot</cite>&gt; Created ACTION-321
- Draft repsonse for open issues in lc 2392 [on Thierry Michel
- due 2010-10-12].</p>
<p class='phone'><cite>veronique:</cite> update of 2405 needs
to be done after syntax update<br />
... also update on normative/non-normative is required (action
in joakim)</p>
<p class='phone'><cite>joakim:</cite> next week normal telecon,
then api telecom</p><a name="action05" id="action05"></a>
<p class='irc'>&lt;<cite>scribe</cite>&gt;
<strong>ACTION:</strong> joakim to send mail to api doc editors
to attend call next week [recorded in <a href=
"http://www.w3.org/2010/10/05-mediaann-minutes.html#action05">http://www.w3.org/2010/10/05-mediaann-minutes.html#action05</a>]</p>
<p class='irc'>&lt;<cite>trackbot</cite>&gt; Created ACTION-322
- Send mail to api doc editors to attend call next week [on
Joakim Söderberg - due 2010-10-12].</p><a name="action06" id=
"action06"></a>
<p class='irc'>&lt;<cite>scribe</cite>&gt;
<strong>ACTION:</strong> thierry to book telecon bridge for api
call [recorded in <a href=
"http://www.w3.org/2010/10/05-mediaann-minutes.html#action06">http://www.w3.org/2010/10/05-mediaann-minutes.html#action06</a>]</p>
<p class='irc'>&lt;<cite>trackbot</cite>&gt; Created ACTION-323
- Book telecon bridge for api call [on Thierry Michel - due
2010-10-12].</p>
<p class='phone'>[adjourned]</p>
</div>
<h2><a name="ActionSummary" id="ActionSummary">Summary of Action
Items</a></h2><!-- Action Items -->
<strong>[NEW]</strong> <strong>ACTION:</strong> chris to respond
to unsolved issues of lc 2419 [recorded in <a href=
"http://www.w3.org/2010/10/05-mediaann-minutes.html#action01">http://www.w3.org/2010/10/05-mediaann-minutes.html#action01</a>]<br />
<strong>[NEW]</strong> <strong>ACTION:</strong> joakim to send
mail to api doc editors to attend call next week [recorded in
<a href=
"http://www.w3.org/2010/10/05-mediaann-minutes.html#action05">http://www.w3.org/2010/10/05-mediaann-minutes.html#action05</a>]<br />
<strong>[NEW]</strong> <strong>ACTION:</strong> thierry to book
telecon bridge for api call [recorded in <a href=
"http://www.w3.org/2010/10/05-mediaann-minutes.html#action06">http://www.w3.org/2010/10/05-mediaann-minutes.html#action06</a>]<br />
<strong>[NEW]</strong> <strong>ACTION:</strong> thierry to draft
repsonse for open issues in lc 2392 [recorded in <a href=
"http://www.w3.org/2010/10/05-mediaann-minutes.html#action04">http://www.w3.org/2010/10/05-mediaann-minutes.html#action04</a>]<br />
<strong>[NEW]</strong> <strong>ACTION:</strong> thierry to draft
repsonse to open issues in lc 2395 [recorded in <a href=
"http://www.w3.org/2010/10/05-mediaann-minutes.html#action02">http://www.w3.org/2010/10/05-mediaann-minutes.html#action02</a>]<br />
<strong>[NEW]</strong> <strong>ACTION:</strong> veronique to
draft response for open issues in lc 2418 [recorded in <a href=
"http://www.w3.org/2010/10/05-mediaann-minutes.html#action03">http://www.w3.org/2010/10/05-mediaann-minutes.html#action03</a>]<br />
&nbsp;<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: 2010/10/05 12:05:39 $
</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)
Found ScribeNick: wbailer
Inferring Scribes: wbailer
WARNING: Dash separator lines found. If you intended them to mark
the start of a new topic, you need the -dashTopics option.
For example:
&lt;Philippe&gt; ---
&lt;Philippe&gt; Review of Action Items
Default Present: Doug_Schepers, joakim, wbailer, +1.201.807.aaaa, +39.538.5.aabb, vero
Present: doug thierry joakim werner daniel (irc) veronique
Regrets: florian felix wonsuk raphael
Got date from IRC log name: 05 Oct 2010
Guessing minutes URL: <a href=
"http://www.w3.org/2010/10/05-mediaann-minutes.html">http://www.w3.org/2010/10/05-mediaann-minutes.html</a>
People with action items: chris joakim thierry veronique
</pre>[End of <a href=
"http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm">
scribe.perl</a> diagnostic output]
</div>
</body>
</html>