Re: [ebxml-dev] gorilla hair vs. beach balls - Stefano POGLIANI - org.ebxml.lists.ebxml-dev

17 messages in org.ebxml.lists.ebxml-devRe: [ebxml-dev] gorilla hair vs. beac...

From	Sent On	Attachments
Beach, Scott	Jun 14, 2002 10:24 am
Duane Nickull	Jun 14, 2002 10:56 am
colin adam	Jun 14, 2002 12:24 pm
Rainer Volz	Jun 14, 2002 12:32 pm
Duane Nickull	Jun 14, 2002 12:56 pm
CRAWFORD, Mark	Jun 17, 2002 4:33 am
Martin W Sachs	Jun 18, 2002 4:05 pm
Matt Long	Jun 18, 2002 4:33 pm
Michael C. Rawlins	Jun 18, 2002 5:10 pm
Martin W Sachs	Jun 18, 2002 5:27 pm
bhaugen	Jun 18, 2002 5:45 pm
BELFORD Neil	Jun 18, 2002 6:08 pm
Dieter E. Jenz	Jun 19, 2002 12:59 am
Jean-Jacques Dubray	Jun 19, 2002 1:18 am
Adrian Robinson	Jun 19, 2002 1:31 am
Stefano POGLIANI	Jun 19, 2002 4:29 am
Webb, Mark	Jun 19, 2002 4:30 pm

Subject:	Re: [ebxml-dev] gorilla hair vs. beach balls
From:	Stefano POGLIANI (stef...@sun.com)
Date:	Jun 19, 2002 4:29:53 am
List:	org.ebxml.lists.ebxml-dev

Jean-Jacques,

most of the "things" that ebXML deals with are there more or less independently on the fact that Internet is used, imho. It is a matter of fact when "money" is involved in the exchanges.

One of the nice things that I like in ebXML, is its ability to deal with all the "business related aspects" in a consistent framework.

When I buy some bread from my baker, I buy according to an agreed upon sequence of (trans)actions; this sequence, together with the fact that we use some currency, that he may or may not accept a credit-card, that I cannot exit the shop without paying...or that he cannot pretend I did not give him money... are all part of an agreement which is there (even if implicit in the use). When I do business over the internet, I would do the same by means of using electronically-enforceable artifacts.

/stefano

Jean-Jacques Dubray wrote:

This should not be expressed in only in terms of benefit, but also "what do you need to carry out business transactions" over the internet. Some people may already have passed the decision point about using the internet for doing business (benefits), however there is a lot of confusion on how.

One could argue that that a good old fax machine and a state of the art OCR, which can read the XML content faxed back and forth, is far from enough. Your CPP is your fax number. All you want is there: robust security, non-repudiation, guaranteed delivery, ... why spend more?

There are several also forms of B2B, it would be good to sort benefits and requirements based on what is it you want to do. Zoe's Pizza does not have the same need as GM, though GM might buy some Pizza's from Zoë.

Thanks,

Jean-Jacques

-----Original Message----- From: bhaugen [mailto:link...@interaccess.com] Sent: Tuesday, June 18, 2002 8:46 PM To: Martin W Sachs Cc: ebtw...@lists.ebtwg.org; 'ebXML-dev List (E-mail)' Subject: Re: [ebxml-dev] gorilla hair vs. beach balls

From: Martin W Sachs

If so, those two pieces should be used to build a separate white

paper

rather than being hidden among the TC-specific information in the Requirements and Technical Architecture documents. In the process of building that white paper, it may become clear whether the content

suitable for both business people and developers or whether it is

still too

technical for business people and not technical enough for

developers.

I think we need two separate approaches: * business benefits for business people * developer benefits for developer people.

Both should be short and sweet and memorable. Written by good communicators. Spec writers don't seem to be good communicators. (Although there are exceptions.)

	Start a set with this search
	Include this search in one of my sets
	Exclude this search from one of my sets