RE: Gallery API use cases?

Hi. Annsi and all.
I agree it's better way to make the precise gallery API in terms of scope and role.
I will try to make the first draft for the requirement in proposed style before the next call. Even I am not sure I can participate in the next call because of the business trip.

Thanks.

Best regards,
Wonsuk.

> -----Original Message-----
> From: public-device-apis-request@w3.org [mailto:public-device-apis-
> request@w3.org] On Behalf Of Anssi Kostiainen
> Sent: Wednesday, October 13, 2010 1:05 AM
> To: public-device-apis@w3.org WG
> Subject: Gallery API use cases?
> 
> 
> Hi,
> 
> I looked at the Gallery API and noticed that it is still a bit unclear to
> me from where the requirements are derived from and whether they are
> meaningful:
> 
>   http://dev.w3.org/2009/dap/gallery/#requirements
>   http://www.w3.org/TR/2009/NOTE-dap-api-reqs-20091015/#gallery
> 
> In order to move the spec forward, I guess it would help if we could come
> up with a set of sensible use cases, similarly to:
> 
>   http://dev.w3.org/2009/dap/file-system/file-dir-sys.html#use-cases
> 
> After we agree on the UCs, we could see if ...
> 
> - The UCs are fulfilled with what we already have.
> 
> - It would make sense to extend the file-dir-sys by defining an entry
> point to a well-known filesystem area for media and extending the metadata
> interface with media-specific metadata, among others changes. This would
> be a headless API with no UI integration.
> 
>   http://dev.w3.org/2009/dap/file-system/file-dir-sys.html
> 
> - If the Gallery design could align with Contacts, as discussed some
> months ago. Depending on the use cases we come up with, I could see the
> merits of e.g. reusing the file picker for finding and filtering media
> objects.
> 
> So, use cases anyone?
> 
> -Anssi
> 
> (I guess this relates to ACTION-216)

Received on Thursday, 14 October 2010 02:30:10 UTC