<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://pgbartlett.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from PG Bartlett</title>
 <link>http://pgbartlett.sys-con.com/</link>
 <description>Latest News from PG Bartlett</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Thu, 10 Dec 2009 14:06:46 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>An Easy Introduction to XML Publishing - Part 3 of a Five-Part Series</title>
 <link>http://pgbartlett.sys-con.com/node/114133</link>
 <description>In Part 1 of this series we discussed some of the key problems of capturing and sharing information and in Part 2 we looked at the critical components of a solution: modularization, automation, and XML.&lt;p&gt;&lt;a href=&quot;http://pgbartlett.sys-con.com/node/114133&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Tue, 02 Aug 2005 17:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://pgbartlett.sys-con.com/node/114133</guid>
 <comments>http://pgbartlett.sys-con.com/node/114133#feedback</comments>
</item>
<item>
 <title>An Easy Introduction to XML Publishing</title>
 <link>http://pgbartlett.sys-con.com/node/48762</link>
 <description>In part 1 of this series, we discussed some of the key problems of capturing and sharing information - problems like delivering information to multiple types of media, making updates faster and easier, and reducing the cost and time to translate and publish. Given those challenges, what should we do? In this part, we&#039;ll describe the essentials for solving these problems, which include building a &#039;single source&#039; of information that eliminates redundancy, creating information in reusable modules, and automatically assembling and publishing information for multiple audiences and multiple media.  Let&#039;s take a trip through the Wayback Machine to 1960. You find yourself responsible for publishing a technical manual. You begin the project by figuring out what information the book will contain and assigning various sections to subject matter experts (SMEs). The SMEs are mostly engineers, and they write out their content in longhand on foolscap. (If you don&#039;t know that &#039;foolscap&#039; is writing paper, congratulate yourself on your youth and vitality.) The secretarial pool types out the handwritten notes from the engineers. An editor - that&#039;s your job too - reviews and edits those typewritten notes and then sends them back to the secretarial pool to re-type.&lt;p&gt;&lt;a href=&quot;http://pgbartlett.sys-con.com/node/48762&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 26 May 2005 10:15:00 EDT</pubDate>
 <guid isPermaLink="true">http://pgbartlett.sys-con.com/node/48762</guid>
 <comments>http://pgbartlett.sys-con.com/node/48762#feedback</comments>
</item>
<item>
 <title>Why Publishing is Getting More Complicated and Costly</title>
 <link>http://pgbartlett.sys-con.com/node/47285</link>
 <description>Are you just beginning to try to figure out how XML and content management can help you wrestle with your publishing problems? Are you confused by all the jargon and acronyms that the experts are throwing around? Do you wish that someone would clear it all up for you? If so, then this 4-part series of articles is for you.&lt;p&gt;&lt;a href=&quot;http://pgbartlett.sys-con.com/node/47285&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 02 Dec 2004 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://pgbartlett.sys-con.com/node/47285</guid>
 <comments>http://pgbartlett.sys-con.com/node/47285#feedback</comments>
</item>
<item>
 <title>Seven Ways to Mess Up with XML</title>
 <link>http://pgbartlett.sys-con.com/node/40724</link>
 <description>A successful XML publishing project inspired this article. The project&#039;s leader, who claims that the financial return gained for his company &#039;made his career&#039; there, achieved success for two reasons: he focused on the right goals and executed the project in the right way.&lt;p&gt;&lt;a href=&quot;http://pgbartlett.sys-con.com/node/40724&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 29 Oct 2003 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://pgbartlett.sys-con.com/node/40724</guid>
 <comments>http://pgbartlett.sys-con.com/node/40724#feedback</comments>
</item>
</channel>
</rss>
