thanks @fdrake , but was more about to see if can support a relationship path that’s beyond the filtered by type. i.e.,
instead of
http://www.example.com/debtors?filter[assets.type]=houses
trying to see if with a generic relationship (assets) that links to heterogeneous resource types (houses/cars/securities etc),
would it be possible to achieve something like this
/debtors?included=assets.houses&filter[assets.houses.zipcode]=xxx
i.e.,
with JSON:API spec, would that kind of relationship path be possible? or that would be implementation semantic?