Welcome to WebHeadStart.org

Web Technologies

Sponsored By

WebHeadStart.org is currently in beta.
Please pardon our appearance as we work to provide you with the most comprehensive reference on today's web technologies.

Interested in advertising on WebHeadStart? Become an advertising partner today!

[WWW-HTML Mailing List Archive Home] [Messages By Thread] [Messages By Date]

Comments on "3.2. User Agent Conformance" in XHTML 1.0

From: Laurens Holst <lholst@students.cs.uu.nl>
Date: Fri, 13 Jan 2006 09:52:20 +0100
Message-ID: <43C76A44.50701@students.cs.uu.nl>
To: www-html@w3.org

In section 3.2, list item 7 of the XHTML 1.0 specification, it says the 
following:
> 7. If it encounters an entity reference (other than one of the 
> entities defined in this recommendation or in the XML recommendation) 
> for which the user agent has processed no declaration (which could 
> happen if the declaration is in the external subset which the user 
> agent hasn't read), the entity reference should be processed as the 
> characters (starting with the ampersand and ending with the 
> semi-colon) that make up the entity reference.

Correct me if Iâ??m wrong, but doesnâ??t the XML specification define 
different processing rules (i.e., throw an error)? This would be 
orthogonal to item 1 of that same section, and a bad idea, too.


In section 3.2, list item 3 of the XHTML specification, it says the 
following:
> 3. When a user agent processes an XHTML document as generic XML, it 
> shall only recognize attributes of type |ID| (i.e. the |id| attribute 
> on most XHTML elements) as fragment identifiers.

What about xml:id, then? Why this restriction?

I suggest to remove these lines from the specification.


~Grauw

-- 
Ushiko-san! Kimi wa doushite, Ushiko-san nan da!!
Received on Friday, 13 January 2006 08:52:26 GMT
Valid XHTML 1.0! Valid CSS! Site Map | Privacy Policy | Terms of Use | WebHeadStart.org © 2005 All Rights Reserved.