CODEWITHSUNDEEP
xmlxsd
Craig
Craig

Reputation: 2376

How to Override Xsd element inside of parent/extended element

I'm creating a new dataexchange service at my company. We would like to extend an existing object that is defined in our core.xsd definitions file. Here is an example of what I need to do:

<xs:complexType name="parentType">
  <xs:sequence>
    <xs:element name="departmentName" type="core:DEPARTMENT_NAME" 
                minOccurs="0" maxOccurs="1" />    
  </xs:sequence>
</xs:complexType>

<xs:complexType name="childType">
  <xs:complexContent>
    <xs:extension base="parentType">
      <xs:sequence>
        <xs:element name="departmentName" 
                    type="core:DEPARTMENT_NAME" 
                    minOccurs="1" maxOccurs="1"/>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>

I think this makes perfect sense. I want to override the parent element and make it required. However, a valid xml file would be this. Where there is now an extra department name!?

<childType>
  <departmentName>HR</departmentName>
  <departmentName>IT</departmentName>
</childType>

How can I do this so that the XML file would become:

<childType>
  <departmentName>IT</departmentName>
</childType>

Thanks, Craig

Upvotes: 14

Views: 18370

Answers (2)

Deepu Singh
Deepu Singh

Reputation: 23

if my scenario is as below
<xs:complexType name="parentType">
  <xs:sequence>
    <xs:element name="departmentName" type="core:DEPARTMENT_NAME" 
                minOccurs="1"/>    
  </xs:sequence>
</xs:complexType>

    <xs:complexType name="childType">
      <xs:complexContent>
        <xs:extension base="parentType">
          <xs:sequence>
            <xs:element name="departmentName" 
                    type="core:DEPARTMENT_NAME" 
                    minOccurs="0"/>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
than what will be the solution.

Upvotes: 0

Petru Gardea
Petru Gardea

Reputation: 21658

You need to use restriction instead of extension. This would be a full valid schema for the scenario you indicated (I've liberally used namespaces to make it valid).

<?xml version="1.0" encoding="utf-8" ?>
<!-- XML Schema generated by QTAssistant/XSD Module (http://www.paschidev.com) -->
<xs:schema targetNamespace="http://tempuri.org/XMLSchema.xsd" xmlns="http://tempuri.org/XMLSchema.xsd" xmlns:core="http://tempuri.org/XMLSchema.xsd" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <xs:complexType name="parentType">
        <xs:sequence>
            <xs:element name="departmentName" type="core:DEPARTMENT_NAME" minOccurs="0"/>
        </xs:sequence>
    </xs:complexType>

    <xs:complexType name="childType">
        <xs:complexContent>
            <xs:restriction base="parentType">
                <xs:sequence>
                    <xs:element name="departmentName" type="core:DEPARTMENT_NAME"/>
                </xs:sequence>
            </xs:restriction>
        </xs:complexContent>
    </xs:complexType>

    <xs:simpleType name="DEPARTMENT_NAME">
        <xs:restriction base="xs:string"/>
    </xs:simpleType>

    <xs:element name="childType" type="childType"/>
</xs:schema>

Upvotes: 10

Related Questions