Now, when we create a sib-display to show a container, the listMixin only creates children with a data-src. Each sib-display child is now autonomous to create its own widgets. For example:

<sib-display data-src="http://server/users/">
    <sib-display data-src="http://server/users/1/"></sib-display>
    <sib-display data-src="http://server/users/2/"></sib-display>
</sib-display>

Also, we now get sources like this from our servers:

{
  "@id": "",
  "@type": "ldp:Container",
  "ldp:contains": [
    {
      "@id": "https://api.test-nantes.happy-dev.fr/users/",
      "@type": "ldp:Container",
    },
    {
      "@id": "https://api.test-paris.happy-dev.fr/users/",
      "@type": "ldp:Container",
    }
  ]
}

Does it seem fair to deal with the sources the same way? For example, to have a DOM like this:

<sib-display data-src="http://server/sources/users/">
    <sib-display data-src="http://server/users/">
        <sib-display data-src="http://server/users/1/"></sib-display>
        <sib-display data-src="http://server/users/2/"></sib-display>
    </sib-display>
</sib-display>

It works almost out of the box: no need for a FederationMixin, but the post-processing of the list is not working because it's handled at a top level

What do you think @balessan @sylvain @clement ?