W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2000

Re: Attr: Tokenized attribute values.

From: Philippe Le Hegaret <plh@w3.org>
Date: Thu, 31 Aug 2000 10:54:02 -0400
Message-ID: <39AE718A.929384C@w3.org>
To: bbrodie@savagesoftware.com
CC: www-dom@w3.org
> Date: Fri, 28 Apr 2000 13:55:14 -0700
> From: bbrodie@savagesoftware.com (Blaine Brodie)
> Subject: Attr: Tokenized attribute values.
> Some clarification please.   In the DOM2 spec of December 10, 1999,
> section 1.2 describing the Attr interface [p.57] contains the following
> paragraph:
> "In XML, where the value of an attribute can contain entity references,
> the child nodes of the Attr node provide a representation in which entity
> references are not expanded.  These child nodes may be either Text [p.66]
> or EntityReference [p.71] nodes.  Because the attribute type may be
> unknown, there are no tokenized attribute values."
> I don't understand the meaning of the last sentence.  Does it mean that
> attribute values MUST be atomic?  Can anyone provide a clearer explanation
> and possibly illustrate the meaning with an example?

We decided to add (and link for the paragraph) the following definition
in the glossary:

 The description given to various information items (for example, attribute
 values of various types, but not including the StringType CDATA) after having
 been processed by the XML processor. The process includes stripping leading
 and trailing white space, and replacing multiple space characters by one.  See
 the definition of tokenized type.

Received on Thursday, 31 August 2000 10:54:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:07 UTC