Re: StatusCodeDescription vs. Status (ISSUE-32)

>>> That might not be entirely true as you could give that specific
>>> status an identifier and then return it as is as response:
>>>
>>>    {
>>>      "@context": "http://www.w3.org/ns/hydra/context.jsonld",
>>>      "@id": "http://example.com/api/errors/180984",
>>>      "@type": "Status",
>>>      "title": "Too Many Requests",
>>>      "description": "A maximum of 500 requests per hour and user is
>>> allowed."
>>>     }
>> I like that very much.
>> So much that I would actually recommend in the spec
>> that the status is given an identifier, that it's not just a blank
>> node. That way, it can be annotated easily later on.
> Cool! I've created ISSUE-39 to keep track of this:
>
>    https://github.com/HydraCG/Specifications/issues/39
>

I think this matches what we discussed in [1] already in the context of 
API documentation.
The tenor was to "combining returns with the Status description" and I 
specifically stressed
the fact that we can re-use such status code descriptions.

[1] http://lists.w3.org/Archives/Public/public-hydra/2014Feb/0102.html

Received on Monday, 3 March 2014 21:02:34 UTC