This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: XSLT feature request - element value templates!
- To: xsl-list at mulberrytech dot com
- Subject: Re: XSLT feature request - element value templates!
- From: David Carlisle <davidc at nag dot co dot uk>
- Date: Wed, 28 Jun 2000 19:05:45 +0100 (BST)
- References: <7784D3376646D311B082000021CF26243F81F9@PIKE>
- Reply-To: xsl-list at mulberrytech dot com
> This will make XSLT easier to teach to new people -
Not convinced, the {} notation is a big win in attribute values
because strings of character data are all you can have in an attribute
value anyway, but simplifying xsl:value down to {} would only deal with
a relatively infrequent case, as normally in elements you are wanting
some more structured data. using text like {} instead of an element node
like <xsl:value-of> would make xsl's white space node stripping rules
rather strange, as unlike the xsl:value of, {} would be in the same
text node as any preceding space.
You could have a <xsl:foo something="avt"/> more like the original
suggestion, as this doesn't interfere with white space stripping.
I'm not convinced that it helps much (having a more concise syntax for
passing parameters would help a lot more:-)
Having {} in text in a template would be a major compatibility problem
(even in an xsl 2.0 system) especially for those of us in the habit of
writing out tex files from xsl.
> { { &cbra;
Neither the numeric character reference nor the cbra entity reference
would qork as a quoting mechanism as they'd both look like an { by the
time the xml parser passed the stylesheet to the xsl system.
David
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list