W3C home > Mailing lists > Public > public-media-annotation@w3.org > July 2009

AW: Type of media file and its metadata

From: Bailer, Werner <werner.bailer@joanneum.at>
Date: Thu, 16 Jul 2009 17:14:56 +0200
To: Felix Sasaki <felix.sasaki@fh-potsdam.de>
CC: "public-media-annotation@w3.org" <public-media-annotation@w3.org>
Message-ID: <CD9846F872C7874BB4E0FDF2A61EF09F18DAF34351@RZJC1EX.jr1.local>
Hi Felix,

This an interesting question, actually I think there are two issues here:

- The metadata to expect does not only depend on the type of the media resource, but also of the metadata format used.We have discussed that issue at the last F2F, and in the API design draft [1] we have added the functionality to filter by source format, and to get all properties that have a value (see section Iterating), in a source format or in all available annotations. Looking at the Wiki page again, I believe we have forgotten a function to get the list of source formats.

- The other issue are annotation of collections such as the feed you mentioned. In that case I think one could only expect a (subset of) descriptive properties, similar to media resources that do not represent actual manifestations of a work. 

Best regards,

[1] http://www.w3.org/2008/WebVideo/Annotations/wiki/Strawman_API_design_and_notes

> -----Ursprüngliche Nachricht-----
> Von: public-media-annotation-request@w3.org [mailto:public-media-
> annotation-request@w3.org] Im Auftrag von Felix Sasaki
> Gesendet: Mittwoch, 15. Juli 2009 22:29
> An: public-media-annotation@w3.org
> Betreff: Type of media file and its metadata
> Hi all,
> appologies in advance if you have discussed this before ... but have we
> decided how our API should "find out" the type of a media file? That
> information is important for knowing what metadata  to expect. Not all
> formats we are discussing have a mime type registered. And a URI like
> http://gdata.youtube.com/feeds/api/videos? gives you the content-type
> application/atom+xml , but within the Atom feed there are many formats
> being used. Should we allow the API to do content sniffing to find out
> what is available?
> Felix
Received on Thursday, 16 July 2009 15:16:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:24:36 UTC