| Revision as of 14:24, 28 April 2007 editSmackBot (talk | contribs)3,734,324 editsm Date/fix the maintenance tags or gen fixes← Previous edit | Revision as of 19:09, 1 March 2008 edit undo24.175.196.192 (talk) fixed typoNext edit → | ||
| Line 1: | Line 1: | ||
| {{Orphan|date=September 2006}} | {{Orphan|date=September 2006}} | ||
| '''Document Modelling''' looks at the inherent structure in documents. It looks not at the structure in '''formatting''' which is the classic real of word-processing tools, but at the structure in content. Because document content is typically |
'''Document Modelling''' looks at the inherent structure in documents. It looks not at the structure in '''formatting''' which is the classic real of word-processing tools, but at the structure in content. Because document content is typically viewed as the '''ad hoc''' result of a creative process, the art of document modelling is still in its infancy. Most document modelling comes in the form of '''form templates''' evidenced most often as fillable ] or ] forms. These provide a form of structured data which is set in the visual context of a document. | ||
| Document modelling goes beyond mere form-filling to look at the structure of information in, for example, a legal document, an inspection report, or some form of analysis. By using tagging (similar to XML tagging) information can be sliced into different subjects and addressed in a form different from the actual form of the document. For example, using a document model, you can take a 50 page negotiated lease (if properly tagged) and produce a lease abstract merely by using the appropriately designed XLT file. | Document modelling goes beyond mere form-filling to look at the structure of information in, for example, a legal document, an inspection report, or some form of analysis. By using tagging (similar to XML tagging) information can be sliced into different subjects and addressed in a form different from the actual form of the document. For example, using a document model, you can take a 50 page negotiated lease (if properly tagged) and produce a lease abstract merely by using the appropriately designed XLT file. | ||
Revision as of 19:09, 1 March 2008
 | This article is an orphan, as no other articles link to it. Please introduce links to this page from related articles; try the Find link tool for suggestions. (September 2006) |
Document Modelling looks at the inherent structure in documents. It looks not at the structure in formatting which is the classic real of word-processing tools, but at the structure in content. Because document content is typically viewed as the ad hoc result of a creative process, the art of document modelling is still in its infancy. Most document modelling comes in the form of form templates evidenced most often as fillable PDF or Acrobat forms. These provide a form of structured data which is set in the visual context of a document.
Document modelling goes beyond mere form-filling to look at the structure of information in, for example, a legal document, an inspection report, or some form of analysis. By using tagging (similar to XML tagging) information can be sliced into different subjects and addressed in a form different from the actual form of the document. For example, using a document model, you can take a 50 page negotiated lease (if properly tagged) and produce a lease abstract merely by using the appropriately designed XLT file.
Document Modelling therefor looks at the structures and patterns of the written work, and breaks it down into different options or branches. It then labels the branches and the results. Document Assembly software presumes document modelling to work best. By using a model that contents hundreds and thousands of branches, a user can create close to infinite structured variations almost to the point that such systems can rival the unstructured drafting of a specialist. In fact, the results of a sophisticated document model can surpass those of the specialist in terms of lack of error and consistency of prose.
qSHIFT from Ixio has set forth perhaps the best web-based tool which is based on the document modelling paradigm. It allows the user to break up the document into paragraph and phrases into a branch and tree shaped model. The user can then use rule-constrained assembly or a pure manual selection to turn these models into finished products.
External links
Basha Systems LLC, Document Automation Articles by Seth Rowland, Esq. and Rose Rowland; Document Automation Article Index
Seth Rowland has a blog dedicated to issues regarding document automation methods as well as developments in the document automation industry called Document Assembly (and Case Management)
In addition, Document Automation Tip Archives are accessible through the Basha Systems LLC Information Portal for:
- HotDocs,
- Time Matters, and
- GhostFill.