feedback on implementation

Florian,

Thanks for your implementation.

We need 3 different things

- an API test suite (a set of test cases)
- an API implementations inputing these test cases
- an API implementaion report, a document listing the test cases that 
pass or fail the implementation.


We have been thinking that the testsuite should reflect the API 
functionalities. That is indeed what we need to test.
The following are probably the interfaces and methods which need to be 
tested.

Your implementation probably used these or a subset of these interfaces.

So we were thinking of your implementation outputting an additional 
table for the methods.

This would probably be the way to report the implementation status in 
our implementaion document.



------------------------------------


4.1 interfaces with multiple methods

1-MediaResource interface
- createMediaResource
- getMediaProperty

4.2-AsyncMediaResource interface

- getMediaProperty
- getOriginalMetadata
- handleEvent ???


4.3-SyncMediaResource interface
- getMediaProperty
- getOriginalMetadata

4.4-MediaAnnotation interface
--> has seven attributes:
* fragmentIdentifier
* language
* mappingType
* propertyName
* sourceFormat
* statusCode
* value



4.6-MetadataSource interface
--> has two attributes:
* metadataSource
* sourceFormat

Received on Thursday, 3 November 2011 21:13:08 UTC