(In reply to comment #0)
> http://www.w3.org/International/2005/02/xq-func-op-review.html Comment ID: 8

Is there a concat operation that includes normalization splicing at the contact
point? This would be very helpful, and ideally should be the default, because
this may be the most efficient way to maintain a certain normalization. The same
applies to string-join and potentially other operations.

You can do

normalize-unicode(concat($a, $b))

If vendors think this is an important use case then they can easily detect this
pattern and optimize it. 

Michael Kay
(personal response)

(In reply to comment #2)
> You can do
> 
> normalize-unicode(concat($a, $b))
> 
> If vendors think this is an important use case then they can easily detect this
> pattern and optimize it. 
> 
> Michael Kay
> (personal response)

Could you give "normalize-unicode(concat($a, $b))" as an example in sec. 
7.4.1.1 (the one on concat) and explain the role of the combination of these 2
functions, e.g. "The application of normalize-unicode is the most efficient way
to maintain a certain normalization for the concat operation"? This would
resolve the commment (in my view).

Felix Sasaki
(personal response)

(In reply to comment #1)
> (In reply to comment #0)
> > http://www.w3.org/International/2005/02/xq-func-op-review.html Comment ID: 8
> 
> Is there a concat operation that includes normalization splicing at the contact
> point? This would be very helpful, and ideally should be the default, because
> this may be the most efficient way to maintain a certain normalization. The same
> applies to string-join and potentially other operations.

the i18n-core-wg reached consensus about this comment in this version, at the
telecon 25 may 2005.

The joint WGs agreed on the 6/7/2005 telcon to add an example to the discussion
of fn:concat that explains how fn:normalize-unicode can be used to normalize the
result of an fn:concat operation.

Ashok Malhotra

consenus of the i18n-core-wg (telecon 21 May 2005):
The working group thanks you very much for your resolution and regards the bug 
as closed.
Regards,
Felix Sasaki