This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
When in boundary space mode "strip", can the expected result both of these tests be correct? If empty CDATA sections generate an empty sequence, then no content appears before the computed attribute and neither test should throw XQTY0024. If empty CDATA sections generate an empty text node, then both tests should throw XQTY0024. (:*******************************************************:) (: Test: K2-ComputeConAttr-35 :) (: Written by: Frans Englich :) (: Date: 2007-01-15T15:15:44+01:00 :) (: Purpose: Empty CDATA sections generate no text nodes. :) (:*******************************************************:) <elem><![CDATA[]]>{attribute name {"content"}}<alem/> </elem> (:*******************************************************:) (: Test: K2-ComputeConAttr-5 :) (: Written by: Frans Englich :) (: Date: 2007-01-15T15:15:44+01:00 :) (: Purpose: Ensure XQTY0024 is issued when content appears before computed attri butes. :) (:*******************************************************:) <elem> <![CDATA[]]> {attribute name {"content"}} </elem>
The empty CDATA section is a lexical notation for a sequence of zero characters within the element content. It's the same as writing nothing at all, except that the rules for determining boundary whitespace are determined before expansion of entity references and CDATA sections. For better or for worse, the definition is: Boundary whitespace is a sequence of consecutive whitespace characters within the content of a direct element constructor, that is delimited at each end either by the start or end of the content, or by a DirectConstructor, or by an EnclosedExpr and in K2-ComputeConAttr-5, the whitespace characters are not boundary whitespace because they are delimited at one end by a CDATA section, which is neither a DirectConstructor nor an EnclosedExpr.
Thanks.