See also: IRC log
we need to finalise the descriptions of the implementations
daniel reminds that moving api doc to cr is a requirement for moving ontology doc to pr
issue raised by wonsuk: he can contact webkit community about implementation of the api
scribe: implementers will want to
look at use case document
... we should consider updating the use case and requirements
document
... then wonsuk could raise the issue of implementing the api
in the webkit community
... uc and rec document needs to be aligned
<scribe> ACTION: wonsuk to propose use case related to webkit [recorded in http://www.w3.org/2011/09/07-mediaann-minutes.html#action01]
<trackbot> Created ACTION-441 - Propose use case related to webkit [on WonSuk Lee - due 2011-09-14].
<scribe> ACTION: florian to check and update uc and req document for consistency with specs [recorded in http://www.w3.org/2011/09/07-mediaann-minutes.html#action02]
<trackbot> Created ACTION-442 - Check and update uc and req document for consistency with specs [on Florian Stegmaier - due 2011-09-14].
reviewing thierry's proposal for the status of the document paragraph
thierry's proposal is accepted
florian: todos: 1. define
normative json from the ontology testuite, 2. positive/negative
test cases
... two layers: only unstructured, and
structured+unstructured
... the unstructured test cases tests the return values in the
generic MediaAnnotation interface
... the second level would test the specific return types
... in addition define test cases for retrieving properties not
defined, not present in the source file etc
<scribe> ACTION: florian to draft api test suite document based on the outcomes of today's discussions [recorded in http://www.w3.org/2011/09/07-mediaann-minutes.html#action03]
<trackbot> Created ACTION-443 - Draft api test suite document based on the outcomes of today's discussions [on Florian Stegmaier - due 2011-09-14].
for the unstructured test cases, the behaviour is not specific to the properties, ie it is not strictly necessary to cover all properties in an implementation
for the structured case, the behaviour may be different, thus all properties must be tested
<fstegmai> http://www.w3.org/2008/WebVideo/Annotations/wiki/TestSuite
in case that some properties are not covered in formats, we need to make sure that we cover all the properties
florian: JSON comparison will be
client-side as a JS library, thus the tests could run similar
to those testing user agent features
... cf eg http://www.w3.org/2008/webapps/ElementTraversal/index.html
in addition to all the properties, there will be negative test cases, and optional features such as filtering
we need to able to easily create the overview table of features vs implementations from the JSON comparison results from each individual test
wonsuk: should each column in the test output be a separate metadata format?
florian: not all implementations
support all formats, plan is to select the formats to be tested
for each implementation
... should run tests for the formats separately
daniel: for results, use a table of test vs implementations, summarise results over all formats tested with one implementation
florians proposal for interface for defining the test cases uploaded to http://www.w3.org/2008/WebVideo/Annotations/wiki/TestSuite
test cases should include typical error cases
we should discuss with thierry how many test cases are required
florian: first version of test suite could be available before tpac
<scribe> ACTION: thierry to set up api test suite page [recorded in http://www.w3.org/2011/09/07-mediaann-minutes.html#action04]
<trackbot> Created ACTION-444 - Set up api test suite page [on Thierry Michel - due 2011-09-14].
<tmichel> can I join the call to discuss the API CR exit criteria ?
daniel reports on test suite discussion
<tmichel> OK I will join too ...Here is a first draft of the Status of this Document section for the API
<tmichel> CR version.
<tmichel> http://www.w3.org/2008/WebVideo/Annotations/drafts/API10/CR/sotd.html
group agrees on the proposed text
<tmichel> OK very good, I will put it in the spec
<tmichel> Thierry will make a new testsuite page for the API + an implementation report.
<tmichel> Florian is done with the editing of the API. Thierry has the editing token.
descriptions of implementations can be made available to the public
plan is to transit documents in about 2 weeks from now
<tmichel> Use Cases and Requirements for Ontology and API for Media Resource 1.0
wonsuk proposes to update use case doc for proposing api to webkit community
<tmichel> http://www.w3.org/TR/2010/WD-media-annot-reqs-20100121/
<tmichel> this document is kind of out of date regarding our specs.
<tmichel> should be updated accordinglly
we have assigned actions to wonsuk and florian to work on updating it and aligning it with the specs
tobias can contribute to updates
pr phase for ontology doc is expected to take about 4 weeks
<tmichel> http://lists.w3.org/Archives/Public/public-media-annotation/2011Aug/0002.html
<tmichel> Thierry will add a reference to part 1 and part 2.
<scribe> scribenick: wbailer
This is scribe.perl Revision: 1.136 of Date: 2011/05/12 12:01:43 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/joakim/daniel/ Succeeded: s/fitlering/filtering/ Succeeded: s/api/api cr/ Found ScribeNick: wbailer Inferring Scribes: wbailer Default Present: graz_f2f, tmichel Present: daniel wonsuk florian tobias martin werner thierry Got date from IRC log name: 07 Sep 2011 Guessing minutes URL: http://www.w3.org/2011/09/07-mediaann-minutes.html People with action items: florian thierry wonsuk[End of scribe.perl diagnostic output]