If schemas are like language then they’re also better negotiated through common usage.
If schemas are like language then they’re also better negotiated through common usage.
The benefits of interop are greater than the convenience of not caring about standard formats.
[Choosing where and how to store data is less about how to make it work for one app work and more about all other apps.]
How does the way we write data impact others’ ability to reuse that data?
[The document box approach creates conflicts between 1) how data was obtained (provenance); 2) what it will be used for (trust); 3) logical groupings of items (context); 4) who has access (permission). For example, an address book app that dealing with all contact data versus a birthday app dealing only with one detail of many contacts.]
Let me compare my reading list with another to see overlap. I find this a wonderful way to spark conversation and find common interests.
[Sometimes it’s better not to decide what data you share, and defer the choice to someone with more expertise, such as medical data being provisioned by your doctor (who likely knows better how to respond to the request).]
Not only can my pod automatically fill out such forms; the forms don’t need to be there in the first place, because my pod can just share the needed data, machine to machine.
[Recipients will want to keep the trust envelope because it’s their proof to an auditor that they comply with its policy.]
Musician’s own website as definitive source of all info
I think the musician’s own “.com” homepage website should be the one-and-only place the musician ever has to enter their info. It should be the sole definitive source for their music, photos, bio, lyrics, calendar, blog, and especially their fan/friend/email list.
[With a modular enough system, people can simply curate components or plugins into a kind of software experience, requiring less effort or technical skill than programming.]
Interoperability is people connecting, communicating, collaborating.
Whereas classically we think of the situation where a user interacts with one identity provider, one storage provider, and multiple applications, recent experiments in practice have moved more towards also using multiple storage providers linked to a single identity.
There is an example app called Projectron which is mentioned throughout the Solid Application Interoperability spec and which can be used to track projects and issues; a first step would be to make this app compatible with the SolidOS Issue tracker, so that issues created through Solid OS will “magically” show up when you open Projectron.
Problems and Goals for Interoperability, Collaboration, and Security in a Solid Pod
Applications must have a shared understanding of data
Data must be discoverable.
Data must be durable.
Data must be portable.
Problem #3 - Disparate entities using different applications must be able to safely and effectively interoperate within their scope of authorization
Problem #4 - People shouldn’t need to think about how to physically organize their data to use Solid.
Embark - Dynamic documents for making plans
Travel-certified trip planning demo combining end-user programming and customization, spreadsheet-like formulas, text as super app.