[OASIS Issue Tracker] (EBXMLMSG-73) PMode[1].BusinessInfo.Service

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Pim van der Eijk created EBXMLMSG-73:
----------------------------------------

             Summary:  PMode[1].BusinessInfo.Service
                 Key: EBXMLMSG-73
                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-73
             Project: OASIS ebXML Messaging Services TC
          Issue Type: Bug
          Components: Core Spec
            Reporter: Pim van der Eijk
            Priority: Minor


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.  





--
This message was sent by Atlassian JIRA
(v6.2.2#6258)