- From: Fadi Maali <fadi.maali@deri.org>
- Date: Thu, 30 May 2013 16:49:23 +0100
- To: Makx Dekkers <makx@makxdekkers.com>
- Cc: Richard Cyganiak <richard.cyganiak@deri.org>, GLD Public Comments <public-gld-comments@w3.org>, John Erickson <olyerickson@gmail.com>
Makx, apologies I forgot to push the changes online. Now I did: https://dvcs.w3.org/hg/gld/raw-file/default/dcat/index.html#class-concept The new text makes it clear that this is a requirement on the concepts used with DCAT and the datasets and not to all SKOS concepts. It also changes necessary to recommended. it says: "It is recommended to use either skos:inScheme or skos:topConceptOf on every skos:Concept used to classify datasets to link it to the concept scheme it belongs to. This concept scheme is typically associated with the catalog using dcat:themeTaxonomy" Thanks again, Fadi -------------------------------------------------- Fadi Maali PhD student @ DERI Irish Research Council Embark Scholarship holder http://www.deri.ie/users/fadi-maali On 30 May 2013, at 16:44, Makx Dekkers <makx@makxdekkers.com> wrote: > Fadi, > > Thanks. I guess you refer to the text: "It is necessary to use either skos:inScheme or skos:topConceptOf on every skos:Concept otherwise it's not clear which concept scheme they belong to." > > The text is fine with me, but my point was really that this requirement is a limit on the set of concepts that can be used to describe datasets. As far as I know (but correct me if I am wrong), there is no obligation for a skos:Concept to be in a skos:ConceptScheme. So if someone defines a set of concepts without explicitly asserting the relationship with a concept scheme using skos:inScheme, those concepts are illegal values in the context of DCAT. > > But I can't really judge if that would create problems in practical terms. > > Makx. > > > > > > On 30 May 2013 16:23, Fadi Maali <fadi.maali@deri.org> wrote: > Hi Makx, > > regarding you comment on DCAT and SKOS: > http://lists.w3.org/Archives/Public/public-gld-wg/2013Mar/0201.html > > >It's just that I ask for > >clarification to understand why, as soon as someone uses dcat:theme, > >DCAT expects a certain behaviour, either based on a formal rule > >(normative in 5.5: "It is necessary to use either skos:inScheme or > >skos:topConceptOf on every skos:Concept") or in non-normative note (the > >one in 4.2). > > > > to know why those rules are necessary for the base specification. > >>They are not necessary. But they are beneficial for the use case of > >>filtering a DCAT-enabled catalog by theme. This is a feature that's > >>supported in the majority of government data catalogs, and DCAT is > >> designed to support exactly that set of features. > >> > > >I think it might help the reader of the specification if such expected > >behaviour were made explicit. > > > Please notice that I "hedged" the language in the Spec now: > https://dvcs.w3.org/hg/gld/raw-file/default/dcat/index.html#class-concept > > Do you agree with the new text? > > Best regards, > Fadi > > -------------------------------------------------- > Fadi Maali > PhD student @ DERI > Irish Research Council Embark Scholarship holder > http://www.deri.ie/users/fadi-maali > > > > > -- > -------------------------------------------------------------------------------- > Makx Dekkers > makx@makxdekkers.com > --------------------------------------------------------------------------------
Received on Thursday, 30 May 2013 15:49:54 UTC