Schema Derivation by Restriction

[Wells Caughey]

I am trying to create an XML Schema type definition by deriving from another
type definition using restriction. For example suppose my base type was
this:

<xs:schema <<schema element setup>> >
<xs:complexType name="Fruits">
<xs:sequence>
<xs:any minOccurs="8" maxOccurs="8"/>
</xs:sequence>
</xs:complexType>
</xs:schema>

and I wanted to derive to create a type that requires that the first fruit
is an apple but still have a max of 8 "Fruits". For example without using
derivation I'd have:

<xs:schema <<schema element setup>> >
<xs:complexType name="Fruits">
<xs:sequence>
<xs:element name="Apple">
<xs:complexType/>
</xs:element>
<xs:any minOccurs="7" maxOccurs="7"/>
</xs:sequence>
</xs:complexType>
</xs:schema>

How would I acheive this using derivation by restriction?

Thanks,
Wells

[Kevin Yu [MSFT]]

Hi Wells,

Thank you for using MSDN Newsgroup! My name is Kevin, and I will be
assisting you on this issue.

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that you're writing the Xml schema of a type
and would like to reuse it with derivation.

As far as I know, we have to re-list all the parts of the base types while
doing derivation. Here's an example. Suppose we have defined a Person type.
Now we need to derive from it to define a RestrictedPerson. It will looks
like the following:

<xsd:complexType name="RestrictedPerson">
<xsd:complexContent>
<xsd:restriction base="tns:Person">
<!-- redefine base type's particles here -->
...
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>

The xsd:restriction element indicates the base type we're restricting and
it contains the new definitions for all of the base type's particles (e.g.,
compositors, element definitions, wildcards, etc.). When doing this, you
must list all of the particles of the base type as well as those of the
base type's ancestors, if it has any. I think the complexity might be
similar to not using derivation.

Here is an article about how to designing XML schema libraries. Hope this
will be helpful to you.

http://msdn.microsoft.com/library/de...us/dnxml/html/
desxsdlib.asp

Does this answer your question? If anything is unclear, please feel free to
reply to the post.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

[Wells Caughey]

Hi Kevin,

Thank you for the reply. Your reply and the link are exactly what I needed.
I tried get this info from the XML Schema definition, but that is not the
easiest to read document.

Thanks,
Wells
"Kevin Yu [MSFT]" <v-****@online.microsoft.com> wrote in message
news:2g**************@cpmsftngxa08.phx.gbl...

Hi Wells,

Thank you for using MSDN Newsgroup! My name is Kevin, and I will be
assisting you on this issue.

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that you're writing the Xml schema of a type and would like to reuse it with derivation.

As far as I know, we have to re-list all the parts of the base types while
doing derivation. Here's an example. Suppose we have defined a Person type. Now we need to derive from it to define a RestrictedPerson. It will looks
like the following:

<xsd:complexType name="RestrictedPerson">
<xsd:complexContent>
<xsd:restriction base="tns:Person">
<!-- redefine base type's particles here -->
...
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>

The xsd:restriction element indicates the base type we're restricting and
it contains the new definitions for all of the base type's particles (e.g., compositors, element definitions, wildcards, etc.). When doing this, you
must list all of the particles of the base type as well as those of the
base type's ancestors, if it has any. I think the complexity might be
similar to not using derivation.

Here is an article about how to designing XML schema libraries. Hope this
will be helpful to you.

http://msdn.microsoft.com/library/de...us/dnxml/html/ desxsdlib.asp

Does this answer your question? If anything is unclear, please feel free to reply to the post.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

[Kevin Yu [MSFT]]

Hi Wells,

I'm glad that my reply makes sense. If you have any further questions or
concerns, please feel free to post it in the group. I'm standing by to be
of assistance.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."