RE: Is there proposal of accessing metadata of media files?

We are still in early stage of defining requirements for Gallery API. Some thoughts are:
	Gallery API:
	Browse for content
	List items
	Type: photo, video, audio, ..etc?
	Resource info: resolution, type
	Protocol info
	Author, artist, genre, album, etc
	List containers
	Move, create, remove

I think the remote services such as media streams would cover under URI.


-----Original Message-----
From: [] On Behalf Of Dan Brickley
Sent: Tuesday, October 13, 2009 11:23 AM
To: Robin Berjon
Cc: Arthur Barstow; Soohong Daniel Park; ext Shumpei Shiraishi; public-webapps WG;;
Subject: Re: Is there proposal of accessing metadata of media files?

Hi Robin,

On Thu, Oct 8, 2009 at 12:40 AM, Robin Berjon <> wrote:
> Hi,
> On Oct 7, 2009, at 15:39 , Arthur Barstow wrote:
>> Soohong, Media Annotations WG - would you please provide a short
>> update/status and plans regarding your Media API spec? Also, is this the
>> most recent API document:
> Could you also copy DAP (cc'ed) please? We have an API in our list (Gallery)
> that could probably be expressed simply with File System plus some metadata.
> We certainly wouldn't mind being able to declare an easy victory there.
> [For those who are missing the context, it's at
> ]

Do you have any more details on DAP's Gallery requirements?

I found my way to;%20charset=iso-8859-1#gallery
which says
This interface:

    * must enable listing all available gallery sources, their names and types;
    * must enable finding content inside a gallery;
    * must enable adding, updating, and removing content from a gallery;
    * must expose metadata about the gallery's content items
(copyright, author, media-dependent information, etc.).

Is that the latest word on the topic? What content types are in scope
for these galleries? anything that might live in a filesystem? Is it
supposed to allow for remote services too (eg. a list of media

Context: Lately I have been looking into 'media centre' APIs (xbmc,
boxee, itunes etc) for the NoTube project. These typically address
some or all of the above requirements plus a bunch more (eg.
pause/play/stream etc content).

I am working up a proposal to expose some of this functionality using
XMPP (aka Jabber), such that an EPG or content browsing app running on
a phone could communicate over XMPP to a TV or media centre. The use
of XMPP for messaging is to avoid the difficulties of exposing
HTTP/REST services in a home or NAT setting, and an attempt to
sidestep the need for devices to be on the same location network. My
impression of DAP is that it's more for device-local access (so less
concern for async interfaces perhaps?). Is that correct?

If any of this is close to our concerns, let's stay in touch..



Received on Tuesday, 13 October 2009 18:40:28 UTC