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

Re: QNames vs. NCNames

From: Norman Walsh <Norman.Walsh@Sun.COM>
Date: Mon, 27 Nov 2006 09:30:17 -0500
To: public-xml-processing-model-wg@w3.org
Message-ID: <87odqtufly.fsf@nwalsh.com>
/ ht@inf.ed.ac.uk (Henry S. Thompson) was heard to say:
| 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?

A little of both. The name of a parameter has to be token because
we allow '*' and 'foo:*' in addition to proper QNames. The names
of the built-in constructs should be QName, I think.

                                        Be seeing you,

Norman Walsh
XML Standards Architect
Sun Microsystems, Inc.

Received on Monday, 27 November 2006 14:31:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:41 UTC