- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Sun, 29 Jan 2006 19:40:56 +0100
- To: Chris Lilley <chris@w3.org>
- Cc: www-svg@w3.org
* Chris Lilley wrote: >BH> From http://www.w3.org/TR/2005/WD-SVGMobile12-20050413/linking.html >BH> section 14.3.2 > >BH> [...] >BH> Note: characters in fragment identifiers that are outside the >BH> repertoire of US-ASCII must be encoded using UTF-8 and %HH escaping >BH> if the value of the XLink href attribute is converted to a URI for >BH> resolution. [RFC3987] >BH> [...] > >BH> Please change the draft such that this statement is limited to cases >BH> where the fragment identifier participates in this "resolution" pro- >BH> cess and such that it does not contradict RFC 3987. >We have altered the text to state > > Note: since fragment identifiers are stripped from IRIs before > resolution, there is no need to escape any characters in fragments > that are outside the repertoire of US-ASCII. That's incorrect, if the resolution process requires to give the full resource identifier including the fragment identifier and the protocol requires use of URIs instead of IRIs, the fragment identifier part must be escaped. This text also encourages implementers to assume they don't have to unescape the fragment before further processing, this is a common interoperability problem and should be discussed in detail. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Sunday, 29 January 2006 18:40:12 UTC