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

ACTION-430: Definition of features to be tested

From: Bailer, Werner <werner.bailer@joanneum.at>
Date: Tue, 5 Jul 2011 09:34:31 +0200
To: "public-media-annotation@w3.org" <public-media-annotation@w3.org>
Message-ID: <CD9846F872C7874BB4E0FDF2A61EF09FC99A41F8D0@RZJC1EX.jr1.local>
Dear all,

Here is a first draft of the definition of what constitutes a feature of the API to be tested.


The following elements are considered features of the API and must be tested by the test suite:
- construction of MediaResource with one or more metadata sources and querying of the supported modes
- read access to the list of properties (single properties and sets of properties, applying filters)
- reading source metadata

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 implementation for the different use cases.


Please review and propose changes/extension etc.

Best regards,

  Werner Bailer
  Audiovisual Media Group
  DIGITAL - Institute of Information and Communication Technologies
  JOANNEUM RESEARCH Forschungsgesellschaft mbH
  Steyrergasse 17, A-8010 Graz, AUSTRIA
  phone:  +43-316-876-1218            personal fax: +43-316-876-91218             
  mobile: +43-699-1876-1218            general fax: +43-316-876-1191  
  web:    http://www.joanneum.at/digital        
  e-mail: mailto:werner.bailer@joanneum.at
Received on Tuesday, 5 July 2011 07:34:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:17:43 UTC