Re: XLink: the architectural issue

> | * Don't tell other people what to do in their name spaces
>
> How does XLink tell anyone what to do in their namespace? XLink says
> how to use the XLink namespace to leverage a set of linking semantics.

I said name spaces, not namespaces... XLink forces the use of xlink syntax
to denote a link, rather than letting a langauge designer determine their
own term.


> | * Don't put metadata in identifiers
>
> Where is that proposed?

It's implied by URI Opacity [1]. In other words, XLink, or at least the
syntax that most people want to use, seems to force the conflation of the
identification of a property (a particular kind of link) and the fact that
it's a link; this is very limiting, as has been outlined elsewhere.


1. http://www.w3.org/DesignIssues/Axioms.html#opaque

Received on Wednesday, 2 October 2002 17:30:00 UTC