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.
Gets you started with DocBook, an SGML/XML dialect that describes the content of technical articles and other documents. David discusses the benefits of using DocBook, and then describes how to plan and modularize a large document conversion project.
Since 2005 the German National Library of Science and Technology (TIB) is established as a DOI registration agency for scientific content. Data providers transmit XML-files containing the DC-based metadata descriptions of the scientific data to a webservice infrastructure at the TIB, which was created by the Research center L3S during a project founded by the registration agency for scientific content. Data providers transmit XML-files containing the DC-based metadata descriptions of the scientific data to a webservice infrastructure at the TIB, which was created by the Research center L3S during a project founded by the German research association (DFG). This webservice infrastructure is based on the web application framework COCOON. We have however extended COCOON with full webservice functionalities. Using XSLT the webservice is furthermore able to transform XML-metadata files into well-formed PICA-files to insert the metadata information into the library catalogue of the TIB.
It’s hard to go to a content management or publishing technology conference these days without there being a presentation on DITA — the Darwinian Information Typing Architecture. For the uninitiated, DITA is an XML architecture for authoring and publishing topic-based content, typically technical documentation. The brainchild of IBM, where it is used internally for many documentation projects, DITA is now an open-source standard under the aegis of OASIS.
Greymatter is an excellent web content management system. After you install it, you can begin to syndicate your content using XML. This article gives you an explicit step-by-step overview of how I created RSS 1.0 and RSS 0.92 files using Greymatter. It is assumed that you have some knowledge of HTML and XML, and that you have already installed Greymatter. Many examples and references are provided to help you along the way.
If you are using any word processor or editor in a group situation, such as a technical writing team, or an office, then it will probably be in your interest to set up templates for authors to use to ensure consistency, reduce effort, and help automate conversation of documents between formats, such as building web pages from office documents. If you are also trying to store and manipulate content in XML but want to use a word processing environment for authoring, then well-crafted templates are even more important.
XML can simplify production of documents for print, help and web delivery. It can make document components reusable, portable between platforms and easier to maintain. XML also has a dark side. Parts of the standard are turbulent, vendors are rushing XML products to market that are not fully standard-compliant, implementation requires careful planning, and porting of legacy documents to XML is not trivial. Technical communicators can prosper by identifying the parts of XML that can be implemented immediately, by preparing documents to exploit support for XML available in new versions of Microsoft Word and Adobe FrameMaker, and by using hybrid HTML/XML for document delivery.
Some feeds are only skim worthy, while others I read word-for-word. Still, 90 feeds is really more than I can realistically keep up with. The question of which feeds to unsubscribe from plagues me. How long does one subscribe to a feed before deciding it's not worthwhile?
In the evolving and demanding world of telecommunications, Tellabs supports telecom service providers with the design, development, and deployment of wireline, wireless , and cable solutions worldwide. But with each unique solution deployment requires knowledge transfer from engineers to field service staff to ensure a smooth system upgrade. Learn how Tellabs' New Product Introduction group used DITA to transition to customer-centric writing. *What are the key things the organization as a whole should keep in mind regarding processes?"
How can you create an RSS for a specific HTML page, especially if the page-create software or web host doesn't provide an automated method. This article discusses how to use a screen scraper to quickly and easily create a RSS feed for any HTML page.
This tutorial uses the DITA Open Toolkit 220.127.116.11 and the corresponding PDF plugin release, and Wrycan's demo text. This assumes you have a working DITA environment and can run the default formatting with PDF plugin.
XML, a way of tagging and structuring your content, can help solve a number of problems, including storing, mining, reusing, and sharing content. XML helps enable the interoperability of information between systems, allowing you to export and import your content from one application to another. XML is behind much of the collaboration and information sharing Web 2.0 technologies, such as RSS (really simple syndication) and blogs. By storing content in XML, technical writers can ensure greater flexibility among technologies for authoring and publishing their content.
Cisco relies on Elearning for much of its training. So much so, that Cisco has become one of the largest Elearning providers in the world. In fact, Cisco provides over 120 courses in 152 different countries around the world. The courses and related assessments are often subject to frequent change, and the content must be produced in multiple languages or formats, combined into different courses, or efficiently searched and retrieved from large volumes of similar material. Early on, they realized that in order to keep that content current and manageable it was important to build an architecture that scaled well and was easy to maintain.XML became a clear choice for the data format. Cisco’s RLO (Reusable Learning Object) data model provides for flexible data modules that can be reused in many different contexts and driven to many different formats.
With XML, the flow of information and documents around the world has never been greater - with its robust and flexible format that enables sharing of data stored in multiple formats. As a result, XML is shrinking the global marketplace and opening doors to new markets that had previously been hindered by compatibility issues. The last and arguably most important mile in reaching new markets, however, is often in localizing or tailoring communications to fit the particular audience, whether by translating languages to ensuring sensitivity to local nuances and culture.
IDC, a global information technology market research firm, identified a couple of trends related to and influencing dynamic publishing. These include the growth in internet users (and where they get their content), and where organizations will publish content over the next two years.
It is unclear how adoption of Web services contracting systems based on XML standards will affect the frequency of litigated contract disputes among businesses. During the more than 20 years that business-to-business EDI contracting systems have been in use, there have been no reported cases of litigated contract disputes involving EDI contracts. By contrast, there have been many litigated disputes involving business-to-consumer contracts formed through the use of clickwrap and browsewrap Internet interfaces that have been in use for only a decade. B2B EDI contracts are usually formed between businesses that are already in a long-term trading partner relationship, and the high initial investment required to use EDI may provide additional incentives to resolve disputes informally. Businesses without long-term relationships should be able to use B2B XML contract technologies, and the absence of a relationship of trust may make it more difficult to resolve disputes informally when they arise. B2B XML contracts should still have a lower rate of litigation than B2C Internet contracts, however, because most businesses prefer arbitration to litigation.
The focus of this paper and the presentation will be to discuss how XML has changed and improved the legislative and regulatory document creation and management processes for agencies of the federal government. During the presentation, we will briefly describe the evolution of XML adaptation in the Legislative Branch agencies. A more in depth discussion can be found at xml.house.gov.