- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Tue, 29 May 2012 17:51:38 +0200
- To: Christoph Päper <christoph.paeper@crissov.de>
- CC: www-style list <www-style@w3.org>, public-media-fragment@w3.org
On 2012-05-29 15:54, Christoph Päper wrote: > Julian Reschke: > >> note that HTML5 (via DOMCORE) closed the door on extending the identifier format, because it makes pretty much everything a legal id. > > Do you mean this bit?<http://www.w3.org/TR/domcore/#concept-id>: > >>> An element has an ID if it has an id attribute whose value is not the empty string. >>> The ID is that attribute's value. Yes. > That doesn’t seem to say anything about the use of IDs in fragment identifiers, where they could be percent-escaped as necessary. That means > > <a id="foo=bar"> > > should be referenced by > > #foo%3Dbar > > and not by > > #foo=bar So how do you reference an HTML element with the id of "foo%3Dbar" then? > The “scroll to the fragment identifier” algorithm currently described in HTML5 could (and probably should) be extended in step 7 to support other methods than simple IDs, names and keywords.<http://www.w3.org/TR/html5/Overview#scroll-to-the-fragment-identifier> > > Note that there is a reference to RFC 3023 for HTML documents with an XML MIME type. This in turn mentions (a WD of) XPointer. > <http://tools.ietf.org/html/rfc3023#page-15> HTML should restrict the set of valid IDs (just like HTML4 or XML did), so that new addressing schemes can be deployed. Best regards, Julian
Received on Tuesday, 29 May 2012 15:57:18 UTC