Uploaded image for project: 'OASIS ebXML Messaging Services TC'
  1. OASIS ebXML Messaging Services TC
  2. EBXMLMSG-73

PMode[1].BusinessInfo.Service

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: New
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: Core Spec
    • Labels:
      None
    • Proposal:
      Hide

      Change to PMode.BusinessInfo.Service, to express its value is shared by all the user messages in the exchange.

      Show
      Change to PMode.BusinessInfo.Service, to express its value is shared by all the user messages in the exchange.

      Description

      Following up on discussion in the last TC call, I'm working on sample tooling to convert CPA3 to a PMode-like output format. Currently, the implementation is an XSLT stylesheet that generates text output using the dotted string notation used in the ebMS3 and AS4 specifications. I willl record any questions I run into as issues.

      Here is the first one:

      The PMode[1].BusinessInfo.Service syntax suggests that each leg in the Two Way MEP can have different values for Service. Is that really what we want? A response to a request in some service is always part of that Service.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              pvde Pim van der Eijk
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: