API Parameter Mapping via Key Model Standardization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional APIs lack standard formal definitions, leading to heterogeneity issues when developers interact with multiple APIs, as they often use different terminology and formats, making it challenging to map API parameters correctly and efficiently.
Innovation Solution
A system that generates a key model based on a defined API specification, allowing for the mapping of API parameters from various formats to a standardized format by considering key terms, value terms, and root parents, enabling accurate association and simplification of API specifications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional APIs use different terminology and formats, then each API can maintain its own unique characteristics, but it becomes difficult to map API parameters correctly and efficiently across multiple APIs
Solution Approach 1:
The patent introduces an intermediary component that translates between different API parameter formats and a standardized internal representation. This mediator enables seamless integration of diverse APIs without requiring complex custom mapping logic for each API, thus resolving the contradiction between maintaining format diversity and reducing mapping complexity
Solution Approach 2:
The system dynamically changes parameter representations by converting various API-specific parameter formats into a unified standardized format. This parameter transformation approach allows the system to handle diverse API formats while maintaining consistent internal processing, effectively reducing mapping complexity
2Reliability
If developers review API specifications manually, then they can understand the details, but it consumes significant time and effort
Solution Approach 1:
The patent replaces the manual mechanical review process with an automated computational system that parses, analyzes, and validates API specifications programmatically. This substitution maintains thorough understanding of API details while dramatically reducing the time developers need to invest in reviewing specifications
3Adaptability or versatility
If API parameters are represented in various formats, then each API can use its native format, but it complicates the process of finding and using API parameters
Solution Approach 1:
The patent implements a universal parameter representation system that can handle multiple native API formats while presenting a consistent interface to developers. This multi-functional approach allows the system to work with various API formats internally while providing ease of operation through standardized access methods
Data Source
AI summary
A system may include a communication interface and a processor operatively coupled to the communication interface. The processor may receive a defined API specification, which may include an API table in a first format in which each column may be associated with an API parameter. The processor may generate a key model that includes one or more API parameters of the API table mapped to a corresponding class of API parameters in a defined format based on the defined API specification. The processor may receive an extracted table in which each column may be associated with an API parameter in the first format. The processor may associate each column of the extracted table with a class of API parameters in the defined format based on the key model. The processor may generate an API specification that includes the API parameters of the extracted table in the defined format.