I want to develop a linked data collections application for Solid as part of my master thesis. I choose a collections app as this is one of the use cases I am most excited about. Currently data like this is saved with the content providers and is a pain to migrate to a new platform. I want a single source of truth of all movies, tv series and songs I have ever listened to or watched that can be synced with existing content providers.
I have set up the basics already but now I come to the actual storing part of the application. I have been wrapping my head around countless articles on how to store RDF correctly and about the used ontologies. But some points especially the modeling of how to store the data so other apps can easily compare them is still a problem.
Some of the questions/ideas that are still open:
Should I use a existing ontology to safe the data and what data should I save?
I was thinking about defining my own ontology for the saved data, but could I somehow store that within my Solid pod?
I could also use the existing movie schema from schema.org but than where do I stop with saving data?
Has somebody experienced similar problems?
The thing is we don’t have a go to solution yet for stuff like this and we need to figure out how we really want to do this. We can only save the most basic data like a link to the movie with stuff like a rating, comments and a state like seen, but in reality most of this data is quite static so it might make sense to store it with the entity.
In my opinion we should have like a file per entity e.g. movie, tv series, artist with its sub entries like episodes, albums and tracks.
Than there would be collection files that link to the entity files where collections could be watched, owned or want to watch.
For individual actions like watched, added to collection, rated I would create something like an activity stream per resource entity. The activity stream would write to a new file each month/year to keep files manageable.
Any input on this is highly welcome!