07:05:26 RRSAgent has joined #mediaann 07:05:26 logging to http://www.w3.org/2010/09/09-mediaann-irc 07:05:31 Zakim has joined #mediaann 07:26:33 daniel has joined #mediaann 07:26:53 trackbot, start telecon 07:26:55 RRSAgent, make logs public 07:26:57 Zakim, this will be MAWG 07:26:57 I do not see a conference matching that name scheduled within the next hour, trackbot 07:26:58 Meeting: Media Annotations Working Group Teleconference 07:26:58 Date: 09 September 2010 07:27:16 Agenda: http://www.w3.org/2008/WebVideo/Annotations/wiki/Meeting_Agenda_SophiaF2F 07:27:29 vero has joined #mediaann 07:27:32 Present: Wonsuk, Werner, Raphael, Véronique, Joakim, Dong-Youg_Lee, Daniel, Chris, Thierry 07:27:52 Regrets: Tobias, Jean Pierre, John Charles 07:27:58 Chair: Joakim, Daniel 07:34:38 wonsuk has joined #mediaann 07:34:42 http://www.w3.org/2010/POI/wiki/Draft_Charter 07:35:42 scribe: Werner 07:35:42 scribenick: wbailer 07:36:05 topic: ontology doc LC-2404 07:36:30 meeting: MAWG F2F (day 2) 07:36:48 comments by ivan herman 07:37:03 unclear to see how definitions translate to rdf 07:37:14 rrsagent, make logs public 07:37:37 veronique: we will have examples in the ontology doc 07:38:22 raphael: core properties and values are defined, domain is media resource 07:38:44 veronique: we had an example with description as domain 07:39:12 raphael: domain of properties is not defined in the doc 07:39:31 ... the rdf tf has defined classes for the domain of the properties 07:39:50 ... is this the correct approach? this is the question behind ivans comment 07:40:16 raphael: if it always media resource, write in the spec 07:40:34 ... independent of specific representation language 07:41:18 chris: define domain, and reply that there will be the rdf version in the next version of the doc 07:41:42 raphael: update notation to clarify definition of properties 07:43:37 raphael: for properties that have both datatype and object, owl full is needed, how is that modelled by rdf tf 07:49:30 veronique: the task force just chose object properties 07:50:12 chris: sent a comment to support both, rdf tf did not agree 07:50:33 veronique: was intended to an rdf implementation, but not the authoritative one 07:51:08 raphael: is rdf representation of definition is complex, we need to consider the definition 07:52:53 raphael: type of identifier seems to come from a controlled vocabulary 07:53:24 chris: should we add more examples to the ontology doc 07:54:30 raphael: when we expect a controlled vocabulary, we should make this clear (without requiring a specific controlled vocabulary) 07:55:35 veronique: we should add for all these properties a sentence saying it is recommended to use a controlled vocabulary 07:55:57 raphael: rename type attribute, as it might be confusing 07:56:18 s/attribute/attribute of identifier/ 07:57:06 chris: in the api def it's called value and type of value - there is a difference in naming between the documents 07:57:12 ... same for title 07:57:39 ... changed based on comments on the api 07:59:07 raphael: isn't the type of the identifier obvious from the value? 07:59:26 Dong-Young has joined #mediaann 08:01:42 chris: there is a reference to fragments uc 4.4, that states mention different identifiers 08:01:54 raphael: this are all uris 08:03:06 s/this/these/ 08:04:32 if identifiers are encoded as uris, the type is clear from the start of the uri 08:09:15 resolution: drop type attribute of ma:identifier as it is not required for identifiers that must be URIs 08:09:58 action: chris to make updates to api document related to dropping type attribute of identifier 08:09:58 Created ACTION-290 - Make updates to api document related to dropping type attribute of identifier [on Chris Poppe - due 2010-09-16]. 08:10:45 raphael: require use of bcp47 for ma:language 08:11:02 veronique: should be best practice 08:11:24 raphael: that argument holds for many things, for language this could be enforced 08:15:11 veronique andchris 08:15:52 veronique to work with chris and raphael to update the properties of the ontology doc 08:16:15 for ma:language bcp47 is recommended practice 08:16:39 comment from ivan concerning ma:location 08:16:59 chris: add example, refer to rdf in appendix 08:18:13 raphael: add examples, and that coordinate system string is from controlled vocabulary 08:18:43 ... examples: take real world place with coordinates, and mythological place with string 08:21:53 veronique: use of controlled vocabulary is recommended for coordinate system 08:22:59 action: thierry to put agreed version of ontology to url pointed to by namespace 08:22:59 Created ACTION-291 - Put agreed version of ontology to url pointed to by namespace [on Thierry Michel - due 2010-09-16]. 08:23:43 comment on missing appendix: 08:24:04 tmichel has joined #mediaann 08:24:07 raphael: appendix will be added, will go for another lc 08:24:19 rrsagent, make logs public 08:24:28 rrsagent, draft minutes 08:24:28 I have made the request to generate http://www.w3.org/2010/09/09-mediaann-minutes.html wbailer 08:24:41 action: thierry to draft response to ivan 08:24:41 Created ACTION-292 - Draft response to ivan [on Thierry Michel - due 2010-09-16]. 08:25:34 raphael: about title, what is type? replace it by role? 08:25:47 chris: not sure about renaming to role 08:26:56 raphael: type is likely to come from a controlled vocabulary 08:29:09 raphael: date property is generic, but it is still called createdate 08:31:48 we do not want to support any kind of date, but creation/publication related date (up to release/first broadcast) 08:32:18 raphael: again recommend use of controlled vocabulary 08:33:09 florian^ has joined #mediaann 08:36:10 raphael: be more precise in the prose about creator / contributor: creator as primary agent related to creation, contributor as secondary 08:38:34 back to title: rename type attribute to role? 08:39:56 vero: we cannot use role if we use it already in a different way 08:40:38 vero: clarify the ones that are used, or ask on the mailing list about other options 08:42:05 action: veronique to check together with other table editors option for clarifying type/role attributes 08:42:05 Sorry, couldn't find user - veronique 08:43:12 rrsagent, make logs piblic 08:43:25 rrsagent, make logs public 08:43:35 rrsagent, draft minutes 08:43:35 I have made the request to generate http://www.w3.org/2010/09/09-mediaann-minutes.html wbailer 09:22:12 topic: LC comments on API document 09:22:50 topic: LC-2419 09:23:34 editorial: shouldn't there be plural "media resource_s_" in the title? 09:24:40 thierry: no formal issue to change the title 09:30:43 raphael_ has joined #mediaann 09:32:24 we will change to plural in both docs, maybe also in uc 09:32:34 Zakim has left #mediaann 09:32:39 action: chris to chanage title to plural in api doc 09:32:40 Created ACTION-295 - Chanage title to plural in api doc [on Chris Poppe - due 2010-09-16]. 09:32:56 action: wonsuk to change title to plural in ontology doc 09:32:57 Created ACTION-296 - Change title to plural in ontology doc [on WonSuk Lee - due 2010-09-16]. 09:33:11 please reflect also this changes into the api-doc while working on the LC-comments: http://lists.w3.org/Archives/Public/public-media-annotation/2010Sep/0038.html 09:33:46 editorial: thereby ... approved 09:34:09 editorial: formats in scope are stored ... approved 09:35:08 editorial: in the browser ... approved, (there -> their) 09:35:36 editorial: api has # of interfaces ... approved 09:36:24 implementation should support interfaces: change to must? 09:37:49 change to: must implement these interfaces 09:38:41 comment on example ... HTML5 by making the HTMLMediaElement inherit from the MediaResource interface, not an example, but a MUST? 09:39:00 chris: difficult, example assumes changes to HTML5 spec 09:40:00 ... can't be required without agreement with HTML5 group 09:43:37 thierry: problem is also that HTML5 is to a final rec 09:44:43 raphael: we should get review from HTML5 group 09:45:47 wonsuk: agrees to get review, concerned of time frame to get review 09:46:07 raphael: it's a question of negotation 09:46:22 thierry: requested review from HTML WG 09:46:23 Last Call review http://lists.w3.org/Archives/Public/public-media-annotation/2010Jun/0050.html 09:46:42 thierry asked also for scheduling of review 09:47:03 http://lists.w3.org/Archives/Public/public-media-annotation/2010Jun/0023.html 09:47:04 ... got no response 09:47:23 raphael: propose to send mail again to all chairs 09:48:28 chris: propose to drop the example 09:49:43 raphael: is there another way of doing the same in HTML5? 09:50:27 chris: what is needed to get an object that implements the interface, HTMLMediaElement is just one way of doing this, there are other ways 09:50:53 raphael: would you consider being a media reosurce something else? 09:51:13 chris: could be added as a separate object in HTML5 09:52:08 raphael: a binding between HTML5 and MAWG is needed 09:55:41 resolution: ask HTML5 for their response on this issue 09:56:00 rrsagent, draft minutes 09:56:00 I have made the request to generate http://www.w3.org/2010/09/09-mediaann-minutes.html wbailer 09:57:01 action: thierry to send mail to HTML WG chairs 09:57:01 Created ACTION-297 - Send mail to HTML WG chairs [on Thierry Michel - due 2010-09-16]. 10:00:41 raphael: this is a topic for hcg telecon 10:03:31 parameters optional in webIDL: mark as optional instead of using OPTIONAL keyword in prose 10:08:39 chris: optional keywords are present in the webidl code 10:09:24 comment on general getProperty 10:10:02 chris: metadata is not necessarily loaded, this is up to the implementation 10:16:24 nick raphael 10:19:24 Geolocation API: http://www.w3.org/TR/geolocation-API/ 10:19:51 woksuk: geolocation uses asynchrounous api 10:20:04 joakim has joined #mediaann 10:20:18 http://www.w3.org/TR/geolocation-API/ 10:24:16 chris: should not be a big problem to change to this pattern, callbacks would get MAObjects 10:26:41 we could support both asynchronous and synchronous mode of using the API 10:31:40 chris: to check in webidl spec if overloading is possible (to have same name for synchronous and asynchronous variants of the functions) 10:32:01 resolution: we will add asynchronous variants of the functions to the api 10:32:14 rrsagent, draft minutes 10:32:14 I have made the request to generate http://www.w3.org/2010/09/09-mediaann-minutes.html wbailer 10:32:54 substantial: getdiagnosis is not thread safe 10:33:21 http://www.w3.org/2006/02/lc-comments-tracker/42786/WD-mediaont-api-1.0-20100608/ 10:34:36 [lunch break] 10:34:43 rrsagent, draft minutes 10:34:43 I have made the request to generate http://www.w3.org/2010/09/09-mediaann-minutes.html wbailer 11:44:59 Group Photo: http://www.w3.org/2008/WebVideo/Annotations/wiki/File:MAWG-Nice-201009.JPG 12:08:11 scribenick vero 12:09:18 Follow-up of the discussion on the LC comments 2419 for API document 12:10:10 current issue discussed: getDiagnosis doesn't seem thread safe... 12:11:13 tmichel has joined #mediaann 12:16:03 Werner: the problem only occurs only if the API works synchronously 12:22:35 Chris: I can check out in the WebIDL if it is possible to pass an ma:Object reference as an argument in a method 12:22:48 ... so that it can be modified in the method 12:23:02 ... then we can return the status code instead of an ma:Object 12:23:28 ... that would prevent the need of the getDiagnosis method 12:30:05 Chris: if status is OK, it means that the process ran correctly but no value was found 12:30:19 ... probably needs to be clarified in the API document 12:35:38 Joakim: pasting an example code in the WG notes related to the LC comment 2419 on the API document 12:37:08 Next point in LC comment 2419 12:37:32 "I suggest exposing the properties directly on the object..." 12:37:54 Werner: is inherited from the single getProperty method that we agreed on 12:38:30 ... we do not want to duplicate the method for all the properties 12:39:14 ... the suggestion from Robin works with the assumption that you want to retrieve all the values for the properties 12:39:52 Chris: the discussed method gives back the properties that have a value 12:40:11 ... I do not mind its removal 12:41:14 Werner: what would be the alternative to querying for the values of all the properties? 12:42:04 ... Dough and Silvia also wanted one function with a list of values returned 12:43:05 Chris: the function is implemented for the ease of the implementers 12:43:28 Werner: the name is misleading, maybe the re would be less confusion by replacing it 12:46:46 Chris: the main reason for the getProperty function is that when you request even for one property, there might be several responses due to language etc 12:46:47 ... 12:47:02 and this is not easily representable as a property directly linked to an object 12:47:30 ... this is why we have one method returning a list of objects 12:47:32 tmichel has joined #mediaann 12:47:54 Werner: we have been asked to simplify the use of the API and provide a single getProperty method 12:48:30 rrsagent, draft minutes 12:48:30 I have made the request to generate http://www.w3.org/2010/09/09-mediaann-minutes.html tmichel 12:48:41 Chris: we keep the getPropertyNamesWithValues but will change the naming to a more appropriate one 12:49:32 Next point of the LC comment 2419 on the API document 12:50:12 Chris: the media object is the annotation attached to media resource 12:50:29 ... so media annotation is indeed better 12:51:16 Next point "simpler to replace getSOurceFormatWithValues with..." 12:52:11 Werner: same as the answer to the above, the point about the getPropertyNamesWithValues method 12:53:04 Chris: the function is meant to get the information of the provenance of an annotation 12:53:24 Werner: it is interesting mostly in the case of multiple annotations, to decide on how to handle it 12:53:55 Chris: so we decide to keep the method, and we add an example with EXIF that demonstrates its usefulness 12:55:42 Chris: actually... it's more t check out whether an annotation of a certain format is available (ex: if there is an exif annotation for a given resource) 12:58:29 Chris: can also get the information and process it otherwise... 12:59:58 ... provides simply an easier way of filtering 13:00:21 ... but we do not have a good use case for justifying it 13:00:55 The group agrees for dropping the method 13:01:30 At least the people presents at F2F agree to the dropping of the abovementioned method 13:02:24 Next point of the LC comment 2419 on the API document, about status codes 13:03:01 Werner/Chris: we can make the unsupported format a status quote 13:05:54 Werner: the description of the selectMAresource should be improved, made more precise 13:06:32 Werner: yes, the function is there to load an other resource and external metadata 13:06:46 ... and yes there will be an asynchronous version of this function 13:06:58 ... the return type will be changed to return a status code 13:19:19 Chris: we will look into creating a constructor for the media resource interface 13:19:37 ... which would avoid the selectMAmedia method 13:20:51 Next point of the LC comment 2419 on the API document "language interface is meant to be inherited..." 13:21:07 Chris: agreee 13:21:17 s/agreee/agree/ 13:21:48 Next point of the LC comment 2419 on the API document "unclear 'plain text' is for unstructuredValue..." 13:23:48 I have made the request to generate http://www.w3.org/2010/09/09-mediaann-minutes.html raphael 13:24:15 Chris: it is for the values that have no clear type; binary values are converted to a string, XML elements are parsed and their textual value returned 13:25:47 Next point of the LC comment 2419 on the API document "what is the type of sourceFormat" 13:26:11 Rapahel: it's DOMstring... 13:26:25 Werner: the comment is about the syntax 13:26:28 ... 13:26:50 ... in mediaFragment it's a URI, but WebIDL's spec is quite fuzzy 13:29:07 Raphael: so the API document has to be changed and the required information has to be added 13:30:03 Next point of the LC comment 2419 on the API document "why is there a value field on identifier if it's holding a URI..." 13:37:54 CHris: we'll remove the URI from ma:interfaceobject, because sometimes you don't have a URI (for the heigth or width for example) 13:38:25 ... was inherited from older version/implementation of the API 13:39:48 Next point of the LC comment 2419 on the API document 13:40:47 "usage s a service are not precise enough and not normative enough..." 13:41:16 Chris: ask Felix for the rationale behind it 13:41:46 Werner: we have the same in our implementation, but there is no WebIDL binding for that, so WebIDL is not enough for defining it 13:42:01 ... maybe we can present the section as an example 13:44:42 s/usage s a service/usage ss a service/ 13:45:08 Werner: useful as an example for a webservice implementation, but it should not be normative 13:48:07 Chris: someone contacts WebIDL to stay that we are looking into standardising web services and we are wondering in what direction things are going with WebIDL 13:48:50 ACTION: Joakim to contact WebIDL for requesting information about the planned direction for the webservices 13:48:51 Created ACTION-298 - Contact WebIDL for requesting information about the planned direction for the webservices [on Joakim Söderberg - due 2010-09-16]. 13:49:20 Next point of the LC comment 2419 on the API document "counter-intuitive.." 13:50:01 Werner/Chris: it is the same type of comment as before, on the "unique method for get lists of properties", same answer 13:50:30 Next point of the LC comment 2419 on the API document 13:50:32 RRSAgent, draft minutes 13:50:32 I have made the request to generate http://www.w3.org/2010/09/09-mediaann-minutes.html vero 13:54:29 "suggested terms should not be in the API document" 13:55:09 Werner: we should fix the naming of the properties and attributes 13:55:34 Chris/Raphael will go through the API+Ontology document to check out for consistency 13:56:03 Chris: I will indeed remove the suggested terms from the API document, and will put them in the Ontology document 13:57:27 fsasaki has joined #mediaann 13:57:51 Next point of the LC comment 2419 on the API document "DAte in the interface name" 13:58:09 Chris: will change the interface to create a Date 13:58:41 ACTION: Chris to change the API interface about Date 13:58:42 Created ACTION-299 - Change the API interface about Date [on Chris Poppe - due 2010-09-16]. 13:58:50 Werner: typo in the example 13:59:33 Next point of the LC comment 2419 on the API document "Location interface coordination with Geolocation WG" 14:00:10 http://dev.w3.org/geo/api/spec-source.html#position 14:00:18 Werner: can the interface be aligned? 14:02:04 Raphael: problem is for the locations that are not on Earth 14:02:39 Werner: we culd have either their coordinate system or a URI, but they require accuracy specification, which we don't have 14:02:47 Chris: we have floats, they have double 14:04:19 Raphael: dont change anything, but state that you cover more than locations on Earth 14:04:28 Chris: we cover more 14:05:54 Raphael: can we change the value to double, then we can copy the value 14:08:42 Raphael: the Geolocation WG is not fixed yet, still in LC, we should contact them to ask for the optionality of the accuracy element. This way we could use their interface 14:09:58 ACTION: Joakim to contact the Geolocation WG and see if they'd be OK to make the accuracy optional 14:09:58 Created ACTION-300 - Contact the Geolocation WG and see if they'd be OK to make the accuracy optional [on Joakim Söderberg - due 2010-09-16]. 14:10:27 Chris: they have a fixed geolocation system, that would solve the problem for us too 14:10:54 Next point of the LC comment 2419 on the API document "In Relation" 14:11:01 Chris: changed that 14:11:51 Next point of the LC comment 2419 on the API document "easier to read if interface atributes..." 14:13:09 Chris: I'll add a link to the corresponding properties in the Ontology document 14:13:54 Next point of the LC comment 2419 on the API document "FrameSize preferred value and example" 14:14:27 Chris: it's a dot value, European/US notation clash, it's not a float 14:14:43 ... will do the editing work 14:15:04 Next point of the LC comment 2419 on the API document "compression" 14:15:19 Chris: related to the way it is defined in the ontology document 14:15:31 Joakim: compression type is used 14:17:34 Chris: this is a question for the ontology document, will be dealt with when updating the ontology document 14:17:56 ACTION: Chris to check out the compression property of the Ontology document 14:18:00 Created ACTION-301 - Check out the compression property of the Ontology document [on Chris Poppe - due 2010-09-16]. 14:18:36 Werner: recommended to use controlled vocabulary, like extended MIME type 14:20:22 Next point of the LC comment 2419 on the API document "samplingRate" 14:21:45 Werner/Chris: change to capital R, and other property names to be consistent with the naming convention 14:22:23 ACTION: Chris to check out the consistency in the property names in the Ontology document's table 14:22:23 Created ACTION-302 - Check out the consistency in the property names in the Ontology document's table [on Chris Poppe - due 2010-09-16]. 14:23:38 Next point of the LC comment 2419 on the API document "relationship of section 5 to HTTP is unclear" 14:24:57 Next point of the LC comment 2419 on the API document "privacy issues, section 7" 14:25:22 Werner: if someone publishes metadata on the Web, it can be accessed 14:27:06 Werner: we do not implement the tool that extracts this info from the image, we use other tools that do that 14:32:16 Next point of the LC comment 2419 on the API document "integration with Media Capture" 14:32:58 ACTION: Joakim to inform the Media Capture WG about our LC document 14:32:58 Created ACTION-303 - Inform the Media Capture WG about our LC document [on Joakim Söderberg - due 2010-09-16]. 14:42:19 RRSAgent, draft minutes 14:42:19 I have made the request to generate http://www.w3.org/2010/09/09-mediaann-minutes.html vero 15:04:56 scribenick: wbailer 15:05:10 topic: LC-2395 15:05:19 sampling rate as only audio param? 15:05:25 I understand Robin's comment. I would propose to drop the "usage as a service" sections. We don't have time to discuss the details of the "usage as a service" sections. It was a kind of ad hoc proposal, copying the "normal" API calls 15:05:25 [2010-09-09 오후 10:55:27] Felix Sasaki: So I would not contact WebIDL for requesting information about the planned direction for the webservices, but reply to Robin that I agree with his comment, and drop the "usage as a service" sections. That's of course my personal opinion. Just my two sents 15:06:03 chris: same answer as for ontology doc 15:06:38 I understand Robin's comment. I would propose to drop the "usage as a service" sections. We don't have time to discuss the details of the "usage as a service" sections. It was a kind of ad hoc proposal, copying the "normal" API calls 15:07:03 concerning quality parameter: cf answer in ontology doc 15:08:01 explain about "no exceptions" 15:08:41 omission of speex and vp8: same as for ontology doc 15:09:00 action: thierry to draft answer for lc-2395 15:09:01 Created ACTION-304 - Draft answer for lc-2395 [on Thierry Michel - due 2010-09-16]. 15:09:16 topic: LC-2406 15:10:53 thierry: invite doug to join telecon and discuss these issues 15:11:18 action: joakim to invite doug to telecon to discuss his lc comments 15:11:18 Created ACTION-305 - Invite doug to telecon to discuss his lc comments [on Joakim Söderberg - due 2010-09-16]. 15:11:50 chris: explicitly state that we support several metadata sources 15:12:52 action: chris to add paragraph to section 2 about support for several metadata sources 15:12:52 Created ACTION-306 - Add paragraph to section 2 about support for several metadata sources [on Chris Poppe - due 2010-09-16]. 15:13:25 wonsuk: doug reviewed version from march, and not the lc version 15:14:17 joakim to inform doug about current version 15:14:47 rrsagent, draft minutes 15:14:47 I have made the request to generate http://www.w3.org/2010/09/09-mediaann-minutes.html wbailer 15:17:24 topic: LC-2410 15:18:43 action: chris to fix description of parameters in getoriginaldata 15:18:43 Created ACTION-307 - Fix description of parameters in getoriginaldata [on Chris Poppe - due 2010-09-16]. 15:20:23 topic: LC-2394 15:22:18 action: chris to take care of editorial issues in this comment 15:22:18 Created ACTION-308 - Take care of editorial issues in this comment [on Chris Poppe - due 2010-09-16]. 15:22:42 the api -> this api: approved 15:23:34 mocp: add explanation and reference 15:23:47 Does "Media Ontology" here refer to the same thing as MOCP earlier? 15:24:20 chris: yes, it's the same thing 15:24:30 clarify in abstract 15:25:53 lies on -> is 15:26:26 drop underlying: approved 15:27:47 to support -> of supporting: approved 15:29:39 drop the sentence "This document is being published with the aspiration to gather wide feedback on the yet available API design." 15:31:34 improve markup of section as normative/informative (eg.section 2 api doc) 15:33:15 action: thierry to improve markup of nomative/informative, probably with specific class to visualise 15:33:15 Created ACTION-309 - Improve markup of nomative/informative, probably with specific class to visualise [on Thierry Michel - due 2010-09-16]. 15:34:00 add figure title for figure in sec. 1, in the first sentence add reference to Fig. x 15:34:49 drop the "the" after "includes" and add an "and" before "possibly": approved 15:35:19 change "of" to "to" approved 15:38:39 I have made the request to generate http://www.w3.org/2010/09/09-mediaann-minutes.html raphael 15:38:56 http://dev.w3.org/2009/dap/contacts/#security-and-privacy-considerations 15:46:17 raphael: ask commenter to provide a proposal for handling security 15:46:45 change "by" to "with": approved 15:47:31 At the back-end of the web service -> in the implementation of the web service 15:49:09 full stop after "database, movie store) " 15:49:42 With the help of such a service thee user agent could retrieve ... 15:49:58 replace "as" with "than": approved 15:51:12 rewrite alt text of figure 15:51:24 action: werner to add hyphens in Java-Script in the figure 15:51:25 Created ACTION-310 - Add hyphens in Java-Script in the figure [on Werner Bailer - due 2010-09-16]. 15:51:51 In both scenarios, the access to the metadata properties needs the following stack of components: drop "the" before access 15:52:27 An implementation of the mappings from a specific source format to the properties of the media ontology -> change media ontology to proper noun 15:52:42 change "on" to "with" and "working" to "applied": approved 15:53:32 it is assumed that there is at least -> one needs at least 15:53:50 change "exists" to "consists": already taken care of 15:54:02 ... specific operation: getProperty. approved 15:54:15 change "to iterate" to "iteration": approved 15:54:50 Lastly, methods are available -> Methods are available 15:55:32 in 3.1 offers -> ... provides a number of operations to access the metadata ... 15:55:42 change "on" to "of": approved 15:57:12 It seems like you're invading the HTML WG's namespace.... : issue of ongoing discussion 15:59:10 getProperty is singular, it shouldn't be returning an array. : we keep it, the method does not return multiple properties but multiple values of one property 15:59:20 rrsagent, draft minutes 15:59:20 I have made the request to generate http://www.w3.org/2010/09/09-mediaann-minutes.html wbailer 16:00:26 change name getProperty to getMediaProperty to avoid conflics with DOM 16:01:29 getPropertyNamesWithValues -> renamed to Having vlaues 16:01:49 getSourceFormatsWithValues has been dropped 16:02:01 getSourceFormatsWithValues has been dropped 16:02:51 s/getSourceFormatsWithValues/getDiagnosis/ 16:03:16 getOriginalData will be renamed to getOriginalMetadata 16:03:37 operation is the conventional name in WebIDL 16:04:04 Change "to retrieve" to "retrieval of" (globally) - we dropped getDiagnosis 16:05:21 And splitting a return value ... : it's no longer split, with function returning a status code; exception are not used due to objections brought forward in comments to earlier drafts 16:05:57 Requesting "title" returns : add quotation mark 16:06:56 rrsagent, draft minutes 16:06:56 I have made the request to generate http://www.w3.org/2010/09/09-mediaann-minutes.html wbailer 16:08:05 replace "to refine" with "refining" and add a period to this "sentence": approved 16:08:32 Only if the metadata is available in the specified language, the values are returned. ---> Values for the metadata will only be returned if it is available in the specified language 16:08:41 You have a space inside the quotes around " UMID" which seems odd. approved 16:08:57 the earlier request seemed to be for 'title', not 'Title' ...: approved 16:09:20 Why is this a string instead of a url type? there is no URI type in WebIDL 16:10:56 Shouldn't organization be creative commons and the "link" property be to the license? example is outdated, will use new examples provided by PLING 16:11:12 behaviour -> behavior 16:11:43 system specific information: approved 16:11:56 Enlarged is odd. Later versions of this document may include additional status codes or other changes. approved 16:12:07 should be "OK" approved 16:12:25 this is really unhelpful. - obsolete when removing getDiagnosis 16:13:04 layout issues: random indentation, random trailing whitespace 16:13:43 wbailer has joined #mediaann 16:13:59 rrsagent, draft minutes 16:13:59 I have made the request to generate http://www.w3.org/2010/09/09-mediaann-minutes.html wbailer 16:14:07 layout issues: approved 16:14:31 ask timeless for his real name, and add to acknowledgements 16:15:15 Members of the Working Group are: is there twice 16:15:30 fix special characters in European names 16:15:40 rrsagent, draft minutes 16:15:40 I have made the request to generate http://www.w3.org/2010/09/09-mediaann-minutes.html wbailer 16:24:33 I have made the request to generate http://www.w3.org/2010/09/09-mediaann-minutes.html raphael 16:27:57 wonsuk has left #mediaann