- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 18 Jan 2008 12:44:25 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5393 Summary: CVS: fn-doc-available-4 and xml:id errors Product: XML Query Test Suite Version: unspecified Platform: PC OS/Version: Windows NT Status: NEW Severity: normal Priority: P2 Component: XML Query Test Suite AssignedTo: andrew.eisenberg@us.ibm.com ReportedBy: tim@cbcl.co.uk QAContact: public-qt-comments@w3.org fn-doc-available-4 is described as a test which checks that a document with an invalid xml:id attribute is flagged. Quoting xml:id version 1.0 (http://www.w3.org/TR/xml-id/#dt-xml-id-error) "An xml:id error is a non-fatal error that occurs when an xml:id processor finds that a document has violated the constraints of this specification." "A violation of the constraints in this specification results in an xml:id error. Such errors are not fatal, but should be reported by the xml:id processor. In the interest of interoperability, it is strongly recommended that xml:id errors not be silently ignored." It seems to me from the above that failing an xml:id constraint will not necessarily cause the document to be considered as not available. That said, a mechanism for catching an xml:id error in XQuery would, I presume, be implementation defined. More generally, is it a requirement that a document loaded with fn:doc (directly, or indirectly via fn:doc-available): 1. Perform xml:id processing? 2. Perform DTD processing if a DOCTYPE is included? 3. Perform XML Schema validation if a schema is referenced?
Received on Friday, 18 January 2008 12:44:31 UTC