According to the section about Hypertext cache pattern:
To activate this client behaviour for a given link, servers SHOULD
add an embedded resource into the representation with the same
relation.
Servers SHOULD NOT entirely "swap out" a link for an embedded
resource (or vice versa) because client support for this technique is
OPTIONAL.
This would imply that to have an embedded resource ea:order there SHOULD be a link ea:order which in this case would be an array of links, where each link points to a resource (which is what is being embedded).
Hi Mike,
I think there was a thread in hal-discuss about this but shouldn't the example in the main page have an
ea:order
within the links section? like so:According to the section about Hypertext cache pattern:
This would imply that to have an embedded resource
ea:order
there SHOULD be a linkea:order
which in this case would be an array of links, where each link points to a resource (which is what is being embedded).If you agree I can make a pull request.