Review of CURIE Syntax 1.0 draft of 2008-01-22

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

I remain of two minds about the value proposition of this spec., but
in re-reading it the following specific points arose.

Section 1.  "1) [QNames] are NOT intended for use in attribute values"

 This is at best misleading -- W3C XML Schema datatypes, of which
 QName is one, are explicitly and intentionally intended for use to
 define the allowed content of both attributes and elements.

Section 3.  Prefixes and even colons are optional (again/still).

 This is just asking for trouble, in my view, particularly the 'no
 colon' case..  What use cases require default prefixes?  The absence
 of _any_ visible signal seems very dangerous.

Section 3.  "The concatenation of the prefix value associated with a
              CURIE and its reference MUST be an IRI [IRI]."

 Just what production is meant here?  I.e. the IRI production itself
 (I hope so) or the IRI-reference production (I hope not)?

Section 5.  "lexical value"

 This is at best a confusing phrase -- I suggest sticking with
 "lexical form" instead of "raw CURIE" and "value as IRI" for "lexical
 value" (or "value as URI", depending on which you actually mean).


If this spec. is in fact intended to define an XSD datatype, a schema
document, or at least a simple type definition, would be a good
addition.

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)

iD8DBQFHsuPqkjnJixAXWBoRAmrkAJ4sStldlfbD2jniciVHiS50gKfCZgCbBN2z
e7VXMDftUZljF8ogqN1yDeg=
=Hi8U
-----END PGP SIGNATURE-----

Received on Wednesday, 13 February 2008 12:34:59 UTC