OASIS ebXML Messaging Services TC

 View Only

Re: PIP IDs; Qualified Invocation

  • 1.  Re: PIP IDs; Qualified Invocation

    Posted 07-19-2001 12:24
    >This whole discussion leads me to think that what is needed is a generic
    >series of tags
    >that qualify each other in an ordered sequence, a Qualified Invocation
    >Sequence, that
    >can be mapped to from whatever upper level software that the MSH needs to
    >do the
    >upcall to.
    
    +1
    
    Scott Hinkelman, Senior Software Engineer
    XML Industry Enablement
    IBM e-business Standards Strategy
    512-823-8097 (TL 793-8097) (Cell: 512-940-0519)
    srh@us.ibm.com, Fax: 512-838-1074
    
    
    Scott Hinkelman, Senior Software Engineer
    XML Industry Enablement
    IBM e-business Standards Strategy
    512-823-8097 (TL 793-8097) (Cell: 512-940-0519)
    srh@us.ibm.com, Fax: 512-838-1074
    
    
    
    Scott Hinkelman/Austin/IBM@IBMUS on 07/19/2001 09:17:18 AM
    
    To:   christopher ferris <chris.ferris@east.sun.com>
    cc:   Martin W Sachs/Watson/IBM@IBMUS, David Fischer
          <david@drummondgroup.com>, "Burdett, David"
          <david.burdett@commerceone.com>, ebXML Msg
          <ebxml-msg@lists.oasis-open.org>
    Subject:  Re: PIP IDs; Qualified Invocation
    
    
    
    This whole discussion leads me to think that what is needed is a generic
    series of tags
    that qualify each other in an ordered sequence, a Qualified Invocation
    Sequence, that
    can be mapped to from whatever upper level software that the MSH needs to
    do the
    upcall to.
    
    Scott Hinkelman, Senior Software Engineer
    XML Industry Enablement
    IBM e-business Standards Strategy
    512-823-8097 (TL 793-8097) (Cell: 512-940-0519)
    srh@us.ibm.com, Fax: 512-838-1074
    
    
    
    christopher ferris <chris.ferris@east.sun.com>@Sun.COM on 07/19/2001
    09:09:36 AM
    
    Sent by:  Chris.Ferris@Sun.COM
    
    
    To:   Martin W Sachs/Watson/IBM@IBMUS
    cc:   David Fischer <david@drummondgroup.com>, "Burdett, David"
          <david.burdett@commerceone.com>, ebXML Msg
          <ebxml-msg@lists.oasis-open.org>
    Subject:  Re: PIP IDs
    
    
    
    +1
    
    Martin W Sachs wrote:
    >
    > In my opinion it makes more sense for Service to point to the PIP ID and
    > action to point to the particular business transaction within the PIP. In
    > other words one execution of a PIP is a conversation.  I believe that
    some
    > of the PIPs include multiple business transactions.
    >
    > Regards,
    > Marty
    >
    >
    *************************************************************************************
    
    
    >
    > Martin W. Sachs
    > IBM T. J. Watson Research Center
    > P. O. B. 704
    > Yorktown Hts, NY 10598
    > 914-784-7287;  IBM tie line 863-7287
    > Notes address:  Martin W Sachs/Watson/IBM
    > Internet address:  mwsachs @ us.ibm.com
    >
    *************************************************************************************
    
    
    >
    > David Fischer <david@drummondgroup.com> on 07/19/2001 10:45:54 AM
    >
    > To:   "Burdett, David" <david.burdett@commerceone.com>
    > cc:   ebXML Msg <ebxml-msg@lists.oasis-open.org>
    > Subject:  PIP IDs
    >
    > David, in the F2F you mentioned the need for a new element to contain
    > industry specific business process identifiers such as a RosettaNet PIP
    > identifier.  Could this be done with Service/Action where the Service
    would
    > be something like RNet and the Action something like PIP3A1 (Request
    > Quote)?
    >
    > <eb:Service>urn:services:RNet</eb:Service>
    > <eb:Action>PIP3A1</eb:Action>
    >
    > Regards,
    >
    > David Fischer
    > Drummond Group.
    >
    > ------------------------------------------------------------------
    > To unsubscribe from this elist send a message with the single word
    > "unsubscribe" in the body to: ebxml-msg-request@lists.oasis-open.org
    
    ------------------------------------------------------------------
    To unsubscribe from this elist send a message with the single word
    "unsubscribe" in the body to: ebxml-msg-request@lists.oasis-open.org
    
    
    
    ------------------------------------------------------------------
    To unsubscribe from this elist send a message with the single word
    "unsubscribe" in the body to: ebxml-msg-request@lists.oasis-open.org