Relationships level or basic rules joining related resourses

[deividas]

I have done some research:

@ethanresnick

@giannico

And if musicians also had another association, like, their “preferred” equipment, could those relationships be included as part of the document above, say under data.relationships?

Definitely. The drummer represented is just a standard resource object, so it can certainly include relationships of its own. In fact, it should include those additional relationships if they exist (unless there’s a ?fields restriction). That way, users can just follow one relationship to the next, to the next, without ever having to go back and request /musicians/9 directly.

From here: Usage of `related` field in Relationships link - #8 by ethanresnick

So, in real word example ( from my previous post ) i believe it should like something like this:

GET /v1/module/countries

{
  "links": {
    "self": "https://example.com/v1/module/countries"
  },
  "data": {
    "id": "county_id",
    "type": "countries",
    "relationships": {
      "state": {
        "links": {
          "related": "https://example.com/countries/county_id/states" // states is plural, it's ok?
        },
        "data": {"id": "state_id", "type": "state"}
      }
    }
  },

  "included": [{
    "id": "state_id",
"type": "state",
"attributes": {

},
"relationships": {
  "cities": {
    "links": {
      "related": "https://example.com/state/state_id/cities"  // cities is plural, it's ok?
    },
    "data": {
      "id": "cities", // what about cities id
      "type": "accountProfile"
    }
  }
}]
  }
 }

According this resource: Is it ok to add multiple levels of nested relationships in the relationships field - #2 by ethanresnick

But still i feel like missing something and confused about all these relationships and i don’t see any logical reasoning and connections between this complexity.