| |
| |
| Preface | |
| |
| |
| Acknowledgments | |
| |
| |
| |
| MAJOR THEMES | |
| |
| |
| Introduction | |
| |
| |
| Who Are You? | |
| |
| |
| This Book is Distinctive Because | |
| |
| |
| Road Map | |
| |
| |
| |
| Why XML | |
| |
| |
| W3C Agenda for XML | |
| |
| |
| W3C Goals for XML | |
| |
| |
| Isn''t the Web Another Strong Motivator for XML? | |
| |
| |
| |
| |
| |
| Decision Maker''s Problem | |
| |
| |
| Snapshot of the Terminology Chaos | |
| |
| |
| Look at Me First | |
| |
| |
| Ten Questions About XML that a Manager Should Ask | |
| |
| |
| |
| What''s the Really Big Idea? | |
| |
| |
| The Big Idea. Computer-Recognizable Content | |
| |
| |
| Author''s (Embarrassing) Lesson Learned | |
| |
| |
| 4 | |
| |
| |
| Why Digital? | |
| |
| |
| Why Open Systems? | |
| |
| |
| So What''s the Problem? | |
| |
| |
| So What''s the Solution? | |
| |
| |
| Content as Categories | |
| |
| |
| Content as Structured Data | |
| |
| |
| Separation of Structure and Appearance | |
| |
| |
| |
| XML as Workflow | |
| |
| |
| Electronic Content: Content in Motion | |
| |
| |
| XML Is Communication | |
| |
| |
| XML as the Total Solution: Reality Check | |
| |
| |
| Translation and Transformation | |
| |
| |
| So What Has XML Bought Us? | |
| |
| |
| |
| XML as Knowledge | |
| |
| |
| Markup Knowledge | |
| |
| |
| Hierarchies to Express Relationships | |
| |
| |
| Markup''s Value Added | |
| |
| |
| Easier Interpretation: XML as Exposed Content | |
| |
| |
| More Intelligent Searches | |
| |
| |
| |
| Core Technologies | |
| |
| |
| |
| Elements and Attributes to Expose Content | |
| |
| |
| Need for Elements | |
| |
| |
| Element as a Basic Unit of XML | |
| |
| |
| Deeper Knowledge Exposure | |
| |
| |
| Advantages of Elements and Attributes | |
| |
| |
| Five Ways Elements and Attributes Add Value to Information | |
| |
| |
| |
| Getting Personal-Attributes | |
| |
| |
| Two Faces of Attributes | |
| |
| |
| Case: Business rules for Investment Records | |
| |
| |
| Attribute Mechanics (Syntax) | |
| |
| |
| Seven Business Aspects of Attributes | |
| |
| |
| |
| Well-formed XML | |
| |
| |
| Self-Exposing Mixed Content? | |
| |
| |
| Lowering One Bar. Not Just "Good Enough" But Pretty Good | |
| |
| |
| "Good Enough" XML | |
| |
| |
| Case: Repository for State Laws | |
| |
| |
| Where''s the Catch? | |
| |
| |
| Seven Reasons Why Well-Formedness Makes Business Sense | |
| |
| |
| |
| Why a Type Definition? | |
| |
| |
| Need for Structure Definition in Large Systems | |
| |
| |
| Document type: Working Definition | |
| |
| |
| Something''s "Under the Hood" | |
| |
| |
| A Talking Document Type. Five Reasons Why Schemas Make Good Business Sense | |
| |
| |
| |
| The Self-Describing XML Tree | |
| |
| |
| Why Should I Bother with DTDs? | |
| |
| |
| How a DTD Works | |
| |
| |
| Assessing the DTD | |
| |
| |
| |
| XML Schemas | |
| |
| |
| Why Should I Bother? | |
| |
| |
| How Does It Work? | |
| |
| |
| XML Namespaces in an XML Schema | |
| |
| |
| How the Schema Describes Structure | |
| |
| |
| The Beauty of Namespaces. Schema-aware Tools | |
| |
| |
| As The Specification Says� Four Reasons why XML Schema Makes Good Sense | |
| |
| |
| |
| Entities | |
| |
| |
| The Indispensable Layer: Why? | |
| |
| |
| How does It Work? | |
| |
| |
| Entities of Distributed Content: One-to-Many | |
| |
| |
| Executive Talkthrough. Unparsed entities for non-XML Data | |
| |
| |
| How Do You Create Entities? Entities as Reusable Objects | |
| |
| |
| If No Entities Then What? | |
| |
| |
| |
| As The Specification Says� Eight Reasons Why Entities Make Good Business Sense12<l>14</l> | |
| |
| |
| Why Do I Need Yet More Notation? | |
| |
| |
| How Does It Work? | |
| |
| |
| Essential Syntax | |
| |
| |
| Selecting Nodes: Location Paths and Location Steps | |
| |
| |
| XPath Meets the Bard | |
| |
| |
| As The Specification Says� Four Reasons Why XPath Makes Good Business Sense | |
| |
| |
| |
| XML Namespaces | |
| |
| |
| XML for Serious Work | |
| |
| |
| How Does It Work? | |
| |
| |
| The Syntax | |
| |
| |
| As the Specification Says� Five Reasons Why Namespaces Make Good Sense | |
| |
| |
| |
| Transforming Your Data with XSLT | |
| |
| |
| Why Do I Need XSLT? | |
| |
| |
| How does It Work? | |
| |
| |
| XSLT in the IT Workplace | |
| |
| |
| Management Issues in Web Distribution | |
| |
| |
| XML as Data Islands | |
| |
| |
| Executive Talkthrough: Creating an HTML Data Island | |
| |
| |
| XSLT for More Exotic Data Islands | |
| |
| |
| Island Hopping with XSLT | |
| |
| |
| As the Specification Says� Five Reasons Why Even Elementary XSLT Transformations Make Sense | |
| |
| |
| |
| XSLT for Adaptive Content | |
| |
| |
| Unlock My System...Please! How Does It Work? | |
| |
| |
| Browser Wars Hit Data Island Beaches | |
| |
| |
| XSLT for Schema Translation | |
| |
| |
| Workflow Broken: Incompatible Schemas | |
| |
| |
| XSLT Transforms the Schema | |
| |
| |
| XSLT Transformation to Restore Original Structure | |
| |
| |
| XSLT and XSL-FO. As The Specification Says� Four More Good Reasons Why XSLT Makes Good Sense for Serious Data Exchange | |
| |
| |
| |
| XSL for Format | |
| |
| |
| No Style, No Content | |
| |
| |
| How Does It Work? | |
| |
| |
| Executive Orientation | |
| |
| |
| The Bookends | |
| |
| |
| XML to Beyond | |
| |
| |
| How Formatting Objects View a Page | |
| |
| |
| How To Build Formatting Objects that Really Format | |
| |
| |
| As the Specification Says� Five Reasons Why XML-FO Makes Good Business Sense | |
| |
| |
| |
| XLink and Xpointer | |
| |
| |
| Managing Links: A Battle We Can Never Win | |
| |
| |
| How Does It Work? Beyond the Web | |
| |
| |
| Proposed XML Solution | |
| |
| |
| DIGAM: Executive Talkthrough | |
| |
| |
| Digital Playlist: Executive Talkthrough | |
| |
| |
| Xpointer: Conjoined Twin of Hyperlinking | |
| |
| |
| As The Specification Says� Four Reasons Why XLink/Xpointer Make Good Business Sense | |
| |
| |
| |
| XML At Work | |
| |
| |
| |
| XML At Work: Manufacturing | |
| |
| |
| Using XML to Enhance Mature Manufacturing Technology | |
| |
| |
| What Does a BOM Contain? | |
| |
| |
| Who Uses the BOM? | |
| |
| |
| Summary of XML BOM | |
| |
| |
| |
| XML At Work: Extensible Business Reporting Language | |
| |
| |
| Abstract of the XBRL Specification | |
| |
| |
| Purpose of XBRL | |
| |
| |
| Taxonomies and XML Schema. Sample Report | |
| |
| |
| Adoption Curve | |
| |
| |
| |
| XML AT Work: Security | |
| |
| |
| Security in a Nutshell | |
| |
| |
| Use Case Studies | |
| |
| |
| Encryption | |
| |
| |
| Digital Signatures | |
| |
| |
| |
| XML At Work: Law and the Courts | |
| |
| |
| Michigan State Law | |
| |
| |
| LegalXML | |
| |
| |
| "Raw" XML on a Web Browser After All? | |
| |
| |
| |
| XML At Work: WAP & WML | |
| |
| |
| Wireless Markup Language | |
| |
| |
| Wireless Exhibit: Interactive Professional Training Planner | |
| |
| |
| Has WAP''s Time Come? | |
| |
| |
| |
| It''s Up to You: Ten Questions You Should Ask About XML | |
| |
| |
| Decision Maker''s List | |
| |
| |
| Index | |