- From: Fadi Maali <fadi.maali@deri.org>
- Date: Thu, 5 Dec 2013 14:43:52 +0000
- To: Leigh Dodds <leigh@ldodds.com>
- Cc: "public-gld-comments@w3.org" <public-gld-comments@w3.org>
Hello Leigh, I want to check that your comment was addressed properly. We provided further examples in the document (non-normative section) however we did not provide guidance along the property descriptions. The reason is that we didn't have proper criteria in place to decide which URIs to suggest. The Working Group was concerned that this might results in a long list of proposals and suggestions that require examining each suggestion and deciding on its adequacy. something that requires more resources and time than are available. Profiles of DCAT are encouraged to include such restrictions for the properties they use (DCAT-AP [1] does). I hope that addresses your feedback. Many thanks again! Fadi Maali [1] https://joinup.ec.europa.eu/asset/dcat_application_profile/asset_release/dcat-application-profile-data-portals-europe-final-draf?page=1 -------------------------------------------------- Fadi Maali PhD student @ Insight Galway (formerly DERI) Irish Research Council Embark Scholarship holder http://www.deri.ie/users/fadi-maali On 4 Nov 2013, at 16:48, Leigh Dodds <leigh@ldodds.com> wrote: > Hi, > > Am back from holiday and have had chance to look this over. My main > concerns was making sure there were pointers to useful supplementary > data on use of those properties. I think your examples help to address > that. > > But I was also hoping to see these pointers included elsewhere in the > document, specifically in the definitions for each of the properties. > > Some of the existing properties include guidance on ranges (e.g. > dct:modified notes preferred datatype). It would be useful to add > similar references to dct:accrualPeriodicity, etc. For example: > > Range: dct:Frequency (A rate at which something recurs). Good > sources for these URIs are the Dublin Core frequency > guidelines and the DataCube Content Oriented Guidelines > > I think this would help promote useful high-quality sources, but > without mandating a particular approach. > > Cheers, > > L. > > > > On Wed, Oct 30, 2013 at 6:47 AM, Fadi Maali <fadi.maali@deri.org> wrote: >> Hello Leigh, >> >> Sorry for late reply. >> >> I have extended the examples in the DCAT specification to include the other properties. https://dvcs.w3.org/hg/gld/raw-file/default/dcat/index.html#basic-example >> In particular I added: >> - dct:spatial with an example URI from Geonames >> - dct:temporal with an example URI from the Interval dataset from data.gov.uk >> - dcat:contactPoint with an made-up URI and a description that this can be further described using VCARD. >> >> Can you please let us know if you think this addresses your comment. >> >> Thank you! >> >> Best regards, >> Fadi Maali >> >> >> -------------------------------------------------- >> Fadi Maali >> PhD student @ Insight Galway (formerly DERI) >> Irish Research Council Embark Scholarship holder >> http://www.deri.ie/users/fadi-maali >> >> On 29 Jun 2013, at 00:00, Leigh Dodds <leigh@ldodds.com> wrote: >> >>> Hi, >>> >>> I've been reviewing the 12th March draft [1]. There are a number of >>> properties that don't have examples of their usage. I think the >>> specification should have example uses of every property, particularly >>> those that might be underspecified or documented elsewhere. >>> >>> This is true of properties such as dct:accrualPeriodicity, >>> dct:spatial, dct:temporal, etc. >>> >>> The Dublin Core have some general guidance which might be referenced >>> (or used to create examples. I've also recently learnt that there are >>> some standard accrual periods [3]. >>> >>> Additional examples will help ensure that users create more consistent metadata. >>> >>> Cheers, >>> >>> L. >>> >>> [1]. http://www.w3.org/TR/2013/WD-vocab-dcat-20130312/ >>> [2]. http://wiki.dublincore.org/index.php/User_Guide/Publishing_Metadata >>> [3]. http://dublincore.org/groups/collections/frequency/ >>> >>> -- >>> Leigh Dodds >>> Freelance Technologist >>> Open Data, Linked Data Geek >>> t: @ldodds >>> w: ldodds.com >>> e: leigh@ldodds.com >>> >> > > > > -- > Leigh Dodds > Freelance Technologist > Open Data, Linked Data Geek > t: @ldodds > w: ldodds.com > e: leigh@ldodds.com
Received on Thursday, 5 December 2013 14:44:24 UTC