Harmonization Indicator for Context-Specific Data Component Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The lack of uniform and standardized methods for representing business data structures and semantics in electronic commerce leads to difficulties in exchanging business documents between parties without prior coordination and manual mapping, despite the existence of standards like ebXML Core Components Technical Specification (CCTS), which does not address non-uniform semantics and structure issues.
Innovation Solution
A method is introduced to create context-independent data types with harmonization indicators that determine the inclusion of data elements in specific contexts, allowing for explicit inclusion or exclusion of data elements, and enabling context-specific editing and management of data components, aligning with CCTS-based context categories.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If CCTS-based core components are used to standardize business data representation, then syntax uniformity and machine processing capability are improved, but semantic non-uniformity and structural variety remain unresolved
Solution Approach 1:
The patent segments the data component into multiple data elements, each with its own harmonization indicator. This allows the system to handle semantic variety at the element level while maintaining overall syntax uniformity through the standardized data type structure.
Solution Approach 2:
The patent introduces harmonization indicators as parameters associated with each data element. By changing the state of these indicators (set or not set), the system dynamically controls inclusion/exclusion of data elements based on context, resolving the contradiction between uniformity and adaptability.
2Adaptability or versatility
If manual mapping between different document structures is performed to enable document exchange, then compatibility between business partners is improved, but time consumption and operational complexity increase
Solution Approach 1:
The patent performs preliminary actions by pre-defining data types with data elements and harmonization indicators in a standardized framework. This preliminary structuring eliminates the need for manual mapping during actual document exchange, as the harmonization indicators automatically handle context-specific inclusion/exclusion.
Solution Approach 2:
The patent introduces harmonization indicators as intermediaries between the standardized data type and context-specific requirements. These indicators act as mediators that automatically determine which data elements should be included or excluded based on the target context, replacing manual mapping operations.
3Adaptability or versatility
If context-specific data components are created from a standardized data type, then adaptability to different business contexts is improved, but control over data element inclusion becomes complex
Solution Approach 1:
The patent applies local quality by assigning individual harmonization indicators to each data element. This allows granular control at the local element level rather than requiring complex global control mechanisms, simplifying the management of context-specific inclusions and exclusions.
Data Source
AI summary
Data elements for a data component are specified by creating a data type that includes several data elements, the data type to be used in creating data components for specific contexts. Each of the several data elements is associated with a harmonization indicator that causes the associated data element to be included, or not included, in the data components for any of the specific contexts. A method of performing a predefined operation on a data component includes receiving a user input specifying at least one context value for performing a predefined operation on a data component for a specific context characterized by the at least one context value. The predefined operation is performed using a harmonization indicator included in a data type that is context independent. Data components are used in software components or application components.