<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Writing&gt;XML</title>	<link>http://tc.eserver.org/dir/Articles/Writing/XML</link>
	<description>A listing of the most recently indexed works about Articles and Writing and XML 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;Writing&gt;XML</title>
		<link>http://tc.eserver.org/dir/Articles/Writing/XML</link>
	</image>
	<item>
		<title>Structured Authoring for Everyone</title>
		<link>http://tc.eserver.org/34070.html</link>
		<guid>http://tc.eserver.org/34070.html</guid>
		<description>While the concepts of structured authoring are more than just slightly useful for technical writing, they can be beneficial for just about any writing task within an organization. But how do you bring XML-based structured authoring to the masses? Perhaps by taking a cue from a word processor called Yeah Write.</description>
	</item>
	<item>
		<title>Syntext Serna and New Trends in XML Content Authoring</title>
		<link>http://tc.eserver.org/33822.html</link>
		<guid>http://tc.eserver.org/33822.html</guid>
		<description>Recent trends in XML content authoring demonstrate increasing shift towards advanced reuse patterns and multi-source compound document architectures. This imposes completely new requirements for the XML authoring tools, most of which were originally developed for narrative document authoring and architectures like Docbook or TEI. The key requirement is the ability to provide a single, transparent, directly editable view for such complex documents.</description>
	</item>
	<item>
		<title>Technical Writing and XML: Reconciling Editorial License with Structured Markup</title>
		<link>http://tc.eserver.org/33784.html</link>
		<guid>http://tc.eserver.org/33784.html</guid>
		<description>In writing reference material, consistency of organization and presentation is key. If the same information is presented in a consistent order and style throughout the publication or information set, it enhances the readability and usability of the material for the consumer. Ease of use is vital. XML provides a means to assist in the standardization of reference material from both an organizational and a semantic/content-oriented standpoint. Standardization based on structure and content enhances the potential for reuse of the XML-tagged information for both print and electronic delivery.But while there can be a strong relationship between the authoring and editing of content and structured markup, all too often conflicts arise between technical writers and DTD/schema designers and programmers. The perceived need for editorial license and creative freedom by many authors/editors clashes with the need for rigid structure to facilitate ease of programming for markup technologists and programmers. The disagreements are commonly between format and structure, looseness and rigidity, and are often more philosophical than practical.</description>
	</item>
	<item>
		<title>Structured Authoring for Everyone</title>
		<link>http://tc.eserver.org/33673.html</link>
		<guid>http://tc.eserver.org/33673.html</guid>
		<description>Structured authoring isn&apos;t just for technical writers. Just about any department in an organization can benefit from it. This article looks at one way of bringing structured authoring to the masses: by adopting the authoring concepts used in an obscure word processor called Yeah Write.</description>
	</item>
	<item>
		<title>Paradigm Shifts are Never Pretty: Advice on Making the Move to XML Authoring</title>
		<link>http://tc.eserver.org/32179.html</link>
		<guid>http://tc.eserver.org/32179.html</guid>
		<description>The move toward XML-based authoring in technical publications is a classic paradigm shift. It requires content creators to change their writing process and learn new concepts.</description>
	</item>
	<item>
		<title>Authoring in XML -- Why Start?</title>
		<link>http://tc.eserver.org/32180.html</link>
		<guid>http://tc.eserver.org/32180.html</guid>
		<description>As techcom professionals, we have been talking about authoring in XML for a very long time. At first, it was a lot of hype about a format that required major programming skills and had zero tools’ support, but that is now changing. Today, there are hundreds, if not thousands, of tools that support XML and a standard called DITA that is in constant development to support content publishing for different industries. As a result, more and more companies seem to be embracing this content format.If you are a writer or techcom manager who is encouraging your company to make this change, then what do you need to know to prepare?</description>
	</item>
	<item>
		<title>XML Authoring: Coming to a Desktop Near You</title>
		<link>http://tc.eserver.org/32185.html</link>
		<guid>http://tc.eserver.org/32185.html</guid>
		<description>Organizations are moving business documents to structured XML authoring -- a technology that was once reserved for only the bravest of technical publications departments. They are using new tools that make the transition much easier, even for completely non-technical authors, and they are reaping benefits that will drive structured authoring in XML across the entire organization.</description>
	</item>
	<item>
		<title>Who Says You Can&apos;t Use Microsoft Word To Do XML?</title>
		<link>http://tc.eserver.org/32186.html</link>
		<guid>http://tc.eserver.org/32186.html</guid>
		<description>MS Word is not an XML authoring tool, no matter what your IT team believes. While Word may indeed understand and use some XML, it doesn&apos;t use XML in the way technical communicators need it to. Instead, it uses XML to transfer information back and forth between MS Office products. Useful? Yes. XML authoring? Not even close.</description>
	</item>
	<item>
		<title>XML Authoring: Coming to a Desktop Near You</title>
		<link>http://tc.eserver.org/31736.html</link>
		<guid>http://tc.eserver.org/31736.html</guid>
		<description>XML for use in technical publications is growing in popularity. As the author explains, technical writers are likely to become more and more involved in XML document production in the future. This article looks at the many benefits of XML authoring and the trend that&apos;s moving technical publications toward structured content.</description>
	</item>
	<item>
		<title>Authoring Content in XML</title>
		<link>http://tc.eserver.org/24650.html</link>
		<guid>http://tc.eserver.org/24650.html</guid>
		<description>XML authoring is the latest mode of electronic communication of content. XML is about freedom: freeing the content, freeing the author.</description>
	</item>
	<item>
		<title>Avoiding Traumatic XML/SGML Transitions: Moving to XML/SGML Without Losing Your Writers Along the Way</title>
		<link>http://tc.eserver.org/23612.html</link>
		<guid>http://tc.eserver.org/23612.html</guid>
		<description>When moving to single-sourcing through XML and SGML, management often spends considerable time on tools evaluation and content management, but not enough on&#xD;preparing the writers for the paradigm shift to the new&#xD;environment. This presentation provides some hints for a&#xD;successful transition for your personnel as well as your&#xD;documentation.</description>
	</item>
	<item>
		<title>A Writer&apos;s Guide to XML Content Management</title>
		<link>http://tc.eserver.org/22153.html</link>
		<guid>http://tc.eserver.org/22153.html</guid>
		<description>A discussion of how XML changes what you do as a writer.</description>
	</item>
	<item>
		<title>Anything Worth Writing Is Worth Writing in XML</title>
		<link>http://tc.eserver.org/14780.html</link>
		<guid>http://tc.eserver.org/14780.html</guid>
		<description>Tyson supports the claim of his title with a detailed discussion of three important benefits of XML.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Writing/XML.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>