[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Safe-guarding codepoints-to-string() from wrong in

Subject: Re: Safe-guarding codepoints-to-string() from wrong input
From: Abel Braaksma <abel.online@xxxxxxxxx>
Date: Thu, 21 Dec 2006 09:21:51 +0100
Re:  Safe-guarding codepoints-to-string() from wrong in
Florent Georges wrote:
  The intent of XSLT transformations is not to work with
characters, but with the data model defined in [XDM].  Of
course, there are a lot of functions to operate on strings,
but dealing with the codepoints directly in the stylesheet
is not a frequent thing IMHO.

The data model and its lexical representation are two
different beasts.


I understand that. But with the advent of unparsed-text() and related functions, plus removing the necessity of having an input document, XSLT opened up a whole new world of applications of data transformations. As a matter of fact, I find myself working daily doing transformations of legacy text-based data formats.

But I'm aware of the discussions that have been in the past about XML compliant data and if XSLT should be able to treat non-XML characters (through unparsed-text() or otherwise). For this version, partly for security reasons (buffer overflow etc), it was decided against facilities for non-XML compliant data. Unfortunately. Perhaps in a next version (in another decade?).

Cheers,
-- Abel

Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.