[
Lists Home |
Date Index |
Thread Index
]
I think I understand the idea behind the design of XLink. Here's an example
of how it breaks down.
Say, in XHTML2, you have a form label. <label>
Now, you want the content of the label to come from an out-of-document
source.
XLink : <label xlink:href="sometext.html" xlink:type="simple"
xlink:show="embed" xlink:actuate="onLoad">...
XHTML2: <label src="sometext.html">...
Now, to the same element, you want to establish a conventional link, so that
users can "click" on it and navigate to another page.
XHTML2: <label src="sometext.html" href="gohere.html">...
XLink : ???
When combining vocabularies, the chances of something like this happening
increase exponentially. Refactoring (so that the above construct would use
two elements), or using complex links often is either not possible or too
much hassle when you simply want to combine two pre-defined vocabularies.
.micah
-----Original Message-----
From: DuCharme, Bob (LNG-CHO) [mailto:bob.ducharme@lexisnexis.com]
Sent: Wednesday, January 21, 2004 11:23 AM
To: XML Developer List
Subject: RE: [xml-dev] RDDL(2): new version up
>>Why does XLink have problems with mixed vocabularies?
>Because it uses a single attribute name (xlink:href) for multiple purposes.
The idea is that instead of using n different attributes for n purposes, one
attribute, href, is used to identify the URL and others
(http://www.w3.org/TR/xlink/#link-semantics) are used to identify the
purpose.
Bob
|
