Open bblfish opened 9 years ago
Clearly they need to be cached locally, but also on a server so that a session can be restarted from its previous state on a different device. As a result it looks like the WebAgent should be the interface to all this information. But what should the name of the graph be where this is stored? This could be an arbitrary URI at first, but later one to be found from the user's profile page, where it can be stored - which means that the user first needs to be able to authenticate...
To start off with, we want to keep the state of the session of the user, even before we have his WebID profile, or a space where she can save the data. We therefore need a default graph name.
Here is a little space to play with some ideas. Just to get going first.
<> a solid:PreferencesGraph;
solid:pref [ a solid:Preference;
solid:application <https://github.com/read-write-web/rww-scala-js/>;
rww:preferedId <http://bblfish.net/people/henry/card#me>;
].
I started looking at this in this wiki page: https://github.com/read-write-web/SoLiD/wiki/Storing-an-Apps-Public-Key There is also a lot of work going on about this in SoLiD
How & where should one store app preferences? such as
Also preferences have to be named and distinguished so that preferences for small devices can co-exist with preferences for larger ones.