the document in question is 16 months old and forms
the basis for many implementations, products, services, and so on.
Indeed the document is 16 months old. In the intervening
16 months, there have been the basis for updates
and a very active mailing list
and a large number of issues
I think that it would be good to review how some of those
issues might affect SOAP in BEEP (e.g., issues 12, 67,
69, 95 and 105) to insure that the BEEP binding wouldn't
change depending on the resolution of those and related
issues. (I'm especially concerned about how the counterparts
of the use of HTTP 500 errors and the SOAPAction header
would map -- or not map -- to a BEEP binding.)
At the very least, you should be explicit about the
fact that SOAP is undergoing active review.