- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 21 Sep 2006 03:45:55 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3757
Summary: [FS] technical: 2.3.1 ElementValue
Product: XPath / XQuery / XSLT
Version: Candidate Recommendation
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Formal Semantics
AssignedTo: simeon@us.ibm.com
ReportedBy: jmdyck@ibiblio.org
QAContact: public-qt-comments@w3.org
2.3.1 / -- / para 4,5,6
"Element nodes have a type annotation and contain a complex value or a
simple value. ... A simple value is a sequence of atomic values. A complex
value is a sequence of attribute nodes followed by a sequence of element,
text, comment, or processing-instruction nodes."
First, this definition doesn't support the following example from
2.3.2:
element weight of type xs:integer {
attribute xsi:type of type xs:QName {
"xs:integer" of type xs:QName
},
42 of type xs:integer
}
(An attribute node followed by an atomic value doesn't satisfy the
definition for 'complex value' or 'simple value'.)
More generally, what is the mapping between FS ElementValues and XDM
ElementNodes? In particular, if an FS ElementValue V represents an
XDM Element Node N, then what does V's inner Value represent, with
respect to N? It seems that sometimes it represents the concatenation
of N's 'attributes' and 'children' properties, and sometimes it
represents the concatenation of N's 'attributes' and 'typed-value'
properties. (The above example is an instance of the latter.) I think
this is non-obvious enough that it should be spelled out.
Received on Thursday, 21 September 2006 03:46:03 UTC