<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Design&gt;Web Design&gt;Metadata&gt;Controlled Vocabulary</title>	<link>http://tc.eserver.org/dir/Design/Web-Design/Metadata/Controlled-Vocabulary</link>
	<description>A listing of the most recently indexed works about Design and Web Design and Metadata and Controlled Vocabulary 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>Design&gt;Web Design&gt;Metadata&gt;Controlled Vocabulary</title>
		<link>http://tc.eserver.org/dir/Design/Web-Design/Metadata/Controlled-Vocabulary</link>
	</image>
	<item>
		<title>Creating a Controlled Vocabulary</title>
		<link>http://tc.eserver.org/21280.html</link>
		<guid>http://tc.eserver.org/21280.html</guid>
		<description>You have probably heard information architects discussing the benefits of their latest taxonomy project and how you should be implementing one. But how, you might wonder, can you get started? In the next installment about Controlled Vocabularies, our authors go into detail about one methodology.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Design/Web-Design/Metadata/Controlled-Vocabulary.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>