Return to Answer

<xs:complexType name="Item" /> 

<xs:sequence> <xs:element minOccurs="0" maxOccurs="1" name="Name" type="xs:string" /> </xs:sequence> 

 <xs:complexType name="Item"> <xs:sequence> <xs:element minOccurs="1" maxOccurs="1" name="Id" type="xs:int" /> </xs:sequence> </xs:complexType> 

 <xs:complexType name="Item" /> 

 <xs:complexType name="Item"> <xs:sequence> <xs:element minOccurs="0" maxOccurs="1" name="Id" type="xs:int" /> </xs:sequence> </xs:complexType> 

<xs:complexType name="Item" /> 

<xs:sequence> <xs:element minOccurs="0" maxOccurs="1" name="Name" type="xs:string" /> </xs:sequence> 

 <xs:complexType name="Item"> <xs:sequence> <xs:element minOccurs="1" maxOccurs="1" name="Id" type="xs:int" /> </xs:sequence> </xs:complexType> 

 <xs:complexType name="Item" /> 

 <xs:complexType name="Item"> <xs:sequence> <xs:element minOccurs="0" maxOccurs="1" name="Id" type="xs:int" /> </xs:sequence> </xs:complexType> 

An additional complexity can arise when the property in question is of a non-nullable value type. Consider the following three versions of Item. Firstly, a version with a unconditionally included value property:

An additional complexity can arise when the property in question is of a non-nullable value type. Consider the following three versions of Item. Firstly, a version with an unconditionally included value property:

While the following for #2 includes the Name member:

While the following for #2 conditionally includes the Name member: