xsd.exe (version 1.1) can't deal with <xs:annotation> ?

[SA]

Hi all,

in the following situation:

<xs:element name="Type">

<xs:simpleTyp e>

<xs:restricti on base="xs:NMTOKE N">

<xs:enumerati on value="I"/>

<xs:enumerati on value="J"/>

<xs:enumerati on value="P">

<xs:annotation> P will occur for Primary.</xs:annotation>

</xs:enumeration>

<xs:enumerati on value="S">

<xs:annotation> S will occur for Secondary.</xs:annotation>

</xs:enumeration>

</xs:restriction>

</xs:simpleType>

</xs:element>

which is part of an otherwise valid Schema, xsd.exe fails to generate the
class because of the text in the <xs:annotatio n> elements.

Is this behavior correct?

--
Sven.

[Derek Harmon]

"SA" <in*********@fr eemail.nl> wrote in message news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..

<xs:enumerati on value="P">
<xs:annotation> P will occur for Primary.</xs:annotation>
</xs:enumeration> : : which is part of an otherwise valid Schema, xsd.exe fails to generate the
class because of the text in the <xs:annotatio n> elements.

Is this behavior correct?

I believe the <xs:annotatio n> element is not valid (e.g., xsd is correct), because
the definition of an annotation's content model is:

( appinfo | documentation )*

not character data (i.e., <xs:annotatio n> cannot contain an immediate child text node).

See XML Schema 1.0 Part 1 Section 3.13.2,

http://www.w3.org/TR/2004/REC-xmlsch...are-annotation

Try putting the text into an <xs:documentati on> child element, like this,

<xs:enumerati on value="P">
<xs:annotatio n>
<xs:documentati on>P will occur for Primary.</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
Derek Harmon

[SA]

Derek:

That was it indeed.

Not a Schema expert myself, I had to deal with the schema that was handed to
me by a vendor.

Thanks,

--
Sven.

"Derek Harmon" <lo*******@msn. com> wrote in message
news:#y******** ******@TK2MSFTN GP15.phx.gbl...

"SA" <in*********@fr eemail.nl> wrote in message news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..

<xs:enumerati on value="P">
<xs:annotation> P will occur for Primary.</xs:annotation>
</xs:enumeration>

: :

which is part of an otherwise valid Schema, xsd.exe fails to generate the class because of the text in the <xs:annotatio n> elements.

Is this behavior correct?

I believe the <xs:annotatio n> element is not valid (e.g., xsd is correct),

because the definition of an annotation's content model is:

( appinfo | documentation )*

not character data (i.e., <xs:annotatio n> cannot contain an immediate child text node).
See XML Schema 1.0 Part 1 Section 3.13.2,

http://www.w3.org/TR/2004/REC-xmlsch...are-annotation
Try putting the text into an <xs:documentati on> child element, like this,

<xs:enumerati on value="P">
<xs:annotatio n>
<xs:documentati on>P will occur for Primary.</xs:documentatio n>
</xs:annotation>
</xs:enumeration>
Derek Harmon