#28070
Service Oriented Architecture (SOA) Made Simple
Even if you're wrapping a legacy application, you'll need a service description that other web services applications can use. Of course, there are many data-binding tools available that are, for example, capable of turning a Java class into an XML Schema or a Windows-compatible wizard with a "generate WSDL" button. But even then, you'll have to give those descriptions to others, the tools may have bugs (surprising, I know, but it's been known to happen), or you'll need to hand-tweak the generated files because a particular customer "just wants the namespace or URL changed." At that point, you don't want to have to burn the midnight oil with a copy of the WSDL and Schema specs in hand and the generated WSDL file on your screen.
Salz, Rich. XML.com (2005). Articles>Information Design>XML
#27285
The fact that many decisions need a combination of information sources makes easy integration of geospatial data an important data usability issue. Our vision is to achieve automated just-in-time integration. As a foundation, we present a system architecture with distributed data and services. Existing and evolving standards and technologies fitting into this architecture are presented along with their scope and shortcomings. A major point is the appropriate definition of data and operation semantics. Further research is needed here to make the automatic formation of service chains for data integration possible.
Riedemann, Catharina and Christian Timm. Data Science Journal (2003). Articles>Information Design>XML>Geography
#29587
Simple Web Syndication with RSS 2.0
Simply put RSS is an XML application for simple web feed syndication and content subscriptions. Let's say you have content on your site that you want to feed, or make available for other sites. This is known as web syndication. Most commonly this takes the form of sharing news headlines, product releases, or some similar timely content. RSS provides a standardized method for web sites to use when creating these feeds.
Dev Articles (2007). Articles>Information Design>XML>RSS
#27722
SOAP is a protocol for exchanging XML-based messages over a computer network, normally using HTTP. SOAP forms the foundation layer of the Web services stack, providing a basic messaging framework that more abstract layers can build on. SOAP can be used to facilitate a Service-Oriented architectural pattern.
Wikipedia (2006). Articles>Information Design>XML>SOAP
#27915
About ten years ago, a handful of highly specialised consultants were trying with missionary zeal to establish SGML as the basic format in technical communication; today, the XML-standard is no longer something that can be dispensed with, and is, in fact, even mandatory in many projects. This article takes a look in hindsight at the beginnings of SGML and XML, and the current developments and standards around XML, and also hazards a guess at what the years to come might hold in store.
Rath, Hans Holger. tekom (2006). Articles>Information Design>Standards>XML
#27914
Standards-Based Publishing with XML, XSLT, XHTML and XSL-FO 
XML, the Extensible Markup Language recommendation by the W3C, separates content from processing. When you author XML, you describe your information semantically using a computer readable and human readable syntax. The syntax of XML is elements and attributes. We call this semantic markup.
Arbury, Autumn. tekom (2005). Articles>Information Design>XML>Semantic
#21499
Strategies in Re-Purposing Graphics for Interactive Intelligent Delivery
In the domain of aerospace/defense, a products life cycle may likely span up to 30 years. The amount of technical data required to manufacture, operate, and maintain those products is immense. The graphic representation of that data facilitates the communication of operational and maintenance instructions. This paper outlines issues with creating, authoring, revising, and delivering intelligence with graphics and the associated meta-data.
Woolsey, Jeremiah and Martin Jackson. XML Europe (2001). Articles>Information Design>XML>Metadata
#19468
Implementing structured authoring with XML allows organizations to create better content. The addition of hierarchy and metadata to content improves reuse and content management. These benefits, however, must be weighed against the time and money required to implement a structured authoring approach. The business case is compelling for larger writing organizations; they will be the first to adopt structured authoring. Over time, improvements in available tools will reduce the cost of implementing structured authoring and make it affordable for smaller organizations.
O'Keefe, Sarah S. Scriptorium (2002). Design>Publishing>Information Design>XML
#28185
Structured Authoring and XML: Part One
Implementing structured authoring with XML allows organizations to create better content. The addition of hierarchy and metadata to content improves reuse and content management. These benefits, however, must be weighed against the time and money required to implement a structured authoring approach. The business case is compelling for larger writing organizations; they will be the first to adopt structured authoring. Over time, improvements in available tools will reduce the cost of implementing structured authoring and make it affordable for smaller organizations.
O'Keefe, Sarah S. Carolina Communique (2003). Articles>Documentation>Information Design>XML
#28177
Structured Authoring and XML: Part Three
Not every content-creation group will benefit from structured authoring and XML. Sometimes, the expense of implementation outweighs the benefits realized, especially in smaller groups with less total page count.
O'Keefe, Sarah S. Carolina Communique (2004). Articles>Documentation>Information Design>XML
#28186
Structured Authoring and XML: Part Two
In a structured authoring environment, authors create documents by assembling elements and text in an order permitted by the structure definition document. You might think of structured authoring as being similar to template-based authoring with a strict template. Authors do not assign formatting; the formatting is automatically assigned based on the structure of the document. Formatting may differ for different output media.
O'Keefe, Sarah S. Carolina Communique (2003). Articles>Documentation>Information Design>XML
#28184
Structuring Your Documents for Maximum Reuse 
A major topic among information development managers these days is single sourcing--writing information once and using it many times. Structured documents are critical for single sourcing. So, let's explore: what we mean by structuring documents; why structuring is useful; some of the concerns that writers have about structuring documents.
Redish, Janice C. 'Ginny'. Center for Information-Development Management (2005). Articles>Content Management>Information Design>XML
#29402
Subsetting and Customizing DITA
This article explores ideas related to subsetting and customizing the DITA specification without the addition of new elements. Instead, we explore taking default rules and adapting them to meet the needs of specific writing and publishing environments. Introductory information about the DITA specification and the difference between subsetting and specialization is provided.
Aschwanden, Bernard. Publishing Smarter (2006). Articles>Information Design>XML>DITA
#21622
A Survey of XML Standards: Part 1
The world of XML is vast and growing, with a huge variety of standards and technologies that interact in complex ways. It can be difficult for beginners to navigate the most important aspects of XML, and for users to keep track of new entries and changes in the space. In this series of articles, Uche Ogbuji provides a guide to XML standards, including a wide range of recommended resources for further information.
Ogbuji, Uche. IBM (2004). Design>Information Design>Standards>XML
#27741
Technical Context and Cultural Consequences of XML
The Extensible Markup Language (XML) is an open standard for creating domain- and industry-specific markup vocabularies. XML has become the predominant mechanism for electronic data interchange between information systems and can be described as a universally applicable, durable “Code of Integration.â€Ω As we celebrate its tenth anniversary, it is appropriate to reflect on the role XML has played and the technical ecosystem in which it functions. In this paper, we discuss both the environment from which XML arose and its technical underpinnings, and we relate these topics to companion papers in this issue of the IBM Systems Journal. We discuss the broad consequences of XML and argue that XML will take its place among the technical standards having the greatest impact on the world in which we live. We conclude with some reflections on the significant technical, economic, and societal consequences that XML is likely to have in the future.
Adler, S., R. Cochrane, J.F. Morar and A. Spector. IBM (2006). Articles>Information Design>XML
#25978
Topic-Oriented Information Development and Its Role in Globalization
For all of its upside, XML-based single-source publishing has proven to be expensive and complicated to implement. XML-based single sourcing requires significant tool development, data conversion, and system integration prior to realizing the benefits of repurposing and reuse. To mitigate this, some vertical industries have developed their own XML tag sets. While successful on their own, these vertical industry efforts have not been extensible to other industries. A new XML-based approach to information development is the Darwin Information Typing Architecture (DITA).
Trippe, Bill. Gilbane Report (2004). Articles>Information Design>Metadata>XML
#18715
An informative web site about Topic Maps.
Biezunski, Michel and Steven R. Newcomb. TopicMaps. Resources>Information Design>XML
#18714
Topicmaps.Org is an independent consortium of parties interested in developing the applicability of the Topic Maps Paradigm to the World Wide Web, by leveraging the XML family of specifications as required.
TopicMaps (2002). Resources>Information Design>XML
#27078
Transforming Documentation from the XML Doctypes Used for the Apache Website to DITA: A Case Study
A primary factor behind the enormous interest in XML is the support it provides for transforming documents to meet the needs of information-processing applications as well as human readers working with HTML, print, and other presentation media. This case study reviews the issues we confronted, the tools we implemented, and the procedures we adopted to transform a documentation set from one XML document type to another, and from XML to HTML and Adobe PDF. The documentation set for Xalan, the Apache XSL transformer based largely on code donated by Lotus/IBM, is written in XML, using document types shared by the projects on the Apache XML website. To present Xalan reference releases to IBM project groups, the Cambridge Advanced Technology Group has set up build procedures to transform the Xalan XML documentation to DITA, an extensible XML information typing architecture currently under development in IBM. After verifying that the DITA output conforms to its declared document type, the build publishes the DITA documentation set as HTML and as PDF.
Leslie, Donald M. Cover Pages (2004). Articles>Information Design>XML>DITA
#21642
Extensible Stylesheet Language (XSL) is a language designed to provide presentation for the content of XML documents. It is composed of three parts: XSLT, XPath, and XSL Formatting Objects (XSL-FO). In this chapter, I'll show you XSLT and the .NET assembly that deals with it, System.Xml.Xsl. But first, some background.
Bornstein, Niel M. O'Reilly and Associates (2003). Design>Information Design>XML>XSL
#14678
Houser explores the growing popularity of XML and compares several current XML authoring tools. A sidebar to the article explains the World Wide Web Consortium's (W3C) standards process.
Houser, Alan R. Intercom (2001). Design>Information Design>XML
#27615
UML 3.0 and the Future of Modeling
The major revision work for UML 2.0 is complete, and it is now an OMG Final Adopted Specification. This is a good time to reflect on UML's future, and the future of model-driven development.
Kobryn, Cris. UML Forum (2004). Articles>Information Design>XML>UML
#21607
This document covers key areas in UML (the Unified Modeling Language), such as Association, Multiplicity, Aggregation, Generalization and diagrams such as the Use Case diagram, Class Diagram, and Sequence Diagram.
Sundaram, Elango. Yahoo (2003). (Farsi) Articles>Information Design>XML>UML
#27583
UML is the way the world models not only application structure, behavior, and architecture, but also business process and data structure.
UML Resource Page (1996). Resources>Information Design>XML>UML
#21624
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.
Chase, Nicholas. IBM (2003). Design>Web Design>Information Design>XML
