Extensible Markup Language (XML) is revolutionizing Web content, electronic commerce, and enterprise computing. As with most technology revolutions, the concept behind XML is deceptively simple--to provide a standardization for specifying the meaning of information exchanged over networks. However, the implications for such a capability ripple throughout the entire field of distributed computing.
Organizations, applications, and individuals can communicate far more effectively if they agree on the structure and meaning of information. XML was specifically designed to facilitate such communication over the Internet. Its rapid adoption is taking Web content beyond page layout, e-commerce to a new level of sophistication, and enterprise software into an era of true interoperability.
This book serves as a concise guide for technical managers, as well as a starting point for developers interested in taking advantage of XML. It uses clear explanations of XML essentials as a foundation to demonstrate how this technology can substantially benefit your organization. Designed to let you access exactly the information you require, this book clearly delineates different paths through the chapters based on your needs, provides executive briefings for every chapter, and includes fast-track summaries of major points in the margins.
XML: A Manager's Guide consists of three sections. The first section explains the need for XML, introduces fundamental XML concepts, and describes how combining XML with related standards forms a new paradigm for information exchange. The second section analyzes the tools, processes, and staff you will need to deploy applications that effectively leverage the power of this paradigm. Finally, the third section discusses a portfolio of XML applications relevant to both enterprise software development organizations and independent software vendors.
(Most chapters include an Executive Summary.)
Foreword.
Preface.
Purpose of This Book.
Who Should Read This Book.
Organization of This Book.
Acknowledgments.
1. The Internet Crisis: Exchanging Information
Connections Without Understanding.
Convergence of Information Exchange Problems.
Metadata Standard Is a First Step.
Shared Context Standard Delivers True Understanding.
The XML Approach.
Jumping In.
XML Conceptual Model.
Introducing Elements.
Introducing Attributes.
Creating an "Order" in XML.
Introducing Document Types.
Introducing Entities.
Technical Summary.
Overview of Namespaces.
Overview of XLink.
Overview of XSL.
Overview of XSLT.
Overview of XML Schema.
Technical Summary.
Fundamental Components.
Web Infrastructure.
Development Tools.
Authoring Tools.
Content Management Tools.
XML Applications Introduce Change.
Content Documents.
Business Documents.
Protocol Documents.
Application Spectrum.
Enterprise Application Types.
Information Distribution.
Knowledge Management.
Workflow.
Application Integration.
Data Integration.
Vendor Application Types.
Customized Publishing.
Information Aggregation.
Software Bill of Materials.
Configuration and Logging Files.
Distributed Protocol.
Glossary.
Index. 0201433354T04062001
Extensible Markup Language (XML) is an exciting new technology for exchanging structured information over intranets, extranets, and the Internet. As with many new software technologies, information flows into the developer community first. This flow starts electronically with e-mail lists, newsgroups, and technical Web sites. Then technology references, developer guides, and tutorials appear on bookstore shelves.
After developers use a technology to create some inspiring prototypes, the computing press usually latches on to the trend. Articles hail it as the solution to a wide variety of application development problems. Executives take notice of the press coverage. They may even hear about internal "skunkworks" projects. Quickly, they want assessments of how the technology will affect their organizations.
Managers get caught in the middle. They are at an information disadvantage when it comes to assessing the benefits of the technology and managing its use. On the one hand, developers are pushing from the bottom to use the technology on projects. On the other hand, executives are pushing from the top for formal technology planning. Unfortunately, information resources targeted specifically at managers are usually extremely limited. Therefore, managers must often resort to a time-consuming process of scanning volumes of developer-oriented details and dissecting executive summaries to synthesize a manager's perspective.
XML: A Manager's Guide, addresses this problem for XML. It delivers:
Obviously, this book targets managers. More specifically, it targets software development managers in (1) information systems (IS) organizations within enterprises and (2) product development groups within software vendors. To a great extent, the needs of these two different managerial audiences intersect. They both need a basic understanding of the technology as well as guidance in the tools, processes, and people necessary for success. They do differ in the types of XML applications relevant to their organizations, and this book accommodates the difference.
Even within these two audiences, managers differ significantly in their individual backgrounds and managerial goals. Different managers will require different levels of detail for each of the three basic XML topics in the preceding list. To a certain extent, the level of detail required correlates with job responsibility.
Technology planners and project managers will find this book most useful. Executives may find it useful to read portions of this book, but they will probably want to skip much of the detailed information. Application designers will find it a useful overview of XML technology and may find it provides some high-level inspiration. However, they will definitely want to acquire a more technical resource such as a developer's guide.
The organization of this book allows you to either read all the chapters sequentially or pick and choose the chapters that you find most interesting. All chapters after Chapter 1 begin with an Executive Summary section. After reading this section, you can decide whether you need the details provided in the rest of the chapter. You may also quickly skim these details by using the Fast Track paragraph summaries, which appear in the margins. This book has seven chapters:
As you can see, the last three chapters focus on the needs of project managers, enterprise technology planners, and vendor technology planners, respectively. If you don't fall into the primary audience for one of these chapters, you may wish to read only the Executive Summary.
There is a Glossary at the end of the book that defines many of the XML and general Internet terms used in this book. You will find it helpful if you come across an unfamiliar term or simply want to refresh your memory of its definition. The first time a word defined in the Glossary appears, it is set in color. Terms specific to XML appear in italics, while general Internet terms appear in plain typeface.
