• From: "David E. Cleary" <davec@p...>
• To: Cheryl_Gielau@c..., xml-dev@l...
• Date: Tue, 21 Aug 2001 15:07:50 -0400

> 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

You should package up all common definitions in a schema D. Include schema D
in A and B. When C includes A and B, you will not get your duplicate
definition error, because there is only a single source (schema D) for those
definitions.

Dave

• References:
  • RE: Including multiple schemas - duplicate name errors
    • From: Cheryl_Gielau@c...

• Prev by Date: Re: XInclude vs SAX vs validation
• Next by Date: RE: What are web services good for? (WAS: RE: Two new features o f the Web)
• Previous by thread: RE: Including multiple schemas - duplicate name errors
• Next by thread: RE: Including multiple schemas - duplicate name errors
• Index(es):
  • Date
  • Thread