Re: remove hydra:Resource and hydra:Class

> 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/ ;-)

Best,

Ruben

Received on Tuesday, 6 January 2015 14:44:44 UTC