[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Simple xs:restriction issue

• To: xml-dev@l...
• Subject: Simple xs:restriction issue
• From: Jimmy Monin <jm.ais40@w...>
• Date: Wed, 16 Nov 2005 17:57:27 +0100
• User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)

Hi all,

I have to deal with the following schema defined as an interface with a 
proprietary software :
.
.
.
  <xs:simpleType name="TypeTypeAvion">
    <xs:restriction base="xs:string">
      <xs:enumeration value="SEM 3"/>
      <xs:enumeration value="SEM 4"/>
      <xs:enumeration value="Rafale F1"/>
      <xs:enumeration value="M2000D R2"/>
      <xs:enumeration value="M2000N K2"/>
      <xs:enumeration value="M2000DA S4-2A"/>
      <xs:enumeration value="M2000DA S5-2C"/>
      <xs:enumeration value="M2000-5F SF1-C"/>
      <xs:enumeration value="F1 CT T2"/>
      <xs:enumeration value="F1 CR F7"/>
      <xs:pattern value=".*"/>
    </xs:restriction>
  </xs:simpleType>
.
.
.
The main idea was (I guess) to start defining a list of acceptable 
value, but still accept any (use of pattern). With Xerces2 included in 
JAXP 1.21, I get an error message (value not valid with respect to its 
type) with a string that differs from those listed.
My question is : is this schema definition valid?

Thanks in advance,

-- 
Jimmy Monin

SCM & Development
EADS Systems & Defence Electronics

• Follow-Ups:
  • Re: Simple xs:restriction issue
    • From: "Pete Cordell" <petexmldev@t...>
  • RE: Simple xs:restriction issue
    • From: "Michael Kay" <mike@s...>

• Prev by Date: Re: Key constraint on optional attribute
• Next by Date: XTECH 2006 Call for Papers announced
• Previous by thread: Key constraint on optional attribute
• Next by thread: RE: Simple xs:restriction issue
• Index(es):
  • Date
  • Thread