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

Re: [mawg] AW: [mawg] Re: ACTION-177: API at client/server side

From: Pierre-Antoine <pierre-antoine.champin@liris.cnrs.fr>
Date: Wed, 11 Nov 2009 22:20:06 +0100
Message-ID: <4AFB2A86.9060707@liris.cnrs.fr>
To: "Bailer, Werner" <werner.bailer@joanneum.at>
CC: "public-media-annotation@w3.org" <public-media-annotation@w3.org>
Le 11/11/2009 11:29, Bailer, Werner a écrit :
> Dear Pierre-Antoine,
> we had a discussion about this issue at the F2F, triggered by comments from Doug Schepers. The arguments for having one function are 
> - browser vendors only need to implement one function to support the API

well, ok but that function embeds the complexity of all the small ones
they would have to implement in the other scenario, so...

> - it might be convenient for web developers to query several properties by defining an array with property names and iterate over it
> - extensibility, both to new properties, but also wrt to subtypes, e.g. when we define a subtype "albumTitle" of title one could directly query for it, instead of using a filter on getTitle



Received on Wednesday, 11 November 2009 21:20:48 UTC

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