Re: XLink 1.1: Xlink vs "legacy" linking

* Norman Walsh wrote:
>/ 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).

What do you mean by "can"? Can I make a fully conforming XHTML+XLink
user agent that does not observe any of the XLink processor require-
ments? All I want to do is to make a XHTML+XLink user agent that fully
complies with all XLink and XHTML requirements, I think this is not
currently possible, so either this is made possible or the draft needs
to point out that making such a user agent is a bad idea. I'd think it's
a bad idea. I'm happy with this beeing a bad idea, but it needs to be
clear from the draft.
-- 
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 21:30:36 UTC