Got a question that’s not here? Try asking on the Solid forum, on the Matrix Solid Project room or using the Solid tag on Stack Overflow.
+Got a question that’s not here? Try asking on the Solid forum, on the Matrix Solid Project room or using the Solid tag on Stack Overflow.
Examples of personal data include: location, genome data, written communication, spoken communication, lists of contacts, internet browsing habits, financial transactions, supermarket spending, tax payments, criminal record, laptop and mobile phone camera lens recording, device microphone recordings, driving habits via car trackers, mobile and health records, fitness activity, nutrition, substance use, heartbeat, sleep patterns and other vital signs.
-In Europe personal data is defined under the General Data Protection Regulation (GDPR) as "any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical,physiological, genetic, mental, economic, cultural or social identity of that natural person;"
+In Europe personal data is defined under the General Data Protection Regulation (GDPR) as "any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical,physiological, genetic, mental, economic, cultural or social identity of that natural person;"
According to the Cambridge dictionary, interoperability is “the quality of being able to be used together”. For example, if you use a Solid app, you can store your data in any Pod because apps and Pods are interoperable. Also, you should be able to reuse data from one Solid calendar app to another because apps are interoperable.
+According to the Cambridge dictionary, interoperability is “the quality of being able to be used together”. For example, if you use a Solid app, you can store your data in any Pod because apps and Pods are interoperable. Also, you should be able to reuse data from one Solid calendar app to another because apps are interoperable.
A Pod is where data is stored on the Web with Solid. (see quote). A user may store their data in one Pod or several Pods, and applications read and write data into the Pod depending on the authorisations granted by the user or users associated to that Pod.
+A Pod is where data is stored on the Web with Solid. (see quote). A user may store their data in one Pod or several Pods, and applications read and write data into the Pod depending on the authorisations granted by the user or users associated to that Pod.
A WebID is a unique identifier used to identify a specific user. An example of what a WebID could look like is: https://fulano.pod.provider/profile/card#me. To share data with a third party, a user associates sharing preferences to the WebID of that third party. Don’t worry though: it’s not just one more login to remember.
A WebID is an Internationalised Resource Identifier (IRI) that can be dereferenced as a FOAF profile document serialized in RDF (source). In Solid, WebIDs are used to identify Agents i.e. people and organisations as well as to manage their access rights though Web Access Control.
+A WebID is an Internationalised Resource Identifier (IRI) that can be dereferenced as a FOAF profile document serialized in RDF (source). In Solid, WebIDs are used to identify Agents i.e. people and organisations as well as to manage their access rights though Web Access Control.
To log into Solid apps and/or access data on Pods, you just have to provide your WebID and login to your Identity Provider, like "Sign in with Google" today. It is possible for the same company or organisation to be both a Pod Provider and a Identity Provider although they are distinct separable services that are compatible with other Pod Providers and Identity Providers (which means you are free to choose the provider that suits you the most).
An Identity Provider implements an identification protocol (e.g. OIDC), and allows you to prove that you own the WebID.
+An Identity Provider implements an identification protocol (e.g. OIDC), and allows you to prove that you own the WebID.
A Pod Provider delivers storage space under one or more domains, usually (but not necessarily) pointed to by <webID> solid:storage <pod> statements included in the profile document associated to the WebID.
Solid does not reinvent the wheel. When you use Solid you will still be able to access your data using the same Web browser on the same computer. Solid is still the web, but with a few things added and a few assumptions overturned (see quote at 33:30).
+Solid does not reinvent the wheel. When you use Solid you will still be able to access your data using the same Web browser on the same computer. Solid is still the web, but with a few things added and a few assumptions overturned (see quote at 33:30).
Solid adds:
Solid is built on top of existing Web standards. The core Solid specification relies on LDP and WAC (WAC draft, both being based on HTTP and RDF vocabularies. Solid also uses a subset of SPARQL UPDATE through HTTP PATCH queries. Identification in Solid is based on WebID-TLS and/or OIDC.
+Solid is built on top of existing Web standards. The core Solid specification relies on LDP and WAC (WAC draft, both being based on HTTP and RDF vocabularies. Solid also uses a subset of SPARQL UPDATE through HTTP PATCH queries. Identification in Solid is based on WebID-TLS and/or OIDC.
No. Self-hosting means that your data would sit at home on your own physical hard drive or server. Self-hosting is possible but not essential when using Solid, and it currently requires some technical knowledge. A Solid user can rely on an Identity Provider and a Pod Provider, and is not expected to have any particular expertise. It is also possible to self-host and become a small Identity Provider and Pod Provider, to provide Solid to your family, association, friends…
The Solid standard is open as are some of its implementations such as the Community Solid Server meaning that anyone can self-host their own Identity and Pod or the Identity and Pod of a group of users.
+The Solid standard is open as are some of its implementations such as the Community Solid Server meaning that anyone can self-host their own Identity and Pod or the Identity and Pod of a group of users.
Yes, the same data point can exist in more than one Pod. You can choose to have more than one Pod deliberately, for example for work and for home, in which case, some data may be relevant to both settings. You can also choose to have a single Pod and give selective access. Some data is relevant to multiple users so may be replicated in a slightly different way in another person’s Pod. For example, if you have a conversation with someone the data may be stored in both your Pod and the Pod of the person you spoke with.
Eventually, yes. The Solid long term vision includes local first and a flexibility of different topologies of patch-passing sync networks. However, there are no implementations yet.
Yes, unless the Pod provider doesn’t allow you to. The best way to understand the service of a particular Pod provider is to read the Terms. There are some support tools like Terms of Service; Didn’t Read to help you understand the small print more easily.
+Yes, unless the Pod provider doesn’t allow you to. The best way to understand the service of a particular Pod provider is to read the Terms. There are some support tools like Terms of Service; Didn’t Read to help you understand the small print more easily.
The data in Solid Pods is structured according to Linked Data principles by the applications writing them in the first place. Therefore, the Pod Provider is completely neutral regarding the Pod content, and the same data structure should be supported by any Pod Provider. The storage technology picked by each Pod Provider is another question.
@@ -125,7 +125,7 @@Each Pod Provider may offer a its own procedure to delete Pods, which means closing the storage space they rented to you. Once your Pods are deleted, you can delete your WebID by closing your account at your Identity Provider. As for Pod Providers, the exact procedure may differ from an Identity Provider to the other. Remember that you need to log in your Identity Provider to have access to your Pods: if you delete your Identity Provider account first, you may lock yourself out of your Pods.
Technically, you may host your FOAF profile independently from your Identity Provider, and have it point to a WebID you control. In this case, to fully delete your Solid identity, you may want to delete this profile document as well.
+Technically, you may host your FOAF profile independently from your Identity Provider, and have it point to a WebID you control. In this case, to fully delete your Solid identity, you may want to delete this profile document as well.
The Data Transfer Project is a great start. The next step is to build a healthy array of options for users to make their data work for themselves.
+The Data Transfer Project is a great start. The next step is to build a healthy array of options for users to make their data work for themselves.
It is possible for developers to take an iOS or Android app and make it Solid compatible by following the standard and supporting documentation.
@@ -153,7 +153,7 @@Currently there are no developer kits in development for Android or iOS. If you really want to have an app that can be installed on Android or iOS, you might consider writing it as a progressive web app or writing it as a hybrid app.
The Semantic Web and Linked Data principles and technologies have always meant to make data more reusable, and to make data independent from applications, which is why it is at the core of Solid.
+The Semantic Web and Linked Data principles and technologies have always meant to make data more reusable, and to make data independent from applications, which is why it is at the core of Solid.
The Semantic Web and Linked Data technologies are centered on the question of interoperability. By using these technologies, data is provided a context and is made more reusable. In order to achieve one of the goals of Solid and enable applications to share and reuse data without having the control over it, this kind of interoperability is key, and the Semantic Web and Linked Data principles and technologies seemed to be the fittest for this purpose.
@@ -182,7 +182,7 @@If you would like to ask for your data to be deleted from other services, In Europe there is a law called the Right to be Forgotten which makes it possible for European citizens to ask for their data to be deleted. See datarequests.org’s sample GDPR erasure-request letter for template letters and instructions on how to exercise this right.
Yes. Today, other people and organisations have a copy of your data, but you may not. If you join Solid and move your data there, it does not prevent the apps already having your data to keep their copy. However, these apps will have to ask for your authorization to access the new data you store in Solid.
@@ -213,7 +213,7 @@There is a lot of variation in what people feel to be right and wrong, and ultimately it is down to you to decide what to do with your data. Solid does try to help you make informed choices by providing relevant information and by constantly validating the accuracy of that information.
The Solid specification warns that the “trusted apps” feature is new and experimental, as it is known that Origin has the common weakness (CWE-346) of “origin validation”.
+The Solid specification warns that the “trusted apps” feature is new and experimental, as it is known that Origin has the common weakness (CWE-346) of “origin validation”.
Currently when a user gives a Solid web app access to their Pod, the app Origin is added to that user’s list of trusted apps. The app then receives a token that allows it to interact with the Pod on behalf of the user, and only the Origin included with those interactions is verified using the list of trusted apps.
Although standard browsers automatically include the Origin when they send HTTPS requests, a non-browser client is not required to send one. This means anyone with access to the aforementioned Origin-based token can use non-browser clients to bypass Origin validation for the Pod.
Solutions already are planned to revise and replace this experimental use of Origin, in order to evolve security of the trusted app feature.
diff --git a/KNOWN-LINT-ISSUES.md b/KNOWN-LINT-ISSUES.md new file mode 100644 index 000000000..049a5ff33 --- /dev/null +++ b/KNOWN-LINT-ISSUES.md @@ -0,0 +1,142 @@ +# Known lint issues — baseline for solidproject.org + +This document records the lint rules that were **disabled, downgraded, +or had files excluded** when `htmlhint`, `stylelint`, and `pa11y-ci` +were first wired up (commit trio under +`feat/apps-page-redesign`). The goal of linting here is to catch +**new** regressions introduced by PR diffs, not to enforce a clean-up +march on the existing content. + +If you are the `solid-site-a11y-sweeper` (or any other cleanup agent), +this file is your to-do list. + +## htmlhint — `.htmlhintrc` + +Ran against `**/*.html` (excluding `_site/`, `node_modules/`, +`rdfa/`). 72 source files. + +### First-run violation counts + +| Rule | Count | Action | +| -------------------- | ----: | ------------------------------------------------- | +| `doctype-first` | 52 | **Disabled** globally. Reason below. | +| `tag-pair` | 3 | Enabled; offending files ignored. See below. | +| `spec-char-escape` | 3 | Enabled; offending files ignored. See below. | +| `id-unique` | 1 | Enabled; offending file ignored. See below. | +| `attr-lowercase` | 1 | Enabled; offending file ignored. See below. | + +### Rule: `doctype-first` — DISABLED + +Every Jekyll source page begins with a YAML front-matter block: + +``` +--- +permalink: /foo +layout: default +--- +