Matches in Ruben’s data for { ?s ?p "When a Solid application writes data to a storage, it does not yet know all possible use cases for which this data will be used. With cross-app interoperability in mind, choosing an application profile and write-structure becomes guess-work: some apps will only work partially with more shallow semantics, some will work slower without a querying API such as a SPARQL endpoint, or some will just not work at all. This requires studying negotiation processes between what apps need to be able to read and how apps write. In this paper, we position our opinion that Solid apps must always write using the richest semantics available to them, which must be written to an interface that is tailored to handle replication and synchronization of data across services. We show how to store data as an Event Source on Solid using the Linked Data Event Streams specification applied to the use-case of storing personal location history. The history of the data is preserved by design, as an Event Source stores all the changes in the data over time. For reasoning of backwards compatibility, we also illustrate that for both reading and writing to the Event Source the complexities can be abstracted away towards a symmetric read/write interface following the current Solid specification."@en }
Showing triples 1 to 1 of
1
with 100 triples per page.
- publication abstract "When a Solid application writes data to a storage, it does not yet know all possible use cases for which this data will be used. With cross-app interoperability in mind, choosing an application profile and write-structure becomes guess-work: some apps will only work partially with more shallow semantics, some will work slower without a querying API such as a SPARQL endpoint, or some will just not work at all. This requires studying negotiation processes between what apps need to be able to read and how apps write. In this paper, we position our opinion that Solid apps must always write using the richest semantics available to them, which must be written to an interface that is tailored to handle replication and synchronization of data across services. We show how to store data as an Event Source on Solid using the Linked Data Event Streams specification applied to the use-case of storing personal location history. The history of the data is preserved by design, as an Event Source stores all the changes in the data over time. For reasoning of backwards compatibility, we also illustrate that for both reading and writing to the Event Source the complexities can be abstracted away towards a symmetric read/write interface following the current Solid specification.".