W3C home > Mailing lists > Public > public-device-apis@w3.org > October 2010

Gallery API use cases?

From: Anssi Kostiainen <anssi.kostiainen@nokia.com>
Date: Tue, 12 Oct 2010 19:05:13 +0300
Message-Id: <4384D651-B381-4F0F-AB4A-7191FCDD2B99@nokia.com>
To: "public-device-apis@w3.org WG" <public-device-apis@w3.org>

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:


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:


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.


- 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?


(I guess this relates to ACTION-216)
Received on Tuesday, 12 October 2010 16:05:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:23 UTC