W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2005

[Bug 2259] [xqueryx] xqx:constructorFunctionExpr

From: <bugzilla@wiggum.w3.org>
Date: Tue, 20 Sep 2005 12:01:01 +0000
To: public-qt-comments@w3.org
Message-Id: <E1EHgo1-0007ni-3n@wiggum.w3.org>


------- Additional Comments From davidc@nag.co.uk  2005-09-20 12:01 -------
>  then what harm is there?

It increases the burden on an XQueryX processor (it has to implement
both elements) and (much) more importantly it works directly against the
(presumed) intent of XQueryX. Having an XML syntax means that it is much
easier to analyze and transform a Query Expression, however whenever you
have multiple ways of encoding the same thing (in any language) such
analysis becomes harder, and becomes exponentially harder the more
duplicated terms you have. (Which is why parallel bug reports argue
against node tests being encoded as XQueryX function calls (and boolean
equality tests being encoded as AttributeConstructors).

Some redundancy is probably inevitable but there is no need (and some
harm) in introducing distinctions in XQueryX that are not present in

Received on Tuesday, 20 September 2005 12:01:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:08 UTC