W3C home > Mailing lists > Public > public-wai-ert@w3.org > October 2006

Re: sequences in the HTTP vocabulary

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Mon, 30 Oct 2006 17:32:27 +0100
Message-ID: <4546291B.6080704@w3.org>
To: Johannes Koch <johannes.koch@fit.fraunhofer.de>
Cc: public-wai-ert@w3.org

Hi Johannes,

This seems to solve the issue for the sequence of multiple headers of
the same field, in this case the "Accept" field.

Are there other types of sequence restrictions that we need to consider
within the HTTP vocabulary (for example the significance of one field
being processed before another one)?

As to the EARL vocabulary, I think we will need a sequential list for
the request and response properties. Do you agree?

Thanks,
   Shadi


Johannes Koch wrote:
> 
> Hi group!
> 
> Another possible solution for sequences in the HTTP vocabulary is to 
> store the headers as if there was only one per header field:
> 
> Accept: text/html;q=1.0
> Accept: application/xhtml+xml;q=0.9
> 
> is represented as
> 
> <http:accept>text/html;q=1.0, application/xhtml+xml;q=0.9</http:accept>

-- 
Shadi Abou-Zahra     Web Accessibility Specialist for Europe |
Chair & Staff Contact for the Evaluation and Repair Tools WG |
World Wide Web Consortium (W3C)           http://www.w3.org/ |
Web Accessibility Initiative (WAI),   http://www.w3.org/WAI/ |
WAI-TIES Project,                http://www.w3.org/WAI/TIES/ |
Evaluation and Repair Tools WG,    http://www.w3.org/WAI/ER/ |
2004, Route des Lucioles - 06560,  Sophia-Antipolis - France |
Voice: +33(0)4 92 38 50 64          Fax: +33(0)4 92 38 78 22 |
Received on Monday, 30 October 2006 16:33:23 GMT

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