Reusable Clauses via Usage Tags and Master Document Logic
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems for generating customized documents using master templates face complexity and maintenance challenges due to intricate usage statements in clause files, which become error-prone and require frequent modifications when new master documents are introduced, embedding logic that is not master document-independent.
Innovation Solution
The solution involves replacing usage statements in clause files with generic usage tags, defining these tags in master documents, and using separate files for tag definitions and variable attribute descriptions, allowing different master documents to apply unique conditions to conditional content without embedding logic in clause files, thus maintaining a single clause file for each type.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If usage statements are embedded in clause files to control conditional content inclusion, then the system can generate customized documents according to specific conditions, but the clause files become complex and error-prone when new master documents are introduced
Solution Approach 1:
The patent separates the conditional logic into two distinct parts: usage tags embedded in clause files (simple placeholders) and usage statements defined in master documents (complex logic). This segmentation allows the clause files to remain simple while the master documents handle the complexity of conditional logic for different document types.
Solution Approach 2:
The patent introduces usage tags as intermediary elements that bridge clause files and master documents. These tags act as placeholders that reference usage statements defined elsewhere, allowing clause files to remain simple while enabling complex conditional control through the master document's usage statements.
2Adaptability or versatility
If usage statements are modified frequently to accommodate new master documents, then the system remains adaptable to different document types, but maintenance effort and error risk increase
Solution Approach 1:
The patent extracts the complex usage statements from clause files and places them in master documents where they are naturally defined based on document-specific requirements. This extraction means that when new master documents are introduced, only the master document needs to be created or modified, not the clause files, significantly reducing maintenance effort.
Solution Approach 2:
Instead of the conventional approach where clause files contain the logic and master documents reference them, the patent inverts the relationship: master documents contain the usage statements (logic) and clause files contain only simple usage tags (references). This inversion makes the system more maintainable as the complex logic is localized to specific master documents.
3Adaptability or versatility
If clause files contain embedded logic for different master documents, then each clause file can be customized, but the clause files lose independence and require frequent modifications
Solution Approach 1:
The patent makes usage tags universal elements that can be used in any clause file without containing document-specific logic. These tags serve multiple functions: they provide structure in clause files, reference usage statements in master documents, and enable conditional content selection. This universality maintains clause file independence while allowing customization through the master document's usage statements.
Data Source
AI summary
The present invention relates to the generation of customised documents using document templates and in particular to the generation of different types of customised documents including clauses or other portions of document content which are common to two or more types of customised document.