Another attempt to enable hydra for non-RDF resources

Dear hydranians

On the last conf-call we've made a small agreement on how to proceed
with the vocabulary's evolution towards non-RDF resources handling.

To make things short, conclusion is that the currently used
specification of the hydra:expects and hydra:returns should me
slightly modified so it will be possible to introduce either built-in
new vocabulary terms or protocol-specific extensions presented in
future.

I've create a new pull-request #200 [1] on the hydra's Specifications
GitHub. Please, take your time to take a look at it as it does change
`rdfs:range` of the aforementioned predicates, which possible may
break something within existing implementations and/or specifications.

I know that it may be inconvenient, but it feels it is the only
reasonable way of moving forward with the vocabulary's development
(alternative modifications were worse!).

I hope to receive some feedback.

Kind regards

Karol Szczepanski

[1] https://github.com/HydraCG/Specifications/pull/200

Received on Monday, 9 September 2019 19:39:15 UTC