- From: Daniel Veillard <Daniel.Veillard@w3.org>
- Date: Mon, 8 May 2000 22:49:02 +0200
- To: Graham Moore <gdm@stepuk.com>, www-xml-linking-comments@w3.org
- Cc: Daniel.Veillard@w3.org, "'Martyn Cutcher'" <mgc@stepuk.com>, "'Jason Markos'" <jsm@step-dpsl.co.uk>
Hi Graham, as precised on the XLink draft, the www-xml-linking-comments@w3.org list is the right place to provide feedback. The last call period for XLink is over but we are still seeking feedback especially from implementor. I will forward this to the list and I invite you to discuss those aspects there. thanks, Daniel On Mon, May 08, 2000 at 01:44:37PM +0100, Graham Moore wrote: > > Hi Daniel, > > I've been working on the next release of X2X which I intended to include > compatibility with 21/02/00. I was please to see the removal of > actuateDefault etc from xlink:link, but have some concerns about the new > role of 'xlink:role' with regard to the arcs. > > My general feeling is that the arc structures are instances and should be > specified as such. I have no problem with some syntax that can create > multiple unique arcs. But with the use of role as the identifier there is no > way to specialise as there is no longer a way to uniquely address an anchor. > > Given: > > <extendedlink> > <loc xlink:href="..." xlink:role="parent" xlink:title="p1" /> > <loc xlink:href="..." xlink:role="parent" xlink:title="p2" /> > <loc xlink:href="..." xlink:role="child" xlink:title="c1" /> > <loc xlink:href="..." xlink:role="child" xlink:title="c2" /> > <loc xlink:href="..." xlink:role="child" xlink:title="c3" /> > <go xlink:from="parent" xlink:to="child" actuate="user" /> > </extendedlink> > > The above generates a number of arcs. If I change a property of an arc after > processing this markup, such as on one of the parent child arcs I want the > actuate to be "auto" then if I try and re-serialise the link containing the > arcs I am unable to do so. > > I think that the change should be made such that the arc markup can address > ID's and Roles. This will allow declarative rules to create multiple links > but allow easy refinement and correct reserialisation of the link and its > arcs. > > In general by not having the unique ID the practice of the link authoring by > refinement becomes extremely complex. > > I hope that these comments are not to late to be considered. > > Cheers > > Graham > > Graham Moore > CTO STEP UK > gdm@stepuk.com -- Daniel.Veillard@w3.org | W3C, INRIA Rhone-Alpes | Today's Bookmarks : Tel : +33 476 615 257 | 655, avenue de l'Europe | Linux XML libxml WWW Fax : +33 476 615 207 | 38330 Montbonnot FRANCE | Gnome rpm2html rpmfind http://www.w3.org/People/all#veillard%40w3.org | RPM badminton Kaffe
Received on Monday, 8 May 2000 16:49:08 UTC