W3C home > Mailing lists > Public > public-qt-comments@w3.org > August 2002

op:concatenate vs. xf:concat

From: Jeni Tennison <jeni@jenitennison.com>
Date: Mon, 19 Aug 2002 19:45:28 +0100
Message-ID: <109623754701.20020819194528@jenitennison.com>
To: public-qt-comments@w3.org


It isn't an issue in XPath because the op:concatenate operator is an
',' operator rather than a function, but having two
operators/functions that have very similar names but do completely
different things is very confusing in the Data Model WD.

The definition of infoitem-to-text-nodes() in Section 4.7.4 of the
Data Model WD, for example, uses both op:concatenate() and xf:concat()
in the same expression. I found it hard to understand what was going
on until it came to me that op:concatenate() must be combining
sequences while xf:concat() combines strings.

Perhaps op:concatenate's name could be changed to something more
explicit, such as op:construct-sequence?


Jeni Tennison
Received on Monday, 19 August 2002 14:45:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:56:43 UTC