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
Sacha:
No that is not what I said nor is it what I wrote. The messaging may
contrain certain aspects of the business process at runtime. They
should be capable of working together.
For the record, I informed members of the BPSS team 2-3 years ago
(Monica Martin and Dave Welsh) that using BSI as a term within BPSS was
probably a very bad idea that would lead to confusion.
Duane
Sacha Schlegel wrote:
>Hi Duane,
>
>Good to see you :)
>
>So you say:
>
>"Abstract = BSI"
>"Concrete = MS, CPA and BPSS"
>
>no concrete BSI? ;)
>
>So you say a MS takes care of the BPSS?
>
>Sacha
>
>Am Freitag, den 04.02.2005, 12:21 -0800 schrieb Duane Nickull:
>
>
>>Monica J. Martin wrote:
>>
>>
>>
>>>mm1: David, I would suggest we have some clear boundaries before
>>>engaging ebSOA team. Some of the discussion surrounds assumptions
>>>about the role of the MSI or BSI should be clarified by the
>>>experienced parties and experts involved from ebBP and ebMS teams (not
>>>to say there are not experts in ebSOA). Thanks.
>>>
>>>
>>Monica:
>>
>>Those groups are where a lot of FUD comes from surrounding the BSI.
>>Some people actually stated they believed the BSI was concrete and hence
>>not an abstract artifact.
>>
>>Abstract = BSI
>>Concrete = MS, CPA and BPSS
>>
>>Duane
>>
>>
>>
>
>
>
--
***********
Senior Standards Strategist - Adobe Systems, Inc. - http://www.adobe.com
Vice Chair - UN/CEFACT Bureau Plenary - http://www.unece.org/cefact/
Adobe Enterprise Developer Resources - http://www.adobe.com/enterprise/developer/main.html
***********
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]