[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: XLink and mixed vocabulary design

• To: 'Micah Dubinko' <MDubinko@c...>, "'DuCharme, Bob (LNG-CHO)'" <bob.ducharme@l...>, XML Developer List <xml-dev@l...>
• Subject: RE: XLink and mixed vocabulary design
• From: "Bullard, Claude L (Len)" <clbullar@i...>
• Date: Wed, 21 Jan 2004 14:23:03 -0600

You do.  Here's where it falls apart:

"conventional" 

<a href="" isn't a clever innovation; 
it's a vestige of the 1960s.  The 80/20 
approach to lighting a fire is to pour 
gasoline on the wood and toss a lit match 
on it. It's simple and it works but don't try 
it in a small stove.

Context matters.

len


From: Micah Dubinko [mailto:MDubinko@c...]

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.

• Prev by Date: Re: Genx
• Next by Date: RE: Sweet nostalgia
• Previous by thread: XLink and mixed vocabulary design
• Next by thread: RE: XLink and mixed vocabulary design
• Index(es):
  • Date
  • Thread