- From: Eve L. Maler <Eve.Maler@east.sun.com>
- Date: Wed, 12 Jul 2000 10:55:11 -0400
- To: Elliotte Rusty Harold <elharo@metalab.unc.edu>
- Cc: www-xml-linking-comments@w3.org, xlxp-dev@fsc.fujitsu.com
Thanks, we'll add the issue. This has come up a couple of times, but we always ended up keeping the terms we had because the proposed alternatives didn't suit. This will be our last chance to get it right! :-) Eve At 10:07 AM 7/12/00 -0700, Elliotte Rusty Harold wrote: >I'm concerned that some of the terminology in the XLink CR is a little >inconsistent and unnecessarily confusing. In particular, it bothers me >that a resource type element only refers to local resources whereas a >locator element refers to remote resources. > >For example, consider this paragraph from a chapter I'm working on about >the latest version of XLink: > >A resource element can and generally does have the same attributes as a >locator element; that is, xlink:label, xlink:role, and xlink:title. >These all have the same semantics as they do for locator elements. For >instance, the label can be used so arcs can connect to and from >resources. An arc can connect a resource to a resource, a resource to a >locator, a locator to a resource, or a locator to a locator. Arcs really >don't care whether resources are local or remote. > >Actually all arcs connects rtesources to resources. I think that's less >clear than this: > >A local element can and generally does have the same attributes as a >locator element; that is, xlink:label, xlink:role, and xlink:title. >These all have the same semantics as they do for locator elements. For >instance, the label can be used so arcs can connect to and from local >elements. An arc can connect a local to a local, a local to a locator, a >locator to a local, or a locator to a locator. Arcs really don't care >whether resources are local or remote. > >What I'm proposing is to rename the type of the local resource from >resource to something else such as "local". The reason is that a >resource element doesn't really represent all kinds of resources, just >local ones. I'm not wedded to the name "local". I just don't want it to >be "resource". > >Another possibility is to rename the resource type to local and the >locator type to remote, though I suppose that might be a little >confusing when the locator locates an element in the same document. Or >we could rename locator "uri" and resource "here". That more clearly >indicates what's expected in the attribute value. -- Eve Maler +1 781 442 3190 Sun Microsystems XML Technology Center elm @ east.sun.com
Received on Wednesday, 12 July 2000 10:54:43 UTC