<florian> somehow lost the line...

<daniel> PA are you coming to the call now ?

<pchampin> yep, just starting linphone

<pchampin> this is me

<tmichel> Unfortunatly not much participants, I had asked people to join the call to have a quorum ...

scribe wbailer

open actions

daniel to remind wonsuk about his open actions

close action-460

<trackbot> ACTION-460 Get new youtube example files with help of sebastian closed

action 465 no news on webkit, but implementation in python planned/ongoing, daniel will ask wonsuk about news

<trackbot> Sorry, couldn't find user - 462

florian proposes to ask media fragment participants about contacts to webkit

<scribe> ACTION: daniel to contact media fragment group about getting media annotation implementation into webkit [recorded in http://www.w3.org/2012/03/27-mediaann-minutes.html#action01]

<trackbot> Sorry, couldn't find user - daniel

<scribe> ACTION: soohong to contact media fragment group about getting media annotation implementation into webkit [recorded in http://www.w3.org/2012/03/27-mediaann-minutes.html#action02]

<trackbot> Created ACTION-468 - Contact media fragment group about getting media annotation implementation into webkit [on Soohong Daniel Park - due 2012-04-03].

<florian> maybe the fragment guys can bring is in there since nothing happened for months...

close action-465

<trackbot> ACTION-465 Check with Florian if there are updates to be done in the PR version closed

API document

open issues: see http://lists.w3.org/Archives/Public/public-media-annotation/2012Mar/0049.html

issue 1: status codes in JSON examples

issue 2: points on fragment identifiers in http://lists.w3.org/Archives/Public/public-media-annotation/2011Dec/0024.html

<tmichel> second issue:

<tmichel> > There are the issues about fragments without identifiers in the source,

<tmichel> and resources/fragments with multiple identifiers (see [2]). This is something

<tmichel> to go into implementation notes/best practices, either as informative

<tmichel> section/annex of the API document or as a separate note.

issue 2a: multiple identifiers for fragment/resource

scribe: proposal is to return all the identifiers, and allow queries for fragments using each of the identifiers

<florian> +1 thierry

<pchampin> "canonical" identifier?

resolution for issue 2a: proposal agreed

<scribe> ACTION: werner to draft text on multiple identifiers [recorded in http://www.w3.org/2012/03/27-mediaann-minutes.html#action03]

<trackbot> Created ACTION-469 - Draft text on multiple identifiers [on Werner Bailer - due 2012-04-03].

issue 2b: fragment without identifiers

scribe: proposal: API generates identifier, that can be used to query properties of the fragment
... API ensures it remains valid for a defined time, eg a session, but not beyond

<pchampin> the API ensures it remains valid for at least a defined time

for server side, to make the protocol stateless, the identifier should remain valid for all clients for a defined time after the last access

<scribe> ACTION: werner to send draft text on missing fragment identifier issue to mailing list [recorded in http://www.w3.org/2012/03/27-mediaann-minutes.html#action04]

<trackbot> Created ACTION-470 - Send draft text on missing fragment identifier issue to mailing list [on Werner Bailer - due 2012-04-03].

thierry: place to add this text?

werner to propose a place where to add the text

JSON examples in section 3.1 and 3.2 do not include missing properties

scribe: we should add a sentence stating that they are not included in the JSON response and point to the generic no JSON file

we should check the 2xx status codes in general and atomic JSON repsonses

<scribe> ACTION: florian to draft text for start of section 3 about missing properties in the responses [recorded in http://www.w3.org/2012/03/27-mediaann-minutes.html#action05]

<trackbot> Created ACTION-471 - Draft text for start of section 3 about missing properties in the responses [on Florian Stegmaier - due 2012-04-03].

<scribe> ACTION: werner to compile list of status code issues [recorded in http://www.w3.org/2012/03/27-mediaann-minutes.html#action06]

<trackbot> Created ACTION-472 - Compile list of status code issues [on Werner Bailer - due 2012-04-03].

<tmichel> Resoluition: The MAWG agrees to move the API spec to PR after inclusion of the two resolutions taken during this call.

+1

<tmichel> The document should be frozen friday night.

<pchampin> +1

<tmichel> +1

<daniel> +1

<florian> +1

<tmichel> Resolution: above proposal (resolution) adopted.

thierry: remaining actions
... finish implementation report
... advertise API, eg with Webkit
... finish additional mappings

additional mappings

<scribe> ACTION: thierry to remind mari-carmen to finalise schema.org mapping [recorded in http://www.w3.org/2012/03/27-mediaann-minutes.html#action07]

<trackbot> Created ACTION-473 - Remind mari-carmen to finalise schema.org mapping [on Thierry Michel - due 2012-04-03].

[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/465/462/
No ScribeNick specified.  Guessing ScribeNick: wbailer
Inferring Scribes: wbailer
Default Present: wbailer, +82.31.27.9.aaaa, daniel, florian, pchampin
Present: daniel florian thierry werner pierre-antoine
Got date from IRC log name: 27 Mar 2012
Guessing minutes URL: http://www.w3.org/2012/03/27-mediaann-minutes.html
People with action items: daniel florian soohong thierry werner