Jørn Wildt

Sorry for bashing this, but I'm trying to figure out the best way to store app-data. Here is a very concrete example: I'm working on a web-app for logging flights...

Continuing on this line of thought: > Data belongs to the end-user, not the applications working on the data. Take "photos" as another example - my app lets the end-user...

Wow, didn't know Github would cross reference links in that way!

And here is another data storage guideline that would be nice to have: given that my pet-app stores a list of "my pets" ... should that list be stored as...

And yet another observation - it may not be such a good idea to store things directly under the root, like for instance `/pets`, for the simple reason that you...

> That latter thing is a UI bug we should fix. Ah, okay, then its back to `/pets` again :-)

> For example in my profile I Have : > > `http://www.w3.org/ns/pim/space#preferencesFile` > > `../settings/prefs.ttl` Yep. But I would still need some guidelines telling me what to store in that...

Things like https://github.com/solid/solid/blob/master/proposals/data-discovery.md, https://www.w3.org/TR/activitystreams-vocabulary/ and https://github.com/solid/solid/blob/master/proposals/app-discovery.md was suggested in the previous thread.

One easy-peasy way to solve this issue, would be to add a link like the one above to each of the resources: [, , ] Given that the current incarnation...

I do although think a better long term solution would be to let apps register URL templates for data types (as discussed in the linked solid/node-solid-server#944). The data browser would...