RE: Business Protocol (was: Application Protocol Definition)

Assaf Arkin wrote:
> Behind offer and accept there is a communication act and Web services
> can do that by exchanging offer and acceptance messages. Whether it's
> an offer or acceptance, legal contract or imaginary contract, depends
> on the information contained in the message.

> In my opinion you would want some framework for describing offers
> and acceptance from a contractual perspective, and a generic
> framework that could associate these business semantics with
> the specific data that is communicated, e.g. defining one as an
> ontology and the other using RDF.

Most of the above has already been done by UNCEFACT -
including the ontology, and some work on the RDF.
More than you want to know documented at
http://webster.disa.org/cefact-groups/tmg/

The UNCEFACT work attempts to be technology-neutral.
ebXML BPSS is an XML representation.
The work is closely related to RosettaNet, so you can consider
PIP 3A4 to be in the same family.
Web service implementations are in progress by several groups.
REST implementations have been discussed in the
rest-discuss yahoo group.

Received on Saturday, 1 March 2003 07:48:40 UTC