- From: Phil Archer <phila@w3.org>
- Date: Thu, 18 Oct 2012 11:48:13 +0100
- To: Richard Cyganiak <richard@cyganiak.de>
- CC: Dave Reynolds <dave.e.reynolds@gmail.com>, Government Linked Data Working Group <public-gld-wg@w3.org>
OK, let me go back to that proposal. Yes, I see the value in saying that specifically a data catalogue that conforms if certain conditions are met. [[ A data catalog conforms to DCAT if: * It is organized into [[datasets]] and [[distributions]]. +1 * An [[RDF description]] of the catalog itself and its datasets and distributions is available (but the choice of RDF syntaxes, access protocols, and access policies is not mandated by this specification). +1 * The contents of all metadata fields that are held in the catalog, and that contain data about the catalog itself and its dataset and distributions, are included in this RDF description, expressed using the appropriate classes and properties from DCAT, except where no such class or property exists. This is rather wordy and I think it can be clarified and split in two: * The metadata concerning the catalog, its datasets and distributions is expressed using the appropriate classes and properties from DCAT. * terms from other vocabularies are not used *instead* of ones defined in DCAT that could reasonably be used (use of such terms in *addition* to DCAT terms is permissible). Incidentally, if I misunderstood your meaning in the original then I offer that as evidence that it needs clarification ;-) Back to your original * All classes and properties defined in DCAT are used in a way consistent with the semantics declared in this specification. +1 DCAT-compliant catalogs MAY include additional non-DCAT metadata fields and additional RDF data in the catalog's RDF description. -1 Not necessary as we've covered that in the earlier clarification. +1 from here on. A *DCAT profile* is a specification for data catalogs that adds additional constraints to DCAT. A data catalog that conforms to the profile also conforms to DCAT. Additional constraints in a profile MAY include: * A minimum set of required metadata fields * Classes and properties for additional metadata fields not covered in DCAT * Controlled vocabularies or URI sets as acceptable values for properties * Requirements for specific access mechanisms (RDF syntaxes, protocols) to the catalog's RDF description ]] On 12/10/2012 09:46, Richard Cyganiak wrote: > On 11 Oct 2012, at 14:51, Phil Archer wrote: >> Having done that, how would you and Richard feel about resolving that all GLD vocabs will use this conformance template? > > The key thing to me is that all vocabularies have a reasonable conformance section. I think it's a good idea if they follow the template at least in spirit. Whether they follow it in words isn't important to me. It's a template. Individual vocabularies will deviate from it in various ways. > >> Any objection to using it for DCAT, Richard? > > I proposed a conformance section for DCAT here: > > http://lists.w3.org/Archives/Public/public-gld-wg/2012Sep/0063.html > > It has a couple of points not contained in the template that I think are important. > > Best, > Richard > -- Phil Archer W3C eGovernment http://www.w3.org/egov/ http://philarcher.org +44 (0)7887 767755 @philarcher1
Received on Thursday, 18 October 2012 10:48:40 UTC