OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: [ebxml-dev] gorilla hair vs. beach balls


Jacques,

I think that the point is that you need different words and especially different styles of presentation to business people and to developers. Right now, all we have in the way of overall descriptions of ebXML are the Requirements document and the ebXML Architecture document. Both of those speak to members of the ebXML teams but are good neither for business people nor for developers.

Regards,
Marty

*************************************************************************************
Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287; IBM tie line 863-7287
Notes address: Martin W Sachs/Watson/IBM
Internet address: mwsachs @ us.ibm.com
*************************************************************************************
Jean-Jacques Dubray <jjd@eigner.com>




          Jean-Jacques Dubray <jjd@eigner.com>

          06/18/2002 12:21 AM



To: "'Adam Sroka'" <AdamS@rewardsplus.com>, ebtwg-bcp@lists.ebtwg.org, "'ebXML-dev List (E-mail)'" <ebxml-dev@lists.ebxml.org>
cc:
Subject: RE: [ebxml-dev] gorilla hair vs. beach balls


You must be a developer right? JMS ain’t ebXML and as you probably missed it: guaranteed message delivery at the transport level has nothing to do with guaranteed processing of your messaging by the receiving application (essential for synchronization of the business state), and “business transaction” means that we both agree that we succeeded or failed in synchronizing our state. Could you do business in an environment where someone could claim that you made this commitment while the other one refuses to accept it and no-one has any ways to prove it? Those are not big words, they are real business concepts that every business person understand on a snap. I even argue that a developer could not care less, for him/her a call is a call, it should succeed otherwise it is a bug, or maybe you try the call until it succeeds.

JJ-

-----Original Message-----
From:
Adam Sroka [mailto:AdamS@rewardsplus.com]
Sent:
Monday, June 17, 2002 3:59 PM
To:
ebXML-dev List (E-mail)
Subject:
RE: [ebxml-dev] gorilla hair vs. beach balls

I agree, pronouncing big words is a great way to get business people to agree with you - mostly because they don't know what they mean but are afraid to admit it ;-) Once you leave the room, though, they won't even bother to file it away (I believe the cliche "In one ear and out the other" is appropriate here.) In the end, whether the project goes or not will have very little to do with these words.

I tried to sell a JMS project a few months ago and was very surprised at how little weight words like "guaranteed messaging," and "transaction" carried with that audience. In the end, the solution they chose ignored these principles entirely, not because the business didn't need them, but because I did an inadequate job of selling them.

That is my experience, and, of course, yours may vary.

Regards,
Adam



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help


Powered by eList eXpress LLC