Digital Object Attribute Inheritance via Handle ID Naming

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing attributes for related digital objects within the Digital Object Architecture (DOA) is difficult and time-consuming, as updating attributes for a group of related digital objects requires individual updates to each handle record, leading to administrative overhead and resource consumption.

Innovation Solution

Implementing a method for attribute inheritance between related digital objects, where a child object automatically inherits attributes from its parent object using naming conventions or data models, reducing the need for individual updates and minimizing storage consumption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If individual handle records for each digital object are updated manually, then attribute accuracy is maintained, but administrative time and operational complexity increase significantly

Engineering Contradiction:
Improveattribute accuracyVSAvoidadministrative time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent merges multiple individual handle records into a hierarchical structure where parent objects can represent groups of child objects. By combining the update operation across multiple records through a single parent object reference, the system maintains attribute accuracy while dramatically reducing administrative time required for bulk updates.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The parent object handle record serves multiple functions: it represents an individual digital object while simultaneously representing a group of related child objects. This multi-functionality allows a single update operation to propagate attributes across multiple child objects, eliminating the need for individual updates while maintaining precision.

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

2Ease of operation

If individual handle records for each digital object are updated manually, then update control is maintained, but device complexity and operational difficulty increase

Engineering Contradiction:
Improveupdate controlVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments the update operation into two distinct levels: individual child object updates and parent object group updates. This segmentation allows users to choose the appropriate granularity for each update scenario, simplifying the user interface and operational流程 while maintaining the underlying complexity only where necessary for data integrity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The parent object acts as an intermediary between the update operation and multiple child objects. Instead of directly updating each child object handle record, the system uses the parent object as a mediator to propagate updates automatically, reducing operational complexity while maintaining precise control over attribute propagation.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Quantity of substance

If attributes are stored in each handle record individually, then data independence is maintained, but storage resource consumption increases

Engineering Contradiction:
Improvestorage resourcesVSAvoiddata independence
Core Design Contradiction:
Quantity of substanceVSAdaptability or versatility

Solution Approach 1:

The patent implements a nested structure where child object handle records contain references to parent object handles, and parent object handles contain the actual attribute data. This nesting eliminates redundant storage of identical attributes across multiple child objects while maintaining data independence through reference-based access, significantly reducing storage resource consumption.

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

Instead of storing actual attribute data in each child object handle record, the system creates reference copies pointing to the parent object's attribute storage. This copying approach maintains data independence and accessibility while eliminating redundant storage, as all child objects reference the same parent object attributes without duplicating the actual data.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12321759B1Attribute inheritance of related objects for a digital object architecture
Publication Date: 2025.06.03 VERISIGN INC
  • US12321759B1 patent drawing
  • US12321759B1 patent drawing
  • US12321759B1 patent drawing

AI summary

For digital objects registered via the DOA infrastructure, attribute inheritance is enabled between related objects using naming conventions for the handle IDs or data models for handle data. Each child object of a parent object may automatically inherit at least one predetermined attribute of the parent object. When a retriever machine (local handle registry or client machine) obtains a handle ID for a digital object, the retriever machine may determine that the digital object is a child object of a parent object, determine a handle ID for the parent object, obtain the author attribute from the handle data of the parent object, and associate the author attribute of the parent object with the child object. The retriever machine may determine that the digital object is a child object of the parent object via naming conventions for handle IDs or via data models for the handle data.