W3C home > Mailing lists > Public > www-dom@w3.org > April to June 1999

RE: RFC: White Space Handling In XML Parsing

From: Joel A. Nava <jnava@Adobe.COM>
Date: Mon, 17 May 1999 18:18:17 -0400 (EDT)
To: "John Cowan" <cowan@locke.ccil.org>
Cc: <www-dom@w3.org>
Message-ID: <000901bea0b3$08d3c900$8c9f2099@corp.adobe.com>
Your right, the second sentence under (3), does make a
new requirements on the application receiving the info
from the parse. I see no reason that that cannot be done,
as the para you show from the XML does not imply anything
if the xml:space has not been declared on the root. That
definitely leaves it to the application to decide id it
wants to.

--
Joel A. Nava                  (408)536-6209
Adobe Systems, Inc.         jnava@adobe.com

> -----Original Message-----
> From: John Cowan [mailto:cowan@locke.ccil.org]
> Sent: Monday, May 17, 1999 6:31 AM
> To: Joel A. Nava
> Cc: www-dom@w3.org
> Subject: Re: RFC: White Space Handling In XML Parsing
>
>
> Joel A. Nava wrote:
>
> > 3) Elements that do not specify a value for the 'xml:space'
> >    attribute inherit that value from the element in which
> >    they are contained up to the root element. If the root
> >    element does not specify a value for the 'xml:space'
> >    attribute, the value 'default' is assumed.
> >
> > [This is what the XML REC requires.]
>
> Actually not.  The last paragraph of clause 2.10 says:
>
> # The root element of any document is considered to have
> # signaled no intentions as regards application space handling,
> # unless it provides a value for this attribute or the
> # attribute is declared with a default value.
>
> So there are really three possible states of "xml:space" as inherited:
> default, preserve, and clueless.
>
> --
> John Cowan	http://www.ccil.org/~cowan		cowan@ccil.org
> 	You tollerday donsk?  N.  You tolkatiff scowegian?  Nn.
> 	You spigotty anglease?  Nnn.  You phonio saxo?  Nnnn.
> 		Clear all so!  'Tis a Jute.... (Finnegans Wake 16.5)
>
Received on Tuesday, 18 May 1999 08:18:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:13:46 GMT