- From: Alex Milowski <alex@milowski.com>
- Date: Sun, 2 Jun 2013 20:28:58 -0700
- To: James Fuller <jim@webcomposite.com>
- Cc: XProc WG <public-xml-processing-model-wg@w3.org>
Received on Monday, 3 June 2013 03:29:25 UTC
On Sat, Jun 1, 2013 at 3:36 AM, James Fuller <jim@webcomposite.com> wrote: > The p:template note states at the end of 1. Introduction > > 'Where the expressions occur in attribute values, their string value > is used. Where they appear in text content, their node values are > used.' > > though as this is a Note we can just change the document, but don't > you think this sentence is enough ? > Well, I'm not sure. "Node value" isn't really an official term. So, what is the "node value" of a attribute node that can't be copied into the children of an element? It is also a confusing term to using as we usually mean a "copy of the node" and, yet, we can't copy the attribute node into a child. "node value" also means "attribute value" in the context of the DOM. "node value" has no meaning in the context of the XDM. > > You can still do string(/element/@someattr) to achieve what you want. > > Yes, of course, that's what I had to do. I put this in the category of "expected behavior." -- --Alex Milowski "The excellence of grammar as a guide is proportional to the paucity of the inflexions, i.e. to the degree of analysis effected by the language considered." Bertrand Russell in a footnote of Principles of Mathematics
Received on Monday, 3 June 2013 03:29:25 UTC