Web Service Versioning Consistency Across Sub-Organizations
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In large organizations, web service versioning is processed in a decentralized manner across independent sub-organizations, leading to inconsistent evolution of web services due to independent evolution of baseline-namespaces, resulting in potential inconsistencies in web service versions.
Innovation Solution
A system and method for maintaining versioning of web services and XML schemas across sub-organizations, which tracks versioning history, identifies a baseline web service version, validates WSDL and XSD documents for compliance with dependency schemes, and recommends the baseline version and dependencies to users to ensure consistency, using a web service factory platform with tools for validation and versioning analysis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If web service versioning is processed in a decentralized manner across independent sub-organizations, then each sub-organization can independently evolve web services and adapt to local needs, but inconsistencies in web service versions and baseline-namespaces will occur across the organization
Solution Approach 1:
A centralized versioning management system acts as an intermediary between independent sub-organizations. This system tracks versioning history across all sub-organizations, automatically identifies appropriate baseline web service versions, validates WSDL and XSD documents for compliance with dependency schemes, and provides recommendations to maintain consistency while allowing decentralized development.
2Ease of operation
If baseline-namespaces are evolved independently by different sub-organizations, then local customization and flexibility are achieved, but inconsistent evolution of the same web service occurs
Solution Approach 1:
The versioning management system implements feedback mechanisms by tracking versioning history across sub-organizations and providing automated recommendations. When a sub-organization evolves a baseline-namespace, the system monitors changes, validates compliance with dependency schemes, and communicates version consistency requirements back to the sub-organization, ensuring coordinated evolution while maintaining local customization capabilities.
3Reliability
If automated validation of WSDL and XSD documents is implemented, then version consistency and compliance are ensured, but system complexity increases
Solution Approach 1:
The validation system operates autonomously by automatically tracking versioning history, identifying baseline versions, validating WSDL and XSD documents against dependency schemes, and generating compliance reports without requiring manual intervention. This self-service approach ensures reliable version compliance while minimizing the operational complexity burden on users.
Data Source
AI summary
A system, method, and computer program product are provided for maintaining versioning of web services and XML (Extensible Markup Language) schemas associated with a plurality of independent sub-organizations. In use, a versioning history of a plurality of web services is tracked across a plurality of sub-organizations associated with an organization. Further, a new version of a web service to be introduced in at least one of the sub-organizations is identified. Additionally, a baseline web service version to use for the new version of the web service is automatically identified based on a tracked versioning history of the web service. Furthermore, an existing state of WSDL (Web Services Definition Language) documents and XSD (XML Schema Definition) documents is validated to ensure compliance with a dependency scheme associated with the tracked versioning history of the web service. Moreover, the baseline web service version and dependencies to use for the new version of the web service is recommended to a user, and an impact of introducing the new version of the web service is indicated, such that consistency of the versioning history of the plurality of web services across the plurality of sub-organizations is capable of being maintained.