`
`
`
`
`
`Merrill Communications LLC
`d/b/a Merrill Corporation
`Exhibit 1006 pt. 1
`
`

`

`H
`
`TM
`
`.,.. The definitive XML resource:
`applications, products, and
`technologies!
`
`.,.. Leverage your Web and
`intranet expertise with
`structured information
`
`.,.. CD-ROM: Unique trialware,
`demos, examples, specs, and
`more-plus 55 great, gen(cid:173)
`uinely free XML software
`packages
`
`Adobe®
`FromeMake~ +SGML
`Free Trial with
`XML Update
`
`CHARLES F. GOLDFARB · PAUL PRESCOD
`
`THE DEFINITIVE XML SERIES FROM CHARLES F. GOLDFARB
`
`

`

`

`

`The
`XML
`Handbook™
`
`ISBN 0-13-081152-1
`
`90000
`
`©1998 THE XML HANDBOOK™
`
`9 780130 811523
`
`

`

`<f~f~) The Charles F. Goldfarb Series on
`
`,£1!! Open lnformaialon Nanaaemen•
`"Open Information Management" (OIM) means managing informa(cid:173)
`tion so that it is open to processing by any program, not just the pro(cid:173)
`gram that created it. That extends even to application programs not
`conceived of at the time the information was created.
`OIM is based on the principle of data independence: data should
`be stored in computers in non-proprietary, genuinely standardized
`representations. And that applies even when the data is the content of
`a document. Its representation should distinguish the innate infor(cid:173)
`mation from the proprietary codes of document processing programs
`and the artifacts of particular presentation styles.
`Business data bases-which rigorously separate the real data from
`the input forms and output reports-achieved data independence
`decades ago. But documents, unlike business data, have historically
`been created in the context of a particular output presentation style.
`So for document data, independence was largely unachievable until
`recently.
`That is doubly unfortunate. It is unfortunate because documents
`are a far more significant repository of humanity's information. And
`documents can contain significantly richer information structures
`than data bases.
`It is also unfortunate because the need for 0 IM of documents is
`greater now than ever. The demands of "repurposing" require that
`information be deliverable in multiple formats: paper-based, online,
`multimedia, hypermedia. And information must now be delivered
`through multiple channels: traditional bookstores and libraries, the
`World Wide Web, corporate intranets and extranets. In the latter
`modes, what starts as data base data may become a document for
`browsing, but then may need to be reused by the reader as data.
`Fortunately, in the past ten years a technology has emerged that
`extends to documents the data base's capacity for data independence.
`And it does so without the data base's restrictions on structural free-
`
`CD I 9 9 H THE X M L H AND B o 0 K '"'
`
`

`

`dom. That technology is the "Standard Generalized Markup Lan(cid:173)
`guage" (SGML), an official International Standard (ISO 8879) that
`has been adopted by the world's largest producers of documents and
`by the World Wide Web.
`With SGML, organizations in government, aerospace, airlines,
`automotive, electronics, computers, and publishing (to name a few)
`have freed their documents from hostage relationships to processing
`software. SGML coexists with graphics, multimedia and other data
`standards needed for OIM and acts as the framework that relates
`objects in the other formats to one another and to SGML documents.
`The World Wide Web's HTML and XML are both based on
`SGML. HTML is a particular, though very general, application of
`SGML, like those for the above industries. There is a limited set of
`markup tags that can be used with HTML. XML, in contrast, is a
`simplified subset of SGML facilities that, like full SGML, can be used
`with any set of tags. You can literally create your own markup lan(cid:173)
`guage with XML.
`As the enabling standard for OIM of documents, the SGML fam(cid:173)
`ily of standards necessarily plays a leading role in this series. We pro(cid:173)
`vide tutorials on SGML, XML, and other key standards and the
`techniques for applying them. Our books vary in technical intensity
`from programming techniques for software developers to the business
`justification of OIM for enterprise executives. We share the practical
`experience of organizations and individuals who have applied the
`techniques of OIM in environments ranging from immense industrial
`publishing projects to websites of all sizes.
`Our authors are expert practitioners in their subject matter, not
`writers hired to cover a "hot" topic. They bring insight and under(cid:173)
`standing that can only come from real-world experience. Moreover,
`they practice what they preach about standardization. Their books
`share a common standards-based vocabulary. In this way, knowledge
`gained from one book in the series is directly applicable when reading
`another, or the standards themselves. This is just one of the ways in
`
`©1998 THE XML HANDBOOK TM
`
`

`

`which we strive for the utmost technical accuracy and consistency
`with the OIM standards.
`And we also strive for a sense of excitement and fun. After all, the
`challenge of OIM-preserving information from the ravages of tech(cid:173)
`nology while exploiting its benefits-is one of the great intellectual
`adventures of our age. I'm sure you'll find this series to be a knowl(cid:173)
`edgable and reliable guide on that adventure.
`
`About the Series Editor
`
`Dr. Charles F. Goldfarb invented the SGML language in 197 4 and
`later led the team that developed it into the International Standard on
`which both HTML and XML are based. He serves as editor of the
`Standard (ISO 8879) and as a consultant to developers of SGML and
`XML applications and products. He is based in Saratoga, CA.
`
`About the Series Logo
`
`The rebus is an ancient literary tradition, dating from 16th cen(cid:173)
`tury Picardy, and is especially appropriate to a series involving fine
`distinctions between things and the words that describe rhem . For the
`logo, Andrew Goldfarb incorporated a rebus of the series name within
`a stylized SGMLIXML comment declaration.
`
`©1998 THE XML HAN0600KT'-'
`
`

`

`<f
`
`cFo) 'lhe Charles F. Goldfarb Series on
`• Oi M Open lnformai:ion Manaaemenc
`As XML is a subset of SGML, the Series List is categorized to show the degree to
`which a title applies to XML. "XML Titles" are those that discuss XML explicitly
`and may also cover full SGML. "SGML Titles" do not mention XML per se, but
`the principles covered may apply to XML.
`
`XML 'lii:les
`Goldfarb, Pepper, and Ensign
`I SGML Buyer's Guide ™: Choosing the Right XML
`and SGML Products and Services
`Megginson
`I Structuring XML Documents
`Leventhal, Lewis, and Fuchs
`I Designing XML Internet Applications
`Goldfarb and Prescod
`I The XML HandbookT"
`Jelllffe
`I The XML and SGML Cookbook: Recipes for
`Structured Information
`
`SGML 'lii:les
`Turner, Douglass, and Turner
`I ReadMe. I st: SGML for Writers and Editors
`Donovan
`I Industrial-Strength SGML:An Introduction to
`Enterprise Publishing
`Ensign
`I SGML:The Billion Dollar Secret
`Rubinsky and Maloney
`I SGML on the Web: Small Steps Beyond HTML
`McGrath
`I ParseMe.l st: SGML for Software Developers
`DuCharme
`I SGML CD
`
`© 1998 THE XML HANDBOOKTM
`
`

`

`
`

`

`The
`XML
`Handbook·M
`
`I Charles F. Goldfarb
`I Paul Prescod
`
`Prentice Hall PTR, Upper Saddle River, NJ 07458
`http:/ /www.phptr.com
`
`©1998 TH E XML HANDBOOKTM
`
`

`

`Library of Congress Cataloging-in-Publication Data
`
`Goldfarb, Charles F.
`XML handbook I Charles F. Goldfarb, Paul Prescod.
`p.
`em. --
`(Charles F. Goldfarb series on open information
`management)
`Includes index.
`: alk. paper)
`ISBN 0-13-081152-1 (pbk.
`1. XML
`(Document markup language)
`I. Prescod, Paul. II. Title.
`III. Series.
`QA76.76.H92G65 1998
`005.7'2--dc21
`
`98-16 708
`CIP
`
`Edit01ial!Production Supervision: Patti G!terderi
`Acquisitions Editor: Mark L. Taub
`Editorial Assistant: Audri Ba;:.lan
`Marketing Manager: Dan Rush
`Manufacturing Manager: Alexis R. Heydt
`Cover Design: Anthony Gemmellaro
`Cover Design Direction: Jerry Votta
`Series Design: Gail Cocker-Bogusz
`
`It © 1998 Prentice Hall PTR
`
`Prentice-Hall, Inc.
`A Simon & Schuster Company
`Upper Saddle River, NJ 07458
`
`Prentice Hall books are widely used by corporations and government agencies for training,
`marketing, and resale.
`
`The publisher offers discounts on this book when ordered in bulk quantities. For more information, contact:
`orporate Sales D eportment, Phone: 00-382-3419; Fax: 201-236-71 4 l; E-mail: corpsales@pr nhall.com;
`or write: Prentice HnTI PTR, Corp. Sales D pl., One Lake Str e.t, Upp r Saddle Riv r, NJ 07458.
`
`All rigbts res •rved. No part of this book may be
`reproduced, in any form or by any means, without
`permission in writing from the publisher.
`
`Printed in the United States of America
`
`10 9 8 7 6 54 3 2
`
`ISBN 0-13-081152-1
`
`Prentice-Hall International (UK) Limited, London
`Prentice-Hall of Australia Pty. Limited, Sydney
`Prentice-Hall Canada Inc. , Toronto
`Prentice-Hall Hispanoamericana, S.A., Mexico
`Prentice-Hall of India Private Limited, New Delhi
`Prentice-Hall ofJapan, Inc., Tokyo
`Simon & Schuster Asia Pte. Ltd. , Singapore
`Editora Prentice-Hall do Brasil, Ltda., Rio de Janeiro
`
`©1 9 98 THE XML HANDB O OKTM
`
`

`

`Adob , the Adobe logo, Acmbut, From Mnke r, and PostScript are trademarks of Adobe Systems
`JncorpomL d. Microsoft and Windows are r>gist r cl trad · marks of Microsoft Corporation in the U.S. and
`other ·ow1tdes. Dyna':D xt, Dynal3as , lnso, and th
`l nso Logo are trademarks or registered trademarks of
`Inso Corporation.
`
`The ML Handbook, HARP, and oth r r gi. t red and unregistered trademarks, service marks, logos,
`company na mes, and product names appearing in this book or on its cover are the property of their respective
`owners.
`
`Series logo by Andrew Goldfarb for EyeTech Graphics, copyright ©1996 Andrew Goldfarb.
`
`Series foreword copyright ©1996, 1997 Charles F. Goldfarb.
`
`Excerpts from the following Intenmtiom1l Standard are copyright ©1986, 1988 International Organization for
`Standardization, and are included wlt:U lhe kind permh;sion of the copyright owner:
`
`ISO 8879:1986, Information processing- Text and office systems- Standard Generalized Markup
`Language (SGML).
`
`Complete copies of this standard can be obtained from the national member body of ISO in your country, or
`contact ISO, case postale 56, CH-1211 Geneva 20, Switzerland.
`
`Excerpts from the following World Wide Web Consortium documents are included in accordance with the
`W3C IPR Document Notice, http://www.w3.org/Consortium/LegaVcopyright-documents.html. Copyright
`©World Wide Web Consortium (Massachusetts Institute of Technology, Institut National de Recherche en
`Informatique et en Automatique, Keio University) . All Rights Reserved.
`
`Extensible Markup Language (XML) 1.0, http:l!www.w3.org/TRIREC-xml, W3C Recommendation
`10-February-1998.
`
`Extensible Linking Language (XLink), http://www.w3.org!TRIWD-xlink, W3C Working Draft 3-March-
`1998.
`
`XML Pointer Language (XPointer), http://www.w3.org!TRIWD-xptr, W3C Working Draft 03-March-1998.
`
`A Proposal for XSL, http://www.w3.org!TRINOTE-XSL-970910, Note submitted to W3C on 27 August
`1997.
`
`HTML 4.0 Specification, http:llwww.w3.org/TRIREC-html401, W3C Recommendation, revised on 24-Apr-
`1998.
`
`The development of this book was partly subsidized by Sponsors, who provided both fin ancial support and
`expert assistance in preparing the initial draft of the text identified with their nom
`. How ver, as the Authors
`exercised final editorial control over the book, the Sponsors are in no way responsible for its content. In
`particular, opinions expressed in this book are those of the Authors and are not necessarily those of the Series
`Editor, Sponsors, or Publisher.
`
`This book, and the CD-ROM included with it, contain software and descriptive materials provided by (or
`adapted from materials made publicly nvniluble by) product developers, vendors, and service providers. Said
`software and materiab have not be n r viewed, edited, or tested, and neither the Authors, Contributors,
`Series Editor, Publisher, Sponsors, or other parties connected with this book are responsible for their
`accuracy or reliability. H aders are warned that they use said software and materials at their own risk, and are
`urged to test the softwar and confirm the validity of the information prior to use.
`
`©1998 THE XML HANDBOOK "'
`
`

`

`

`

`To Linda- With love, awe, and gratitude.
`
`Charles F. Goldfarb
`
`For Lilia- Your support makes it possible and
`your love makes it worthwhile.
`
`Paul Prescod
`
`©1998 THE XML HANDBOOK™
`
`

`

`

`

`Contents
`
`Foreword
`Preface
`
`I Pan one
`
`The Who, What, and
`Why ofXML
`Chapter I Why X MLt
`1.1 1 Text formatters and SGML
`1.1.1 Formatting markup
`1.1.2 Generalized markup
`1.1.2.1 Common document representation
`1.1.2.2 Customized document types
`1.1.2.3 Rule-based markup
`1.2 1 HTML and the Web
`1.2.1 HTML gets extended - unofficially!
`1.2.2 The World Wide Web reacts
`1.3 1 Conclusion
`
`©1 998 T HE XML HANDBOOKTM
`
`XXXV
`
`XXXV
`
`I
`
`2.
`
`4
`
`4
`
`6
`6
`6
`12
`
`14
`
`16
`
`16
`
`18
`
`xiii
`
`

`

`Xl V
`
`CONTENTS
`
`Chapter 2 Where is XML goingt
`2.1 1 Beyond HTML
`2.2 1 Database publishing
`2.3 1 Electronic commerce
`2.4 1 Metadata
`2.5 1 Science on the Web
`Chapter:. Just enough XML
`3.1 1 The goal
`3.2 1 Elements: The logical structure
`3.3 1 Unicode: The character set
`3.4 1 Entities: The physical structure
`3.5 1 Markup
`3.6 1 Document types
`3.7 1 Well-formedness and validity
`3.8 1 Hyperlinking and Addressing
`3.9 1 Stylesheets
`3.1 o 1 Conclusion
`Chapter • XML in the real world
`4.1 1 Is XML for documents or for data?
`4.2 1 Endless specbum of application opporhmities
`4.2.1 Presentation-oriented publishing
`4.2.2 Message-oriented middleware
`4.2.3 Opposites are attracted
`4.2.4 MOM and POP- They're so great together!
`4.3 1 XML tools
`4.4 1 XML jargon demystifier
`4.4.1 Structured vs. unstructured
`
`10
`
`21
`
`25
`
`26
`
`26
`
`28
`31
`
`34
`
`35
`
`37
`
`38
`
`39
`
`40
`
`44
`
`45
`
`47
`
`47
`
`48
`
`49
`
`50
`
`52
`
`54
`
`55
`
`57
`
`58
`
`59
`
`60
`
`©1998 T HE XML HANOBOOK 'rM
`
`

`

`CONTENTS
`
`XV
`
`4.4.2 Tag vs. element
`4.4.3 Document type, DTD, and markup declarations
`4.4.4 Document, XML document, and document instance
`4.4.5 Coding, encoding, and markup
`4.5 1 Conclusion
`
`60
`
`61
`
`62
`
`63
`
`63
`
`6S
`
`66
`
`1 Pan Two What You Can Do with XML
`chapcer s Personalized frequent -flyer
`Web site
`5.1 1 Today's frequent-flyer sites
`5.1 1 What's wrong with today's Web model?
`5.3 1 A better model for doing business on the Web
`5.4 1 An XML-enabled frequent-flyer Web site
`5.5 1 Understanding the Softland Air scenario
`5.6 1 Towards the Brave New Web
`Chapcer • Building an online auction
`Web s~e
`6. 1 1 Getting data from the middle tier
`6.1.1 Defining the XML document structure
`6.1.2 Using ASP files to generate XML documents
`6.1.3 Generating XML from multiple databases
`86
`6.1.4 Generating XML from both databases and XML data sources
`86
`6.1 1 Building the user interface
`6.2.1 Using procedural scripts
`6.2.2 Using descriptive data binding
`6.3 1 Updating the data source from the client
`6.4 1 Conclusion
`
`67
`
`68
`
`69
`
`70
`
`73
`
`76
`
`78
`
`80
`
`82
`
`82
`
`89
`
`89
`
`90
`
`91
`
`93
`
`© 1 9 98 THE XML HANDB OOK TM
`
`

`

`XVI
`
`CONTENTS
`
`Chap•er 7 XML and EDI:
`The new Web commerce
`7.1 1 What is EDI?
`7 .I. I Extra nets can't hack it
`7.1.2 XML can!
`7.1.3 The new EDI
`7.1.4 Ubiquitous EDI: A quantum leap forward
`7.1.5 The value of EDI
`7.2 1 Traditional ED I: Built on outdated principles
`7.2.1 The history ofEDI
`7.2.2 EDI technology basics
`7.2.3 The problems of traditional EDI
`7.2.3.1 Fixed transaction sets
`7.2.3.2 Slow standards evolution
`7.2.3.3 Non-standard standards
`7.2.3.4 High fixed costs
`7.2.3.5 Fixed business rules
`7.2.3.6 Limited penetration
`7.3 1 The new ED I: Leveraging XML and the Internet
`7.3.1 XML
`7 .3.2 The Internet
`Internet technologies
`7.3.3
`7.3.4 XML data storage
`7.3.5 Data filtering
`7.4 1 Conclusion
`Chap•er a Supply chain integration
`8.1 1 Linking up a supply chain
`8.2 1 Supply chain integration requirements
`8.3 1 The B2B Integration SeiVer
`8.4 1 OveiView of the system
`
`96
`
`97
`
`98
`
`99
`
`99
`
`100
`
`101
`
`103
`
`104
`
`104
`
`106
`106
`106
`107
`108
`109
`110
`
`110
`
`111
`
`113
`
`114
`
`115
`
`116
`
`117
`110
`
`121
`
`122
`
`123
`
`123
`
`©19 9 8 THE XML HANDB O QKTM
`
`

`

`CONTENTS
`
`XVll
`
`8 •5 1 The manufacturer seiVices
`8.5.1 B2B plug-in
`8.5.2 Server stub
`8.5.3 XML requests and replies
`8.5.4 Java thin client
`8.5.5 Manufacturer interface specification
`8.a 1 The supplier seiVices
`8.6.1 Client stub
`8.6.2 Supplier interface specification
`8.7 1 Conclusion
`chapter • Comparison shopping service
`Web site
`t.l 1 Shopping online for books
`t.1 1 The Junglee Shopping Guide
`t.J 1 How the Shopping Guide works
`t.4 1 Conclusion
`chapter •• Natural language translation
`1 o. 1 1 Mistakes can be costly
`10.1 1 It's a small world
`10.3 1 Business challenges
`I 0.3.1 Cost containment
`I 0.3.2 Fast-paced product development
`I 0.3.3 Diverse documents
`1 o.4 1 Translations today
`1o.s 1 New directions
`I 0.5.1 Components
`I 0.5.2 Reduce reinvention with reuse
`Identify changes with versioning
`I 0.5.3
`
`©1998 THE XML HANDBOQKTM
`
`124
`
`125
`
`126
`
`126
`
`126
`
`127
`
`128
`
`128
`
`129
`
`130
`
`1 :Jl
`
`133
`
`134
`
`135
`
`137
`140
`
`141
`
`142
`
`143
`
`143
`
`144
`
`144
`
`144
`
`147
`
`147
`
`148
`
`149
`
`

`

`XVlll
`
`CONTENTS
`
`I 0.5.4 Alignment enables concurrent authoring and
`translation
`1o.e 1 In the real world
`Chapter 11 Securities regulation filings
`1 1.1 1 Visualizing an XML document
`1 1.2 1 An EDGAR Submission with XML
`11.2.1 Reviewing the EDGAR DTD
`11.2.2 Creating an instance of the DTD
`11.2.3 Checking your EDGAR instance for conformance
`11.2.4 Repairing non-conforming elements
`I 1.2.5 Generating your EDGAR submission
`I 1.2.6 Publishing for the SEC
`I 1.2. 7 Repurposing for your Web site
`11.3 1 Conclusion
`Chapter 12 Help Desk automation
`12.1 1 1he hapless Help Desk
`12.1.1 The old way
`12.1.2 What needed to be done?
`12.1.3 Helping the Help Desk
`12.2 1 How the Solution System works
`Information flow
`12.2.1
`12.2.2 Architecture
`12.3 1 Using the Help Desk Solution System
`12.3.1 Make the query
`12.3.2 Research product information
`12.3.3 Write a solution
`12.3.4 Update the repository
`12.3.5 Route for approval
`
`150
`
`151
`
`152
`
`154
`
`156
`
`157
`
`158
`
`158
`
`159
`
`161
`
`161
`
`161
`
`162
`
`164
`
`165
`
`165
`
`166
`
`167
`
`168
`
`168
`
`169
`
`170
`
`170
`
`170
`
`171
`
`172
`
`173
`
`©1998 THE XML HANDBOOK™
`
`

`

`CONTENTS
`
`XlX
`
`12.3.6 Check in document to knowledge base
`chapi:er 11 Extended linking
`u. 1 1 The Shop notes application
`13 .1.1 What is extended linking?
`13.1.2 Displaying extended links
`13.1.3 Notes survive to new versions of manuals
`13.1.4 Vendors can use the notes
`13.1 1 Other applications of extended linking
`13.2.1 Public resource communities of interest
`13.2.2 Guidance documents
`13.2.3 Computer-augmented memory
`13.2.4 Intellectual property management
`13.3 1 Strong link typing
`13.3.1 Hiding the installation log
`13.3.2 Why do we need strong link typing?
`13.3.3 Anchor role identification
`13.4 1 Conclusion
`
`175
`176
`
`177
`
`178
`
`179
`
`180
`
`181
`
`181
`
`182
`
`183
`
`184
`
`185
`
`185
`
`186
`
`186
`
`187
`
`187
`
`193
`
`194
`
`196
`
`197
`
`I Part Three What's Being Done with XML 191
`Chapi:er •• Hitachi Semiconductor
`191
`14. 1 1 Introduction
`14.1 1 The business case
`14.3 1 Phase 1: Creating a single source file
`14.4 1 Phase 2: Automating transformations with XML
`14.s 1 "Publishing on steroids"
`14,6 1 Facilitation ofWeb-based searching
`14.7 1 Quantifiable savings
`14.a 1 Conclusion: A new dimension of automation
`
`198
`
`198
`
`200
`
`200
`
`©1998 THE XML HANDBOOKTM
`
`

`

`XX
`
`CONTENTS
`
`Chap•er 1s The Washington Post
`1 s.1 1 The Post Web site
`1 s.1 1 Job searching online
`I 5.2.1 Andersen Consulting
`I 5.2.2 CACI International
`I 5.2.3 Career Post
`1 s.:~ 1 How JobCanopy works
`1 s.4 1 Summary
`Chap•er 16 Frank Russell Company
`1 cs. 1 1 Background
`1 cs.1 1 Project strategy considerations
`16.2.1 Proceeding from a theoretical abstraction to
`practical applications
`16.2.2 Phasing deliverables with measurable return on
`investment
`16.2.3 Continuing research in parallel with focused
`development projects
`16.2.4 Alignment with overall corporate strategies
`16.2.5 Executive sponsorship
`1 C5.3 1 Identifying the needs
`16.3.1 Business requirements
`16.3.1.1 Compliance
`16.3.1.2 Premium typographic quality
`16.3.1.3 Data integrity
`16.3.1.4 Security
`16.3.2 Technical requirements
`16.3.2.1 Scalability
`16.3.2.2 Low licensing impact for reader software
`16.3.2.3 Ease of use
`16.3.2.4 Cross-platform
`16.3.2.5 Multilingual capability
`
`101
`
`203
`
`204
`
`204
`
`204
`
`205
`
`20s
`
`209
`11 o
`211
`
`212
`
`213
`
`213
`
`213
`
`214
`
`214
`
`215
`
`215
`
`215
`215
`216
`216
`
`216
`
`216
`216
`216
`217
`217
`
`©1998 THE XML HANDBOOK™
`
`

`

`4 I Create an abstract architecture
`16.
`16.5 1 Implement applications
`16.5.1 Real-world design issues
`lnternetworking
`16.5.1.1
`16.5.2 Document representation
`16.5.2.1 Abstract document representation
`16.5.2.2 Rendered document representation
`16.5.3 Phased implementation plan
`16.5.3.1 Phase 1: Records management business study
`16.5.3.2 Phase II: Document management of PDF files
`16.5.3.3 Phase Ill: Document assembly and formatting
`16.5.3.4 Phase IV: XML and the future
`16.6 1 Conclusion
`chap•er 1 7 A gent Discovery
`17.1 1 Agent Discovery
`17.2 1 Picture this
`17.2.1 Access vs. integration
`17.2.2 The solution: Web automation
`17.:J 1 \Vhat is Web automation?
`17.4 1 Discovering common ground
`17.5 1 What about XML?
`17.6 1 Architecture principles
`17.7 1 Conclusion
`Chap•er •• Major Corporation
`18.1 1 Background
`18.2 1 First generation: Client/server
`18. :J 1 Second generation: Three-tier
`18.3.1 Data extraction
`18.3.2 Database maintenance
`18.4 1 Summary
`
`©!998 THE XML HANDBOOKTM
`
`CONTENTS
`
`XXI
`
`217
`
`220
`
`220
`220
`220
`221
`221
`222
`222
`223
`224
`228
`
`230
`lll
`
`233
`
`234
`
`235
`
`236
`
`237
`
`238
`
`239
`
`240
`
`241
`l4l
`
`244
`
`245
`
`247
`
`248
`
`249
`
`250
`
`

`

`XX:ll
`
`CONTENTS
`
`Ch•pter •• City Of Providence
`1 ~. 1 1 The Providence Guide prototype
`1 ~.2 1 Information architecture
`1 ~.3 J Conversion to XML
`1 ~.4 1 Generating the electronic book
`19.4.1 Using multiple stylesheets
`19.4.1.1 Contextual searching and personalization
`1 ~.s 1 Web delivery
`1 ~.cs 1 Dynamic Web delivery
`1 ~.7 1 Updating the XML data
`1 ~.8 1 Revising the Electronic Book
`1 ~.~ 1 Summary
`Ch•pter 20 lnternationa• Organization
`for Standardization
`20. 1 1 ISO 12083; DTDs for publishers
`20.2 1 Adapting ISO 12083 to XML
`20.2.1 Automated modifications
`20.2.1.1 XML declaration
`20.2.1.2 Omitted tag minimization rules
`20.2.1.3 Grouped element type and attribute declarations
`20.2.1.4 Comments in other declarations
`20.2.1.5 Quoted default attribute values
`20.2.1.6 Parameter entity references
`20.2.1.7 Example of automated modifications
`20.2.2 Assisted modifications
`20.2.2.1 Attribute types and defaults
`20.2.2.2 Declared content
`20.2.3 Other modifications
`20.2.3.1 Eliminating inclusions
`20.2.3.2 Eliminating AND connectors
`20.2.3.3 Eliminating exclusions
`
`252
`
`253
`
`255
`
`255
`
`255
`
`256
`256
`
`257
`
`258
`
`260
`
`261
`
`263
`
`264
`
`266
`
`266
`
`267
`267
`267
`267
`268
`268
`268
`268
`
`269
`269
`270
`
`271
`
`272
`273
`274
`
`© 19 98 THE X ML H ANDBOOK™
`
`

`

`CONTENTS
`
`XX:lll
`
`274
`275
`
`278
`
`20.2.3.4 Adding system identifiers
`10.3 1 Conclusion
`I Pan Four Tools for Working with XML 277
`chap•er 21 FrameMaker+ SGML:
`Editing+ composition
`11 .1 1 Leveraging information
`11.1 1 XML authming functions
`21.2.1 Guided editing
`21.2.2 Authoringflexibility
`21.2.3 Problem correction
`21 .2.4 Authoring utilities
`21 .2.4.1 Cross-references
`Indexing
`21.2.4.2
`21.2.4.3 Hypertext
`21.2.5 Managing external content
`21.2.6 Welljormedness support
`11.3 1 Automated formatting and composition
`21.3.1 Rule-based formatting
`21.3.2 Interactive formatting
`11.4 1 Document fragments
`11.s 1 Publishing the document
`21.5.1 Paper publishing
`21.5.2 Online publishing
`21.5.2.1 PDF
`21.5.2.2 HTM L
`11.cs 1 Customization and preparation
`21.6.1 DTD customization
`21.6.2 Defining formatting rules
`21.6.3 Extensibility
`
`279
`
`280
`
`281
`
`281
`
`283
`
`286
`286
`286
`287
`
`288
`
`288
`
`288
`
`289
`
`289
`
`290
`
`290
`
`291
`
`292
`292
`293
`
`293
`
`293
`294
`
`295
`
`©19 9 8 T HE XML HANDBOOK™
`
`

`

`XXIV
`
`CONTENTS
`
`Chapter 22 ADEPT•Editor:
`Edit for content management 296
`11. 1 1 Automated document systems
`22.1.1 Structure
`22.1.2 Content management
`11.1 1 What information warrants these tools?
`
`297
`
`298
`
`301
`
`303
`
`303
`
`303
`
`303
`
`304
`
`304
`
`304
`
`304
`
`305
`
`305
`306
`307
`
`309
`309
`312
`
`22.2. 7 Created by formal processes
`11.3 1 Characteristics to consider
`22.3.1 Authoring issues
`"Task-matched" tools
`22.3.1.1
`22.3.1.2 Structure consistency
`22.3.2 Development issues
`22.3.2.1 Content management integration
`22.3.2.2 Customization
`22.3.3 Business issues
`313
`22.3.3.1 Authoring productivity
`314
`22.3.3.2 Batch composition
`315
`22.3.3.3 Presentation independence
`316
`22.3.3.4 Standards-based
`317
`Chapter 2:. X MetaL: Friendly XML editing 318
`13.1 1 Familiar interface
`13.1 1 HTML markup transition
`13.3 1 Sbuctured editing
`23.3.1 Multiple views
`23.3.2 Tables
`
`319
`
`320
`
`321
`
`321
`
`321
`
`©1998 T HE XML H AND BOOK™
`
`

`

`CONTENTS
`
`XXV
`
`3 3 Named bookmarks
`23 ..
`23 .3.4 Samples and templates
`23.3.5 Context-sensitive styles
`23 .3.6 Default HTML styles
`23.3.7 Direct DTD processing
`23.3.8 Customization
`21 •4 1 Extend XML capabilities to outside authors
`chapter 24 DynaTag visual conversion
`environment
`14.1 1 Concepts of document conversion
`24.1.1 Data rescue
`24.1.2 Style serves meaning
`14.2 1 Converting documents with DynaTag
`24.2.1 Getting started
`24.2.2 Mapping
`24.2.2.1 Automatic mapping
`24.2.2.2 Variant detection
`24.2.2.3 New-mapping helper
`24.2.2.4 Conditional mapping
`24.2.2.5 List wizard
`24.2.2.6 Tables
`24.2.2.7 Character mapping
`24.2.2.8 Cross-references
`24.2.2.9 Searching
`24.2.2.1 o Comments
`24.2.2.11 XML markup features
`24.2.2.12 Capturing structure
`24.2.2.13 Reuse
`24.1 1 Prepruing for electronic publishing
`Chapter 2s XML Styler: Graphical XSL
`stylesheet editor
`u.1 I Introduction to XSL
`
`© 1 9 9 8 THE X M L HAND B o 0 K 1M
`
`322
`
`322
`
`323
`
`323
`
`323
`
`323
`
`324
`
`316
`
`327
`
`328
`
`329
`
`329
`
`329
`
`330
`331
`331
`332
`332
`332
`332
`332
`333
`334
`334
`335
`335
`335
`
`336
`
`3 38
`
`339
`
`

`

`XXVI
`
`CONTENTS
`
`u.1 1 Creating a stylesheet with XML Styler
`15.3 1 XSL patterns
`15.4 1 XSL actions
`25.4.1 HTML!CSS flow objects
`25.4.2 DSSSLjlow objects
`u.s 1 Conclusion
`Chapter !16 Astoria: Flexible content
`management
`16.1 1 Components are everywhere
`26.1.1 Components in publishing
`26.1.1.1 System simplification
`26.1.1.2 Easier revision
`26.1.1.3 Efficient authoring
`26.1.1.4 Less routine editing
`26.1.1.5 Fast, easy customization
`26.1.1.6 Universal updates
`26.1.1.7 Streamlined translations
`26.1.1.8 Flexible distribution
`26.1.2 XML makes components
`26.1.3 Applications for content reuse
`16.1 1 A content management implementation
`26.2.1 Revision tracking
`26.2.2 Search
`26.2.3 Dynamic document assembly
`Chapter !17 POET Content
`Management Suite
`17.1 1 Managing the information life cycle
`27.1.1 Changes to the information life cycle
`27.1.2 The World Wide Web has changed the rules
`27.1.3 Object-oriented components
`17.1 1 The POET Content Management Suite
`
`340
`
`343
`
`348
`
`348
`
`348
`
`349
`
`1s1
`
`353
`
`354
`354
`354
`355
`355
`355
`355
`356
`356
`
`356
`
`358
`
`359
`
`360
`
`361
`
`362
`
`164
`
`365
`
`366
`
`366
`
`367
`
`368
`
`©1998 THE XML HANDBOOK™
`
`

`

`CONTENTS
`
`XXVll
`
`369
`· 369
`370
`370
`370
`
`379
`
`380
`
`382
`382
`382
`383
`
`383
`186
`
`27.2.1 POET CMS components
`27.2.1.1 POET Content Server
`27.2.1.2 POET Content Client
`27.2.1.3 POET Content SDK
`21.2.2 The POET CMS Architecture
`27.2.3 Using POET CMS
`371
`371
`27.2.3.1 Server-side content management
`371
`27.2.3.2 Client-side editing and viewing
`chapter 2a HoTMetaL Application Server 178
`28.1 1 Dynamic descriptive markup
`28.2 1 How HoTMetaL APPS works
`28.2.1 Middle-tier server tags
`28.2.1.1 Data access tags
`28.2.1.2 Conditional logic tags
`28.2.2 Guided construction of dynamic pages
`28.3 1 Functionality can be friendly
`Chap•er 20 Junglee Virtual DBMS
`20.1 1 Why virtual database technology?
`20.2 1 How the VDBMS works
`29.2.1 Wrapper Development Kit (WDK)
`29.2.2 The Extractor Development Kit (EDK)
`29.2.3 VDB Server and Data Quality Kit
`29.2.4 Administration interface
`20.3 1 Applications ofVDB technology
`Chapter :.o Free XML software
`30.1 1 What do we mean by "free"?
`30.2 1 The best XML free software
`30.2.1 Parsers and engines
`30.2.1.1 Xlink engines
`30.2.1.2 XSL engines
`30.2.1.3 DSSSL engines
`
`387
`
`389
`
`389
`
`390
`
`391
`
`392
`
`392
`194
`
`395
`
`396
`
`396
`396
`397
`398
`
`©1998 THE XML HANDBOOKTM
`
`

`

`XX:Vlll
`
`CONTENTS
`
`30.2.1.4 SGMUXML parsers
`30.2.1.5 XM L parsers
`30.2.1.6 XML middleware
`30.2.2 Editing and composition
`30.2.2.1 XML editors
`30.2.3 Control information development
`30.2.3.1 XSL editors
`30.2.3.2 DTD editors
`30.2.3.3 DTD documenters
`30.2.4 Conversion
`30.2.4.1 General S-converters
`30.2.4.2 Specific N-converters
`30.2.4.3 General N-converters
`30.2.5 Electronic delivery
`30.2.5.1 XML browsers
`30.2.6 Resources
`30.2.6.1 Useful programs
`30.2.6.2 Archiving software
`
`I PaM: F~Ye
`The Technology of XML
`Chapcer :. 1 XM L basics
`3 1 • 1 1 Syntactic details
`31.1.1 Case-sensitivity
`3 1.1.2 Markup and data
`3 1.1.3 White space
`31.1.4 Names and name tokens
`31.1.5 Literal strings
`31.1.6 Grammars
`3 1 .1. 1 Prolog vs. instance
`3 1. 3 1 The logical sbuchrre
`3 1.4 1 Elements
`3 1.s 1 Attributes
`
`400
`401
`408
`412
`412
`414
`414
`415
`415
`416
`416
`416
`417
`417
`417
`419
`419
`421
`
`423
`
`424
`
`426
`426
`
`427
`428
`
`428
`429
`
`431
`
`431
`
`432
`
`434
`
`436
`
`©1998 THE XML HANDBOOK™
`
`

`

`3 1•6 1 The prolog
`31 .6.1 XML declaration
`31.6.1.1 Version info
`31.6.1.2 Encoding declaration
`31.6.1 .3 Standalone document declaration
`31.6.2 Document type declaration
`31 •7 1 Markup miscellany
`3 1. 7 .I Predefined entities
`31.7.2 CDATA sections
`31.7.3 Comments
`3 1.B 1 Summary
`chap•er 12 Creating a document
`type definition
`3 2.1 1 Document type declaration
`3 2.2 1 Internal and external subset
`32.3 1 Element type declarations
`32.4 1 Element type content specification
`32.4.1 Empty content
`32.4.2 ANY content
`32.4.3 Mixed content
`32.5 1 Content models
`n.6 1 Attributes
`32.6.1 Attribute-list declarations
`32.6.2 Attribute defaults
`32.6.3 Attribute types
`32.6.3.1 Attribute value normalization
`32.6.3.2 CDATA and name token attributes
`32.6.3.3 Enumerated and notation attributes
`32.6.3.4 10 and IDREF attributes
`
`©!998 T H E XML HANDBOOKTM
`
`CONTENTS
`
`XXIX
`
`438
`439
`440
`440
`441
`441
`
`441
`442
`
`444
`
`446
`
`447
`
`448
`
`450
`
`452
`
`455
`
`456
`
`457
`457
`
`458
`
`459
`
`462
`463
`
`464
`
`466
`467
`468
`470
`470
`
`

`

`XXX
`
`CONTENTS
`
`32.6.3.5 ENTITY attributes
`32.6.3.6 Summary of attribute types
`12.7 1 Notation Declarations
`Chap•er ;~;~ Entities: Breaking up
`is easy to do
`()vervievv
`11.1
`u.2 1 Entity details
`11.1 1 Classifications of entities
`11.4 1 Internal general entities
`u.s 1 External parsed general entities
`33.5.1 External parsed entity support is optional
`11.cs 1 U nparsed entities
`11.7 1 Internal and exte1nal parameter entities
`11.a 1 Markup may not span entity boundalies
`33.8.1 Legal parameter entity reference
`u.9 1 External identifiers
`33.9.1 System identifiers
`33.9.2 Public identifiers
`u.1 o 1 Conclusion
`Chap•er i4 XML Linking Language(Xlink
`14.1 1 Basic concepts
`34.1.1 Simple links
`34.1.2 Link roles
`34.1.3 Is this for real?
`34.1.4 Link behaviors
`34.1.4.1 Show
`34.1.5 Actuate
`34.1.6 Behavior
`
`472
`473
`
`474
`
`476
`
`477
`
`481
`
`482
`
`483
`
`485
`
`485
`
`486
`
`487
`
`490
`
`493
`
`494
`
`495
`
`495
`
`496
`
`498
`
`5oo
`
`501
`
`502
`
`504
`
`505
`506
`
`508
`
`508
`
`©1998 THE XML HANDBOOK™
`
`

`

`34.:1 1 Extended links
`34•2•1 Locator elements
`34.2.2 Link groups
`34•3 1 Addressing
`34•4 1 Uniform Resource Identifier (URI)
`34•5 1 Referring to IDs
`34•6 1 Location terms
`34.7 1 Conclusion
`chap~er :~s Extensible Style
`Language (XSL)
`35.1 1 XSL overview
`35.1.1 XSL stylesheets
`35.:1 1 Referencing XSL stylesheets
`35.3 1 Ru1es, patterns and actions
`35.4 1 Flow Objects
`35.5 1 UsingXSL
`u.6 1 Patterns
`u.7 1 Actions
`u.s 1 Flow objects and characteristics
`u.9 1 XSL and JavaScript
`Chap~er :~o Adva.,.ced features
`36.1 1 Conditional sections
`36.1 1 Character references
`36.3 1 Processing mstructions
`36.4 1 Standalone document declaration
`36