W3C home > Mailing lists > Public > public-hydra@w3.org > January 2015

Re: remove hydra:Resource and hydra:Class

From: John Walker <john.walker@semaku.com>
Date: Tue, 6 Jan 2015 16:35:42 +0100 (CET)
To: Ruben Verborgh <ruben.verborgh@ugent.be>, Dietrich Schulten <ds@escalon.de>
Cc: public-hydra@w3.org
Message-ID: <2085134146.2694190.1420558542398.open-xchange@oxweb03.eigbox.net>
> On January 6, 2015 at 3:44 PM Ruben Verborgh <ruben.verborgh@ugent.be> wrote:
>
>
> > That seems an incompatible change, so it will break existing
> > implementations.
>
> It would most definitely not.
> Where would it break?
>
> > Since that won't be the last time that an
> > incompatible change happens - does it make sense to introduce some
> > versioning scheme, e.g. add date information to the hydra URL, like
> >
> > "hydra": "http://www.w3.org/2015/01/ns/hydra/core#"
>
> That's how FOAF got stuck with http://xmlns.com/foaf/0.1/ ;-)
>

Indeed, putting version numbers into URIs is not *cool* in this case.

Having a versioned URI for the information resource where you can get a certain
snapshot/release of the vocabulary is all fine, but the concept of
hydra:Resource is *the same* thing across all releases of the vocabulary so
ideally the URI should also be the same.
If you change the definition of the concept sufficiently that it is a breaking
change, it should get a new URI and the old concept marked as deprecated.
Also don't re-use/re-purpose URIs for a different concept.

> Best,
>
> Ruben
>
Received on Tuesday, 6 January 2015 15:36:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:29:44 UTC