- From: <bugzilla@jessica.w3.org>
- Date: Thu, 29 May 2014 20:44:09 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25919 Bug ID: 25919 Summary: unparsed-text-023 should not expect a static error Product: XPath / XQuery / XSLT Version: Recommendation Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: XQuery 3 & XPath 3 Test Suite Assignee: oneil@saxonica.com Reporter: josh.spiegel@oracle.com QA Contact: public-qt-comments@w3.org Group: XSLXQuery_WG fn-unparsed-text-023 currently expects XPST0001 because $href is a relative URI and the static base URI is undefined: <test-case name="fn-unparsed-text-023" ...> <description>Evaluates the "unparsed-text" function with the argument set as follows: $href is a relative URI, static base URI undefined.</description> <created by="Tim Mills" on="2011-11-28"/> <environment> <static-base-uri uri="#UNDEFINED"/> </environment> <test><![CDATA[fn:unparsed-text("unparsed-text/text-plain-utf-8.txt")]]></test> <result> <error code="XPST0001"/> </result> </test-case> XPST0001 is a static error. In general it is not possible to determine if the value of $href is relative or not during static analysis so I don't think a static error is appropriate. In this particular case it may be possible for an implementation to detect the error during static analysis but this would still be a dynamic error that is detected during static analysis (not a static error). Consequently, I also think that fn-unparsed-text-available-023 should return false instead of expecting a static error: <test-case name="fn-unparsed-text-available-023"> <description>Evaluates the "unparsed-text-available" function with the argument set as follows: $href is a relative URI, static base URI undefined.</description> <created by="Tim Mills" on="2011-11-28"/> <environment> <static-base-uri uri="#UNDEFINED" /> </environment> <test>fn:unparsed-text-available("unparsed-text/text-plain-utf-8.txt")</test> <result> <error code="XPST0001"/> </result> </test-case> http://www.w3.org/TR/2014/REC-xpath-functions-30-20140408/#func-unparsed-text-available "... the function returns true if a call on fn:unparsed-text with the same arguments would succeed, and false if a call on fn:unparsed-text with the same arguments would fail with a non-recoverable dynamic error" The following tests fall in this category: fn-unparsed-text-023 fn-unparsed-text-024 fn-unparsed-text-lines-023 fn-unparsed-text-lines-024 fn-unparsed-text-available-023 fn-unparsed-text-available-024 Thanks. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 29 May 2014 20:44:11 UTC