RE: DCAT Last Call issues: additional rules for skos:Concept

> 
> You've snipped my reference to the part of the spec that discusses
> these questions.

Oh sorry. Yes, I read that the example says that the theme used for a
dataset *should be* part of the concepts scheme identified for the
catalog.  But that is in a non-normative section of the spec so there is
no formal rule that requires that.

> 
> > But most of all, I don't understand why "discovering the entire
> concept
> > scheme" is a requirement. Are you saying that an application that
> uses
> > DCAT without being able to find out the concept scheme(s) used is in
> > some sense not useful?
> 
> It is not a requirement. That's why dcat:theme is optional.

Yes I know that dcat:theme is optional. 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.

Makx.

Received on Tuesday, 26 March 2013 16:33:16 UTC