Excellent points @josephguillaume. I’d like to elaborate on your statement “containers provide limited semantic information about their content” because that fact is a key sticking point in how new users transition into Solid.
On my home computer, I have a folder labeled “Music” and, in that, a hierarchy of “World Music”, “African Music”, “Afrobeat”, “Fela Kuti” and, within that, files that end in extensions .ogg, .mp3, etc. While not everyone is as obsessive as I am, something like this is the way most people relate to their personal computers.
As, @justin points out above, "There is a 1-1 correspondence between containment triples and relative reference within the path name hierarchy. "
So if containers correspond to path hierarchies, why can’t I just slap my folder structure from my home computer onto my pod and call it quits? Well, I can. Pods will let me treat them that way. I’m done, right? Terms like “Music” and “African Music” appear semantic to me. So I’m living the Solid life, cool!
But the labels I put on the containers have no meaning to software. Software can’t guess from the label that “Afrobeat” is a kind of “African Music”. It can’t even tell from the .ogg and .mp3 extensions that the files contain music - they might be voice recordings. And what happens if I want a list of other saxophone players or musicians from Nigeria?
That’s the real Solid life - being able to tell the software that Afrobeat is a kind of African music and that Fela Kuti is an Afrobeat musician, a person, a Nigerian, a strong advocate of African autonomy, and a saxophone player and that those particular .ogg and .mp3 files contain his music.