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

Reaction for webkit item

From: Soohong Daniel Park <soohongp@gmail.com>
Date: Sat, 5 Nov 2011 05:43:41 +0900
Message-Id: <C36CAB9C-C9AC-44B1-96A1-DCC0AF772758@gmail.com>
Cc: "public-media-annotation@w3.org" <public-media-annotation@w3.org>
To: Florian Stegmaier <stegmai@dimis.fim.uni-passau.de>
Folks,

Regrading the webkit contribution, we decided to update our uc&req doc first and input to the webkit during the previous f2f. Florian did propose the updated changes to the group, but few feedbacks on it yet. 

At this f2f we have decided;
- finalizing uc&req doc update
- Daniel and Joakim as participating companies in webkit will internally discuss it and try to move it forward. (progress status will be shared with the group whenever available)


Daniel.


Soohong Daniel Park
Samsung Electronics, DMC R&D
www.soohongp.com, twitter:@natpt

2011. 11. 4. 오후 2:33 Florian Stegmaier <stegmai@dimis.fim.uni-passau.de> 작성:

> Hi Thierry!
> 
> I hope sou have a productive time at TPAC!
> 
> I will discuss this things with Werner today and respond to you soon.
> 
> Let me ask a few questions:
> - what is the progress of the WEBAPPS use case?
> - Are there any news from Yves regarding the API issues?
> - As far as i know it was planned to get in touch with browser vendors - any news about this?
> - Have you discussed the UC&Req spec yet?
> 
> Could you please send the link to the minutes? Otherwise it is very hard to follow you :(
> 
> Cheers.
> _____________________________
> Dipl. Inf. Florian Stegmaier
> Chair of Distributed Information Systems
> University of Passau
> Innstr. 43
> 94032 Passau
> 
> Room 248 ITZ
> 
> Tel.: +49 851 509 3063
> Fax: +49 851 509 3062
> 
> stegmai@dimis.fim.uni-passau.de
> https://www.dimis.fim.uni-passau.de/iris/
> http://twitter.com/fstegmai
> _____________________________
> 
> Am 03.11.2011 um 22:12 schrieb Thierry MICHEL <tmichel@w3.org>:
> 
>> 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 Friday, 4 November 2011 20:49:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 4 November 2011 20:49:30 GMT