Re: [xsl] xml to xml issue in XSLT2.0

Subject: Re: [xsl] xml to xml issue in XSLT2.0
From: "G. Ken Holman" <gkholman@xxxxxxxxxxxxxxxxxxxx>
Date: Tue, 20 Nov 2007 08:12:18 -0500
At 2007-11-20 12:48 +0000, you wrote:
Ken, what do you mean by a serialization surrogate?

On 20/11/2007, G. Ken Holman <gkholman@xxxxxxxxxxxxxxxxxxxx> wrote:
> At 2007-11-20 11:34 +0000, Colin Adams wrote:
> >I would think that a private code point would be an ideal separator.
> I'm increasingly using private characters as serialization
> surrogates.

The example I use in class is to map &#xe000; to "<" and &#xe001; to ">" for non-XML sequences in my stylesheet such as ASP directives by using xsl:output-character. That way I can write well-formed XSLT and let the serializer worry about putting out naked characters.

What if I was using those characters in my stylesheet and two trading partners agreed to use the same private characters for their own purpose? Their data characters would be lost in the serialization.

Unlikely, but I think more likely than &#xd; being coded in someone's XML.

I hope this helps.

. . . . . . . . . . . . Ken

Comprehensive in-depth XSLT2/XSL-FO1.1 classes: Austin TX,Jan-2008
World-wide corporate, govt. & user group XML, XSL and UBL training
RSS feeds:     publicly-available developer resources and training
G. Ken Holman                 mailto:gkholman@xxxxxxxxxxxxxxxxxxxx
Crane Softwrights Ltd.
Box 266, Kars, Ontario CANADA K0A-2E0    +1(613)489-0999 (F:-0995)
Male Cancer Awareness Nov'07
Legal business disclaimers:

Current Thread