OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: [ebxml-dev] "Description" element in "Error"


I am currently setting up test cases and scenarios for the European Interoperability Pilot, therefore I am playing around with several constellations of input/output data on our ebXML connector.

While creating ebXML error message I was wondering about a parser error once the 'Error' element does contain of more than one 'Description' element and found the message msg-header-2_0.xsd defining:

	<element name="Error">
				<element ref="tns:Description" minOccurs="0"/>
				<any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

unlike the 'MessageHeader' and 'Manifest' which both define maxOccurs="unbounded".
(If you try to parse a message which contains more than one 'Description' on an error element, a validating parser will throw an error.)

Is this intention? I can see no reason why to restrict the description of an error to only one language while I am allowed to define multi-language messages for the header and the payloads.
Unfortunately the ebMS 2.0 spec does not define the min/max count of Descriptions in Errors (but it does for Manifest and MessageHeader).

Best Regards,

SEEBURGER AG, Edisonstrasse 1, D-75015 Bretten, Germany
Fon:+49(0)7252 96-1185 Fax:+49(0)7252 96-2400 <http://www.seeburger.de/>

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC