All,

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

Hi Claudio,

1. Your fix for the “src-resolve.4.1” issue is correct - the bug will be fixed in the next update kit.

2. I failed to reproduce the error message regarding the “Unique Particle Attribution” constraint. Please provide the following information:

• which version of Tamino are you using (looks like 4.4!?)
• the schemas you are using including your importing schema
• the exact error message you obtain in the schema editor when defining
  the schema including the details - may be including a screen snapshot

Best regards
Uli

Uli,

Thanks for your answer.

I’m using Tamino 4.4.1.1. 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>

Best Regards,

Claudio
TaminoResponseSchemaProblem.zip (21.5 KB)

Hi Claudio

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.

Best regards
Uli

Hi Claudio

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.

Regards
Uli