XML Repository for Runtime Message Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems fail to provide synchronized and detailed documentation for runtime messages, leading to user confusion and inefficiency in addressing technical issues, as developers and documentors often work independently, and language inconsistencies complicate parameter formatting and sequencing across different environments.

Innovation Solution

A method and system utilizing an XML repository to store and manage runtime messages with unique IDs, allowing for easy access and synchronization of message content, including parameters, across different languages and environments, decoupling message content from source code and enabling versioning based on runtime conditions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If messages are included in user documentation separately from source code, then detailed explanations and remedial actions can be provided, but synchronization between documented messages and actual runtime messages becomes difficult

Engineering Contradiction:
Improvemessage documentation completenessVSAvoidmessage synchronization
Core Design Contradiction:
Loss of informationVSReliability

Solution Approach 1:

The patent merges message storage and documentation into a single XML repository structure. Message content, parameters, and documentation are combined in one location rather than separated, ensuring that the documentation always reflects the actual runtime messages since they share the same data source.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The XML repository serves multiple functions simultaneously: it stores runtime message content, maintains message parameters for localization, and provides documentation source material. This multi-functional approach eliminates the need for separate message files and documentation files, ensuring consistency across all uses.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If property files are used to store different language versions of message text, then runtime language selection is enabled, but documentation synchronization remains unresolved

Engineering Contradiction:
Improvelanguage supportVSAvoiddocumentation consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent adds a documentation dimension to the existing message storage structure by incorporating documentation elements directly within the XML message repository. This allows documentation to be retrieved and displayed alongside message content in the user's selected language, maintaining consistency across both message and documentation without requiring separate translation processes.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Adaptability or versatility

If parameters are formatted according to different language environments, then localized message display is achieved, but parameter sequencing consistency becomes problematic

Engineering Contradiction:
Improvelanguage localizationVSAvoidparameter sequence consistency
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The system dynamically adjusts parameter formatting and sequencing based on the user's language environment while maintaining a stable core parameter structure in the XML repository. The parameter definitions remain fixed in the repository, but their presentation format and order can adapt to locale requirements, resolving the conflict between stability and adaptability.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9189255B2System and methods for generating runtime messages
Publication Date: 2015.11.17 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US9189255B2 patent drawing
  • US9189255B2 patent drawing
  • US9189255B2 patent drawing

AI summary

A method for generating a runtime message of an application (20) comprising the steps of generating a unique message identification for the runtime message, generating a message content, providing an XML repository (30), which stores the unique message identification and the message content in an XML format and including a call for the message in the application (20) using the unique message identification so that the XML repository (30) is accessed during runtime for display of the message content.