The Extensible Markup Language (XML) is an open, general-purpose specification for creating markup languages. Its primary purpose is to help information systems share structured data, particularly via the Internet, and it is used both to encode documents and to serialize data. It is used in a wide variety of technical communication document formats, including Microsoft Word, OpenOffice, XHTML, DITA, DocBook, and RSS, among others.
#27316
Delivering Content with RSS for Web Developers
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 'feeds.' 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.
Apple Inc. (2006). Design>Web Design>XML>RSS
#13139
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.
Badre, Albert and Sharon Laskowski. STC Proceedings (2001). Presentations>Information Design>XML
#26198
A Delta Format for XML: Identifying Changes in XML Files and Representing the Changes in XML
This paper describes how changes to XML documents and data files can be represented in XML and proposes a delta format for XML. Although Canonical XML provides a mechanism for verifying that two XML files or documents are equal, it is more often necessary to determine the differences between two XML documents. Such differences should ideally be represented in XML and this paper describes how such changes can be represented in XML with minimal additional attributes and elements. The paper describes how any changes can be simply represented using this delta format, and how the delta file has the same look and feel as the original files being compared. The paper describes how the delta file can be transformed into HTML for viewing by using a simple XSL style sheet, and by modifying this style sheet changes to particular XML file types can be presented to users in a way that suits their view. In addition, the delta file can be processed by any XML application for other purposes.
La Fontaine, Robin. XML Europe (2001). Articles>Information Design>XML
#29638
Demonstration of an XML-Based Content Management System Implementation 
The impact of XML and content management on the field of technical communications is no longer just a speck on the horizon. This paper presents techniques and observations from the trenches of a real-world XML-based content management system implementation that is being used to develop and publish print and online documentation at a prominent software company.
Bookless, Jody, Annette Marx and Scott Davis. STC Proceedings (2005). Articles>Content Management>XML
#19679
Discusses some different ways of describing your document structure so that both computers and humans know what you mean.
Tyson, Paul H. Intercom (2003). Design>Information Design>XML>Metadata
#21184
Describing Document Structure, Part 2
Discusses some different ways of describing your document structure so that both computers and humans know what you mean.
Tyson, Paul H. Intercom (2003). Design>Information Design>XML>Metadata
#20390
Designing a New Schema with XML Design Patterns
Proposes the design of an XML-based type library format. If you've had exposure to Microsoft COM or Mozilla's XPCOM, you're probably familiar with their binary TLB (MS) and XDT (Mozilla) formats that define the available operations and interfaces for a package of portable components. An interpreted language such as JavaScript can use these definitions as cheat sheets to find out what operations and parameters are available to call on-the-fly.
Downey, Kyle. XML.com (2003). Articles>Information Design>XML>Metadata
#27633
Designing Your Own XML Schema: Learn the Essentials
This is the first article in a series which guides you in designing XML Schemas right from the basics without any hurdles.
Chaterjee, Jagadish. Dev Articles (2006). Articles>Information Design>Databases>XML
#29589
Displaying ADO Retrieved Data with XML Islands
An XML data island is a piece of well-formed XML embedded into an HTML file. This article will show you how to retrieve data in an XML format from a database using ADO; you will also learn how to bind this data into an HTML document.
Krishnaswamy, Jayaram. Dev Articles (2006). Articles>Information Design>XML>XHTML
#27456
This presentation addresses a low-effort-required solution for users looking to take a step into XML for their technical documentation. The Darwin Information Typing Architecture (DITA) and its associated public toolkit provide you with the DTDs, stylesheets and other tools you require to make your steps into XML.
Kravogel, Christian and Boris Horner. IDEAlliance (2005). Articles>Document Design>XML>DITA
#31124
I have seen a couple of blog postings lately that underscore the statement that DITA is not for everyone or for every situation.
Rockley Group, The (2008). Articles>Information Design>XML>DITA
#29971
Can DITA be used as a Help authoring technology? Superficially, of course it can! The DITA Open Toolkit includes an HTML Help transformer, an Eclipse Help transformer, and an HTML transformer (which can also generate some sort of Table of Contents). So isn't it obvious then? DITA is perfect for Help authoring. Or is it? Looking a bit deeper, it's not so obvious. Can I include context-hooks in my content? Can I specify a popup link? Can I build a modular Help system? If I can't, then DITA is probably not suitable for Help.
Self, Tony. HyperWrite (2007). Articles>Documentation>XML>DITA
#31754
A searchable knowledge base of specifications for DITA users.
#31749
Single sourcing is good, I’m sure most of us can agree on that, but I’ve recently been wondering if perhaps DITA isn’t quite good enough?
McLean, Gordon. One Man Writes (2007). Articles>Content Management>XML>DITA
#27048
The DITA Knowledge Base pages provide a reliable basis of technical and educational information on the standard.
XML.org (2006). Resources>Information Design>XML>DITA
#29285
#31752
You will better understand how DITA can support your organization and how it can scale to meet your enterprise content needs by first understanding the basics of DITA standardization.
Priestley, Michael and Amber Swope. Just Systems (2008). Articles>Information Design>XML>DITA
#29286
The DITA Open Toolkit is an implementation of the OASIS DITA Technical Committee's specification for Darwin Information Typing Architecture (DITA) DTDs and Schemas. The Toolkit transforms DITA content (maps and topics) into deliverable formats.
Sourceforge (2007). Resources>Software>XML>DITA
#26180
DITA Resources Online (Darwin Information Typing Architecture)
If you need to learn more about the Darwin Information Typing Architecture (DITA), look no further. Links to a few of the most useful DITA resources available on the web today.
Rockley Group, The (2005). Resources>Content Management>Metadata>XML
#31755
This area provides access to my DITA specialization tutorial and other DITA specialization-related information and materials.
#29972
Two of the oft-quoted benefits of DITA, the Darwin Information Typing Architecture, are 'single-sourcing' and 'content re-use'. These benefits do not only apply to the commonly-accepted definition of technical documents, but to many other forms of documents from outside the technical communicator's realm.
Self, Tony. HyperWrite (2007). Articles>Documentation>XML>DITA
#27916
The abbreviation DITA stands for 'Darwin Information Typing Architecture', an information architecture based on XML. DITA is not a mere reinvention of the wheel: rather, it sets the standards for known structuring requirements. The most striking feature of this architecture is the clear orientation towards a technology for structuring, which has already proved its worth in online documentation.
Closs, Sissi. tekom (2006). Articles>Information Design>XML>DITA
#27373
The Darwin Information Typing Architecture (DITA) is an XML-based, end-to-end architecture for authoring, producing, and delivering technical information. This architecture consists of a set of design principles for creating 'information-typed' modules at a topic level and for using that content in delivery modes such as online help, books, and Web sites.
#31171
DITA: From the Perspective of Someone Actually Using It
In this podcast, Marlene Martineau of New Dawn Technologies explains why they adopted DITA, how they adopted it, the benefits they're experiencing, and the reasons why she'll never go back.
Martineau, Marlene. Tech Writer Voices (2008). Articles>Information Design>XML>DITA
#31743
DITA: Opportunities To Help Shape The Standard, Promote DITA Adoption, Develop Real-World Solutions
Want to get involved in the formation of one of the most important XML standards impacting content professionals? You can. And, you should. The folks at OASIS—the Organization for the Advancement of Structured Information Standards—have made it easy for just about anyone to participate.
