Web Component Metadata Registration API

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing web application frameworks face challenges in consistently updating web components across different teams and repositories, leading to errors and version mismatches.

Innovation Solution

A computer-implemented method for runtime completion of web component metadata, where the loader script of a web component calls a registration API, combining component-specific metadata with a web component signature to produce completed metadata, and storing it in a component registry.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If web components are updated across different teams and repositories, then functionality and bug fixes can be applied, but maintenance complexity and error rates increase

Engineering Contradiction:

Improveweb component consistencyVSAvoidupdate management complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a registration API as an intermediary between web components and the rendering engine. This API centralizes the metadata management process, allowing components from different teams to be registered consistently without direct coordination. The registration API handles the complexity of metadata combination and version tracking, reducing the burden on individual component maintainers.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the state of web component metadata from static to dynamic. Instead of requiring components to declare all their metadata at definition time, the system allows metadata to be completed and updated at runtime through the registration API. This enables components to be registered with minimal initial metadata and have additional properties added as needed.

Inventive Principle:

Principle #35Parameter changes

2Ease of manufacture

If web component metadata is manually managed, then component-specific functionality can be defined, but maintenance effort and version mismatches increase

Engineering Contradiction:

Improvecomponent development easeVSAvoidmaintenance time

Core Design Contradiction:

Ease of manufactureVSLoss of time

Solution Approach 1:

The registration API implements self-service by automatically combining component-specific metadata with standard web component signatures. Developers only need to provide essential component information, and the API handles the rest by automatically retrieving and integrating standard metadata properties. This eliminates the need for manual coordination of metadata updates across the system.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The registration API serves multiple functions: it registers web components with the rendering engine, combines component-specific metadata with standard signatures, manages version information, and maintains component catalogs. This multi-functionality consolidates what would otherwise require multiple separate processes into a single operation.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Ease of operation

If web components are registered with complete metadata, then rendering engine integration is straightforward, but component definition flexibility is reduced

Engineering Contradiction:

Improveregistration process simplicityVSAvoidcomponent definition flexibility

Core Design Contradiction:

Ease of operationVSAdaptability or versatility

Solution Approach 1:

The system performs preliminary action by pre-defining standard web component signatures that include common properties and behaviors. These standard signatures are prepared in advance and automatically applied during registration. Component developers only need to provide their specific customizations, while the standard framework handles the bulk of metadata preparation.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent segments web component metadata into two parts: mandatory component-specific metadata that developers provide, and optional standard metadata that is automatically retrieved and combined. This segmentation allows components to be registered with minimal information while still receiving complete standard metadata through the registration process.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS12287841B2Runtime completion of web component metadata

Publication Date: 2025.04.29 ORACLE INT CORP

AI summary

Systems and methods described herein relate to runtime completion of web component metadata. Execution of a loader script of a web component may call a registration application programming interface (API) and provide component-specific metadata of the web component to the registration API. Execution of the registration API may provide a rendering engine with completed metadata of the web component, combining the component-specific metadata of the web component with a web component signature (e.g., a standard metadata signature that indicates a plurality of properties of the web component) to produce the completed metadata of the web component. The execution of the registration API may also store an entry in a component registry of the rendering engine that associates a name of the web component with the completed metadata of the web component.