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

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

From: <bugzilla@jessica.w3.org>
Date: Tue, 01 Mar 2011 01:08:38 +0000
To: public-qt-comments@w3.org
Message-Id: <E1PuE4s-0007HH-PE@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12173

--- Comment #3 from Jonathan Robie <jonathan.robie@redhat.com> 2011-03-01 01:08:37 UTC ---
The Working Group agreed to delete the following text (excuse the formatting
loss due to lack of HTML):

<delete>
It is a static error [err:XQST0036] to import a module if the in-scope schema
definitions of the importing module do not include all of the following:

An in-scope schema type for each type-name that appears:
in the type of a variable that is declared in the imported module and
referenced in the importing module, OR
in a parameter-type or result-type of a function that is declared in the
imported module and referenced in the importing module.
An in-scope element declaration for each element-name EN such that:
schema-element(EN) appears in the declared type of a variable in the imported
module, and that variable is referenced in the importing module, OR
schema-element(EN) appears in a parameter-type or result-type of a function
declared in the imported module, and that function is referenced in the
importing module.
An in-scope attribute declaration for each attribute-name AN such that:
schema-attribute(AN) appears in the declared type of a variable in the imported
module, and that variable is referenced in the importing module, OR
schema-attribute(AN) appears in a parameter-type or result-type of a function
declared in the imported module, and that function is referenced in the
importing module.
</delete>

And to modify this:

<changeme>
To illustrate the above rules, suppose that a certain schema defines a type
named triangle. Suppose that a library module imports the schema, binds its
target namespace to the prefix geometry, and declares a function with the
following function signature: math:area($t as geometry:triangle) as xs:double.
If a query wishes to use this function, it must import both the library module
and the schema on which it is based. Importing the library module alone would
not provide access to the definition of the type geometry:triangle used in the
signature of the area function.
</changme>

The modification must illustrate the interaction of types in the two ISSDs.

The following text will be kept as is:

<keep>
The following example illustrates a module import:

import module namespace math =
  "http://example.org/math-functions";
</keep>

-- 
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 Tuesday, 1 March 2011 01:08:40 UTC

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