W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2011

(wrong string) €“ Invalid example?

From: Hkan <hakan.canberger@gmail.com>
Date: Wed, 26 Oct 2011 17:54:15 +0200
Message-ID: <CAF0yRJsMD1C3jPPDjgoZ_2orjjQ8z9EhEgc+CT-griczQJeNKg@mail.gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: ietf-http-wg@w3.org
On Wed, Oct 26, 2011 at 15:17, Julian Reschke <julian.reschke@gmx.de> wrote:

> On 2011-10-26 15:08, Hkan wrote:
>
>> ...
>>
>> Agree with that too. Spaces are allowed BETWEEN the elements and list
>> separator. But spaces are not allowed BEFORE the first list separator or
>> element, and spaces are not allowed AFTER the last list separator or
>> element, according to the list rules. But the example "  foo ,
>> ,bar,charlie " states it's allowed.
>>
>> The rules would have to look something like this to allow OWS before and
>> after (not a real attempt to produce correct rules, just to illustrate
>> my point):
>>
>> #element => [  *OWS ( "," / element ) *( OWS "," [ OWS element ] ) *OWS ]
>> 1#element => *OWS *( "," OWS ) element *( OWS "," [ OWS element ] ) *OWS
>> ...
>>
>
> Ack.
>
> Those are allowed because of the header-field ABNF:
>
>  header-field   = field-name ":" OWS field-value BWS
>
> ...but I agree that the prose around the examples needs to say that...
>
> Either that or, in order to isolate the examples to lists only, remove the
prefix/suffix spaces in the examples. The 1.2.1 section is near the top of
the document, in a section that talks about syntax. Headers have not been
introduced and since headers are not needed to understand the syntax around
lists I think it only introduces unnecessary complexity to include headers.

So what's the next step? Open an issue?

/Hkan
Received on Wednesday, 26 October 2011 15:55:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:49 GMT