RE: Real value (was implementing single-source) - demonstrated!

[edunn -at- transport -dot- bombardier -dot- com]

I don't see where Tim Altom showed contempt for technical writers and their
professional ability.

I think the difference in approach between the two sides of the discussion is
comparable to a carpenter working on a construction site and a carpenter making
custom furniture. Norm Abrahm (sp?) (This Old House/New Yankee Workshop) does
both and I don't think he shows contempt to those that hammer together stud
walls for a living when building an ornate piece of furniture. Nor does he show
contempt for the artisan carpenter when he builds walls for a home. Both
activities use many of the same skills but apply them in a different manner and
in different circumstances. Indeed Norm often shows how the two worlds overlap.
While building furniture he always highlights various specialised tools and jigs
that automate his work and while building homes points out where a custom or
personal touch is required.

Much the same can be said of the current discussion. I think part of the problem
is a quote used by one of the opponents of XML/SGML/Single Source: "When you
have a hammer all problems begin to look like nails." While this is true of some
XML/SGML/Single Source supporters, the same can be said of the other sides'
"creative" approach which could be summarised as: "Nails are worthless, mortise
and tennon have existed through the ages and demonstrate our greater skill. "

We found that much of our documentation was treated as a custom job each time.
But in reality it wasn't. After analysis, a large portion of our work was either
identified as common to all contracts or it could be standardised without too
much difficulty. Keep in mind that this is without looking into reuse of data
(and hence a possibly greater benefit).

"One size must fit all, because it's too costly and time consuming to adjust the
DTDs and conversion routines when a new training or documentation design is
prescribed by funding constraints or market requirements."

But is the approach of redesigning each and every time anymore efficient? Look
at the process of factory built homes. The common elements are built assembly
line fashion and only the truly custom elements require investment in planning
and on-site implementation. If you look at the docs produced by many
organisations you can see the same patterns from doc to doc/product to product.

With a standardised information input, the bid process from contract to contract
becomes easier and more accurate. The only variable is the custom work required.
The standard content has a known production time and cost. With design resources
only being expended on the custom elements, time required till shipment is also
reduced as the design cycle for the common elements is no longer in the
production cycle.

Eric L. Dunn

PS: As for Glenn Emerson's challenge:
"(Show me how you can SINGLE SOURCE a motion picture to print and I'll give you
a cigar.)"

Easy. In your source document/database you have both the motion picture and a
still picture of series of pictures. When outputting to print, the stills are
used. When outputting to multimedia the motion picture is used.
No different to how you can produce printed help with screen shots and callouts
and context-sensitive help without screen shots from the same source.



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Develop HTML-based Help with Macromedia Dreamweaver! (STC Discount.)
**NEW DATE/LOCATION!** January 16-17, 2001, New York, NY.
http://www.weisner.com/training/dreamweaver_help.htm or 800-646-9989.

Sponsored by SOLUTIONS, Conferences and Seminars for Communicators 
Publications Management Clinic, TECH*COMM 2001 Conference, and more 
http://www.SolutionsEvents.com or 800-448-4230

---
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.