See also: IRC log
remember to register people!
shadi: has anyone read through atag 2.0 yet?
<shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2007Jan/0032
shadi: summarizes email
... definition of authoring tool seems too wide
johannes: doesnt think earl is part of this api
shadi: has anyone looked at the confirmance claims?
johannes: has thought about api for earl objects
shadi: could we use sparql queries?
<JohannesK> see e.g. <http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/> appendices C, D, E
carlos: doesnt think earl is ready yet for a full api
shadi: do any other tool api's offer anything better then what earl can provide?
http://www.w3.org/TR/mobileOK/
<shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2007Feb/0008.html
carlos: not had chance to look yet
<scribe> ACTION: ALL, read through mobileOK document and review Johannes comments [recorded in http://www.w3.org/2007/02/07-er-minutes.html#action01]
<JohannesK> <http://lists.w3.org/Archives/Public/public-mobileok-checker/2007Feb/0007.html>
<shadi> http://www.w3.org/WAI/ER/HTTP/issues
johannes: issue 001 is most interesting
carlos: if we add a property to the request class that points to the response class then we also need the opposite
shadi: only need to be a 'one way' relationship so property only needs to be created in a single class
<shadi> rdf:Seq
shadi: current proposal is that request class points to response class and if ther are multiple request/responses pairs then the requests are put in rdf sequence list