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 17:19:44 +0000
To: public-qt-comments@w3.org
Message-Id: <E1Psequ-000562-E6@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12173

--- Comment #2 from Jonathan Robie <jonathan.robie@redhat.com> 2011-02-24 17:19:44 UTC ---
(In reply to comment #1)

> 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. 

The in-scope schema definitions still come from:

1. built-in types
2. explicit schema import
3. implementation-defined additions

Module import does not import the ISSD of the imported module. And it shouldn't
- a single query should be allowed to use library modules whose definitions may
conflict if merged into one ISSD, e.g. library modules for various flavors of
html.

So I think the effect of the proposed change is limited: 

1. Importing such a module is not an error

2. Variables and functions can be used even if their types are unknown, because
their derivation is known, and the implementation can determine whether they
are allowed in a given expression.

-- 
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 17:19:46 UTC

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