<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Information Design&gt;Metadata&gt;Writing</title>	<link>http://tc.eserver.org/dir/Articles/Information-Design/Metadata/Writing</link>
	<description>A listing of the most recently indexed works about Articles and Information Design and Metadata and Writing in the field of technical communication (and technical writing).</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>Articles&gt;Information Design&gt;Metadata&gt;Writing</title>
		<link>http://tc.eserver.org/dir/Articles/Information-Design/Metadata/Writing</link>
	</image>
	<item>
		<title>From Structured Abstracts to Structured Articles: A Modest Proposal</title>
		<link>http://tc.eserver.org/29020.html</link>
		<guid>http://tc.eserver.org/29020.html</guid>
		<description>Work with structured abstracts--which contain sub-headings in a standard order--has suggested that such abstracts contain more information, are of a higher quality, and are easier to search and to read than are traditional abstracts. The aim of this article is to suggest that this work with structured abstracts can be extended to cover scientific articles as a whole. The article outlines a set of sub-headings--drawn from research on academic writing--that can be used to make the presentation of scientific papers easier to read and to write. Twenty published research papers are then analyzed in terms of these sub-headings. The analysis, with some reservations, supports the viability of this approach.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Information-Design/Metadata/Writing.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>