XML
  Home arrow XML arrow Page 2 - Designing Your own XML Schema: Constrainin...
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: Constraining with Restrictions
By: Jagadish Chaterjee
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 5 stars5 stars5 stars5 stars5 stars / 5
    2006-03-13

    Table of Contents:
  • Designing Your own XML Schema: Constraining with Restrictions
  • Working with other data types in XML Schema
  • Constraining values (restricting a range)
  • Restricting lengths in XML Schema
  • Restrictions based on lists (or enumerations) in XML Schema
  • Defining a Primary Key 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: Constraining with Restrictions - Working with other data types in XML Schema


    (Page 2 of 6 )

    In this section, we shall go through an example covering most of the important data types available in the XML Schema definition.  Let us have a look at the following XML schema now:

    <?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>Comment describing your root
    element
    </xs:documentation>
                </xs:annotation>
                <xs:complexType>
                      <xs:sequence>
                            <xs:element name="Employee" maxOccurs="unbounded">
                                  <xs:complexType>
                                        <xs:sequence>
                                              <xs:element name="Name" type="xs:string"/>
                                              <xs:element name="HireDate" type="xs:date"/>
                                              <xs:element name="isMarried" type="xs:boolean" minOccurs="0"/>
                                              <xs:element name="Salary" type="xs:float"/>
                                              <xs:element name="Age" type="xs:integer"/>
                                        </xs:sequence>
                                        <xs:attribute name="ID" type="xs:string" use="required"/>
                                  </xs:complexType>
                            </xs:element>
                      </xs:sequence>
                </xs:complexType>
          </xs:element>
    </xs:schema>



    According to the above example, the document root element would be “Employees.”  The element “Employees” internally can contain “Employee” elements.  The element “Employee” internally contains a few more elements: “Name,” “Hiredate,” “isMarried,” “Salary” and “Age.”  You should observe that there could be any number of “Employee” elements within “Employee.” 

    You should also observe that “Name,” “HireDate,” “isMarried,” “Salary” and “Age” are defined with different simple data types rather than with “complex types.”  The only complex elements are “Employees” and “Employee.”  I also declared an attribute ID for the “Employee” element as follows:

    <xs:attribute name="ID" type="xs:int" use="required"/>

    Another important point to observe is that the “isMarried” element is declared as optional.  This is possible by making “minOccurs” be “0” (default is “1”).

    Now, how would the XML document look when it conformed to the above XML Schema?  The following would be a sample XML document which conforms to the XML Schema above.

    <?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\ForDec\ForDec\XSLT\XMLExamples\02
    \SampleDataTypes.xsd
    ">
          <Employee ID="1001">
                <Name>Jag</Name>
                <HireDate>1978-06-25</HireDate>
                <isMarried>false</isMarried>
                <Salary>2500</Salary>
                <Age>27</Age>
          </Employee>
          <Employee ID="1002">
                <Name>Winner</Name>
                <HireDate>1985-09-08</HireDate>
                <Salary>2500</Salary>
                <Age>20</Age>
          </Employee>
    </Employees>


    More XML Articles
    More By Jagadish Chaterjee


       · Hai, this is another extension of the 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 4 Hosted by Hostway
    For more Enterprise Application Development news, visit eWeek