RE: Modeling permissions with Hydra

Am 10.11.2015 22:43 schrieb Markus Lanthaler <markus.lanthaler@gmx.net>:
>
> On 9 Nov 2015 at 10:54, Asbjørn Ulsberg wrote: 
> > 2015-11-06 20:35 GMT+01:00 Ryan Shaw <ryanshaw@unc.edu>: 
> >> 1. There still doesn't seem to be consensus on the function of the API 
> >> documentation. Markus' position, if I understand correctly, is that 
> >> the API documentation is a kind of convenience or shortcut for 
> >> specifying state transitions; rather than or in addition to including 
> >> this information directly in representations. The advertised state 
> >> transitions from any specific representation are always the aggregate 
> >> of 1) the transitions specified in the representation itself PLUS 2) 
> >> any transitions specified in linked documentation. 
>
> This is not "my position". It is how it is currently defined. If you have a class C which supports operation O and a resource of type C, then a client can infer that the resource supports O. 

It does not seem that a reasoner can infer (as in RDF inference) the :operation triple on the resource from the :supportedOperation triple on the :Class. Or do I miss something? 

Dietrich