Re: Attribute normalisation and character entities
On Mon, 24 Jan 2000, I wrote: > On 24 Jan 2000, Richard Tobin wrote: > > > Section 3.3.3 [...] > > However the Oasis test suite [...] > > > > Which is correct? > > If the intent is to do it the SGML way, then 3.3.3 is correct. [...] > > The SGML gotcha here has to do with the 'SEPCHAR' category. s/SEPCHAR/SPACE/g Sorry about that. Perhaps it's worth pointing out that a numeric character reference is the only way to have the literal character in a normalized attribute value, since internal CDATA entities are not allowed. So, under the Oasis interpretation, one could never have end-of-lines in CDATA attribute values. I'm not sure that's reasonable. OTOH, if these literals do sneak through the whitespace rules, what about the further tokenization for non-CDATA attributes? The SGML rules scream "Error!!", but I'm not sure that's reasonable either. Arjun xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ or CD-ROM/ISBN 981-02-3594-1 Unsubscribe by posting to majordom@i... the message unsubscribe xml-dev (or) unsubscribe xml-dev your-subscribed-email@your-subscribed-address Please note: New list subscriptions now closed in preparation for transfer to OASIS.
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format