RFB&D is looking for help.
kford at teleport.com
kford at teleport.com
Mon Jul 29 11:16:00 PDT 1996
>Return-Path: owner-guispeak at LISTSERV.NODAK.EDU
>Date: Mon, 29 Jul 1996 10:51:32 -0400
>Reply-To: mattioli at panix.com
>Sender: Access to GUI via Speech <GUISPEAK at LISTSERV.NODAK.EDU>
>From: "John R. Mattioli Jr." <mattioli at panix.com>
>Organization: Pitney Bowes, Shipping & Weighing Systems, Shelton, CT
>Subject: RFB&D is looking for help.
>To: Multiple recipients of list GUISPEAK <GUISPEAK at LISTSERV.NODAK.EDU>
> As you know, RFB&D has long had a policy regarding e-text production.
>Because of the extreme investment in time, energy and money that it takes to
>produce an e-text title, consumers have been unable to ask RFB&D to produce
>specific titles in e-text. Instead, they've been producing books which they
>believe will be important and necessary titles in e-text.
> This has resulted in a very low return on investment where RFB&D's
>e-text efforts are concerned. While RFB&D is not exactly looking to maximize
>their proffits here (they are a non-proffit and only wish to break even) it
>seems rediculous to all involved that they produce massive amounts of books
>which nobody purchases. This is the case to date. Many of their e-text books
>have sold one two or three copies. Some have sold absolutely ZERO. Clearly
>this is not in anyone's best interest.
> The VIDPI E-text committee has been asked to help and I, as chairman of
>that committee, am asking you for help.
> What is needed:
> The best way to get anything done is to make a good business case for
>it. This is as true in the e-text world as it is in any other business. Thus,
>if you've got any books you feel very strongly about, here's what you need to
>1. Write down as much information as you can about the book: title,
> author, publisher, copyright date, etc.
>2. Write down WHY this book is important: is it an industry standard
> book? Is it a book common to your work environment? Is it the kind of
> book that every software engineer (or person in another profession) has
> sitting on their shelf?
>3. What is the subject matter: in order to avoid loads of overlap, it
> would be good to know exactly what subjects we are suggesting RFB&D do.
> Remember that RFB&D resources are limited and they can't do everything
> we request. Therefore we need to prioritize and negotiate a bit.
>4. Write down alternative titles: if RFB&D found this book overly
> difficult to produce, would there be alternatives?
> If you can answer as many of these above questions as possible, you
>have a pretty good business case for why your book needs to be produced. I can
>not promise that it will get produces, but I can promise that RFB&D will hear
>the need for it.
> Please do not feel that your needs will go unheeded by RFB&D. Shortly
>after VIDPI's 1995 convention, we sent them several requests for Oracle
>documentation. Oracle is a major player in the database market and many blind
>technologists use the system. At this year's convention, George Kerscher
>informed us that RFB&D will be attempting to seek an agreement with Oracle
>Corporation similar to that which they've reached with Microsoft. Obviously,
>the details of this agreement are not yet public, nor do we know if RFB&D will
>be able to successfully negotiate such an agreement, but it is clear that they
>are trying to be responsive to our needs.
> Please respond to this plea for information as quickly and frequently
>as possible! Consider this my announcement of an open door policy regarding
>any issue for the e-text committee!
>John R. Mattioli, jr. | It doesn't matter if you go in Circles |
>E-mail: mattioli at panix.com | as long as you do it efficiently. |
More information about the Wash-at