This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The effect of the erratum agreed against bug #4463 is that query namespace-decl-3 is now a valid query.
A fix has been attempted in CVS, XQTS_current.zip is updated. If the resolution is satisfactory, feel free to change status to closed. Otherwise reopen this report. If no feedback is given within two weeks, status will be set to closed.
In the current CVS version of the catalog, namespace-decl-3 is still recorded as expecting an error result.
Sorry, the name of the test is namespaceDecl-3
Ok, a second attempt is in CVS.
I'm probably missing something here, but shouldn't this be expecting XQTS0070? Quoting from Bug 4463: "(1) Section 4.12 (Namespace Declaration) Replace paragraph 5 as follows: The namespace prefix specified in a namespace declaration must not be xml or xmlns [err:XQST0070]." That said, I note that Bug 4463 hasn't been listing in Errata for XQuery 1.0. What's the current status? (: Name: namespaceDecl-3:) (: Description: Evaluation of usage of predefined namespace xml = "http://www.w3 .org/XML/1998/namespace":) declare namespace xml = "http://www.w3.org/XML/1998/namespace"; (: insert-start :) declare variable $input-context1 extern al; (: insert-end :) "a"
Agreed - it seems that the outcome of bug 4463 is that explicitly binding the prefix "xml" to the XML namespace is OK in a direct element constructor but not in the prolog. Sigh.
Alrighty, CVS should be back to where we started.
I'm getting an error runnng Catalog002 which may indicate an error in the catalog. Expected '<standard-no-outputfile></standard-no-outputfile>', was '<standard-no-outputfile>namespaceDecl-3</standard-no-outputfile>'