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

RE: [Device APIs Requirements] Input to Gallery API

From: 이원석 <wslee@etri.re.kr>
Date: Mon, 2 Nov 2009 17:01:20 +0900
Message-ID: <B4EAD1122C31304099A5CDEA5447210F01B57F1E@email2>
To: "Tran, Dzung D" <dzung.d.tran@intel.com>
Cc: "SULLIVAN, BRYAN L (ATTCINW)" <BS3131@att.com>, "Device APIs and Policy Working Group WG" <public-device-apis@w3.org>
Hi. Tran and all.

API for Media Resource 1.0(link from previous email) was published as a FPWG at 20th October 2009.
And this is http://www.w3.org/TR/mediaont-api-1.0/.

Best regards,
Wonsuk.

> -----Original Message-----
> From: public-device-apis-request@w3.org [mailto:public-device-apis-
> request@w3.org] On Behalf Of Tran, Dzung D
> Sent: Saturday, October 31, 2009 1:52 AM
> To: SULLIVAN, BRYAN L (ATTCINW); Device APIs and Policy Working Group WG
> Subject: RE: [Device APIs Requirements] Input to Gallery API
> 
> 
> 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 Monday, 2 November 2009 08:02:06 GMT

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