Name Change from Business Service Interface to Business Service Handler?

["Sacha Schlegel" <sschlegel@cyclonecommerce.com>]

Hi BP team
 
The ebXML Message Service Specification describes the functionality of the Message Service Handler. The abstract Message Service Interface is a way to interact with the Message Service Handler system.
 
In analogy this would need to change the name from Business Service Interface to Business Service Handler and to provide an abstract Business Service Interface to interact with the Business Service Handler?
 
I understand that the Business Service Interface was promoted as being the public interface of a party to its partners.
 
Please find attached a diagram of an ebXML deployment scenario and an ebXML collaboration system.
 
In my example the ebXML collaboration system includes a Business Service Handler and a Message Service Handler. The two handlers interact with each other through their interface (today proprietary as there is no Message Service Interface). Today's implementations might have a direct link from the Message Service Handler to the Enterprise Application Integration (EAI) side. If the ebXML business process is about to be enforced it must go through an Business Service Handler though (shown in the diagram). In this case the Business Service Handler would hold and change the state of a collaborative business process. In the diagram there is no integration of public business processes (ebXML collaborative business processes) and the internal business processes. 
 
Question: Do you think the term Business Service Interface in regards to Handler is still appropriate?
 
 
Regards
 
Sacha Schegel
 
PS: Any comments to the diagrams welcomed

organisationIT.png

ebXML-collaboration-system.png