W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > February 2011

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

From: <bugzilla@jessica.w3.org>
Date: Mon, 07 Feb 2011 22:28:13 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PmZZ7-0003Gh-4O@jessica.w3.org>

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |WONTFIX

--- Comment #10 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-02-07 22:28:11 UTC ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:

Status: Rejected
Change Description: no spec change
Rationale: (In reply to comment #0)
> Because the XML serialization of HTML5 does not require or specify a DOCTYPE
> (and therefore, a DTD), generic XML processing tools have no way of determining
> the proper attribute to use as an ID.

There are several ways for generic XML processing tools to know that the id=""
attribute on elements in the HTML, MathML, and SVG namespaces is an ID
attribute. The tool can have hardcoded namespace knowledge. The tool can be
given a DTD. The tool can be given an XML Schema. The tool can be configured
with namespace-specific information.

> This causes problems when using e.g.
> XInclude with the "element" xpointer, which uses the ID to determine the
> subtree to include.

If the tool implements XInclude, it can also implement HTML (and MathML and
SVG), at least the minimum required for its users to use HTML (or MathML or
SVG) with XInclude.

> I use this currently to include relevant portions of XHTML
> into an Atom feed, and it is broken with XHTML5.

You can use an XPath XPointer in XInclude, instead of relying on IDness.

> Currently, the specification is silent about whether xml:id is permitted at all

That's out of scope of the HTML spec. Nothing stops you from using xml:id with
HTML. If you decide xml:id is a specification that applies to your stack, then
it is conforming in HTML for you.

> and if so, what its interaction is with id.

If there are any specific interactions that are not defined, that's an
oversight. The HTML spec, as far as I am aware, _does_ define the behaviour of
its APIs with respect to other features that introduce IDs (there are many more
than just xml:id).

> I suggest that xml:id be permitted

That's up to you. Only you can decide what specs are in scope for your

> and be preferred over id for the XML serialization

xml:id doesn't seem to do anything that the id="" attribute in HTML doesn't
already do, so recommending that people use it seems like a bad idea.

> while being forbidden in the HTML serialization. 

It's not forbidden, it's impossible.

> Whatever the decision may be, please make it clear in
> the text.

It's not clear to me that there is any relevant decision to make clear in the

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, 7 February 2011 22:28:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:40 UTC