W3C home > Mailing lists > Public > public-wai-ert@w3.org > March 2007

Re: Comments on WD-HTTP-in-RDF-20070301

From: Johannes Koch <johannes.koch@fit.fraunhofer.de>
Date: Mon, 19 Mar 2007 14:59:32 +0100
Message-ID: <45FE9744.5030603@fit.fraunhofer.de>
To: public-wai-ert@w3.org

Johannes Koch schrieb:
> Jo Rabin schrieb:
>> 5. I'm not clear as to what normalisation is pre-supposed on the 
>> contents of
>> the various header field values. For our purposes it would be useful 
>> to have
>> those values in a normal form, where possible. Equally it would be 
>> useful,
>> for audit purposes, to have a literal representation of the unprocessed
>> headers.
> Competing requirements: good searchability (named properties) vs. 
> original order.
> Possible solution:
> Preserve order (rdf:Bag) with
> http:MessageHeader
>   |- http:fieldName rdf:resource="&http;content-type"
>   |  (poining to a specified _value_ instead of named property)
>   |- http:fieldValue

Or using an RDF collection:

<http:Request ...>
   <http:headers rdf:parseType="Collection">
     <http:MessageHeader rdf:ID="mh1">
       <http:fieldName rdf:resource="&http;accept-language"/>
     <http:MessageHeader rdf:ID="mh2">
       <http:fieldName rdf:resource="&http;accept"/>
       <http:fieldValue rdf:parseType="Collection">
           <foo:params rdf:parseType="Collection">

which is a representation of

Accept-Language: en
Accept: application/xhtml+xml;q=1.0, text/html;q=0.9,bar=blah

>> 6. It would be useful for those header field values that have 
>> structure to
>> be represented so that their components are exposed in a way that allows
>> easy access via XPATH expressions.

See #mh2 in the example above.
Johannes Koch
BIKA Web Compliance Center - Fraunhofer FIT
Schloss Birlinghoven, D-53757 Sankt Augustin, Germany
Phone: +49-2241-142628    Fax: +49-2241-142065
Received on Monday, 19 March 2007 14:00:22 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:55 UTC