[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (EBXMLMSG-76) Overlap in definitions of EBMS:0003 and EBMS:0010
[ https://issues.oasis-open.org/browse/EBXMLMSG-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59458#comment-59458 ] Sander Fieten commented on EBXMLMSG-76: --------------------------------------- This issue is related to [issue #27|https://issues.oasis-open.org/browse/EBXMLMSG-27]. The resolution of this issue redefines the semantics of EBMS:0010 to _"No P-mode could be determined for the received ebMS message"_ Based on this new definition there is no overlap anymore with EBMS:0003. > Overlap in definitions of EBMS:0003 and EBMS:0010 > ------------------------------------------------- > > Key: EBXMLMSG-76 > URL: https://issues.oasis-open.org/browse/EBXMLMSG-76 > Project: OASIS ebXML Messaging Services TC > Issue Type: Improvement > Reporter: Pim van der Eijk > > Error EBMS:0010 is defined as: > "The ebMS header or another header (e.g. reliability, security) expected by the MSH is not compatible with the expected content, based on the associated P-Mode." > Error EBMS:0003 is defined as: > "Although the message document is well formed and schema valid, some element/attribute value is inconsistent either with the content of other element/attribute, or with the processing mode of the MSH, or with the normative requirements of the ebMS specification." > EBMS:0010 looks like a subcase of EBMS:0003. Should we clarify the definitions so that it becomes unambguous which one to use when? -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]