ACTION-177: API at client/server side (was: Call for Test Cases)

Dear Silvia, all,

thanks for your mail, you are asking a very good question. In fact, we discussed about that yesterday before you joined, resulting in an action to visualise the options we discussed.

Attached is a sketch showing two options:

1. implementation as Javascript interface in the browser, requiring also all the functionality for extracting metadata from the source formats and for mapping there (I think this is the option you are discussing in your mail)

2. implementation as a web service, accessing either remote or local (e.g. database of a portal in proprietary format) media resources and metadata, there could be an (optional) Javascript library that provides the same API interfaces and handles the calls to the web service

Feedback is of course highly welcome.

Concerning the two proposals:

- single function: no final decision, but it is very to likely

- other formats: we have already done the mappings for QuickTime, we should do it for the others you mentioned

Best regards,
Werner

________________________________________
Von: public-media-annotation-request@w3.org [public-media-annotation-request@w3.org] im Auftrag von Silvia Pfeiffer [silviapfeiffer1@gmail.com]
Gesendet: Samstag, 07. November 2009 01:11
An: Joakim Söderberg
Cc: public-media-annotation@w3.org
Betreff: Re: Call for Test Cases

Hi all,

I was going to ask some questions that emerged over the last hour, but
unfortunately it seems the group has finished meeting.

I have a question about where you are going to use the API that you're
defining. One suggestion that I heard was as a javascript interface to
the metadata available in a video/audio file referenced in a <video>
or <audio> element of HTML5.

Is this indeed something you are contemplating?

In this case, it would be great to have:
* a single function and not multiple to access the metadata,
and
* analysis of the metadata used in to QuickTime, Ogg, MPEG4, FLV and
whether it matches with the API.

I'd be happy to help promote the generic function into HTML5 when the
spec is finalised.

Cheers,
Silvia.


2009/11/6 Joakim Söderberg <joakim.soderberg@ericsson.com>:
> Hello everyone,
>
> As a result of the 5th F2F meeting in Santa Clara we have started to define
> our test suite
> requirements (http://www.w3.org/2008/WebVideo/Annotations/wiki/TestSuite).
> We kindly ask the workgroup participants for some more example test cases!
> We came up with some example test cases:
>
> 1) getTitle
> The API should deal with the situation that
>  1) there is no title
>  2) there are multiple titles (that all come from different metadata
> formats)
>  3) multiple types of title (such as Album title, Song title)
>
> 2) Make sure that the API can get additional metadata that are referred to
> in the embedded metadata
> ex. An XMP description referring to another metadata document ( a license
> etc.)
> 3) For the Ontology
> Take two metadata resources that represent the same thing and make sure that
> the API return the same values.
>
> 4) Write something in the wrong way, fake a metadata format that is not
> valid with a metadata specification and see what the API should do with it,
> return in anyway, or not return it at all.
>
> 5) Combination example
> Get the value of the title and then filter
>
> Asking for a generic property like title, then filter the result to get just
> the album title,
> and second directly ask for Album title and compare the results.
>
> See more at:
> http://www.w3.org/2008/WebVideo/Annotations/wiki/TestSuite
> Regards
> Joakim Söderberg
>