W3C home > Mailing lists > Public > public-device-apis@w3.org > November 2009

Re: Use Cases and Requirements for Saving Files Securely

From: Maciej Stachowiak <mjs@apple.com>
Date: Tue, 10 Nov 2009 17:53:39 -0800
Cc: Dominique Hazael-Massieux <dom@w3.org>, "public-webapps@w3.org" <public-webapps@w3.org>, public-device-apis@w3.org
Message-id: <8C6FAC81-637B-4A90-891A-172285A9985E@apple.com>
To: Ian Hickson <ian@hixie.ch>

On Nov 10, 2009, at 12:36 PM, Ian Hickson 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?

Many modern platforms (well, at least iPhone and Mac OS X) have APIs  
to manipulate a system notion of media gallery. We have considered  
exposing the ability to choose from the user's media collection via  
<input type="file">, possibly keying off of accept="image/*" or "audio/ 
*" or "video/*".

I think an API to freely add and remove items from the media  
collection is something we might not be comfortable with exposing to  
the Web, for security reasons. We might consider an API to save to the  
media collection as long as there is user control.

Regards,
Maciej
Received on Wednesday, 11 November 2009 01:54:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:01 GMT