Re: remove hydra:Resource and hydra:Class

>
> > John's approach to deprecate old stuff makes sense. How about
> > deprecating hydra:Resource and hydra:Class, then?
>
> I would remove, because they are (needlessly) used in the modeling.
> Furthermore, our own ontology is the only one that uses it.
> It's bloat—I think we need to get rid of it while we still can.
>
> Note that changes such as repurposing hydra:writeonly to hydra:writeable
> had far more consequences, yet we didn't use deprecation either.

Here I'd put a caveat that Hydra core vocabulary is still a 'draft' and subject
to change.
More formal change control should be applied once it is released.

Early adopters/implementers understand that things are still subject to change
and accept the consequences.

>
> Best,
>
> Ruben

Cheers,
John