Implementation report for the API for Media Resources 1.0

The API is designed for both client- and server side implementations. Depending on whether the API is implemented in a user agent or plugin, or as a web service, different communication patterns are more appropriate. In the client side case, asynchronous access is typically preferred, while synchronous access is more appropriate for a web service. Thus the two version of the interface are not considered distinct features but different modes of access for the different use cases.

@@@@

2. Implementations of the API for Media Resource 1.0

API for Media Resource 1.0 is implemented in a large variety of products. Following is a non exhaustive list of products that support API 1.0, for information only.

The following are implementations of the API for Media Resource 1.0:

• The API for Media Resource 1.0 (and thus the underlying ontology) has been implemented and integrated in two different showcases (both implementations online at http://mawg.joanneum.at/):
  The first deals with an image gallery showing images as well as its metadata information. Here, the API is implemented as a Web service following the synchronous mode of operations.
  In contrast to that, the second showcase utilizes the API in a browser extension following the asynchronous mode of operation. The application enables a user to generate a video playlist, where videos and the corresponding metadata informations from different platforms can be arranged in an unified way.

The following are applications using features of the Media Annotation Ontology:

• The PrestoPRIME Semantic Converter allows the user to perform mappings between the following metadata formats: Ontology for Media Resource 1.0, DublinCore, MPEG-7 and EBU Core. The application infers alignments between a pair of input an output formats based on ontology representations of their formats and their mappings to an intermediate ontology. The mapping instructions (represented as XSL templates) are derived from then derived.
• The EventMedia Live application is a real-time and large knowledge base containing descriptions of events and media resources derived from several public sources. Its main purpose is to enable interlinking of the events with the according distributed media resources and people who attended the events. In order to annotate media resources, the Ontology for Media Resource 1.0 is used.
• The NinSuna platform combines the Media Fragment URI and the Ontology for Media Resource 1.0 specifications in order to enable a semantically enriched metadata-driven media adaptation as well as media delivery. A demonstrator web application for annotating fragments of media items has been developed.
• The Media Annotation translator aims to provide translators for legacy metadata formats to the ma ontology proposed by the W3C Media Annotation Working Group. Pierre Antoine's Python based implementation only supports ID3 for the moment.

3. API for Media Resource 1.0 Implementations Tested

This implementation report tested 2 separate API for Media Resource 1.0 implementations.

The data presented here is intended solely to be used as proof of API for Media Resource 1.0 implementability. It is only a snapshot of the actual implementation behaviors at one moment of time, this data is not intended to be used for assessing or grading the performance of any individual implementation.

The following table lists the API for Media Resource 1.0 implementations used to cover by the test results.

Company	Product	Version	Type	Platform
JOANNEUM RESEARCH Salzburg Research University of Passau	@@@		webservice	Windows XP
JOANNEUM RESEARCH	@@@		Browser extension	Windows XP

Implementation Results

used to cover by the test results.