ERT WG

Debrief from W3C Technical Plenary week

saz: WAI EOWG overlap of mobileOK and WCAG
... we may want to ask them to review EARL Guide
... topics for TPAC day: HTML5, namespaces, openness, view on W3C from outside

jk: audio recordings from TPAC day available

saz: and transcriptions are being refined
... POWDER WG want to add EARL example in POWDER document
... ATAG WG - relation between authoring and evaluation, definition of manual/semiautomatic/automatic (we may want to do some minor changes here)
... ATAG - scope of authoring tool (everything is an AT)

<shadi> ACTION: SAZ send description and draft response on POWDER to ERT WG mailing list [recorded in http://www.w3.org/2007/11/28-er-minutes.html#action01]

<shadi> ACTION: SAZ send background information and notes from meeting with ATAG to ERT WG mailing list [recorded in http://www.w3.org/2007/11/28-er-minutes.html#action02]

saz: next TP is planned for early November 2008 in Paris; possible ERT F2F?

updated Editor's draft for HTTP Vocabulary in RDF

<shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2007Oct/0015

saz: any comments?

<shadi> http://www.w3.org/WAI/ER/HTTP/WD-HTTP-in-RDF-20070914

saz: needs some cleaning (saz volunteers)
... apart from that looks quite stable, examples are helpful

jk: HTTP-in-RDF has a "stable" structure using one namespace, but references resources from several files (statusCodes, headers, methods)

draft proposal for "Content-in-RDF" (working title)

<shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2007Nov/0013

saz: Content-in-RDF is only a sceleton right now; focus on the concept

ci: 2.1: What is "content"?
... needs definition, could be tricky
... Pointers vocabulary has a concept of snippets, but maybe snippets better fit in Content-in-RDF

saz: attempts to define "content" fail miserably :-(
... real meaning depends on the context
... better use examples

ci: snippets in Pointers could be dropped and Content could be used instead
... could we subclass Content for DOM node uses? There was a proposal of DOM-in-RDF.

<shadi> DOMContent Class

<shadi> subclass of XMLContent?

ci: DOM is not necessarily XML

saz: we need to explore the idea of a DOMContent class

<shadi> ACTION: Johannes explore the idea of an DOMContent Class (as opposed to an DOM-in-RDF) [recorded in http://www.w3.org/2007/11/28-er-minutes.html#action03]

jk: it depends on use cases; what we want it to be used for, to look like

saz: use case: evaluation tool gets DOM from browser, can record DOM for a test result
... another use case: node with ID "bla" causes error
... we may need a lot of properties/classes
... so what is our scope, how far do we want to go?

ci: use cases must be restricted on Content-in-RDF

saz: postpone the scope discussion

<shadi> ACTION: SAZ send two or three use cases for DOM usage as content to the ERT WG mailing list [recorded in http://www.w3.org/2007/11/28-er-minutes.html#action04]

jk: I don't think it's DOMContent vs. DOM-in-RDF; maybe DOMContent is a full-blown DOM-in-RDF with some classes being subclasses of Content
... Content-in-RDF is based on Dominique's (DOM's) original proposal

<shadi> "Representations of Content in RDF"

<shadi> "RDF Representations of Content"

ci: how do we manage namespaces in XMLContent?

jk: example 2.5

<shadi> ACTION: SAZ send some naming suggestions to improve "Content in RDF" title [recorded in http://www.w3.org/2007/11/28-er-minutes.html#action05]

jk: because xmlRest points to an XMLLiteral, you can declare namespaces

update on "Pointer Methods in RDF" document

ci: did some cleaning-up of the schema; think it's quite complete; some things to discuss
... I can post some open issues to the list

saz: maybe next meeting next week, but for sure in 2 weeks