Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xml-dev] Problem about imported schema type when processing XQuery module import

From: "Michael Kay" <mike@--------.--->
To: "'he harrison'" <harrison076@-----.--->
Date: 1/2/2008 4:27:00 PM
Since 
it does not import in-scope schema definitions from the imported modules, the 
importing 
module should not see what schema definitions are there in the 
imported modules.Since they
could not see each other, then how could they 
decide whether their ISSD is "equivalent"? 
and it seems also meaningless to 
compare their ISSD because they will not disturb each 
other. 
 
This may be why the spec doesn't require an 
implementation to check that the two ISSDs are compatible, but merely says that 
the results are unpredictable if they are 
not. 

and


  If a module could see the imported module's 
  schema definition, then why spec. still
force the importing module 
  explicitly import necessary schema definition, since these types 
will 
  surely be imported from other module's ISSD?

XSLT took the 
  decision that all imported schema definitions would be available in all 
  modules. However, that makes it harder to do separate compilation of 
  modules. I think the rule in XQuery that each module must import all 
  the schema definitions that it needs is there in the belief that this will 
  make separate compilation of modules easier.
   
  Michael Kay
  http://www.saxonica.com/


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent