W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2002

RE: space

From: Julian Reschke <julian.reschke@gmx.de>
Date: Sun, 3 Mar 2002 15:08:24 +0100
To: "Babich, Alan" <ABabich@filenet.com>, <w3c-dist-auth@w3c.org>, <www-webdav-dasl@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCKEDNECAA.julian.reschke@gmx.de>
> From: www-webdav-dasl-request@w3.org
> [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Babich, Alan
> Sent: Friday, March 01, 2002 9:59 PM
> To: w3c-dist-auth@w3c.org; www-webdav-dasl@w3.org
> Subject: RE: space
>
>
> Julian:
>
> SEARH must take a position on spaces. It is a critical
> issue for string literals. I agree that we're defining a
> protocol -- something processed by software. The readability
> of the protocol string is secondary. However, examples are
> presented in specs., and there is some benefit to having
> these examples be readable. For many elements, extra
> whitespace doesn't matter. So including whitespace for
> such elements is good idea to enhance the presentation
> of the example in the spec. (but not on the wire). For
> string literals, however, whitespace is critical.
>
> Upon reflection, I agree with you that SEARCH should say
> that all characters, including all whitespace (i.e., spaces,
> tabs, carriage returns, vertical form feeds, etc.) in string
> literals are part of the string literal.

Thanks, Alan.

Just for the record: you can't have any control characters except TAB, CR
and LF in an XML string (and preservation of the type of line break is not
guaranteed).

Julian
Received on Sunday, 3 March 2002 09:09:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:00 GMT