#14748
Wiles examines the challenges of implementing Extensible Markup Language (XML).
Wiles, Debbie. Intercom (2002). Design>Information Design>XML
#25981
XML Repositories: An Idea Whose Time has Finally Come
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.
Holst, Sebastian. Gilbane Report (2004). Articles>Content Management>Information Design>XML
#18826
XML Structures for Existing Databases
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
#27087
XML is 'extensible markup language' and SGML is 'standard generalized markup language' is somewhat 'related' to XML and HTML.
Bright Path Solutions (2006). Resources>Information Design>XML
#19113
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.'
TopicMaps (2001). Resources>Information Design>XML>Sitemaps
#21627
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.
Ogbuji, Uche. IBM (2003). Design>Web Design>Information Design>XML
#27953
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.
Youssef, Michael. ASP Free (2004). Articles>Information Design>XML>ASP
#27859
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.
Gowans, David. Free Webmaster Help (2001). Design>Information Design>XML
#20389
In this XML tutorial you will learn what XML is and the difference between XML and HTML. You will also learn how to start using XML in your applications.
#27082
So, your company has decided to implement XML. You are tasked with figuring out exactly how, when, and why. For starters, you should find out what XML is and what you can do with it. This tutorial serves to explain the basics of XML documents. Once you understand what they are, it can help you know the how, when, and why. XML fits into a lot of places. It can replace, or work with, other technologies. It can be used instead of, or to supplement, scripts. It can work with databases, or on its own to store readable content. Before you dive into what XML might do, it can help if you learn a little more about it.
Bright Path Solutions (2005). Articles>Information Design>XML
#25039
XML: The Answer to Everything?
This article weighs the pros and cons of XML for some applications (publishing), and explores why it is the best possible solution for many programming and publishing needs.
Ethier, Kay and Scott Abel. Free Software Magazine (2005). Articles>Information Design>XML
#18209
Extensible Markup Language (XML) is often touted as revolutionary breakthrough in information management. A more realistic description is that XML is one very good tool among many used to handle information. It's true that XML could potentially save your company a great deal of money—but that depends on your circumstances. In some cases, migration to XML will be expensive. You need to know if you'll get a reasonable return on your investment. The purpose of this paper is to help you ask the right questions.
#22198
XMLIreland Special Interest Group
The Irish XML Special Interest Group, is an informal, not-for-profit trade association, whose members subscribe to an electronic forum and attend monthly events on topics surrounding XML.
#27660
XQuery speeds up the process of finding information contained in an XML document, which is very handy when dealing with long XML documents. This article, the first of two parts, will teach you how to write XQuery expressions.
Dev Articles (2006). Articles>Information Design>Databases>XML
#30105
New office document standards like the OpenDocument Format(ODF) and Office Open XML (OOXML), however, are making office document integration in business processes a reality. A key benefit of ODF and OOXML for developers is the reuse of existing standards.
Van Cappellen, Marc. Dr. Dobb's (2007). Design>Information Design>Software>XML
#27661
XQuery speeds up the process of finding information contained in an XML document -- which is very handy when dealing with long XML documents. This article, the second of two parts, will teach you how to write XQuery expressions.
Dev Articles (2006). Articles>Information Design>Databases>XML
#32091
A brief overview for a couple of fellow Austin writers who have asked me recently how and where to get started with DITA.
Gentle, Anne. Just Write Click (2007). Articles>Information Design>XML>DITA
#32102
In this conclusion to a three-part series on path expressions, you'll learn about complex predicates, dynamic paths, and more. This article is excerpted from chapter four of the book XQuery.
Walmsley, Priscilla. Dev Articles (2008). Articles>Information Design>XML>XSL
#32239
RELAX NG is not a capitalized misspelling of something you probably get to do all too rarely as a busy programmer and web designer. If you use XML to any great degree, you'll want to take a close look at it. It can help make your life as a web developer easier, allowing you to relax a little more.
McCullough, Peyton. Dev Articles (2008). Articles>Web Design>Information Design>XML
#32240
XML schemas don't have to be rigid. Sometimes, it's best to provide flexibility and allow the author of XML documents to make choices. In this second part of a three-part article, we'll make some modifications to the schema we created in the first part, and learn how to make some things optional.
McCullough, Peyton. Dev Articles (2008). Articles>Web Design>Information Design>XML
#32241
Datatypes and More in RELAX NG
Welcome to the third part of a three-part series on RELAX NG. In this part, we will discuss datatypes, the grammar element, and creating named patterns.
McCullough, Peyton. Dev Articles (2008). Articles>Web Design>Information Design>XML
#32365
Linking DITA Topics Through Relationship Tables
DITA provides a powerful means of linking using relationship tables. The benefit of using a relationship table is the ability to create and maintain links in one place with the map rather than in the topics. Links can be created both between topics of the same information type and between topics of different information types that are not directly related through parent/child relationships. Therefore, the best practice for linking in DITA is to use a relationship table within a map.
Bruski, Kylene. Center for Information-Development Management (2005). Articles>Information Design>XML>DITA
#32366
Specializing Topic Types in DITA
The Darwin Information Typing Architecture (DITA) provides a way for documentation authors and architects to create collections of typed topics that can be easily assembled into various delivery contexts. Topic specialization is the process by which authors and architects can define topic types, while maintaining compatibility with existing style sheets, transforms, and processes. The new topic types are defined as an extension, or delta, relative to an existing topic type, thereby reducing the work necessary to define and maintain the new type.
Priestley, Michael. IBM (2001). Articles>Information Design>XML>DITA
#32367
Migrating HTML to DITA, Part 1: Simple Steps to Move from HTML to DITA
The Darwin Information Typing Architecture (DITA) has emerged as a standard topic-oriented document architecture. DITA holds many advantages over information authored directly in HTML, including better reuse, easily changed presentation styles, and easy single sourcing. This article, the first of two parts, explains how to get a quick start with DITA using HTML topics that are already available. It shows you how to use the provided XSLT transform to do the migration, and examines what is needed to ensure quality results.
Anderson, Robert, Don Day and Erik Hennum. IBM (2005). Articles>Information Design>XML>DITA
#32381
Some general notes on RDF, its history and prospects, and a Grand Challenge to the RDF community.
Bray, Tim. Aaron Swartz Weblog (2008). Articles>Information Design>XML>RSS
