- From: <bugzilla@jessica.w3.org>
- Date: Thu, 13 Jun 2013 16:36:48 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22353 Bug ID: 22353 Summary: [XQ3TS] prohibit-typed-data-2-ns Classification: Unclassified Product: XPath / XQuery / XSLT Version: Candidate Recommendation Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P2 Component: XQuery 3 & XPath 3 Test Suite Assignee: oneil@saxonica.com Reporter: tim@cbcl.co.uk QA Contact: public-qt-comments@w3.org The functions module:nine() and module:ten() both produce typed data and are being consumed by a module which prohibits use of typed data. Were they to produce untyped data, an expected result would be false. Since this is not the case, I can't see how an expected result of false can be expected. I would be grateful if someone could explain it with reference to the current text in https://www.w3.org/Bugs/Public/show_bug.cgi?id=20828#c6 (unless this has been superseded by something else)? I can't see anything in here which suggests that the typed data from the function calls gets stripped, except perhaps "If an XQuery implementation does not provide the Typed Data Feature, it MUST guarantee that: ... 3. Elements constructed by the query always have the type xs:untyped; attributes constructed by the query always have the type xs:untypedAtomic." but this doesn't hint at the mechanism by which this would be achieved when operating on data from another module (or from, say, a call to fn:doc). -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 13 June 2013 16:36:49 UTC