OASIS ebXML Messaging Services TC

 View Only

Re: [ebsoa] Re: [ebxml-bp] Closing the gap between MSI and BSI andmove on

  • 1.  Re: [ebsoa] Re: [ebxml-bp] Closing the gap between MSI and BSI andmove on

    Posted 02-04-2005 20:17
     MHonArc v2.5.0b2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    ebxml-msg message

    [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


    Subject: Re: [ebsoa] Re: [ebxml-bp] Closing the gap between MSI and BSI andmove on


    It is already defined in the 1.04 TA doc - the CPA is the gatekeeper.  
    It points at the BPSS instance. It constrains the parameters that make 
    up the BSI.  THe BSI is an abstract architectural concept, not a 
    concrete implement able thing.
    
    Duane
    
    David Webber (XML) wrote:
    
    >Sacha,
    >
    >I think this is also something that involves the ebSOA team - as
    >these are part of the patterns needed.
    >
    >We can certainly jointly develop this - and put initial outline work
    >in the BPSS specification - that can then be more formally
    >detailed for the ebSOA work in 2005 here.
    >
    >Thanks, DW
    >
    >----- Original Message ----- 
    >From: "Sacha Schlegel" <sschlegel@cyclonecommerce.com>
    >To: "ebXML BP" <ebxml-bp@lists.oasis-open.org>;
    ><ebxml-msg@lists.oasis-open.org>
    >Sent: Friday, February 04, 2005 9:32 AM
    >Subject: [ebxml-bp] Closing the gap between MSI and BSI and move on
    >
    >
    >Hi ebXML Message Service team
    >Hi ebXML Business Process team
    >
    >I suggest to define an interface between
    >
    >o MSI and BSI (or MSH and BSH)
    >
    >and close that gap in the ebXML spec and move on to the next step, from a
    >ebBP view point, to define an interface between
    >
    >o BSI and private business process engines (or BSH and OASIS WSBPEL for
    >example)
    >
    >Regards
    >
    >Sacha
    >
    >-----------------------------
    >
    >MSH = Message Service Handler
    >BSH = Business Service Handler
    >MSI = Message Service Interface
    >BSI = Business Service Interface
    >WSBPEL = Web Services Business Process Execution Language
    >
    >PS: BSH is to ebXML Business Process what MSH is to ebXML Message Service
    >
    >
    >
    >
    >
    >  
    >
    
    -- 
    ***********
    Senior Standards Strategist - Adobe Systems, Inc. - http://www.adobe.com
    Vice Chair - UN/CEFACT Bureau Plenary - http://www.unece.org/cefact/
    Enterprise Server Products - http://www.adobe.com/enterprise/main.html
    ***********
    
    


    [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]