- From: <bugzilla@jessica.w3.org>
- Date: Tue, 04 Jun 2013 20:22:31 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19597 --- Comment #21 from Michael Kay <mike@saxonica.com> --- You say "the specification clearly says that the implementation must not attempt to do so [import the schema or module]". But it says nothing of the kind. It only says that it's a static error if it finds an import module/schema declaration. There is nothing that prevents it detecting other errors in this declaration, for example the presence of a duplicate namespace prefix or an invalid URI, or even the fact that the module/schema being imported is invalid. You might regard it as implausible that an implementation that doesn't support import schema would waste its time looking for such errors, but there is nothing in the spec that says it is not allowed to do so; and in the specific case where the implementation doesn't yet know that it doesn't support schema/module import, because it hasn't yet reached the declaration that informs it of this fact, it is entirely plausible that it should validate the declaration as far as it is able during initial parsing. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 4 June 2013 20:22:37 UTC