 |
 |
 |
Thanks for the feedback - the MS people also pointed me to the following
snippet from the XML Schema Part 1: Structures -
"Schema Representation Constraint: QName resolution (Schema Document)
(...)
4 its *namespace name* is either the target namespace of the schema document
containing the *QName* or that schema document contains an <import> element
information item the *actual value* of whose namespace [attribute] is
identical to that *namespace name*. "
According case 4, the referenced component should have an import for the
namespace if its namespace is not the targetNamespace of the schema.
I am curious why the specification defines that this information must be
declared again locally when in my case it is being declared by the imported
schema? Should the lack of the <import> be considered a schema validation
error if the implementation can infer this from a child schema?
James
-----Original Message-----
From: ht@i... [mailto:ht@i...]
Sent: Wednesday, June 23, 2004 10:47 AM
To: Delmerico, James
Cc: xmlschema-dev@w...
Subject: Re: Chaining <xs:import> statements
Just to explain _why_ the previous answer (import both) is correct,
note that <xs:import> achieves _two_ things:
1) It provides a place for a hint to processors where they can
find schema documents likely to be of use ('schemaLocation'
attribute);
2) It signals to processors that references to components in
particular namespace _from this schema document_ are allowed
('namespace' attribute).
Since the second use is _local_ to the schema document in which it
occurs, it's the one which is at issue in your situation.
ht
--
Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
Half-time member of W3C Team
2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht@i...
URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged
spam]
From noah_mendelsohn@u... Wed Jun 23 12:02:35 2004
Return-Path: <noah_me
|
 | 

|  |
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.
|  |
| |
 |
 |
 |