W3C home > Mailing lists > Public > public-gld-comments@w3.org > April 2013

Re: "corrections" property for dataests.

From: Fadi Maali <fadi.maali@deri.org>
Date: Mon, 8 Apr 2013 11:35:30 +0100
Cc: public-gld-comments@w3.org, Makx Dekkers <makx@makxdekkers.com>
Message-Id: <229DC409-F53F-4AEF-8EC5-93FE937047EA@deri.org>
To: Christopher Gutteridge <cjg@ecs.soton.ac.uk>
Hello Christopher,

Thanks for your feedback!

I agree that it is helpful to have a contact associated with each dataset for corrections and queries. This is currently not part of DCAT as it didn't occur frequently in existing catalogues.
It should be possible however for a profile to include extra properties. The conformance section states that a DCAT profile may include classes and properties for additional metadata fields not covered in DCAT ( http://www.w3.org/TR/vocab-dcat/#conformance )

Regards,
Fadi

On 5 Apr 2013, at 16:24, Christopher Gutteridge <cjg@ecs.soton.ac.uk> wrote:

> Hi, sorry to leave it so close to the line on giving feedback.
> 
> I work with datasets which are frequently 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.
> 
> An example of this in practice is equipment.data.ac.uk -- each dataset from each university has an associated "corrections" email or URL so that when someone views a record and spots an error they can email the correct person at the right organisation rather than asking me (I am only an aggregator, and don't clean the data).
> 
> -- 
> 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 Monday, 8 April 2013 10:36:00 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 10 October 2018 10:43:22 UTC
http://lists.w3.org/Archives/Public/public-gld-comments/2013Apr/0063.html
lists.w3.org
crawl=CC-MAIN-2019-13
11842
application/http; msgtype=response
sha1:SJVYR4LQNJV3CIFPMZH4VH2C3LCTQGX6
<urn:uuid:ec343df9-b444-4028-9b5d-1b687b445571>
2019-03-26T18:25:01Z
128.30.52.41
application/xhtml+xml
sha1:BQNRN3J2KQ3UEPQBUB3VCRXOV6E5UAVC
<urn:uuid:76a31aa8-76a4-4241-b5e6-0f410c7a2006>
http://lists.w3.org/Archives/Public/public-gld-comments/2013Apr/0063.html
response
<urn:uuid:836f8b1d-ed6d-4c75-a783-018ef0a1cd6e>
isPartOf: CC-MAIN-2019-13
publisher: Common Crawl
description: Wide crawl of the web for March 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-168-29-43.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 0.11-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/