W3C home > Mailing lists > Public > public-qt-comments@w3.org > February 2011

[Bug 12173] Do we need [err:XQST0036] in-scope schema definitions of the importing module?

From: <bugzilla@jessica.w3.org>
Date: Thu, 24 Feb 2011 16:04:29 +0000
To: public-qt-comments@w3.org
Message-Id: <E1Psdg5-0000WK-9o@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12173

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mike@saxonica.com

--- Comment #1 from Michael Kay <mike@saxonica.com> 2011-02-24 16:04:28 UTC ---
I'm inclined to agree. At one time our spec encouraged the interpretation that
the static context of a module included the schema namespaces explicitly
imported into that module, and nothing else, and I went to painful lengths to
ensure that a reference to a name that wasn't explicitly imported was rejected. 

We have since repudiated that interpretation in favour of the idea that the
static context contains all the schema components you happen to know about at
compile time, whether explicitly imported or not. This means that XQST0036 has
lost most of its original point.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 24 February 2011 16:04:30 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:45 UTC