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.
Metadata has taken on a new look with the advent of XML and digital resources. XML provides a new versatile structure for tagging and packaging metadata as the rapid proliferation of digital resources demands both rapidly produced descriptive data and the encoding of more types of metadata. Two emerging standards are attempting to harness these developments for library needs. The first is the Metadata Object and Description Schema (MODS), a MARC-compatible XML schema for encoding descriptive data. The second standard is the Metadata Encoding and Transmission Standard (METS), a highly flexible XML schema for packaging the descriptive metadata and various other important types of metadata needed to assure the use and preservation of digital resources.
Extensible Markup Language, or XML, provides a way to mark up content that adds information about its purpose. With the information stored using XML, an application known as a parser can reliably extract the relevant information and process it accordingly for multiple situations.
This paper is based from a number of real-world XML validation projects, and compares and contrasts the experience 'in the trenches' with the current state of the art in XML validation standards. Validation is a topic of some controversy in the XML community. While there has been movement from the basic validation offered by XML 1.0 DTD's, there is little consensus on whether that movement has been in the right direction.
How do you simplify the message you want to broadcast to the world without losing its meaning? For established players it's so much easier because they can get in front of their customers. They can run seminars or publish White Papers that will most likely reach an audience. Or they may gain interest from independent technical consultants to whom users will listen.
XML is now acknowledged as the best format for authoring technical documentation. Its wide support, extensible nature, separation of form and content, and ability to publish in a wide variety of output formats such as PDF, HTML, and RTF make it a natural choice. XML, thanks to its extensible nature and rigorous syntax, has also spawned many standards that allow the exchange of information between different systems and organizations, as well as new ways of organizing, transforming, and reusing existing assets. For publishing and translation, this has created a new way of using and exploiting existing documentation assets, known as Open Architecture for XML Authoring and Localization (OAXAL).
The OpenDocument Format ("ODF") shows promise for bringing the eXtensible Markup Language (XML) to the common desktop PC of the future as the native file format for office documents in the next-generation office suites including OpenOffice, StarOffice, KOffice, Workplace, Writely and others. An ODF Plugin for MS Office -- currently under development by the OpenDocument Foundation -- can deliver this promise to the 450 million legacy Windows desktop PCs already in place. Sam Hiser, an officer of the OpenDocument Foundation, will discuss the origins and design objectives of the Foundation's ODF Plugin. He will also discuss the strategic goals of the Foundation's ODF Plugin while showing how the Plugin effort is already influencing the development of the ODF standard itself at OASIS. An audience of general business people and software developers will leave Hiser's presentation with a clear understanding of the ODF Plugin, its context of relevance and development, and how it can alter the landscape for XML.
During the past twenty years, a huge number of custom languages - at least hundreds, perhaps a couple of thousand - have been attempted. Almost all have been miserable failures. That is to say, the vast majority have failed to achieve wide adoption, and those that were adopted have often failed to achieve their goals, whether of reducing costs, enriching applications, or both.
Enterprises looking to fast track their content strategy and minimize the risks of a big-bang initiative are choosing DITA–one of the most popular information models to suit today’s content–rich, multi-channel environment.
This month I'm taking a break from covering XSLT 2.0 to describe how the combination of XSLT 1.0 and an application with an open XML format solved a problem for me. I solved this problem so quickly and easily that it got me thinking about how the combination of XSLT 1.0 and the increasing amount of open XML formats are opening up a world of simple, valuable new applications and utilities for us to write.
All OpenOffice.org applications use XML-based file formats. All applications (except Math) use the same format as defined in the specification. The Math component uses the package structure and format, but uses MathML inside the package.
The OpenOffice.org XML project is the home of of XML related features of OpenOffice.org, like its OASIS OpenDocument/ISO/IEC 26300 file format implementation. It further provides some XML base implementations, like XML parser and printer components.
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.
During a recent development effort, one of our clients was alarmed at the conversion costs of the proposed XML-based content management system compared to the existing MS Word-based process. This was just one instance of an alarming trend of balking at XML-based systems in favor of using public web folders, indexed by some full-text search engine, as part of a local intranet. In the short run, these edit, drop, and index solutions have some appealing features, including low development and conversion costs. But they are short-lived systems that either wither from lack of functionality or rapidly outgrow their design.
Most people are risk-averse, and profound changes such as the move to structured authoring require new skills and workflows. To ensure a successful transition, XML implementers need to assess their team members, identify allies, and build their implementation strategy around the staff members who embrace change.
The move toward XML-based authoring in technical publications is a classic paradigm shift. It requires content creators to change their writing process and learn new concepts.
Covers XPath's new ability to do some things that every real programming language can do: conditional statements and iteration, or, as they're more colloquially known, "if" statements and "for" loops. We'll also look at a useful related technique for checking whether certain conditions do or don't exist in a set of nodes.
The transition in a markup-based publishing environment from SGML- to XML-based tools and procedures can sometimes be complex. This session details Cessna Aircraft Company's implementation as it moves from an SGML environment to an XML enviroment.
XML [EXtensible Markup Language] is what its name suggests: a markup language, much like HTML. In fact, XML and HTML are siblings (if you want to think of it that way) in that they are both derivatives of SGML, or “Standard Generalized Markup Language”. XML is not a programming language (neither is HTML for that matter).
In 1998 the industry got behind a common vision of interoperability for systems and data using XML. The web (HTTP/HTML) connected millions of users to each other as well by presenting information they needed - both at work and from home. The next logical step is to connect systems together and break down the stove pipes of information and business logic that exist to unleash an entirely new wave of productivity gains. In this talk I will trace the march of computing that has led to incredible productivity gains over several decades; draw parallels to the invention of electrical generation facilities and the subsequent building of the electric grid that provided power for all to harness and call out the challenges that still lie ahead of us.
Many governments are moving to using XML for drafting and publishing legislation. SAIC has worked with a number of jurisdictions to facilitate the automation of legislative drafting and publication processes using XML.