Misplaced Pages

Document modelling: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 21:19, 14 November 2008 editJamwod (talk | contribs)36 edits External links← 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 
(39 intermediate revisions by 25 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 '''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.

==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
* .

]

Latest revision as of 23:29, 20 May 2024

Redirect to:

This page is a redirect. The following categories are used to track and monitor this redirect:
  • With history: This is a redirect from a page containing substantive page history. This page is kept as a redirect to preserve its former content and attributions. Please do not remove the tag that generates this text (unless the need to recreate content on this page has been demonstrated), nor delete this page.
    • This template should not be used for redirects having some edit history but no meaningful content in their previous versions, nor for redirects created as a result of a page merge (use {{R from merge}} instead), nor for redirects from a title that forms a historic part of Misplaced Pages (use {{R with old history}} instead).
When appropriate, protection levels are automatically sensed, described and categorized.