W3C home > Mailing lists > Public > xmlschema-dev@w3.org > October 2003

Re: Enumeration component and restriction

From: Henry S. Thompson <ht@cogsci.ed.ac.uk>
Date: Fri, 10 Oct 2003 09:23:50 +0100
To: "Nikola" <nikola.stojanovic@acm.org>
Cc: <xmlschema-dev@w3.org>
Message-ID: <f5bsmm1cxgp.fsf@erasmus.inf.ed.ac.uk>

"Nikola" <nikola.stojanovic@acm.org> writes:

> <Henry S. Thompson>
> Yeah, the two parts of the REC are in conflict here.  I'll raise an
> official issue.
>
> The intended semantics are clear (it should be a restriction, after
> all), but the prose gets pretty confused.
> </Henry S. Thompson>
>
> Could you explain intended restriction semantics in a litlle bit different example. Here is the schema:
>
>  <xs:simpleType name = "A">
>   <xs:restriction base = "xs:token">
>    <xs:enumeration value = "x"/>
>    <xs:enumeration value = "y"/>
>    <xs:enumeration value = "z"/>
>   </xs:restriction>
>  </xs:simpleType>
>
>  <xs:simpleType name = "B">
>   <xs:restriction base = "A">
>    <xs:enumeration value = "blabla"/>
>   </xs:restriction>
>  </xs:simpleType>
>
> Is this valid? XSV (2.5-2 of 2003/07/09) reports no schema errors.

No, not valid.  XSV doesn't check this, but it should.  

ht
-- 
  Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
                      Half-time member of W3C Team
     2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
	    Fax: (44) 131 650-4587, e-mail: ht@cogsci.ed.ac.uk
		     URL: http://www.ltg.ed.ac.uk/~ht/
 [mail really from me _always_ has this .sig -- mail without it is forged spam]
Received on Friday, 10 October 2003 04:23:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:40 GMT