Re: QNames vs. NCNames

/ 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,
                                          norm

-- 
Norman Walsh
XML Standards Architect
Sun Microsystems, Inc.