Re: XLink 1.1: Xlink vs "legacy" linking

/ Bjoern Hoehrmann <derhoermi@gmx.net> was heard to say:
| * Norman Walsh wrote:
|>There are no elements in the XLink namespace. Your question, if I
|>understand it, is what should this mean:
|>
|>  <html:a href="x" xlink:href="y" ...>
|
| I am not interested in what this "means", I am interested in whether
| it makes sense to make a XHTML+XLink user agent that can process
| XHTML+XLink documents and if, what should happen for a fragment as
| above when the user activates the link. You are basically saying it
| is clear what happens for an XHTML-only user agent and for a XLink-
| only user agent; I do not disagree, but that's not what I am talking
| about.

The Core WG has considered this question again. As far as we can see,
the XHTML specification, if it chose to adopt XLink, could say what a
UA should do. The XLink specification describes precisely what XLink
semantics the element has. There's nothing more that the XLink
specification *can* say. An XHTML UA that encounters this (invalid)
XHTML element is free to do whatever the XHTML speicification says it
can do. If it's also an XLink application, then it can implement the
XLink semantics if it wants (or at user request).

Please let us know if this satisfies your concerns.

                                        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.