Add new assertion on text element in collection.xconf.xsd

[daliboris]

Following index definition shouldn't be valid, when indexing it throws all instances of a given field name must have the same term vectors settings (storeTermVectors changed for field="p-field") error.

<collection>
  <index>
    <lucene>
      <text qname="tei:p" field="p-field">
        <field name="p-field" />
      </text>
    </lucene>
  </index>
</collection>

The problem is caused by identical field names in the text index definition and in the field definition. (That would be valid: <text qname="tei:p" field="p-field"> <field name="p-field-inner" />).

Change textType definition in the XSD Schema to validate this issue:

<xs:complexType name="textType">
        <xs:annotation>
            <xs:documentation>Either @qname or @match must be specified. Not both!</xs:documentation>
            <xs:documentation>If both text/@field and field/@name exist, their values must be different!</xs:documentation>
        </xs:annotation>
        <xs:group ref="cc:textInstruction"/>
        <xs:attributeGroup ref="cc:qnameOpt"/>
        <xs:attributeGroup ref="cc:matchOpt"/>
        <xs:attributeGroup ref="cc:analyzerOpt"/>
        <xs:attributeGroup ref="cc:boostOpt"/>
        <xs:attributeGroup ref="cc:fieldOpt"/>
        <xs:attributeGroup ref="cc:indexOpt"/>
        <xs:assert test="(@qname and not(@match)) or (@match and not(@qname))"/>
        <xs:assert test="not(exists(@field)) or not(@field = cc:field/@name)" />
    </xs:complexType>

[dizzzz]

Hmmmn ow I see that we actually use XML Schema 1.1 constructs in our codecase. That is a pity as the used library has some issues. Eg is it really maintained? [yes it is, hard to find]

recent blog: https://blog.frankel.ch/xml-schema-validation-1-1/

[daliboris]

I have a feeling that the xconf file is not validated against XSD before processing anyway.

[line-o]

Not before processing but it is verified in eXide when you open it there.