XML
  Home arrow XML arrow Page 2 - Designing Your Own XML Schema: Indicators
Dev Articles Forums 
ADO.NET  
Apache  
ASP  
ASP.NET  
C#  
C++  
ColdFusion  
COM/COM+  
Delphi-Kylix  
Design Usability  
Development Cycles  
DHTML  
Embedded Tools  
Flash  
Graphic Design  
HTML  
IIS  
Interviews  
Java  
JavaScript  
MySQL  
Oracle  
Photoshop  
PHP  
Reviews  
Ruby-on-Rails  
SQL  
SQL Server  
Style Sheets  
VB.Net  
Visual Basic  
Web Authoring  
Web Services  
Web Standards  
XML  
Mobile Linux 
App Generation ROI 
IBM® developerWorks 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
XML

Designing Your Own XML Schema: Indicators
By: Jagadish Chaterjee
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 5 stars5 stars5 stars5 stars5 stars / 5
    2006-03-27

    Table of Contents:
  • Designing Your Own XML Schema: Indicators
  • The Choice indicator in XML Schema
  • The Sequence indicator in XML Schema
  • The maxOccurs and minOccurs indicators in XML Schema
  • Groups in XML Schema
  • Attribute Groups in XML Schema

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    Designing Your Own XML Schema: Indicators - The Choice indicator in XML Schema


    (Page 2 of 6 )

    Another indicator from the XML Schema vocabulary is the “Choice” indicator.  It is specially used to inform that one of the child elements could occur.  We can define as many numbers of elements as possible (with the “choice” indicator), but finally only one has to be chosen.  Let us consider the following schema:

    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
     elementFormDefault="qualified" attributeFormDefault=
    "unqualified">
      <xs:element name="Employees">
         <xs:annotation>
               <xs:documentation>Contains All Employee
    information</xs:documentation>
         </xs:annotation>
         <xs:complexType>
               <xs:sequence>
                     <xs:element name="Employee" maxOccurs="unbounded">
                           <xs:complexType>
                                 <xs:sequence>
                                       <xs:element name="ID"
     type="xs:string" />
                                       <xs:element name="Name"
     type="xs:string" />
                                       <xs:element
     name="EmployeeType">
                                             <xs:complexType>
                                                   <xs:choice>
                                                                <xs:element name="Management" type="xs:string" />
                                                                <xs:element name="Clerk" type="xs:string" />
                                                          </xs:choice>
                                             </xs:complexType>
                                       </xs:element>
                                 </xs:sequence>
                           </xs:complexType>
                     </xs:element>
               </xs:sequence>
         </xs:complexType>
         <xs:key name="PK_Employee_ID">
               <xs:selector xpath=".//Employee" />
               <xs:field xpath="ID" />
         </xs:key>
       </xs:element>
    </xs:schema>

    The most important fragment to concentrate on is the following:

    <xs:element name="EmployeeType">
      <xs:complexType>
            <xs:choice>
                  <xs:element name="Management" type="xs:string" />
                  <xs:element name="Clerk" type="xs:string" />
            </xs:choice>
      </xs:complexType>
    </xs:element>

    The above specifies that the “EmployeeType” element can contain “Management” or “Clerk” elements (but not both).  A sample XML document, which conforms to the above schema, would be as follows:

    <?xml version="1.0" encoding="UTF-8"?>
    <Employees xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:noNamespaceSchemaLocation="C:\Documents and
    Settings\Administrator\Desktop\Employees.xsd
    ">
          <Employee>
                <ID>1001</ID>
                <Name>Jag</Name>
                <EmployeeType>
                      <Management>Manager</Management>
                </EmployeeType>
          </Employee>
          <Employee>
                <ID>1002</ID>
                <Name>Chat</Name>
                <EmployeeType>
                      <Clerk>Admin</Clerk>
                </EmployeeType>
          </Employee>
    </Employees>



    More XML Articles
    More By Jagadish Chaterjee


       · Hello guys, this is another extension for my "XML Schema" series. enjoy!
     

    XML ARTICLES

    - Using Regions with XSL Formatting Objects
    - Using XSL Formatting Objects
    - More Schematron Features
    - Schematron Patterns and Validation
    - Using Schematron
    - Datatypes and More in RELAX NG
    - Providing Options in RELAX NG
    - An Introduction to RELAX NG
    - Path, Predicates, and XQuery
    - Using Predicates with XQuery
    - Navigating Input Documents Using Paths
    - XML Basics
    - Introduction to XPath
    - Simple Web Syndication with RSS 2.0
    - Java UI Design with an IDE







    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 5 Hosted by Hostway
    For more Enterprise Application Development news, visit eWeek