Service Registry Policy Aggregation via Triplestore Shredding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current service registry and repository systems face challenges in retrieving and aggregating all policy attachments linked directly or indirectly to service documents, leading to a lack of comprehensive policy encapsulation in WSDL service definition files.
Innovation Solution
A method is implemented to receive a service document request, shred its elements into logical objects within a triplestore database, search for policy attachments associated with these objects, retrieve policy details, and compile a list of policies and associated logical objects, providing an aggregated view of policies related to the service document.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If service documents are stored with their policy attachments in the service repository, then comprehensive policy information is available, but retrieving all policies becomes complex and time-consuming
Solution Approach 1:
The system performs preliminary actions by pre-processing service documents and policy attachments, extracting policy information and storing it in a structured format (such as a triplestore or knowledge graph) before actual retrieval requests. This allows comprehensive policy information to be ready in advance, enabling fast retrieval without needing to search through entire document stores during runtime.
Solution Approach 2:
An intermediary indexing mechanism (such as a triplestore, knowledge graph, or inverted index) is introduced between the service repository and the retrieval system. This intermediary layer stores extracted policy information in a structured, query-friendly format, acting as a mediator that translates retrieval requests into efficient queries without requiring full document processing, thus reducing retrieval time while maintaining information completeness.
2Reliability
If multiple policy attachments are linked to service documents, then comprehensive policy coverage is achieved, but the complexity of managing and retrieving these policies increases
Solution Approach 1:
The system segments policy management by separating policy attachments from service documents and organizing them into distinct, manageable units within the indexing structure. Each policy attachment is independently processed, extracted, and stored as a separate entity with its relationships to service documents clearly defined. This segmentation allows the system to handle multiple policies without increasing overall complexity, as each policy can be managed and retrieved independently through structured queries.
Solution Approach 2:
The system adds another dimension to policy storage by using a triplestore or knowledge graph structure that represents policies, service documents, and their relationships in a multi-dimensional semantic space. Instead of storing policies as flat attachments, the system creates a layered representation with subjects, predicates, and objects, enabling complex policy relationships to be queried efficiently through standardized ontology-based queries, thus reducing management complexity while maintaining comprehensive coverage.
3Loss of information
If service documents are shredded into logical objects for policy aggregation, then comprehensive policy view is achieved, but processing time increases
Solution Approach 1:
The system performs shredding and logical object creation as a preliminary action during the initial service document loading phase. Service documents are decomposed into their constituent logical objects (such as operations, messages, bindings) and these objects are pre-indexed in the triplestore with their associated policies. This preliminary processing eliminates the need for time-consuming shredding operations during actual policy aggregation requests, as the logical objects and their policy relationships are already prepared and stored in an optimized structure.
Data Source
AI summary
A method of operating a service registry and repository based on a triplestore comprises: receiving a request to aggregate a service document; shredding elements of the service document to create logical objects within the triplestore; for each logical object, searching for all policy attachments logical objects that have a relationship with the logical object; for each located policy attachment, retrieving details of the policy and building a list of policies and associated logical objects in the repository; and returning an indication of the list of polices and associated logical objects. The list of logical objects and associated polices is used to compile a service document containing details of policies that have relationships with the selected service document logical objects. Objects that have associated polices are rendered with a hypertext policy icon next to the object and selection of the hypertext policy icon opens a new window with the policy details.