Context-Dependent Data Element Property Identification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data element standards, such as UN/CEFACT's Core Components Technical Specification, lack the ability to effectively represent and manage context-dependent properties in electronic communications, leading to inefficiencies in identifying and defining relevant data elements for specific business contexts.

Innovation Solution

A computer-implemented method and system that evaluates logical rules to identify and define properties of data elements based on context values, using an ontology and reasoner to determine valid properties for specified contexts, enabling intuitive, maintainable, and expressive context dependency management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional data element standards (UN/CEFACT Core Components) are used, then data standardization is achieved, but context-dependent property management capability is lost

Engineering Contradiction:
Improvecontext-dependent property managementVSAvoidbusiness context information
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent segments the data element model into multiple hierarchical levels: core components (generic), business information entities (context-specific), and properties (context-dependent). This segmentation allows the system to maintain generic data structures while adding context-specific properties through logical rules that activate only in relevant business contexts, thus recovering context information without sacrificing standardization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces dynamic property management where properties are not statically defined but dynamically determined through logical rules evaluated against business context. The system can adaptively add, remove, or modify properties based on context values (e.g., industry, country, business role), enabling the data model to be flexible and context-aware while maintaining a stable core structure.

Inventive Principle:
Principle #15Dynamics

2Loss of information

If context-specific properties are added to data elements, then business context representation is improved, but system complexity increases

Engineering Contradiction:
Improvebusiness context representationVSAvoidsystem complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent introduces logical rules as intermediaries between the core data element structure and context-specific properties. These rules act as a mediation layer that automatically determines which properties apply in which contexts, eliminating the need for manual configuration and reducing system complexity. The rules evaluate context values and dynamically activate appropriate properties without requiring complex hard-coded logic.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements self-service through automatic rule evaluation and property activation. When business context information is provided, the system automatically evaluates logical rules and activates the appropriate properties without requiring manual intervention or complex configuration management. This self-service mechanism reduces operational complexity while maintaining comprehensive context representation.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If manual property definition is used, then flexibility is achieved, but identification efficiency decreases

Engineering Contradiction:
Improveproperty definition flexibilityVSAvoidproperty identification efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent applies preliminary action by pre-defining logical rules that encode property-definition logic before runtime. These rules are established in advance and automatically evaluated when business context is provided, eliminating the need for manual property identification during implementation. The system pre-processes context information and automatically determines applicable properties, significantly improving identification efficiency while maintaining flexibility.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where logical rules continuously evaluate business context values and automatically adjust property definitions accordingly. This feedback loop ensures that the correct properties are identified and activated based on the specific business context, providing both automation (improving efficiency) and adaptability (maintaining flexibility) without manual intervention.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8078568B2Properties of data elements
Publication Date: 2011.12.13 SAP SE
  • US8078568B2 patent drawing
  • US8078568B2 patent drawing
  • US8078568B2 patent drawing

AI summary

Methods and computer program products relating to properties of data elements. A computer-implemented method for identifying a property of a data element includes receiving a request for at least one sought property of a data element. The data element is configured for use in semantically identifying information portions in electronic communications. The sought property is to be valid in a context defined by at least one context value indicated by the request. The method includes identifying the at least one sought property by evaluating at least one logical rule that defines at least one property of the data element as being valid for a specified context. The method includes generating an output in response to the request that indicates the at least one sought property.