should sub-directories of solid:instanceContainer considered in apps?

[soltanireza65]

Suppose we have a solid:instanceContainer that points to https://pod-url.net/bookmarks/ in a typeindex document
That also has subdirectories such as /meetings, /video-tuts, etc.

should an app parse all files inside the sub-directories of /bookmarks or do only the first-level files have to be parsed?

[lecoqlibre]

should an app parse all files inside the sub-directories of /bookmarks or do only the first-level files have to be parsed?

I think it's depend on the client-client standard the app is following. In my understanding, TypeIndex should be used to advertise primary objects like contacts/address books, pictures and so on. Once an app has discovered its entry points, the next steps should be defined in a client-client spec that can be followed by different apps for ("vertical") interoperability.

[michielbdejong]

It would be very confusing if the meaning of solid:instanceContainer were different for various verticals! I think we should either understand it to mean direct containment + subfolders for all verticals, or only direct containment for all verticals.

[michielbdejong]

From https://github.com/solid/solid/blob/main/proposals/data-discovery.md#solidinstancecontainer:

solidInstancedContainer maps a type to a Solid container which the client would have to list to get the instances of that type.

It says "list", not "traverse" or "recursively traverse" so let's assume the answer to the OP's question is "no", unless new evidence to the contrary is found.

[angelo-v]

I am still unsure what "list" means. A container contains documents, not instances of the given type. So does it mean I have to read all documents contained in the container and consider all instances of the type found in those documents?