This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Many of these tests make a call to unparsed-text("../docs/atomic.xml") but the environment is empty. I suggest rewriting the tests to use (for example) unparsed-text("http://www.w3.org/fots/docs/atomic.xml") and reference the "atomic" environment.
I can see why you would like this, so that unparsed-text() mirrors the way doc() is handled in the specs, but at present the spec of the two functions is different: doc() uses a mapping of URIs to resources in the static context, whereas unparsed-text() lacks this indirection: the spec is written to require direct resolution of the URI supplied. So I think this is a spec issue, not a test issue - the tests as written reflect the spec.
Should I raise this against the spec? It would be a bit strange if doc($uri) is markedly different from parse-xml(unparsed-text(
The fn:serialize tests actually use fn:doc, not fn:unparsed-text so need the fix I suggested. <test-case name="serialize-xml-001"> <description>serialize test</description> <created by="ONeil Delpratt, Saxonica" on="2010-10-05"/> <environment name="empty"/> <test>serialize(doc('../docs/atomic.xml'))</test> <result> <assert>contains($result,'atomic')</assert> </result> </test-case>
Most of these tests have been rewritten.
The tests serialize-xml-005 serialize-xml-007 serialize-xml-009 each use a serialization parameter document which is invalid with respect to the schema. I expect the fn:serialize function to follow the process described in "3.1 Setting Serialization Parameters by Means of a Data Model Instance" at: https://www.w3.org/XML/Group/qtspecs/specifications/xslt-xquery-serialization-30/html/Overview.html#serparams-in-xdm-instance Thus setting a parameter will necessitate lax validation, and therefore each of these tests should expect SEPM0017.
For tests serialize-xml-005 and serialize-xml-009 I have changed the error code from SEPM0016 to SEPM0017 as suggested. For test serialize-xml-007 I have anticipated the changes discussed by the WG today: it is expected that the schema will be changed to permit unrecognized elements in a "foreign" namespace but disallow those in the standard output namespace. I split the test into two to cover both cases.
Confirmed fixed. Thanks.