Embedded representations and their context

[chrysn]

Around the topic of storing problem details, it appears that there is some need for storing contexts of requests.

When we next take a closer look at embedded representations, we might want to look into whether CoRAL can help here. (Especially when methods like POST are involved where the response is not a representation of a named resource but of an anonymous one).

I've seen patterns like this in RDF processors:

[ a http:exchange,
  http:request_uri "http://...",
  http:request_method "POST",
  http:response_code 502,
  http:response_body "...",
]

With the concepts of navigating forms, this might look a bit prettier. I don't expect any of this to be "navigated" by a constrained device, but it touches on topics we already express in CoRAL, and it might be found on constrained devices as logging output.