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.
Three panellists talk about the challenges of managing an XML publishing and documentation project. After brief introductory remarks from each speaker, there will be a general discussion with the audience about the challenges of XML project management in the publishing world.
This white paper discusses the role of an XML repository into today’s enterprise infrastructure. Virtually every database and repository provide some degree of XML support; however, there are important distinctions between support for XML as a data type and the role of a repository whose architecture and operations are optimized to support the broad family of XML recommendations and standards. Specifically, this white paper will explore: The nature and extent of XML use across the enterprise, cost and quality of service implications of an infrastructure with, and without, an XML repository, the evolution of XML repositories from both a technology and a market segment perspective, criteria to determine when an XML repository would add significant value to an existing infrastructure, and capability and packaging recommendations for XML repository functionality that can be used to evaluate specific offerings.
If you are a technical writer or manager of a documentation group you have probably encountered or been faced with solving problems like: single-sourcing, collaborative authoring, cross-platform editing, multi-channel publishing, improving information quality and consistency, enhancing functionality of electronic output, negating technology lock-in, and even reducing costs without reducing team head count. This article explores how the use of XML technologies within your authoring system can help you achieve each of these objectives.
It is easy to see why the first edition of Michael Young's book won the top award, 'Distinguished Technical Communication,' in the 2000–-2001 International Technical Publications Competition. Young has taken the complex subject of Extensible Markup Language (XML) and written about it in such a way as to make learning about XML an enjoyable experience.
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. 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.
Williams, Kevin, Michael Brundage, Patrick Dengler, Jeff Gabriel, Andy Hoskinson, Michael Kay, Thomas Maxwell, Marcelo Ochoa, Johnny Papa and Mohan Vanman. VBXML (2002). Design>Information Design>XML>Web Design
xml:tm (XML-based Text Memory) is the vendor-neutral open XML standard for embedding text memory directly within an XML document using XML namespace syntax. xml:tm leverages the namespace syntax of XML to embed text memory information within the XML document itself.
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.
This specification provides a model and grammar for representing the structure of information resources used to define topics, and the associations (relationships) between topics. Names, resources, and relationships are said to be characteristics of abstract subjects, which are called topics. Topics have their characteristics within scopes: i.e. the limited contexts within which the names and resources are regarded as their name, resource, and relationship characteristics. One or more interrelated documents employing this grammar is called a 'topic map.'
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.
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.
In this article, gain knowledge about the difference between elements and attributes in XML, as well as differences in character sets. The author shows the benefits and drawbacks of using XML components and why you should carefully consider your character set when developing your software.
XML is a new type of language which has been developed for the web which is different to any other type of scripting or programming language available before. Instead of being concerned with the processing and display of data, XML's primary purpose is to tell the computer what data entered actually means.
In this paper, we consider a way to represent contact center applications as a set of multiple XML documents written in different markups including VoiceXML and CCXML. Applications can comprise a dialog with IVR, call routing and agent scripting functionalities. We also consider ways how such applications can be executed in run-time contact center environment.
XML Schema’s abstract data model consists of components, which are the structures that eventually deﬁne a schema as a whole. XML Schema’s XML syntax, on the other hand, is not a direct representation of the schema components, and it proves to be surprisingly hard to derive a schema’s components from the XML syntax. The Schema Component XML Syntax (SCX) is a representation which attempts to map schema components as faithfully as possible to XML structures. SCX serves as the starting point for applications which need access to schema components and want to do so using standardized and widely available XML technologies.
During the transitional paper–electronic period, a nonprofit STM publisher faces the challenge of publishing a scientific journal in both digital and analog formats while controlling costs and ensuring consistency between electronic and printed representations of an article. This must be achieved, as its sophisticated constituency expects a constantly expanding range of information products and services. In a few short years the American Geophysical Union (AGU) leapfrogged from the paste-up era, when authors prepared their own “camera-ready copy” to be pasted on boards for a printer, to the age of XML, when an article marked up in accordance with a custom-designed DTD serves both as a version of record and a source for generating PDF and HTML article representations. Bibliographic and reference metadata are then extracted from the XML article instance into a relational database, which serves as a basis for generating online and print access mechanisms/products, including various tables of contents and author and subject indices.
This paper discusses approaches to validating XML documents for compliance to constraints. Our particular focus is on structural and content constraints that go beyond what is readily expressible in XML Schema technologies. We provide examples and solutions drawn from our specific experience building an XML-native constraint validator based on a mathematical language called Structural Notation (SN) . SN is used to express operational constraints as machine-processible Rules against a particular category of hierarchically structured, text-oriented military messages, called Message Text Formats (MTFs) , which have been migrated to a corresponding XML-based representation.
XML has dramatically changed the way we exchange and store data, and a new crop of standards promises to change the way we query data. On today's Internet, most data is queried and stored using relational databases, exchanged as XML, and displayed as HTML. For those who need to use XML and databases together, the last five years have been chaotic, creative, interesting, and often frustrating. Every major database vendor has added XML support, but each vendor takes a very different approach, and sometimes changes that approach dramatically from one version to the next. Today, the vendors seem to be lining up behind XQuery and the SQL/XML mappings - is this just the latest wave of marketing hype, or has the industry now found its way?
Yahoo Search Marketing makes extensive use of XML internally, for data exchange and APIs between back-end systems, and externally, as the primary interaction mechanism with third parties via REST and SOAP APIs.
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'm seriously impressed with the possibility of a true breakthrough documentation solution. I'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.
XML stands for eXtensible Markup Language. It is a markup language much like HTML, designed to carry data. Its tags are not predefined. XML is a W3C (World Wide Web Consortium) recommendation. It was created so that richly structured documents could be used over the web. The only viable alternatives, HTML and SGML, are not practical for this purpose. XML, simple and self-descriptive, has shot to fame all around the world in a short span of time. He has for long been a disciple and a keen follower of KISS. XML is modest and is easily available to anyone who wants to seek him out.
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 'doctrine of 'one input â*” many outputs' ... is basically wrong.' 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.