See also: IRC log
<scribe> scribe: wbailer
i-know conference program: http://i-know.tugraz.at/wp-content/uploads/2011/08/program_i-know_i-semantics_praxisforum_2011_final.pdf
florian reports on status of api doc
restructured web idl, to integrate sync and async
last call comment on use of code 501
criticism is that 501 is defined that request method is not supported for any resource
option is to define our own error code for this, eg 562
wonsuk: not sure of our own error
code makes it more clear
... we can define our own error code for this error
... scope of our spec is not closely related with http
... we could change the definition of the 501 code for our
spec
proposed solution: define error code 562, description: property not supported
<scribe> ACTION: florian to draft response to LC-2556 [recorded in http://www.w3.org/2011/09/06-mediaann-minutes.html#action01]
<scribe> ACTION: thierry to include text on what constitutes a feature / cr exit criteria into the api doc [recorded in http://www.w3.org/2011/09/06-mediaann-minutes.html#action02]
<scribe> ACTION: thierry to check / update list of group members in api doc acknowledgements section [recorded in http://www.w3.org/2011/09/06-mediaann-minutes.html#action03]
we plan to vote for moving api doc to cr in the mawg telco on sept. 13
daniel reminds the group of cr exit criteria
cablelabs: rdf validation issues
skip for now, if there is time, we work on this document
dig35: compliant, comment missing, martin will add
dublin core: compliant
ebu core: pellet) detects conflict
<martinh> <http://www.dummy.ch/News/16Jan2011/Items/20110116-PNN-0428-528229/> a ma-ont:Document , ma-ont:Collection ; ma-ont:locator "http://www.dummy.ch/News/16Jan2011/Items/20110116-PNN-0428-528229/index.html"^^<http://www.w3.org/2001/XMLSchema#anyURI> .
instance is of collection, as it has locator, reasoner infers it's also a media resource
the two classes are disjoint
ma-ont: Document is found, class is not defined in the ma ontology
martin will send mail to jean-pierre with details
exif: compliant
id3: compliant
agent could be specified in more detail, defining a person rather than just a resource
same issue for second id3 example
iptc: duration value as string, not as decimal
<tmichel> Will do now
media rss: still to be checked
mpeg7: comment missing, martin to fix
ogg: average bit rate includes unit in value field
2 instances of bitrate with this issue
duration of type double instead decimal
fixed in local copy
quicktime: comment missing, martin to fix
smpte: comment missing, martin to fix
ttml: comment missing, martin to fix
tva: ratingscalemin is string instead of decimal
same for rating value and max
txfeed: still to be checked
xmp: language has 3 labels, should be 3 instances - only in the RDF XML
XML and Turtle serialisations are not consistent
youtube: still to be checked
3gp: drop xml base, otherwise ontology is not imported
flv: both examples correct
mp4: compliant
webm: unit in average bit rate - same issue as for ogg
<wonsuk> http://lists.w3.org/Archives/Public/public-media-annotation/2011Sep/0007.html
media rss: compliant, comment missing
txfeed: compliant, comment missing
<wbailer2> scribenick: wbailer2
back to tva example:
issue with collection identifier, pellet finds a literal
<wbailer> scribenick: wbailer
<daniel> ACTION: florian to draft response to LC-2556 [recorded in http://www.w3.org/2011/09/06-mediaann-minutes.html#action04]
tva issues resolved, with changing durations, ratings and location coordinates to decimal
collection should be changed to use rdf:resource
then the reasoner also infers the inverse property
comment in the file about creator and version # is missing
<pchampin> sorry I'm late
<pchampin> anyone here?
we're back from lunch break and will continue
we will do editing of RDF examples until 3pm
quicktime: same issue with xml base as in 3gp and webm
<tmichel> I am back on Zakim, if you need me
<tmichel> Ok can we discuss it now ?
<tmichel> I am on the telecon ;-)
thierry: 2 things remaining
... resolve lc comment
... second is exit criteria
... usual w3c criteria
... thierry will send proposal by tomorrow morning
<scribe> ACTION: werner to send consolidated draft of what constitutes a feature [recorded in http://www.w3.org/2011/09/06-mediaann-minutes.html#action05]
thierry to join tomorrow 10am
<tmichel> http://www.w3.org/2008/WebVideo/Annotations/#Implementa
thierry: no implementations, but
testsuite and tools, services using ontology
... link to wonsuk's implementation still missing
telecon with director to move to pr, need to show that we need exit criteria
scribe: we have to find some kind
of wording for the demonstrators
... just to show that we meet exit criteria, not in the
spec
daniel: must these implementations be synced to test suite files?
thierry: would be great if this is doable
daniel: wonsuk's implementation is not compatible with test suite files, eg different rdf representation
thierry: it's a problem if different from the latest version of the ontology
<tmichel> At least two applications have been demonstrated that use features of the Media Annotation Ontology.
thierry: or mention it and say that it is not fully compatible
<daniel> we have 7 implementations, once preparing the sample using the Werner's implementation, we will ask others implementors for preparing the same illustration regarding each implementation.
revisiting ebucore example
revisiting ebucore example
proposal for fixing it: remove ma-ont Document, replace ma-ont:locator of the collection by dc:format
<scribe> new youtube example: compliant
fixing xmp example
<scribe> .. done
dig35 example
changing rdf:about to rdf:ID, fixing multiple identifiers
fixed datatypes and values
split multiple values for properties into multiple instances of properties
conclusion on test suite examples:
- we have compliant versions for all the files now
- for some files we made modifications based on what we think was meant, editors may want to comment, this applies to ebucore, cablelabs
- martin will generate also the turtle version for all the modified files
florian: we need a normative JSON
representation for the test suite
... two options: 1. browser extensions or native support, JSON
returned; 2. web service returns JSON
... in both cases we can match the JSON result against the
reference JSON for a test file
... basic requirement: value attribute must be correct
... extended: also the structured specific attributes for each
property are correct
... we will need JSON example response for each of the
formats
... option could be to use RDF to JSON conversion of normative
examples
<fstegmai> RDF2JSON converter: http://www.epimorphics.com/web/wiki/rdf-json-converter-google-app-engine
to be checked if the converter is usable for that
<scribe> ACTION: florian to check if this converter is useful for us [recorded in http://www.w3.org/2011/09/06-mediaann-minutes.html#action06]
<trackbot> Created ACTION-440 - Check if this converter is useful for us [on Florian Stegmaier - due 2011-09-13].
florian: we should define tomorrow which are the positive and negative test cases to be covered
[adjourned]
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/pellet/ebu core: pellet/ Found Scribe: wbailer Inferring ScribeNick: wbailer Found ScribeNick: wbailer2 Found ScribeNick: wbailer ScribeNicks: wbailer, wbailer2 Default Present: +43.316.876.aaaa, graz_f2f, +33.9.53.85.aabb Present: daniel wonsuk martin florian werner tobias thierry Agenda: http://www.w3.org/2008/WebVideo/Annotations/wiki/Graz2011Agenda Got date from IRC log name: 06 Sep 2011 Guessing minutes URL: http://www.w3.org/2011/09/06-mediaann-minutes.html People with action items: florian thierry werner[End of scribe.perl diagnostic output]