OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] RE: Is schemaLocation just a hint in schema import?

This seems another instance where the schema 
folks changed the path of the XML standard. In a 
DTD, it is the last definition read that becomes 
the definition - seems like the import rules 
should treat schemas in the same way. The only 
place that seems like it needs special handling 
is with redefine in the situation that I just got caught in.

I have Schema A that is imported into Schema B, I 
then redefine Schema A and import Schema B. This 
also seems to be a implementation dependent 
problem and the solution that was proposed but I 
haven't tested was to remove the schema location 
on the import of Schema A into schema B. I find 
it strange that some how the physical file 
location might control part of the triggering of 
this rule. Seems to me that the namespace should 
be the equivalent of specifying a file location, but maybe it isn't.

How about a push to simplify XML schema instead 
of changing the syntax and features of the core XML spec?


At 09:03 AM 10/9/2006, Michael Kay wrote:
> > "NOTE: The above is carefully worded so that multiple
> > <import>ing of the same schema document will not constitute a
> > violation of clause 2 of Schema Properties Correct (§3.15.6),
> > but applications are allowed, indeed encouraged, to avoid
> > <import>ing the same schema document more than once to
> > forestall the necessity of establishing identity component by
> > component.
> > Given that the schemaLocation [attribute] is only a hint, it
> > is open to applications to ignore all but the first <import>
> > for a given namespace, regardless of the ·actual value· of
> > schemaLocation, but such a strategy risks missing useful
> > information when new schemaLocations are offered."
> >
> >
> > Can anybody tell me the motivation for this note in the schema spec?
> >
>I've pointed out in comments on 1.1 that if the spec really were carefully
>worded, then the (non-normative) note wouldn't be needed.
>The spec, I think, is saying two things:
>(a) if you do two imports from the same schemaLocation (whatever "same"
>means) then you should be OK; the components should only be imported once.
>(b) if you do two imports from different schemaLocations (whatever
>"different" means) then it's pretty much undefined what happens: the system
>may import both and report any conflicts (such as the same element
>declaration appearing in both), or it may import both and detect that the
>two are actually identical, or it may import one and ignore the other.
>Michael Kay
>XML-DEV is a publicly archived, unmoderated list hosted by OASIS
>to support XML implementation and development. To minimize
>spam in the archives, you must subscribe before posting.
>[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
>Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
>subscribe: xml-dev-subscribe@lists.xml.org
>List archive: http://lists.xml.org/archives/xml-dev/
>List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

Danny Vint

Specializing in Panoramic Images of California and the West

voice: 510-522-4703

When H.H. Bennett was asked why he preferred to be out
shooting landscapes rather than spending time in his portrait studio:

"It is easier to pose nature and less trouble to please."



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS