We use cookies and other similar technologies (Cookies) to enhance your experience and to provide you with relevant content and ads. By using our website, you are agreeing to the use of Cookies. You can change your settings at any time. Cookie Policy.

Leveraging Information and Intelligence

David Linthicum

Considering Vertical Ontologies

user-pic
Vote 0 Votes


To gather information specific to an entity, for understanding our data, we need to leverage different resources to identify individual entities, which vary widely from each physical information store. For instance, when leveraging a relational database, entities are identified using keys (e.g., customer number). Within the various information systems, many different terms are used for attributes. Thus, the notion of ontologies in this scenario allows us to determine whether entities from different applications and databases are the same or non-crucial to fusing information.

Considering that pattern of architecture there are two basic types of ontologies, horizontal and vertical.

Horizontal ontologies are general in nature, such as space-time relationships. These are common ontologies that span multiple domains, are not applicable to any single vertical space and provide a mechanism to organize and standardize information content. We've employed this type of ontology for years in the form of object models, hierarchies, taxonomies and, in many cases, XML vocabularies.

Vertical ontologies, which also incorporate features from horizontal ontologies, are domain-specific, such as natural languages for healthcare or financial services. Vertical ontologies not only define data in terms of semantics native to a particular vertical industry, they also contain rules and formal computer languages that can perform certain types of runtime automated reasoning. This means we understand the meta data and have logic bound to the meta data as well.

The use of vertical ontologies, which extend the capabilities of horizontal applications, is where the most value exists. As we learn to define these ontologies as common frameworks for specific business requirements and define the reuse of such frameworks applicable across multiple like-domains, we also learn to apply languages and reasoning techniques. Ultimately, this provides repeatable information formats, rules and logic that, in turn, provide data integration architects with the ability to leverage existing solutions rather than form them from general-purpose middleware and application development technology.

All valuable when considering understanding data, and the use of data, within our problem domain.

2 Comments

I have developed a system which allows each user to create their own ontology. This is supported in a number of ways by the system.

The user can ever create "complex ontologies". Those which span multipe areas of through

well articulated, David.

At zAgile (www.zAgile.com), we have created one of the first "semantic context servers," called zCALM, and it is open source. zCALM acts as the delivery vehicle for such vertical ontologies.

With our wiki plug-in called Wikidsmart (and zCALM under the covers; available for download at SourceForge under the Wikidsmart project name), we enable the Atlassian Confluence enterprise wiki as a GUI front-end to showcase zCALM's power. This allows organizations to plug in their vertical ontology of choice. Therefore, the wiki becomes a semi-structured knowledge repository.

Furthermore, zAgile Teamwork leverages zCALM and Wikidsmart for the specific use case of collaboration for software engineering teams and executives. It includes Connectors for Atlassian's JIRA issue tracker, Atlassian Confluence (Wikidsmart plug-in), Subversion, CruiseControl, and Salesforce. This enables the leveraging of the 'vertical ontology' for software engineering to be the collaboration knowledge model. In this way, information is fluidly exchanged in a contextual fashion across the software engineering teams and company in a very precise collaborative and contextual manner. Concepts such as Issue, Project, Requirements, Tasks, are understood across the whole software engineering lifecycle thanks to the software engineering vertical ontology residing in zCALM.

We have some exciting use cases and customer case studies in process, outside the vertical domain of software engineerinng, that we look forward to sharing with you and your readers.

Industry expert Dave Linthicum tells you what you need to know about building efficiency into the information management infrastructure

David Linthicum

David Linthicum is the CTO of Blue Mountain Labs, and an internationally known distributed computing and application integration expert. View more

Subscribe

 Subscribe in a reader

Recently Commented On

Categories

Microsoft,

Monthly Archives

Blogs

ADVERTISEMENT