Re: [dxwg] DCAT 1.1 URL in W3C space

If DCAT 1.0 is expressible as a profile of DCAT-ver then the set of DCAT1.0
instances are also valid DCAT-ver instances.

I would expect reasoning over DCAT 1 to be a small enough case that
requiring explicit importing of the profile axioms to reason over DCAT 1.0
semantics is a reasonable expectation - but this is something we can posit
explicitly in the FPWD - and if counter-arguments emerge then we can deal
with it.

There may be a requirement to reason over the universe of DCAT1.0 and
DCAT-ver separately - again I'd like to see evidence of this before tying
ourselves in knots.

If not, then far simpler and more useful to move forward without versioning
and not arbitrarily split the universes.


On Tue, 3 Apr 2018 at 09:10 Andrea Perego via GitHub <>

> Thanks, @makxdekkers .
> Backward compatibility is indeed crucial. The new DCAT can have new things
> - and a wider scope -, relax domain and/or range restrictions, deprecated
> terms, but this must not affect backward compatibility. And I think this is
> also in line with the (unwritten?) W3C rules for vocabularies.
> If using "version 2" may give the wrong message that the new DCAT is not
> compatible with the original one, I'm happy with "version 1.1".
> I'm also happy with the idea of using the "rev" string (or another
> keyword). In this case we should probably add a revision number, e.g.:
> But the vocabulary namespace must be the same:
> --
> GitHub Notification of comment by andrea-perego
> Please view or discuss this issue at
> using your
> GitHub account

Received on Tuesday, 3 April 2018 02:03:51 UTC