[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Things that make you go Hmmmm!
On 29/03/2014 12:42, Ihe Onwuka wrote:
On Sat, Mar 29, 2014 at 11:57 AM, Andrew Welch <andrew.j.welch@xxxxxxxxx> wrote:On Fri, Mar 28, 2014 at 4:48 PM, Andrew Welch <andrew.j.welch@xxxxxxxxx> wrote:I was surprised that the content models of xsl:copy and xsl:copy-of were different (by dint of the select attribute) in the first place. But xsl:copy takes content, and xsl:copy-of is an empty element (as has been stated several times before) Why do you consider their content models remotely similar?
Why? and in what way, what would element content of xsl:copy-of do??
It generates a text node with value a an empty string. In most circumstances that text node is then discarded when adding nodes to a parent node. What is the advantage of restricting a language constructs content model to the use-cases you can foresee today. What is the disadvantage of doing that? If you allow things you (or at least the language designer) has to say what they mean. What would you want element content of xsl:copy-of to mean? David
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|