RE: [xsl] Tokenized values

Subject: RE: [xsl] Tokenized values
From: Mulberry Technologies List Owner <xsl-list-owner@xxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 25 Jul 2001 12:21:14 -0400
>Reply-To: <mhkay@xxxxxxxxxxxx>
>From: "Michael Kay" <mhkay@xxxxxxxxxxxx>
>To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
>Subject: RE: [xsl] Tokenized values
>Date: Wed, 25 Jul 2001 09:21:49 +0100
>Message-ID: <002201c114f0$93416e90$91363c3e@PCUKMKA>
>MIME-Version: 1.0
>
>> According to the XML Spec there are several tokenized types (IDREFS,
>> ENTITIES, NMTOKENS
>> http://www.w3.org/TR/2000/WD-xml-2e-20000814#NT-TokenizedType)
> which are
>valid for attribute values. How would one handle these values in XSL? I'm in
>the middle of building a recursive named template to parse out the values
>but then when I'm done, all I get is a series of result trees.
>
>Is there a reason why XSL doesn't include something like
>
><xsl:variable name="values" select="split(@something)" />
><xsl:apply-templates select="$values/text()" />
>
>Saxon has an extension saxon:tokenize() which you mighht consider. I believe
>it's been cloned in one or two other products as well.
>
>Mike Kay
>Software AG


-- 
======================================================================
B. Tommie Usdin                        mailto:btusdin@xxxxxxxxxxxxxxxx
Mulberry Technologies, Inc.                http://www.mulberrytech.com  
17 West Jefferson Street                           Phone: 301/315-9631
Suite 207                                    Direct Line: 301/315-9634
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
  Mulberry Technologies: A Consultancy Specializing in SGML and XML              
======================================================================

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Current Thread