Erik Wilde
Erik Wilde
i guess the point i was raising here is related to #191 (the question whether the `service-*` link relations might fit into JSON home).
specifically, the example given currently looks like this: ``` "api": { "title": "Example API", "links": { "author": "mailto:[email protected]", "describedBy": "https://example.com/api-docs/" } ``` by using more specific link relations, the example...
would it help if i submit a PR replacing the more generic `describedBy` approach with the more specific `service-*` one?
possibly related to #212
it seems that this is a valid point, and one issue that tends to surface in certain ways of representing links in JSON. some designs then go the route of...
On 2017-10-10 18:04, Henry Andrews wrote: > We're struggling a bit with this in JSON Hyper-Schema as well. > Currently, our |links| is an array of objects (which may use...
as one additional data point: https://tools.ietf.org/html/draft-wilde-home-xml-03#section-4.1 defines `application/problem+xml` assuming that the structured syntax suffix is a useful pattern to follow.
@RubenVerborgh: it is an RFC (https://tools.ietf.org/html/rfc6838), but media types are free to follow or ignore this pattern.
On 2016-07-19 22:42, James Cox wrote: > In this example, the success of this request is contingent on the HTTP > client replacing || with |%20|. Are you sure that's...
On 2016-07-23 13:59, Chris Mullins wrote: > @dret https://github.com/dret Can you explain what you mean by this: > and of course there's the wonderful issue of IRIs. those at least...