[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ebxml-dev] developing ebms, schema question.
Hi, You are likely to encounter serious interoperability problems if you radically change the schema (supposing that the infosets on the wire change significantly as well.) For the nondeterminism complaint about Acknowledgment, the least disruptive change is to remove/commentout: <any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> Just after <element ref="ds:Reference" minOccurs="0" maxOccurs="unbounded"/> If you do need an extension after the ds:Reference element, and you want a schema that will bless your infoset, then you can modify the ##other value to the specific namespace value you wish to extend into. If you add an element not in a namespace, you can modify ##other to ##local. I thought the ebMS TC was going to issue an errata about this problem, but I did not see it on the errata page. I will copy this to remind Ian to put it on the agenda eventually. Dale Moberg -----Original Message----- From: Pim van der Eijk [mailto:lists@sonnenglanz.net] Sent: Thursday, April 07, 2005 11:08 AM To: ebxml-dev@lists.ebxml.org Subject: RE: [ebxml-dev] developing ebms, schema question. Hello Bryan, A good resource for projects like this is the OASIS IIC deployment template. It specifies a standard template for describing customizations of ebMS, e.g. preferred values for Service/Action values, Party Identification schemes to be used in ebMS envelopes and many other issues that require standardization in a particular community: http://www.oasis-open.org/committees/download.php/1713/ebMS_Deployment_G uide _Template_10.doc I've found it to be quite useful in two recent ebMS projects. Pim -----Original Message----- From: Bryan Rasmussen [mailto:brs@itst.dk] Sent: 07 April 2005 14:22 To: 'ebxml-dev@lists.ebxml.org' Subject: [ebxml-dev] developing ebms, schema question. Hi It looks like we will be developing an ebms Invoicing application, the Invoicing standard used will be a variation of UBL, two questions: 1. Anyone have documentation on similar experiences, Code libraries available, whitepapers, etc. 2. Because of the nondeterministic error in the definition of Acknowledgement in ebms 2.0 message schema, we want to use our own schema for that namespace. There aren't any restrictions on doing so are there?
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]