[
Lists Home |
Date Index |
Thread Index
]
I try the example:
<xs:simpleType name='MyEnum' >
<xs:restriction base='xs:QName' >
<xs:enumeration value='foo:Val1' />
<xs:enumeration value='foo:Val2' />
<xs:enumeration value='foo:Val3' />
</xs:restriction>
</xs:simpleType>
<xs:simpleType name='MyOpenEnum' >
<xs:union memberTypes='tns:MyEnum xs:QName' />
</xs:simpleType>
<xs:element name='MyData' type='tns:MyOpenEnum' />
but, in the code, MyData is the String type. That means i can't use a MyEnum instance for MyData.
Is that right?
Best Regards.
Jacky Keenmicro
----- Original Message -----
From: "Jonathan Robie" <jonathan.robie@datadirect.com>
To: "Rich Salz" <rsalz@datapower.com>
Cc: "David Carlisle" <davidc@nag.co.uk>; <xml-dev@lists.xml.org>
Sent: Thursday, October 14, 2004 9:08 PM
Subject: Re: [xml-dev] Element declaring
> Rich Salz wrote:
>
> > Sure. It's like saying "xsd:string" except that it gives special
> > significance to particular values. You can enumerate them in the schema,
> > define semantics in a spec more easily, etc.
> >
> > It's just a neat hack. For standards, in particular, that want to define
> > some base functionality and still allow an extensibility point, this makes
> > it explicit.
>
> Right - programs can know exactly what to do with the enumerated values.
> If it's not one of these, then all the program cares about is that it is
> something else, which is why I like the 'other' trick. But the program
> might want to know where to find the user's value so it can be
> displayed, even if it has no special semantics for the program.
>
> Jonathan
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>
>
>
|
