Impedance mismatch 2.0

A recurring challenge for Topic Maps-based projects is how to structure applications internally. For traditional projects based on relational storage this problem is known as the impedance mismatch problem. That is, the problem of how to handle the database in the code. Should SQL queries be just littered all over the code? Should there be some sort of structure to the database interaction? Should one perhaps use an O/R mapping tool? And so on.

The same challenge exists for Topic Maps-based projects, but it’s much less well understood, and it has not been discussed very much yet. Lars Marius Garshol did a presentation about this at an internal Bouvet conference, which describes some possible approaches to the problem. Since this is highly relevant to Ontopia users we publish the presentation here.

2 thoughts on “Impedance mismatch 2.0”

  1. I suspect what’s needed here is the ability to introspect/”meta-program” on semantic technology. That is what tends to save the day for the Object/Relational mismatch (as much as it is ‘saved’ 😦

  2. By “introspect” I suspect you mean “introspect the ontology/schema”, right? That’s possible today, if awkward. Hopefully it will be easier in Ontopia once we implement TMCL.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s