W3C home > Mailing lists > Public > www-xml-linking-comments@w3.org > January to March 2006

Re: XLink 1.1: xlink:href requirements

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Mon, 23 Jan 2006 21:48:37 +0100
To: Norman Walsh <Norman.Walsh@Sun.COM>
Cc: www-xml-linking-comments@w3.org
Message-ID: <m4gat114cv5u6jnrkp89obfqat3shf6don@hive.bjoern.hoehrmann.de>

* Norman Walsh wrote:
>|>|   http://www.w3.org/TR/2005/WD-xlink11-20050707/ section 5.4 notes
>|>| "The value of the href attribute must be an IRI reference as defined in
>|>| [IETF RFC 3987] or must result in an IRI reference after the escaping
>|>| procedure described below is applied." Except for the space character,
>|>| applying the algorithm would just render illegal IRIs XLink-compliant;
>|>| I do not really see how this would make sense, please replace this
>|>| part of the draft with something more reasonable.
>|>I'm sorry, could you please explain your comment in more detail, I don't
>|>understand your comment.
>| The requirement is that the value must be a IRI reference after applying
>| the IRI reference -> URI reference conversion algorithm. Since all URI
>| references are said to be IRI references, applying the algorithm makes a
>| difference iff a string that is not an IRI reference is converted to a
>| URI reference. What's the point?
>The point is to allow xlink:href="http://example.org/path/file with spaces"
>to be treated as if the author had written the "correct" value:
>Experience with HTML suggests that authors will frequently make this
>mistake and that most deployed software "does the right thing". XLink
>explicitly defines what the right thing is in this case.

You have isValidIRI(convertIRItoURI(escapeSpace(x))) while you seem to
desire isValidIRI(escapeSpace(x)), so keeping things as is does not
address my concern.
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 Monday, 23 January 2006 20:48:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:32:25 UTC