W3C home > Mailing lists > Public > public-hydra@w3.org > June 2014

RE: Specifying operations for instances

From: Markus Lanthaler <markus.lanthaler@gmx.net>
Date: Wed, 18 Jun 2014 22:51:27 +0200
To: <public-hydra@w3.org>
Cc: "'McBennett, Pat'" <McBennettP@DNB.com>
Message-ID: <016a01cf8b37$14a45590$3ded00b0$@gmx.net>
On 18 Jun 2014 at 09:53, McBennett, Pat wrote:
> Markus Lanthaler wrote on June 15, 2014 8:09 PM:
>> On 14 Jun 2014 at 23:27, Tomasz Pluskiewicz wrote:
>>> I understand that the resource still supports the DELETE because it is
>>> an instance of the ForumPost class. But in very practical terms, would
>>> you consider the absence of the DELETE operation in the instance's
>>> representation a good enough clue for the client not to render a
>>> delete button?
>> 
>> Yes, with the caveat that the ApiDocumentation doesn't tell me otherwise. 
> 
> Ok, I totally agree here, but this seems to be contradicted below at [1]...

a)

[...]

>>> I meant the guidelines would be more appropriate than rules.
>>> 
>>> I think what's missing is or vague is:
>>> 1. what clients should assume if a resource representation has some
>>> but not all of the supported operations defined by it's class
>> 
>> The operations associated to the resource itself and the ones associated to
>> its class are merged. After that, they are indistinguishable. Again, it doesn't
>> matter where the operations are asserted. 

b)

> [1]... but if this is the correct assumption, then won't the client always have to render the
> DELETE button in the example above? There seems to be a clear inconsistency here...

No. Example a) might looks like this:
  ApiDocumentation: ForumPost supportedOperation x, y, does *not* include DELETE
  /posts/a operation z, *not* a DELETE

No DELETE in the representation of /posts/a and the ApiDocumentation also "doesn't tell me otherwise", i.e., also doesn't include a DELETE.

Example b) might look like this
  ApiDocumentation: ForumPost supportedOperation x, y, does *not* include DELETE
  /posts/b operation x (again, *not* a DELETE)

The representation of /posts/b includes some (x) but not all (y is missing) operations know to be supported by instance of the class ForumPost.

Thus,
   /posts/a has the following operations: x, y, z
   /posts/b has the following operations: x, y

Where do you see "the clear inconsistency" Pat?


--
Markus Lanthaler
@markuslanthaler
Received on Wednesday, 18 June 2014 20:51:59 UTC

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