<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Presentations&gt;Information Design&gt;XML</title>	<link>http://tc.eserver.org/dir/Presentations/Information-Design/XML</link>
	<description>A listing of the most recently indexed works about Presentations and Information Design 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>Presentations&gt;Information Design&gt;XML</title>
		<link>http://tc.eserver.org/dir/Presentations/Information-Design/XML</link>
	</image>
	<item>
		<title>Concept, Task, Reference: A Practical Guide to Choosing the Right Topic Type</title>
		<link>http://tc.eserver.org/35431.html</link>
		<guid>http://tc.eserver.org/35431.html</guid>
		<description>This presentation is for beginning to intermediate users of DITA. It&apos;s based on my experience with projects on which I&apos;m project manager, information architect, and writer.</description>
	</item>
	<item>
		<title>Developing DITA Maps</title>
		<link>http://tc.eserver.org/34722.html</link>
		<guid>http://tc.eserver.org/34722.html</guid>
		<description>DITA maps provide a mechanism for ordering topics and creating a topic hierarchy. Because DITA maps consist of lists of references to topics, you can reorganize the content in a deliverable simply by changing the order of the topic references. You can create different maps referencing the same source topics to create two deliverables to meet different users&apos; needs.</description>
	</item>
	<item>
		<title>Moving Forward with DITA 1.2 and the DITA-OT</title>
		<link>http://tc.eserver.org/34421.html</link>
		<guid>http://tc.eserver.org/34421.html</guid>
		<description> DITA enters a new phase this year with version 1.2. We&apos;ll learn about the big new features, such as keyref, and see them used in the latest DITA Open Toolkit. Attendees will know how to make use of new DITA 1.2 features using the DITA Open Toolkit. Attendees will understand key aspects of the new DITA 1.2 standard.</description>
	</item>
	<item>
		<title>XML Overview</title>
		<link>http://tc.eserver.org/33803.html</link>
		<guid>http://tc.eserver.org/33803.html</guid>
		<description>This presentation is a 90 minute session. It will cover many areas of XML and XML technologies. It has been constructed to provide the audience a broad understanding of XML and XML technologies in a short amount of time. The presentation is geared to ensure that new XML users can obtain the maximum benefit from other sessions presented at XML 2004. The attendees will gain an understanding of XML jargon and acronyms used in XML technologies, as well.</description>
	</item>
	<item>
		<title>How Tellabs Uses XML</title>
		<link>http://tc.eserver.org/33737.html</link>
		<guid>http://tc.eserver.org/33737.html</guid>
		<description>In the evolving and demanding world of telecommunications, Tellabs supports telecom service providers with the design, development, and deployment of wireline, wireless , and cable solutions worldwide. But with each unique solution deployment requires knowledge transfer from engineers to field service staff to ensure a smooth system upgrade. Learn how Tellabs&apos; New Product Introduction group used DITA to transition to customer-centric writing. *What are the key things the organization as a whole should keep in mind regarding processes?&quot;</description>
	</item>
	<item>
		<title>Essential Tools of an XML Workflow</title>
		<link>http://tc.eserver.org/33705.html</link>
		<guid>http://tc.eserver.org/33705.html</guid>
		<description>This webcast is for those publishers who have made the decision to pursue digital channels for their content. What tools are out there? What do all those acronyms mean? How can publishers implement new strategies without disrupting current workflows? Here we explore the alphabet soup of digital publishing, sort out the tools that are most useful, and help publishers find some solid ground.</description>
	</item>
	<item>
		<title>Metadata and XML: Improving the Findability of Information </title>
		<link>http://tc.eserver.org/33031.html</link>
		<guid>http://tc.eserver.org/33031.html</guid>
		<description>Information about objects on subjects - metadata describes objects. Purposes: Information management and discovery. Metadata enables content to be retreived, tracked, and assembled automatically.</description>
	</item>
	<item>
		<title>Does XML Suck? Or: Why XML is Technologically Terrible, but You Have to Use It Anyway</title>
		<link>http://tc.eserver.org/31756.html</link>
		<guid>http://tc.eserver.org/31756.html</guid>
		<description>XML purports to be a simple, vendor-neutral textual external representation for hierarchically-structured data. But...</description>
	</item>
	<item>
		<title>XML Holds Potential to Transform Data Transport</title>
		<link>http://tc.eserver.org/23521.html</link>
		<guid>http://tc.eserver.org/23521.html</guid>
		<description>XML is a language for creating data-description languages.</description>
	</item>
	<item>
		<title>XML Basics for Technical Communicators</title>
		<link>http://tc.eserver.org/21703.html</link>
		<guid>http://tc.eserver.org/21703.html</guid>
		<description>What is XML? Cross-platform, software and hardware independent tool for storing information. A subset of SGML. Its goal is to enable generic SGML to be served and processed on the Web in a way that is now possible with HTML. XML has been designed for ease of implementation and for interoperability with both SGML and HTML. </description>
	</item>
	<item>
		<title>Delivering Dynamic Content</title>
		<link>http://tc.eserver.org/13139.html</link>
		<guid>http://tc.eserver.org/13139.html</guid>
		<description>Cisco Systems IOS ITD Documentation group had a requirement to move to the dynamic delivery of documentation to their customers. This meant that the documentation had to be redesigned using a component architecture, moved to XML, and delivered through a personalization engine. This session discusses this process and the results.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Presentations/Information-Design/XML.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>