- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 04 Nov 2005 17:02:27 +0000
- To: public-qt-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2463
Summary: [XDM] String value of a document node
Product: XPath / XQuery / XSLT
Version: Candidate Recommendation
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: Data Model
AssignedTo: Norman.Walsh@Sun.COM
ReportedBy: mike@saxonica.com
QAContact: public-qt-comments@w3.org
When a document is constructed from an Infoset, or from a PSVI, or using a
document node constructor in XQuery, it ends up having a string value that is
the concatenation of all the descendant text nodes in the document. However,
there appears to be no constraint in XDM that this is true of documents
constructed in other ways, for example "synthetically" by an application. It
appears to be possible for such document nodes to have a string value that is
quite unrelated to the textual content of the document. The same is true (in a
more complicated way) of element nodes.
I'm sure that this was never intended.
XSLT, unlike XQuery, does not say what the string value of a newly constructed
document is. We all assumed that this was specified in XDM, but it seems that it
isn't.
Proposal: add a constraint to XDM.
Received on Friday, 4 November 2005 17:02:35 UTC