- From: <bugzilla@jessica.w3.org>
- Date: Thu, 06 Jun 2013 06:15:50 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19597 --- Comment #26 from Michael Kay <mike@saxonica.com> --- Another little twist on this. Consider: import schema namespace v="http://www.w3.org/2012/xquery" at "http://www.w3.org/2003/05/soap-envelope/"; declare option prohibit-feature "v:schema-aware"; in the case of a processor that is capable of being schema-aware, and is also capable of pretending not to be schema-aware. It seems that such a processor must bind the prefix v to the target namespace of the schema before it can discover than it is not supposed to be schema-aware and therefore should not have done so. At the very least we must therefore allow such a processor to report problems with the namespace binding, e.g. if v is a duplicate binding. This means that the processor does NOT behave precisely in the way that a non-schema-aware processor behaves; it cannot possibly do so. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 6 June 2013 06:15:52 UTC