W3C home > Mailing lists > Public > public-lod@w3.org > June 2012

Evolving vocabularies

From: Carsten Keßler <carsten.kessler@uni-muenster.de>
Date: Wed, 27 Jun 2012 10:11:29 +0200
To: public-lod@w3.org
Cc: Chad Hendrix <hendrix@un.org>, perrin.v@gmail.com
Message-ID: <BB07D4637E614BFAA91AF443B8817D43@gmail.com>
Dear LODers, 

I have already bugged this list with our Humanitarian eXchange Language project a couple times, and I'd like to hear your opinion on the following problem.

We are constantly working on the vocabulary (see http://hxl.humanitarianresponse.info/ for the latest version), so it gets revised fairly often, sometimes several times a week. While we are doing that, we are also developing our tools around the vocabulary, and we have started producing some data (you can already query the endpoint at http://hxl.humanitarianresponse.info/sparql, although there is not much there yet). 

When we are producing data, we always use the latest version of the vocabulary; obviously, that will create problems over time, say if you want to query all Camps (http://hxl.humanitarianresponse.info/ns-2012-06-14/#Camp) out of the triple store, independent of the vocabulary version. So far, each version of the vocabulary is linked to the previous version via dc:replaces, but this does not really solve our problem.

We are working towards a stable first "release" of the vocabulary at some point, but until then, we will have to work around this issue somehow. Is there any best practice for that kind of problem? Would it make sense to apply dc:replaces to every class/property that is carried over from a previous version? 


Received on Wednesday, 27 June 2012 08:11:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:21:25 UTC