RE: Including multiple schemas - duplicate name errors

[Cheryl_Gielau@cargill.com]

My understanding of the purpose 
of namespaces was to address
same term - different meaning 
kinds of situations.  Like if 
the term address was used to in
one schema for a postal address 
and in another for an ip address.

The common elements in schemas b 
and c are the same term because they 
have the same meaning.  For example, 
element TransportationMode appears 
in both schema b and c.  b & c are
packaged together into one schema
for particular shipment scenarios.

Cheryl


-----Original Message-----
From: Brian.Magick@compaq.com [mailto:Brian.Magick@compaq.com]
Sent: Tuesday, August 21, 2001 12:32 PM
To: Gielau, Cheryl /mtka
Subject: RE: Including multiple schemas - duplicate name errors


Sounds like you need to use Namespaces in schemas b and c.....schema a 
can
then reference these namespaces and then prevent any naming conflicts.


Brian

-----Original Message-----
From: Cheryl_Gielau@cargill.com [mailto:Cheryl_Gielau@cargill.com]
Sent: Tuesday, August 21, 2001 12:09 PM
To: xml-dev@lists.xml.org
Subject: Including multiple schemas - duplicate name errors


Hello, 
I have a schema (A) that logically contains
2 other schemas (B & C).  I used the 
include feature to bring B & C into the 
A schema.  Some of the elements
between the B & C schemas have the 
same name (and logically have the same
definition) and the parser tells me that the 
element type has been defined more than 
once in the A schema.  

What are some ways I could resolve this?  

Cheryl 



 






-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.xml.org/ob/adm.pl>