TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: JPL Editing Method From:Smokey Lynne L Bare <slbare -at- JUNO -dot- COM> Date:Mon, 24 Nov 1997 00:09:38 -0500
Dan Wise wrote:
"Ron Rhodes referred to the JPL Levels of Edit as a method. The Levels
of
Edit book I have is not a method, it is just a description of a heirarchy
of
levels of complexity......tool to use in defining a scope of work.....
When you establish a level of edit, you let your customer know exactly
what you will do."
*****
I agree 100% Dan. It is not a methodology. This editing scope
architecture is reminescent of the old Europen certification process in
technical and scientific writing several years ago. It affords the
potential employer the opportunity of requesting a specified level of
work which BOTH parties can understand and easily define, and most
importantly assign the same task value in the 'work for hire'
negotations.
