
Hi, please, I would like to know how I can get the newest xml-cdl.xsd and component-model.xsd files? Using the ones from the last versions of the specification documents, after correcting namespaces, I get the error: "Content model violates the unique particle attribution rule" This error is thrown when the schema is ambiguous. Thanks in advance, Ayla

Hello, I've found the CVS repository under: http://sourceforge.net/cvs/?group_id=123256 but even replacing the component-model.xsd files, I continue with the same problem while using Muse:"Content model violates the unique particle attribution rule". I've got this problem before also with the xml-cdl.xsd, but replacing with the new one it did not happen. Has anyone else had the same problem? Is there a newer version of this file? Regarding ws-addressing, I've got confused, because the files point to an older version of ws-addressing, but they use a muws-1.0 version that points to the new one. In a previous mail Steve has said that you were aware of the changes in wsa. Are you planning to change the documents to the new version or it is this change that will lead to even more internal inconsistency, as said before? Best regards, Ayla Ayla Debora Dantas de Souza - Projeto Ourgrid wrote:
Hi,
please, I would like to know how I can get the newest xml-cdl.xsd and component-model.xsd files? Using the ones from the last versions of the specification documents, after correcting namespaces, I get the error:
"Content model violates the unique particle attribution rule"
This error is thrown when the schema is ambiguous.
Thanks in advance, Ayla

Ayla Debora Dantas de Souza - Projeto Ourgrid wrote:
Regarding ws-addressing, I've got confused, because the files point to an older version of ws-addressing, but they use a muws-1.0 version that points to the new one. In a previous mail Steve has said that you were aware of the changes in wsa. Are you planning to change the documents to the new version or it is this change that will lead to even more internal inconsistency, as said before?
WSDM uses two different draft versions of the specification internally; one for its addressing, one for WS-Notification. This has followon consequences for everything else. For us, it means -there is no formally standardised version to adopt -there is no one single draft version to adopt I'm not happy with it, but if you integrate with WSDM, you end up being inconsistent. This is why we have our own version of the various imported .xsd and .wsdl files, all fixed up to appear consistent, at least as far as XML spy and Ant's <schemavalidate> are concerned. If there are problems, let me know. also, give me your sourceforge login and I'll give you full access to the repository. -steve

Hi Steve, thanks a lot for making things clear. I was trying to use the xsds from Muse, which were the same pointed out by their namespaces, but now I'll try to use those from your sourceforge repository. I did not have a sourceforge login, but I could get the files as an anonymous user. Thanks again, Ayla Steve Loughran wrote:
Ayla Debora Dantas de Souza - Projeto Ourgrid wrote:
Regarding ws-addressing, I've got confused, because the files point to an older version of ws-addressing, but they use a muws-1.0 version that points to the new one. In a previous mail Steve has said that you were aware of the changes in wsa. Are you planning to change the documents to the new version or it is this change that will lead to even more internal inconsistency, as said before?
WSDM uses two different draft versions of the specification internally; one for its addressing, one for WS-Notification. This has followon consequences for everything else. For us, it means
-there is no formally standardised version to adopt -there is no one single draft version to adopt
I'm not happy with it, but if you integrate with WSDM, you end up being inconsistent. This is why we have our own version of the various imported .xsd and .wsdl files, all fixed up to appear consistent, at least as far as XML spy and Ant's <schemavalidate> are concerned. If there are problems, let me know. also, give me your sourceforge login and I'll give you full access to the repository.
-steve
participants (2)
-
Ayla Debora Dantas de Souza - Projeto Ourgrid
-
Steve Loughran