W3C home > Mailing lists > Public > www-xml-linking-comments@w3.org > October to December 2000

Re: Problem with local resources

From: Eve L. Maler <eve.maler@east.sun.com>
Date: Thu, 07 Dec 2000 12:46:53 -0500
Message-Id: <>
To: "Benkley,Carl W." <cbenkley@mitre.org>
Cc: www-xml-linking-comments@w3.org
Hello Carl-- You can make the extended link element itself participate in 
the link, but only by making it a "remote" resource (that is, using a 
locator element to point to it, if you wish by using an XPath expression 
with "ancestor::" in it.  So what you seek isn't prohibited, but it isn't 
optimized for, either.

I can see utility in optimizing for this, but it might also cause design 
problems.  For example, would we need to add "resourcerole" and 
"resourcetitle" attributes to extended links to allow them to have a full 
complement of metadata?...

 From a process perspective, it's unlikely that we'd be able to add such a 
feature without having to go back to Second Last Call.  However, I'll bring 
it up.

Hope this helps,


At 03:07 PM 12/6/00 -0500, Benkley,Carl W. wrote:
>Consider an extended link with a local resource.  The Xlink spec says
>that the local resource must be defined as an Xlink resource element
>type which is a child of an Xlink extended element type.
>Why can't the extended element type also be a possible resource element
>type?  There doesn't seem to be any logical reason to prohibit this.
>However, there is no Xlink label attribute identified for the Xlink
>extended element type, so it can't be done within the context of the
>Xlink spec.
>Carl Benkley
>MITRE Corporation

Eve Maler                                          +1 781 442 3190
Sun Microsystems XML Technology Center    eve.maler @ east.sun.com
Received on Thursday, 7 December 2000 12:53:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:32:22 UTC