- From: Melvin Carvalho <melvincarvalho@gmail.com>
- Date: Sat, 16 Mar 2019 12:36:29 +0100
- To: Mitzi László <mitzil@inrupt.com>
- Cc: public-solid@w3.org
- Message-ID: <CAKaEYhKrVDNA7Y=FKXEotBV-txs5AMAFE3Nzec7FrukLkxiyqg@mail.gmail.com>
Solid is basically a web file system leading to a web operating system. On Sat, 16 Mar 2019 at 11:33, Mitzi László <mitzil@inrupt.com> wrote: > Hi W3C Solid Community Group, > > In preparation for our call next Thursday I wanted to share some thoughts > on the following agenda item: > > - Discuss possibility of Solid Design Requirements Specification in > particular the potential for defining the default data sharing settings in > such a way that the user is protected while able to engage at a minimum > level. > > > I have begun to write the Solid spec chronologically i.e. detailing the > technical requirements when they are relevant to the user journey. It is a > very rough draft. The purpose of this thought experiment is not to restrict > the path, rather to identify where the default design is critical and if > there are any technical requirements that if done by a single party would > result in a conflict of interest to the core values of Solid. I would like > to talk about the minimum. > > As homo sapiens, the default tends to be our choice, we are lazy. Rather > than fight our natural wiring (which anyone who went on a diet can tell you > is tough) I think we should reflect on the default to make sure it > represents our more considered choices and defined values. > > Pat’s work on G consent could be a very useful reference to build on > http://openscience.adaptcentre.ie/ontologies/GConsent/docs/ontology > > Depending on our conversations next week perhaps this could be a new > repository on the Solid GitHub. > > Please excuse me for using Microsoft Word, however, it illustrates the > point I am trying to make rather neatly. > > Mitzi > > > >
Received on Saturday, 16 March 2019 11:37:02 UTC