Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xml-dev] Access to elements from schema imported once removed!

From: "Chiusano Joseph" <chiusano_joseph@---.--->
To: "Kasimier Buchcik" <kbuchcik@---------.-->
Date: 9/5/2005 3:11:00 PM
Title: RE: [xml-dev] Access to elements from schema imported once removed!






Thanks - can you bottom-line 
that please?
 
Joe Chiusano



From: Kasimier Buchcik 
[mailto:kbuchcik@4...]
Sent: Mon 9/5/2005 10:40 
AM
To: Chiusano Joseph
Cc: XML-dev
Subject: RE: 
[xml-dev] Access to elements from schema imported once 
removed!



Hi,

On Mon, 2005-09-05 at 10:18 -0400, Chiusano Joseph 
wrote:
> From a quick glance, in your "imported schema", element 
"globalElement
> is not in the "urn:foo" namespace because it does not 
have a namespace
> prefix, and you have not specified a default namespace 
for that
> schema. If you add a default namespace declaration to the 
imported
> schema that makes the "urn:foo" namespace your default 
namespace, it
> should work.

The target-namespace of a top-level 
element declaration is dependent
on the targetNamespace attribute of the 
parent <schema> element only;
i.e. the value of the "name" attribute is 
not a QName. On the other
hand, references to schema components _are_ QNames, 
so namespace
declarations are taken into account when 
referencing.

Regards,

Kasimier


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