- From: Tran, Dzung D <dzung.d.tran@intel.com>
- Date: Fri, 30 Oct 2009 09:51:51 -0700
- To: "SULLIVAN, BRYAN L (ATTCINW)" <BS3131@att.com>, Device APIs and Policy Working Group WG <public-device-apis@w3.org>
Also, there is still an outstanding issue around if we can just use FS API with http://dev.w3.org/2008/video/mediaann/mediaont-api-1.0/mediaont-api-1.0.html to achieve the objective of Gallery API. Thanks Dzung Tran, Intel Corporation -----Original Message----- From: public-device-apis-request@w3.org [mailto:public-device-apis-request@w3.org] On Behalf Of SULLIVAN, BRYAN L (ATTCINW) Sent: Thursday, October 29, 2009 02:22 PM To: Device APIs and Policy Working Group WG Subject: [Device APIs Requirements] Input to Gallery API Here is some input to the Gallery API requirements for next week: Re "must expose metadata about the gallery's content items (copyright, author, media-dependent information, etc.)" and "Issue: Exposing metadata is tricky, often giving a choice between creating an endless ontology or building an open-ended system that guarantees no interoperability.": Similar to the ability to discover the supported fields for contacts etc, this can be addressed by enabling the webapp to discover supported metadata. Metadata vocabularies are still evolving but there are some items that are being adopted widely, defined through namespaces to ensure interoperability at least in terms of what the metadata item is supposed to represent. All that the gallery API needs to do is enable the discovery of the supported metadata. Thus I propose the requirement: "must enable discovery of the supported metadata attributes, including the attribute name and its declared namespace, if any.". Best regards, Bryan Sullivan | AT&T
Received on Friday, 30 October 2009 16:52:27 UTC