last call: corrections

Hi, sorry to leave it to the line on feedback.

I work with datasets which are changing and being updated, such as our 
staff directory, list of buildings etc.

These have errors, and when it's open data people spot these errors and 
want them fixed.

We have been working on the principle that it's good practice to include 
a contact for every dataset and a URL or email address for suggesting 
corrections. For this we use the terms:

http://purl.org/openorg/contact
http://purl.org/openorg/corrections

I've just been told by the Europe dcat application profile group that 
they will only consider terms for the application profile which are 
considered "part of dcat" and so I would very strongly like to see these 
terms included, or equivalent terms added.

Getting feedback from the consumers of your open data is really key in 
getting the best value out of it, and should be best practice in all 
non-static datasets.

-- 
Christopher Gutteridge -- http://users.ecs.soton.ac.uk/cjg

University of Southampton Open Data Service: http://data.southampton.ac.uk/
You should read the ECS Web Team blog: http://blogs.ecs.soton.ac.uk/webteam/

Would you recommend the software you use to another institution?
http://uni-software.ideascale.com/

Received on Friday, 5 April 2013 15:08:37 UTC