Re: XLink 1.1: xlink:href requirements

/ Bjoern Hoehrmann <derhoermi@gmx.net> was heard to say:
| * Norman Walsh wrote:
|>/ Bjoern Hoehrmann <derhoermi@gmx.net> was heard to say:
|>|   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:
xlink:href="http://example.org/path/file%20with%20spaces".

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.

                                        Be seeing you,
                                          norm

-- 
Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc.
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.