Databases
StackOverflow2013
Postsdbo
POSame element name in xsd, but different validation logic
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSame element name in xsd, but different validation logic
    primarykey
    data
    text
    <p>I have xml file that seems like that</p> <pre><code>&lt;doc&gt; &lt;field name="simple_meta"&gt;book&lt;/field&gt; &lt;field name="complex_meta"&gt;journal&lt;/field&gt; &lt;field name="text_date"&gt;some text&lt;/field&gt; &lt;/doc&gt; </code></pre> <p>I would like to validate element text by pattern based on value in attribute "name". that is, if the value of attribute is "simple_meta" I want to make the "simpleRestriction" validation, in case of the "complex_meta" to make the "complexRestriction" validation. The problem is that I cannot define element with same name under the same node. Can someone to help me to resolve this problem?</p> <pre><code>&lt;xs:schema ......&gt; &lt;xs:simpleType name="simpleRestriction"&gt; &lt;xs:restriction base="xs:string"&gt; &lt;xs:maxLength value="20"/&gt; &lt;/xs:restriction&gt; &lt;/xs:simpleType&gt; &lt;xs:simpleType name="complexRestriction"&gt; &lt;xs:restriction base="xs:string"&gt; &lt;xs:maxLength value="10"/&gt; &lt;xs:pattern value="([\w])*"/&gt; &lt;/xs:restriction&gt; &lt;/xs:simpleType&gt; &lt;xs:element name="str"&gt; &lt;xs:complexType&gt; &lt;xs:simpleContent&gt; &lt;xs:extention base="simpleRestriction"&gt; &lt;xs:attribute name="name"&gt; &lt;xs:simpleType&gt; &lt;xs:restriction base="xs:string"&gt; &lt;xs:pattern value="simple_meta"/&gt; &lt;/xs:restriction&gt; &lt;/xs:simpleType&gt; &lt;/xs:attribute&gt; &lt;/xs:extention&gt; &lt;/xs:simpleContent&gt; &lt;/xs:ComplexType&gt; &lt;/xs:element&gt; &lt;xs:element name="str"&gt; &lt;xs:complexType&gt; &lt;xs:simpleContent&gt; &lt;xs:extention base="complexRestriction"&gt; &lt;xs:attribute name="name"&gt; &lt;xs:simpleType&gt; &lt;xs:restriction base="xs:string"&gt; &lt;xs:pattern value="complex_meta"/&gt; &lt;/xs:restriction&gt; &lt;/xs:simpleType&gt; &lt;/xs:attribute&gt; &lt;/xs:extention&gt; &lt;/xs:simpleContent&gt; &lt;/xs:ComplexType&gt; &lt;/xs:element&gt; &lt;/xs:schema&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USSveta
    1. USSveta
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSame element name in xsd, but different validation logic
      1. USPaweł Wyrwiński
      1. VTFavorite
    2. VO
      singulars
      1. POSame element name in xsd, but different validation logic
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis cannot be done with XSD 1.0 - you need some other system (Schematron or RelaxNG or XSD 1.1 maybe, but I am not familiar with them)
      singulars
      1. POSame element name in xsd, but different validation logic
      1. USMiMo
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload