This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Reason for restrictions on RTFs in XSLT 1.0?
- To: xsl-list at lists dot mulberrytech dot com
- Subject: [xsl] Reason for restrictions on RTFs in XSLT 1.0?
- From: steffen dot dingel at sdm dot de
- Date: Tue, 30 Jan 2001 10:20:38 +0100
- Reply-To: xsl-list at lists dot mulberrytech dot com
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@sdm.de
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