xml - Specify type for an element that must have at least one child element -


the element elements must contain @ least element element1 or element2, each of them @ once. i've specified following xml schema:

<?xml version="1.0" encoding="utf-8"?>  <xs:schema xmlns:xs="http://www.w3.org/2001/xmlschema" elementformdefault="qualified">    <xs:element name="elements" type ="elementstype"/>    <xs:complextype name="elementstype">       <xs:choice>          <xs:sequence>             <xs:element name="element1" type="xs:string" minoccurs="0"/>             <xs:element name="element2" type="xs:double"/>          </xs:sequence>          <xs:element name="element1" type="xs:string"/>       </xs:choice>    </xs:complextype> <xs:schema/>

validation of xml schema gives "unique particle attribution" violation error:

cos-nonambig: element1 , element1 (or elements substitution group) violate "unique particle attribution". during validation against schema, ambiguity created 2 particles.

why?

the reason xsd violates unique particle attribution due ambiguity across xs:choice whether element1 should associated first or second choice possibility.

you can avoid violation , still require @ least 1 of element1 , element2 using xsd 1.1's assertions:

<?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" elementformdefault="qualified"   vc:minversion="1.1">   <xs:element name="elements" type ="elementstype"/>   <xs:complextype name="elementstype">     <xs:sequence>       <xs:element name="element1" type="xs:string" minoccurs="0"/>       <xs:element name="element2" type="xs:double" minoccurs="0"/>     </xs:sequence>     <xs:assert test="count(*) > 0"/>   </xs:complextype> </xs:schema>

update

i don't understand why there ambiguity. if instance contains element1 , element2 or element2 first choice possible. otherwise, if there element2, second choice applies only.

pretend you're validating parser , encounter element1. won't know whether associate first or second branch of xs:choice, ambiguity. sure, look-ahead 1 level , resolve ambiguity, how far should have look-ahead? xsd recommendation says validating parser shouldn't have look-ahead @ in these circumstances. therefore, job validator parser easier (but job xsd author bit harder).


Comments

Post a Comment

Popular posts from this blog

Email notification in google apps script -

https://support.google.com/docs/answer/91588?hl=en i have sheet the cells filled in data pulled via apps script, website. pull in exact same data, not. on old sheets version use able emails when data "changes" different value. new sheets, email when new data pasted cells, though exact same data......and, can't set @ ranges anymore, entire document. there easy way watch cells when data changes, , email myself? this looks lot you're trying do. for checking whether value has changed after edit, this gives necessary information it. hence, know whether new value same 1 or not. implementing "workaround" talked in second link, able compare , send email myself if value changed. initiate onedit trigger goes off onedit function uses these lines after checks in place have passed. var email = "xyz@whatever.com"; mailapp.sendemail(email, "triggermail", "a change has occurred in sheet"); note: sends "notification...
Read more

c++ - Difference between pre and post decrement in recursive function argument -

i have following sample code used pre-decrement void function(int c) { if(c == 0) { return; } else { cout << "dp" << c << endl; function(--c); cout << c << endl; return; } } this function give output input 4 : dp3 dp2 dp1 dp0 0 1 2 3 but when use post decrement void function(int c) { if(c == 0) { return; } else { cout << "dp" << c << endl; function(c--); cout << c << endl; return; } } output goes in infinite loop dp4 can explain me in detail why happens ? this happens because function(c--) called same value of c , when finishes c decremented. recursively called, hence called same value no chance of return , hit stack overflow error. assume this, int x = 1, y = 0; y = x++ result y == 1 , x == 2. if y = ++x , bot x , y 2.
Read more

javascript - IE11 incompatibility with jQuery's 'readonly'? -

the code i'm running has no issues in firefox, or chrome. user typing 1 textbox, tabs next , can continue typing that. when run webpage on ie11, user tabs next textbox , can't type in. textbox has double-clicked before user can insert anything. i've googled , seems ie give problems when using older jquery (i.e. prefers 'prop' 'attr' ). in code below jquery's readonly keyword being used in way ie11 no longer recognise/accept? i assume issue readonly , removeclass('ignore') working expected. //when focus on textbox 1 $("#field1").focus(function() { //remove readonly property textbox 1 $('#field1').prop('readonly', false).removeclass('ignore'); //add readonly property other textboxes $('#field2, #field3, #field4') .prop('readonly', 'readonly').addclass('ignore').val(''); }); i'm using jquery 2.1.3 ...
Read more