W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > November 2010

[Bug 11427] should allow use of xml:id for XHTML5

From: <bugzilla@jessica.w3.org>
Date: Mon, 29 Nov 2010 17:30:40 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PN7Ym-0007za-38@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11427

--- Comment #8 from brian m. carlson <sandals@crustytoothpaste.net> 2010-11-29 17:30:39 UTC ---
(In reply to comment #7)
> You need the optional but specified functionality in appendix E of the xml
> catalog spec (or use an sgml-open catalog:
> 
> http://www.oasis-open.org/committees/entity/spec-2001-08-06.html#s.doctype
> 
> But I guess you knew that and discounted this in advance with the "normative"
> rider.

You can't expect non-normative parts of specifications to be implemented.  I
have in the past used (and continue to use) other tools that don't support
appendix E.  And I think my arguments have technical merit without regard to my
particular setup.

> > And I don't see the recalcitrance to allowing it for the XML serialization. 
> > I'm not requesting that xml:id be the only option, or even the preferred
> > option.
> 
> But I think that you were requesting that a valid HTML5 DOM that is serialised
> as xhtml should use xml:id rather than id for attributes of type ID (that is,
> that the name of the attribute be changed on serialisation)?

I'm not requesting that at all.  I'm requesting that it be an acceptable
(valid) serialization to serialize the DOM as XHTML using xml:id instead of id.
 I'm also requesting that it be valid when parsing XHTML to the DOM to use the
xml:id attribute as the ID if no id attribute is specified.

Alternatively, you could specify a DTD for the XHTML serialization, but even I
think that's an unacceptable alternative.

> xml:id is usable with any XML document type and infers IDness if used with an
> xml:id processor, but usually (as here) it makes the document invalid, whether
> that matters or not depends on what you are doing.

Right.  I'm trying to use valid XHTML5 here, since the pages will end up on the
Internet.  I'm not interested in solutions that produce invalid documents.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 29 November 2010 17:30:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 29 November 2010 17:31:01 GMT