Linked Resource Model for Digital Object Change Propagation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data management approaches fail to effectively consider the interdependencies between digital objects, leading to inadequate management of changes that can impact the usability and preservation of digital content over time, especially in environments subject to continuous change.

Innovation Solution

A Linked Resource Model (LRM) is introduced, where digital objects are represented as nodes in a graph with dependencies that include context-related information, allowing for the propagation of changes across the network based on intent and dependencies, using forward and backward chaining mechanisms to analyze and simulate the effects of changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If digital objects are managed individually without considering interdependencies, then management simplicity is improved, but change management effectiveness deteriorates

Engineering Contradiction:
Improvemanagement simplicityVSAvoidchange management effectiveness
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent merges individual digital object management into a unified dependency graph structure that captures relationships between objects. The system combines metadata from multiple objects into a graph where nodes represent digital objects and edges represent dependencies, enabling comprehensive change management that considers interdependencies while maintaining operational simplicity through automated propagation analysis.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The dependency graph serves as an intermediary structure between individual digital objects and the change management system. It mediates by capturing contextual relationships and enabling the propagation of change effects through predefined dependency paths, allowing the system to manage changes effectively without directly handling complex interobject relationships.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If contextual information and dependencies are captured for all digital objects, then change management capability is improved, but system complexity increases

Engineering Contradiction:
Improvechange management capabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the complex task of managing digital object relationships by dividing it into discrete dependency relationships captured in a graph structure. Each digital object is represented as a node with associated metadata, and relationships are represented as directed edges with specific dependency types, allowing the system to handle complexity through structured decomposition rather than monolithic management.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system changes the parameter representation from simple object metadata to a graph-based dependency structure with multiple attributes per relationship (dependency type, direction, strength). This parameter transformation enables sophisticated change management capabilities while managing complexity through standardized graph operations and automated propagation algorithms.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10762062B2Data governance: change management based on contextualized dependencies
Publication Date: 2020.09.01 GENESEE VALLEY INNOVATIONS LLC
  • US10762062B2 patent drawing
  • US10762062B2 patent drawing
  • US10762062B2 patent drawing

AI summary

A method for change management includes providing a dependency graph as an instantiation of a linked resource model in which a plurality of resources are linked by at least one dependency. The resources include at least one source resource and at least one target resource, each of the at least one dependency specifying preconditions on at least one of the at least one source resources for the dependency to be activated and an impact on at least one of the at least one target resources when the dependency is activated. A change to one of the plurality of resources is propagated to at least one other of the plurality of resources in the graph and information based on the propagation is output.