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.
749 lines
25 KiB
749 lines
25 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>SV_MEETING_TITLE -- 21 Dec 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="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>- DRAFT -</h1>
|
|
|
|
<h1>SV_MEETING_TITLE</h1>
|
|
|
|
<h2>21 Dec 2010</h2>
|
|
|
|
<p>See also: <a href=
|
|
"http://www.w3.org/2010/12/21-mediaann-irc">IRC log</a></p>
|
|
|
|
<h2><a name="attendees" id="attendees">Attendees</a></h2>
|
|
|
|
<div class="intro">
|
|
<dl>
|
|
<dt>Present</dt>
|
|
|
|
<dt>Regrets</dt>
|
|
|
|
<dt>Chair</dt>
|
|
|
|
<dd>SV_MEETING_CHAIR</dd>
|
|
|
|
<dt>Scribe</dt>
|
|
|
|
<dd>pchampin</dd>
|
|
</dl>
|
|
</div>
|
|
|
|
<h2>Contents</h2>
|
|
|
|
<ul>
|
|
<li>
|
|
<a href="#agenda">Topics</a>
|
|
|
|
<ol>
|
|
<li><a href="#item01">administrative</a></li>
|
|
|
|
<li><a href="#item02">open action items</a></li>
|
|
|
|
<li><a href="#item03">changes in the ontology document
|
|
proposed by the RDF taskforce</a></li>
|
|
|
|
<li><a href="#item04">Follow up on Implementation of LC
|
|
comments</a></li>
|
|
|
|
<li><a href="#item05">continuation of the group</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'>I'll scribe</p>
|
|
|
|
<p class='irc'><<cite>scribe</cite>> scribe: pchampin</p>
|
|
|
|
<h3 id="item01">administrative</h3>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> next telecon
|
|
meeting is the 11th January</p>
|
|
|
|
<p class='phone'><cite>joakim:</cite> next meeting proposed on
|
|
2011-01-11</p>
|
|
|
|
<p class='irc'><<cite>joakim</cite>> <a href=
|
|
"http://www.w3.org/2010/11/30-mediaann-minutes.html">http://www.w3.org/2010/11/30-mediaann-minutes.html</a></p>
|
|
|
|
<p class='phone'><cite>joakim:</cite> minutes approved for the
|
|
last meeting</p>
|
|
|
|
<h3 id="item02">open action items</h3>
|
|
|
|
<p class='phone'>close action-269</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> ACTION-269 Report
|
|
about "library to extract test cases for JavaScript" at next
|
|
call closed</p>
|
|
|
|
<p class='phone'><cite>joakim:</cite> wonsuk, about action 309
|
|
?</p>
|
|
|
|
<p class='irc'><<cite>wonsuk</cite>> That is not
|
|
done.</p>
|
|
|
|
<p class='irc'><<cite>wonsuk</cite>> please keep it
|
|
open.</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> wonsuk are you on
|
|
Zakim ?</p>
|
|
|
|
<p class='phone'>close action-309</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> ACTION-309 Improve
|
|
markup of nomative/informative, probably with specific class to
|
|
visualise closed</p>
|
|
|
|
<p class='irc'><<cite>wonsuk</cite>> no... I will be on
|
|
the Zakim ;)</p>
|
|
|
|
<p class='phone'><cite>joakim:</cite> wonsuk, about action
|
|
328?</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> ACTION-328 wonsuk
|
|
?</p>
|
|
|
|
<p class='irc'><<cite>wonsuk</cite>> That was done.</p>
|
|
|
|
<p class='phone'>close action-328</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> ACTION-328 Check
|
|
if comment 2389 is in the document closed</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> ACTION-334</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> leave open</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> ACTION-337 wonsuk
|
|
again</p>
|
|
|
|
<p class='phone'><cite>joakim:</cite> wonsuk, about action
|
|
337?</p>
|
|
|
|
<p class='irc'><<cite>wonsuk</cite>> That has been
|
|
done.</p>
|
|
|
|
<p class='phone'>close action-337</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> ACTION-337 Check
|
|
if comment 2405 is in the document closed</p>
|
|
|
|
<p class='phone'><cite>joakim:</cite> no report on action 343
|
|
for Daniel, leave it open<br />
|
|
... wonsuk, about action 351 ?</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> ACTION-348 done</p>
|
|
|
|
<p class='phone'><cite>wonsuk:</cite> 351 has been done</p>
|
|
|
|
<p class='phone'>close action-351</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> ACTION-351 Change
|
|
"issuer of classification" to "classification scheme" in Onto
|
|
and API documents closed</p>
|
|
|
|
<p class='phone'><cite>joakim:</cite> what about 356?</p>
|
|
|
|
<p class='irc'><<cite>msuaref</cite>> hi</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> ACTION-348 NOT
|
|
done</p>
|
|
|
|
<p class='phone'><cite>wonsuk:</cite> as I wrote in my e-mail,
|
|
I missed the point of that action</p>
|
|
|
|
<p class='irc'><<cite>stegmai</cite>> <a href=
|
|
"http://lists.w3.org/Archives/Public/public-media-annotation/2010Dec/0069.html">
|
|
http://lists.w3.org/Archives/Public/public-media-annotation/2010Dec/0069.html</a></p>
|
|
|
|
<p class='phone'><cite>joakim:</cite> I think this was raise by
|
|
Jean-Pierre at the F2F in Lyon</p>
|
|
|
|
<p class='phone'><cite>jean-pierre:</cite> we had this
|
|
discussion about the RDF ontology</p>
|
|
|
|
<p class='phone'><cite>joakim:</cite> I think the conclusion
|
|
was that the text should be rewritten to match the RDF
|
|
representation<br />
|
|
... I think that we said that rating should be more precisely
|
|
defined, to prevent mixing it up with classification</p>
|
|
|
|
<p class='phone'><cite>thierry:</cite> I think wonsuk and
|
|
jean-pierre should coordinate to check/improve the text in the
|
|
ontology document</p>
|
|
|
|
<p class='phone'><cite>jean-pierre:</cite> for me the text is
|
|
ok as is</p>
|
|
|
|
<p class='phone'><cite>joakim:</cite> it seems that the text
|
|
has been updated according to 351</p>
|
|
|
|
<p class='phone'>close action-356</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> ACTION-356 Make
|
|
more precise description of rating in ontology closed</p>
|
|
|
|
<p class='phone'><cite>florian:</cite> action-360 still
|
|
ongoing</p>
|
|
|
|
<p class='phone'><cite>joakim:</cite> action-365 is about one
|
|
particulat issue in LC-2419<br />
|
|
... still open<br />
|
|
... action-368 is also for me, about ma:compression and
|
|
ma:format</p>
|
|
|
|
<p class='phone'><cite>werner:</cite> we had some discussion on
|
|
the list about that<br />
|
|
... the conclusion being: there are two problems with merging
|
|
them<br />
|
|
... 1/ for tracks, you need 'compression', 'format' doesn't
|
|
make sense for them<br />
|
|
... 2/ extended mimetypes are not sufficiently well defined for
|
|
us to rely on them<br />
|
|
... so ma:compression and ma:format were deemed not
|
|
redundant</p>
|
|
|
|
<p class='phone'><cite>joakim:</cite> I can write that down in
|
|
an e-mail and send it on the mailing list<br />
|
|
... next action is action 369<br />
|
|
... keep it open</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> ACTION-372 Wonsuk
|
|
?</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> CVS updated. Please
|
|
close</p>
|
|
|
|
<p class='phone'>close action-372</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> ACTION-372 Upload
|
|
veronique's version to CVS closed</p>
|
|
|
|
<p class='irc'><<cite>chpoppe</cite>> Here is the last
|
|
version of the API doc</p>
|
|
|
|
<p class='irc'><<cite>chpoppe</cite>> <a href=
|
|
"http://dev.w3.org/2008/video/mediaann/mediaont-api-1.0/mediaont-api-1.0.html">
|
|
http://dev.w3.org/2008/video/mediaann/mediaont-api-1.0/mediaont-api-1.0.html</a></p>
|
|
|
|
<p class='phone'><cite>florian:</cite> misunderstood action373,
|
|
will do it for the next telecon</p>
|
|
|
|
<p class='phone'><cite>joakim:</cite> next is action 375, to
|
|
Véronique<br />
|
|
... no repporting, we leave it open</p>
|
|
|
|
<p class='irc'><<cite>chpoppe</cite>> action 374 is
|
|
done</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> Sorry, couldn't
|
|
find user - 374</p>
|
|
|
|
<p class='phone'><cite>joakim:</cite> next actions were created
|
|
at the last telecon because we lacked reviews</p>
|
|
|
|
<p class='phone'><cite>florian:</cite> 377 is done</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> close 377</p>
|
|
|
|
<p class='phone'>close action-377</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> ACTION-377 Review
|
|
LC2393 closed</p>
|
|
|
|
<p class='irc'><<cite>chpoppe</cite>> you can also close
|
|
action 374</p>
|
|
|
|
<p class='phone'><cite>werner:</cite> 378 is done too; some
|
|
change should be done in the API document<br />
|
|
... explaining what "no exception" means</p>
|
|
|
|
<p class='phone'>close action-374</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> ACTION-374 Change
|
|
createdate to creationdate in the api doc closed</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> missing text to be
|
|
added in the API for LC 2395</p>
|
|
|
|
<p class='phone'>close action-378</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> ACTION-378 Review
|
|
LC 2395 closed</p>
|
|
|
|
<p class='phone'><cite>felix:</cite> action 380 is done</p>
|
|
|
|
<p class='phone'>close action-380</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> ACTION-380 Review
|
|
LC 2406 closed</p>
|
|
|
|
<p class='irc'><<cite>fsasaki</cite>> felix: comment
|
|
looks good to me</p>
|
|
|
|
<p class='phone'>action chris to add missing text in the API
|
|
document for LC 2395 (about "no exception")</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> Created ACTION-382
|
|
- Add missing text in the API document for LC 2395 (about "no
|
|
exception") [on Chris Poppe - due 2010-12-28].</p>
|
|
|
|
<h3 id="item03">changes in the ontology document proposed by
|
|
the RDF taskforce</h3>
|
|
|
|
<p class='phone'><cite>jean-pierre:</cite> we proposed to add
|
|
track as a sub-class of fragment<br />
|
|
... unless we consider that having a 'number of tracks' is
|
|
enough</p>
|
|
|
|
<p class='phone'><cite>werner:</cite> I think the definitions
|
|
we have is sufficient<br />
|
|
... the definition of fragments refers to the Media Fragment
|
|
definition, which includes track fragments</p>
|
|
|
|
<p class='phone'><cite>jean-pierre:</cite> fine with me<br />
|
|
... next item is about captionning track<br />
|
|
... we only have the notion of caption, but not 'sign
|
|
language'<br />
|
|
... suggest to add it as an example<br />
|
|
... and we would add it as a subclass of Track in the RDF
|
|
ontology</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> I am fine with
|
|
adding signing ...</p>
|
|
|
|
<p class='phone'><cite>felix:</cite> one piece of
|
|
information<br />
|
|
... in a language identifier, sign language can be
|
|
identified</p>
|
|
|
|
<p class='phone'><cite>jean-pierre:</cite> there are two
|
|
things: the language and the purpose</p>
|
|
|
|
<p class='phone'><cite>felix:</cite> sign language is defined
|
|
just as one kind of language<br />
|
|
... so I'm not sure whether we need a distinction here</p>
|
|
|
|
<p class='phone'><cite>jean-pierre:</cite> at least this should
|
|
be mentionned in the 'language' definition then</p>
|
|
|
|
<p class='irc'><<cite>fsasaki</cite>> <a href=
|
|
"http://people.w3.org/rishida/utils/subtags/index.php?find=sign+language&submit=Find">
|
|
http://people.w3.org/rishida/utils/subtags/index.php?find=sign+language&submit=Find</a></p>
|
|
|
|
<p class='phone'><cite>werner:</cite> a caption track with a
|
|
sign language as its language would be strange</p>
|
|
|
|
<p class='phone'><cite>jean-pierre:</cite> there are several
|
|
options</p>
|
|
|
|
<p class='irc'><<cite>fsasaki</cite>> see the above link
|
|
for sign language sub tags, which are "normal" language sub
|
|
tags</p>
|
|
|
|
<p class='phone'><cite>jean-pierre:</cite> 1/ the signing is
|
|
embeded in the video, so there are actually two languages<br />
|
|
... 2/ the signing is an external file</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> ma:language add
|
|
sign languages</p>
|
|
|
|
<p class='phone'><cite>pierre-antoine:</cite> think that we
|
|
should make this explicit in the definition of
|
|
'ma:language'</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> ma:numTracks add
|
|
signing as example.</p>
|
|
|
|
<p class='phone'>action felix to write an addition to the
|
|
definition of ma:language to mention sign language</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> Created ACTION-383
|
|
- Write an addition to the definition of ma:language to mention
|
|
sign language [on Felix Sasaki - due 2010-12-28].</p>
|
|
|
|
<p class='phone'><cite>jean-pierre:</cite> another problem is
|
|
that we can not express the *purpose* of a captionning
|
|
track</p>
|
|
|
|
<p class='phone'><cite>pierre-antoine:</cite> the relation
|
|
between a media resource and its track could carry this
|
|
information</p>
|
|
|
|
<p class='phone'><cite>werner:</cite> agrees that relation
|
|
could be used; the same issues appears elsewhere</p>
|
|
|
|
<p class='phone'><cite>jean-pierre:</cite> I'll illustrated
|
|
this with an example<br />
|
|
... e.g. "translation", "audio description"</p>
|
|
|
|
<p class='phone'><cite>joakim:</cite> it would be good to
|
|
include them in the ontology document</p>
|
|
|
|
<p class='irc'><<cite>msuaref</cite>> I also agrees on
|
|
using the relations (in some way) to this issue</p>
|
|
|
|
<p class='phone'><cite>jean-pierre:</cite> next point:
|
|
creationDate is not the most general date property<br />
|
|
... and other dates (like "release date") are not really
|
|
subproperties of *creation* date</p>
|
|
|
|
<p class='phone'><cite>joakim:</cite> I think we discussed this
|
|
issue in Barcelona,</p>
|
|
|
|
<p class='irc'><<cite>joakim</cite>> Do you agree that we
|
|
should change ma:creationDate to ma:Date?</p>
|
|
|
|
<p class='irc'><<cite>chpoppe</cite>> I have no objection
|
|
if the type can be used to specify the exact semantics of the
|
|
date</p>
|
|
|
|
<p class='phone'><cite>joakim:</cite> though I don't remember
|
|
why we settled on creation data</p>
|
|
|
|
<p class='phone'><cite>werner:</cite> I think we found that
|
|
creationDate was more specific<br />
|
|
... and all our examples were related to creation date</p>
|
|
|
|
<p class='irc'><<cite>stegmai</cite>> +1 werner</p>
|
|
|
|
<p class='irc'><<cite>joakim</cite>> +1</p>
|
|
|
|
<p class='phone'><cite>werner:</cite> we didn't have qualifier
|
|
at the time, but now that we have, why not make it more
|
|
general</p>
|
|
|
|
<p class='phone'>+1</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> +1</p>
|
|
|
|
<p class='irc'><<cite>chpoppe</cite>> so I change
|
|
creationdate to date in the API doc?</p>
|
|
|
|
<p class='irc'><<cite>joakim</cite>> Resoultion: change
|
|
ma:creationDate to ma:date</p>
|
|
|
|
<p class='phone'><cite>thierry:</cite> this makes action 375
|
|
obsolete</p>
|
|
|
|
<p class='phone'>close action-375</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> ACTION-375 Change
|
|
createdate to creationdate in the ontology doc closed</p>
|
|
|
|
<p class='phone'>action wonsuk to change creationDate to
|
|
date</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> Created ACTION-384
|
|
- Change creationDate to date [on WonSuk Lee - due
|
|
2010-12-28].</p>
|
|
|
|
<p class='phone'><cite>jean-pierre:</cite> next point was about
|
|
rating values as float<br />
|
|
... it is still double in the ontology document</p>
|
|
|
|
<p class='irc'><<cite>chpoppe</cite>> the ontology
|
|
document has not been updated</p>
|
|
|
|
<p class='irc'><<cite>joakim</cite>> Resolution: change
|
|
ma:creationDate to ma:date</p>
|
|
|
|
<p class='irc'><<cite>chpoppe</cite>> I think that
|
|
Veronique has problems with accessing the cvs or something</p>
|
|
|
|
<p class='irc'><<cite>chpoppe</cite>> in the API it is
|
|
float</p>
|
|
|
|
<p class='phone'><cite>pchampin:</cite> the ontology document
|
|
only uses double</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> RatingValue should
|
|
be Double</p>
|
|
|
|
<p class='phone'><cite>pchampin:</cite> while the API document
|
|
sometimes uses float, sometimes double<br />
|
|
... unless there is a good reason to mix them, I suggest the
|
|
API sticks to double, just like the ontology document</p>
|
|
|
|
<p class='irc'><<cite>chpoppe</cite>> the API only uses
|
|
double for the location</p>
|
|
|
|
<p class='irc'><<cite>chpoppe</cite>> latitude, longitude
|
|
and altitude</p>
|
|
|
|
<p class='irc'><<cite>chpoppe</cite>> I can change the
|
|
value of the rating to double</p>
|
|
|
|
<p class='irc'><<cite>joakim</cite>> +1</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> language and
|
|
compression will allow string and anyURI values.</p>
|
|
|
|
<p class='phone'>action chris to change float to double in the
|
|
API document</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> Created ACTION-385
|
|
- Change float to double in the API document [on Chris Poppe -
|
|
due 2010-12-28].</p>
|
|
|
|
<p class='phone'>action jean-pierre to change float to double
|
|
in the RDF ontology</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> Created ACTION-386
|
|
- Change float to double in the RDF ontology [on Jean-Pierre
|
|
EVAIN - due 2010-12-28].</p>
|
|
|
|
<p class='irc'><<cite>joakim</cite>> Resolution: use
|
|
double everywhere</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> Ontology does not
|
|
need updates : we keep Double.</p>
|
|
|
|
<p class='phone'><cite>jean-pierre:</cite> last point: language
|
|
and compression only allow string as value; we suggest to allow
|
|
URIs</p>
|
|
|
|
<p class='phone'><cite>joakim:</cite> sounds like a good
|
|
idea</p>
|
|
|
|
<p class='phone'><cite>pchampin:</cite> +1</p>
|
|
|
|
<p class='irc'><<cite>joakim</cite>> any objections?</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> +1</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> I will do it</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> language and
|
|
compression will allow string and anyURI values.</p>
|
|
|
|
<p class='irc'><<cite>wonsuk</cite>> +1</p>
|
|
|
|
<p class='phone'>action tmichel to add URIs as allowed values
|
|
for ma:language and ma:compression</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> Created ACTION-387
|
|
- Add URIs as allowed values for ma:language and ma:compression
|
|
[on Thierry Michel - due 2010-12-28].</p>
|
|
|
|
<p class='phone'><cite>joakim:</cite> can everybody stay
|
|
another 10 minutes?</p>
|
|
|
|
<p class='irc'><<cite>msuaref</cite>> yes</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> extending 10
|
|
minutes ...</p>
|
|
|
|
<h3 id="item04">Follow up on Implementation of LC comments</h3>
|
|
|
|
<p class='phone'><cite>joakim:</cite> thierry will go through
|
|
the mails and see what is still relevant in the comments</p>
|
|
|
|
<p class='phone'><cite>thierry:</cite> should we try to settle
|
|
LC 2405 now?</p>
|
|
|
|
<p class='phone'><cite>jean-pierre:</cite> everything is
|
|
basically in my comment</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>> thanks JP</p>
|
|
|
|
<p class='phone'><cite>joakim:</cite> jean-pierre can you
|
|
propose a text that Wonsuk would add?</p>
|
|
|
|
<p class='irc'><<cite>joakim</cite>> ping Wonsuk!</p>
|
|
|
|
<p class='irc'><<cite>tmichel</cite>>
|
|
WonSUKKKKKKKKKKKKKKK ?</p>
|
|
|
|
<p class='irc'><<cite>chpoppe</cite>> when making updates
|
|
to the ontology please use the latest version on the cvs!</p>
|
|
|
|
<p class='irc'><<cite>joakim</cite>> 1) Introduction Note
|
|
to implementers, content authors - not really explicit, maybe
|
|
these roles should be mentioned saying things like "it is
|
|
expected that implementers will do." ". to the benefit of
|
|
content providers", etc.</p>
|
|
|
|
<p class='irc'><<cite>joakim</cite>> problem 2) There is
|
|
no section 1.1 on the purpose of the specification</p>
|
|
|
|
<p class='irc'><<cite>joakim</cite>> 3) Section 4.1 core
|
|
property definitions -> now section 5.1</p>
|
|
|
|
<p class='irc'><<cite>joakim</cite>> 4) The ma: prefix
|
|
still appears in the table but since the comment was made
|
|
Pierre Antoine, while working on the mapping table suggested
|
|
that the prefix should only be used with the ma-ont namespace
|
|
in the RDF -> reconsider position?</p>
|
|
|
|
<p class='phone'><cite>wonsuk:</cite> I'll update the ontology
|
|
document with respect to these comments</p>
|
|
|
|
<p class='irc'><<cite>chpoppe</cite>> please first get
|
|
the latest version of the ontology document from the cvs
|
|
wonsuk</p>
|
|
|
|
<p class='phone'><cite>pchampin:</cite> another proposal I
|
|
made, regarding Ivan Herman's comments, was to remobe the 'ma:'
|
|
prefix for the 'abstract' ontology<br />
|
|
... only the RDF ontology needs a namespace</p>
|
|
|
|
<p class='irc'><<cite>joakim</cite>> I agree with can
|
|
remove the prefix in the abstract ontology</p>
|
|
|
|
<p class='irc'><<cite>joakim</cite>> werner?</p>
|
|
|
|
<p class='irc'><<cite>joakim</cite>> All agree to remove
|
|
ma: in the abstract ontology?</p>
|
|
|
|
<p class='irc'><<cite>joakim</cite>> including the
|
|
mapping table</p>
|
|
|
|
<p class='irc'><<cite>msuaref</cite>> i also agree on
|
|
removing 'ma:' in the ontology document.</p>
|
|
|
|
<p class='phone'><cite>pchampin:</cite> it can be done
|
|
automatically, I already spotted all the false positives :)</p>
|
|
|
|
<p class='irc'><<cite>joakim</cite>> wonsuk, are you ok
|
|
with removing ma: from the abstract ontology doc?</p>
|
|
|
|
<p class='phone'><cite>pchampin:</cite> I'll send the
|
|
recommendatio on the list again</p>
|
|
|
|
<p class='phone'>action thierry to remove 'ma:' from the
|
|
mapping table</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> Created ACTION-388
|
|
- Remove 'ma:' from the mapping table [on Thierry Michel - due
|
|
2010-12-28].</p>
|
|
|
|
<p class='phone'>action wonsuk to remove 'ma:' from the mapping
|
|
table</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> Created ACTION-389
|
|
- Remove 'ma:' from the mapping table [on WonSuk Lee - due
|
|
2010-12-28].</p>
|
|
|
|
<p class='phone'>action wonsuk to remove 'ma:' from the
|
|
ontology document</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> Created ACTION-390
|
|
- Remove 'ma:' from the ontology document [on WonSuk Lee - due
|
|
2010-12-28].</p>
|
|
|
|
<p class='phone'>close action-389</p>
|
|
|
|
<p class='irc'><<cite>trackbot</cite>> ACTION-389 Remove
|
|
'ma:' from the mapping table closed</p>
|
|
|
|
<h3 id="item05">continuation of the group</h3>
|
|
|
|
<p class='irc'><<cite>joakim</cite>> next year!</p>
|
|
|
|
<p class='irc'><<cite>joakim</cite>> :-)</p>
|
|
|
|
<p class='phone'><cite>florian:</cite> according to the
|
|
charter, the group will end in June 2011<br />
|
|
... what should we do in the meantime</p>
|
|
|
|
<p class='phone'><cite>thierry:</cite> it is unlikely that we
|
|
reach REC by june<br />
|
|
... so we will ask for an extension<br />
|
|
... but during an extension we can not re-chart the group<br />
|
|
... a new charter can be made after the workshop in
|
|
september</p>
|
|
|
|
<p class='phone'><cite>werner:</cite> of course, if we don't
|
|
each REC by june, we should stick to that</p>
|
|
|
|
<p class='phone'><cite>thierry:</cite> getting an extension is
|
|
an easy process</p>
|
|
|
|
<p class='irc'><<cite>scribe</cite>> ... new charter is
|
|
much more complicated</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: 2010/12/21 13:33:32 $
|
|
</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 Scribe: pchampin
|
|
Inferring ScribeNick: pchampin
|
|
|
|
WARNING: No "Present: ... " found!
|
|
Possibly Present: Chris IPcaller Resoultion aabb aacc aadd aaee chpoppe felix florian fsasaki jean-pierre joakim ma msuaref msuarezf pchampin pierre-antoine stegmai thierry tmichel trackbot wbailer werner wonsuk
|
|
You can indicate people for the Present list like this:
|
|
<dbooth> Present: dbooth jonathan mary
|
|
<dbooth> Present+ amy
|
|
|
|
|
|
WARNING: No meeting title found!
|
|
You should specify the meeting title like this:
|
|
<dbooth> Meeting: Weekly Baking Club Meeting
|
|
|
|
|
|
WARNING: No meeting chair found!
|
|
You should specify the meeting chair like this:
|
|
<dbooth> Chair: dbooth
|
|
|
|
Got date from IRC log name: 21 Dec 2010
|
|
Guessing minutes URL: <a href=
|
|
"http://www.w3.org/2010/12/21-mediaann-minutes.html">http://www.w3.org/2010/12/21-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>
|