ebMS3 Core section 6.3, presence of RefToMessageId in errors

XMLWordPrintable

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major
    • Component/s: Core Spec
    • None
    • Hide

      Rewrite to:

      An error signal message MUST have an eb:RefToMessageId in eb:MessageInfo if and only if the eb:Error(s) in a signal message all relate to a single message (i.e. the eb:RefToMessageInError is present in all eb:Error elements with the same value as the eb:RefToMessageId).

      An error signal message MUST NOT have an eb:RefToMessageId if the eb:Error(s) relate to different messages (different values for eb:RefToMessageInError) and/or to no particular message (no eb:RefToMessageInError subelement).

       

      Show
      Rewrite to: An error signal message MUST have an eb:RefToMessageId in eb:MessageInfo if and only if the eb:Error(s) in a signal message all relate to a single message (i.e. the eb:RefToMessageInError is present in all eb:Error elements with the same value as the eb:RefToMessageId). An error signal message MUST NOT have an eb:RefToMessageId if the eb:Error(s) relate to different messages (different values for eb:RefToMessageInError) and/or to no particular message (no eb:RefToMessageInError subelement).  

      Section 6.3 states:

      When reported as messages, ebMS Errors are packaged as ebMS Signal Messages. Several eb:Error elements MAY be present under eb:SignalMessage. If this is the case, and if eb:RefToMessageId is present as a child of eb:SignalMessage/eb:MessageInfo, then every eb:Error element MUST be related to the ebMS message (message-in-error) identified by eb:RefToMessageId.

      If the element eb:SignalMessage/eb:MessageInfo does not contain eb:RefToMessageId, then the eb:Error element(s) MUST NOT be related to a particular ebMS message.For an example of an ebXML Error Message, see Section 5.3.3.

      This section is hard to read (second has an implication between two negated propositions).

       

            Assignee:
            Unassigned
            Reporter:
            Pim van der Eijk (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: