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>
