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.
Sharing XML documents during the writing and review process is a missing link in the XML publication chain. While Office or PDF applications help, they also add another extra-layer of complexity and lose the 'XML awareness' of our initial document. That's where LiveTechDocs comes into play.
Looking through my Programs folder, I see many programs I use to work with XML documentation. Which one is my favorite? Well, that depends on the size of my project, the size of my budget, and the file I am working on.
While technical documentation has traditionally been the domain for structured authoring, there is increasing interest in using XML for more “creative” materials such as sales brochures and marketing collateral. Such pre-sales materials often have even more compelling opportunities for single-sourcing and reuse than technical documents. Up to now, these materials have been produced one at a time in page-oriented publishing systems like Adobe InDesign and Quark. While this provides maximum flexibility in controlling exact page layouts, it can create a nightmare when small changes must be replicated across all the independent pages and documents. Why can’t we use XML to more flexibly handle this kind of content? In fact, we can! Using page formats from real marketing content, this whitepaper demonstrates how XML tools can be used to maintain highly graphical sales collateral, web pages, and product catalogs from a single source of XML information.
XML is the acronym for the extensible markup language. According to the W3C, it is 'the universal format for structured documents and data on the Web'. The following list explains what XML is and what it is not.
Pharmaceutical and biotechnology companies are required by law to compile and maintain over a multi-year life-cycle, large and complex collections of documents for submission to national regulatory agencies in order to obtain and sustain marketing approval for drugs and biologically active substances. The content includes both data and textual narrative, and is of great value in terms of intellectual property and legal liability. Over the past few years a cooperative effort between the regulators and industry has developed XML-based standards for electronic submission.
A recent survey of XML implementations found that many United States Air Force (USAF) communities are incorporating XML as a foundational step in their migration to a net-centric vision. Although the survey was limited to publicly available resources –and thus only a partial view of total USAF efforts – thoughtful analysis of the survey results nonetheless reveals both strengths and weaknesses in the approaches inspected. In this paper we summarize the survey results and what they imply for how the USAF is progressing towards net-centricity. We note potential positive impacts XML technologies could have on USAF business practices, and some potential shortfalls.
The pharmaceutical industry has been slow to adopt XML until recently. Initiatives in the US and EU, as well as other jurisdictions, have begun that use XML to define important documentation formats as part of the drug product life cycle. In the US the FDA is mandating that drug product descriptions called "labels" be submitted in an XML format called the Standard Product Label (SPL) language by the end of 2005 and similar mandates are being made in the EU and other regions. Since most pharmaceutical companies are international, companies are scrambling to figure out the best method for managing their data in order to meet all of meeting these specific requirements. Also, drug label information will become an important component in the broader set of medical records and prescription standards that are being developed concurrently. This session will describe the roles and status of these standards, initiatives for adoption in the US and the EU, and provide some ideas on strategies for managing data within this complex set of requirements.
Maybe XML is more like a carcinogen. We don't notice it's there, but we're still getting exposed to it. In ever-increasing doses. But unlike a carcinogen, XML is not bad for our health; in fact, it has many life-enhancing properties. Well, work-enhancing properties.
The discussion will share advancements in the areas of digital capture, storage, management, access and output. It will review the significant benefits and cultural implications with the digitization of information, focusing on software and storage solutions creating easy access and search capability for scanned information. A demonstration and review of the automatic bookscanning process relating to the use of XML will share how modifications can be made to a pre-existing XML file.
This chapter focuses on the details of XML markup. It will describe the fundamental building blocks of all XML-derived languages: elements, attributes, entities, processing instructions, and more. And I'll show you how they all fit together to make a well-formed XML document. Mastering these concepts is essential to understanding every other topic in the book, so read this chapter carefully.
This session will provide base line information on how native XML customer-defined schema support in Office applications is enabling XML based eGovernment interests from Europe, Asia, South and North America. Concrete and deployed examples will be shared to spark a new but real perspective on leveraging popular and user-friendly desktop applications to become, via XML and Web Services, the front-end to Government back-end systems. In short, real and effective solutions to enabling eGov Services in Government to Citizens, Government to Businesses and Government to Government scenarios.
This presentation is a 90 minute session. It will cover many areas of XML and XML technologies. It has been constructed to provide the audience a broad understanding of XML and XML technologies in a short amount of time. The presentation is geared to ensure that new XML users can obtain the maximum benefit from other sessions presented at XML 2004. The attendees will gain an understanding of XML jargon and acronyms used in XML technologies, as well.
Microsoft breathed new life into legacy office documents by opening an XML window (Office Open XML) to its office products through its royalty-free XPS specification. XPS stands for XML Paper Specification that specifies cross-platform, open standard, document representation that can be used for generating, sharing, printing and archiving of paginated documents. Its virtues in Microsoft's own words are, "With XPS, documents print better, can be shared easier, be archived with confidence, and are more secure."
Pipeline processing is a powerful programming technique that can lead to programs that are easier to maintain and enhance and monolithic imperative programs. Developers familiar with the power of pipeline operations central to the UNIX operating system know how simple, modular tools can be chained together to accomplish a wide variety of complex tasks. XSLT pipelines offer the same advantage for XML transformation. Where UNIX pipelines are based around standard input and output of lines of text, XSLT pipelines rely on the structure of well-formed XML between stages. The panel members will demonstrate the value of a pipeline processing approach and discuss implementation specifics.
XML Pocket Consultant is the latest in Microsoft Press's Pocket Consultant series. Other books in the series include guides to server administration developed for IT professionals. Stanek explains in his introduction that XML pocket consultant is aimed at a wider audience, namely 'developers creating XML-based solutions, administrators who support XML-based solutions and technologists working with XML.'