| |||||||||
|
101. #19468 Implementing structured authoring with XML allows organizations to create better content. The addition of hierarchy and metadata to content improves reuse and content management. These benefits, however, must be weighed against the time and money required to implement a structured authoring approach. The business case is compelling for larger writing organizations; they will be the first to adopt structured authoring. Over time, improvements in available tools will reduce the cost of implementing structured authoring and make it affordable for smaller organizations. O'Keefe, Sarah S. Scriptorium (2002). Design>Publishing>Information Design>XML 102. #28185 Structured Authoring and XML: Part One Implementing structured authoring with XML allows organizations to create better content. The addition of hierarchy and metadata to content improves reuse and content management. These benefits, however, must be weighed against the time and money required to implement a structured authoring approach. The business case is compelling for larger writing organizations; they will be the first to adopt structured authoring. Over time, improvements in available tools will reduce the cost of implementing structured authoring and make it affordable for smaller organizations. O'Keefe, Sarah S. Carolina Communique (2003). Articles>Documentation>Information Design>XML 103. #28177 Structured Authoring and XML: Part Three Not every content-creation group will benefit from structured authoring and XML. Sometimes, the expense of implementation outweighs the benefits realized, especially in smaller groups with less total page count. O'Keefe, Sarah S. Carolina Communique (2004). Articles>Documentation>Information Design>XML 104. #28186 Structured Authoring and XML: Part Two In a structured authoring environment, authors create documents by assembling elements and text in an order permitted by the structure definition document. You might think of structured authoring as being similar to template-based authoring with a strict template. Authors do not assign formatting; the formatting is automatically assigned based on the structure of the document. Formatting may differ for different output media. O'Keefe, Sarah S. Carolina Communique (2003). Articles>Documentation>Information Design>XML 105. #28184 Structuring Your Documents for Maximum Reuse A major topic among information development managers these days is single sourcing--writing information once and using it many times. Structured documents are critical for single sourcing. So, let's explore: what we mean by structuring documents; why structuring is useful; some of the concerns that writers have about structuring documents. Redish, Janice C. 'Ginny'. Center for Information-Development Management (2005). Articles>Content Management>Information Design>XML 106. #29402 Subsetting and Customizing DITA This article explores ideas related to subsetting and customizing the DITA specification without the addition of new elements. Instead, we explore taking default rules and adapting them to meet the needs of specific writing and publishing environments. Introductory information about the DITA specification and the difference between subsetting and specialization is provided. Aschwanden, Bernard. Publishing Smarter (2006). Articles>Information Design>XML>DITA 107. #21622 A Survey of XML Standards: Part 1 The world of XML is vast and growing, with a huge variety of standards and technologies that interact in complex ways. It can be difficult for beginners to navigate the most important aspects of XML, and for users to keep track of new entries and changes in the space. In this series of articles, Uche Ogbuji provides a guide to XML standards, including a wide range of recommended resources for further information. Ogbuji, Uche. IBM (2004). Design>Information Design>Standards>XML 108. #27741 Technical Context and Cultural Consequences of XML The Extensible Markup Language (XML) is an open standard for creating domain- and industry-specific markup vocabularies. XML has become the predominant mechanism for electronic data interchange between information systems and can be described as a universally applicable, durable “Code of Integration.â€Ω As we celebrate its tenth anniversary, it is appropriate to reflect on the role XML has played and the technical ecosystem in which it functions. In this paper, we discuss both the environment from which XML arose and its technical underpinnings, and we relate these topics to companion papers in this issue of the IBM Systems Journal. We discuss the broad consequences of XML and argue that XML will take its place among the technical standards having the greatest impact on the world in which we live. We conclude with some reflections on the significant technical, economic, and societal consequences that XML is likely to have in the future. Adler, S., R. Cochrane, J.F. Morar and A. Spector. IBM (2006). Articles>Information Design>XML 109. #25978 Topic-Oriented Information Development and Its Role in Globalization For all of its upside, XML-based single-source publishing has proven to be expensive and complicated to implement. XML-based single sourcing requires significant tool development, data conversion, and system integration prior to realizing the benefits of repurposing and reuse. To mitigate this, some vertical industries have developed their own XML tag sets. While successful on their own, these vertical industry efforts have not been extensible to other industries. A new XML-based approach to information development is the Darwin Information Typing Architecture (DITA). Trippe, Bill. Gilbane Report (2004). Articles>Information Design>Metadata>XML 110. #18715 An informative web site about Topic Maps. Biezunski, Michel and Steven R. Newcomb. TopicMaps. Resources>Information Design>XML 111. #18714 Topicmaps.Org is an independent consortium of parties interested in developing the applicability of the Topic Maps Paradigm to the World Wide Web, by leveraging the XML family of specifications as required. TopicMaps (2002). Resources>Information Design>XML 112. #27078 Transforming Documentation from the XML Doctypes Used for the Apache Website to DITA: A Case Study A primary factor behind the enormous interest in XML is the support it provides for transforming documents to meet the needs of information-processing applications as well as human readers working with HTML, print, and other presentation media. This case study reviews the issues we confronted, the tools we implemented, and the procedures we adopted to transform a documentation set from one XML document type to another, and from XML to HTML and Adobe PDF. The documentation set for Xalan, the Apache XSL transformer based largely on code donated by Lotus/IBM, is written in XML, using document types shared by the projects on the Apache XML website. To present Xalan reference releases to IBM project groups, the Cambridge Advanced Technology Group has set up build procedures to transform the Xalan XML documentation to DITA, an extensible XML information typing architecture currently under development in IBM. After verifying that the DITA output conforms to its declared document type, the build publishes the DITA documentation set as HTML and as PDF. Leslie, Donald M. Cover Pages (2004). Articles>Information Design>XML>DITA 113. #21642 Extensible Stylesheet Language (XSL) is a language designed to provide presentation for the content of XML documents. It is composed of three parts: XSLT, XPath, and XSL Formatting Objects (XSL-FO). In this chapter, I'll show you XSLT and the .NET assembly that deals with it, System.Xml.Xsl. But first, some background. Bornstein, Niel M. O'Reilly and Associates (2003). Design>Information Design>XML>XSL 114. #14678 Houser explores the growing popularity of XML and compares several current XML authoring tools. A sidebar to the article explains the World Wide Web Consortium's (W3C) standards process. Houser, Alan R. Intercom (2001). Design>Information Design>XML 115. #27615 UML 3.0 and the Future of Modeling The major revision work for UML 2.0 is complete, and it is now an OMG Final Adopted Specification. This is a good time to reflect on UML's future, and the future of model-driven development. Kobryn, Cris. UML Forum (2004). Articles>Information Design>XML>UML 116. #21607 Sundaram, Elango. Yahoo (2003). (Farsi) Articles>Information Design>XML>UML 117. #27583 UML is the way the world models not only application structure, behavior, and architecture, but also business process and data structure. UML Resource Page (1996). Resources>Information Design>XML>UML 118. #21624 Even before there was XML, there was the Document Object Model, or DOM. It allows a developer to refer to, retrieve, and change items within an XML structure, and is essential to working with XML. In this tutorial, you will learn about the structure of a DOM document. You will also learn how to use Java technology to create a Document from an XML file, make changes to it, and retrieve the output. Chase, Nicholas. IBM (2003). Design>Web Design>Information Design>XML 119. #27033 Unravel the OpenOffice File Format OpenOffice provides a suite of applications whose native file format consists of a set of XML files, compressed into a ZIP archive. This article explores the basics of the OpenOffice file format. O'Reilly and Associates (2004). Articles>Information Design>XML>OpenOffice 120. #27744 With XForms technology, you can provide a lightweight editor for an existing collection of XForms. Explore an approach to form authoring for simple, quick changes that improve the effectiveness of data collected. Typical form editing requires a separate application even for the most trivial changes. XForms manipulates XML data and submits it to a server, making it an ideal choice to author these trivial changes and submit them for redeployment. Speicher, Steve K., Jan J. Kratky and Kevin E. Kelly. IBM (2006). Articles>Information Design>XML 121. #27034 Use Character and Entity References Not all characters are available on the keyboard! This hack shows you how to represent such characters in an XML document by using decimal and hexadecimal character references, and how to represent entities by using entity references. O'Reilly and Associates (2005). Articles>Information Design>XML 122. #26890 Use Data URIs to Include Media in XML There are many ways to link to non-XML content within XML, including binary content. Sometimes you need to roll all such external content directly into the XML. Data scheme URIs are one way to specify a full resource within a URI, which you can then use in XML constructs. In this tip, Uche Ogbuji shows how to use this to bundle related media into a single file. Ogbuji, Uche. IBM (2006). Articles>Information Design>Multimedia>XML 123. #21620 Use Language-Specific Tools for XML Processing DOM and SAX are the two best known systems for XML processing, but they are really compromises across programming languages. As such, they do not take advantage of any language's particular strengths. Often it is better to duck conventional wisdom and use special APIs that take advantage of particular strengths. Ogbuji, Uche. IBM (2004). Design>Information Design>XML 124. #29960 Use PHP to create XForms, Part 1: Creating a PHP XForms library This two-part article series is designed to get PHP developers up to speed in leveraging Web 2.0 XForms forms for their PHP forms development so that they can finally put their outdated Web 1.0 HTML forms away. This will be accomplished by creating a library of functions that generate XForms elements when called upon. In this article, Part 1 of a two-part series, developers will create the XForms library using PHP, allowing each function to take in parameters and output XForm elements. Anderson, Tyler. IBM (2007). Articles>Information Design>XML>XSL 125. #29959 Use PHP to create XForms, Part 2: Using the PHP XForms Library to Create Useful XForms This two-part article seriess is designed to get PHP developers up to speed in leveraging Web 2.0 XForms forms for their PHP forms development so that they can finally put their outdated Web 1.0 HTML forms away. In Part 1, you created the PHP XForms library. In this article, Part 2, you will enhance the library to include some error checking and convenience functions to help make using the library more manageable, and lastly you'll demo the library by creating a proof of concept XForm. Anderson, Tyler. IBM (2007). Articles>Information Design>XML>XSL
| |||||||||
| |||||||||
Click here to learn how to embed the RSS feed of this category in your website.