<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-6321008</id><updated>2011-07-14T00:09:59.246-05:00</updated><title type='text'>Techdocspoliciesprocedures</title><subtitle type='html'>Welcome to a web log for students and professionals who study/write technical documents, policies, and procedures. Join in the discussion.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><link rel='next' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default?start-index=101&amp;max-results=100'/><author><name>Lee S. Tesdell</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>148</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-6321008.post-116240797191478074</id><published>2006-11-01T13:05:00.000-06:00</published><updated>2006-11-01T13:06:11.933-06:00</updated><title type='text'>The Report for Decision Making</title><summary type='text'>I found it quite interesting that Rude basis her argument, at least partially, on the idea that genre should be defined through context rather than form. She describes the differences in terminology and procedure used by textbooks for writing repots which deal with decision making. Some of the various names, given by the textbooks, for these reports include feasibility reports, problem solving </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/116240797191478074/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=116240797191478074' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/116240797191478074'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/116240797191478074'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/11/report-for-decision-making.html' title='The Report for Decision Making'/><author><name>Matthew Bichler</name><uri>http://www.blogger.com/profile/17089995350576148497</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-116167035530057025</id><published>2006-10-24T00:42:00.000-05:00</published><updated>2006-10-25T00:47:00.313-05:00</updated><title type='text'>Engineering writing engineering</title><summary type='text'>Winsor begins by commenting that she would never do a so-called study like this now. The article is outdated for several reasons, mostly problems with construction like explanation of her subject choice or analytical triangulation. Regardless, its value is in its interdisciplinary perspective.  The basic premise here is this: Observations of the external world is transformed into "knowledge" </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/116167035530057025/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=116167035530057025' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/116167035530057025'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/116167035530057025'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/10/engineering-writing-engineering.html' title='Engineering writing engineering'/><author><name>Thia</name><uri>http://www.blogger.com/profile/04487577511729091790</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-116128514810264866</id><published>2006-10-19T14:11:00.000-05:00</published><updated>2006-10-19T14:12:28.116-05:00</updated><title type='text'>Beyond Skill Building: Challenges Facing Technical Communication Teachers in the Computer Age</title><summary type='text'>The questions and issues raised in Selber’s article published in 1993 still reverberate with the use of technology in and for education in general and in tech comm., in particular. The author begins by surveying the courses that involved the use of technology in technical communication programs in the US and categorizing them. Three main categories of approaches to the design of computer related </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/116128514810264866/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=116128514810264866' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/116128514810264866'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/116128514810264866'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/10/beyond-skill-building-challenges.html' title='Beyond Skill Building: Challenges Facing Technical Communication Teachers in the Computer Age'/><author><name>Sasha Komarenko</name><uri>http://www.blogger.com/profile/17278685201404548658</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-116042124827510078</id><published>2006-10-09T14:11:00.000-05:00</published><updated>2006-10-09T16:47:26.540-05:00</updated><title type='text'>The Social Perspective and Professional Communication</title><summary type='text'>        In this article, “The social perspective and professional communication”, Charlotte Thralls and Nancy Roundy Blyler talks about three different social perspectives in professional and academic communication. They are: the social constructionist approach, the ideologic approach, and the paralogic hermeneutic approach. They further breaks these categories down to abstract some similarities </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/116042124827510078/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=116042124827510078' title='7 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/116042124827510078'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/116042124827510078'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/10/social-perspective-and-professional.html' title='The Social Perspective and Professional Communication'/><author><name>Deeba</name><uri>http://www.blogger.com/profile/15124149752124697779</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>7</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-115980862262825427</id><published>2006-10-02T11:58:00.000-05:00</published><updated>2006-10-02T13:59:01.353-05:00</updated><title type='text'>The Composing Process of an Engineer</title><summary type='text'>Jack Selzer's article "The Composing Process of an Engineer" details the approach to writing taken by Kenneth E. Nelson, an engineer at Henningson, Durham, and Richardson (HDR). Selzer examined Nelson's documents and notes, interviewed Nelson, and listened to responses to questions recorded by Nelson before and after he created documents. This in-depth examination of Nelson's writing process </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/115980862262825427/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=115980862262825427' title='6 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115980862262825427'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115980862262825427'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/10/composing-process-of-engineer.html' title='The Composing Process of an Engineer'/><author><name>Hoops</name><uri>http://www.blogger.com/profile/17140691594267646858</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>6</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-115954416303209615</id><published>2006-09-29T10:35:00.000-05:00</published><updated>2006-09-29T10:36:03.036-05:00</updated><title type='text'>Writing in an Emerging Organization</title><summary type='text'>“The research results that form this model describe and explain the rhetorical and organizational activities of a particular case, and as such can be generalized only very tentatively.”This line from very near the end of the article summed up the skepticism I felt throughout the article. The results seem rather obvious: a business plan, written by the five individuals who control the entire </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/115954416303209615/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=115954416303209615' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115954416303209615'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115954416303209615'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/09/writing-in-emerging-organization_29.html' title='Writing in an Emerging Organization'/><author><name>Matthew Bichler</name><uri>http://www.blogger.com/profile/17089995350576148497</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-115863015325086768</id><published>2006-09-18T19:41:00.000-05:00</published><updated>2006-09-18T20:42:37.716-05:00</updated><title type='text'>Writing and Database Technology</title><summary type='text'>The author begins by noting when the original article was written.   Today, she comments,  technology has advanced so far and so ubiquitously that the content is more common sense.  However, despite the fact that the focus should be less on the data, the fundamental necessity for rhetorical understanding of data presentation (reports) remains the same (382).  Mirel tackles the importance and </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/115863015325086768/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=115863015325086768' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115863015325086768'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115863015325086768'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/09/writing-and-database-technology.html' title='Writing and Database Technology'/><author><name>Thia</name><uri>http://www.blogger.com/profile/04487577511729091790</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-115800584263211446</id><published>2006-09-11T15:15:00.000-05:00</published><updated>2006-09-11T15:17:22.670-05:00</updated><title type='text'>Teaching Discourse And Reproducing Culture</title><summary type='text'>Herndl argues that current state of research and pedagogy in the field of technical communication (and, likely, composition in general) fails to critically examine, and thus, possibly, reinforces the hegemony of the prevalent power/political structures. Research, the author argues, has failed to examine the conditions and relationships between the established power structures and the people who </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/115800584263211446/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=115800584263211446' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115800584263211446'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115800584263211446'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/09/teaching-discourse-and-reproducing.html' title='Teaching Discourse And Reproducing Culture'/><author><name>Sasha Komarenko</name><uri>http://www.blogger.com/profile/17278685201404548658</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-115759279404541658</id><published>2006-09-06T20:22:00.000-05:00</published><updated>2006-09-06T20:33:14.080-05:00</updated><title type='text'>History, Rhetoric, and Humanism</title><summary type='text'>In this article, “History, Rhetoric, and Humanism”, Russell Rutter portrayed how technical communication is linked with rhetoric and oratorical ideologies. He showed us how thoughts and ideas about technical communication have changed with time. Technical communication is not about making technology the center point. It is to create a way for people to understand the usage of technology. As David</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/115759279404541658/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=115759279404541658' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115759279404541658'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115759279404541658'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/09/history-rhetoric-and-humanism.html' title='History, Rhetoric, and Humanism'/><author><name>Deeba</name><uri>http://www.blogger.com/profile/15124149752124697779</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-115755873632709429</id><published>2006-09-06T10:57:00.000-05:00</published><updated>2006-09-06T11:06:21.250-05:00</updated><title type='text'>Here at last. Here at last. Here AND last.</title><summary type='text'>Sorry this is so late. I just finished moving to Champlin and did not have internet access until now.As far as my interest in Technical Writing, I would love to edit in a big publishing company on the coast. In reality, I see myself working for a company like Medtronic or Boston Scientific.Matthew Bichler</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/115755873632709429/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=115755873632709429' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115755873632709429'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115755873632709429'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/09/here-at-last-here-at-last-here-and.html' title='Here at last. Here at last. Here AND last.'/><author><name>Matthew Bichler</name><uri>http://www.blogger.com/profile/17089995350576148497</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-115716220687786654</id><published>2006-09-01T20:54:00.000-05:00</published><updated>2006-09-01T20:56:46.900-05:00</updated><title type='text'>Teaching Technical Writing--How Did We Get Here From There?</title><summary type='text'>In his article, “The Rise of Technical Writing Instruction in America,” Robert J. Connors describes in detail the progression of technical writing instruction since the middle of the nineteenth century. Connors begins his essay by stating that technical writing, in one form or another, has existed since ancient times; however, he states that the attempt to actually create an instructional </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/115716220687786654/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=115716220687786654' title='6 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115716220687786654'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115716220687786654'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/09/teaching-technical-writing-how-did-we.html' title='Teaching Technical Writing--How Did We Get Here From There?'/><author><name>Hoops</name><uri>http://www.blogger.com/profile/17140691594267646858</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>6</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-115696027229229963</id><published>2006-08-30T12:37:00.000-05:00</published><updated>2006-08-30T12:51:12.306-05:00</updated><title type='text'>Hello...</title><summary type='text'>My name is Deeba Rahman. I graduated from St Cloud State University with major in Business Computer Information Systems and a minor in Graphic Design. This is my first semester in MSU. I am pursuing MA in Technical Writing while working full-time at James Tower as a Technical Support Specialist.I am originally from Bangladesh was born in Dubai, finished my high school in England and finally moved</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/115696027229229963/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=115696027229229963' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115696027229229963'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115696027229229963'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/08/hello.html' title='Hello...'/><author><name>Deeba</name><uri>http://www.blogger.com/profile/15124149752124697779</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-115695698122037090</id><published>2006-08-30T11:43:00.000-05:00</published><updated>2006-08-30T11:56:21.240-05:00</updated><title type='text'>Howdy...</title><summary type='text'>My name is Catherine and I am a second year grad student. I am pursuing both the MA in t.com and the MFA in creative writing (fiction), so, as I mentioned the other day, I feel kind of schitzophrenic most of the time. In one program, sentence fragments and intentional comma splices are the way to go. In the other, we write by the book. Plus, while I'm a pretty quick learner, I don't know any HTML</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/115695698122037090/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=115695698122037090' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115695698122037090'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115695698122037090'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/08/howdy.html' title='Howdy...'/><author><name>Hoops</name><uri>http://www.blogger.com/profile/17140691594267646858</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-115690931622109780</id><published>2006-08-29T22:41:00.000-05:00</published><updated>2006-08-29T22:45:17.283-05:00</updated><title type='text'>Hi All,</title><summary type='text'>I’m a grad student. Sad to say this is my 3rd grad program. I have a Speech Comm. MA and hope finish my TESOL MA this semester. I’m just starting the Tech Comm. Certificate program at MSU and hoping to finish it in a year. I’m really excited about this program because all of my academic and professional experiences have involved technical communication in one way or another. Since I’m an </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/115690931622109780/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=115690931622109780' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115690931622109780'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115690931622109780'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/08/hi-all.html' title='Hi All,'/><author><name>Sasha Komarenko</name><uri>http://www.blogger.com/profile/17278685201404548658</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-115689823693773547</id><published>2006-08-29T19:23:00.000-05:00</published><updated>2006-08-29T19:50:35.593-05:00</updated><title type='text'>Umm. Hi?</title><summary type='text'>(Looks like I'm the first one, so I hope I'm doing this right. :P)My name's Thia, and I took the red pill.   TechComm grad student.I'm a software, internet, and computer junkie, spending far too much time in front of my laptop than is healthy.  (I'm typing this via the latest version of K-meleon, but I much prefer Opera.) That said, I hope to get into technical writing for hardware or software or</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/115689823693773547/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=115689823693773547' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115689823693773547'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115689823693773547'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/08/umm-hi.html' title='Umm. Hi?'/><author><name>Thia</name><uri>http://www.blogger.com/profile/04487577511729091790</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-115681688284331403</id><published>2006-08-28T20:55:00.000-05:00</published><updated>2006-08-28T21:17:48.703-05:00</updated><title type='text'>Welcome to F2006 Central Works blog</title><summary type='text'>Welcome to the Fall 2006 edition of the Central Works blog; it is our intention to continue the discussion of the readings here. In your first blog entry, please introduce yourselves though there is no need to divulge a lot of personal information.Throughout the semester you will be responsible for your own entry but also for a response to everyone else's blog entry.</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/115681688284331403/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=115681688284331403' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115681688284331403'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/115681688284331403'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/08/welcome-to-f2006-central-works-blog.html' title='Welcome to F2006 Central Works blog'/><author><name>Lee S. Tesdell</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114772491537979574</id><published>2006-05-15T15:12:00.000-05:00</published><updated>2006-05-15T15:28:35.393-05:00</updated><title type='text'>Semester wrap-up</title><summary type='text'>Thanks to everyone who kept our Central Works blog alive during the spring semester. I thought that Wes, Anna, and Nisha all did a nice job of  summarizing and critiquing Central Works articles. Thanks also to Stuart Selber of Penn State (and one of the editors of Central Works), for blogging with us.While the media and the public seem to notice only the political blogosphere, we used our </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114772491537979574/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114772491537979574' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114772491537979574'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114772491537979574'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/05/semester-wrap-up.html' title='Semester wrap-up'/><author><name>Lee S. Tesdell</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114709799356394323</id><published>2006-05-08T09:15:00.000-05:00</published><updated>2006-05-08T09:19:53.576-05:00</updated><title type='text'>Political-Ethical Implications of Defining Technical Communication as a Practice</title><summary type='text'>While developing a PHD program at Michigan Technological University, the author, Dale L. Sullivan, wrote this article that voices some concerns that the author dealt with during that period. The author has a reactionary stand towards the technological society but she accepts the fact that this wouldn’t help a person who has to make a living in a technological world created by our revolving </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114709799356394323/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114709799356394323' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114709799356394323'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114709799356394323'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/05/political-ethical-implications-of.html' title='Political-Ethical Implications of Defining Technical Communication as a Practice'/><author><name>Nisha</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114705902471190077</id><published>2006-05-07T22:29:00.000-05:00</published><updated>2006-05-07T22:30:24.726-05:00</updated><title type='text'>Text and Action</title><summary type='text'>James Paradis wrote this article following his experiences as an expert witness in a liability suit involving the studgun. The lawsuit arose questions regarding the role manuals play in the user’s mental construction of the tool and how effectively the operator’s manuals elaborated the procedurally sensitive process of safely applying the studgun to various tasks. According to Paradis, a operator</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114705902471190077/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114705902471190077' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114705902471190077'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114705902471190077'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/05/text-and-action.html' title='Text and Action'/><author><name>Nisha</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114696023093244759</id><published>2006-05-06T19:03:00.000-05:00</published><updated>2006-05-06T19:03:50.933-05:00</updated><title type='text'>Relocating the Value of Work - Johndan Johnson-Eilola, Johndan</title><summary type='text'>In this article, the author talks about the misplacement of technical writing in today's information age. According to the author, technical communicators are situated as experts in the final stage to create association among various bits of information. While technical communicators should have had a central role in this new information age economy, the field was frequently cast in a supporting </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114696023093244759/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114696023093244759' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114696023093244759'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114696023093244759'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/05/relocating-value-of-work-johndan_06.html' title='Relocating the Value of Work - Johndan Johnson-Eilola, Johndan'/><author><name>Nisha</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114696013163602112</id><published>2006-05-06T18:59:00.000-05:00</published><updated>2006-05-06T19:05:46.730-05:00</updated><title type='text'>The Politics of the Interface - Cynthia L. Selfe &amp; Richard J. Selfe, Jr.</title><summary type='text'>In this article, the authors suggest that it is important to help teachers identify the effects of domination and colonialism associated with computer use so that they can establish a new territory to understand the relationships between technology and education. They claim that, the teachers of English, though unknowingly, teach students inequity even as they strive to erase such lessons from </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114696013163602112/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114696013163602112' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114696013163602112'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114696013163602112'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/05/politics-of-interface-cynthia-l-selfe.html' title='The Politics of the Interface - Cynthia L. Selfe &amp; Richard J. Selfe, Jr.'/><author><name>Nisha</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114692750589464623</id><published>2006-05-06T09:51:00.000-05:00</published><updated>2006-05-06T09:58:25.913-05:00</updated><title type='text'>Empiricism is Not a Four-Letter Word</title><summary type='text'>Charney, through this article, responds to other theorists who misunderstood, and therefore avoided, a straightforward empirical approach towards writing. Craney suggests that the writer’s ability to improve their work may be impaired by them advocating to subjective methods as opposed to objective methods. Charney doesn’t hold back when she argues against the mischaracterizations of science, for</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114692750589464623/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114692750589464623' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114692750589464623'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114692750589464623'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/05/empiricism-is-not-four-letter-word.html' title='Empiricism is Not a Four-Letter Word'/><author><name>Nisha</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114670808311681937</id><published>2006-05-03T20:59:00.000-05:00</published><updated>2006-05-03T21:01:23.133-05:00</updated><title type='text'>Technical Communication Courses - Beyond Skill Building</title><summary type='text'>Technology is changing everyday. It has imbued not just the workplace but also the classrooms. Staurt A. Selber, through his article, looks into the challenges that technical communication teachers face in today’s computer age. This article reports results from a survey of US technical and professional communication undergraduate programs concerning core concepts emphasized and most commonly </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114670808311681937/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114670808311681937' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114670808311681937'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114670808311681937'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/05/technical-communication-courses-beyond.html' title='Technical Communication Courses - Beyond Skill Building'/><author><name>Nisha</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114485986788483945</id><published>2006-04-12T11:36:00.000-05:00</published><updated>2006-04-12T11:37:47.896-05:00</updated><title type='text'>Cultrual differences in Tech Comm</title><summary type='text'>It’s no secret that globalization is growing. As companies expand into many countries, there is a growing diversity among the people who work for these companies. With this diversity comes the inevitability of cultural clash. Cultures can differ on how they conduct collaboration projects, what values are held, and how communication is conducted. Deborah Bosley knows this and addresses how these </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114485986788483945/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114485986788483945' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114485986788483945'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114485986788483945'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/04/cultrual-differences-in-tech-comm.html' title='Cultrual differences in Tech Comm'/><author><name>Wes Ahles</name><uri>http://www.blogger.com/profile/17729944904258226209</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114480937479636877</id><published>2006-04-11T21:35:00.000-05:00</published><updated>2006-04-11T21:36:14.813-05:00</updated><title type='text'>Brasseur's course on gender issues in tech comm</title><summary type='text'>In “Contesting the Objectivist Paradigm: Gender Issues in the Technical and Professional Communication Curriculum,” Lee Brasseur describes her first semester of teaching a master’s level seminar class titled “Gender Issues in Technical and Professional Writing and Communication.”  She argues that “the discourse of technical communication has traditionally rested on a foundation of scientific </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114480937479636877/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114480937479636877' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114480937479636877'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114480937479636877'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/04/brasseurs-course-on-gender-issues-in.html' title='Brasseur&apos;s course on gender issues in tech comm'/><author><name>Anna</name><uri>http://www.blogger.com/profile/13614810967604329092</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114459913817257385</id><published>2006-04-09T11:11:00.000-05:00</published><updated>2006-04-09T11:14:14.280-05:00</updated><title type='text'>Stuart's comments</title><summary type='text'>Like Lee, I would like to thank Stuart for taking the time to contribute to our blog, and for producing Central Works.  I was also intrigued by Stuart’s comments on editing the book.  I appreciate that he acknowledges that even though the editors attempted to keep politics out of their decisions on what essays to include in the collection, the fact that the collection reflects their values to a </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114459913817257385/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114459913817257385' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114459913817257385'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114459913817257385'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/04/stuarts-comments.html' title='Stuart&apos;s comments'/><author><name>Anna</name><uri>http://www.blogger.com/profile/13614810967604329092</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114459824533458885</id><published>2006-04-09T10:56:00.000-05:00</published><updated>2006-04-09T10:57:25.366-05:00</updated><title type='text'>copyright in the electronic age</title><summary type='text'>In “Who ‘Owns’ Electronic Texts,” Tharon W. Howard discusses the historical background of U.S. copyright law.  Contrary to the romantic notions that some of us have today, copyright was not originally established to protect the rights of authors.  Rather, it originated with a royal charter issued to the Stationers’ Company (representatives of the publishing industry) by Mary Tudor and Philip of </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114459824533458885/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114459824533458885' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114459824533458885'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114459824533458885'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/04/copyright-in-electronic-age.html' title='copyright in the electronic age'/><author><name>Anna</name><uri>http://www.blogger.com/profile/13614810967604329092</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114427180765634953</id><published>2006-04-05T16:13:00.000-05:00</published><updated>2006-04-05T16:16:47.670-05:00</updated><title type='text'>Our Present Shaping our Future</title><summary type='text'>There comes a time when we must consider what the future will bring. We must look at where we currently are, what has led us to this point, and what it will eventually lead to. If his article “The Shape of Text to Come: The Texture of Print on Screens” is any indication, Stephen Bernhardt knows this concept very well. The very first sentence in Berhardt’s article states that “changes in the </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114427180765634953/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114427180765634953' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114427180765634953'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114427180765634953'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/04/our-present-shaping-our-future.html' title='Our Present Shaping our Future'/><author><name>Wes Ahles</name><uri>http://www.blogger.com/profile/17729944904258226209</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114417593545338819</id><published>2006-04-04T13:28:00.000-05:00</published><updated>2006-04-04T13:38:55.493-05:00</updated><title type='text'>Thanks Stuart</title><summary type='text'>Thanks Stuart, for taking time out of your busy schedule to blog with us. I was particularly interested in your second point about putting together Central Works with Johndan Johnson-Eilola. I sometimes think that the intellectual journey we students take from high school, through undergraduates studies, and on to graduate programs is partly a process of deciding what the relationship should be, </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114417593545338819/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114417593545338819' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114417593545338819'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114417593545338819'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/04/thanks-stuart.html' title='Thanks Stuart'/><author><name>Lee S. Tesdell</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114408402010879657</id><published>2006-04-03T11:50:00.000-05:00</published><updated>2006-04-03T12:07:00.180-05:00</updated><title type='text'>Hi/A Few Comments</title><summary type='text'>Lee asked me to check in on your blogging of Central Works. I was hoping to do this last week, but time got away from me. But I really enjoyed reading your posts thus far on Central Works. I'll make two brief comments: one on my own essay, the other on the task of editing the book. I don't know if you'll be getting to my essay or not, the one called "Beyond Skill Building," but here is some </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114408402010879657/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114408402010879657' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114408402010879657'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114408402010879657'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/04/hia-few-comments.html' title='Hi/A Few Comments'/><author><name>Stuart Selber</name><uri>http://www.blogger.com/profile/17220671014120183379</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114366408379444072</id><published>2006-03-29T14:25:00.000-06:00</published><updated>2006-03-29T14:28:03.806-06:00</updated><title type='text'>Collaboration: The Strength of Many</title><summary type='text'>The article “What Experienced Collaborators Say About Collaborative Writing” is, oddly enough, a sizeable collaboration between Nancy Allen, Diane Atkinson, Meg Morgan, Teresa Moore, and Craig Snow. To save time and monotony, I will merely call this eclectic group “the writers” from here on out. The writers start out by making a distinction between collaborative writing and group work. Going with</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114366408379444072/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114366408379444072' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114366408379444072'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114366408379444072'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/03/collaboration-strength-of-many.html' title='Collaboration: The Strength of Many'/><author><name>Wes Ahles</name><uri>http://www.blogger.com/profile/17729944904258226209</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114348679482731245</id><published>2006-03-27T13:12:00.000-06:00</published><updated>2006-03-27T13:13:14.843-06:00</updated><title type='text'>engineers and the textual construction of knowledge</title><summary type='text'>In “Engineering Writing/Writing Engineering,” Dorothy A. Winsor seeks to fill a gap in the research by applying contemporary views of the “textual construction of knowledge” (342) to an examination of engineers’ writing, which is traditionally seen as being closely tied to physical reality, with little mediation or interpretation.  In this sense, Winsor’s approach has much in common with other </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114348679482731245/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114348679482731245' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114348679482731245'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114348679482731245'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/03/engineers-and-textual-construction-of.html' title='engineers and the textual construction of knowledge'/><author><name>Anna</name><uri>http://www.blogger.com/profile/13614810967604329092</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114192542651803963</id><published>2006-03-09T11:28:00.000-06:00</published><updated>2006-03-09T11:30:26.536-06:00</updated><title type='text'>The critical perspective and its application to technical communication</title><summary type='text'>The goal that Nancy Blyler seems to strive for in her article “Taking a Political Turn: The Critical Perspective and Research in Professional Communication” seems to be nothing less than change how we as technical communicators conduct our research and writing standards. Upon reviewing the established method of communication, Blyler notes how it has been skills-oriented, how it “ignores the </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114192542651803963/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114192542651803963' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114192542651803963'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114192542651803963'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/03/critical-perspective-and-its.html' title='The critical perspective and its application to technical communication'/><author><name>Wes Ahles</name><uri>http://www.blogger.com/profile/17729944904258226209</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114174670852078418</id><published>2006-03-07T09:51:00.000-06:00</published><updated>2006-03-07T09:51:48.556-06:00</updated><title type='text'>writing in organizational contexts</title><summary type='text'>In “Frameworks for the Study of Writing in Organizational Contexts,” Teresa M. Harrison explores approaches to rhetorical and organizational theory can be applied to writing in organizations.  She begins with a discussion of the New Rhetoric, a variety of approaches to rhetorical theory that differ from classical rhetoric in their emphasis on the social communities that frame the contexts for </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114174670852078418/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114174670852078418' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114174670852078418'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114174670852078418'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/03/writing-in-organizational-contexts.html' title='writing in organizational contexts'/><author><name>Anna</name><uri>http://www.blogger.com/profile/13614810967604329092</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114098913510338241</id><published>2006-02-26T15:25:00.000-06:00</published><updated>2006-02-26T15:25:35.113-06:00</updated><title type='text'>Staying relevant in the information economy</title><summary type='text'>As I read Johndan Johnson-Eilola’s “Relocating the Value of Work: Technical Communication in a Post-Industrial Age,” I was struck by some of the similarities between how technical communicators and professionals in other fields in which I’ve worked (specifically development research and librarianship) have had to redefine themselves in the information age.  Johnson-Eilola argues that technical </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114098913510338241/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114098913510338241' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114098913510338241'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114098913510338241'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/02/staying-relevant-in-information.html' title='Staying relevant in the information economy'/><author><name>Anna</name><uri>http://www.blogger.com/profile/13614810967604329092</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114098638157134853</id><published>2006-02-26T14:39:00.000-06:00</published><updated>2006-02-26T14:39:41.580-06:00</updated><title type='text'>What's in a name?</title><summary type='text'>Wes raises an interesting question in response to Johnson-Eilola’s article—should we still call ourselves “technical” communicators?  I think so, because the technical nature of our communication is what distinguishes us from other professions that also trade in communication.  With the shift from an industrial to an information economy, many professions are focusing on information and </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114098638157134853/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114098638157134853' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114098638157134853'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114098638157134853'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/02/whats-in-name.html' title='What&apos;s in a name?'/><author><name>Anna</name><uri>http://www.blogger.com/profile/13614810967604329092</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114074817157347807</id><published>2006-02-23T20:28:00.000-06:00</published><updated>2006-02-23T20:29:31.586-06:00</updated><title type='text'>Theory and Practice</title><summary type='text'>I agree with Wes that practitioners of technical communication should be concerned with theoretical discussions of topics such as ethics, humanism, and feminism precisely because of our role as communicators.  For instance, a technical writer using Campbell’s book as a practical guide to writing policies and procedures might consider Campbell’s recommendation to use gender-neutral language as </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114074817157347807/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114074817157347807' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114074817157347807'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114074817157347807'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/02/theory-and-practice.html' title='Theory and Practice'/><author><name>Anna</name><uri>http://www.blogger.com/profile/13614810967604329092</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114065852215642436</id><published>2006-02-22T19:32:00.000-06:00</published><updated>2006-02-22T19:50:52.743-06:00</updated><title type='text'>Can Theory Be Put into Practice?</title><summary type='text'>Academics mostly work with idealistic models. That is, they try to incorporate the maximum number of best practices. The whole point of ethics in writing is to encourage sticking to the facts. The starker the facts in your information, the closer it is to reality. The closer it is to reality, the more useful is the information.Every technical communicator worth their salt must be a good technical</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114065852215642436/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114065852215642436' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114065852215642436'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114065852215642436'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/02/can-theory-be-put-into-practice.html' title='Can Theory Be Put into Practice?'/><author><name>Nisha</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114064504393303245</id><published>2006-02-22T15:43:00.000-06:00</published><updated>2006-02-22T15:50:43.950-06:00</updated><title type='text'>Defing technical communication</title><summary type='text'>After reading "Relocating the Value of Work", I have a few comments and a question for Johndan. First, it's always refreshing to hear how technical communicators are trying to redefine what we do. All too often we--or at least I do--have to fall back on the technical part of what we do, making documents and procedures for implementation. The four areas that you describe focus more on the </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114064504393303245/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114064504393303245' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114064504393303245'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114064504393303245'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/02/defing-technical-communication.html' title='Defing technical communication'/><author><name>Wes Ahles</name><uri>http://www.blogger.com/profile/17729944904258226209</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114064274491405532</id><published>2006-02-22T15:00:00.000-06:00</published><updated>2006-02-22T15:12:24.926-06:00</updated><title type='text'>What does academia have to do with tech comm anyway?</title><summary type='text'>I've been thinking about your post from last week, Lee.  How can theoretical pieces have any effect on the technical writer in the workplace? After some thought I came up with the conclusion: what DOESN'T it have to do with technical writing? It may sounds like I'm beating a dead horse here, but we as technical writers have to take almost everything into consideration.  Our practice can have a </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114064274491405532/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114064274491405532' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114064274491405532'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114064274491405532'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/02/what-does-academia-have-to-do-with.html' title='What does academia have to do with tech comm anyway?'/><author><name>Wes Ahles</name><uri>http://www.blogger.com/profile/17729944904258226209</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114047449459305696</id><published>2006-02-20T16:24:00.000-06:00</published><updated>2006-02-20T16:28:14.603-06:00</updated><title type='text'>Welcome Johndan</title><summary type='text'>Johndan Johnson-Eilola may have time to join us this week in our blog. I would suggest that you read his article in Central Works so that you know where he is coming from. Please try to engage him in conversation this week.</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114047449459305696/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114047449459305696' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114047449459305696'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114047449459305696'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/02/welcome-johndan.html' title='Welcome Johndan'/><author><name>Lee S. Tesdell</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114005686708721054</id><published>2006-02-15T20:03:00.000-06:00</published><updated>2006-02-15T20:30:31.943-06:00</updated><title type='text'>And down the road we go</title><summary type='text'>We are successfully blogging Central Works. I am impressed with the level of writing so far.I would like to propose that we take a break next week from the summary and critique in Central Works and instead try to make connections, on the one hand, between the pragmatic nature of work that technical communicators do in the work place, and on the other hand, the kind of theoretical work that we </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114005686708721054/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114005686708721054' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114005686708721054'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114005686708721054'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/02/and-down-road-we-go.html' title='And down the road we go'/><author><name>Lee S. Tesdell</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-114004113552375083</id><published>2006-02-15T16:04:00.000-06:00</published><updated>2006-02-15T16:05:35.526-06:00</updated><title type='text'>The price of expediency in tech writing</title><summary type='text'>For his article “The Ethic of Expediency: Classical Rhetoric, Technology, and the Holocaust” Steven Katz takes a bit of a philosophical look at what technical communication should be used to accomplish. Katz talks about how in order to be successful, a writer must adopt the ethos whatever organization they are working for. He quotes Walker Gibson’s idea that “in this style responsibility is </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/114004113552375083/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=114004113552375083' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114004113552375083'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/114004113552375083'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/02/price-of-expediency-in-tech-writing.html' title='The price of expediency in tech writing'/><author><name>Wes Ahles</name><uri>http://www.blogger.com/profile/17729944904258226209</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-113997416514997150</id><published>2006-02-14T21:28:00.000-06:00</published><updated>2006-02-14T21:29:25.166-06:00</updated><title type='text'>Sullivan on political-ethical implications of defining tech comm as a practice</title><summary type='text'>Dale Sullivan published “Political-Ethical Implications of Defining Technical Communication as a Practice” in 1990.  Sullivan’s article focuses on what he sees as a conflict between humanism and vocationalism in technical communication education.  He argues that while many technical writing educators are sympathetic with the humanistic point of view, since they “teach thought forms and discourse </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/113997416514997150/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=113997416514997150' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113997416514997150'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113997416514997150'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/02/sullivan-on-political-ethical.html' title='Sullivan on political-ethical implications of defining tech comm as a practice'/><author><name>Anna</name><uri>http://www.blogger.com/profile/13614810967604329092</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-113993312701153351</id><published>2006-02-14T09:57:00.000-06:00</published><updated>2006-02-14T10:10:52.113-06:00</updated><title type='text'>Humanistic Approach to Technical Writing</title><summary type='text'>In the essay, A Humanistic Rationale for Technical Writing, written in 1979, Carolyn R. Miller, daunted by a question that arose in a committee discussion, debates on whether or not technical writing has humanistic value. She critiques the common belief of technical writing being a ‘skill’ course with little or no humanistic value. Miller credits the positivist view of science for this belief. </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/113993312701153351/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=113993312701153351' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113993312701153351'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113993312701153351'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/02/humanistic-approach-to-technical.html' title='Humanistic Approach to Technical Writing'/><author><name>Nisha</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-113980535943493949</id><published>2006-02-12T22:32:00.000-06:00</published><updated>2006-02-13T08:46:13.236-06:00</updated><title type='text'>Durack’s View on Women’s Role in the History of Technical Communication</title><summary type='text'>In her essay "Gender, Technology, and Technical Communication", Katherine T. Durack debates the reasons behind women’s invisibility from the recorded history of science and technology. During the course of her essay, Durack, with the help of both references and citations, succeeds in proving her point that historians have often ignored the contributions by women to the fields of science and </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/113980535943493949/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=113980535943493949' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113980535943493949'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113980535943493949'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/02/duracks-view-on-womens-role-in-history.html' title='Durack’s View on Women’s Role in the History of Technical Communication'/><author><name>Nisha</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-113968063391284666</id><published>2006-02-11T11:56:00.000-06:00</published><updated>2006-02-11T11:59:55.040-06:00</updated><title type='text'>Mary Lay on what feminist theory has to offer tech comm</title><summary type='text'>Mary M. Lay originally published “Feminist Theory and the Redefinition of Technical Communication” in the Journal of Business and Technical Communication in 1991.  In her article, she examines how “current views of scientific objectivism and the adoption of ethnographic studies—particularly those of collaborative writing—necessitate a new and, perhaps, revolutionary affiliation for technical </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/113968063391284666/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=113968063391284666' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113968063391284666'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113968063391284666'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/02/mary-lay-on-what-feminist-theory-has.html' title='Mary Lay on what feminist theory has to offer tech comm'/><author><name>Anna</name><uri>http://www.blogger.com/profile/13614810967604329092</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-113944025472292512</id><published>2006-02-08T17:05:00.000-06:00</published><updated>2006-02-08T17:10:54.733-06:00</updated><title type='text'>What is technical about tech writing? Dobrin may have an answer....</title><summary type='text'>What David Dobrin does in his article “What’s Technical About Technical Writing?” is address ways in which other technical writers try to define technical writing, while also providing his own interpretation of what tech writing should be. What Dobrin first claims is that what tech writers choose to define “determines the definer’s project” (108). What he means by this is that there are two terms</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/113944025472292512/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=113944025472292512' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113944025472292512'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113944025472292512'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/02/what-is-technical-about-tech-writing.html' title='What is technical about tech writing? Dobrin may have an answer....'/><author><name>Wes Ahles</name><uri>http://www.blogger.com/profile/17729944904258226209</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-113885126910549095</id><published>2006-02-01T21:32:00.000-06:00</published><updated>2006-02-01T21:34:29.116-06:00</updated><title type='text'>Linda Driskill's "Content"</title><summary type='text'>In school, the tech comm student is taught from a textbook, studying the ways of constructing documents via ideas of comparison, analysis, and hierarchy. Through her article “Understanding the Writing Context in Organizations,” Linda Driskill points out that although these teachings methods are needed, the “success of many business documents seem to depend on factors outside the genre” that are </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/113885126910549095/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=113885126910549095' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113885126910549095'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113885126910549095'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/02/linda-driskills-content.html' title='Linda Driskill&apos;s &quot;Content&quot;'/><author><name>Wes Ahles</name><uri>http://www.blogger.com/profile/17729944904258226209</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-113881881419056547</id><published>2006-02-01T12:32:00.000-06:00</published><updated>2006-02-01T12:35:17.373-06:00</updated><title type='text'>Johnson's article on "audience involved" writing</title><summary type='text'>In “Audience Involved: Toward a Participatory Model of Writing,” Robert R. Johnson discusses what he calls “audience involved” discourse production, in which the user is an “actual participant in the writing process who creates knowledge and determines much of the content in the discourse” (93).  This model stands in contrast to the more traditional “addressed” or “invoked” audience models.  </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/113881881419056547/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=113881881419056547' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113881881419056547'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113881881419056547'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/02/johnsons-article-on-audience-involved.html' title='Johnson&apos;s article on &quot;audience involved&quot; writing'/><author><name>Anna</name><uri>http://www.blogger.com/profile/13614810967604329092</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-113872384151469413</id><published>2006-01-31T09:54:00.000-06:00</published><updated>2006-01-31T10:10:41.596-06:00</updated><title type='text'>So far, so good</title><summary type='text'>Both Wes and Anna have blogged their readings from the Histories section of Central Works. Both are well written blog postings. Wes points to Rutter's argument for a rhetorical basis for the work of technical communication as opposed to a science or engineering foundation. Anna explores the idea that technical communicators need to acknowledge the applicability of TC not just to software </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/113872384151469413/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=113872384151469413' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113872384151469413'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113872384151469413'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/01/so-far-so-good.html' title='So far, so good'/><author><name>Lee S. Tesdell</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-113867783823408934</id><published>2006-01-30T21:22:00.000-06:00</published><updated>2006-01-30T21:26:57.473-06:00</updated><title type='text'>Durack's article</title><summary type='text'>In “Gender, Technology, and the History of Technical Communication,” Katherine T. Durack argues that women are underrepresented in histories of technical communication “as technical writers, as scientists,” and “as inventors or users of technology” (36).  She discusses a common view of technical communication that defines it as having “a close relationship (in subject matter or function) to </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/113867783823408934/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=113867783823408934' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113867783823408934'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113867783823408934'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/01/duracks-article.html' title='Durack&apos;s article'/><author><name>Anna</name><uri>http://www.blogger.com/profile/13614810967604329092</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-113862868393188998</id><published>2006-01-30T07:41:00.000-06:00</published><updated>2006-01-30T07:44:43.976-06:00</updated><title type='text'>Good morning at the beginning of week three</title><summary type='text'>Thank you Wes for your pioneering blog posting as we begin our new semester. As Wes has done, please post your two-paragraph summary/critique to the blog. We will continue through the readings in this way. I would like to encourage your reactions to your colleagues writing as well. Let's make this an electronic conversation, not just a place to post our writing.</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/113862868393188998/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=113862868393188998' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113862868393188998'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113862868393188998'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/01/good-morning-at-beginning-of-week.html' title='Good morning at the beginning of week three'/><author><name>Lee S. Tesdell</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-113841059123242520</id><published>2006-01-27T19:07:00.000-06:00</published><updated>2006-01-27T19:09:51.246-06:00</updated><title type='text'>Summary and critique on Nutter's article from Central Works</title><summary type='text'>In his article “History, Rhetoric, and Humanism,” Rutter talks about the common belief that technical communication mimics science and technology. Both are “rigid, monolithic, and devoted to formulaic thinking” (25). This belief puts more emphasis on aspects such as grammar, punctuation, and the more mechanic ideas of writing. Rutter states that in order to be successful, technical communicators </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/113841059123242520/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=113841059123242520' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113841059123242520'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113841059123242520'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/01/summary-and-critique-on-nutters.html' title='Summary and critique on Nutter&apos;s article from Central Works'/><author><name>Wes Ahles</name><uri>http://www.blogger.com/profile/17729944904258226209</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-113812120137695495</id><published>2006-01-24T10:41:00.000-06:00</published><updated>2006-01-24T10:48:59.633-06:00</updated><title type='text'>Let's get started with our discussion of Central Works</title><summary type='text'>Our first reading is going to be from Part 1: Histories. We have three articles: Connors, Rutter, and Durack. I would like you each to write a two paragraph summary/critique of one of these articles. Please post your summary/critique by class time on Jan. 31. Tell us which article you are going to write on by Wednesday, Jan. 26.</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/113812120137695495/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=113812120137695495' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113812120137695495'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113812120137695495'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/01/lets-get-started-with-our-discussion.html' title='Let&apos;s get started with our discussion of Central Works'/><author><name>Lee S. Tesdell</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-113755368034648681</id><published>2006-01-17T21:05:00.000-06:00</published><updated>2006-01-17T21:08:00.356-06:00</updated><title type='text'>Let's re-invigorate this blog!</title><summary type='text'>My 477/577 students wrote this blog two years ago. I think we should start it up again, don't you? We'll use it for 577 work. Students will post their critiques and responses of/to their readings in Central Works.</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/113755368034648681/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=113755368034648681' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113755368034648681'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/113755368034648681'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2006/01/lets-re-invigorate-this-blog.html' title='Let&apos;s re-invigorate this blog!'/><author><name>Lee S. Tesdell</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-108370402868248262</id><published>2004-05-04T15:53:00.002-05:00</published><updated>2004-05-04T15:57:39.356-05:00</updated><title type='text'>International, Cross-Cultural, and Translated Texts</title><summary type='text'>Campbell and Barker are strong proponents for the critical understanding of your audience. A technical writer makes effective decisions based on the knowledge that he/she possess of the audience. Campbell discusses the importance of audience research on pg. 32. Although Barker’s discussion if, of course, much more thorough, Campbell also offers an effective discussion.I have not had much </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/108370402868248262/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=108370402868248262' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108370402868248262'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108370402868248262'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/05/international-cross-cultural-and.html' title='International, Cross-Cultural, and Translated Texts'/><author><name>Leah</name><uri>http://www.blogger.com/profile/17548513970272447534</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-108370400535935398</id><published>2004-05-04T15:53:00.001-05:00</published><updated>2004-05-04T15:57:16.046-05:00</updated><title type='text'>Taxonomy of Reviews</title><summary type='text'>Barker and Campbell both offer good discussions of the review process. Campbell outlines each step and places reviews in their respective categories. While Barker offers a focused approach with a multi-person review process in place. I think that Barker’s view is the ideal – while Campbell’s discussion offers the “basics.”In my own experience, the review process can be a blessing and a project </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/108370400535935398/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=108370400535935398' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108370400535935398'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108370400535935398'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/05/taxonomy-of-reviews.html' title='Taxonomy of Reviews'/><author><name>Leah</name><uri>http://www.blogger.com/profile/17548513970272447534</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-108370398255145855</id><published>2004-05-04T15:53:00.000-05:00</published><updated>2004-05-04T15:56:53.250-05:00</updated><title type='text'>Week 5 Discussion</title><summary type='text'>Okay -- apparently I had problems longer than I thought. I'm just glad that I was able to recover some of these post responses and I didn't have to rewrite them.Both Barker and Campbell have compelling thoughts in their texts. However, Campbell’s text is a more how-to, with somewhat simplistic, straightforward discussions and accompanying tasks lists. However, Barker’s text is a more thorough </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/108370398255145855/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=108370398255145855' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108370398255145855'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108370398255145855'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/05/week-5-discussion.html' title='Week 5 Discussion'/><author><name>Leah</name><uri>http://www.blogger.com/profile/17548513970272447534</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-108334861684406226</id><published>2004-04-30T13:10:00.000-05:00</published><updated>2004-04-30T13:14:35.606-05:00</updated><title type='text'></title><summary type='text'>In reviewing the blogs, I realized that a couple posts did not go through properly. I was having some "technical difficulties" with our Internet DSL connection and my blogger account part way through the semester. Hence, I think my posts looked like they went through, but obviously, didn't -- since I can't find them now when I double-checked. So, I will repost my responses. I'll indicate to which</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/108334861684406226/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=108334861684406226' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108334861684406226'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108334861684406226'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/04/in-reviewing-blogs-i-realized-that.html' title=''/><author><name>Leah</name><uri>http://www.blogger.com/profile/17548513970272447534</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-108328636864760642</id><published>2004-04-29T19:52:00.000-05:00</published><updated>2004-04-29T19:57:06.576-05:00</updated><title type='text'>End of the Semester</title><summary type='text'>Have a great summer everyone!</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/108328636864760642/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=108328636864760642' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108328636864760642'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108328636864760642'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/04/end-of-semester.html' title='End of the Semester'/><author><name>Tony</name><uri>http://www.blogger.com/profile/14325038889954660848</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-108197948626816357</id><published>2004-04-14T16:43:00.000-05:00</published><updated>2004-04-14T16:55:42.293-05:00</updated><title type='text'>Language</title><summary type='text'>Language is an integral part of technical communication. As a technical communicator, it is important to use language correctly and efficiently so that the document is usable. Language involves both visual and verbal language involved in documents. It is important to keep in mind who our audience is so that both are used correctly. Certain symbols may mean two different things in different </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/108197948626816357/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=108197948626816357' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108197948626816357'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108197948626816357'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/04/language.html' title='Language'/><author><name>redfrontdoor</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-108181206731521719</id><published>2004-04-12T17:49:00.000-05:00</published><updated>2004-04-12T18:25:01.436-05:00</updated><title type='text'>Language and Technical Documents</title><summary type='text'>As an ongoing goal, technical writers strive to make their documents usable by virtually anyone.  This means that the language contained within the document must be suitable for any/all types of users.  This may be difficult since shapes, colors, gestures, and other visual mediums can represent a variety of meanings across cultures, as we discussed in the last blog.  Obviously, language also </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/108181206731521719/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=108181206731521719' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108181206731521719'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108181206731521719'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/04/language-and-technical-documents.html' title='Language and Technical Documents'/><author><name>Tony</name><uri>http://www.blogger.com/profile/14325038889954660848</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-108180641699504198</id><published>2004-04-12T16:46:00.000-05:00</published><updated>2004-04-12T16:50:50.670-05:00</updated><title type='text'></title><summary type='text'>Language – both text and visual – is everything in communicating information in a document. As a former reporter/editor, I grew accustomed to “writing down” for the mass media audience. Most newspaper and general magazine articles are geared to a fourth- to sixth-grade reading level. Hence, language needed to be appropriate to the topic as well as the audience.How do we know what language to use</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/108180641699504198/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=108180641699504198' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108180641699504198'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108180641699504198'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/04/language-both-text-and-visual-is.html' title=''/><author><name>Leah</name><uri>http://www.blogger.com/profile/17548513970272447534</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-108151478800819520</id><published>2004-04-09T07:24:00.000-05:00</published><updated>2004-04-09T10:22:57.810-05:00</updated><title type='text'>Language and Technical Documents</title><summary type='text'>Performance-oriented WritingIn Chapter 12, Barker grounds the needs of both the user and the technical writer in linguistic and learning theory. Based on research, the basic foundation of a functional technical document is simplified concrete language within a patterned structure designed to meet the users’ expectations and contextual needs. The guidelines that Barker offers technical writers (</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/108151478800819520/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=108151478800819520' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108151478800819520'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108151478800819520'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/04/language-and-technical-documents_09.html' title='Language and Technical Documents'/><author><name>Catherine</name><uri>http://www.blogger.com/profile/04284451966808565186</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-108144285741240307</id><published>2004-04-08T11:47:00.000-05:00</published><updated>2004-04-08T11:52:12.123-05:00</updated><title type='text'>Language and technical documents</title><summary type='text'>How do we know what language to use for our documents? As a novice tech writer, how would we start? Would you model your writing after the existing documents? Would you solicit feedback from users of your documents? What does Barker say about this topic in Chapter 12? As a novice tech writer, I would be interested to see previous documents written for the company I am employed at. After </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/108144285741240307/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=108144285741240307' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108144285741240307'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108144285741240307'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/04/language-and-technical-documents_08.html' title='Language and technical documents'/><author><name>sara</name><uri>http://www.blogger.com/profile/01966940825532441015</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-108136762837631605</id><published>2004-04-07T14:37:00.000-05:00</published><updated>2004-04-07T14:57:35.013-05:00</updated><title type='text'></title><summary type='text'>Language and technical documentsHow do we know what language to use for our documents? As a novice tech writer, how would we start? Would you model your writing after the existing documents? Would you solicit feedback from users of your documents? What does Barker say about this topic in Chapter 12?     When we look at our documents and try an decide what the appropriate language for that </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/108136762837631605/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=108136762837631605' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108136762837631605'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108136762837631605'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/04/language-and-technical-documents-how.html' title=''/><author><name>melissa</name><uri>http://www.blogger.com/profile/05617262951729513142</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-108122576826424822</id><published>2004-04-05T23:29:00.000-05:00</published><updated>2004-04-05T23:33:13.060-05:00</updated><title type='text'>Language and technical documents</title><summary type='text'>Language definitely describe everything. For technical documents, amount of language depends on the type of document. For example a manual of "how-to" should be short in sentence and contain simple words with aid of image as often as possible. A documentation in the other hand should be very precise and detailed therefore might contain more sentences compare to a "how-to" document.A good </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/108122576826424822/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=108122576826424822' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108122576826424822'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108122576826424822'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/04/language-and-technical-documents_05.html' title='Language and technical documents'/><author><name>agnes</name><uri>http://www.blogger.com/profile/08874137514407813455</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-108122404255190354</id><published>2004-04-05T23:00:00.000-05:00</published><updated>2004-04-05T23:04:27.606-05:00</updated><title type='text'>International, cross-cultural, and translated texts in editing</title><summary type='text'>Campbell’s opinion on the audience goes in parallel with Barker’s opinion. Both agree that you must understand your audience in order to design a good document. Different words can have different meanings and certain jargons can’t be directly translated to another language. Tone of document can also affect the audience too.I’ve written one cross-cultural document in the past and I agree that </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/108122404255190354/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=108122404255190354' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108122404255190354'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108122404255190354'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/04/international-cross-cultural-and.html' title='International, cross-cultural, and translated texts in editing'/><author><name>agnes</name><uri>http://www.blogger.com/profile/08874137514407813455</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-108120846069727763</id><published>2004-04-05T18:41:00.000-05:00</published><updated>2004-04-05T18:51:35.000-05:00</updated><title type='text'>Language and technical documents</title><summary type='text'>What is the connection between language and technical documents? You could say that language is everything. Let's narrow the focus a little bit. How do we know what language to use for our documents? As a novice tech writer, how would we start? Would you model your writing after the existing documents? Would you solicit feedback from users of your documents? What does Barker say about this </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/108120846069727763/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=108120846069727763' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108120846069727763'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108120846069727763'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/04/language-and-technical-doc_108120846069727763.html' title='Language and technical documents'/><author><name>Lee S. Tesdell</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-108113463572093359</id><published>2004-04-04T22:10:00.000-05:00</published><updated>2004-04-04T22:14:19.216-05:00</updated><title type='text'>International, cross-cultural, and translated texts in editing</title><summary type='text'>Campbell says it all on page 32 when she points out that “the more you know about your audience, the better the choices you can make in the content, wording, format, and design of the document.” This holds true for every audience, but is particularly pertinent to international audiences since many writers are not used to writing for these audiences.Since I have no experience translating </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/108113463572093359/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=108113463572093359' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108113463572093359'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108113463572093359'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/04/international-cross-cultural-and_04.html' title='International, cross-cultural, and translated texts in editing'/><author><name>sara</name><uri>http://www.blogger.com/profile/01966940825532441015</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-108112406088813000</id><published>2004-04-04T19:04:00.000-05:00</published><updated>2004-04-04T19:28:17.623-05:00</updated><title type='text'>Editing for International Audiences/Translated Texts</title><summary type='text'>Campbell Chapter 8 discusses the topic of editing and levels of review. On page 269, she recommends the editor develop and use a style sheet to facilitate consistency in reviewing documents for readability and usability. User analysis and organizational insight should guide the editor in her view. Given the context of an international or multi-lingual audience, it would be important to insert </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/108112406088813000/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=108112406088813000' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108112406088813000'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108112406088813000'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/04/editing-for-international.html' title='Editing for International Audiences/Translated Texts'/><author><name>Catherine</name><uri>http://www.blogger.com/profile/04284451966808565186</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-108035884820233128</id><published>2004-03-26T21:20:00.000-06:00</published><updated>2004-03-26T21:49:52.640-06:00</updated><title type='text'>Cross-Cultural Readers</title><summary type='text'>In Campbell Chapter 4, the use of language is discussed. Campbell and Barker both explain how language should be clear and accurate. Barker explains that using limited and simplified language offers better readability for cross-cultural readers. I especially liked how Campbell chapter 4 included excellent examples of simple words and phrases to use in the "Tools and Resources" section.Both </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/108035884820233128/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=108035884820233128' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108035884820233128'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108035884820233128'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/03/cross-cultural-readers.html' title='Cross-Cultural Readers'/><author><name>redfrontdoor</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-108009030022064913</id><published>2004-03-23T18:51:00.000-06:00</published><updated>2004-03-23T19:08:27.186-06:00</updated><title type='text'>Cross-cultural considerations</title><summary type='text'>I agree with Barker in that you should try to use short, simplified sentences with active verbs.  This will make things easier for users who are not very familiar with the English language; there will not be much additional text for them to sort through.  Also, it will make translating the document much easier if the wording is concise and simple.  I have talked with many people here at MSU who </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/108009030022064913/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=108009030022064913' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108009030022064913'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108009030022064913'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/03/cross-cultural-considerations.html' title='Cross-cultural considerations'/><author><name>Tony</name><uri>http://www.blogger.com/profile/14325038889954660848</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-108000632326942051</id><published>2004-03-22T19:03:00.000-06:00</published><updated>2004-03-22T19:48:48.530-06:00</updated><title type='text'></title><summary type='text'>Cross Cultural EditingEverything Campbell says about audience would fit in with Barker.  In looking at cross cultural editing it is really just looking at your documents audience.  You are trying to create something that works for the users you intend it to work for.  If these users possibly secondary English speakers, then you must take a closer look at your wording.My only experience in </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/108000632326942051/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=108000632326942051' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108000632326942051'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108000632326942051'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/03/cross-cultural-editing-everything.html' title=''/><author><name>Nate</name><uri>http://www.blogger.com/profile/16676165252220244039</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-108000273943712225</id><published>2004-03-22T18:27:00.000-06:00</published><updated>2004-03-22T18:49:04.436-06:00</updated><title type='text'></title><summary type='text'>International, cross-cultural, and translated texts in editingOn pp 290-292 Barker discusses editing for international audiences and for translation. First, look in Campbell for any information that would support Barker's claims. Second, what does your own experience tell you about this topic? Do you agree with Barker?Editing for Cross-Cultural ReadersCampbell supports some of Barker's claims</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/108000273943712225/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=108000273943712225' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108000273943712225'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108000273943712225'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/03/international-cross-cultural-and.html' title=''/><author><name>melissa</name><uri>http://www.blogger.com/profile/05617262951729513142</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-108000166178435534</id><published>2004-03-22T18:17:00.000-06:00</published><updated>2004-03-22T18:31:07.013-06:00</updated><title type='text'></title><summary type='text'>Campbell/Barker ReviewI know this is a little late but I in the review of Campbell and Barker, derived from our class discussion and from our readings I found that:  Campbell defines five different stages: Verification, validation, editing, proofreading, and approval. Barker defines six different stages: Managerial, user, technical, subject-matter, editorial, and sponsor. Some differences I </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/108000166178435534/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=108000166178435534' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108000166178435534'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108000166178435534'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/03/campbellbarker-review-i-know-this-is.html' title=''/><author><name>melissa</name><uri>http://www.blogger.com/profile/05617262951729513142</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-107990698345936262</id><published>2004-03-21T15:57:00.000-06:00</published><updated>2004-03-21T16:13:07.436-06:00</updated><title type='text'>Editing for Cross-Culture and Translation</title><summary type='text'>Campbell's discussion about audience (pg. 32) talks about how critical understanding your audience is.  The more you know about your audience, the better the choices you can make in content, wording, format, and design of the document.  This would apply to cross-culture documentation and editing for translation.  If you don't know enough about terminology, meanings of colors and icons, or </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/107990698345936262/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=107990698345936262' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107990698345936262'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107990698345936262'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/03/editing-for-cross-culture-and.html' title='Editing for Cross-Culture and Translation'/><author><name>Prinna</name><uri>http://www.blogger.com/profile/06055024508997632387</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-107989169619641657</id><published>2004-03-21T11:49:00.000-06:00</published><updated>2004-03-21T11:58:19.326-06:00</updated><title type='text'>cross cultural editing</title><summary type='text'>The chapter in Campell that supports Barker's pages on cross-cultural editing is best supported by chapter 4 "What's the best way to word this?" Campbell lays out rules for wording documentation, being a word miser, and use of clear, succint, and specific language.Following Barker's guidelines will help make documentation that is clear to readers of most reading levels, cultures, and to English </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/107989169619641657/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=107989169619641657' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107989169619641657'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107989169619641657'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/03/cross-cultural-editing.html' title='cross cultural editing'/><author><name>Bobby</name><uri>http://www.blogger.com/profile/16131803500112587917</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-107941187625072010</id><published>2004-03-15T22:37:00.000-06:00</published><updated>2004-03-15T22:41:11.983-06:00</updated><title type='text'>International, cross-cultural, and translated texts in editing</title><summary type='text'>On pp 290-292 Barker discusses editing for international audiences and for translation. First, look in Campbell for any information that would support Barker's claims. Second, what does your own experience tell you about this topic? Do you agree with Barker?</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/107941187625072010/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=107941187625072010' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107941187625072010'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107941187625072010'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/03/international-cross-cultural-and_15.html' title='International, cross-cultural, and translated texts in editing'/><author><name>Lee S. Tesdell</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-107939782753226844</id><published>2004-03-15T17:00:00.000-06:00</published><updated>2004-03-15T18:50:36.623-06:00</updated><title type='text'></title><summary type='text'>I guess I haven't been checking the blog lately.  Oops!  Before talking about the differences in review methods between Campbell and Barker, I would like to go back to our last topic.  Today on Minnesota Public Radio, they did a feature on accountability in newsbroadcasting.  It was interesting to me that a lot of the discussion was spent on the use of blogs and how they are impacting news and </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/107939782753226844/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=107939782753226844' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107939782753226844'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107939782753226844'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/03/i-guess-i-havent-been-checking-blog.html' title=''/><author><name>Linda</name><uri>http://www.blogger.com/profile/07023556601551479929</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-107930792474847330</id><published>2004-03-14T17:36:00.000-06:00</published><updated>2004-03-14T17:48:38.746-06:00</updated><title type='text'></title><summary type='text'>It is hard to say one of these views is better than the other.  I think the authors go about looking at this subject in a slightly different manor.  I personally find Campbell's approach more understandable and useful, but I also appreciate some of Barker's thoughts.One area both authors stress is that suitable time must be planned into the budget for this area.  I think that is a major point.</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/107930792474847330/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=107930792474847330' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107930792474847330'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107930792474847330'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/03/it-is-hard-to-say-one-of-these-views.html' title=''/><author><name>Nate</name><uri>http://www.blogger.com/profile/16676165252220244039</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-108122291797566993</id><published>2004-03-01T22:14:00.000-06:00</published><updated>2004-04-05T22:45:42.623-05:00</updated><title type='text'>Taxonomy of Reviews</title><summary type='text'>I think there’s no right or wrong between Barker and Campbell’s taxonomy of reviews. They are intended for different types of reviews and subjects. However from my opinion Campbell’s taxonomy of reviews can be applied to Barker’s whereas Barker is not. Campbell’s review is more generalized than Barker, he define the steps for reviews whereas Barker applies the taxonomy in a subjective ways </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/108122291797566993/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=108122291797566993' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108122291797566993'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/108122291797566993'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/03/taxonomy-of-reviews.html' title='Taxonomy of Reviews'/><author><name>agnes</name><uri>http://www.blogger.com/profile/08874137514407813455</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-107818924285396141</id><published>2004-03-01T18:44:00.000-06:00</published><updated>2004-03-01T19:48:01.670-06:00</updated><title type='text'>Levels of Review: Functional/Structural</title><summary type='text'>I would generalize that Barker sees the review process in terms of the hierarchical structure of an organization. Campbell describes the process with more functional labels. Ultimately one hopes that all aspects of the document(s) undergo some measurement against the proposed standard put forth in the planning stages. Certainly there is some crossover between the two taxonomies- perhaps </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/107818924285396141/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=107818924285396141' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107818924285396141'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107818924285396141'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/03/levels-of-review-functionalstructural.html' title='Levels of Review: Functional/Structural'/><author><name>Catherine</name><uri>http://www.blogger.com/profile/04284451966808565186</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-107818702982565168</id><published>2004-03-01T18:18:00.000-06:00</published><updated>2004-03-01T18:26:46.310-06:00</updated><title type='text'>Taxonomy of Reviews</title><summary type='text'>After reading Barker and Campbell's thoughts on the review process, I think both approaches effectively review all aspects of the documentation.  Campbell puts each aspect into its own category while Barker appears to repeat each aspect within six different categories.  While Campbell's method appears to be a bit more logical, I think that Barker's is more realistic.  From my review experience, I</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/107818702982565168/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=107818702982565168' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107818702982565168'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107818702982565168'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/03/taxonomy-of-reviews_01.html' title='Taxonomy of Reviews'/><author><name>Prinna</name><uri>http://www.blogger.com/profile/06055024508997632387</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-107811490407926163</id><published>2004-02-29T22:02:00.000-06:00</published><updated>2004-02-29T22:24:39.436-06:00</updated><title type='text'>A Campbell/Barker Review</title><summary type='text'>Campbell defines the review process through five different stages: Verification, validation, editing, proofreading, and approval.  While some of the steps can be meshed into one, Campbell suggests, if you have the time, do each one separately.Barker uses six different reviews including: Managerial, user, technical, subject-matter, editorial, and sponsor.  Each review has its own clearly defined</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/107811490407926163/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=107811490407926163' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107811490407926163'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107811490407926163'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/02/campbellbarker-review.html' title='A Campbell/Barker Review'/><author><name>Tony</name><uri>http://www.blogger.com/profile/14325038889954660848</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-107808305564911980</id><published>2004-02-29T13:30:00.000-06:00</published><updated>2004-02-29T13:33:50.390-06:00</updated><title type='text'>Taxonomy of Reviews</title><summary type='text'>I believe that Campbell's taxonomy of reviews is more efficient and useful. I like how you can see that each review is a step after the next. When I review a document, there are different things I look for each time, which is why a list of steps to follow is very useful. Campbell’s simplifies and labels the steps that I already follow when reviewing a document. Barker's list of reviews may be </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/107808305564911980/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=107808305564911980' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107808305564911980'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107808305564911980'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/02/taxonomy-of-reviews.html' title='Taxonomy of Reviews'/><author><name>redfrontdoor</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-107806218488701706</id><published>2004-02-29T07:26:00.000-06:00</published><updated>2004-02-29T07:49:51.950-06:00</updated><title type='text'>Reviews</title><summary type='text'>When I look at how Campbell and Barker define "review", it appears inherently different, and it is. However, I do not think either is right or wrong, it's simply a difference of context and semantics.Barker's description of review comes from a whole-project stand point. The ideas is to have the document reviewed by all the parties involved in the creation of the document, from the managers who </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/107806218488701706/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=107806218488701706' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107806218488701706'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107806218488701706'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/02/reviews.html' title='Reviews'/><author><name>Bobby</name><uri>http://www.blogger.com/profile/16131803500112587917</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-107806105914796236</id><published>2004-02-29T07:10:00.000-06:00</published><updated>2004-02-29T07:27:13.700-06:00</updated><title type='text'>Blogs</title><summary type='text'>The article is interesting in that it speaks of the core concept of the blog as new, although the author does allude to older forms. In the early days of public Internet before Web browsers when we had to use Pine, the blog as we know it today, to my mind, was the discussion group. People could create public or private groups, and the content was updated much like a blog, and could be presented </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/107806105914796236/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=107806105914796236' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107806105914796236'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107806105914796236'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/02/blogs.html' title='Blogs'/><author><name>Bobby</name><uri>http://www.blogger.com/profile/16131803500112587917</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-107791616931219995</id><published>2004-02-27T15:09:00.000-06:00</published><updated>2004-02-27T15:12:21.716-06:00</updated><title type='text'>Taxonomy of reviews</title><summary type='text'>The taxonomy in Campbell seems like it would be useful when incorporated into the different types of reviews listed in Barker. Granted, different types of Barker reviews may not be as all-encompassing as others (e.g. an editorial review is likely to be more in-depth than a sponsor review), but all of them could use Campbell’s five types of review as a reminder of the different steps each document</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/107791616931219995/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=107791616931219995' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107791616931219995'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107791616931219995'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/02/taxonomy-of-reviews_27.html' title='Taxonomy of reviews'/><author><name>sara</name><uri>http://www.blogger.com/profile/01966940825532441015</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-107783154409859573</id><published>2004-02-26T15:39:00.000-06:00</published><updated>2004-02-26T15:45:34.296-06:00</updated><title type='text'>Who is correct, Campbell or Barker?</title><summary type='text'>I have enjoyed reading your interesting discussions of blogging in online learning. Of course  originally for me one of the attractions was its uniqueness. The second attraction was that blogs offered us one more technology that we could learn to use in our online courses. That in itself seemed to be a worthwhile reason to use it. The more I use it as a pedagogical tool, the more I can adapt it </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/107783154409859573/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=107783154409859573' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107783154409859573'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107783154409859573'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/02/who-is-correct-campbell-or-barker.html' title='Who is correct, Campbell or Barker?'/><author><name>Lee S. Tesdell</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-107756441367738127</id><published>2004-02-23T13:26:00.000-06:00</published><updated>2004-02-23T13:29:40.216-06:00</updated><title type='text'>Blogs in online learning</title><summary type='text'>I thought the article was interesting. I agree with the idea that blog is an "unedited, published voice of the people" (Winer 2003). It's a way for students in this case to interact, share thoughts, and discuss online with ability to present information not only in text format but also image,and URL link.Though I've been using blog for more than 1 semester now, but somehow I'm still a bit </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/107756441367738127/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=107756441367738127' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107756441367738127'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107756441367738127'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/02/blogs-in-online-learning.html' title='Blogs in online learning'/><author><name>agnes</name><uri>http://www.blogger.com/profile/08874137514407813455</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-107747018913209685</id><published>2004-02-22T10:52:00.000-06:00</published><updated>2004-02-22T11:20:37.153-06:00</updated><title type='text'>"Blogosphere: Intellectual Cyberspace"</title><summary type='text'>It's interesting to read about the purpose of blogs AFTER using the technology for what appeared to be an exchange forum for short essay question responses for this course. In fact, when I posted a resulting question that occured to me in my response to the first initial prompt from Lee, it went totally unacknowledged. Based on that response, I took it that the forum in this course was meant </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/107747018913209685/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=107747018913209685' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107747018913209685'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107747018913209685'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/02/blogosphere-intellectual-cyberspace.html' title='&quot;Blogosphere: Intellectual Cyberspace&quot;'/><author><name>Catherine</name><uri>http://www.blogger.com/profile/04284451966808565186</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-107716308962117074</id><published>2004-02-18T21:43:00.000-06:00</published><updated>2004-02-18T22:00:50.186-06:00</updated><title type='text'>Blogging into the future</title><summary type='text'>The article gave a good insight into the purpose and effects of blogs (weblogs).  When I first heard of a blog (as Lee knows since I e-mailed him before our first class in a panic), I had no idea what it was.  I also admit that when I first started using the system, I became a little frustrated.  I would miss Lee's posts occasionally, and I wasn't used to checking something continuously (although</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/107716308962117074/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=107716308962117074' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107716308962117074'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107716308962117074'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/02/blogging-into-future.html' title='Blogging into the future'/><author><name>Tony</name><uri>http://www.blogger.com/profile/14325038889954660848</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-107697855457357022</id><published>2004-02-16T18:08:00.000-06:00</published><updated>2004-02-16T18:45:11.623-06:00</updated><title type='text'></title><summary type='text'>I found the article on blogging very interesting and helpful.  It opened up new horizons and possibilities that I had not considered before.  I didn't realize there was so much availability as far as hyperlinks within the blog until Lee had us do so this week.I liked their idea about introducing blogging and felt that some of us (me in particular) could have used a little more instruction on </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/107697855457357022/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=107697855457357022' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107697855457357022'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107697855457357022'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/02/i-found-article-on-blogging-very.html' title=''/><author><name>Linda</name><uri>http://www.blogger.com/profile/07023556601551479929</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-107699125318287679</id><published>2004-02-16T16:44:00.000-06:00</published><updated>2004-02-16T22:16:50.810-06:00</updated><title type='text'>Week five discussion</title><summary type='text'>In Breemer Case 4, there are a few problems that occur concerning policies and procedures.  First of all, Peterson broaches the idea of a meeting involving city council members and private landowners who would be interested in starting up a renewable energy project in their town, then inviting the students to attend.  When Mills, the teacher, mentions the idea to to Winterbach, he is confused to </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/107699125318287679/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=107699125318287679' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107699125318287679'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107699125318287679'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/02/week-five-discussion.html' title='Week five discussion'/><author><name>Tony</name><uri>http://www.blogger.com/profile/14325038889954660848</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-107695455798416816</id><published>2004-02-16T11:56:00.000-06:00</published><updated>2004-02-16T12:05:15.186-06:00</updated><title type='text'>Reponse For Week 5</title><summary type='text'>I would happen to agree with what the article is stating.  Blogs are a good source of learning tool for users, but I do believe you must pay attention to the audience in which the tool is being used.  If the blog was used in a class where the familiarity with computers is not that adequate, then I would be a little reluctant in using the learing tool.  This does correlate to the discussion we </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/107695455798416816/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=107695455798416816' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107695455798416816'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107695455798416816'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/02/reponse-for-week-5.html' title='Reponse For Week 5'/><author><name>melissa</name><uri>http://www.blogger.com/profile/05617262951729513142</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-107689939260852996</id><published>2004-02-15T20:19:00.000-06:00</published><updated>2004-02-15T20:45:48.390-06:00</updated><title type='text'></title><summary type='text'>response to the blog article.....The idea of publishing opportunity for knowledge is a good one.  There is something about putting down thoughts in a savable format and being able to both receive feedback and edit your ideas.  Lets face it we forget a lot of things, but when we save it the information can only become more valuable. The ability of understanding the feedback process and how to </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/107689939260852996/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=107689939260852996' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107689939260852996'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107689939260852996'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/02/response-to-blog-article.html' title=''/><author><name>Nate</name><uri>http://www.blogger.com/profile/16676165252220244039</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-107680936374271124</id><published>2004-02-14T19:36:00.000-06:00</published><updated>2004-02-14T19:45:18.233-06:00</updated><title type='text'>Role of blogs in online learning</title><summary type='text'>It was interesting to look at the article Lee posted. I hadn't realized just how blogs could be such a useful learning tool! Blogs seemed to be useful in posting answers as an assignment but it was interesting to learn that blogs are also important as a social interaction. Since we don't get to see each other while in class, it's nice to be able to "hear" each other on a blog.</summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/107680936374271124/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=107680936374271124' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107680936374271124'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107680936374271124'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/02/role-of-blogs-in-online-learning.html' title='Role of blogs in online learning'/><author><name>redfrontdoor</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6321008.post-107680859226467682</id><published>2004-02-14T19:07:00.000-06:00</published><updated>2004-02-14T19:38:47.903-06:00</updated><title type='text'>Week five discussion</title><summary type='text'>To find out just how to approach the audience situation in Breemer case 4 it would be helpful to follow the guidelines in Barker 5. Through analyzing the situation and emails given in light of Barker 5 it may be possible to solve the audience challenge.  The most helpful way would be to formally interview some possible audience members which is not possible in our situation. We may still be able </summary><link rel='replies' type='application/atom+xml' href='http://techdocspoliciesprocedures.blogspot.com/feeds/107680859226467682/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6321008&amp;postID=107680859226467682' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107680859226467682'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6321008/posts/default/107680859226467682'/><link rel='alternate' type='text/html' href='http://techdocspoliciesprocedures.blogspot.com/2004/02/week-five-discussion_14.html' title='Week five discussion'/><author><name>redfrontdoor</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>
