RE: [xsl] keys and idrefs - XSLT2 request?

> Speculating a bit - given all the talk of 'sequences' in the
> XPath/XQuery documents, perhaps tokenising on whitespace will be
> fairly automatic, especially if you have access to the DTD or XML
> Schema and can work out that a particular value is a IDREFS, ENTITIES
> or other 'list' type.
> In other words, an XSLT 2.0 processor might look at the 'controls'
> attribute, go "aha, an IDREFS attribute" and treat it as a sequence of
> IDREF values. *If* that were the case, then:
> <xsl:key name="control" match="process" use="@controls" />

My preference certainly, the backwards compatibility issue,
wouldn't that be addressed by the stylesheet version?

> Which is all to say that I don't think we'll have to worry about
> tokenising on whitespace in XPath 2.0. *But* we might want to ask for
> tokenisation on other characters (e.g. commas) - I can't see a
> xf:tokenize() function to create sequences in the F&O document...

I would certainly support its addition to 2.0.
I find saxon:tokenize () extremely useful, and invoke it 
quite regularly. Pity about the spelling:-)

Use case:
  DB output, subfields are token split using $ symbol.
   xf:for-each select= xf:tokenise (., '$')

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 

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


Received on Wednesday, 10 October 2001 04:09:33 UTC