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

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

From: Jo Rabin <jrabin@mtld.mobi>
Date: Thu, 15 Mar 2007 16:29:00 +0000
Message-ID: <815E07C915F39742A29E5587B3A7FA192A25CFEE@lk0-cs0.int.link2exchange.com>
To: <public-wai-ert@w3.org>, <public-mobileok-checker@w3.org>




> -----Original Message-----
> From: public-mobileok-checker-request@w3.org [mailto:public-mobileok-
> checker-request@w3.org] On Behalf Of Shadi Abou-Zahra
> Sent: 15 March 2007 11:16
> To: Jo Rabin
> Cc: public-wai-ert@w3.org; public-mobileok-checker@w3.org
> Subject: Re: Comments on WD-HTTP-in-RDF-20070301
> 
> 
> Hi Jo,
> 
> Thanks for further clarifying your comments, I think we are mostly set
> now and the ball is in our court to address them. Find some additional
> comments below.
> 
Thanks, Shadi.

One small note:
> 
> 
> >>> 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.
> >> Can you reformulate the question, I'm not sure I quite understand
it.
> >
> > 1. For audit purposes it will be useful to (optionally) have a
textual
> > transcription of the headers, as they appeared on the connection, to
> show
> > that they have been correctly formulated in HTTP-in-RDF.
> >
> > 2. nocache and NOCACHE, for example, are both fine as values.
Someone
> has to
> > normalise the values somewhere and since the application that is
> producing
> > HTTP-in-RDF is already manipulating the Headers it will be useful to
> have
> > the values in a normal form with respect to capitalisation and
white-
> space.
> 
> Ah, OK. We only do #1 so far, I think #2 refers again to the "inside
> checker" vs "between client/server" perspective issue.
> 

I wasn't aware that you do have 1. ... I must take another look, but for
clarity, what I meant was to make available the text of the headers,
like:

HTTP/1.0 200 OK
Date: Thu, 15 Mar 2007 16:20:25 GMT
Server: Apache/1.3.37 (Unix) PHP/4.4.5
Expires: Thu, 15 Mar 2007 22:20:25 GMT
WWW-Authenticate: Basic realm="W3CACL"
P3P: policyref="http://www.w3.org/2001/05/P3P/p3p.xml"
X-Powered-By: PHP/4.4.5
Set-Cookie: cookieb2evosession=6358856_8KNHkkAd64FFnLTEQ5D4QFVyeH8t8zf5;
expires=Sunday, 12-Mar-17 16:20:25 GMT; path=/; domain=w3.org
Cache-Control: max-age=0
Vary: Accept,User-Agent
ETag: "PUB6547a986644a5dce73a668bab07a5ae9"
Last-Modified: Thu, 15 Mar 2007 16:20:25 GMT
Content-Length: 7099
Content-Type: application/xhtml+xml
X-Cache: MISS from www.w3.org

Jo
Received on Thursday, 15 March 2007 20:10:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:28 GMT