Overlay Rule Integration with Hidden Metadata for Document Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing document creation systems fail to maintain associations between document fragments and the rules that select them, leading to complex and resource-intensive migrations when rules become unavailable or proprietary, hindering the porting of documents to new systems.
Innovation Solution
Embedding rule identifiers in document fragments as hidden metadata, allowing systems to extract and share rules across disparate systems, enabling flexible and transparent content generation with customizable rules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If rules are stored as machine code in proprietary formats, then document generation can be secured and controlled, but the rules become unavailable for porting and require manual rebuilding
Solution Approach 1:
The patent introduces a rule identifier as an intermediary element that bridges the gap between proprietary machine code rules and human-readable documentation. The rule identifier acts as a mediator that can be extracted from the machine code and used to reference rules in human-readable formats, enabling porting without requiring manual rebuilding while maintaining security
Solution Approach 2:
The patent enables copying of rules by extracting rule identifiers from machine code and creating references to human-readable rule definitions. This allows rules to be copied between systems through documentation rather than direct code transfer, facilitating porting while maintaining the original machine code security
2Adaptability or versatility
If rules are maintained in proprietary formats, then system-specific control is achieved, but sharing rules across disparate systems becomes complex and resource-intensive
Solution Approach 1:
The patent segments the rule system into separate components: machine code for execution, rule identifiers for reference, and human-readable definitions for documentation. This segmentation allows each component to serve its specific purpose independently, enabling rule sharing across systems without requiring migration of the entire proprietary format
Solution Approach 2:
The rule identifier serves multiple functions: it identifies rules in machine code, references rules in human-readable formats, and enables sharing across disparate systems. This multi-functionality reduces migration complexity by providing a universal reference mechanism that works across different system formats
3Productivity
If no association is maintained between document fragments and rules, then document generation is simpler, but migration requires manual rebuilding of all rules
Solution Approach 1:
The patent performs preliminary action by embedding rule identifiers into document fragments during the initial document generation process. This ensures that the association information is captured before migration is needed, allowing rapid migration by simply transferring the documented rules with their associated identifiers rather than manual rebuilding
4Ease of operation
If rules are embedded in machine code, then execution efficiency is maintained, but human-readable documentation and customization become difficult
Solution Approach 1:
The patent extracts rule identifiers from machine code without extracting the executable machine code itself. This allows human-readable documentation and customization by referencing the extracted identifiers, while maintaining execution efficiency by keeping the machine code intact and only extracting the identification information
Data Source
AI summary
Documents are often generated using a customer communication management (CCM) application that utilizes rules to select and/or modify certain fragments of a document. By analyzing the rules and content that produced a certain fragment, a second CCM application may be automatically provided with the rules, such as when the first set of rules are not available for porting to a second system. Accordingly, a server may access a rule comprising a condition, a document fragment, and a rule identifier. A server may generate a first document to comprise visible content and hidden content. Generating the first document may comprise evaluating the rule and, when the rule is true, including the document fragment as a portion of the visible content and including the rule identifier as a portion of hidden content. A server may provide the first document to a destination.