- From: <bugzilla@wiggum.w3.org>
- Date: Sun, 01 Oct 2006 02:13:53 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3757
------- Comment #4 from jmdyck@ibiblio.org  2006-10-01 02:13 -------
(In reply to comment #0)
>
>     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.
That fact that an V's inner Value doesn't represent N's 'children' and
'typed-value' properties at the same time is a serious problem, I think,
because  V might occur in a context that wants the property that isn't
represented. For instance, consider the post-validation V referred to above:
    element weight of type xs:integer {
      attribute xsi:type of type xs:QName {
        "xs:integer" of type xs:QName
      },
      42 of type xs:integer
    }
If you apply an axis step like child::node() to V, you'll get an empty
sequence, because V does not contain any child NodeValues. But presumably it
should yield a TextValue (i.e., text { "42" }), because the corresponding N
does (still) have a Text Node in its 'children' property.
Received on Sunday, 1 October 2006 02:13:58 UTC