[business-transaction] agneda request - procedures for new bindings

[Peter Furniss <peter.furniss@choreology.com>]

Bill,

Could we include an item for the ftf on the procedures (if any) for new
carrier bindings.

Some of the possibilities are:

 a) do nothing, i.e. people can create new bindings and publicize
 them however they wish

 b) have just a registration mechanism, whereby the BTP
 TC agrees to host a list of submitted bindings, but doesn't discuss, vet or
approve them at all

 c) have a heavier-weight mechanism., whereby bindings from the
 registry can be proposed for adoption as stand-alone specifications or for
incorporation into the spec.

Of course, the spec allows anyone to create and "register" a binding
(register in the sense of assigning an unambiguous  binding name, using a
URI under their own control) anyway. The question is whether the BTP TC
should do anything additional to make (some) bindings more standard.

Peter



------------------------------------------
Peter Furniss
Chief Scientist, Choreology Ltd
web: http://www.choreology.com
email:  peter.furniss@choreology.com
phone:  +44 20 7670 1679
direct: +44 20 7670 1783
mobile: +44 7951 536168
13 Austin Friars, London EC2N 2JX