Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


XML Schema namespace association at the API level

From: "Bryan Rasmussen" <BRS@----.-->
To: <xmlschema-dev@--.--->
Date: 3/7/2006 12:19:00 PM
Hi,

Most processors I'm familiar with allow some sort of association of =
schemas
with namespaces via the API so that one can have a list of schemas =
maintained
by the API seperate from the actual Schemas, allowing the Processor to =
take
care of scenarios such as 
Schema # 1 uses xsd:any with processContents= strict when content of =
the
document at the point where xsd:any is allowed is in namespace x without
Schema #1 referencing Schema #2 which validates x directly. 

This basically gives the same capability that one can have with
xsi:schemaLocation at the instance to the application. 

The thing I'm wondering about is, is this capacity defined anywhere in =
the
XML Schema specs? I'm looking in "4 Schemas and Namespaces: Access and
Composition" http://www.w3.org/TR/xmlschema-1/#composition and I can't =
find
anything. Anywhere else? Different Processors seem to implement this
differently, and it doesn't seem to me to be the kind of thing that one =
would
require of a spec, thus my question. Hope this question was clear.

Cheers,
Bryan Rasmussen

From xml1@l... Tue Mar 07 18:00:49 2006
Received: from maggie


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