13:01:29 RRSAgent has joined #mediaann 13:01:29 logging to http://www.w3.org/2009/11/24-mediaann-irc 13:01:38 zakim, mute me 13:01:38 sorry, pchampin, I don't know what conference this is 13:01:46 zakim, this is mawg 13:01:46 ok, wbailer; that matches IA_MAWG()8:00AM 13:01:59 joakim has joined #mediaann 13:02:04 meeting: MAWG 13:02:42 http://www.w3.org/2009/11/17-mediaann-minutes.html 13:02:49 veroniqueM has joined #mediaann 13:03:02 +??P6 13:03:04 scribe: pchampin 13:04:07 topic: approval of last minutes 13:04:27 + +49.851.509.aaff 13:04:31 minutes approved 13:04:39 Zakim, aaff is me 13:04:39 +florian; got it 13:04:59 topic: last call of the requirements document 13:05:16 the last call of the Requirements and used case documents is due to december 13:06:54 Joakim: what is the status of the requirements document? 13:07:44 zakim, who is here? 13:07:45 On the phone I see +329331aaaa, ??P1, +82.10.58.00.aabb, +1.574.905.aacc, +46.1.07.19.aadd, +47.26.9.aaee, ??P6, florian 13:07:47 On IRC I see veroniqueM, joakim, RRSAgent, pchampin, wonsuk, wbailer, tobiasbue, Zakim, daniel, florian, trackbot 13:07:48 I didn't see any critical issues around UC&Req. documents at the previous F2F, so I think we can go to the LC with the current version... 13:08:34 I think that there was someone proposing to add one requirement, but I cannot remember who 13:09:02 and I think that there was also a set of things to change, minor rewritings 13:09:11 who did the last review? 13:09:13 -??P6 13:09:32 Zakim, ??P1 is me 13:09:32 +tobiasbue; got it 13:09:33 Wonsuk: an action item has been added at the Stockolm F2F 13:09:47 on whom? 13:10:25 http://dev.w3.org/2008/video/mediaann/mediaont-req/mediaont-req.html 13:10:59 Joakim: Wonsuk has written a new version and everyone should review it 13:11:30 +??P6 13:12:05 http://www.w3.org/2008/WebVideo/Annotations/track/actions/open 13:13:07 Werner: the result of action 185 (put in Santa Clara) should be included as a requirement 13:13:35 Veronique, di you have time to work on actipn 185? 13:13:40 ... and today's discussion on the mailing list on the adressing of fragents should also be in the requirements 13:13:54 +1 for Werner 13:14:16 ... http://lists.w3.org/Archives/Public/public-media-annotation/2009Nov/0090.html 13:14:18 I did not ask PLING the piece of text, I had understood that they were supposed to provide me with it :) 13:14:25 pchampin: +1 for Werner 13:14:44 Joakim: do the editors agree to add those paragraphs? 13:14:55 +1 from my side as well for Werner 13:15:09 +1 13:15:09 but I inserted a disclaimer about copyrights, also the piece of text suggested by Doug Sheppers, and I am currently updating the ontology document 13:15:28 good 13:15:32 the new version should be ready and sent to the different editors by next Tuesday 13:15:41 it's quite a long piece of text :) 13:16:02 action joakim and everyone to review the Requirements document before 1/12 13:16:02 Created ACTION-192 - And everyone to review the Requirements document before 1/12 [on Joakim Söderberg - due 2009-12-01]. 13:16:44 zakim, who is here? 13:16:44 On the phone I see +329331aaaa, tobiasbue, +82.10.58.00.aabb, +1.574.905.aacc, +46.1.07.19.aadd, pchampin (muted), florian, ??P6 13:16:46 On IRC I see veroniqueM, joakim, RRSAgent, pchampin, wonsuk, wbailer, tobiasbue, Zakim, daniel, florian, trackbot 13:17:03 regrets+ felix 13:17:22 regrets+ raphael 13:19:48 close ACTION-167 13:19:48 ACTION-167 Ask team contact about access to pages for invited experts (e.g. pierre-antoine cannot access the list of tpac attendees) closed 13:20:06 action on pchampin test TPAC attendees page to see if it is accessible to IE now 13:20:06 Sorry, couldn't find user - on 13:20:28 action pchampin to test TPAC attendees page to see if it is accessible to IE now 13:20:28 Created ACTION-193 - Test TPAC attendees page to see if it is accessible to IE now [on Pierre-Antoine Champin - due 2009-12-01]. 13:21:44 W3C SeMuDaTe2009 paper: http://ceur-ws.org/Vol-539/paper_21.pdf 13:22:57 Joakim: is ACTION-174 (Véronique) ongoing? 13:23:19 ... anyone has any update on ACTION-175 (Felix) ? 13:24:03 ... We leave them open, then. 13:24:15 close ACTION-184 : no existing link 13:24:24 close ACTION-184 13:24:24 ACTION-184 Explain the link, difference or relation of our work with the Media Queries closed 13:24:40 close ACTION-188 13:24:40 ACTION-188 Put the "Error Handling" topic into the agenda of the next telecon closed 13:25:10 Tobias: about 189, on subproperty 13:25:22 ... I started, but postponed it until the end of the discussion. 13:25:58 Daniel: ACTION-190 is still open 13:26:11 RRSAgent, draft minutes 13:26:11 I have made the request to generate http://www.w3.org/2009/11/24-mediaann-minutes.html pchampin 13:26:45 Topic: subproperties 13:27:17 Werner: the starting point of the discussion was: should we define a set of subproperties we are suporting 13:27:34 cons: how do we decide which to include, which to exclude? 13:27:54 cons: why re-define what's already out there? 13:28:33 pros: provide an additional, finer grain, level of mapping 13:28:46 ... allowing to filter some results 13:28:57 consensus: generic approach 13:29:09 we provide a placeholder for subproperties 13:29:26 but we don't define, for the moment, the values that this placeholder can take 13:29:34 werner is speaking 13:29:43 veroniqueM has joined #mediaann 13:29:53 @werner: thanks for the nice summary 13:30:03 it is a good compromise because it allows for future extensions 13:31:04 Joakim: the discussion started with the contributor property, right? 13:31:19 Werner: yes, but the problem also exists with title (e.g. album title) 13:31:37 or fragment (e.g. spatial, temporal, track) 13:32:01 but fragment subproperty could also be "my favorite scenes" 13:33:16 We could ask the API filter by a subproperty, like "creator/author" 13:33:54 Joakim: this could be tricky; take ID3, the labels are not plain text 13:34:12 you have to know how ID3 names "composer", .e.g. 13:34:21 raphael has joined #mediaann 13:34:51 zakim, who is here? 13:34:51 On the phone I see +329331aaaa, tobiasbue, +82.10.58.00.aabb, +1.574.905.aacc, +46.1.07.19.aadd, pchampin, florian, ??P6 13:34:53 On IRC I see raphael, veroniqueM, joakim, RRSAgent, pchampin, wonsuk, wbailer, tobiasbue, Zakim, daniel, florian, trackbot 13:35:15 Chris: I followed the mail discussion passively 13:35:24 tried different things in my implementations 13:35:32 I do not know the best solution yet 13:36:17 I have made the request to generate http://www.w3.org/2009/11/24-mediaann-minutes.html raphael 13:36:52 Chris: we can make the API to conform to the generic method 13:37:21 trackbot, start telecon 13:37:23 RRSAgent, make logs public 13:37:25 Zakim, this will be MAWG 13:37:25 ok, trackbot, I see IA_MAWG()8:00AM already started 13:37:26 Meeting: Media Annotations Working Group Teleconference 13:37:26 Date: 24 November 2009 13:38:23 the difficult part is, for the user, to know which property to use 13:39:06 pchampin: for the moment, we let the implementors put anythink they like in the subproperty placeholder 13:39:09 if anything at all 13:39:18 and let the users find out what subproperty they get 13:39:22 Daniel takes over, I have to leave 13:39:40 chair: daniel 13:40:18 topic: API 13:40:32 Daniel: Chris raised a question on the mailing list 13:40:59 Chris: when implementing the API, I encountered a problem 13:41:12 how to we identify the metadata-source on which the API is drawing? 13:42:49 pchampin: ultimately, our API is the API of a metadata source 13:42:54 +1 for pa 13:43:00 in the simple case, the resource is its own metadata source 13:43:19 but the metadata source can come from somewhere else 13:45:14 However, our API assumes the simple case for the moment, 13:45:32 since we do not specify either the resource to be describe, or the source of metadata 13:45:57 Chris: what about the javascript API in the browser 13:45:59 ? 13:46:16 Present: raphael, veronique, pierre-antoine, wonsuk, werner, tobias, daniel, florian, joakim, chris 13:46:18 we should add to the API method to manage metadata sources 13:46:27 pchampin: +1 13:46:31 Regrets: Felix 13:47:59 Werner: when initializing the object, we can provide a set of metadata sources 13:49:10 pchampin: this is a simple way to go 13:49:28 allow to add or remove sources afterwards is better, but more complicated 13:49:59 ???: Is this an implementation issue or an API issue? 13:50:32 Chris: from the browser perspective, we should address it 13:52:01 pchampin: depending on the use cases of the API in the browser, browser implementation could provide just the particular case of resource=metadata source 13:52:13 depends on the use cases 13:52:29 Chris: I send a mail to Silvia to ask her opinion about that 13:53:24 pchampin has joined #mediaann 13:54:04 action Chris to send a mail to silvia about the implementation of the API in browsers and the need to address several metadata sources 13:54:04 Created ACTION-194 - Send a mail to silvia about the implementation of the API in browsers and the need to address several metadata sources [on Chris Poppe - due 2009-12-01]. 13:54:23 http://lists.w3.org/Archives/Public/public-media-annotation/2009Nov/0036.html 13:54:54 Daniel: another discussion about the management of errors 13:58:27 pchampin: my latest proposal was to retun Null values when there is an error 13:58:52 and to provide an additional method get_diagnosis to get more information about the error, if any 13:59:05 this has been included in the latest Web IDL sent by Chris 13:59:16 Chris: if you want, I can update to API document accordingly 13:59:41 action chris to update the API document regarding error management 13:59:41 Created ACTION-195 - Update the API document regarding error management [on Chris Poppe - due 2009-12-01]. 14:00:15 rrsagent, make minutes 14:00:15 I have made the request to generate http://www.w3.org/2009/11/24-mediaann-minutes.html pchampin 14:00:18 - +1.574.905.aacc 14:00:19 -florian 14:00:19 - +329331aaaa 14:00:20 -??P6 14:00:20 - +46.1.07.19.aadd 14:00:23 -tobiasbue 14:00:26 - +82.10.58.00.aabb 14:00:33 [adjourned] 14:00:49 wonsuk has left #mediaann 14:01:01 I have made the request to generate http://www.w3.org/2009/11/24-mediaann-minutes.html raphael 14:01:19 -pchampin 14:01:20 IA_MAWG()8:00AM has ended 14:01:21 Attendees were +329331aaaa, +82.10.58.00.aabb, +1.574.905.aacc, +46.1.07.19.aadd, +47.26.9.aaee, +49.851.509.aaff, florian, tobiasbue, pchampin 14:02:19 lol 14:02:32 I had a question ... but I guess too late 14:02:44 what is the status planned for the use cases and requirements document? 14:02:50 do you really want to make it a REC? 14:03:01 ... since you talk about LC 14:03:24 ... if it is meant to be a Note ... then, you can safely publish it in its final stage only when the rest is REC ... 14:03:43 I don't think we discussed this particular point 14:03:54 everyone is supposed to review it until next week, though 14:04:07 I guess we will have to decide then 14:07:40 ok, thanks 14:08:41 I can see version 1 on 19/01/2009 and version 2 on 04/06/2009 14:08:49 ... so this will be the 3rd version? 14:09:27 Status section writes: "The group does not expect this document to become a W3C Recommendation." 14:09:35 ... so, I guess it would be a note :-) 14:11:08 raphael: are you still here ? 14:11:13 yes 14:11:35 yes, UC&Req is a Note 14:12:00 OK, this is what I saw reading the status section 14:12:17 ... in this case, you can safely publish the *FINAL* note when the other documents will be REC 14:12:24 ... so no rush for this document 14:12:42 ... LC is important for documents that are then CR ... PR ... REC 14:12:44 oh, regardless of milestone on charter ? 14:12:48 yes 14:13:03 I suggest you publish a new WD, like you have planned 14:13:09 but just called it WD 14:13:19 this document can become Note when the others are REC 14:13:34 at the time of the charter, you didn't know the status of this document ... 14:14:22 zakim, bye 14:14:22 Zakim has left #mediaann 14:14:26 RRSAgent, bye 14:14:26 I see no action items 14:14:26 so your suggestion: no push UC&Req to be officially published as a note, and take a time to increase the quality of doc itself. Right ?