W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > November 2006

QNames vs. NCNames

From: Henry S. Thompson <ht@inf.ed.ac.uk>
Date: Thu, 23 Nov 2006 16:46:15 +0000
To: public-xml-processing-model-wg@w3.org
Message-ID: <f5bbqmyglgo.fsf@erasmus.inf.ed.ac.uk>

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

In the current draft, the names of ports, pipelines and steps have
type 'QName', whereas the names of parameters and the built-in
constructs (viewport etc.) have type 'token'.

I could _maybe_ see the logic for not using QNames for parameter
names, but seems difficult to explain why e.g. an XSLT step is named
with a QName but a 'for-each' is not. . .

Is this a bug or a feature?

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)

iD8DBQFFZdBbkjnJixAXWBoRAuC+AJ9KrRJQG1iOXiBMS7ViNaUvkGG+awCfW6LD
2O4z/Qh607u87zk651DT9Ls=
=miDR
-----END PGP SIGNATURE-----
Received on Thursday, 23 November 2006 16:46:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:49 GMT