The next steps in developing our ontology involve one more set of changes (linking to OPMV) and, most importantly, publishing the ontology somewhere.

These aren't the "final" steps as far as the ontology is concerned, it will need to evolve as people gain experiences applying it and give feedback on design and naming issues. However, it does bring this series of blog postings to a good stopping point.

This is the fourth in our series of postings on the design of an organization ontology. The focus this time is on revising the ontology in the light of feedback and reflection.

This is the third in our series of posts recording the (currently ongoing) process of developing an organization ontology. Here we sketch an initial design. Taking the initial requirements we now look at each part of the domain scope and identify the core classes, properties and design patterns.

This sketch is designed to cover all of the requirements with a minimum core set of concepts. The intention is that particular applications would extend and specialize this core. The next step is to get feedback on both the structure and the naming and associated definitions.

This is the second in our series of posts recording the (currently ongoing) process of developing an organization ontology. Here we are focused on surveying the options that already exist to confirm we haven't missed anything.

Background

The data.gov.uk linked data project found itself in need on an ontology or vocabulary to support linked data publishing of government organizational information. A check for existing ontologies didn't turn up an ideal solution so we decided to develop one.