As @CodeTripper and @fdrake said, this is not clear at all in microservices world… will you clarify it fast or shall I say to fellows JSON:API is just theory unusable in microservices real world scenarios?!
Probably b) is right answer when there is no response for more 2 years.
So now looks like I should check SIREN before we will go with custom, almost JSON:API standard, solution.
I’d like to clarify that the confusion I expressed has nothing to do with a microservices implementation; it’s strictly based on the specification.
I don’t think the implementation strategy (microservices or a monolithic service) is really relevant at this level.
The slowness in clarifications is an issue I’ve brought up with maintainers in the past, more than once. Since it’s significantly resource-constrained, I’m not sure it can be addressed effectively. I’ve certainly found it very frustrating.
-Fred
@fdrake Is the clarification you identified already addressed in v1.1? If not, do you have time to create a GitHub issue for tracking it? If there is a GitHub issue (or even PR) for it already, please point me to it. I will try to have a look asap.
Egads, that was 29 months ago! Took a bit of head scratching to remember what I was thinking back then.
Taking a look at the current 1.1 candidate, I think the requirement is pretty straightforward, and an implementation can provide them reasonably. My thoughts on how related links could be implemented remain applicable, but don’t need any changes or clarifications in the specification. And other implementations are equally possible and valid with respect to the specification.
-Fred