This document discusses using semantic technologies to improve governance in service-oriented architectures (SOA). It addresses current problems in SOA related to visibility, relationships, and control over the service lifecycle. Semantic SOA uses ontologies to model services and their relationships, enabling better discovery, contracts, and lifecycle management. A use case in healthcare demonstrates how ontologies can help model business concepts and discover services. The document concludes that ontologies can guide SOA development in outsourced environments without requiring canonical data models.
2. What is the problem with current web?
I am looking for a battle
tank. The picture that I
have in mind is
Problem: The search
engine understood the
syntax of my query but
not the semantics(the
meaning) of it.
2 February 22, 2013
3. Solution?
• Use semantic web technologies to describe, differentiate and provide
relationship between a tank that blows things up in a battlefield, a
propane tank used for cooking and a tank top worn by soldiers.
• The data is defined and linked in such a way that it can be used by
machines not just for display purposes, but for inference and
automation.
A machine/software system
should be able to say…
Photo Credit: Duncan Hull
3 February 22, 2013
4. Semantic Web Technologies
• Information Format RDF
• Information OWL, RDFS
Organisation SPARQL
• Information Access URIs
•Identification
RDF/OWL provides:
• Natural representation for graphs of relationships
• Automatic inference
• Interoperability through standards (W3C recommendations)
• Enables better communication between Humans/Machines
• Reuse of Ontologies across various applications
4 February 22, 2013
5. Current problems in SOA today
Visibility Relationship
Lack of visibility, Inability to establish
across domains and manage a
for services and relationship between
related metadata service consumer
and provider
Control Consistency
No control over
Inability to
the service
establish policies
lifecycle…
and integrity of
version, change or
overall
impact
architecture
6. Use case – Health care industry
Business Ontologies: Discharge Date, Admission Date, Length of
Stay
“Length of Stay” is connected to the other two because it is
calculated based on them, and all three belong to the InPatient
information domain, within the Care Delivery information domain.
Challenges
1.How to model and import services into a SOA repository that
logically corresponds to the business Ontologies that they might
consume or produce?
2.How to dynamically discover services based on inference?
3.How to use collective intelligence for enriching service metadata?
6 February 22, 2013
7. Use case – Health care industry
Business Ontologies: Discharge Date, Admission Date, Length of
Stay
“Length of Stay” is connected to the other two because it is
calculated based on them, and all three belong to the InPatient
information domain, within the Care Delivery information domain.
Challenges
1.How to model and import services into a SOA repository that
logically corresponds to the business Ontologies that they might
consume or produce.
2.How to dynamically discover services based on inference?
3.How to use collective intelligence for enriching service metadata?
7 February 22, 2013
8. How Semantic technologies can help?
Visibility
Lack of visibility,
across domains
for services and
related metadata
Dynamic service discovery
• With Semantic SOA approach, services are retrieved not by syntactic
interfaces and unstructured meta-data but via ontological reasoning.
• Enriching the service metadata using Ontologies can helps
consumers and providers to easily identify services. This eliminates
service duplication and promotes reuse.
8 February 22, 2013
9. How Semantic technologies can help?
Relationship
Inability to establish
and manage a
relationship between
service consumer
and provider
Ontology-based contracts
With Semantic SOA approach, contracts are created based on
Ontologies, where some clauses within a contract are being
negotiated by software for automation.
9 February 22, 2013
10. How Semantic technologies can help?
Control
No control over
the service
lifecycle.. version,
change or impact
Improved Lifecycle management
Change requests can be evaluated against an Ontology to
determine the appropriate terms to use/exchange to eliminate
downstream mismatch given what else already exists.
10 February 22, 2013
11. How Semantic technologies can help?
• Improved collaboration via Folksonomy
• Semantic enrichment of Folksonomy tags and keywords put on a
business service.
• Improve the service relevancy by selecting and combining relevant
bits of knowledge from the tags and keywords.
• To provide the consumers with the right services based on service
relevancy.
11 February 22, 2013
12. The Anatomy of the query …
Query = “Find Pending Status CRM Services with
High Reputation”
13. Stemmed Entity Recognition &
Linguistic Parsing yields…
Search Verb:
“Find”
Find Pending Status CRM Services with High
Reputation
14. Stemmed Entity Recognition &
Linguistic Parsing yields…
Search Verb:
“Find”
Attribute:Status= “Pending”
Find Pending Status CRM Services with High
Reputation
15. Stemmed Entity Recognition &
Linguistic Parsing yields…
Search Verb: Entity:
“Find” Attribute:Type=“CRM Service”
Attribute:Status= “Pending”
Find Pending Status CRM Services with High
Reputation
16. Stemmed Entity Recognition &
Linguistic Parsing yields…
Search Verb: Entity:
“Find” Attribute:Type=“CRM Service”
Attribute:Reputation= “High”
Attribute:Status= “Pending”
Find Pending Status CRM Services with High
Reputation
17. Stemmed Entity Recognition &
Linguistic Parsing yields…
Search Verb: Target Entity:
“Find” Attribute:Type=“CRM Service”
Attribute:Reputation= “High”
Attribute:Status= “Pending”
Find Pending Status CRM Services with High
Reputation
18. Stemmed Entity Recognition &
Linguistic Parsing yields…
Search Verb: Target Entity:
“Find” Attribute:Type=“CRM Service”
Having Attribute
Attribute:Reputation= “High”
Attribute:Status= “Pending”
Find Pending Status CRM Services with High
Reputation
19. Stemmed Entity Recognition &
Linguistic Parsing yields…
Search Verb: Target Entity:
“Find” Attribute:Type=“CRM Service”
Having Attribute Having Attribute
Attribute:Reputation= “High”
Attribute:Status= “Pending”
Find Pending Status CRM Services with High
Reputation
20. Definition: Service Reputation
Service Reputation = f(User ranking, Compliance,
Verity)
- User ranking = User reviews (Collective
Intelligence, subjective User perception)
- Compliance = Degree of Conformance to policies,
guidelines and standards
- Verity = Degree of consistency exhibited by
Service provider in delivering the quality levels
laid out in service contract, in a range of previous
transactions (Run Time)
21. The Ontology is the basis for the
Search
-Dis c o v e ry (D) -Co d e v e rs io ns (D)
-De s c rip tio n (D) -Do c um e nta tio n (D)
Registry -Que ria ble m e s s a g e
-Co ntra c ts (R)
-Po lic ie s (R) Repository s to re (R)
-Ve rs io ning (R) -Lo g g ing (R)
-A iting (R)
ud
IBM.com
Joe Web Site
Person Lives in Palo Alto IBM
City Company
Publisher of
Fan of
Subscriber to Lives in
Employee of
Sue
Jane Person
Dave.com
Fan of Person
RSS Feed Coldplay
Friend of
Band
Member
of
Design Depiction of
Married to
Team
Source of Member
Group 123.JPG
of
Dave.com Bob Photo
Weblog Person
Depiction of
Member of
Stanford
Dave Member of
Author of Alumnae
Person
Group
Member of
22. Starting with a network of inter-related
governance artifacts
Governance
Governance Related to Artifact
Artifact Governance
Governance Artifact
Related to
Artifact
Related to
Related to Related to
Related to
Governance
Related to Governance Artifact
Governance
Governance Related to
Artifact Artifact
Artifact Related to
Related to
Related to
Related to Governance Related to
Artifact
Governance
Governance Artifact
Governance
Artifact Related to
Artifact
Related to
Related to
Related to Governance
Governance
Artifact Artifact
Related to
23. We locate the CRM related governance
artifacts in that network
CRM Governance
Related to CRM Artifact
Governance
Artifact CRM Governance
Governance Artifact Related to
Related to Artifact
Related to Related to
Related to
CRM
CRM Governance
Related to Governance
Governance Related to Artifact
Governance Artifact
Artifact Artifact Related to
Related to
CRM Related to
Related to Related to
Governance
CRM
CRM Artifact
CRM Governance
Governance Artifact
Governance Related to
Artifact
Related to Artifact
CRM Related to
Related to CRM
Governance Governance
Artifact Artifact
Related to
24. We then locate the CRM Service
governance artifacts in that subset
CRM Governance
Related to CRM Artifact
Service
Artifact CRM Service
Governance Artifact Related to
Related to Artifact
Related to Related to
Related to
CRM
CRM Service
Related to Governance
Governance Related to Artifact
Governance Artifact
Artifact Artifact Related to
Related to
CRM Related to
Related to Related to
Service
CRM
CRM Artifact
CRM Service
Service Artifact
Service Related to
Artifact
Related to Artifact
CRM Related to
Related to CRM
Service Governance
Artifact Artifact
Related to
25. We then locate the CRM Service artifacts
that are pending approval
Pending Governance
CRM Pending
Related to Artifact
Service CRM
CRM
Artifact Service
Governance Related to
Artifact
Related to Artifact
Related to Related to
Related to
CRM
CRM Service
Related to Governance
Governance Related to Artifact
Governance Artifact
Artifact Artifact Related to
Related to
Pending CRM Related to
Related to Related to
Service
Pending CRM
Pending CRM Artifact
CRM Service
Service Artifact
Service Related to
Artifact
Related to Artifact
CRM Related to
Related to CRM
Service Governance
Artifact Artifact
Related to
26. We display them…
Pending CRM
Service Pending CRM
Artifact Service
Artifact
Pending CRM
Service Pending
Artifact CRM
Pending CRM
Service
Service
Artifact
Artifact
27. As a Tabular List
Pending CRM
Service
Artifact
Pending CRM
Service
Artifact
Pending CRM
Service
Artifact
Pending CRM
Service
Artifact
Pending CRM
Service
Artifact
28. With direct Associations as Links
CRM
Pending Governance
CRM Artifact
Related to
Service
Related Governance
Artifact to
Artifact
CRM
Pending Governance
CRM Artifact
Related to
Service CRM
Related to
Artifact Governance
Artifact
CRM
Pending Governance
CRM Artifact
Related to
Service CRM
Related to
Artifact Governance
Artifact
Pending CRM
CRM Governance
Service Artifact
Related toCRM
Related Governance
Artifact
to
Artifact
Pending CRM
CRM Governance
Service Artifact
CRM
Related to
Artifact Related Governance
to
Artifact
29. … and potentially, Inferred Associations
as Graphs CRM
Pending Governance
CRM Artifact
Related to
Inferencing rule, e.g.: Find similar Item
Service
Related Governance
Artifact to
Artifact
CRM
(inferred) CRM
Pending Governance
Service Related to
CRM Artifact
Related to
CRM Artifact
Service (Inferred) CRM
Related to
Artifact Governance Governance
Artifact Artifact
Related to
CRM
Pending Governance
CRM Artifact
Related to (Inferred)CRM
Service CRM
Related to Governance
Artifact Governance
Artifact
Artifact
Pending CRM
CRM Governance
Service Artifact
Related toCRM
Artifact Related Governance
to
Artifact
Pending CRM
CRM Governance
Service Artifact
CRM
Related to
Artifact Related Governance
to
Artifact
31. Conclusion
• Use of Ontologies to guide development of SOA-
solutions in highly outsourced environments.
• Use of Ontologies combined with SOA-based
services to eliminate the issues associated with
traditional EAI tools where canonical data models
are required.
31 February 22, 2013
What are the key elements required to effectively attain SOA governance that can help accelerate SOA success?
With Semantic SOA, it paves the way for automating the discovery of services that can fulfill certain needs, for automating the integration of heterogeneous data models, for better supporting the combination of services or for the creation of smarter systems, as wells as invocation and monitoring of combined services. Using Ontologies enables the development of more adaptable and more extensible systems which are in fact some of the main benefits attributed to SOA. Service Registry : Use of UDDI registry to publish semantic web data for semantic-based description, discovery and integration. Mapping the semantic web concepts to UDDI data model using the tModel structure, which makes possible to store semantically annotated resources internally in UDDI. Service Discovery : Discovery is effectively the query interface over the service repository. One of the strengths of the Semantic SOA approach however is that services are retrieved not by syntactic interfaces and unstructured meta-data but via ontological reasoning. The main discovery goal involves submitting a user needs, and optimally the data to be passed in the intended invocation, and receiving back a list of services. It Provides: Service discovery (what service satisfies my needs?) Service composition (how do I combine services to get what I want?) Service publication (how do I let people know about my service?) Service verification (how do I know that a service does what I want? Service Selection : Having obtained a list of matches from the discovery component, the selection component aids in the selection of a service for invocation. The main goal involves submitting the list of services or mediators, together with an ontology that will distinguish between them in terms of degree of match, QoS profiles, trust/policy matters. Promote Service Reuse Enriching the service metadata using Ontologies can helps consumers and providers to easily identify services. This eliminates service duplication and promotes reuse. Improved Collaboration via Folksonomy Semantic enrichment of Folksonomy tags by selecting and combining relevant bits of knowledge from Ontologies.
The problem with tags is difficult to index in meaningful ways due to the lack of machine-readable, human-understandable, textual data associated with them.