You are hereBlogs / David Schaengold's blog

David Schaengold's blog


FIBO: a path forward for the Financial Services industry

 

Recently I had the privilege of presenting some work Revelytix has been doing in the financial services space at a conference hosted by the Enterprise Data Management Council (EDMC) and the Object Management Group. What we presented focused on using the Financial Industry Business Ontology (FIBO) to drive integration and

Integrating External Data into a Knowledge Management System

3332644561 c9d5041d02 m resized 600A truly distributed database mangement system offers remarkable benefits that sometimes aren't apparent at first. One of those benefits is the ability to integrate internal data and external data into a single knowledgebase or knowledge management system.

When to write rules, and when to focus on ontology development

knowledge management systemA user at answer.semanticweb.com recently asked a great question: when is it best to use an ontology vs writing rules for a task that involves reasoning? Both are forms of semantic modeling, and in many cases both approaches can get you to the same destination.

I think the answer depends on finding a balance between performance, predictability, and ease of management on one side, vs reusability on the other side.

Classifying swaps using a distributed database management system

enterprise analysisRevelytix has embarked on a project in partnership with the Enterprise Data Management Council to demonstrate the value of semantic technology in reasoning about financial data.

Provenance: a Step Towards Real Semantic Software Solutions

This article is the first in a series summarizing the submissions we have made for SemTechBiz West 2012.

Quality Control for Ontologies Using SPARQL

There are a number of existing tools used to check ontologies for OWL DL compliance. To our knowledge, all of these tools include code written especially for checking RDF against the OWL DL ruleset. Recently, we have taken some preliminary steps towards creating a generalized, SPARQL-based validation/quality control strategy requiring no purpose-built code, only the ability to direct SPARQL queries at a graph. Our initial effort resulted in three sets of validation queries, each of which was designed to return violations of a ruleset: