There are few things you cannot restrict with XSD:
---
<xs:attribute name="Create" type="xs:Creation" use="required"/>
.
.
.
<xs:simpleType name="Creation">
<xs:restriction base="xs:string">
<xs:enumeration value="Allow"/>
<xs:enumeration value="Deny"/>
</xs:restriction>
</xs:simpleType>
---
I think you can also use the xs:list facet instead of xs:restriction,
but I'm not very sure about that.
On Oct 6, 11:27 am, Jaydeep <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I am preparing XSD for some XML file required in my application. Snap
> shot of the XML is shown here:
>
> <ELE1 Create="Allow">
> <ELE2="Some value...."/>
> </ELE1>
>
> For this XML file I am preparing XSD. Valid values for an attribute
> "Create" of an element "ELE1" is either Allow or Deny. Also value
> should never be NULL.
>
> Would anybody please let me whether it is possible to assign such
> rules (for attribute) while preparing XSD or not?
>
> Thank you,
> Jaydeep
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web
Services,.NET Remoting" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/DotNetDevelopment
You may subscribe to group Feeds using a RSS Feed Reader to stay upto date
using following url
<a href="http://feeds.feedburner.com/DotNetDevelopment";>
http://feeds.feedburner.com/DotNetDevelopment</a>
-~----------~----~----~----~------~----~------~--~---
