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.
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.