We are doing our first steps with tamino. Based on this, the described problem may be in front of the screen.
We have to use a xsd which was designed externally. The type definitions inside the xsd are based on xs:extension, defining subclasses:
<xs:complexType name=“type.swiss”>
xs:complexContent
<xs:extension base=“type.person”>
…
The root is defined like this
<xs:element name = “reportedPerson”>
xs:complexType
xs:sequence
<xs:element name = “person” type = “type.person”></xs:element>
a) We were able to build a matching tsd from the xsd.
The tsd starts like this
<xs:schema targetNamespace = “http://www.ech.ch/2004/ech-0011”
elementFormDefault = “qualified”
xmlns = “http://www.ech.ch/2004/ech-0011”
xmlns:tsd = “http://namespaces.softwareag.com/tamino/TaminoSchemaDefinition”
xmlns:xs = “XML Schema”
xmlns:xsdconv = “http://namespaces.softwareag.com/tamino/TaminoSchemaEditor/ConverterXSDToTSD”>
b) We were able to load testdocuments into tamino, using the interactive interface.
c) When trying to display the document via X-plorer, we get a runtime error XPLXPE0058. We placed already a request on this.
d) When trying to X-Query the collection, using just “/” we are able to retrieve all documents.
e) When trying to access elements we fail, getting INOXIE8306
The loaded document looks like this:
4711
…
Behaviour is the same when xsi:schemaLocation is omitted.
Question: is it harmful for element retrieval to have xmlns, xmlns:xsi , xsi:schemaLocation in the root ?