Evaluation and Repair Tools Working Group Teleconference

HTTP-in-RDF

SAZ: AWWSW subgroup of W3C TAG
... Technical Architecture Group oversees many differing groups of w3 and how technologies fit together or can be assimilated
... central distnction: syntactic model v. semantic model
... tools exchanging information = syntax, meaning, inference, and description fo resources and their relations = semantics
... how do we communicate conformance - to what degree is it syntactic v. semantic?
... look at coments from group and interact on conformance
... should happen prior to next draft
... Http in RDF will be focal point for discussion since it is most likely to be used in other contexts

<shadi> http://esw.w3.org/topic/AwwswHttpVocabularyInRdfComments

Section header

JK: they want specific property named contentType
... we have two properties: one has literal value, one has resource but we do not ahve specific properties
... fieldName is literal, headerName is resource-oriented
... don't want to provide properties for each and every header defined (e.g. would not be just HTTP1.1)

SAZ: could we have header names/properties for more comon ones (e.g. contenttype)

JK: present reasons for our current approach to AWWSW and ask which headers should be properties (e.g. only ones defined in HTTP 1.1)

+1

body alternativves

JK: strictly speaking, object culd only be Base64Content

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

SAZ: need to revisit
... marked already as an issue

JK: we already ahve separate classes for varying levels of interpreatation in Content in RDF
... how does this work in HTTP?

Term usage

SAZ: probably generic not AAWSW sense of the word 'representation'
... all to look at webarch document cited in comment

MessageHeader

JK: already remove owl restrictions

Date

SAZ: suggestion is to subclass dc:date with our own for more specific purpsoe
... do we want to have a specific meaning?

JK: Do we need it in Http in RDF at all?

SAZ: do we want to add a property that inherits from dc:date (e.g. timestamp)?
... leave this bc it might ahve ripple effects (e.g. do we subclass dc:hasPart)?

MethodName v. Method

Header element

JK: may be confusing given the word 'element' in the ocntext of HTML/XML
... no element in HTTP

SAZ: not sure aobut next steps except to explain 'element'

domains and ranges

JK: is it permisslbe to say that the range is an HTTP Heaer element and then use colection?

Tpoic: status codes

SAZ: ties in directly with EARL schema issue
... every status code would be a class

<shadi> http://www.w3.org/2008/http-statusCodes

<shadi> http://www.w3.org/WAI/ER/EARL10/WD-EARL10-Schema-20081126#OutcomeValue

SAZ: OutcomeValue (e.g. Pass)
... should create a list of status codes we need, they belong to HTTP in RDF
... JK pls draft some responses and update document accordingly
... may also be items for group discussions

Pointers-in-RDF

Next meetings

<shadi> trackbot, end meeting