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

RE: SkunkLink: a skunkworks XML linking proposal

• To: 'Bob DuCharme' <bobdc@s...>, xml-dev@l...
• Subject: RE: SkunkLink: a skunkworks XML linking proposal
• From: "Bullard, Claude L (Len)" <clbullar@i...>
• Date: Thu, 9 Jan 2003 08:14:24 -0600

The beauty of it is that for human users (consider 
why we do hypertext instead of relational records), 
the link is inside a descriptive context because 
the author put it there.  Not only do we know it 
is a CNN link, it is about the weather, we know 
it is about the weather in Los Angeles, it is 
timely (BEFORE flying), and the author considers 
it important (what is it about the weather that 
can't wait).  As a sign, it does its job well. 
As a control, it does its job well.

The task you suggest has analogs in Costello's 
recent emails about what is high value information.

len

From: Bob DuCharme [mailto:bobdc@s...]

At its core, a link only needs a single piece of information: the locator 
for a remote resource. If that's all there is, the resource holding it is 
the implied other end of the relationship being expressed, and you have a link:

<para>Check <link>http://www.cnn.com/WEATHER</link> before you fly to Los 
Angeles.</para>

I'll admit, before Len points it out, that for better or worse this 
particular URI itself carries some additional semantic information; you 
don't have to follow it to get an idea of where it goes. Still, of all the 
people saying "I've stripped down linking to its essentials," I'm shooting 
for the "most stripped-down" prize.

• Prev by Date: Namespace Selection using SelectionNamespaces property
• Next by Date: Re: ANN: Distributed Registry for Web Services
• Previous by thread: RE: SkunkLink: a skunkworks XML linking proposal
• Next by thread: RE: SkunkLink: a skunkworks XML linking proposal
• Index(es):
  • Date
  • Thread