Extended UDDI Registry Item Data Structure
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
UDDI standard-based registries lack information about specific items provided by Web Service providers and do not include APIs for querying specific items, requiring consumers to individually contact providers for details, including electronic communication capabilities.
Innovation Solution
Extending the UDDI registry with an item data structure and corresponding APIs (save_item, delete_item, find_item, get_itemDetail) to publish and search for item information, including extended data types like startAvailabilityDate and itemKey, and integrating these into the businessEntity structure, allowing for enhanced item discovery and communication capability verification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If UDDI registry maintains standard structure with white pages, yellow pages and green pages, then registry structure is simple and standardized, but it cannot store information about specific items provided by Web Service providers
Solution Approach 1:
The patent embeds item information structures within the existing UDDI registry framework by nesting item data structures inside businessEntity structures. Each business entity can contain multiple items, creating a hierarchical organization where items are nested within providers, which are nested within the registry. This allows item information storage while maintaining the standard UDDI structure at higher levels.
Solution Approach 2:
The patent segments the registry information into distinct components: businessEntity structures for providers and nested item structures for products/services. This segmentation allows the registry to maintain its original white/yellow/green page structure while adding item-specific data structures that can be independently managed and queried.
2Loss of time
If UDDI registry does not include item-specific information, then registry structure remains simple, but consumers must contact providers individually to obtain item details
Solution Approach 1:
The patent enables preliminary publication of item information in the UDDI registry by providers before consumers need to search for them. Items are pre-described with detailed attributes, specifications, and provider information stored in the registry, allowing consumers to perform self-service searches and filter results without needing to contact multiple providers individually.
Solution Approach 2:
The extended UDDI registry acts as an intermediary between consumers and providers by storing and organizing item information centrally. Instead of direct consumer-provider communication for item inquiries, the registry mediates by providing a standardized interface for searching, filtering, and retrieving item details, reducing the need for individual contacts.
3Reliability
If existing item registries do not include electronic communication capabilities, then registry data structure is simpler, but consumers cannot verify communication compatibility with providers
Solution Approach 1:
The patent integrates multiple functions into the item data structure by incorporating not only basic item information but also provider contact details, communication capabilities, and service descriptions. This multi-functional structure allows a single registry entry to serve as both an item catalog and a communication interface verification mechanism.
Solution Approach 2:
The patent merges item information, provider information, and communication capability data into a unified data structure. By combining these previously separate information types into the nested item structure within businessEntity, the system enables comprehensive verification of communication compatibility without requiring separate lookup processes.
Data Source
AI summary
A method for extending Universal Description, Discovery and Integration (“UDDI”) registry is disclosed. Information of at least one item provided in a UDDI registry is published by a Web Service provider utilizing an item data structure. An item in the UDDI registry may them be searched utilizing at least one Application Program Interface (“API”) associated with the item data structure.


