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

Re: An XLink question

• From: "W. Eliot Kimber" <eliot@d...>
• To: xml-dev@i...
• Date: Sun, 13 Dec 1998 14:57:11 -0600

At 05:34 PM 12/13/98 +0100, Patrice Bonhomme wrote:
>
>Hi,
>
>I've got a question concerning the XML Link "show" mechanism. I've got 2 
>documents, a primary one and a "virtual" one that owns some links to the
first 
>one. And i have a problem with a link that contains another link and the way 
>they will be evaluated.
>
>My primary document:
><DOC1>
>  <A id="a"><B/></A>
>  <C id="c"/>
></DOC1>
>
>My virtual resource:
><DOC2>
>  <LINK xml:link="simple" href="DOC1#id(a)" show="replace">
>    <LINK xml:link="simple" href="DOC1#id(c) show="replace"/>
>  </LINK>
></DOC2>
>
>My secong LINK is never evaluated, isn't it ? Does someone already have to 
>deal with this kind of things, primary vs virtual ressources ?

Both links will be "evaluated" (if by "evaluated" you mean processed by an
XLink-aware processor in order to enable traversal). When one gets used
depends on how the user interface enables traversal. For example, if you
click on the presented representation of the inner link you might go
directly to element "c" or you might get a dialog giving you a choice of
which link to traverse.  But not that this is *entirely* dependent on how
the user interface implements traversal initiation, which the XLink
specification says nothing about (nor should it).

If you traverse the outer link and the replace show action is respected,
then you would lose the ability to traverse from the inner link unless you
did a "back" following the first traversal.

This all assumes that actuate="user". If actuate="auto", then all bets are
off,  because there doesn't appear to be any obvious way to satisfy both
actuate requests in any meaningful way.  If I was implementing it, I'd
probably say that the first link in tree order governs, which means the
outer link would be actuated and the inner link would never get a chance to
actuate, because the active document would be DOC1 as soon as the actuation
occurred.

This suggests that actuate="auto" is a dangerous tool that should be used
carefully.

Cheers,

E.
--
<Address HyTime=bibloc>
W. Eliot Kimber, Senior Consulting SGML Engineer
ISOGEN International Corp.
2200 N. Lamar St., Suite 230, Dallas, TX 75202.  214.953.0004
www.isogen.com
</Address>

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • Re: An XLink question
    • From: John Cowan <cowan@l...>

• References:
  • An XLink question
    • From: Patrice Bonhomme <Patrice.Bonhomme@l...>

• Prev by Date: Re: An XLink question
• Next by Date: More tests up on Web site "Chinese XML Now!"
• Previous by thread: An XLink question
• Next by thread: Re: An XLink question
• Index(es):
  • Date
  • Thread