- From: Charles McCathieNevile <chaals@opera.com>
- Date: Wed, 11 Nov 2009 08:45:23 +0100
- To: "Ian Hickson" <ian@hixie.ch>, "Dominique Hazael-Massieux" <dom@w3.org>
- Cc: "public-webapps@w3.org" <public-webapps@w3.org>, public-device-apis@w3.org
On Tue, 10 Nov 2009 21:36:36 +0100, Ian Hickson <ian@hixie.ch> wrote:
> On Tue, 10 Nov 2009, Dominique Hazael-Massieux wrote:
>> Le lundi 09 novembre 2009 à 20:08 +0000, Ian Hickson a écrit :
>> > Some use cases:
>> > […]
>> > * Ability to write a Web-based photo management application that
>> handles
>> > the user's photos on the user's computer
>> > * Ability to expose audio files to native media players
>> > * Ability to write a Web-based media player that indexes the user's
>> media
>>
>> Note that these three use cases would be potentially better addressed by
>> the potential Media/Gallery API the group is supposed to work on
>> (“Gallery API, an API to manage the local media file storage” in our
>> charter [1]).
>
> Wouldn't such an API be over-specialisation?
Depends how deeply people care about specific types. It seems the general
feeling in HTML is that knowing something is a video, rather than just an
embedded object, is enough to add an element for it, so probably not
although one would *hope* that there were a general framework behind such
an API to allow mutiple (over-)specialised access APIs to be developed as
deemed useful.
cheers
Chaals
--
Charles McCathieNevile Opera Software, Standards Group
je parle français -- hablo español -- jeg lærer norsk
http://my.opera.com/chaals Try Opera: http://www.opera.com
Received on Wednesday, 11 November 2009 07:46:14 UTC