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.
Houser describes several options for organizations interested in data-oriented publishing--the delivery of discrete, independent pieces of information that can be selected, manipulated, and presented to meet the needs of different audiences with different characteristics and different goals.
This paper discusses the rationale and design behind Jeppesen’s single-source publishing system. With the business needs to single-source publishing capabilities becoming more acute, Jeppesen partnered with Astoria Software to develop a solution. The result is a system based on commercial-off-the-shelf software, XML industry standards, and open-source tools.
XML is becoming the data format of choice for a wide variety of information systems solutions. Common applications using XML include document transmission in B2B systems, message format construction for integration of Internet applications with legacy systems, binding of XML data to visual and non-visual controls, data storage and retrieval, and various data manipulation activities within applications.
LexisNexis, global provider of legal, news, and business information, has migrated the content of its non-US business units to a single product delivery platform. This paper provides an overview of how this was enabled using XML.
A Service-Oriented Architecture (SOA) typically exports a range of services. For XML service modelling and subsequent consumption of those services by users (people, machines, or other services), Java technology provides powerful mechanisms to handle XML data, which in turn provides a key foundation for using SOA concepts. Dive into the practical aspects of SOA using XML and Java technology, and discover clear examples of why this seemingly complex technology is so popular.
This chapter explores the various methods for mapping between XML and relational data models. It focuses on the underlying fundamentals: goals and requirements for mapping between XML and relational data; issues that arise when mapping, such as handling of datatypes and order; and when a particular technique can or cannot support update operations.
As XML becomes ubiquitous so the need for powerful tools to manipulate XML data becomes more pressing. Merging XML is particularly tricky, but often necessary to consolidate data feeds from heterogeneous systems, or to synchronize submissions of XML fragments which make up a larger document. An automated mechanism for defining and controlling such merges has been developed and is demonstrated to provide a consistent, adaptable and resilient solution to this problem. Integration into an information pipeline allows limitless customization.
Information about objects on subjects - metadata describes objects. Purposes: Information management and discovery. Metadata enables content to be retreived, tracked, and assembled automatically.
So you have heard about microformats, read the introductory articles, and even bought the book. But now you are probably thinking "great - I have done my part to make the web a better place by adding microformats; what's next? What can people do with my data besides add it to their address book or calendar?" 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.
This session will provide a technical description of the new Microsoft Office Open XML formats that will become the default XML based formats of the coming version of Microsoft Office (Office 12). The Microsoft Office XML formats provides a great Open and standard-based XML format for Office Documents that enables new XML document scenarios that were not possible before.
As the Internet world shifts its focus to XML and related technologies, what happens to HTML? Everywhere you go, products are becoming 'XMLitized' 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.
The Darwin Information Typing Architecture (DITA) has emerged as a standard topic-oriented document architecture. DITA holds many advantages over information authored directly in HTML, including better reuse, easily changed presentation styles, and easy single sourcing. This article, the first of two parts, explains how to get a quick start with DITA using HTML topics that are already available. It shows you how to use the provided XSLT transform to do the migration, and examines what is needed to ensure quality results.
Two years ago we began the process of upgrading our content management system. Part of this upgrade required our data to be migrated from an Informix database to an Oracle database. This presented us with the opportunity to convert our data from SGML to XML. This presentation will focus on three areas: analysis/preparation for migration, migration of the data and lessons learned.
The high integration costs which exist today mean that we must automate interface maintenance and integration tasks or go insane, or worse, out of business. Ongoing pressure to reduce software development costs while increasing the quality and completeness of the work provide an opportunity for the use of model driven computing. MDA (Model Driven Architecture) is a technique for model based platform independent software specification based on the MOF (Meta-Object Facility) and XMI (XML Meta-data Interchange) standards from the OMG (Object Management Group). There are a number of tool vendors using XMI (especially UML (Unified Modeling Language) drawing tools) but common use and value seem to be slow to show themselves.
This talk describes a new approach to rapid application development using patterns, frameworks and modeling languages based on XML. It explains why earlier model driven paradigms failed, and shares insights from commercial tool development experiences. Then, it shows how models based on XML are being used to automate large parts of the software development life cycle.
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.
DITA (Darwin Information Typing Architecture) is an XML-based information architecture. DITA doesn’t reinvent the wheel – rather, it sets standards for known structuring requirements. One very attractive aspect of this architecture is its clear alignment to a structuring method that has proved itself for years in online documentation. The basis of this method is the division of the content into modules called TOPICS. Today, this structuring method is considered the ideal approach for the organisation of comprehensive contents. As with everything new, there are many questions about DITA.
DITA enters a new phase this year with version 1.2. We'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.
Compilation of the Digital Dictionary of Buddhism (DDB) began with the realization of the dearth of adequate lexicographical and other reference works in the English language for the textual scholar of East Asian Buddhism in particular, and East Asian philosophy and religion in general. The (Chinese, Japanese, Korean) CJK-English Dictionary (CJK-E) began soon after. I decided, during my first Buddhist and Confucian/Taoist texts readings courses, to save everything I looked up, and have continued that practice to the present, through the course of studying scores of classical texts. Although the content of these two lexicons is presently being supplemented by other interested parties, the terms that I have been compiling serve as the major portion of the work.