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

Re: Nested simple, onRequest links and traversal failure

From: Norman Walsh <Norman.Walsh@Sun.COM>
Date: Mon, 23 Oct 2006 12:34:50 -0400
To: Jonathan Watt <jwatt@jwatt.org>
Cc: www-xml-linking-comments@w3.org
Message-ID: <87zmbnyor9.fsf@nwalsh.com>
/ Jonathan Watt <jwatt@jwatt.org> was heard to say:
| Dear XML WG,
| I don't believe the XLink specification specifies what should happen here:
| While working on some patches for Mozilla's XLink implementation, the
| question has arisen as to what should happen if traversal of a simple,
| onRequest link fails and that link has a simple, onRequest ancestor
| link? Should the UA go on to attempt to traverse the ancestor link? Or
| should failure to traverse the exact link specified to the UA be the
| end of it?
| I'd be grateful if you could resolve this issue.

Apologies for the long delay in responding to your issue.

The XLink specification states "If a simple-type element contains
nested XLink elements, such contained elements have no XLink-specified
relationship to the parent link."

The XLink specification makes no effort to impose constraints on the
error recovery behavior of applications. In light of the fact that
there is no XLink-specified relationship between the two links, I'd
personally prefer a choice of error recover behaviors.

Please let us know if this response satisfies your comment.

                                        Be seeing you,

Norman Walsh
XML Standards Architect
Sun Microsystems, Inc.

Received on Monday, 23 October 2006 16:35:01 UTC

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