Apps become views, and you have the option of using any app you want with your data, which is stored on your pod.
The data is represented with common standards, so as to be portable. And the data is linked, so your todolist client could just as easily be written to work with other apps. (And since apps are just views and not data silos, you could fork your todo client, and implement the function you need)
This sounds like it's on the right track, but if I understand correctly, we'd still need a standard type of model for the data.
With that RDF example:
T1 is a task
T1 is labelled "Write an article about Solid"
T1 is due October 5rd 2018
T1 is assigned to @itsarnavb
T1 is incomplete
We'd still need to agree on those fields (like, labels, due, assigned, incomplete, etc.) or have some ability to re-interpret existing data.
So it might still be useful to come up with a shared format. Solid would certainly help in terms of making the data portable between these apps, though.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You're thinking along the lines of Solid.
Apps become views, and you have the option of using any app you want with your data, which is stored on your pod.
The data is represented with common standards, so as to be portable. And the data is linked, so your todolist client could just as easily be written to work with other apps. (And since apps are just views and not data silos, you could fork your todo client, and implement the function you need)
This sounds like it's on the right track, but if I understand correctly, we'd still need a standard type of model for the data.
With that RDF example:
We'd still need to agree on those fields (like, labels, due, assigned, incomplete, etc.) or have some ability to re-interpret existing data.
So it might still be useful to come up with a shared format. Solid would certainly help in terms of making the data portable between these apps, though.