• To: russ@w...
• Subject: RE: Schema issue with enumerated element content
• From: Kasimier Buchcik <K.Buchcik@4...>
• Date: Fri, 18 Nov 2005 21:48:37 +0100
• Cc: ML-xml-dev <xml-dev@l...>
• In-reply-to: <20051118132412.27a792c0bf3172901570a5f4e87e410e.a6633a4d1b.wbe@e...>
• References: <20051118132412.27a792c0bf3172901570a5f4e87e410e.a6633a4d1b.wbe@e...>

Hi,

On Fri, 2005-11-18 at 13:24 -0700, russ@w... wrote:
> Thanks Kasimier. I think I'll just move enumerations into attributes.
> A little more complex for end users, but seemingly much better on the
> schema end.

The nice thing is that I learned - with the help of Henry's reply -
that the following (which I copied from Henry's answer and modified
a bit):

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

 <xs:element name="ElemName">
  <xs:complexType>
   <xs:simpleContent>
    <xs:extension base="vals">
     <xs:attribute name="attr" type="xs:string"/>
    </xs:extension>
   </xs:simpleContent>
  </xs:complexType>
 </xs:element>

... is the same as:

<xs:element name="ElemName">
  <xs:complexType>
    <xs:simpleContent>
      <xs:restriction base="xs:anyType">
        <xs:simpleType>
          <xs:list>
            <xs:simpleType>
              <xs:restriction base="xs:string"/>
            </xs:simpleType>
          </xs:list>
        </xs:simpleType>
	<xs:attribute name="attr" type="xs:string"/>
      </xs:restriction>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>

I'd prefer Henry's version - it looks easier to understand.

Regards,

Kasimier

• References:
  • RE: Schema issue with enumerated element content
    • From: russ@w...

• Prev by Date: RE: Schema issue with enumerated element content
• Next by Date: RE: XTECH 2006 Call for Papers announced
• Previous by thread: RE: Schema issue with enumerated element content
• Next by thread: Public registry for unprefixed XPointer schemes launched by W3C
• Index(es):
  • Date
  • Thread