ERT WG -- 17 Sep 2008

Announcements

SAZ: Mike will co-chair the group
... will be formally announced soon

Comments on HTTP-in-RDF and Content-in-RDF

SAZ: couple of comments on HTTP-in-RDF and Content-in-RDF
... JK do you like to discuss any issue?

JK: wording problems in the comments
... SAZ mentioned he will show comments to some semantic web group

SAZ: will try to get somebody for a teleconference
... also try to invite them to the F2F
... if you have specific questions, please let me know

JK: for example the "represent" wording about RDF classes

CV: don't get that comment either

SAZ: try that somebody help us on this, personally or by phone

JK: the comment about the literal value in the connectionAuthority example doesn't make sense
... it is a literal
... the same with the 2.3.1 comment

<shadi> ACTION: shadi try to recruit someone from SemWeb to help us understand some of the comments and issues [recorded in http://www.w3.org/2008/09/17-er-minutes.html#action02]

<trackbot> Created ACTION-7 - Try to recruit someone from SemWeb to help us understand some of the comments and issues [on Shadi Abou-Zahra - due 2008-09-24].

SAZ: the same comments apply also to several other documents

CV: are the namespaces published?
... at least Content is not

SAZ: should be
... will check
... it is #2008

<shadi> # updated by <http://www.w3.org/WAI/ER/HTTP/http.rdfs>

<shadi> # updated by <http://www.w3.org/WAI/ER/HTTP/http-header.rdfs>

<shadi> # created by <http://www.w3.org/WAI/ER/HTTP/http-headers.rdf>

<shadi> # created by <http://www.w3.org/WAI/ER/HTTP/http-methods.rdf>

<shadi> # created by <http://www.w3.org/WAI/ER/HTTP/http-statusCodes.rdf>

<shadi> # created by <http://www.w3.org/WAI/ER/Content/content.rdfs>

CV: in the document is 2007, but it is published as 2008

JK: will need to update the document

<shadi> ACTION: shadi check possibilities for revising HTTP-in-RDF and Content-in-RDF documents [recorded in http://www.w3.org/2008/09/17-er-minutes.html#action04]

<trackbot> Created ACTION-8 - Check possibilities for revising HTTP-in-RDF and Content-in-RDF documents [on Shadi Abou-Zahra - due 2008-09-24].

<shadi> ACTION: jkoch update HTTP-in-RDF and Content-in-RDF documents [recorded in http://www.w3.org/2008/09/17-er-minutes.html#action05]

<trackbot> Created ACTION-9 - Update HTTP-in-RDF and Content-in-RDF documents [on Johannes Koch - due 2008-09-24].

<shadi> ACTION: shadi update FOAF namespace in the EARL 1.0 Schema to the latest version [recorded in http://www.w3.org/2008/09/17-er-minutes.html#action06]

<trackbot> Created ACTION-10 - Update FOAF namespace in the EARL 1.0 Schema to the latest version [on Shadi Abou-Zahra - due 2008-09-24].

JK: issues of Contents still pending of discussion
... don't understand question 1

SAZ: could response with thanks and asking for a proposal

CV: maybe GRDDL as an alternative to the Content class

SAZ: feel free to ask for more information

JK: about q2, we use always RDF/XML

SAZ: we had N3 representation of EARL schema but decided not to do it any more

CV: don't think N3 is more human readable

SAZ: depending of the kind of human, RDF humans or the rest of humans :)
... should continue with RDF/XML as our primary format

CV: the comment is about examples not the schema

SAZ: could provide also other formats like N3
... it is somehting we can address at the end
... let put it in the wish list for now

JK: about q5 I think it is mentioned in one of the use cases

CV: why jump over q3 and q4?

JK: they are disjoint indeed

SAZ: think disjoint in RDF has an special meaning
... both questions are the opposite

JK: then the first answer is NO and the second is YES

SAZ: I think this is a tricky RDF question and can pospone it until we talk with the RDF guys
... seems that the allowable meaning is also special for RDF people

JK: q4 could be explained further in the document

Pointer Rules and Conventions

SAZ: Pointer conventions

CI: two approaches: 1. more human-friendly approach (which element, 1st character); 2. more parser-friendly (e.g. when parsing of an element is finished)
... several parsers/tools use a certain way of pointing

SAZ: this is focussed on line/char pointer
... XPath pointer should point to most specific element

JK: why do we need these convetions?

CI: readable way to interpret pointers

CV: can discuss this for long
...shouldn't we make a table to say what most parsers do?

CI: we have a specific use case
...for the task force, to point to the same place

<velasco> I need to go: bye

<carlosI> ACTION: ciglesia to provide examples for other kind of pointers [recorded in http://www.w3.org/2008/09/17-er-minutes.html#action07]

<trackbot> Created ACTION-11 - Provide examples for other kind of pointers [on Carlos Iglesias - due 2008-09-24].

Response on POWDER drafts

<shadi> ACTION: Shadi send POWDER comments 1 hour after the call, unless hear otherwise [recorded in http://www.w3.org/2008/09/17-er-minutes.html#action09]

<trackbot> Created ACTION-12 - Send POWDER comments 1 hour after the call, unless hear otherwise [on Shadi Abou-Zahra - due 2008-09-24].

Agenda Items for Upcoming Meetings

SAZ: please send your agenda items to the list

Next Meeting

SAZ: Next Meeting: October 1

ERT WG

17 Sep 2008

Attendees