[XML-DEV Mailing List Archive Home]
[By Thread]
[By Date]
[Recent Entries]
[Reply To This Message]
RE: Problem about imported schema type when processing XQuery
- From: "Michael Kay" <mike@s...>
- To: "'he harrison'" <harrison076@g...>
- Date: Wed, 2 Jan 2008 16:27:15 -0000
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/
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
|
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format
RSS 2.0 |
|
Atom 0.3 |
|
|
Stylus Studio has published XML-DEV in RSS and ATOM formats,
enabling users to easily subcribe to the list from their preferred news reader application.
|
Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website.
they were not included by the author in the initial post. To view the content without the Sponsor Links please
click here.
|
|