See also: IRC log
<JS> Hello
<scribe> scribe: Thierry
<Vero> http://www.w3.org/2010/10/12-mediaann-minutes.html
Propose to accept previous minutes
http://www.w3.org/2010/10/05-mediaann-minutes.html
no objections
no telecon on tuesday during TPAC as we meet on Thrusday and friday
<Joakim> having problem to call bridge again: +33.4.26.46.79.03
close ACTION-223
<trackbot> ACTION-223 Check for overlap between html5 and mawg issues closed
close ACTION-265
<trackbot> ACTION-265 Make a review of media fragments LC doc closed
<scribe> closed ACTION-269
close ACTION-280
<trackbot> ACTION-280 Check the normative parts of the document according to comment 2418 closed
open ACTION-280
reopen ACTION-280
<trackbot> ACTION-280 Check the normative parts of the document according to comment 2418 re-opened
reopen ACTION-283
<trackbot> ACTION-283 Send mail to Geolocation WG for an example, or controlled voca that can be used for the ma:location property re-opened
<Joakim> http://lists.w3.org/Archives/Public/public-media-annotation/2010Oct/0058.html
close ACTION-283
<trackbot> ACTION-283 Send mail to Geolocation WG for an example, or controlled voca that can be used for the ma:location property closed
close ACTION-288
<trackbot> ACTION-288 Unify the XPATH expressions in the mapping tables according to the last substantial comment of Robin closed
<Joakim> no nio
<Joakim> no no
question is accurancy really mandatory?
issue for Daniel was to get some example code to include into our spec
let's wait for geolocation WG response
close ACTION-289
<trackbot> ACTION-289 Deal with the last editorial comment of Robin closed
close ACTION-291
<trackbot> ACTION-291 Put agreed version of ontology to url pointed to by namespace closed
ACTION-293 pending a new version of the property table. raphael should send this new version today
close ACTION-298
<trackbot> ACTION-298 Contact WebIDL for requesting information about the planned direction for the webservices closed
close ACTION-300
<trackbot> ACTION-300 Contact the Geolocation WG and see if they'd be OK to make the accuracy optional closed
close ACTION-303
<trackbot> ACTION-303 Inform the Media Capture WG about our LC document closed
close ACTION-310
<trackbot> ACTION-310 Add hyphens in Java-Script in the figure closed
close ACTION-315
<trackbot> ACTION-315 Update the group web site to reflect the plural in the title and to make working his cvs closed
close ACTION-316
<trackbot> ACTION-316 Pursue development of WebIDL for REST at the Coordination Group meeting closed
reopen ACTION-316
<trackbot> ACTION-316 Pursue development of WebIDL for REST at the Coordination Group meeting re-opened
close ACTION-317
<trackbot> ACTION-317 Ping tobias about reply to media fragments guys comments closed
close ACTION-322
<trackbot> ACTION-322 Send mail to api doc editors to attend call next week closed
close ACTION-323
<trackbot> ACTION-323 Book telecon bridge for api call closed
the LC Comments status is as follows:
=====
Agreed: Commenter approved disposition
******
-- LC Comment -2389 on Media Ontology spec
-- LC Comment -2398 on Media Ontology spec (jose)
-- LC Comment -2403 on Media Ontology spec
-- LC Comment -2404 on Media Ontology spec
-- LC Comment -2410 on Media API spec Jo Rabin
-- LC Comment -2394 on Media API spec (timeless : need to send final draft for review.).
<scribe> On going (response from commenter- partial or no agreement):
***********************************************************
** LC Comment -2393 on Media Ontology spec (deasagree for speex or VP8 and codec)
http://lists.w3.org/Archives/Public/public-media-annotation/2010Sep/0245.html
--> ACTION: Thierry to investigate.
** LC Comment -2405 on Media Ontology spec (Doug)
satisfied by our response but would like to see it in the spec.
Confused by your solution around the "ma" prefix, and would like to
see it in writing.
http://lists.w3.org/Archives/Public/public-media-annotation/2010Oct/0021.html
--> ACTION: Véronique to see with Raphael or Wonsuk about new wording in the spec
** LC Comment -2418 on Media Ontology spec (need to respond to 3 unsolved issues) see to do
http://lists.w3.org/Archives/Public/public-media-annotation/2010Sep/0242.html
--> ACTION: Véronique to investigate 3 unsolved issues
--------------
** LC Comment -2395 on Media API spec(deasagree for speex or VP8 and codec)
http://lists.w3.org/Archives/Public/public-media-annotation/2010Sep/0246.html
--> ACTION: Thierry to investigate.
** LC Comment -2419 on Media API spec (need to respond to unsolved issues)
http://lists.w3.org/Archives/Public/public-media-annotation/2010Sep/0233.html
Proposal from Chris:
http://lists.w3.org/Archives/Public/public-media-annotation/2010Oct/0045.html
--> ACTION: Chris to investigate unsolved issues)
** LC Comment -2406 on Media API spec (Doug)
Should discuus this further with Doug during a telecon. Doug should provide Scenario. Doug kind of agree ... should make this statement more clear.
LC Comment -2405 is almost done. We have resolve the intro and dublin core issue in the latest draft
http://lists.w3.org/Archives/Public/public-media-annotation/2010Oct/0054.html
werner Also I don't understand his conclusion.
he says we have many
details for video formats, which is not true also.
PCM is practically uncompresssed
but all the audio
format parameters seem to assume that audio will be accessed in PCM
format such as audio/L16
not sure were this comes from ?
1 - we don't know how he comes to this conclusion about
2 size of a video 8 bits per channel is not specified
so there are not so many details for video formats in the Media API spec
LC Comment -2419 on Media API spec (need to respond to unsolved issues)
http://lists.w3.org/Archives/Public/public-media-annotation/2010Sep/0233.html
Proposal from Chris:
http://lists.w3.org/Archives/Public/public-media-annotation/2010Oct/0045.html
All to review Chris proposal
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: tmichel Found Scribe: Thierry WARNING: Dash separator lines found. If you intended them to mark the start of a new topic, you need the -dashTopics option. For example: <Philippe> --- <Philippe> Review of Action Items Default Present: +1.201.807.aaaa, wbailer, MarkA, tmichel, joakim Present: +1.201.807.aaaa wbailer MarkA tmichel joakim WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting Got date from IRC log name: 12 Oct 2010 Guessing minutes URL: http://www.w3.org/2010/10/12-mediaann-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]