I’m developing a Schema and I want include TaminoResponse.xsd into this new schema. However this schema is not valid
src-resolve.4.1: Error resolving component ‘error_or_warning_attributes’. It was detected that ‘error_or_warning_attributes’ has no namespace, but components with no target namespace are not referenceable from schema document
Adding the ino prefix to that attribute solves that issue but a new problem is raised after that
cos-nonambig: “http://namespaces.softwareag.com/tamino/response2”:message and “http://namespaces.softwareag.com/tamino/response2”:message (or elements from their substitution group) violate “Unique Particle Attribution”. During validation against this schema, ambiguity would be created for those two particles.
I really do not want to hack TaminoResponse Schema. My questions.
Is there some problem with that Schema or is it ok?
if there is a problem, is a new TaminoResponse Schema available?
Thanks for you help
Thanks for your answer.
I’m using Tamino 188.8.131.52. Attached you will find a zip file with:
- TaminoResponse.xsd without modifications
- The schema that i wrote to develop a Type within a WSDL
- A Snapshot with the original message.
- A Snapshot with the message after fixing the prefix issue.
This is the latest message displayed by Schema Editor.
cos-nonambig: "http://namespaces.softwareag.com/tamino/response2":message and "http://namespaces.softwareag.com/tamino/response2":message (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles. <XSCEDE0031>
TaminoResponseSchemaProblem.zip (21.5 KB)
this may be a problem in the schema editor - I failed to reproduce the problem.
I have forwarded the issue to the respected developers.
You may try to define the schemas step by step via the Tamino Interactive Interface - may be that works. If not: pls provide the error message.
the “cos-nonambig” error message is due to a schema check executed inside the schema editor.
It occurs because the references to elements declared in the imported schemas
(i.e. xql.xsd and xquery.xsd) cannot be resolved - there seems to be a bug in the schema editor.
Nevertheless, when loading the four schemas into the schema editor, you can define them in Tamino
without any problems.