"This manifesto for the document engineering revolution gives you the what, the why, and
the how of automating your business processes with XML, leading to greater cost savings,
higher quality, and more flexibility."
--Hal Varian, Haas School of Business and Department of Economics, University of California, Berkeley
(excerpt from The Rockley Bulletin )"...To help readers understand DOCUMENT ENGINEERING, Glushko and McGrath take great pains to carefully describe concepts, define terminology, and provide real world examples. They use the first six chapters to set the stage for their paradigm-shifting approach, covering topics including XML, HTML, web browsers, metadata, business patterns, business processes, business architecture, and interoperability -- all critical elements of understanding the changes needed to think about documents as interfaces. It's an easy read and full of useful examples...
If you are a content management professional, technical writer, editor, marketing strategist, business analyst, or information manager of any type, Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services is a "must read" addition to your library. But, just don't order the book -- read it! ...
--The Rockley Group helps content managers and authors meet the increasing demands of creating, distributing and managing the content they create.
"Today, information technology is evolving so rapidly that the industry struggles to keep pace.
This book explains the core concepts facing IT workers with respect to engineering data at both
the atomic and aggregate (document) levels. It also tackles interoperability and multiple expressions
of data at the meta and instance levels. This book should become the bible for document and data model
engineering and should be required reading for all current IT workers - period!"
--Duane Allan Nickull,Vice Chair, United Nations Centre for Trade Facilitation and Electronic Business, and Senior Standards Strategist, Adobe Systems
(excerpt from weblog )"...The status of all well-formed XML as both data and documents is something that Glushko and McGrath take very seriously, and they've studied engineering techniques from both the business transaction and the publishing worlds to help the reader address issues in both ends of the spectrum and in the many cases in between....
While the book will be very useful for business process people who want to learn more about the processing of non-relational data, it will be just as valuable to data people who want to understand the different classes of business processes, the different levels of abstraction used to discuss them, and potential interactions between them...
Consultants who need to repeatedly perform business process analysis and related document workflow analysis at multiple clients will find this book to be particularly helpful, both to educate themselves and their clients... "
--Bob DuCharme, XML, XSL, and publishing consultant and author
"Digital documents are at the heart of eCommerce. That's why DOCUMENT ENGINEERING is so important: it's a book that offers a balanced,
readable guide to the conceptual and pragmatic aspects of the new holy
grail, information architecture. All too often, heuristics for designing
and implementing structured digital documents are simply enumerated;
there's little attention given to the underlying motivation and
rationale for the evolution of standards, platforms, and best practices.
But DOCUMENT ENGINEERING doesn't just tell you how; it tells you why.
And it's that "why" that makes all the difference.
Glushko and McGrath emphasize many of the important real-world
constraints on design: that work, technology, and documents are always
changing; that every level of document engineering is worthy of a
thoughtful approach; and that it's just as important to get the
conceptual and physical models right as it is to come up with a working
implementation. The book is rich with examples for the design
practitioner, but it's also worthwhile reading for anyone who harbors an
intellectual curiosity about what's going on behind the scenes of our
digital infrastructure. "
--Cathy Marshall, Senior Researcher and "Document Theorist," Microsoft
(excerpt from the book's foreword) -- "Documents have long been important, but HTML and the World Wide Web dramatically increase their value. They've accelerated document exchange and emphasized the need for structures and discipline. These structures and disciplines are what Document Engineering is about...
We seem to have ten times as many ways of representing information as of processing it. Glushko and McGrath have laid down an organized approach to identify the key documents, canonize their representations and leverage these to solve the larger problem...
The journey is, indeed, the proverbial thousand miles; this book has begun it with well more than the usual single step. Fortunately, we don't have to reach the final destination to reap substantial rewards."
--David Cohn, Director Business Informatics, IBM Research
"This book fills the gap between the useful new technologies of XML, which enable applications to interchange structured data, and the question where the models of this data should come from. Seen from this perspective, the XML revolution still is in its infancy. XML is mostly designed ad-hoc and on the markup level, while a true document engineering approach should be based on more abstract models which could then be mapped to more concrete structures such as XML markup. This book paves the path so that more people will see XML technologies in the larger context of modeling."
--Erik Wilde, Computer Engineering and Networks Laboratory (tik) Swiss Federal Institute of Technology, Zurich (ethz)
"DOCUMENT ENGINEERING provides a common-sense approach to designing the documents used in
service oriented architectures. Well-written and packed with examples, it is useful reading
for architects, developers, and managers."
--Ron Bourret, XML and Databases Consultant
"The history of civilization is in no small part the history of documents -- it is the history of how complex social orders are made possible through the creation of complex webs of documents which link people together in ever more sophisticated ways. Glushko and McGrath have described a new chapter in this evolutionary story, describing how documents themselves are becoming transformed as they become entangled in new kinds of (computational) webs."
--Barry Smith, Department of Philosophy, State University of New York at Buffalo
(excerpt from O'ReillyNet) -- "Bob Glushko and Tim McGrath's standout new book DOCUMENT ENGINEERING applies a dataflow approach to the whole organization, identifying and modeling which documents get sent between business processes and their contents. ...It's not Software Engineering, it's not IT, it's not web publishing, it's not Enterprise Architecture, it's not Business Process Re-engineering, but it straddles all these... Practical, well-expressed and timely -- I recommend it for anyone involved in adopting a highly-automated, loosely-coupled Service Oriented Architecture."
--Rick Jelliffe, Standards Activist and CTO, Topologi Pty. Ltd.
"DOCUMENT ENGINEERING provides a systematic approach to build robust business processes from XML-aware and compliant documents. Armed with this approach, companies in a wide range of industries can develop new ways to serve customers, more efficient ways to leverage suppliers, and become more agile and adaptive as their circumstances change."
--Henry Chesbrough, Director, Center for Open Innovation, University of California, Berkeley
"Component modeling, analysis of information exchanges, and application services usage patterns are critical areas to focus on in designing internal and external interfaces exposed by enterprises, ASPs/SaaS, and other consumer-oriented internet services. These areas covered in DOCUMENT ENGINEERING are very relevant to architects, product managers, developers and technology executives. I especially found the design patterns and process discussion helpful. I would recommend this book to anyone interested in services oriented application platforms, internal and external enterprise integration to employ in the design phase since it covers an effective methodology of designing interfaces based on the document-centric component model.."
-- Zahid Ahmed, Web Services API Platform/3rd Party Integration Architect, eBay, Inc.
"Document automation in any industry not only requires the use and design
of XML standards but also the understanding of methodologies,
architectures, and business processes. DOCUMENT ENGINEERING provides an
interdisciplinary framework incorporating all these aspects, which are
essential for building successful service oriented applications. I'd
highly recommend it for business/operations specialists, technical
architects, and managers."
--Marc Gratacos, XML Specialist, International Swaps and Derivatives Association
DOCUMENT ENGINEERING is a practical exploration of the role documents play in the nexus of contracts that drive modern businesses. The interdisciplinary approach put forward here, taking document engineering out of the realm of pure software engineering, is eye opening and provides some real insight into what it takes to make Service Oriented Architectures work in the real world. This is an absolute must read book for anyone seriously considering developing an XML based document integration strategy. "
--Ben Wolin, Director of Engineering, Bricsnet Corporation
(excerpt from IBM Developer Works blog)
I am the happy owner of an excellent new book entitled DOCUMENT ENGINEERING by Robert Glushko and Tim McGrath. The reader goes on journey through many of the XML technologies that are brought to bear to solve business informatics problems. The journey does not jostle and stab with so many pointy brackets, but rather focuses intently on why we need all of these technologies and how to put them together sensibly.
There are so many nuggets of wisdom in the book that of course I cannot tell you all about it in this blog. Just like the Matrix, you have to see it for yourself!
--John Boyer, Senior Product Architect for IBM Workplace Forms
(excerpt from Amazon) -- "At the end of the day, business success comes down to three things: a product, the market, and the business processes. The business processes consist of people, tools and workflow. You can have a great product in a great market but if you have bad business processes you can forget about it. So how do you go from a manual data collection process to an automated data collection process? I continuously refer to DOCUMENT ENGINEERING for insights on how to develop a clear plan on how to implement a data collection infrastructure that will help to more effectively manage business processes.
-- D. Sunderhaft