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

Reason for restrictions on RTFs in XSLT 1.0?

Subject: Reason for restrictions on RTFs in XSLT 1.0?
From: steffen.dingel@xxxxxx
Date: Tue, 30 Jan 2001 10:20:38 +0100
reason 1.0
Hi,

I've been working with XSLT for a while now and I often
noticed that the Restrictions on what can be done with
result tree fragments significantly decrease the power
of XSLT. The Restrictions are removed in Version 1.1, but
I still wonder what were the reasons for putting them in 1.0.
Maybe that the impossibility to look into the structure of
a result tree fragment again makes it possible to share parts
of the tree structure of input and output tree in implementations?
But that should still be possible when access to the result
tree structure is allowed. The only problem I see there is
that such a shared node might have multiple parents, and so
it would be difficult to implement Xpath's "..".

Does anyone know more about this?
Maybe one of the XSLT designers?

Thanks in advance,
Steffen

--
Steffen Dingel                 mailto:steffen.dingel@xxxxxx
sd&m AG                        http://www.sdm.de
software design & management
Am Schimmersfeld 7a, 40880 Ratingen, Germany
Tel. +49 2102 9957-678, Fax -50
PGP fingerprint: 4B05 3BC5 E72D A5BA FC59  1A55 97B4 C7AD 26A7 E8E7

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


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.