RE: Including multiple schemas - duplicate name errors

[Cheryl_Gielau@cargill.com]

I am using seperate schemas since one (A)
represents a particular kind of operational 
event (the weight of product)and the other (B) 
represents a different kind of operational 
event (the quality of product).  
At points in the workflow, the messages are 
sent seperately.  However, they do have 
some element names that are in common 
like TransportationMode, ServiceLocation 
and others but that are defined globally
in each of the A and B schemas.  

Later in the workflow Schema C packages schemas 
A and B together, along with some additional 
instructions.  In schema C, since A and B are
included, I get the error that TransportationMode
and ServiceLocation & others have been defined
more than once.  

Cheryl



-----Original Message-----
From: davec@progress.com [mailto:davec@progress.com]
Sent: Tuesday, August 21, 2001 1:13 PM
To: davec@progress.com; xml-dev@lists.xml.org
Subject: RE: Including multiple schemas - duplicate name errors


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

Then it should be defined globally somewhere and refered to. What is the
reason you are using separate schemas? Knowing that will help with the
solution.

Dave


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