W3C home > Mailing lists > Public > www-ws-arch@w3.org > February 2003

RE: Business Preotocol (was: Application Protocol Definition)

From: Assaf Arkin <arkin@intalio.com>
Date: Thu, 27 Feb 2003 14:32:37 -0800
To: "bhaugen" <linkage@interaccess.com>, <www-ws-arch@w3.org>

> -----Original Message-----
> From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On
> Behalf Of bhaugen
> Sent: Thursday, February 27, 2003 2:23 PM
> To: www-ws-arch@w3.org
> Subject: RE: Business Preotocol (was: Application Protocol Definition)
> Assaf Arkin asked:
> > Would 'business protocol' be the best term to describe both 5 & 6?
> There are already a number of business protocols
> {e.g. offer-acceptance and the various auction forms }
> that could be implemented in many ways
> (e.g. RosettaNet PIP 3A4, ebXML BPSS, etc.).
> If you usurp the term "business protocol" for
> particular technical implementations, then
> what do you call the technology-independent
> business protocols that you are implementing?

Very good question.

In generic terms I could think of a protocol purely at the business level
which is very abstract. PIP 3A4 could be such a protocol, but once you
couple PIP 3A4 with RNIF you end up with a technical protocol. Same for
BPSS, it could define a very abstract protocol, but once you couple it with
a CPP/CPA it becomes a technical protocol.

Many ways to slice and dice this. We can talk about abstract business
protocols and technical service protocols. Or we can talk about a business
protocol and a SOA realization. We can call one business collaboration and
another service choreography (which is not helping much, isn't it?)

We can also talk about patterns. For example, PIP 3A4 could be considered a
pattern, and we can have a business protocol that realizes that pattern. In
realization you introduce the notion of services, but you still remain
abstract from actual transport/communication protocols which you can mix &
match (or plug-n-play as the term du jour).

Any suggestion?


Received on Thursday, 27 February 2003 17:34:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:41:04 UTC