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: | bhaugen (link...@interaccess.com) | |
| Date: | Jun 18, 2002 5:45:38 pm | |
| List: | org.ebxml.lists.ebxml-dev | |
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 is 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.)
-Bob Haugen
---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.ebtwg.org/ob/adm.pl>