<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Design&gt;Web Design&gt;XML</title>	<link>http://tc.eserver.org/dir/Design/Web-Design/XML</link>
	<description>A listing of the most recently indexed works about Design and Web 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>Design&gt;Web Design&gt;XML</title>
		<link>http://tc.eserver.org/dir/Design/Web-Design/XML</link>
	</image>
	<item>
		<title>Reading XML with jQuery</title>
		<link>http://tc.eserver.org/35809.html</link>
		<guid>http://tc.eserver.org/35809.html</guid>
		<description>How to use the common jQuery JavaScript library to parse XML data sources, and to integrate them into your pages.</description>
	</item>
	<item>
		<title>Unwebbable</title>
		<link>http://tc.eserver.org/35174.html</link>
		<guid>http://tc.eserver.org/35174.html</guid>
		<description>It’s time we came to grips with the fact that not every “document” can be a “web page.” Some forms of writing just cannot be expressed in HTML—or they need to be bent and distorted to do so. But for once, XML might actually help.</description>
	</item>
	<item>
		<title>Introduction to RDFa: Part 2</title>
		<link>http://tc.eserver.org/35175.html</link>
		<guid>http://tc.eserver.org/35175.html</guid>
		<description>RDFa (“Resource Description Framework in attributes”) is having its five minutes of fame: Google is beginning to process RDFa and Microformats as it indexes websites, using the parsed data to enhance the display of search results with “rich snippets.”</description>
	</item>
	<item>
		<title>Enabling Web Service with Common Information Model</title>
		<link>http://tc.eserver.org/35020.html</link>
		<guid>http://tc.eserver.org/35020.html</guid>
		<description>In this article we will introduce the concept of WS-Management and Common Information Model (CIM). By exploring the SOAP message with multiple examples, we will learn how to transfer CIM operations through WS-Management SOAP messages.</description>
	</item>
	<item>
		<title>XSLT Tutorial</title>
		<link>http://tc.eserver.org/34173.html</link>
		<guid>http://tc.eserver.org/34173.html</guid>
		<description>A brief and basic tutorial about the XML-based scripting language.</description>
	</item>
	<item>
		<title>Improving an XML Feed Display Through CSS and XSLT</title>
		<link>http://tc.eserver.org/34143.html</link>
		<guid>http://tc.eserver.org/34143.html</guid>
		<description>XML feeds, though useful, are boring to look at in a browser because they are simple XML files. It&apos;s possible though to make them easier on the eye, and in this article we&apos;ll look at two ways of doing that. First, we&apos;ll use simple CSS properties to format each XML node, and then we&apos;ll use a little more complex but much more powerful XSL transformation.</description>
	</item>
	<item>
		<title>Browser Problems with the XML Prolog</title>
		<link>http://tc.eserver.org/34005.html</link>
		<guid>http://tc.eserver.org/34005.html</guid>
		<description>Some browsers have difficulty upon encountering the XML Prolog. In some cases, the browser will render all the markup as text. In other cases, when a browser has some XML support, it might attempt to render the document as an XML tree. To avoid these problems, many practicing web professionals prefer to leave the prolog off. This table will help you make that decision by showing you which browsers have known problems with the XML prolog.</description>
	</item>
	<item>
		<title>Building Dynamic Applications With Mozilla, REX and XQuery.</title>
		<link>http://tc.eserver.org/33975.html</link>
		<guid>http://tc.eserver.org/33975.html</guid>
		<description>The Mozilla platform offers a rich support of XML techniques, from low level ones (XPath, RDF, DOM, e4x) to rendering dialects like XHTML, SVG, XUL and XForms, thus making this platform a natural choice for the XML inclined. It is becoming a platform of choice when developing rich connected applications. When building dynamic applications, the developer is often facing a common set of programming patterns : gathering data from various remote and local sources, storing data with an optional transformation phase, and updating parts of the GUI to reflect the modifications in the data store. With today&apos;s ubiquitous use of XML as a data exchange syntax, a major part of these tasks can be achieved with XML based solutions.&#xD;&#xD;In this article we will present an XML centric solution that aims at minimizing the impedance mismatch between different data models that plagues classical architectures involving for instance XML/object/relationnal translation. It combines some of Mozilla&apos;s existing capabilities with REX (Remote Events for XML) and a native XML database with XQuery support. REX provides means to update the XUL based GUI and the database, while the XML database is used as a versatile storage engine.</description>
	</item>
	<item>
		<title>The Essence of Declarative, XML-based Web Applications: XForms and XSLT</title>
		<link>http://tc.eserver.org/33982.html</link>
		<guid>http://tc.eserver.org/33982.html</guid>
		<description>In this session, the author discusses best practices, common patterns and pitfalls in using XSLT as a host language for generating web-based user interfaces expressed in XForms.</description>
	</item>
	<item>
		<title>Language Support for Web Service Development</title>
		<link>http://tc.eserver.org/33983.html</link>
		<guid>http://tc.eserver.org/33983.html</guid>
		<description>We will demonstrate how enhancements to the XJ language (http://alphaworks.ibm.com/tech/xj) facilitate the development of Web Service applications.</description>
	</item>
	<item>
		<title>The Session Concept and Web Services</title>
		<link>http://tc.eserver.org/33904.html</link>
		<guid>http://tc.eserver.org/33904.html</guid>
		<description>This paper describes the session concept as it relates to middleware systems in general and Web services in particular. Common applications of the session concept are found in distributed object systems, the Web, and messaging middleware systems. The purpose of a session is to allow multiple individual Web Services to enter a relationship by sharing certain common attributes as an externally modeled entity. For example, multiple Web Services executing within the scope of a single authorized/secure session. In the context of Web services, explicit building blocks for session-oriented protocols and services have been proposed in two specifications, WS-Addressing and WS-Context. The distinguishing characteristic of these two proposals is the degree of coupling they introduce between session participants. In this paper we shall compare and contrast the underlying models these specifications present, as they relate to the session concept in Web services. The aim is to illustrate the advantages and disadvantages of both approaches and summarize best-practices and techniques for supporting a scalable Web services architecture. Note, although this paper is not purely research oriented, it does make an important contribution in the area of software practices and experiences for current and future researchers. The authors believe that it is important to ensure that the Web services architecture scales as well as the World Wide Web and as we shall see, the session concept and how it is provided play an integral role in that arena.</description>
	</item>
	<item>
		<title>Bulletproofing Web Services</title>
		<link>http://tc.eserver.org/33823.html</link>
		<guid>http://tc.eserver.org/33823.html</guid>
		<description>As companies and consumers rely more on Web services, it becomes increasingly important for Web services developers to know how to properly design, develop, deploy, and ultimately manage a Web services system. However, because of the inherent complexities that can arise with a Web service implementation, it can be difficult to grasp practical fundamentals and devise a step-by-step plan for Web services development.</description>
	</item>
	<item>
		<title>Getting the Most Out of COCOON: A XML-Based Webs Service for a Registration Agency</title>
		<link>http://tc.eserver.org/33830.html</link>
		<guid>http://tc.eserver.org/33830.html</guid>
		<description>Since 2005 the German National Library of Science and Technology (TIB) is established as a DOI registration agency for scientific content. Data providers transmit XML-files containing the DC-based metadata descriptions of the scientific data to a webservice infrastructure at the TIB, which was created by the Research center L3S during a project founded by the registration agency for scientific content. Data providers transmit XML-files containing the DC-based metadata descriptions of the scientific data to a webservice infrastructure at the TIB, which was created by the Research center L3S during a project founded by the German research association (DFG). This webservice infrastructure is based on the web application framework COCOON. We have however extended COCOON with full webservice functionalities. Using XSLT the webservice is furthermore able to transform XML-metadata files into well-formed PICA-files to insert the metadata information into the library catalogue of the TIB.</description>
	</item>
	<item>
		<title>Binding the Graphical Web (Component and Data Bindings with XBL, XHTML and SVG)</title>
		<link>http://tc.eserver.org/33836.html</link>
		<guid>http://tc.eserver.org/33836.html</guid>
		<description>The emerging XML based web increasingly relies upon ways of presenting content in a just in time manner. Presentation technologies such as SVG and XHTML can do so, yet the power to properly harness them will likely lie in the emergent binding languages such as XBL, sXBL, and XTF.&#xD;&#xD;In this presentation, bindings and binding languages will be explored, illustrating how such environments as the Mozilla Firefox 1.5 browser are using XBL as a means for performing component binding into XHTML, SVG and XForms interfaces, looks at sXBL and the W3C&apos;s XBL directions, and details why such binding languages likely represent the future of XML presentation and interaction.</description>
	</item>
	<item>
		<title>Deployment Scenarios for Web Service Discovery</title>
		<link>http://tc.eserver.org/33805.html</link>
		<guid>http://tc.eserver.org/33805.html</guid>
		<description>Several Web service discovery technologies including Universal Description, Discovery and Integration (UDDI), Web Services Metadata Exchange (WS-MEX) and other lightweight protocols and techniques can be used for particular scenarios. This presentation will discuss the status of each of these technologies and how they relate to the Web services stack as well as which technology should be employed to solve certain types of Web service integration problems.</description>
	</item>
	<item>
		<title>Lessons from the Front Line: Building Interoperable Web Services</title>
		<link>http://tc.eserver.org/33765.html</link>
		<guid>http://tc.eserver.org/33765.html</guid>
		<description>The ability to interoperate across disparate vendors, platforms and infrastructure stacks is inherently important to the adoption of Web Services technology. For most organizations, cross platform interoperability and the move to a loosely coupled, Service Oriented Architecture (SOA) is usually the main rationale for adoption of the underlying Web Service technologies. In this paper we will discuss some of the issues and stumbling blocks towards interoperability. We will also demonstrate with an example, how an application developed in Java and deployed in a J2EE 1.4 compatible container can interoperate and be consumed from a different client, developed in C# on the .NET platform.</description>
	</item>
	<item>
		<title>The Foundation for Occasionally Connected Computing</title>
		<link>http://tc.eserver.org/33779.html</link>
		<guid>http://tc.eserver.org/33779.html</guid>
		<description>This paper motivates the need for a lightweight, standards-based web services implementation that runs on mass market mobile devices. It describes the advantages of using web services and the challenges which must be overcome to use web services on mass market devices with limited computing power and network bandwidth. The paper concludes by describing a new approach to web services which drastically reduces the code required to exchange data with remote services, enabling the creation of more compelling applications with sophisticated user interfaces and application logic.</description>
	</item>
	<item>
		<title>DOM, SAX and Standards - Where Now?</title>
		<link>http://tc.eserver.org/33787.html</link>
		<guid>http://tc.eserver.org/33787.html</guid>
		<description>It&apos;s been 7 years and three &quot;levels&quot; since the first W3C DOM activity. XML and the way it is used has changed vastly over that time. DOM itself has moved from an API to access and manipulate an in-memory tree with no concept of namespaces, to an end to end XML technology, where parsing, modification of the tree (with the ability to check for validity with a schema as you go) and serialization are all specified.</description>
	</item>
	<item>
		<title>Enhanced Interoperability for Security of XML Web Services</title>
		<link>http://tc.eserver.org/33743.html</link>
		<guid>http://tc.eserver.org/33743.html</guid>
		<description>Enterprises are adopting Web Services to ease application integration across heterogeneous environments within and across security domain boundaries. Security is an important element for the adoption of Web Services. The Organization for the Advancement of Structured Information Standards (OASIS) has recently ratified the Web Services Security standards (Web Services Security: SOAP Message Security 1.0 (WS-Security 2004 ), Web Services Security: UsernameToken Profile 1.0 , and Web Services Security: X.509 Certificate Token Profile ) to provide an extensible framework for providing message integrity, confidentiality, identity propagation, and authentication. The Web Services Interoperability Organization (WS-I) is profiling standards to provide guidelines for implementation and use of relevant standards to enhance interoperability. This paper describes the activities of the WS-I Basic Security Profile (BSP) Working Group (WG). This Working Group is chartered to improve interoperability of security technologies for Web Services by profiling the OASIS Web Service Security and HTTP Over TLS standards. This interoperability profile (known as the Basic Security Profile 1.0) is an extension of the WS-I Basic Profile . The WS-I Basic Profile addresses interoperability for implementations of core Web Services standards.</description>
	</item>
	<item>
		<title>Web 2.0: The Tipping Point for XML</title>
		<link>http://tc.eserver.org/33649.html</link>
		<guid>http://tc.eserver.org/33649.html</guid>
		<description>Have you been waiting for the right time to switch to XML publishing? O’Keefe illustrates that with the advent of Web 2.0, the time is now.</description>
	</item>
	<item>
		<title>Web and XML Glossary</title>
		<link>http://tc.eserver.org/33586.html</link>
		<guid>http://tc.eserver.org/33586.html</guid>
		<description>A concise list of all acronyms, with individual letter indices (always accessible via the letter bar) which organizes the full names as well.</description>
	</item>
	<item>
		<title>The Wisdom of Crowds Meets the Wisdom of Authors: How XML Enables the Semantic Web</title>
		<link>http://tc.eserver.org/32682.html</link>
		<guid>http://tc.eserver.org/32682.html</guid>
		<description>Key to the Semantic Web is semantic markup, which lets users annotate their web pages with metadata -- HTML attributes that don&apos;t get displayed in the document. Semantic metadata describes what the pages are about, letting authors define things with authority and precision.</description>
	</item>
	<item>
		<title>Microformat Encoding and Visualization</title>
		<link>http://tc.eserver.org/32530.html</link>
		<guid>http://tc.eserver.org/32530.html</guid>
		<description>So you have heard about microformats, read the introductory articles, and even bought the book. But now you are probably thinking &quot;great - I have done my part to make the web a better place by adding microformats; what&apos;s next? What can people do with my data besides add it to their address book or calendar?&quot; The intent of this article is to get you to think about microformats in different ways, and to demonstrate some interesting visualizations and mash-ups of microformatted content.</description>
	</item>
	<item>
		<title>jQuery and XML Revisited</title>
		<link>http://tc.eserver.org/32475.html</link>
		<guid>http://tc.eserver.org/32475.html</guid>
		<description>In releasing jQuery v.1.2, a decision was made by the development team to drop XPath support from the core. Instead, an officially released XPath jQuery plugin is now available, which provides deprecated functionality. Although initially disappointed by this decision, I was happy to discover that alternative methods for obtaining data from an XML file are still available without the plugin.</description>
	</item>
	<item>
		<title>An Introduction to RELAX NG </title>
		<link>http://tc.eserver.org/32239.html</link>
		<guid>http://tc.eserver.org/32239.html</guid>
		<description>RELAX NG is not a capitalized misspelling of something you probably get to do all too rarely as a busy programmer and web designer. If you use XML to any great degree, you&apos;ll want to take a close look at it. It can help make your life as a web developer easier, allowing you to relax a little more.</description>
	</item>
	<item>
		<title>Providing Options in RELAX NG</title>
		<link>http://tc.eserver.org/32240.html</link>
		<guid>http://tc.eserver.org/32240.html</guid>
		<description>XML schemas don&apos;t have to be rigid. Sometimes, it&apos;s best to provide flexibility and allow the author of XML documents to make choices. In this second part of a three-part article, we&apos;ll make some modifications to the schema we created &lt;a href=&quot;/32239.html&quot;&gt;in the first part&lt;/a&gt;, and learn how to make some things optional.</description>
	</item>
	<item>
		<title>Datatypes and More in RELAX NG</title>
		<link>http://tc.eserver.org/32241.html</link>
		<guid>http://tc.eserver.org/32241.html</guid>
		<description>Welcome to the third part of a three-part series on RELAX NG. In this part, we will discuss datatypes, the grammar element, and creating named patterns.</description>
	</item>
	<item>
		<title>The Wisdom of Crowds Meets the Wisdom of Authors: How XML Enables the Semantic Web</title>
		<link>http://tc.eserver.org/31865.html</link>
		<guid>http://tc.eserver.org/31865.html</guid>
		<description>Combining semantic markup with a granular authoring approach like DITA holds a lot of promise for content creators and consumers alike. Content becomes easy to define and even easier to discover. The combination also holds a lot of promise for the future of the Semantic Web itself. In fact, creating the Semantic Web might be as easy as authoring content in DITA.</description>
	</item>
	<item>
		<title>httplib2: HTTP Persistence and Authentication</title>
		<link>http://tc.eserver.org/31576.html</link>
		<guid>http://tc.eserver.org/31576.html</guid>
		<description>In this latest Restful Web column, Joe Gregorio explains HTTP persistent connections, pipelining, and the sad state of HTTP authentication.</description>
	</item>
	<item>
		<title>RSS, Search Engine Visibility and Brand Perception</title>
		<link>http://tc.eserver.org/31396.html</link>
		<guid>http://tc.eserver.org/31396.html</guid>
		<description>Branding has been called the most powerful idea in business, yet few companies consciously craft and promote their brand. Making a brand visible to an online audience can be an additional challenge. Studies show that searchers regard the companies that are placed on the first page of search engine results as the major players in the field. So how do you get the coveted page-one positioning? New technologies like RSS feeds are one way to accomplish this and make your brand more visible in the process.</description>
	</item>
	<item>
		<title>XML Processing in Ajax, Part 1: Four Approaches</title>
		<link>http://tc.eserver.org/31104.html</link>
		<guid>http://tc.eserver.org/31104.html</guid>
		<description>Any programming problem can be solved in multiple right ways. This series looks at four approaches for creating an Asynchronous JavaScript + XML (Ajax) weather badge, a small reusable widget that&apos;s easily embedded on any Web page. This first article lays the foundation and examines the first approach--walking the DOM tree.</description>
	</item>
	<item>
		<title>Visual Authoring With XML Data</title>
		<link>http://tc.eserver.org/30816.html</link>
		<guid>http://tc.eserver.org/30816.html</guid>
		<description>Macromedia Dreamweaver 8 supports two workflows when authoring with XML: client-side authoring with complete XSLT template pages and server-side with XSLT fragments. The client-side option is available from the Start page.</description>
	</item>
	<item>
		<title>Convert Atom Documents to JSON</title>
		<link>http://tc.eserver.org/30806.html</link>
		<guid>http://tc.eserver.org/30806.html</guid>
		<description>Converting an Atom document to JSON might, at first, appear to be a fairly straightforward task. Atom is, after all, just a bit of XML and XML-to-JSON conversion tools are widely available. However, the Atom format is more than just a set of XML elements and attributes. A number of subtle details can make proper handling of Atom difficult. This article describes those issues and demonstrates a mechanism implemented by the Apache Abdera project to convert Atom documents into JSON and produces a result that is readable, usable, and complete.</description>
	</item>
	<item>
		<title>Assemble a Cross-Platform Firefox Extension</title>
		<link>http://tc.eserver.org/30670.html</link>
		<guid>http://tc.eserver.org/30670.html</guid>
		<description>XUL is a surprisingly easy way to build cross-platform browser extensions or even stand-alone applications. Discover how to build powerful, flexible Mozilla browser extensions that go beyond the capabilities of other tools like embedded scripting languages or CGI--because they&apos;re built right into the user&apos;s browser.</description>
	</item>
	<item>
		<title>Yellow Screen of Death</title>
		<link>http://tc.eserver.org/30455.html</link>
		<guid>http://tc.eserver.org/30455.html</guid>
		<description>In Mozilla-based applications, the yellow screen of death is the screen displayed when they encounter an XML parsing error. This typically happens when the XML document that the browser is trying to access is not well-formed, for example when it does not nest tags properly.</description>
	</item>
	<item>
		<title>XML Data Binding</title>
		<link>http://tc.eserver.org/29978.html</link>
		<guid>http://tc.eserver.org/29978.html</guid>
		<description>XML became an integral part of Microsoft&apos;s strategy around the time of Internet Explorer 4. IE4 was an XML-aware browser. As well as displaying HTML documents, it could also display XML documents through an inbuilt XML parser. Another part of IE4 was something known as the XML DSO  (Data Source Object). The XML DSO allows you to manipulate primitive XML &apos;data islands&apos; by binding (or attaching) the XML data to HTML presentation elements. The XML elements within Internet Explorer continue to be improved and added to with every new IE release.</description>
	</item>
	<item>
		<title>Firefox 2.0 and XML</title>
		<link>http://tc.eserver.org/29953.html</link>
		<guid>http://tc.eserver.org/29953.html</guid>
		<description>Firefox 2.0 brought several important changes in its XML support. It&apos;s currently reaching its peak in user deployment. Learn about updated XML features in Firefox 2.0, including a controversial change to the handling of RSS Web feeds.</description>
	</item>
	<item>
		<title>Save Time and Code with XPath 2.0 and XSLT 2.0</title>
		<link>http://tc.eserver.org/29961.html</link>
		<guid>http://tc.eserver.org/29961.html</guid>
		<description>Three interesting new features in XPath 2.0 and XSLT 2.0 are the item data type, the to  operator, and the concept of sequences. Build a sample application that uses these features to generate a sophisticated HTML view of an XML document, and with the new features in XSLT 2.0, create shorter stylesheets that are easier to maintain. Along the way, spend a bit of time on data typing in XSLT 2.0, and learn to use the new &lt;xsl:function&gt; element.</description>
	</item>
	<item>
		<title>The Why and How of XML Data Islands</title>
		<link>http://tc.eserver.org/29590.html</link>
		<guid>http://tc.eserver.org/29590.html</guid>
		<description>This article explains a useful way to embed data in an HTML document, and store it on the client, using XML. With XML becoming ever more pervasive and the client side implementation gaining a lot of ground, you will probably find yourself using this technique in many projects.</description>
	</item>
	<item>
		<title>Ajax Tradeoffs: The Many Flavors of XML</title>
		<link>http://tc.eserver.org/28477.html</link>
		<guid>http://tc.eserver.org/28477.html</guid>
		<description>Ajax stands for Asynchronous JavaScript and XML and the idea is that with modern Web browsers you can, with acceptable reliability, keep a channel open to the server to pass data back and forth as your Web application is used. This contrasts with standard Web techniques that follow links, causing the entire page to load anew. Many aspects of Ajax-based development require design different decisions than traditional Web pages: How to manage the back button, how to display updated data, how often to send updates, and more. The focus for now will be on just one group of related aspects: what format should the data exchange take?</description>
	</item>
	<item>
		<title>Calling a Web Service Using VB6 with SOAP 3.0</title>
		<link>http://tc.eserver.org/28314.html</link>
		<guid>http://tc.eserver.org/28314.html</guid>
		<description>This article shows you how to create a client that calls a web service from Visual Basic 6 using SOAP 3.0. If you are still using Microsoft VB 6.0 or C++ and don&apos;t plan to move into VB.NET, you will find this method very useful.</description>
	</item>
	<item>
		<title>XML and Browsers</title>
		<link>http://tc.eserver.org/27860.html</link>
		<guid>http://tc.eserver.org/27860.html</guid>
		<description>Now you should know what XML is for and how to write a basic XML document. In this part I will show you how to create a full XML document and load it in a browser, as well and the different ways it can be displayed.</description>
	</item>
	<item>
		<title>Ajax RSS Reader</title>
		<link>http://tc.eserver.org/27746.html</link>
		<guid>http://tc.eserver.org/27746.html</guid>
		<description>Learn how to build an Asynchronous JavaScript and XML (Ajax) Really Simple Syndication (RSS) reader, as well as a Web component that you can place on any Web site to look at the articles in the RSS feeds.</description>
	</item>
	<item>
		<title>Up and Atom</title>
		<link>http://tc.eserver.org/27743.html</link>
		<guid>http://tc.eserver.org/27743.html</guid>
		<description>Atom is really two different things, both related to syndication (blogs, newsfeeds, and other information which gets updated periodically). The Atom Syndication Format is an IETF standard for publishing entries (single topics or items) and feeds (collections of topics or items). The Atom Publication Protocol (sometimes called the Atom API or abbreviated APP) is a means for finding, listing, adding, editing, and removing content from an Atom repository. While Atom the Syndication Format has gone through the IETF process to become a standard, the standards committee is still at work on Atom the Publishing Protocol, although it seems likely that much of it has stabilized at this point.</description>
	</item>
	<item>
		<title>Don&apos;t CSS your XML</title>
		<link>http://tc.eserver.org/27716.html</link>
		<guid>http://tc.eserver.org/27716.html</guid>
		<description>CSS should not be used to present homemade XML as web pages. You end up with nothing but style. Neither man nor machine can understand the structure of your document. CSS should only be used for widely supported XML applications like XHTML.</description>
	</item>
	<item>
		<title>Delivering Content with RSS for Web Developers</title>
		<link>http://tc.eserver.org/27316.html</link>
		<guid>http://tc.eserver.org/27316.html</guid>
		<description>The delivery of web content is being revolutionized by a new technique known as syndication. The most common format for syndication is RSS, or Really Simple Syndication, an XML (eXtensible Markup Language) format for coordinating the delivery of time-based content streams, or &apos;feeds.&apos; This means that RSS can be used to deliver content that changes over time. RSS provides for the inclusion of additional data, similar to email attachments, using the ENCLOSURE tag.</description>
	</item>
	<item>
		<title>Using SOAP with PHP</title>
		<link>http://tc.eserver.org/27291.html</link>
		<guid>http://tc.eserver.org/27291.html</guid>
		<description>SOAP, the Simple Object Access Protocol, is the powerhouse of web services. It&apos;s a highly adaptable, object-oriented protocol that exists in over 80 implementations on every popular platform, including AppleScript, JavaScript, and Cocoa. It provides a flexible communication layer between applications, regardless of platform and location. As long as they both speak SOAP, a PHP-based web application can ask a C++ database application on another continent to look up the price of a book and have the answer right away.</description>
	</item>
	<item>
		<title>XML Transformations with CSS and DOM</title>
		<link>http://tc.eserver.org/27290.html</link>
		<guid>http://tc.eserver.org/27290.html</guid>
		<description>Mozilla permits XML to be rendered in the browser with CSS, and manipulated with the DOM. This is a real boon to those of us eager to experiment with XML transformations (both visual and structural) without having to delve into unfamiliar technologies such as XPath, the verbose traversal language of XSLT. If you’re already familiar with CSS and DOM, you’re more than halfway to achieving XML transformations in Mozilla.</description>
	</item>
	<item>
		<title>XML in Firefox 1.5, Part 1: Overview of XML Features</title>
		<link>http://tc.eserver.org/26877.html</link>
		<guid>http://tc.eserver.org/26877.html</guid>
		<description>The open source Firefox Web browser continues to grow in popularity. Users like the security and convenience features it offers. Developers like the Firefox attention to standards compliance, inherited from its Mozilla roots. The most recent version, Firefox 1.5, comes with many features for XML developers, including XML parsing, XHTML, CSS, XSLT, SVG, XML Events in JavaScriptâ„¢, and XForms. Additional third-party extensions provide even more XML support. In this article, Uche Ogbuji provides an overview of XML features in Firefox 1.5.</description>
	</item>
	<item>
		<title>XML in Firefox 1.5, Part 2: Basic XML Processing</title>
		<link>http://tc.eserver.org/26876.html</link>
		<guid>http://tc.eserver.org/26876.html</guid>
		<description>This second article in the series, &quot;XML in Firefox 1.5,&quot; focuses on basic XML processing. Firefox supports XML parsing, Cascading Stylesheets (CSS), and XSLT stylesheets.</description>
	</item>
	<item>
		<title>Text Alternatives to Inaccessible Web Pages</title>
		<link>http://tc.eserver.org/26369.html</link>
		<guid>http://tc.eserver.org/26369.html</guid>
		<description>This document details an XML-based method of providing end-user control over the format of an online document, Web page or entire Web site. This functionality is useful in situations where users, due to preference or physical ability, require a way to personalize their view of the content. Content managers, editors, and developers are also able to work with one set of documents, eliminating the need for multiple files that contain the same information with different formatting, therefore reducing redundancy, version inconsistencies, and workload.</description>
	</item>
	<item>
		<title>Processing the Output Buffer with XSLT</title>
		<link>http://tc.eserver.org/26040.html</link>
		<guid>http://tc.eserver.org/26040.html</guid>
		<description>This article shows an example of a technique mentioned in one of our recent articles. It uses the PHP output buffer in combination with XML as intermediate application layer. Ideally you should familiarize yourself with this concept first.</description>
	</item>
	<item>
		<title>Database-Driven Tree Structures with XML and XSLT</title>
		<link>http://tc.eserver.org/25840.html</link>
		<guid>http://tc.eserver.org/25840.html</guid>
		<description>This article deals with the display of tree-structures that are driven by a database. There are actually a few approaches to transform a 2-dimensional structure into a tree, and it seems odd that most are unknown to many developers.</description>
	</item>
	<item>
		<title>XML as Intermediate Application Layer</title>
		<link>http://tc.eserver.org/25724.html</link>
		<guid>http://tc.eserver.org/25724.html</guid>
		<description>In this article I want to share my thoughts on techniques for keeping our code XML-based - so there&apos;s no need to get your hands dirty in your application code to change the markup that is rendered afterwards.</description>
	</item>
	<item>
		<title>More About Custom DTDs</title>
		<link>http://tc.eserver.org/25642.html</link>
		<guid>http://tc.eserver.org/25642.html</guid>
		<description>Discusses the need for custom DTDs: why making a custom DTD for the sole purpose of validation is a mistake, and in which cases it does make sense to create and use one. For these cases, this article will also present techniques for creating clean custom DTDs and avoiding hacks.</description>
	</item>
	<item>
		<title>Can XForm Transform the Web?</title>
		<link>http://tc.eserver.org/23104.html</link>
		<guid>http://tc.eserver.org/23104.html</guid>
		<description>Today&apos;s Web forms are hopelessly tied to the original GUI of NCSA Mosaic for X Windows, circa 1994.</description>
	</item>
	<item>
		<title>Creating RSS Files for Your Web Site</title>
		<link>http://tc.eserver.org/23105.html</link>
		<guid>http://tc.eserver.org/23105.html</guid>
		<description>Recently I have received more and more questions about the Rich Site Summary (RSS) format and its use for Web masters. The short answer is that RSS is a great way for any Web site to advertise their content in an always up-to-date fashion.</description>
	</item>
	<item>
		<title>Doing It With XML</title>
		<link>http://tc.eserver.org/23106.html</link>
		<guid>http://tc.eserver.org/23106.html</guid>
		<description>An introduction on using XML for web development, tools for editing XML, and how to use CSS or XSL to control the presentation and processing of XML.</description>
	</item>
	<item>
		<title>GUIs and XML Configuration Data</title>
		<link>http://tc.eserver.org/23108.html</link>
		<guid>http://tc.eserver.org/23108.html</guid>
		<description>Discusses how XML is used in the configuration of GUI interfaces. He looks at Mozilla&apos;s XML-based User Interface Language (XUL) which allows you to write applications that run without any particular dependency on the choice of underlying operating system. This may seem strange at first, but you&apos;ll soon see that this Mozilla project offers powerful tools for GUI building that allow you to develop for an extensive base of installed users.</description>
	</item>
	<item>
		<title>Introduction to XML for Web Developers</title>
		<link>http://tc.eserver.org/23109.html</link>
		<guid>http://tc.eserver.org/23109.html</guid>
		<description>Using simple, well-explained examples this tutorial walks you through XML and the sister XSL style sheet language.</description>
	</item>
	<item>
		<title>XML 1.1 and Namespaces 1.1 Revealed</title>
		<link>http://tc.eserver.org/23107.html</link>
		<guid>http://tc.eserver.org/23107.html</guid>
		<description>Explains what XML 1.1 and Namespaces 1.1 are about, what changes they bring, and how they affect other specs and users.</description>
	</item>
	<item>
		<title>Introduction to RSS</title>
		<link>http://tc.eserver.org/22643.html</link>
		<guid>http://tc.eserver.org/22643.html</guid>
		<description>Really Simple Syndication (RSS) is an XML format for news headlines. With RSS-enabled feeds, other web sites can easily include your content in their sites. And other applications (besides web browsers) can be used to view your content.</description>
	</item>
	<item>
		<title>The Organized Web</title>
		<link>http://tc.eserver.org/22646.html</link>
		<guid>http://tc.eserver.org/22646.html</guid>
		<description>This document discusses the evolution of the Internet from an unorganized collection of web pages to an organized collection of data. It outlines how XML is at the center of that transformation, and how organizations can take advantage of this evolution with the development of web based services.</description>
	</item>
	<item>
		<title>XSLT Programmer&apos;s Reference: XSLT in Context</title>
		<link>http://tc.eserver.org/22590.html</link>
		<guid>http://tc.eserver.org/22590.html</guid>
		<description>The purpose of XSLT, what kind of language it is, and how it fits in with other technologies you&apos;re likely to use in a typical Web-based application.</description>
	</item>
	<item>
		<title>Extensible Markup Language (XML) Tutorial</title>
		<link>http://tc.eserver.org/22335.html</link>
		<guid>http://tc.eserver.org/22335.html</guid>
		<description>The Extensible Markup Language (XML) is a subset of the Standard Generalised Markup Language (SGML), the standard for creating markup documents. Unlike HTML, another markup language based on SGML, XML allows you to describe data and its structure rather than display it. XML is not a replacement for HTML, but compliments it by allowing the author to describe their own tags. XML is extensible as the author can create an unlimited number of tags. There are no predefined tags in XML.</description>
	</item>
	<item>
		<title>Some Thoughts about SOAP versus REST on Security</title>
		<link>http://tc.eserver.org/22199.html</link>
		<guid>http://tc.eserver.org/22199.html</guid>
		<description>REST is the underlying architecture of the World Wide Web and its two core specifications, URIs and HTTP. It has been proposed that  instead of using new-from-scratch Web Services technologies we can get much more bang for our buck by understanding the full generality of what we&apos;ve got.  A community has arisen around this idea and we spend our time proving that what  the Web already has is better than what is being developed. This page addresses  the security weaknesses of the SOAP approach.</description>
	</item>
	<item>
		<title>Translating XML Documents with xml:tm</title>
		<link>http://tc.eserver.org/22183.html</link>
		<guid>http://tc.eserver.org/22183.html</guid>
		<description>Sooner or later someone will want to have your XML document  translated into another language. In fact XML  documents are much easier to translate than other  electronic documents because they separate out form  from content, and they conform to a rigorous standard  and defined syntax. There are various approaches to improving the translation process.</description>
	</item>
	<item>
		<title>Перево XML- окументовс помощью xml:tm</title>
		<link>http://tc.eserver.org/22184.html</link>
		<guid>http://tc.eserver.org/22184.html</guid>
		<description>Рано или поздно созданный вами XML-документ кто-то захочет перевести на другой язык. В действительности XML-документы переводить гораздо легче нежели другие электронные документы, т. к. они разделяют форму и содержание и соответствуют строгому стандарту и установленному синтаксису.</description>
	</item>
	<item>
		<title>XML Tips</title>
		<link>http://tc.eserver.org/22074.html</link>
		<guid>http://tc.eserver.org/22074.html</guid>
		<description>Extensible Markup Language, or XML, is currently the most promising language for storing and exchanging information on the World Wide Web. Although Hypertext Markup Language (HTML) is presently the most common language used to create Web pages, HTML has a limited capacity for storing information. In contrast, because XML allows you to create your own elements, attributes, and document structure, you can use it to describe virtually any kind of information—from a simple recipe to a complex database. And an XML document—in conjunction with a style sheet or a conventional HTML page—can be easily displayed in a Web browser.</description>
	</item>
	<item>
		<title>Introduction to XML for Web Developers</title>
		<link>http://tc.eserver.org/21986.html</link>
		<guid>http://tc.eserver.org/21986.html</guid>
		<description>Surely, if you have decided to learn about XML, you are probably already quite familiar with the concepts behind HTML (HyperText Markup Language). So let&apos;s start from there.</description>
	</item>
	<item>
		<title>Programming Web Services with SOAP</title>
		<link>http://tc.eserver.org/21655.html</link>
		<guid>http://tc.eserver.org/21655.html</guid>
		<description>The task of creating and deploying web services is really not all that difficult, nor is it all that different than what developers currently do in more traditional web applications. The tendency on all platforms is to automate more and more of the gory details and tedious work in creating web services. Most programmers don&apos;t need to know the exact details of encodings and envelopes; instead, they&apos;ll simply use a SOAP toolkit such as those described here.</description>
	</item>
	<item>
		<title>Beyond Text and Graphics: XML Makes Web Pages Function Like Applications</title>
		<link>http://tc.eserver.org/21618.html</link>
		<guid>http://tc.eserver.org/21618.html</guid>
		<description>XML is displacing the traditional &apos;web page&apos;--generally a static document, created with HTML. Most traditional web pages offer only slim interactivity and rely on an overworked server and CGI script. XML is promoting the concept of a &apos;weblication&apos; (web application) that can work wonders on the web client without generating so much Internet traffic.</description>
	</item>
	<item>
		<title>Take My Advice: Don&apos;t Learn XML</title>
		<link>http://tc.eserver.org/21625.html</link>
		<guid>http://tc.eserver.org/21625.html</guid>
		<description>If you&apos;re a developer interested only in the data-oriented side  of XML, and if you don&apos;t care about document authoring (writing  books, articles, manuals, love poems, Web pages, whatever), feel  free to ignore this article.&#xD;&#xD;&#xD;If, on the other hand, document  authoring is important to you (you&apos;re a technical writer, an  HTML markup author, manager of a documentation group, an  anonymous pamphleteer) and you&apos;re trying to decide whether it  would be worthwhile for you to learn XML and use it for  authoring documents, stick around. What you learn might save you  a lot of time and spare you from some unnecessary frustration.</description>
	</item>
	<item>
		<title>Understanding DOM</title>
		<link>http://tc.eserver.org/21624.html</link>
		<guid>http://tc.eserver.org/21624.html</guid>
		<description>Even before there was XML, there was the Document Object Model, or DOM. It allows a developer to refer to, retrieve, and change items within an XML structure, and is essential to working with XML. In this tutorial, you will learn about the structure of a DOM document. You will also learn how to use Java technology to create a Document from an XML file, make changes to it, and retrieve the output.</description>
	</item>
	<item>
		<title>XML Topic Maps By the Book</title>
		<link>http://tc.eserver.org/21627.html</link>
		<guid>http://tc.eserver.org/21627.html</guid>
		<description>Topic Maps provide a system for organizing information, and XML Topic Maps bring this system to the world of XML. In this article, Uche Ogbuji examines XML Topic Maps, introducing the technology in the course of reviewing a key book on the topic.</description>
	</item>
	<item>
		<title>Sharing Your Site with RSS</title>
		<link>http://tc.eserver.org/21174.html</link>
		<guid>http://tc.eserver.org/21174.html</guid>
		<description>Jason shares his knowledge about RSS: What it is, how it&apos;s used, and why you need it. Just don&apos;t ask him what it stands for.</description>
	</item>
	<item>
		<title>Deep XML</title>
		<link>http://tc.eserver.org/21044.html</link>
		<guid>http://tc.eserver.org/21044.html</guid>
		<description>At the recent XML conference, Norm Walsh hosted a nocturne on Practical RDF, the highlight of which was his tour through thenorman.walsh.name setup. From the outside you may think this is a mere blog, but it’s actually a side-effect of a frighteningly gnarly confluence of metadata streams which are shaken and stirred to produce a sprawling network of resources a small part of which you might want to peruse for Norm’s news &amp; views. I have a picture that made the audience at the session gasp in disbelief.</description>
	</item>
	<item>
		<title>Extensible Markup Language (XML) Activity Statement</title>
		<link>http://tc.eserver.org/20709.html</link>
		<guid>http://tc.eserver.org/20709.html</guid>
		<description>The Extensible Markup Language (XML) is a simple, very flexible text format derived from SGML (ISO 8879). Originally designed to meet the challenges of large-scale electronic publishing, XML is also playing an increasingly important role in the exchange of a wide variety of data on the Web.</description>
	</item>
	<item>
		<title> Migrating from HTML to XML</title>
		<link>http://tc.eserver.org/20458.html</link>
		<guid>http://tc.eserver.org/20458.html</guid>
		<description>As the Internet world shifts its focus to XML and related technologies, what happens to HTML? Everywhere you go, products are becoming &apos;XMLitized&apos; as vendors rush to gain market share. While this is great for companies that are only now beginning to build their infrastructures, what about the rest of us whose sites have existed for years, accumulating documents architected on old HTML technology? How are we to take our millions and millions of HTML documents and bring them into the next generation of Internet computing? Fortunately, the market for tools in this space is growing, and technologies like Extensible Hypertext Markup Language (XHTML) are making it easier to migrate your repository of existing HTML documents.</description>
	</item>
	<item>
		<title>A Child&apos;s Garden of XML</title>
		<link>http://tc.eserver.org/20247.html</link>
		<guid>http://tc.eserver.org/20247.html</guid>
		<description>Sooner or later, most web designers will be called upon to create an internal site. And will quickly learn that one&apos;s own company can be tougher to deal with than any client. Dave Linabury offers tips on surviving the process (and building something good in spite of it).</description>
	</item>
	<item>
		<title>Rated XHTML</title>
		<link>http://tc.eserver.org/20263.html</link>
		<guid>http://tc.eserver.org/20263.html</guid>
		<description>The W3C’s XHTML language is intended to bridge the web’s past (HTML) and future (XML). Shall we cross this bridge, now that we’ve come to it? Or is XHTML more trouble than it’s worth? Peter-Paul Koch puts forth the pros and cons.</description>
	</item>
	<item>
		<title>Validating XML: A Pretty Complete Primer</title>
		<link>http://tc.eserver.org/20253.html</link>
		<guid>http://tc.eserver.org/20253.html</guid>
		<description>XML does not come with a spell checker, and will not work if written improperly. Eisenberg teaches you two nifty ways to validate your XML.</description>
	</item>
	<item>
		<title>XML in Brief</title>
		<link>http://tc.eserver.org/20009.html</link>
		<guid>http://tc.eserver.org/20009.html</guid>
		<description>XML is the acronym for the extensible markup language. According to the W3C, it is &apos;the universal format for structured documents and data on the Web&apos;. The following list explains what XML is and what it is not.</description>
	</item>
	<item>
		<title>XML: Better Grist from a Better Mill?</title>
		<link>http://tc.eserver.org/19577.html</link>
		<guid>http://tc.eserver.org/19577.html</guid>
		<description>In a world of documentation acronyms — ASCII, ANSI, SGML, HTML, DTD, FOSI — I have recently been exposed to the current newcomer on the scene: Extensible Markup Language (XML). For the first time, I&apos;m seriously impressed with the possibility of a true breakthrough documentation solution. I&apos;m particularly impressed that, at last, the industry is thinking of documentation in a way that promises to be practical and useful to us all.</description>
	</item>
	<item>
		<title>XML and Accessibility</title>
		<link>http://tc.eserver.org/19246.html</link>
		<guid>http://tc.eserver.org/19246.html</guid>
		<description>XML (eXtensible Markup Language) is a meta-syntax, used to create new languages. It can be seen as a simplification of SGML (Standard Generalized Markup Language), designed to promote a wider acceptance in Web markets, but serving the same functionality of extensibility and new language design. XML is therefore not to be seen as a replacement of HTML, but as a new building layer, usage examples of which are: XHTML (for general HyperText content). Furthermore, it is important to understand that XML is not only a User Interface technology (like HTML), but can and is often used in protocol communication, to serialize and encode data to be sent from one machine to another.</description>
	</item>
	<item>
		<title>Introduction to XML for Technical Writers</title>
		<link>http://tc.eserver.org/18984.html</link>
		<guid>http://tc.eserver.org/18984.html</guid>
		<description>XML is still the hot technology for technical writing. New XML tools are being delivered at a fast pace Every day, there are new XML initiative being announced. But when you try to learn about this exciting new technology, when you review the many books that are appearing on shelves, or sites popping up on the Web, you&apos;ll find that the information that is available is mostly aimed at developers. This session focuses on the value that it brings to technical writers and their users, and will include code samples.</description>
	</item>
	<item>
		<title>XML: One Input, Many Outputs</title>
		<link>http://tc.eserver.org/18976.html</link>
		<guid>http://tc.eserver.org/18976.html</guid>
		<description>Hillesund (2002) argues that XML does not and cannot fulfil the often touted benefit that it allows authors and publishers to create documents that can be effectively presented in a variety of formats; that the &apos;doctrine of &apos;one input â*” many outputs&apos; ... is basically wrong.&apos; This Letter defends the position that XML is an effective technology, in fact the most effective technology in widespread use, for producing multiple output formats from a single input document.</description>
	</item>
	<item>
		<title>Tutorial de XML en Castellano</title>
		<link>http://tc.eserver.org/18875.html</link>
		<guid>http://tc.eserver.org/18875.html</guid>
		<description>En las siguientes páginas podéis acceder a un manual sobre XML y tecnologías asociadas totalmente en castellano.</description>
	</item>
	<item>
		<title>XML Structures for Existing Databases</title>
		<link>http://tc.eserver.org/18826.html</link>
		<guid>http://tc.eserver.org/18826.html</guid>
		<description>Relational databases are a mature technology, which, as they have evolved, have enabled users to model complex relationships between data that they need to store. In this chapter, we will see how to model some of the complex data structures that are stored in relational databases in XML documents.&#xD;&#xD;To do this, we will be looking at some database structures, and then creating content models using XML DTDs. We will also show some sample content for the data in XML to illustrate this. In the process, we will come up with a set of guidelines that will prove helpful when creating XML models for relational data.</description>
	</item>
	<item>
		<title>XML Accessibility Guidelines</title>
		<link>http://tc.eserver.org/18634.html</link>
		<guid>http://tc.eserver.org/18634.html</guid>
		<description>This document provides guidelines for designing Extensible Markup Language (XML) applications that lower barriers to Web accessibility for people with disabilities (visual, hearing, physical, cognitive, and neurological). XML, used to design applications such as XHTML, SMIL, and SVG, provides no intrinsic guarantee of the accessibility of those applications. This document explains how to include features in XML applications that promote accessibility.</description>
	</item>
	<item>
		<title>Building the Semantic Web</title>
		<link>http://tc.eserver.org/14913.html</link>
		<guid>http://tc.eserver.org/14913.html</guid>
		<description>In the information age it is widely understood that there is now too much information. Some of this newly created information will most certainly be valuable, but despite marked improvement in search tools, finding the valuable information is a slow panhandle. Perhaps in light of this situation, the W3C under the direction of Berners-Lee has begun to build the foundation for the next phase of the web. This phase, called the Semantic Web, will make information stored with this technology much more processible by machines.</description>
	</item>
	<item>
		<title>Inline XML</title>
		<link>http://tc.eserver.org/14898.html</link>
		<guid>http://tc.eserver.org/14898.html</guid>
		<description>I was sitting at my desk a few days ago, whiling away the time and I suddenly wondered why HTML includes a &amp;lt;code&amp;gt; tag, and a &amp;lt;var&amp;gt; tag, and yet it takes marking up code no further than that. It’d be understandable to have just the &amp;lt;code&amp;gt; tag, but if they’re going to have a &amp;lt;var&amp;gt; tag, shouldn’t they have more programming tags?</description>
	</item>
	<item>
		<title>The Death of HTML?</title>
		<link>http://tc.eserver.org/14783.html</link>
		<guid>http://tc.eserver.org/14783.html</guid>
		<description>Knobel considers whether recent developments in Web technology, such as the increasing popularity of XML, have fated HTML to obsolescence.</description>
	</item>
	<item>
		<title>Styling XML: An Opinionated Guide</title>
		<link>http://tc.eserver.org/14683.html</link>
		<guid>http://tc.eserver.org/14683.html</guid>
		<description>McLaughlin evaluates the abilities of CSS (Cascading Style Sheets) and XSLT (eXstensible Style Language for Transformation) to render XML content in Internet browsers.</description>
	</item>
	<item>
		<title>Using XSL in Internet Explorer 5</title>
		<link>http://tc.eserver.org/14707.html</link>
		<guid>http://tc.eserver.org/14707.html</guid>
		<description>Dann explains the workings of a simple Extensible Style Language (XSL) stylesheet capable of displaying an Extensible Markup Language (XML) user procedure in Internet Explorer 5.</description>
	</item>
	<item>
		<title>SVG: The New Flash</title>
		<link>http://tc.eserver.org/13666.html</link>
		<guid>http://tc.eserver.org/13666.html</guid>
		<description>Macromedia has been the dominant force behind vector-based graphics and animation on the web for nearly the past 10 years. Times change, and new methods are always on the horizon. The upcoming contender for vector graphics is Scalable Vector Graphics (SVG), an XML-based language under development by the W3C.</description>
	</item>
	<item>
		<title>Using XML</title>
		<link>http://tc.eserver.org/13586.html</link>
		<guid>http://tc.eserver.org/13586.html</guid>
		<description>XML is not just a pretty face, living in isolation from the rest of the computing world. XML is more than a rulebook for generating custom markup languages. It is part of a family of technologies, which, working together, make your XML-based documents very useful indeed.</description>
	</item>
	<item>
		<title>What the Hell is XML?</title>
		<link>http://tc.eserver.org/13360.html</link>
		<guid>http://tc.eserver.org/13360.html</guid>
		<description>XML (Extensible Markup Language) is the Eurodollar of web development. Both XML and the Euro bring order to chaos; both offer undeniable, wide-ranging benefits; both are poised, in 2002, to change the way we do things. Frankly, both scare the crap out of people.&#xD;&#xD;For web developers, 2002 is a time to conquer fears and take their first hands-on approach to XML. It&apos;s time to examine XML and realize the practical benefits that it can provide to web projects today.&#xD;&#xD;The bankers can fend for themselves.</description>
	</item>
	<item>
		<title>A Technical Writer&apos;s Introduction to XML</title>
		<link>http://tc.eserver.org/13210.html</link>
		<guid>http://tc.eserver.org/13210.html</guid>
		<description>XML is one of the hot topics in Web technology. More&#xD;and more XML sites are being developed every day.&#xD;You&apos;ve probably seen XML without realizing it. It&apos;s also&#xD;showing up in specific tools for technical writers: Sun&apos;s&#xD;JavaHelp uses XML components. But when you try to&#xD;learn about this exciting new technology, when you&#xD;review the many books that are appearing on shelves, or&#xD;sites popping up on the Web, you&apos;ll find that the&#xD;information that is available is mostly aimed at&#xD;developers. This session cuts through the technical detail&#xD;to the core of XML, to the value that it brings to technical&#xD;writers and their users.&#xD;Unlike HTML, which is based on a specific set of tags,&#xD;XML allows you to define your own tags. This means&#xD;you have the ability to tag information based on content&#xD;rather than format structure.</description>
	</item>
	<item>
		<title>Transformers: Using XSLT to Transform XML</title>
		<link>http://tc.eserver.org/13221.html</link>
		<guid>http://tc.eserver.org/13221.html</guid>
		<description>XSLT, the Extensible Stylesheet Language Transformation, can convert your XML data to HTML and other friendly formats. Introduce yourself to this snazzy technology.</description>
	</item>
	<item>
		<title>XML Basics and FAQ</title>
		<link>http://tc.eserver.org/13112.html</link>
		<guid>http://tc.eserver.org/13112.html</guid>
		<description>The World Wide Web Consortium, the standards body for all web technologies, describes XML as a “method for putting structured data in a text file” (See www.w3.org/XML/1999/XML-in-10-points.) That’s accurate, but doesn’t really describe what XML is. This session will attempt to cover the basics of what XML is and answer the questions most frequently asked by technical writers.</description>
	</item>
	<item>
		<title>X Marks the Spot</title>
		<link>http://tc.eserver.org/12995.html</link>
		<guid>http://tc.eserver.org/12995.html</guid>
		<description>An explanation of how one writer is using XML to produce documentation and why it&apos;s such a great idea. </description>
	</item>
	<item>
		<title>Introduction to XML: Fixing the Web</title>
		<link>http://tc.eserver.org/12981.html</link>
		<guid>http://tc.eserver.org/12981.html</guid>
		<description>What&apos;s wrong with the Web and how can the new XML technology fix it? This XML introduction is geared toward newcomers who have heard the buzz, but don&apos;t know what all the fuss is about. The article briefly surveys a number of new Web technologies such as XLL, XSL, RDF, DOM, MathML, SMIL, PGML, and how they relate to XML. Benefits of XML are stressed, as are potential applications in diverse fields. A reference section provides links to key XML resources, as well as to collections of other introductory articles.</description>
	</item>
	<item>
		<title>Defining an XML Document Model with a DTD</title>
		<link>http://tc.eserver.org/11730.html</link>
		<guid>http://tc.eserver.org/11730.html</guid>
		<description>An XML document is considered &apos;well written&apos; when its syntax is correct, and &apos;valid&apos; when it respects a document model. While a document must be &apos;well written,&apos; it does not necessarily have to be &apos;valid.&apos; However, as XML is a meta language, there are an infinite number of XML formats, and most XML documents should respect a particular document model, which can be defined in one of two ways: By a Document Type Definition (DTD); By an XML Schema. In this article, we are going to look at how you should go about implementing the former, using a DTD.</description>
	</item>
	<item>
		<title>Using XML/XSL for Web Publication</title>
		<link>http://tc.eserver.org/11731.html</link>
		<guid>http://tc.eserver.org/11731.html</guid>
		<description>In this article, we look at the problem of Web publication, a process which concerns all enterprises having to send and receive information. What makes XML the technical solution to content syndication? How can the XML/XSL couple facilitate multi-channel publication? We will illustrate this last point using an example near and dear to our hearts, the publication of TrendMarkers e-newsletter. </description>
	</item>
	<item>
		<title>XML: Structuring Data for the Web: An Introduction</title>
		<link>http://tc.eserver.org/11732.html</link>
		<guid>http://tc.eserver.org/11732.html</guid>
		<description>This XML introduction is geared toward newcomers who have heard the buzz, but don&apos;t know what all the fuss is about. The article briefly surveys a number of new Web technologies such as XLL, XSL, RDF, DOM, MathML, SMIL, PGML, and how they relate to XML. Benefits of XML are stressed, as are potential applications in diverse fields. A reference section provides links to key XML resources, as well as to collections of other introductory articles.  </description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Design/Web-Design/XML.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>