![]() ![]() In general when you bare collaboratively editing anything then you want the changes each person makes to be propagated You expect messages in a chat to be as instant as they can. To synchronize every few minutes or every few hours. You may be happy for your calendar events Speed It will vary in the sort of speed a person needs of access to it. You can refer to the by their cryptographic hash as a another name. You can store them on write-once devices, like optical disks. It means that you can keep cached copied of these things forever. Of the archive of chat messages and social actions of past days. Many documents, like birth certificates, drivers licenses and passports and theĭigitally signed certificates that once has taken a course, are just issued once and never change. ![]() Immutability It will vary into whether it is, once written, unchangeable. ![]() Some shapes, like events and contacts, maybe be ubiquitous, and some, like Relating somehow to one interesting incident. Shape It will vary is shape, from simple table data to complex graphs of many different connected objects of differentĬlasses such as a compilation of all of the data the a journalist have Though medium sized things like events and photos, though to huge things like genome data,Īnd scientific data from climate change experiments. Size It will vary in size, from single byte information ("The Doctor is ") This data will vary hugely in a number of dimensions we already see to a limited extent Yourself in real-time ultrasound scan form. Maybe sing in a choir together, say, or share Online but you will be able to in future. This will include activities which currently you can't really do Gaming systems, pubic kiosks, Automatic Teller Machines. The activities in your life you currently do on your phone, on on a web app, or on a laptop, It should be able to include any data in your life, across the data spectrum from public to private We need to think about the huge variety of data which there will be. When we think in general about the structures for organizing data in a pod, Keeping stuff related to the same activity together in a pod,Įven though it is of many different types, is valuable, because the same access and trustĬonditions apply and it is much simpler to get those right. Way we really trust data, people and bots in this very rich, varied, and valuable system. We track and use its provenance carefully and carefully control is access, to be able to model the We expect the classes of data used by different apps to overlap a lot. We do this by principally initially keying data by its RDFS Class, not by the particular app which wrote it.īut then different apps need to be able to create very specific structures including many different types. We expect different apps to often shared common design patterns for similar types of data. Which meets these requirements, and also works well for that particular app. We must give applications the power to configure this data in the users pod in a way To be extensible across these dimensions, It's needs for security, may be very different.īut still it must be organized in clear way, extensible way, andĪ way which allows interoperability between different application. ![]() This data will vary hugely in size and shape, and immutability, and it's needs for speed, and And activities which currently you can't really do The activities in your life you currently do on your phone, on on a web app, What should be in your Solid Pod? Anything, of course.Īny data in your life, across the data spectrum from public to privateĪnd everything shared with communities in between. ![]()
0 Comments
Leave a Reply. |