| Revision as of 02:00, 13 March 2008 editKjq (talk | contribs)10 editsNo edit summary← Previous edit |
Latest revision as of 23:29, 20 May 2024 edit undoRomeshKubajali (talk | contribs)Extended confirmed users515 edits Blanked and redirected to Database model. See talk for rationale.Tag: New redirect |
| (44 intermediate revisions by 28 users not shown) |
| Line 1: |
Line 1: |
|
|
#REDIRECT ] |
|
'''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. |
|
|
|
|
|
|
|
{{Rcat shell| |
|
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. |
|
|
|
{{R with history}} |
|
|
|
|
|
}} |
|
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. |
|
|
|
|
|
] from ] 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. |
|
|
|
|
|
from has a product which creates a truly "]". Documents created with their tools dynamically regenerate themselves when a user changes data right in the document. Those changes, to data or the document, can also be synchronized back to a datasource thus reducing the need for an additional third-party data-entry, business rules, or reporting application. All of this is done using only Microsoft Office (it also works with Excel) and no other special software. |
|
|
|
|
|
==External links== |
|
|
|
|
|
|
|
|
|
|
|
Basha Systems LLC, Document Automation Articles by Seth Rowland, Esq. and Rose Rowland; |
|
|
|
|
|
Seth Rowland has a blog dedicated to issues regarding document automation methods as well as developments in the document automation industry called |
|
|
|
|
|
In addition, Document Automation Tip Archives are accessible through the for: |
|
|
* , |
|
|
* , and |
|
|
* . |
|
|
|
|
|
] |
|