W3C home > Mailing lists > Public > www-xml-query-comments@w3.org > September 2001

RE: [xsl] XQuery 1.0 and XPath 2.0 Functions and Operators Versio n 1.0

From: <DPawson@rnib.org.uk>
Date: Wed, 5 Sep 2001 10:39:51 +0100
Message-ID: <9B66BBD37D5DD411B8CE00508B69700FE7A415@pborolocal.rnib.org.uk>
To: xsl-list@lists.mulberrytech.com
Cc: www-xml-query-comments@w3.org
DC wrote:
> XQuery 1.0 and XPath 2.0 Functions and Operators Version 1.0
> W3C Working Draft 27 August 2001
> http://www.w3.org/TR/2001/WD-xquery-operators-20010827

Couple of funnies in there David,
for example, 
3.3.3 xf:token (string)
  is this expected to 'tokenise' a string as per
saxon:tokenize(string-1, string-2?) which it appears not to follow,
or is it seperate? Not very well explained and no examples.
why else would you want a token, other than in generating element names?
 I would have preferred something equivalent to saxon:tokenize(str, str)


3.3.4 xf:language (string)
  Is this pure magic? Or will xpath2 contain all the dictionaries of the
world?
  xf:language ('le weekend')  is that french or English?

3.3.10.1 Signature
xf:ENTITY(string $srcval) => ENTITY 

I thought that entities were expanded prior to a parse, hence would not
be available to the xslt/xpath environment?


3.5 Functions on String Values
    A case insensitive version of each of many of these would be a useful
addition.
xf:starts-with
xf:ends-with
xf:codepoint-contains
xf:substring-before/after
xf:replace
xf:contains

4.1.3.1 Signature
xf:boolean-from-string(string $srcval) => boolean 
The effective value is the value returned by upper-case($srcval). 
?????? Is this not contr to xpath1? There's nothing intuitive 
about it. And why upper case?

10.2.8 xf:copy
10.2.8.1 Signature
xf:copy(node $srcval) => node 

xf:shallow exists, yet this is xf:copy?
  Irregular, why not xf:deep-copy and xf:shallow-copy
to make it explicit what's happening.


11.4 Functions on Sequences
  No clear definition of what type of sequence is being
discussed. Sequence of nodes? Integers? anytype?


11.4.9 xf:sort
11.4.9.1 Signature
xf:sort(anyType* $srcval, anyURI $collation) => anyType* 

For this and reverse-sort I would like to see a 
case-insensitive sort capability.

11.5.5.1 Signature
xf:intersect(anyType* $parameter1, anyType* $parameter2) => anyType* 

Glad to see this one included!

11.5 I don't see a 'member' type of function.
  To answer the question is nodeX a member of node-setY ?

  Similarly a 'unique' type of function is commonly asked for,
   Return all unique members of this set, second param is
   the definition of 'unique' e.g. unique by element content
   or unique by attribute content.

Issue 67, Should duplicates be eliminated for count() and sum()?
  yes, very clearly IMHO.





Regards DaveP
************* snip here **************




- 

NOTICE: The information contained in this email and any attachments is 
confidential and may be legally privileged. If you are not the 
intended recipient you are hereby notified that you must not use, 
disclose, distribute, copy, print or rely on this email's content. If 
you are not the intended recipient, please notify the sender 
immediately and then delete the email and any attachments from your 
system.

RNIB has made strenuous efforts to ensure that emails and any 
attachments generated by its staff are free from viruses. However, it 
cannot accept any responsibility for any viruses which are 
transmitted. We therefore recommend you scan all attachments.

Please note that the statements and views expressed in this email 
and any attachments are those of the author and do not necessarily 
represent those of RNIB.

RNIB Registered Charity Number: 226227

Website: http://www.rnib.org.uk 
Received on Wednesday, 5 September 2001 05:45:14 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:21:13 UTC