Link attributes in JSON Hyper-schema

[awwright]

The HTTP Link header, HTML, and Atom each define slightly different attributes on link relations. Things like hints at the target resource's media type, language, title, and other metadata that would otherwise require dereferencing the resource.

Perhaps JSON Schema should normatively reference these link-extensions or similar.

[yoshuawuyts]

@ACubed can you post an example? I'm not sure what you mean by "normatively reference". Thanks!

[awwright]

@yoshuawuyts A normative reference, where compliance depends on also complying with the referenced spec, as opposed to a mere informative one.

https://www.ietf.org/iesg/statement/normative-informative.html

[yoshuawuyts]

@ACubed ah, that makes sense. Thanks!

[Relequestual]

I'm unclear what the issue is here. Could you further explain the problem you see?

[handrews]

@Relequestual @awwright what I get from this is that we should explain what relations, if any, our Link Description Object fields have with link attributes defined by RFC 5988, HTML5, and/or Atom. Some of ours agree with some of those, others do not. And some of those do not entirely agree with each other.

It may be helpful to highlight our intentions for where we mean the functionality to be identical, and where we do not.

[handrews]

I think that the abstract link model in RFC 5988bis makes describing compliance a bit more straightforward, with its distinction between the abstract model and serializations (including the HTTP link header). Which means that "fixing" #377 will also address this issue, so I'll put it in the current milestone.

[handrews]

Merged #427 which addressed #377 which, as noted above, means that this issue has been addressed as well.