Re: XLink 1.1: xlink:href requirements

/ Bjoern Hoehrmann <derhoermi@gmx.net> was heard to say:
| Did the TAG, XCG, HCG, and I18N Core WGs review this definition?

No, because the changes are entirely editorial. Strings such as

  http://www.example.org/Some Path To/Somefile(1)

have always been allowed in XLink href attributes and have always been
allowed in XML system identifiers. The changes that we're making are
purely editorial.

| Why is
| this put in the XLink 1.1 draft rather than a more appropriate place?

Historically, it was introduced in XLink 1.0 and has been referenced
From several other specifications. We agree that XLink is a strange
place for this text. So, in fact, our plan is to migrate this text
into a more reasonable place (e.g., XML 1.0 4e). That's why 5.4.1 is a
seperate section. When it finally does appear in a "better place",
we'll use an erratum to remove 5.4.1 and point to it in the "better
place".

It'll take time to get the text into a better place and we'd like to
finish XLink before that occurs, so we're leaving it where it has
always (historically) been for the time being.

| I don't think it's a good idea to encourage silent error recovery here,
| nor does it seem to be a good idea to allow the space for these general
| purpose "XML resource identifiers" since that precludes use e.g. of
| "space-separated lists of XML resources identifiers".

Only in those places where they have *never been allowed*. There's
nothing about these changes that will have any impact on
space-separated lists of URIs like xsi:schemaLocation.

Does that make sense? With these considerations in mind, are you
satisified with this resolution?

                                        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.

Received on Wednesday, 15 February 2006 17:20:31 UTC