| Revision as of 21:33, 14 November 2008 editJamwod (talk | contribs)36 edits Correcting some typos and making this modelling analysis more true to reality,ie, where word processing docs and xml are used, rather than PDF← 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 |
| (37 intermediate revisions by 24 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 realm 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 '''document templates''' evidenced most often as word-processing documents, fillable ] forms and, more recently, XML templates. The particular strength of XML in this context is its ability to model document components in a tree-like structure, and its separation of content and style. |
|
|
|
|
|
|
|
{{Rcat shell| |
|
Document modelling goes beyond mere form-filling and mail-merge to look at the structure of information in, for example, a legal document, a contract, an inspection report, or some form of analysis. |
|
|
|
{{R with history}} |
|
|
|
|
|
}} |
|
Document modelling therefore 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. Without effective document modelling, it is difficult to get full value from a document automation initiative, for example, using document assembly software. But by using a model that contains 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. |
|
|
|
|
|
==External links== |
|
|
|
|
|
|
|
|
|
|
|
Basha Systems LLC, ] 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, ] Tip Archives are accessible through the for: |
|
|
* , |
|
|
* , and |
|
|
* . |
|
|
|
|
|
] |
|