OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   RE: [xml-dev] help in processing compositor's in XML Schema?

[ Lists Home | Date Index | Thread Index ]
  • To: xml-dev@lists.xml.org, 'Bill Riegel' <BRiegel@lgc.com>
  • Subject: RE: [xml-dev] help in processing compositor's in XML Schema?
  • From: "CHIUSANO, Joseph" <JCHIUSANO@lmi.org>
  • Date: Mon, 11 Mar 2002 13:57:26 -0500
  • Return-receipt-to: "CHIUSANO, Joseph" <JCHIUSANO@lmi.org>

Title: RE: [xml-dev] help in processing compositor's in XML Schema?
Slight correction:
 
<Was>
Within each model group, specify the "choice" compositor to avoid having order enforced. For example:
</Was>
 
<ShouldBe>
Within each model group, specify the "all" compositor to avoid having order enforced. For example:
</ShouldBe>

**************************************************************************
  Joseph M. Chiusano
  Logistics Management Institute
  2000 Corporate Ridge
  McLean, VA 22102
  Email: jchiusano@lmi.org
  Tel: 571.633.7722
**************************************************************************

-----Original Message-----
From: CHIUSANO, Joseph [mailto:JCHIUSANO@lmi.org]
Sent: Monday, March 11, 2002 1:55 PM
To: xml-dev@lists.xml.org; 'Bill Riegel'
Subject: RE: [xml-dev] help in processing compositor's in XML Schema?

You can accomplish this with model groups. You can create one model group to hold the "header" elements, and one to hold the "child" elements (both must be declared globally). Within each model group, specify the "choice" compositor to avoid having order enforced. For example:

<xsd:group name="HeaderElementGroup">
     <xsd:all>
          <xsd:element name="header1" type="[sometype]">
          <xsd:element name="header2" type="[sometype]">
          <xsd:element name="header2" type="[sometype]">
     </xsd:all>
</xsd:group>

<xsd:group name="ChildElementGroup">
     <xsd:all>
          <xsd:element name="child1" type="[sometype]">
          <xsd:element name="child2" type="[sometype]">
     </xsd:all>
</xsd:group>

Then, define the "parent" element using the "sequence" compositor and reference the two model groups within it:

<xsd:element name="parent">
     <xsd:sequence>
          <xsd:group ref="HeaderElementGroup">
          <xsd:group ref="ChildElementGroup">
     </xsd:sequence>
</xsd:element>

Hope that helps,
Joe Chiusano

> **************************************************************************
>   Joseph M. Chiusano
>   Logistics Management Institute
>   2000 Corporate Ridge
>   McLean, VA 22102
>   Email: jchiusano@lmi.org
>   Tel: 571.633.7722
> **************************************************************************
>


-----Original Message-----
From: Bill Riegel [mailto:BRiegel@lgc.com]
Sent: Monday, March 11, 2002 1:48 PM
To: xml-dev@lists.xml.org
Subject: [xml-dev] help in processing compositor's in XML Schema?


I am trying to define the following in a XML Schema. I would like the
elements , header1, header2, and header3 to be un-ordered within themselves
and child1 and child2 to be un-undered within themselves. but I would like
to define that the header's occur before the child's.

Without introducing more tags, Is there a way to do this ??

        <parent>
                <header1/>
                <header2/>
                <header3/>
                <child1/>
                <child2/>
        </parent>


Bill Riegel
Landmark Graphics
Phone: 713-839-3388

-----------------------------------------------------------------
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 list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>





 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS