troubles defining index

[Flush]

Hi, I have a hugh scheme about 15000 lines. I can define it in tamino without troubles, but it crashes when I add an standar Index.

The error message is

Tamino access failure (7931, INOXDE7931, An error occurred while processing a schema document, INOXDE7528: Line 12, Column 5: Node declarations are not consistent: child nodes xs:element ‘id’ at Line 14883, Column 4 and xs:element ‘id’ at Line 15124, Column 4 of element ‘cuerpo’)

Line 12column 5 is :

<xs:element name=“esquemaPlantilla”>
xs:complexType
xs:sequence
<xs:element ref=“metaDatosEsquema”/>
<xs:element name=“cuerpo” type=“xs:anyType”/>“line 12”
</xs:sequence>
</xs:complexType>
</xs:element>

Line 14883 is:

<xs:complexType name=“ProfesionalPrimaria2Type”>
xs:sequence
<xs:element name=“id” type=“xs:integer” minOccurs=“0”/>“line 14883”
<xs:element name=“version” type=“xs:integer” minOccurs=“0”/>
<xs:element name=“cnp” type=“xs:long” minOccurs=“0”/>
<xs:element name=“idUsuarioIanus” type=“xs:string” minOccurs=“0”/>
<xs:element name=“nombre” type=“xs:string” minOccurs=“0”/>
<xs:element name=“apellido1” type=“xs:string” minOccurs=“0”/>
<xs:element name=“apellido2” type=“xs:string” minOccurs=“0”/>
</xs:sequence>
</xs:complexType>

Line 15124 is:

<xs:complexType name=“idType”>
xs:sequence
<xs:element name=“id”>"line 15124 "
xs:annotation
xs:appinfo
tsd:elementInfo
tsd:physical
tsd:which/plantillaClinica/metaDatosPlantilla/idPlantilla/id</tsd:which>
tsd:native
tsd:index
tsd:standard/
</tsd:index>
</tsd:native>
</tsd:physical>
</tsd:elementInfo>
</xs:appinfo>
</xs:annotation>
xs:complexType
xs:simpleContent
<xs:extension base=“xs:string”>
<xs:attribute name=“version” type=“xs:long” use=“optional”/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element ref=“idSrvXML” minOccurs=“0”/>
</xs:sequence>
</xs:complexType>

The troubles came when I define the index.
Anyone knows the solution to my trouble?
Thanks and forgive my very bad English
Flush

[Flush]

It only happens in Tamino 4.4.1.5. It works in Tamino 4.2.1.

[Dr_Harald_Schoening (Harald Schöning)]

Hi,

yes, Tamino 4.4 has corrected some gaps in the type checking. You seem to be defining an index on all occurrences of “id”? Unfortunately, I do not see teh index definition in your snippets
The issue is that not all the id instances have the same type (in one case anyType, in the other integer), and hence you cannot define an index that contains both. So either define a more specific index (not including both occurrences, but e.g. a separate index for both of them) or make them have the same or a compatible type

Regards

Harald

[Flush]

Thanks for your answer

The index definition is in the last snippet. I thought that the way for being more specific was the which tag.

Well, as we have no easy way to solve this (Too much changes in our tsd for us :D), we will use Tamino 4.2

Thanks Again.

flush

[Ulrich_Post]

Hi,

I suggest adding the following attribute to your root element:

        blockDefault="#all"

Explanation:
as Tamino 4.4 has full support for xsi:type, it has to take care that different types possibly being used/referenced via xsi:type have consistent declarations also for their respective child elements. This covers not just the logical schema but also physical properties like index definitions. With the additional attribute above usage of xsi:type is completely forbidden. I hope, that is ok for your application.
It will lead to the same behaviour as in Tamino 4.2 - unfortunately, it is not the default as of XML Schema.

Otherwise you may need to use the block=“#all” on a specific element.
Or, simply provide your complete schema with and without the intended modification and I’ll have a look.
Best regards
Uli