- From: John E. Simpson <simpson@polaris.net>
- Date: Wed, 19 Jan 2000 10:43:38 -0500
- To: "'www-xml-linking-comments@w3.org'" <www-xml-linking-comments@w3.org>, "'xlxp-dev@fsc.fujitsu.com'" <xlxp-dev@fsc.fujitsu.com>
The definition of "out-of-line link" provided in Terminology [1.3] seems to imply that multi-directional traversal may be defined only in the context of an out-of-line link. However, use of the arc-type element (whose purpose is to define the direction of traversal) is not restricted to out-of-line extended links. Particularly, in [3.1.4], the following example is used: <xlink:arc /> The commentary preceding that example says: "If no arc-type elements are provided in an extended link, then by extension the missing from and to values are interpreted as standing for all the roles in that link." If I've read this correctly, the implication is that (to use the parent and child roles to which this example applies) the locators with a parent role point to the locators with a child role, AND the child locators point to the parent locators -- i.e., all links among the locators are multi-directional. [As an aside: presumably, in this example, bi-directional links are established not only between every parent and every child, but also between every parent and every other parent, and between every child and every other child -- is that right?] If I've read and understood both portions of the WD correctly, I think the definition of "out-of-line link" can simply be amended by removing the words "for supporting multidirectional traversal and." =================================================================== John E. Simpson | I spilled spot remover on my dog. simpson@polaris.net | He's gone now. http://www.flixml.org | (Stephen Wright)
Received on Wednesday, 19 January 2000 10:42:59 UTC