Here is definition of module:<br>"A query can be assembled from one or more fragments called
<b>modules</b>. [<a title="module" id="dt-module" name="dt-module">Definition</a>: A <b>module</b> is a fragment of XQuery
code that conforms to the <a href="http://www.w3.org/TR/xquery/#doc-xquery-Module">Module</a>
grammar and can independently undergo the <a title="static analysis phase" href="http://www.w3.org/TR/xquery/#dt-static-analysis">static analysis
phase</a> described in <a href="http://www.w3.org/TR/xquery/#id-expression-processing"><b>2.2.3
Expression Processing</b></a>. Each module is either a <a title="main module" href="http://www.w3.org/TR/xquery/#dt-main-module">main module</a> or a <a title="library module" href="http://www.w3.org/TR/xquery/#dt-library-module">
library module</a>.]"<br><br>Since modules could independetly undergo the static analysis phase, then <br>I understand wherever it's imported, it's in-scope schema type definition should not be <br>redefined by importing module.
<br><div><span class="gmail_quote"><br></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><font style="color: rgb(0, 0, 0);" size="-1">
Hi,<br>I come up with a problem when reading XQuery1.0 spec., following is my case:<br><br>a.xq:<br><br>module namespace ma="
<a href="http://www.w3.org/TestModules/moduleA" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.w3.org/TestModules/moduleA</a>";<br>import schema namespace simple="<a href="http://www.w3.org/XQueryTest/simple" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.w3.org/XQueryTest/simple</a>
" at "schema_a.xsd";<br>declare function ma:funcA()<br>{<br> "40" cast as simple:myType<br>};<br><br>b.xq:<br><br>declare namespace mb=" <a href="http://www.w3.org/TestModules/moduleB" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.w3.org/TestModules/moduleB
</a>";<br>import module namespace ma="<a href="http://www.w3.org/TestModules/moduleA" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.w3.org/TestModules/moduleA</a>" at "
a.xq";<br>import schema namespace simple=" <a href="http://www.w3.org/XQueryTest/simple" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.w3.org/XQueryTest/simple</a>" at "schema_b.xsd";<br><br>declare function mB:funcB()<br>{<br> ma:funcA() instance of simple:myType<br>};<br><br><result>{mb:funcB()}</result><br><br>schema_a.xsd:
<br><br><xs:schema xmlns:xs="<a href="http://www.w3.org/2001/XMLSchema" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.w3.org/2001/XMLSchema</a>"<br> xmlns:simple="
<a href="http://www.w3.org/XQueryTest/simple" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.w3.org/XQueryTest/simple
</a>"<br> targetNamespace="<a href="http://www.w3.org/XQueryTest/simple" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.w3.org/XQueryTest/simple</a>"<br> elementFormDefault="qualified" attributeFormDefault="qualified"
<br>><br> <xs:simpleType name = "myType"><br> <xs:restriction base = "xs:int"><br> <xs:minInclusive value = "1"/><br> <xs:maxInclusive value = "50"/>
<br> </xs:restriction><br> </xs:simpleType> <br></xs:schema><br><br>schema_b.xsd:<br><br><xs:schema xmlns:xs=" <a href="http://www.w3.org/2001/XMLSchema" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.w3.org/2001/XMLSchema</a>
"<br> xmlns:simple="<a href="http://www.w3.org/XQueryTest/simple" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.w3.org/XQueryTest/simple</a>"<br> targetNamespace="
<a href="http://www.w3.org/XQueryTest/simple" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.w3.org/XQueryTest/simple
</a>"<br> elementFormDefault="qualified" attributeFormDefault="qualified"<br>><br> <redefine<br> schemaLocation="schema_a.xsd"><br> <extension base="simple:myType">
<br> <xs:minInclusive value = "51"/><br> <xs:maxInclusive value = "100"/><br> </extension><br> </redefine><br></xs:schema><br><br>What would be the result of this case?
<br>true? false? runtime error? or implementation define?<br>Or in another word, would the type in module a.xq should<br>be redefined by module c.xq's imported schema definition?<br><br>This case is related with how to understand the XQuery's "module".
<br><br>Let me give my understanding:<br></font>XSLT's module, in my understanding, should be "included" in <br>another module to compile, could not be compiled independently,<br>in other words, it's a "white box", its semantic
<br>depends on where it's included or imported(because its schema type could be <br>differently redefined in different including or importing module).<br> <br>While I think XQuery's module is different with XSLT's module, I think XQuery spec.
<br>allow its module be compiled independently, no matter where the module is imported,<br>module's semantic should not be changed, in other words, XQuery's module<br>is a "black box", wherever module is imported, module's schema type definition should not be
<br>affected by type redefine mechanism.<br><br>The reason why I make such conclusion is from following XQuery spec statement:<br>1 "A <a title="module import" href="http://www.w3.org/TR/xquery/#dt-module-import" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
module import</a> imports only functions and
variable declarations; it does not import other objects from the
imported modules, such as <a title="in-scope schema definitions" href="http://www.w3.org/TR/xquery/#dt-issd" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">in-scope schema definitions</a> or <a title="statically known namespaces" href="http://www.w3.org/TR/xquery/#dt-static-namespaces" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
statically known namespaces</a>. <span style="color: rgb(255, 0, 0);">Module
imports are not transitive</span>¡ªthat is, importing a module provides
access only to function and variable declarations contained
directly in the imported module." <br><br>Here XQuery's statement is clearly different with XSLT's statement about module import. <br>In XSLT spec, module imports are transitive while XQuery clearly stated that they
<br>are not, so XQuery's module import must be something different with XSLT's module import.<br>My thought is, XQuery's module is a "black box" while XSLT's module is a "white box"<br>
<br>2 "It is a <a title="static error" href="http://www.w3.org/TR/xquery/#dt-static-error" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">static
error</a> [<a title="err:XQST0036" href="http://www.w3.org/TR/xquery/#ERRXQST0036" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">err:XQST0036</a>] to import a module if the
importing module's <a title="in-scope schema type" href="http://www.w3.org/TR/xquery/#dt-is-types" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">in-scope schema types</a> do not include definitions
for the schema type names that appear in the declarations of
variables and functions (whether in an argument type or return
type) that are present in the imported module and are referenced in
the importing module."<br><br>Here spec. force user to import interface needed schema types, if we consider XQuery's<br>module as "white box", then all imported types in "white box" has already imported, then
<br>this statement seems <span style="margin-right: 15px;"></span>lead to redundancy, however if we consider XQuery's module<br>as a "black box", then this statement is quite nature to understand. <br><br>Could someone offer me some comment?
<br>Many thanks! <br><span><span><br></span>
</span></div>
</blockquote></div><br>