<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Kling, Rob, Lisa Spector and Geoff McKim</title>	<link>http://tc.eserver.org/authors/Kling,_Rob,_Lisa_Spector_and_Geoff_McKim</link>
	<description>A bibliography of works by Kling, Rob, Lisa Spector and Geoff McKim in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Kling, Rob, Lisa Spector and Geoff McKim</title>
		<link>http://tc.eserver.org/dir/Kling,_Rob,_Lisa_Spector_and_Geoff_McKim</link>
	</image>
	<item>
		<title>The Guild Model</title>
		<link>http://tc.eserver.org/30743.html</link>
		<guid>http://tc.eserver.org/30743.html</guid>
		<description>The Guild Publishing Model is a workable and presently working model, taken seriously in computer science, economics, business, and demography among other fields; however, it has not entered the discussion of scholarly electronic communication. Instead, for example, discussion of scholarly communication in high energy physics focuses on arXiv.org, the repository model. We believe that this is a mistake; the GPM is an important and significant model that is worth noting, examining, and extending to other fields. The GPM can provide rapid sharing of information and increased comprehensive research access for those in academic departments or research institutes with small libraries, and it is an economically feasible model for institutions with basic computing support. The GPM is flexible, set up locally, according to interest, need, and available resources.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Kling,_Rob,_Lisa_Spector_and_Geoff_McKim.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>