Stefan Wagner

«Truth can only be found in one place: the code.»  Robert C. Martin alias Uncle Bob


Blog | Archive | Resume | Projects | References

Jobseeking with OWL

24 Jan 2015 | reasoning, protege

In the current CTI science project, we’re testing OWL and the possibility to classify objects as well. The idea is to find the right candidat, a job seeker, for a certain vacancy.

Setup jobseeker

The first screen shows a demo of the setup of the jobseeker OWL ontology. There are two job seekers Peter Muster with the property hasSkill set to some CSharp and Stefan Wagner with hasSkill set to some Java.

Demo Vacancy

Now we see an open position Vacancy1 which has a so called necessary and sufficient condition Job and (hasSkill some Java). This setup makes it possible for a reasoner to determine which vacancy has a possible candidate.

Reasoning

On the last screen, I called the reasoner to classify. The result is that StefanWagner was classified to be a sub class of Vacancy1.

This is the simplest use-case. Actually, there would be many more job seekers, vacancies and skills. The point is that the machine can assign candidates to an open position by itself out of a model.

I used Protégé to model this example but you can also use a java library like Apache-Jena or the OWL-API in our source code.

comments powered by Disqus

Older · View Archive (11)

Independent Domain Model

In our current project, we made a design decision for our domain model to be independent of any concrete persistence technology. Due to the fact that the persistence layer had to be replaceable in order to fit in any client environment, we came to the conclusion that we needed to define an API module for the persistence and a temporary or default implementation of it.

Newer

Groovy is awesome!

In my last project, we used Grails 3 that uses groovy as the main technology. With groovy you can really focus on your business problems. You have very little boilerplate code.