W3C home > Mailing lists > Public > xml-uri@w3.org > July 2000

Latest XLink Candidate Recommendation

From: Eric van der Vlist <vdv@dyomedea.com>
Date: Fri, 07 Jul 2000 18:13:56 +0200
Message-ID: <396601C4.C50D600B@dyomedea.com>
To: xml-uri@w3.org
Reading the latest XLink Candidate Recommendation [XLk] to cover it for
XMLfr [Xfr], I came over some lines which rang a bell :

> The value of the role or arcrole attribute must be a URI reference as 
> defined in [IETF RFC 2396]. The URI reference identifies some resource
> that describes the intended property. When no value is supplied, no 
> particular role value is to be inferred. Disallowed URI reference 
> characters in these attribute values must be specially encoded as 
> described in 5.4 Locator Attribute (href).

The context is different than namespaces but basically I see it as still
using a URI reference to identify an abstract type and I wonder if the
spec shouldn't answer questions such as :

 - are relative references allowed ?
 - how should they be processed ?
 - when are 2 semantic attributes considered as equal ?

to avoid letting the answers to the application designers.

This is a question for the linking WG and I have already posted [XLC] it
as such.

If I bring it here, it's because I wonder if the answer shouldn't be
coherent with the one which is given to the namespaces URIs and that
this forum has already worked a lot on a similar subject.

IMHO, it would be preferable to keep them consistent (the concepts would
be easier to explain to XML users and to implement in XML tools).


[XLk] : http://www.w3.org/TR/xlink/
[Xfr] : http://xmlfr.org/actualites/tech/000706-0002.xml
[XLC] :
Eric van der Vlist       Dyomedea                    http://dyomedea.com
http://xmlfr.org         http://4xt.org              http://ducotede.com
Received on Friday, 7 July 2000 12:10:22 UTC

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