RE: using 3rd-party books

[Matthew Horn <mhorn -at- macromedia -dot- com>]

[SM Rush wrote]
  >>can you reference the enclosed book in your own documentation
  >>(for example:  "to troubleshoot a socket connection, refer 
  >>to XXX for Dummies, Chapter 10")?  What would be the drawbacks to that?

No drawbacks that I can see. We currently do refer to specifications,
3rd-party books and Web sites in our docs (anyone familiar with Sun's J2EE
spec process will sympathize with us on keeping up to date). Most savvy
readers and users of our products already have these specs anyway, and
newbies probably appreciate the pointers to them.

I guess a question that comes to mind is, if we include a third-party book
that covers how to develop applications for our app server and just write
the docs specific to our product (exposing the value-adds that our server
has over others), will I be out of a job?

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

A landmark hotel, one of America's most beautiful cities, and 
three and a half days of immersion in the state of the art:
IPCC 01, Oct. 24-27 in Santa Fe.  http://ieeepcs.org/2001/

  +++  Miramo -- Database/XML publishing automation.  See us at  +++
  +++  Seybold SFO, Sept. 25-27, in the Adobe Partners Pavilion  +++
  +++ More info: http://www.axialinfo.com  http://www.miramo.com +++

---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit 
http://www.raycomm.com/techwhirl/ for more resources and info.