Make XML elements required based on attribute values in XSD -

-

my requirement have xsd file checks elements based on attribute values. able write xsd point can restrict attribute values of application/@type. can me complete xsd file can make elements required based on application/@type attribute?

i want make

  • packagearg required when application/@type "batch"
  • version required when application/@type "service"
  • project required when application/@type web" or "service"

xml file

<applications>             <application name="configmanagement" type="web">                     <projectdirname>configmanagement</projectdirname>         <project>web.configmanagement.csproj</project>         <outputdirname>configmanagement</outputdirname>                 </application>     <application name="util" type="web">                     <projectdirname>web</projectdirname>         <project>web.csproj</project>                 <outputdirname>util</outputdirname>         </application>     <application name="configservice" type="service">         <projectdirname>webservices\configservice</projectdirname>         <project>configservice.csproj</project>             <version>2015\04</version>         <outputdirname>configservice</outputdirname>     </application>     <application name="deliveremail" type="batch">                 <projectdirname>\batch\deliveremail</projectdirname>         <packagearg>release</packagearg>                 <outputdirname>tidal\deliveremail</outputdirname>                 </application> </applications>

xsd file

<xs:element name="applications" maxoccurs="1">   <xs:complextype>     <xs:sequence>       <xs:element name="application" maxoccurs="unbounded" minoccurs="1">         <xs:complextype>           <xs:all>             <xs:element type="xs:string" name="projectdirname"/>             <xs:element type="xs:string" name="project" minoccurs="0"/>             <xs:element type="xs:string" name="version" minoccurs="0"/>             <xs:element type="xs:string" name="packagearg" minoccurs="0"/>             <xs:element type="xs:string" name="outputdirname"/>           </xs:all>           <xs:attribute type="xs:string" name="name" use="optional"/>           <xs:attribute name="type" use="required">             <xs:simpletype>               <xs:restriction base="xs:string">                 <xs:enumeration value="web"/>                 <xs:enumeration value="batch"/>                 <xs:enumeration value="service"/>               </xs:restriction>             </xs:simpletype>           </xs:attribute>         </xs:complextype>       </xs:element>     </xs:sequence>   </xs:complextype> </xs:element>

update: op has edited question remove use of xs:assert , has stated in comments validation must take place in c#. answer op's question becomes:

you cannot enforce constraint varies requiredness of element based on attribute value using xsd 1.0, , microsoft not support xsd 1.1, therefore must either relax constraints or check them outside of xsd.

original xsd 1.1 answer

(retained benefit of future readers)

you're close, assertion,

      <xs:assert test="count(./packagearg[@type eq 'batch']) eq 1"/>

tests @type on packagearg when should test @type on application.

the following xsd validate xml , enforce attribute-dependent requirements:

xsd 1.1

<?xml version="1.0" encoding="utf-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/xmlschema"            xmlns:vc="http://www.w3.org/2007/xmlschema-versioning"            vc:minversion="1.1">   <xs:element name="applications">     <xs:complextype>       <xs:sequence>         <xs:element name="application" maxoccurs="unbounded" minoccurs="1">           <xs:complextype>             <xs:all>               <xs:element type="xs:string" name="projectdirname"/>               <xs:element type="xs:string" name="project" minoccurs="0"/>               <xs:element type="xs:string" name="version" minoccurs="0"/>               <xs:element type="xs:string" name="packagearg" minoccurs="0"/>               <xs:element type="xs:string" name="outputdirname"/>             </xs:all>             <xs:attribute type="xs:string" name="name" use="optional"/>             <xs:attribute name="type" use="required">               <xs:simpletype>                 <xs:restriction base="xs:string">                   <xs:enumeration value="web"/>                   <xs:enumeration value="batch"/>                   <xs:enumeration value="service"/>                 </xs:restriction>               </xs:simpletype>             </xs:attribute>             <xs:assert test="packagearg or @type != 'batch'"/>             <xs:assert test="version or @type != 'service'"/>             <xs:assert test="project or not(@type = 'web' or @type = 'service')"/>           </xs:complextype>         </xs:element>       </xs:sequence>     </xs:complextype>   </xs:element> </xs:schema>

be aware microsoft not support xsd 1.1. (you've tagged question 'msxml').


Comments

Post a Comment

Popular posts from this blog

python - TypeError: start must be a integer -

-
i trying draw 5 turtles, getting typeerror on line 25. here code: import turtle wn = turtle.screen() redrose = turtle.turtle() color = input("what background color be?") fillcolor_f = input("what color of rose be?") redrose.hideturtle() redrose.speed(30) redrose.penup() redrose.left(180) redrose.forward(175) redrose.right(90) redrose.forward(30) redrose.right(90) redrose.pendown() def drawrose(red): redrose.color("pink") redrose.fillcolor(fillcolor_f) redrose.fill(true) in range(red): redrose.forward(i) redrose.right(49) in range(5): drawrose(redrose) redrose.penup() redrose.forward(350) redrose.right(144) redrose.pendown() redrose.fill(false) drawrose(50) wn.bgcolor(color) i trying draw 5 roses, produces errors. doing in interactivepython.org. you recursively calling drawrose wrong parameter. on line 23 ( for in range(red): ) expect red integer...
Read more

c# - DevExpress RepositoryItemComboBox BackColor property ignored -

-
i have following code almost works properly; private void cbstatus_drawitem(object sender, listboxdrawitemeventargs e) { string item = e.item string; if (item != null) { switch (item) { case "1": e.appearance.forecolor = color.green; e.appearance.backcolor = color.green; break; case "2": e.appearance.forecolor = color.orange; e.appearance.backcolor = color.orange; break; case "3": e.appearance.forecolor = color.red; e.appearance.backcolor = color.red; break; } } } when dropdown shown, items forecolor correct, backcolor remains whatever backcolor of theme is; i.e. if i've got set dark theme, backcolor dark, cells in gridview, rather being green/orange/red. i've tried setting e.appearance.options.usebackcolor trying set e....
Read more

django - Creating multiple model instances in DRF3 -

-
1) create multiple model instances 1 api call, asked here: how create multiple model instances django rest framework? tried solution named in link, no success. i trying upload multiple files in 1 api call. result: files uploaded (only once overwrote perform_create) 1 instance created (if send 2 files, latter created instance). my code: class fileuploadserializer(serializers.modelserializer): def __init__(self, *args, **kwargs): many = kwargs.pop('many', true) super(fileuploadserializer, self).__init__(many=many, *args, **kwargs) class meta: model = fileupload read_only_fields = ('created', 'datafile', 'owner') class fileuploadviewset(viewsets.modelviewset): queryset = fileupload.objects.all() serializer_class = fileuploadserializer parser_classes = (multipartparser, formparser, ) def perform_create(self, serializer): file_list = self.request.data.getlist('file') ...
Read more