Re: Marketing and publicity

[Mark Little <mcl@arjuna.com>]

> In our view the greatest aid to market acceptance of BTP would be a
> standardized Java API, which would immediately help intuitive
> understanding and remove fear of usage complexity.

And the fact that we have an adopted specification!

>
> The spec addresses the needs of implementers, and not of the user
> community, which is inevitable for an interop spec. The likely community
> of implementers is narrow, and presumably able to handle the
> "complexity".

In an email I sent as a reply to Mark Potts, and which didn't make it to the
list, I said that the specification is *not* a user manual. It should never
be aimed as such. I would not want people to learn about transactions or how
to use the OTS from the OMGs OTS specification. It's simply too much hard
work. People need to be able to differentiate between a specification and an
end-user manual.

> We view such an API as outside the scope of this OASIS BTP TC, as
> currently constituted, and not really the type of thing OASIS
> specializes in anyway, I suspect.

Agreed.

Mark.

----------------------------------------------
Dr. Mark Little
Transactions Architect, HP Arjuna Labs
Email: mark@arjuna.com | mark_little@hp.com
Phone: +44 191 2064538
Fax  : +44 191 2064203