Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: multiple namespaces

From: "Michael Kay" <mike@--------.--->
To: "'Andrew Welch'" <andrew.j.welch@-----.--->, <xmlschema-dev@--.--->
Date: 4/23/2007 4:21:00 PM
> With this XML:
> 
>   <ns1:foo>some text</ns1:foo>
>   <ns2:bar>some text</ns2:bar>
> 
> Am I right in thinking I need two schemas - one for each namespace?

No, you need two *schema documents* each defining part of a single *schema*.

> Also, if I define a simple type of non-empty-string:
> 
>     <xs:simpleType name="non-empty-string">		
> 		<xs:restriction base="xs:string">		
> 			<xs:minLength value="1"/>		
> 		</xs:restriction>		
>     </xs:simpleType>	 	
> 
> ...when I refer to that type it seems I have to use the 
> prefix defined in the schema, for example to use the simple 
> type above I need:
> 
> <xs:element name="foo" type="ns1:non-empty-string"/>

No, you can omit the prefix, and the default namespace will be used (as
declared using xmlns="...". This is not necessarily the same as the target
namespace of the schema document).

>Am I missing something here?

Yes, I think so!

Michael Kay
http://www.saxonica.com/


From noah_mendelsohn@u... Mon Apr 23 14:36:22 2007
Received: from


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