This is just me thinking in the public in the hope of getting a bit of feedback …
Assume we have a note taking app that allows you to assign a location to each of your personal notes - something like “Copenhagen” or “At home”. How would you build a UI/UX for selecting those places?
Usually the application and user owns it’s own data, so the application itself would have a place where you could edit your list of possible locations and then just let the user select from those when entering a new note.
But with Solid/Linked Data you are expected to use standard vocabularies and maybe even open data sets (if possible) - so in this world it might be more natural to use pre-existing locations from, for instance, Wikipedia - and instead of relating notes to locations own by the note-taking app, we should let the user select locations from any place in the world.
On a more practical level this would mean location URLs like http://dbpedia.org/page/Copenhagen and using “foaf:name” to display the title - instead of location URLs like https://my-account.solid.community/public/my-locations/copenhagen-1234 and some proprietary name predicate.
But entering URLs from DBPedia is not exactly the most easy thing to do for the average user - and I am pretty sure DBPedia does not have an entry for “At home” (my home).
So you need some kind of mix - let the user manage a list of their “prefered” locations where they can either create their own locations the classic way - or add DBPedia links to places they want to reference.
It also implies that your app must not expect too much about the target of the location URL since the data may not be under its own control and thus not necessarily conform to anything known by the app.
You can repeat this for all sorts of “related stuff”. For instance colors, pet animals, car brands and so on.
Any thoughts about this?