This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
According to the steps in the spec: http://www.w3.org/TR/2009/WD-xquery-11-20091215/#doc-xquery11-CompPIConstructor "If the atomized value of the name expression is of type xs:string or xs:untypedAtomic, that value is cast to the type xs:NCName. If the value cannot be cast to xs:NCName, a dynamic error is raised [err:XQDY0041]." So, for test K2-ComputeConPI-3 http://dev.w3.org/2006/xquery-test-suite/TestSuiteStagingArea/Queries/XQuery/Construct/ComputeCon/ComputeConPI/K2-ComputeConPI-3.xq since the atomized value can not be casted to an xs:NCName, an alternate result should be added for err:XQDY0041. The same is true for K2-ComputeConPI-4, K2-ComputeConPI-5.
But in all three cases the value CAN be cast to xs:NCName (that, I think, is the point of the test). Casting a string to xs:NCName removes leading and trailing whitespace. (F+O 17.1.1 para 1, "Whitespace normalization is applied as indicated by the whiteSpace facet for the datatype.").
Yes, my fault: I missed that. I have marked the bug as resolved/invalid: I think that is the correct status in this case. Thanks for the help, Sorin Nasoi
Big triage sub-team thinks the ARIA mapping team should review and update this bug as the mappings are prepared, but no need for entire HTML A11Y TF to review. Assigning to Steve Faulkner to track.
Apologies, this bug was accidentally updated in a bulk update to a number of other bugs, where there was a typo in the set of bugs to be updated. Ignore comment 3. Reassigning to original owner.