W3C home > Mailing lists > Public > public-media-annotation@w3.org > November 2009

RE: [MAWG] Web IDL version of the generic GET-method

From: Bailer, Werner <werner.bailer@joanneum.at>
Date: Mon, 16 Nov 2009 18:07:15 +0100
To: "Chris.Poppe@UGent.be" <Chris.Poppe@UGent.be>
CC: "public-media-annotation@w3.org" <public-media-annotation@w3.org>
Message-ID: <CD9846F872C7874BB4E0FDF2A61EF09F3CDB149A02@RZJC1EX.jr1.local>
Dear Chris,

Thanks a lot for the draft. I have three comments:

- I think "in propertyName" should be optional as well, omitting it should return all name/value pairs

- I don't know exactly how optional arguments are specified in WebIDL, but is it like in other languages that only those at the end of the list can be omitted, e.g. if I have foo(a,b) with all arguments being optional I can do foo(), foo(a) but not foo(b) ? If so, we should either think how we can support applying some of the arguments independently, or decide for a good order.

- getOriginal data should probably return object, as we cannot assume the original format to fit into a string

Best regards,

From: public-media-annotation-request@w3.org [mailto:public-media-annotation-request@w3.org] On Behalf Of Chris Poppe
Sent: Montag, 16. November 2009 10:41
To: public-media-annotation@w3.org
Subject: [MAWG] Web IDL version of the generic GET-method

Dear all,

According to my action item (ACTION-187 Create a Web IDL specification to the generic GET Method) I hereby sent the Web IDL specification of such a method (open for discussion). This specification is based on the current strawman API design [1]

module mawg {
                interface MediaResource {

                               // Generic Get method
                               object[] getProperty(in propertyName, in optional DOMString sourceFormat, in optional DOMString subtype, in optional DOMString language, in optional DOMstring fragment );

                                DOMString[] getPropertyNamesWithValues(in optional DOMString sourceFormat, in optional DOMString language, in optional DOMString fragment);
                               DOMString[] getSourceFormatsWithValues(in optional DOMString language);
                               DOMString getOriginalData(in DOMString sourceFormat);

//Method for retrieval of the reason of an error
                               DOMString getDiagnosis();

I didn't know what the appropriate place would be for this updated definition. Do we create an API for Media Resource 1.1? And where should it be placed (Drafts in WG Space, Drafts in development, ...)?

[1] http://www.w3.org/2008/WebVideo/Annotations/wiki/Strawman_API_design_and_notes

Kind regards,

Ghent University - IBBT
Faculty of Engineering
Department of Electronics and Information Systems (ELIS)
Multimedia Lab Gaston Crommenlaan 8 bus 201
B-9050 Ledeberg-Ghent

t: +32 9 33 14959
f: +32 9 33 14896
t secr: +32 9 33 14911
e: chris.poppe@ugent.be<mailto:chris.poppe@ugent.be>

URL: http://multimedialab.elis.ugent.be
Received on Monday, 16 November 2009 17:07:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:24:37 UTC