Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Include/Import and namespace

From: "Bruno Chatel" <bcha@-------.--->
To: "Oancea Adrian" <adi_oancea@-----.--->, <xmlschema-dev@--.--->
Date: 6/2/2006 12:07:00 PM
Hi Adrian,

Thanks for this anwser.

That is effectivly a way to solve the problem.. But of course, there are more than a single "root" schema.
There is a need to factorize declarations in sub-modules (ops-exch, ops-shared). In the project, there are 19 root schemas
using 26 sub-schemas (directly or indirectly included).  Then, if a resolve this by writting 19 compiled root
schemas, it breaks the modularity and lead risks of errors for evolutions.

Finally, if I can't found an other bypass, I need to develop a transformation to build compiled schemas from
the reference set of modular schemas.

Regards

-- 
Bruno Chatel
Tel : (+33) (0)4 96 11 14 57
bcha@c...
http://www.chadocs.com
--------------------------------------


----- Original Message ----- 
From: "Oancea Adrian" <adi_oancea@y...>
To: "Bruno Chatel" <bcha@c...>; <xmlschema-dev@w...>
Cc: "Bruno Chatel" <bcha@c...>
Sent: Thursday, June 01, 2006 8:28 PM
Subject: Re: Include/Import and namespace


>
> For the question 1) :
> Yes, it's possible. You must move the content of all included files in the parent file (recursively). Finally, you will have only
imported files.
>
> I give as example the basic situation: Parent.xsd includes Child.xsd.
>
> Copy all the content between <xs:schema> and </xs:schema> from Child.xsd into Parent.xsd, imediatly after <xs:schema> declaration.
Copy all the declarations of namespaces that appear in Child.xsd and doesn't appear in Parent.xsd, in <xs:schema ..... >. And remove
of course <xs:include>.
>
>
> Regards,
> Adrian Oancea
>  __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
> --0-1672349049-1149186496=:99399
> Content-Type: text/html; charset=iso-8859-1
> Content-Transfer-Encoding: 8bit
>
> For the question 1) :<br>Yes, it's possible. You must move the content of all included files in the parent file (recursively).
Finally, you will have only imported files.<br><br>I give as example the basic situation: Parent.xsd includes Child.xsd.<br><br>Copy
all the content between &lt;xs:schema&gt; and &lt;/xs:schema&gt; from Child.xsd into Parent.xsd, imediatly after &lt;xs:schema&gt;
declaration. Copy all the declarations of namespaces that appear in Child.xsd and doesn't appear in Parent.xsd, in &lt;xs:schema
..... &gt;. And remove of course &lt;xs:include&gt;.<br><br><br>Regards,<br>Adrian
Oancea<p>&#32;__________________________________________________<br>Do You Yahoo!?<br>Tired of spam?  Yahoo! Mail has the best spam
protection around <br>http://mail.yahoo.com
> --0-1672349049-1149186496=:99399--
>
>
>


From ht@i... Fri Jun 02 12:51:27 2006
Received: from lisa.w3.org ([128.30.52.41])
	by frink


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