- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 27 Sep 2006 07:10:37 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3771 Summary: [FS] technical: interleaved with empty text nodes 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 4.7.1 / Norm "we normalize each unit individually and construct a sequence of the normalized results interleaved with empty text nodes." This appears to cause failures in STA. Consider: <e>{ attribute a1 {"v1"} }{ attribute a2 {"v2"} }</e> which is normalized to (roughly): element e { fs:item-sequence-to-node-sequence(( attribute a1 {"v1"}, text {""}, attribute a2 {"v2"} )) } {} The problem here is that there is an attribute node after a text node. This isn't a problem for DEv, because empty text nodes are deleted before checking for misplaced attribute nodes, but it is a problem for STA. Currently, STA fails for the call to fs:item-sequence-to-node-sequence() If (as I suggest in Bug 3760) we drop that call from normalization, then the failure happens when we try to typecheck the element constructor. Are such failures intentional?
Received on Wednesday, 27 September 2006 07:10:43 UTC