<?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;SGML&gt;XML</title>	<link>http://tc.eserver.org/dir/Articles/Information-Design/SGML/XML</link>
	<description>A listing of the most recently indexed works about Articles and Information Design and SGML and XML 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>Articles&gt;Information Design&gt;SGML&gt;XML</title>
		<link>http://tc.eserver.org/dir/Articles/Information-Design/SGML/XML</link>
	</image>
	<item>
		<title>Migrating SGML to XML: Lessons Learned</title>
		<link>http://tc.eserver.org/33795.html</link>
		<guid>http://tc.eserver.org/33795.html</guid>
		<description> Two years ago we began the process of upgrading our content management system. Part of this upgrade required our data to be migrated from an Informix database to an Oracle database. This presented us with the opportunity to convert our data from SGML to XML. This presentation will focus on three areas: analysis/preparation for migration, migration of the data and lessons learned.</description>
	</item>
	<item>
		<title>Creating Documents with Structural Markup</title>
		<link>http://tc.eserver.org/24188.html</link>
		<guid>http://tc.eserver.org/24188.html</guid>
		<description>Now we come to the point of actually producing documents using structural markup—either eXtensible Markup Language (XML) or Standard Generalized Markup Language (SGML). Our sequence of topics illustrates the recommended steps to follow when you first implement structural markup: Learn about it and convince yourself and your organization of its benefits, identify your specific goals and expectations, and spend plenty of time selecting or designing your document structures. Only then should you get down to the specifics of how to produce XML or SGML documents. If you simply try to drop in an XML editor to replace your current word processing application, you will be lucky to avoid total disaster.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Information-Design/SGML/XML.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>