| By Dr. Srinivas Padmanabhuni | Article Rating: |
|
| April 25, 2005 01:00 PM EDT | Reads: |
1,827 |
In a Service-Oriented Architecture (SOA) it becomes imperative for the providers and requestors to communicate meaningfully with each other notwithstanding the heterogeneous nature of the underlying information structures, business artifacts, and other documents. This requirement is termed as semantic interoperability.
* Vertical Domain Centered Business Vocabularies
* Horizontal Canonical Cross-Vertical frameworks like ebXML, UBL etc.
* Semantic Web based ontological frameworks
* Semantic Mediators
Each vertical domain of business applications has various types of peculiarities specific to the domain warranting the development of a specialized shared vocabulary of business processes and documents.
At the same time, it is also observable that various types of business concepts and data types are common across multiple verticals necessitating the development of cross-domain vocabularies and processes so that they can be captured in a domain-independent manner.
Common artifacts falling into this category are:
* Business concepts, Data and Documents like Purchase Orders, Shipping Handles etc.
* Process, workflow, choreography etc. including exception handling
* Contracts, Trust, Roles, permissions etc.
The third truly dynamic category of business processes in SOA fall under the dynamic category. Dynamic SOA based business processes operate on the “publish—find-bind” paradigm principle, where business processes may dynamically involve business partners and associated applications.
The problem of semantic interoperability is far more acute in such dynamic situations involving service brokers, due to the lack of prior business relationships between the enterprises. Industry practitioners have suggested leveraging work in semantic web to devise comprehensive and open ontologies to address the issue of semantic interoperability for dynamic binding based SOA.
While the aforementioned approaches suggest some form of structured common information modeling, a popular prevalent approach to semantic interoperability is via use of custom semantic mediators, which are custom coded application bridges at each information source that handle the task of conversion to/from the format the information source understands.
About the author
Dr. Srinivas Padmanabhuni is a Principal Researcher with the Web Services Centre of Excellence in SETLabs, and specializes in Web services, Service Oriented Architecture, and Grid technologies alongside pursuing interests in semantic web, intelligent agents, and enterprise architecture. He has authored several papers in international conferences. Prior to Infosys, Dr. Srinivas has worked in multiple capacities in startups out of Canada and USA. Dr. Srinivas holds a PhD degree in computing science from University of Alberta, Edmonton, Canada. Prior to PhD he secured his B.Tech and M.Tech from Indian Institutes of Technology at Kanpur and Mumbai respectively.
Published April 25, 2005 Reads 1,827
Copyright © 2005 SYS-CON Media, Inc. — All Rights Reserved.
Syndicated stories and blog feeds, all rights reserved by the author.
More Stories By Dr. Srinivas Padmanabhuni
Dr. Srinivas Padmanabhuni is a principal researcher with the Web Services Centre of Excellence in SETLabs, Infosys Technologies, and specializes in Web Services, service-oriented architecture, and grid technologies alongside pursuing interests in Semantic Web, intelligent agents, and enterprise architecture. He has authored several papers in international conferences. Dr. Padmanabhuni holds a PhD degree in computing science from University of Alberta, Edmonton, Canada.
![]() |
RoyRoebuck 05/19/09 03:46:41 AM EDT | |||
I would like to begin by pointing out some expressions that might help resolve the semantic interoperability impasse in SOA. Communication does take place without a shared terminology. Terminology, Then Technology. Semantics, then syntax, then technology. Those implementing SOA are focusing so much on SOA technology and SOA syntax that they seem to be forgetting about semantics. To gain and apply semantic capabilities, you must first build a series of continouously refreshed semantic products. This series of semantic products is built using a terminology process. Terminology and semantics are based in the information science of librarians, linguists, and translators, not the science of information technology. So if you want semantic interoperability, build a networked knowledge organization schema/system/service (NKOS) using a terminology process and make it consistently available for those data and IT environments that want to interoperate. That NKOS can then serve as the translating "thesaurus" across the diverse ontologies, knowledge-bases, axiologies, and value-chains, and as a knowledge-base for artificial intelligence and expert systems. The approach I’ve developed, and the information system design I’ve created, unify Terminology Management, NKOS, SOA, Enterprise Architecture, and all computer applications. I’ve located many open-source products that provide the capabilities needed for the different parts of my terminology management process. I need help in automating that process. |
||||
- Big Data in Telecom: The Need for Analytics
- Patterns for Building High Performance Applications
- Microsoft Tries Hadoop on Azure
- Amazon to Fix Some Kindle Fire Problems
- What Motivates Open Standards in the Cloud?
- What to Expect in 2012: Cloud Computing and Open Source Software
- Will PaaS Finally Bring Open Source Love to the Enterprise?
- Ten Hot Trends in Cloud Data for 2012
- Oracle Disaster Recovery Site Hosted by Amazon Cloud
- Cross-Platform Mobile Website Development – a Tool Comparison
- Write Once Run Anywhere or Cross Platform Mobile Development Tools
- Three Buzzwords That Every CIO Hears but One They Should Listen To
- The Future of Cloud Computing: Industry Predictions for 2012
- Make Customer On-Boarding Easy as Paint-by-Numbers for Cloud Services
- Gartner Hype Cycle for Emerging Technologies 2011
- Book Excerpt: Introducing HTML5
- Adobe Sends Flex to the Apache Foundation
- Big Data in Telecom: The Need for Analytics
- Book Excerpt: Java Application Profiling Tips and Tricks
- i-Technology in 2012: Five Industry Predictions
- Patterns for Building High Performance Applications
- Microsoft Tries Hadoop on Azure
- The Next Web Architecture
- Cloud Computing: A Comparison of Computing Models
- The i-Technology Right Stuff
- The Top 150 Players in Cloud Computing
- Who Are The All-Time Heroes of i-Technology?
- Where Are RIA Technologies Headed in 2008?
- Get the Message
- ESB Myth Busters: 10 Enterprise Service Bus Myths Debunked
- i-Technology Viewpoint: Is Web 2.0 the Global SOA?
- i-Technology Viewpoint: Thinking Outside the VC Box
- i-Technology Viewpoint: When to Leave Your First IT Job
- SOA Web Services Edge Conference Coverage on SYS-CON.TV
- SYS-CON.TV's "SOA Web Services" and "Enterprise Open Source" Programs To Air in December
- Five Reasons Why Web 2.0 Matters



















