OWL-SOA Ontology for Multi-Technology Service Repository Organization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions for service-oriented architecture (SOA) deployments fail to effectively organize and identify services in development-time service repositories, particularly when multiple service implementation technologies are used, leading to uncontrolled proliferation and inefficient service reuse.
Innovation Solution
A computer-implemented ontology, OWL-SOA, is provided that leverages existing ontologies like OWL-S and WSMO to organize and identify services across various service implementation technologies, integrating Reusable Asset Specification (RAS) artifacts using Open Services for Lifecycle Collaboration (OSLC) specifications, enabling precise search and retrieval in development-time service repositories.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If existing ontology solutions are used for service-oriented architecture deployments, then service organization and identification is provided, but broad applicability for all applications and varying service implementation technologies is not achieved
Solution Approach 1:
The patent creates a universal ontology structure that can handle multiple service implementation technologies (Web services, RESTful services, SOAP services, etc.) through a common framework. The ontology defines technology-agnostic service concepts that can be instantiated with technology-specific properties, allowing the same ontology to serve diverse service types without requiring separate ontology definitions for each technology.
Solution Approach 2:
The ontology is segmented into hierarchical layers: core service concepts (technology-agnostic), technology-specific service types, and implementation details. This segmentation allows the upper-level ontology to remain simple and broadly applicable, while technology-specific variations are handled in lower layers, resolving the contradiction between versatility and complexity.
2Quantity of substance
If services are added to development-time service repository without proper organization, then service repository grows, but uncontrolled service proliferation occurs
Solution Approach 1:
The ontology provides automated classification and organization of services as they are added to the repository. The system automatically categorizes new services based on their properties and relationships defined in the ontology, providing feedback mechanisms that prevent duplicate services and ensure proper organization. This automated feedback loop controls repository growth without requiring manual intervention, managing complexity while allowing service quantity to increase.
3Measurement precision
If manual service identification methods are used, then service repository can be queried, but precise and powerful service searching and retrieval is not achieved
Solution Approach 1:
The patent replaces manual service identification methods with automated ontology-based reasoning and inference mechanisms. The system uses semantic relationships, constraints, and rules defined in the ontology to automatically search, filter, and retrieve services based on query criteria. This substitution of mechanical manual processes with automated intelligent systems achieves both high precision in service identification and rapid retrieval, eliminating the trade-off between accuracy and speed.
Data Source
AI summary
Providing an ontology for a service-oriented architecture deployment in a computing environment, the ontology providing organization and identification of services in a development-time service repository of the service-oriented architecture. The services in the development-time service repository are implemented using varying service implementation technologies and the ontology supports inquiries about services implemented using the varying service implementation technologies. The providing the ontology includes linking to Reusable Asset Specification artifacts associated with the services in the development-time service repository, the linking using an Open Services for Lifecycle Collaboration (OSLC) specification. Based on submission of a request to identify service results from the development-time service repository, identifying, using the ontology, one or more services of the services in the development-time service repository, and responding to the request with an indication of the one or more services.