The path itself is not so important, but it seems like this app stores data in json files, not RDF. In Solid, there are basically two types of files:
- RDF files, with semantic data. This is the main way Solid Apps use to store their data.
- Binary blobs, for everything else (videos, images, etc.).
Of course, as you’ve seen with this application, there’s nothing stopping you from storing json, markdown, or even .sql files. But the chances that other Solid applications are going to understand this is very slim.
I’m curious, how did you come to the conclusion to use plain jsons in the Solid POD? Did you just ask an AI to make “a Solid App” for you and this is what it did? Or did you make a conscious choice to store the data in json format? If it’s the latter, what lead you to making this decision? I’m sure most Solid tutorials and resources that you will find online point you towards using RDF. Or if they haven’t, I’d be curious to see those tutorials.
As I said, the path is not so important. What is important, though, is that you leave a trace so that other apps can find the data created by your app (without knowing any specific container paths). Usually, you can do this with the type index. But since you’re not using RDF, it probably won’t be possible to do that.
I actually wrote a blog post about this topic a while ago, check it out if you want to learn more: Interoperable Serendipity.