Comments on: Document Engineering: A Logical Career Move For Some Business Content Pros http://thecontentwrangler.com/2008/12/15/document_engineering_a_logical_career_move_for_some_business_content_pros/ Content is a business asset worthy of being managed Fri, 10 Feb 2012 16:31:44 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Stefani http://thecontentwrangler.com/2008/12/15/document_engineering_a_logical_career_move_for_some_business_content_pros/comment-page-1/#comment-453 Stefani Wed, 24 Dec 2008 09:21:39 +0000 http://localhost:8888/ee/?p=300#comment-453 <p>Nice review. Your review gives a very clear picture of the book and I am interested. I will read this book very soon. </p> Nice review. Your review gives a very clear picture of the book and I am interested. I will read this book very soon.

]]> By: Doctor Doc http://thecontentwrangler.com/2008/12/15/document_engineering_a_logical_career_move_for_some_business_content_pros/comment-page-1/#comment-452 Doctor Doc Tue, 16 Dec 2008 05:07:06 +0000 http://localhost:8888/ee/?p=300#comment-452 <p>Too brief an article for me to get the full gist; will get the book. One of the things I’ve long evangelized to my legal clients is to adhere to contracts that are standard in text, formatting, naming conventions. You’d be surprised at how many lawyers at the same companies and firms still build their drafts in Microsoft Word, rather than using a form-based approach. As a result, after contracts are executed, they are saddled with a task they rarely follow through on: Extracting the metadata relating to their contractual agreements. Lawyers: Metadata should be extracted during the document authoring phase—that’s a document engineering feat you will appreciate. </p> Too brief an article for me to get the full gist; will get the book. One of the things I’ve long evangelized to my legal clients is to adhere to contracts that are standard in text, formatting, naming conventions. You’d be surprised at how many lawyers at the same companies and firms still build their drafts in Microsoft Word, rather than using a form-based approach. As a result, after contracts are executed, they are saddled with a task they rarely follow through on: Extracting the metadata relating to their contractual agreements. Lawyers: Metadata should be extracted during the document authoring phase—that’s a document engineering feat you will appreciate.

]]> By: Tony Chung http://thecontentwrangler.com/2008/12/15/document_engineering_a_logical_career_move_for_some_business_content_pros/comment-page-1/#comment-451 Tony Chung Mon, 15 Dec 2008 21:28:18 +0000 http://localhost:8888/ee/?p=300#comment-451 <p>Lisa: I bought this book with every intention of reading it, after being completely blown away by Bob’s presentation at DocTrain West. His depth of study and insight into the art of the transaction was engaging, and on some levels, even refreshing. </p> <p> The title “Document Engineering” is a misnomer, especially because as you said, every record used for information transfer is considered a document. In his examples the document isn’t the be-all end-all as we TCs have long thought. Rather, they are as transitory as post-it notes, and to succeed in this venture we must tread into the waters of usability engineering at the same time. </p> <p> Sadly, the rampant typos in my copy made me put the book down for a moment, in which time a variety of work projects lined up to occupy my time and take me further from the material, even though I am interested in the concept. I can see from your synopsis that all that good stuff is just ahead of my bookmark. And so I shall carry on. </p> <p> Thank you for your review, because it inspires me to let the typos be like creative spice that enhances the flavour of the meat, rather than a peculiar taste that I have to force down in order to be a good example to my kids. </p> Lisa: I bought this book with every intention of reading it, after being completely blown away by Bob’s presentation at DocTrain West. His depth of study and insight into the art of the transaction was engaging, and on some levels, even refreshing.

The title “Document Engineering” is a misnomer, especially because as you said, every record used for information transfer is considered a document. In his examples the document isn’t the be-all end-all as we TCs have long thought. Rather, they are as transitory as post-it notes, and to succeed in this venture we must tread into the waters of usability engineering at the same time.

Sadly, the rampant typos in my copy made me put the book down for a moment, in which time a variety of work projects lined up to occupy my time and take me further from the material, even though I am interested in the concept. I can see from your synopsis that all that good stuff is just ahead of my bookmark. And so I shall carry on.

Thank you for your review, because it inspires me to let the typos be like creative spice that enhances the flavour of the meat, rather than a peculiar taste that I have to force down in order to be a good example to my kids.

]]>