Re: XLink 1.1: Schema issues

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm sorry we don't seem to be converging on this.  You seem to have a
schema design methodology in view which carries with it requirements I
don't think are widely shared.

Anyone defining a schema for the XLink namespace is free to do so in
any way they choose, and indeed there are a number of alternative
schema documents for the XLink 1.0 available on the web.  All of them
use only one namespace, and several define components by name beyond
those named in the normative part of the XLink spec.

The schema document in the draft XLink 1.1 spec. attempts to provide
not only definitions for the attributes with normative definitions,
but also building blocks to assist XLink users.  It does so in a
pretty straightforward and conservative way, in a single namespace and
hence in a single schema document.

I'm left thinking this is a matter of taste in schema design, and as
we know, tastes differ.  I'm sorry I haven't understood your arguments
as indicating what substantive technical requirement would be
addressed by using a distinct namespace for some of the names, that
is, what you could do with such a schema that you couldn't do with the
one in the current draft.

ht
- -- 
 Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
                     Half-time member of W3C Team
    2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
            Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFD43fHkjnJixAXWBoRAjvXAJ91YR1tf/q+CgRQMawHI5EHKX2DcACaA235
dzpfWdKdqMKtijx9eHNpFFA=
=imGp
-----END PGP SIGNATURE-----

Received on Friday, 3 February 2006 15:33:41 UTC