<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Girill, T.R</title>	<link>http://tc.eserver.org/authors/Girill,_T.R</link>
	<description>A bibliography of works by Girill, T.R in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Girill, T.R</title>
		<link>http://tc.eserver.org/dir/Girill,_T.R</link>
	</image>
	<item>
		<title>Technical Writing in Science Class: The Handbook</title>
		<link>http://tc.eserver.org/35120.html</link>
		<guid>http://tc.eserver.org/35120.html</guid>
		<description>An organized kit of technical-writing exercises, guidelines, activities, and strategies refined and tested in real high-school classes, with notes and comparisons to help teachers borrow and adapt them. Also used for teacher professional development at the Edward Teller Education Center.</description>
	</item>
	<item>
		<title>School Standards That Support Technical Writing</title>
		<link>http://tc.eserver.org/35121.html</link>
		<guid>http://tc.eserver.org/35121.html</guid>
		<description>The value of learning effective nonfiction nonnarrative writing (&quot;technical writing&quot;) for middle- and high-school students has been cited repeatedly in official and unofficial academic standards starting in the early 1990s.</description>
	</item>
	<item>
		<title>How Document Design Helps English Learners Master Science</title>
		<link>http://tc.eserver.org/26855.html</link>
		<guid>http://tc.eserver.org/26855.html</guid>
		<description>Explores how basic, scaffolded technical-writing exercises can help ESL students gain cognitive maturity, practice science literacy, improve their note taking, and use text signals and science idioms more effectively.</description>
	</item>
	<item>
		<title>Confronting Illiteracy with Scientific Communication</title>
		<link>http://tc.eserver.org/19505.html</link>
		<guid>http://tc.eserver.org/19505.html</guid>
		<description>Explains how workplace principles of effective scientific communication also have an important role in literacy  outreach programs for schools.</description>
	</item>
	<item>
		<title>Example Elaboration as a Neglected Instructional Strategy</title>
		<link>http://tc.eserver.org/19506.html</link>
		<guid>http://tc.eserver.org/19506.html</guid>
		<description>Summarizes psychological research on why some people learn better from examples than others do, and applies the results to improve software documentation and literacy outreach projects. </description>
	</item>
	<item>
		<title>Description-Writing Exercises</title>
		<link>http://tc.eserver.org/14592.html</link>
		<guid>http://tc.eserver.org/14592.html</guid>
		<description>Linked to this page are 6 high-school-level exercises that teach (through worked and scaffolded examples) how to write good technical descriptions. Also included is a set of description-writing guidelines on which these exercises depend. The summary table below links to two versions of each exercise: &#xD;*	A plain version suitable for classroom use as is, and &#xD;*	An annotated version that:&#xD;*	spells out the goal of each exercise and the writing issues that it addresses, &#xD;*	compares the exercise with others in this set, &#xD;*	suggests effective, relevant teaching strategies, as well as extended activities, and &#xD;*	notes the specific 1998 California English-Language Arts content standard(s) that the exercise most strongly supports.</description>
	</item>
	<item>
		<title>The Duty of Candor in Future Software Documentation</title>
		<link>http://tc.eserver.org/14591.html</link>
		<guid>http://tc.eserver.org/14591.html</guid>
		<description>The STC Code for Communicators requires us &apos;to communicate technical information truthfully...&apos;. Such truthfulness has two related but distinct aspects, honesty and candor. I have never been asked to falsify technical claims in documentation (honesty), but I have occasionally been asked to withhold true claims about software that, if known to users, would surely affect how they interpret or apply that software (candor). The century ahead will increasingly demand user documentation that is candid as well as honest. </description>
	</item>
	<item>
		<title>Fuzzy Matching as a Retrieval-Enabling Technique for Digital Libraries</title>
		<link>http://tc.eserver.org/14593.html</link>
		<guid>http://tc.eserver.org/14593.html</guid>
		<description>This paper advocates an often-neglected search-support technique, approximate or &apos;fuzzy&apos; matching of user search terms. When properly deployed, fuzzy matching can significantly enhance the benefits of other, more common approaches to end-user answer retrieval from online reference collections. We compare crude with more sophisticated approximation techniques to explain how astute fuzzy-match software can convert many different near-miss situations (such as those involving faulty prefixes or suffixes, character misplacement, nonstandard word stems, or unanticipated redescription of concepts) into more adequate results. We also suggest practical ways to overcome fuzzy matching&apos;s own major drawbacks (namely, problems with search speed, search imprecision, and misinterpretation of search results). The resulting analysis clarifies how to deploy fuzzy matching for maximum effectiveness. We conclude that appropriate fuzzy matching enables more frequent, more flexible search success than do ordinary retrieval-improvement techniques used without it.</description>
	</item>
	<item>
		<title>Integrating Local and CRI Online Documentation Using SGML and DynaWeb</title>
		<link>http://tc.eserver.org/14594.html</link>
		<guid>http://tc.eserver.org/14594.html</guid>
		<description>This paper tells how Lawrence Livermore National Laboratory enriched CRI&apos;s online documentation set by&#xD;publishing local manuals using the same SGML DTD used by CRI and delivered using (a more sophisticated&#xD;version of) the same World Wide Web server (DynaWeb 3.0). This approach supports flexible local content&#xD;and styles, yet integrates local and CRI manuals through one access mechanism and user interface. We&#xD;explain the basic strategy involved, compare the benefits of this approach with three alternatives, and&#xD;discuss the problems to which it gives rise. </description>
	</item>
	<item>
		<title>Background on SGML</title>
		<link>http://tc.eserver.org/14585.html</link>
		<guid>http://tc.eserver.org/14585.html</guid>
		<description>Educational materials on SGML fall into three broad categories. An evaluative abstract is available for each item on the chart.</description>
	</item>
	<item>
		<title>Instruction-Writing Exercises (for High School)</title>
		<link>http://tc.eserver.org/13311.html</link>
		<guid>http://tc.eserver.org/13311.html</guid>
		<description>These guidelines and 14 scaffolded exercises respond to the&#xD;unmet need for a psychologically solid, work-relevant way to&#xD;learn technical writing by students who are NOT facile writers already.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Girill,_T.R.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>