Assume a resource user. This resource defines a relation named parent, which points to another user.
Inclusion of related resources mentions relationship paths to refer to deeply “nested” relatives.
I am wondering if these kinds of paths should be supported when, for example, simply fetching a related resource. For example,
/user/123/parent.parent to fetch the grandparent.
I didn’t see this being mentioned in the spec, but I felt like it should be. If this path mechanism exists in another area, I feel like consumers of the API would expect this to work in other areas.
Am I mistaken? Is this sort of query already covered by another approach I’m currently not seeing?