@base <https://solid-memo.com/decks/solid-fundamentals/v5.ttl> .

@prefix solid-memo: <https://solid-memo.com/ns/vocab/v1.ttl#> .
@prefix dcterms:    <http://purl.org/dc/terms/> .
@prefix prov:       <http://www.w3.org/ns/prov#> .
@prefix rdfs:       <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd:        <http://www.w3.org/2001/XMLSchema#> .
@prefix dcat:       <http://www.w3.org/ns/dcat#> .
@prefix foaf:       <http://xmlns.com/foaf/0.1/> .
@prefix topic:      <https://solid-memo.com/ns/vocab/topics.ttl#> .
@prefix adms:       <http://www.w3.org/ns/adms#> .
@prefix schema:     <https://schema.org/> .
@prefix vcard:      <http://www.w3.org/2006/vcard/ns#> .
@prefix owl:        <http://www.w3.org/2002/07/owl#> .

# A course as well as a deck: its chapters and steps are subjects of this
# document beside the cards, and every card is a multiple-choice question
# whose back is the correct option and whose distractors are the wrong ones.
<>
    a solid-memo:Deck ,
      dcat:Dataset ,
      schema:Course ;
    dcterms:title "Solid fundamentals"@en ,
                  "Grunderna i Solid"@sv ,
                  "Solid 기초"@ko ,
                  "Solid-Grundlagen"@de ,
                  "Fundamentos de Solid"@es ,
                  "Les bases de Solid"@fr ;
    dcterms:creator <#anton-wiklund> ;
    dcterms:license <https://creativecommons.org/publicdomain/zero/1.0/> ;
    dcterms:description "A course on Solid for people who want to build apps with it: why Solid exists, the linked data and RDF it is built on, vocabularies, pods and containers, reading and writing resources, identity and login, access control and sharing, notifications, designing an app's data, building, securing and publishing an app, a minimal app and Solid Memo itself read piece by piece, Solid's open problems, and the Linked Web Storage drafts that may succeed it. 17 chapters of short steps, each a piece of theory, with code and tables where they help, followed by multiple-choice questions; each chapter ends with a review, and every question you answer becomes a card in your deck. The facts come from the Solid specifications, the W3C standards around RDF, the servers' and libraries' documentation and code, and requests recorded on Community Solid Server 7.2, as of October 2026."@en ,
                        "En kurs om Solid för dig som vill bygga appar med det: varför Solid finns, länkade data och RDF som det bygger på, vokabulärer, poddar och behållare, att läsa och skriva resurser, identitet och inloggning, åtkomstkontroll och delning, notiser, hur en app lägger upp sina data, att bygga, säkra och publicera en app, en minimal app och Solid Memo självt lästa bit för bit, Solids öppna problem och Linked Web Storage, som kan efterträda det. 17 kapitel med korta steg av teori följda av flervalsfrågor; varje fråga du besvarar blir ett kort i din kortlek. Kursen finns bara på engelska."@sv ,
                        "Solid로 앱을 만들고 싶은 사람을 위한 Solid 코스입니다. Solid가 왜 있는지, 그 바탕인 링크드 데이터와 RDF, 어휘, Pod와 컨테이너, 리소스 읽기와 쓰기, 신원과 로그인, 접근 제어와 공유, 알림, 앱의 데이터 설계, 앱의 구축·보안·배포, 최소한의 앱과 Solid Memo 자체를 한 부분씩 읽어 보기, Solid의 미해결 문제, 그리고 Solid의 뒤를 이을 수도 있는 Linked Web Storage 초안을 다룹니다. 17개 챕터는 짧은 단계로 이루어지며, 각 단계는 필요한 곳에 코드와 표를 곁들인 이론 한 부분과 그 뒤의 객관식 문제로 되어 있습니다. 챕터마다 마지막에 복습이 있고, 답한 문제는 모두 덱의 카드가 됩니다. 내용은 Solid 명세, RDF 관련 W3C 표준, 서버와 라이브러리의 문서와 코드, Community Solid Server 7.2에 기록한 요청에서 가져왔으며 2026년 10월 기준입니다."@ko ,
                        "Ein Kurs über Solid für alle, die damit Apps bauen wollen: warum es Solid gibt, Linked Data und RDF, auf denen es aufbaut, Vokabulare, Pods und Container, Ressourcen lesen und schreiben, Identität und Anmeldung, Zugriffskontrolle und Teilen, Benachrichtigungen, die Daten einer App entwerfen, eine App bauen, absichern und veröffentlichen, eine minimale App und Solid Memo selbst Stück für Stück gelesen, die offenen Probleme von Solid und die Entwürfe von Linked Web Storage, das Solid ablösen könnte. 17 Kapitel aus kurzen Schritten, jeder ein Stück Theorie, mit Code und Tabellen, wo sie helfen, gefolgt von Multiple-Choice-Fragen; jedes Kapitel endet mit einer Wiederholung, und jede Frage, die du beantwortest, wird zu einer Karte in deinem Stapel. Die Fakten stammen aus den Solid-Spezifikationen, den W3C-Standards rund um RDF, der Dokumentation und dem Code der Server und Bibliotheken und aus Anfragen, die auf Community Solid Server 7.2 aufgezeichnet wurden, Stand Oktober 2026."@de ,
                        "Un curso sobre Solid para quien quiere crear aplicaciones con él: por qué existe Solid, los datos enlazados y RDF en los que se basa, los vocabularios, los Pods y los contenedores, leer y escribir recursos, la identidad y el inicio de sesión, el control de acceso y el uso compartido, las notificaciones, el diseño de los datos de una aplicación, cómo crear, proteger y publicar una aplicación, una aplicación mínima y el propio Solid Memo leídos pieza a pieza, los problemas abiertos de Solid y los borradores de Linked Web Storage, que podría sucederle. 17 capítulos de pasos breves, cada uno un fragmento de teoría, con código y tablas donde ayudan, seguido de preguntas de opción múltiple; cada capítulo termina con un repaso, y cada pregunta que respondes se convierte en una tarjeta de tu mazo. Los datos proceden de las especificaciones de Solid, los estándares del W3C en torno a RDF, la documentación y el código de los servidores y bibliotecas, y peticiones registradas en Community Solid Server 7.2, a fecha de octubre de 2026."@es ,
                        "Un cours sur Solid pour ceux qui veulent créer des applications avec : pourquoi Solid existe, les données liées et RDF sur lesquels il repose, les vocabulaires, les Pods et les conteneurs, la lecture et l’écriture de ressources, l’identité et la connexion, le contrôle d’accès et le partage, les notifications, la conception des données d’une application, la création, la sécurisation et la publication d’une application, une application minimale et Solid Memo lui-même lus pièce par pièce, les problèmes ouverts de Solid et les brouillons de Linked Web Storage, qui pourrait lui succéder. 17 chapitres de courtes étapes, chacune un morceau de théorie, avec du code et des tableaux là où ils aident, suivi de questions à choix multiple ; chaque chapitre se termine par une révision, et chaque question à laquelle vous répondez devient une carte de votre paquet. Les faits proviennent des spécifications Solid, des standards du W3C autour de RDF, de la documentation et du code des serveurs et des bibliothèques, et de requêtes enregistrées sur Community Solid Server 7.2, en octobre 2026."@fr ;
    prov:wasDerivedFrom <http://xmlns.com/foaf/spec/> ,
                        <https://5stardata.info/en/> ,
                        <https://archives.iw3c2.org/www2016/WWW2016-Proceedings/companion/p223.pdf> ,
                        <https://arxiv.org/abs/2302.06933> ,
                        <https://blog.ldodds.com/2024/03/12/baffled-by-solid/> ,
                        <https://cheatsheetseries.owasp.org/cheatsheets/Cross_Site_Scripting_Prevention_Cheat_Sheet.html> ,
                        <https://cheatsheetseries.owasp.org/cheatsheets/Server_Side_Request_Forgery_Prevention_Cheat_Sheet.html> ,
                        <https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/authorization-methods/> ,
                        <https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/client-credentials/> ,
                        <https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/example-requests/> ,
                        <https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/identity-provider/> ,
                        <https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/metadata/> ,
                        <https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/notifications/> ,
                        <https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/seeding-pods/> ,
                        <https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/starting-server/> ,
                        <https://comunica.dev/docs/query/advanced/solid/> ,
                        <https://comunica.dev/research/link_traversal/> ,
                        <https://dapsi.ngi.eu/success-story-pds-pod-migrator-migrating-your-solid-data/> ,
                        <https://dev.solidproject.org/> ,
                        <https://dev.solidproject.org/guides/authenticating_with_a_script/> ,
                        <https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS> ,
                        <https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS/Errors> ,
                        <https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS/Errors/CORSDidNotSucceed> ,
                        <https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP> ,
                        <https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Access-Control-Expose-Headers> ,
                        <https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy> ,
                        <https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy> ,
                        <https://docs.activitypods.org/architecture/application-interoperability/> ,
                        <https://docs.inrupt.com/ess/2.7/services/service-notification/service-websocket> ,
                        <https://docs.inrupt.com/ess/2.7/services/service-webid> ,
                        <https://docs.inrupt.com/ess/latest/> ,
                        <https://docs.inrupt.com/ess/releases.md> ,
                        <https://docs.inrupt.com/ess/services/service-access-grant> ,
                        <https://docs.inrupt.com/ess/services/service-access-grant/issue-endpoint> ,
                        <https://docs.inrupt.com/guides/access-control-policies> ,
                        <https://docs.inrupt.com/guides/authentication-in-solid/authentication-from-browser.md> ,
                        <https://docs.inrupt.com/guides/authentication-in-solid/authentication-from-browser/session-restore-upon-browser-refresh.md> ,
                        <https://docs.inrupt.com/guides/authentication-in-solid/authentication-server-side.md> ,
                        <https://docs.inrupt.com/guides/authentication-in-solid/authentication-single-user-application.md> ,
                        <https://docs.inrupt.com/guides/universal-api> ,
                        <https://docs.inrupt.com/guides/webid-document-best-practices/managing-webid-profiles> ,
                        <https://docs.inrupt.com/podspaces/podspaces.md> ,
                        <https://docs.inrupt.com/sdk/javascript-sdk/authentication.md> ,
                        <https://docs.inrupt.com/sdk/javascript-sdk/read-and-write-rdf-data.md> ,
                        <https://docs.inrupt.com/sdk/javascript-sdk/tutorial> ,
                        <https://docs.inrupt.com/security/authorization> ,
                        <https://docs.inrupt.com/security/authorization/access-requests-grants.md> ,
                        <https://docs.netlify.com/manage/routing/headers/> ,
                        <https://forum.solidproject.org/t/acl-format-for-authorising-new-apps/1655> ,
                        <https://forum.solidproject.org/t/how-to-authenticate-an-app-with-its-own-identity-e-g-webid/5946> ,
                        <https://forum.solidproject.org/t/solid-interop-in-practice/7701> ,
                        <https://forum.solidproject.org/t/upcoming-software-switch-for-solidcommunity-net/8608> ,
                        <https://forum.solidproject.org/t/why-deprecate-direct-webid-tls/2953> ,
                        <https://forum.solidproject.org/t/why-is-acl-trustedapp-visible-for-everyone-on-css/5603> ,
                        <https://gdpr-info.eu/art-20-gdpr/> ,
                        <https://github.com/CommunitySolidServer/CommunitySolidServer> ,
                        <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/main/RELEASE_NOTES.md> ,
                        <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/main/config/util/auxiliary/strategies/acl.json> ,
                        <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/config/http/middleware/handlers/cors.json> ,
                        <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/config/identity/handler/base/provider-factory.json> ,
                        <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/src/authorization/OwnerPermissionReader.ts> ,
                        <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/src/http/input/body/N3PatchBodyParser.ts> ,
                        <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/src/identity/interaction/oidc/ConsentHandler.ts> ,
                        <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/src/identity/interaction/webid/LinkWebIdHandler.ts> ,
                        <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/src/identity/ownership/TokenOwnershipValidator.ts> ,
                        <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/src/identity/storage/ClientIdAdapterFactory.ts> ,
                        <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/src/init/SeededAccountInitializer.ts> ,
                        <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/templates/identity/account/link-webid.html.ejs> ,
                        <https://github.com/CommunitySolidServer/CommunitySolidServer/tree/main/templates/pod> ,
                        <https://github.com/CommunitySolidServer/CommunitySolidServer/tree/v7.2.0> ,
                        <https://github.com/CommunitySolidServer/CommunitySolidServer/tree/v7.2.0/src/server/notifications/WebhookChannel2023> ,
                        <https://github.com/CommunitySolidServer/access-token-verifier> ,
                        <https://github.com/CommunitySolidServer/access-token-verifier/blob/v2.1.1/src/config/index.ts> ,
                        <https://github.com/NoelDeMartin/media-kraken> ,
                        <https://github.com/NoelDeMartin/umai> ,
                        <https://github.com/SolidOS/mashlib> ,
                        <https://github.com/SolidOS/solidos> ,
                        <https://github.com/digitalbazaar/jsonld.js> ,
                        <https://github.com/inrupt/solid-client-authn-js> ,
                        <https://github.com/inrupt/solid-client-authn-js/blob/main/ARCHITECTURE.md> ,
                        <https://github.com/inrupt/solid-client-authn-js/blob/main/packages/browser/src/Session.ts> ,
                        <https://github.com/inrupt/solid-client-js/blob/main/CHANGELOG.md> ,
                        <https://github.com/linkeddata/rdflib.js> ,
                        <https://github.com/nodeSolidServer/node-solid-server> ,
                        <https://github.com/nodeSolidServer/node-solid-server/releases> ,
                        <https://github.com/nodeSolidServer/node-solid-server/tree/v6.0.0> ,
                        <https://github.com/panva/node-oidc-provider/blob/v8.4.3/lib/helpers/defaults.js> ,
                        <https://github.com/pdsinterop/solid-nextcloud> ,
                        <https://github.com/rdf-ext/rdf-ext> ,
                        <https://github.com/rdfjs/N3.js> ,
                        <https://github.com/shapetrees/specification> ,
                        <https://github.com/solid-contrib/conformance-test-harness> ,
                        <https://github.com/solid-contrib/data-modules> ,
                        <https://github.com/solid-contrib/pivot> ,
                        <https://github.com/solid-contrib/pivot/tree/4bf3123ecab6f7e54f2471b8d014e8dffd7da7cb> ,
                        <https://github.com/solid-contrib/specification-tests> ,
                        <https://github.com/solid-memo/website> ,
                        <https://github.com/solid/node-solid-server/blob/v6.0.0/lib/requests/create-account-request.mjs> ,
                        <https://github.com/solid/solid-auth-client> ,
                        <https://github.com/solid/solid-spec/blob/master/api-rest.md> ,
                        <https://github.com/solid/solid-spec/blob/master/api-websockets.md> ,
                        <https://github.com/solid/solidproject.org/wiki/Create-your-own-vocabulary> ,
                        <https://github.com/solid/solidproject.org/wiki/Vocabularies-essential-to-solid> ,
                        <https://github.com/solid/vocab> ,
                        <https://github.com/solid/web-access-control-spec/issues/81> ,
                        <https://github.com/solid/webid-oidc-spec> ,
                        <https://imec-publications.be/entities/publication/60bf893e-54d1-4dd7-a596-6793b1e42ba5/full> ,
                        <https://inrupt.com/blog/solid-achieves-major-milestone-in-web-standardization-process> ,
                        <https://inrupt.com/blog/why-agentic-wallets> ,
                        <https://inrupt.com/case-study/flanders-strengthens-trusted-data-economy> ,
                        <https://inrupt.com/one-small-step-for-the-web> ,
                        <https://ldkit.io/> ,
                        <https://ldo.js.org/latest/> ,
                        <https://lists.w3.org/Archives/Public/public-solid/2024Oct/0007.html> ,
                        <https://lists.w3.org/Archives/Public/public-solid/2026Feb/0008.html> ,
                        <https://lov.linkeddata.es/dataset> ,
                        <https://lov.linkeddata.es/dataset/lov/vocabs/schema> ,
                        <https://noeldemartin.com/blog/interoperable-serendipity> ,
                        <https://noeldemartin.com/tasks/implementing-a-recipes-manager-using-solid> ,
                        <https://openid.net/specs/openid-connect-core-1_0.html> ,
                        <https://openid.net/specs/openid-connect-rpinitiated-1_0.html> ,
                        <https://penny.vincenttunru.com/> ,
                        <https://prefix.cc/> ,
                        <https://registry.npmjs.org/> ,
                        <https://registry.npmjs.org/solid-auth-client> ,
                        <https://ruben.verborgh.org/articles/redecentralizing-the-web/> ,
                        <https://ruben.verborgh.org/blog/2019/06/17/shaping-linked-data-apps/> ,
                        <https://ruben.verborgh.org/blog/2022/12/30/lets-talk-about-pods/> ,
                        <https://rubenverborgh.github.io/RDF-for-Solid-2022/> ,
                        <https://sagroups.ieee.org/p3330> ,
                        schema:children ,
                        <https://schema.org/docs/datamodel.html> ,
                        <https://schema.org/docs/faq.html> ,
                        <https://schema.org/docs/schemas.html> ,
                        schema:height ,
                        <https://semantic-web-journal.net/content/community-solid-server-supporting-research-development-evolving-ecosystem-0> ,
                        <https://shapetrees.github.io/specification/> ,
                        <https://shex.io/shex-semantics/> ,
                        <https://solid.github.io/authorization-panel/acp-specification/> ,
                        <https://solid.github.io/data-interoperability-panel/primer/application.html> ,
                        <https://solid.github.io/data-interoperability-panel/specification/> ,
                        <https://solid.github.io/notifications/streaming-http-channel-2023> ,
                        <https://solid.github.io/notifications/webhook-channel-2023> ,
                        <https://solid.github.io/notifications/websocket-channel-2023> ,
                        <https://solid.github.io/solid-oidc/> ,
                        <https://solid.github.io/solid-oidc/primer/> ,
                        <https://solid.github.io/type-indexes/> ,
                        <https://solid.github.io/webid-profile/> ,
                        <https://solidproject.org/ED/protocol> ,
                        <https://solidproject.org/TR/> ,
                        <https://solidproject.org/TR/2021/protocol-20211217> ,
                        <https://solidproject.org/TR/2022/protocol-20221231> ,
                        <https://solidproject.org/TR/acp> ,
                        <https://solidproject.org/TR/notifications-protocol> ,
                        <https://solidproject.org/TR/oidc> ,
                        <https://solidproject.org/TR/protocol> ,
                        <https://solidproject.org/TR/wac> ,
                        <https://solidproject.org/about> ,
                        <https://solidproject.org/apps> ,
                        <https://solidproject.org/users/get-a-pod> ,
                        <https://soukai.js.org/> ,
                        <https://soukai.js.org/guide/advanced/interoperability.html> ,
                        <https://strathprints.strath.ac.uk/92706> ,
                        <https://thenextweb.com/news/web-inventor-tim-berners-lee-screw-web3-my-decentralized-internet-doesnt-need-blockchain> ,
                        <https://theodi.org/news-and-events/news/odi-and-solid-come-together-to-give-individuals-greater-control-over-personal-data/> ,
                        <https://url.spec.whatwg.org/> ,
                        <https://w3c-cg.github.io/N3/spec/> ,
                        <https://webfoundation.org/2019/03/web-birthday-30/> ,
                        <https://www.dublincore.org/specifications/dublin-core/dcmi-terms/> ,
                        <https://www.ietf.org/archive/id/draft-ietf-oauth-client-id-metadata-document-02.html> ,
                        <https://www.inrupt.com/blog/inrupt-gives-support-as-the-open-data-institute-commits-to-the-solid-movement> ,
                        <https://www.inrupt.com/case-study/bbc-embraces-future-of-personal-data-access-and-consent> ,
                        <https://www.npmjs.com/package/@inrupt/solid-client-authn-browser/v/5.0.1> ,
                        <https://www.npmjs.com/package/@inrupt/solid-client-authn-core/v/5.0.1> ,
                        <https://www.rfc-editor.org/rfc/rfc3986> ,
                        <https://www.rfc-editor.org/rfc/rfc3987> ,
                        <https://www.rfc-editor.org/rfc/rfc5023> ,
                        <https://www.rfc-editor.org/rfc/rfc5789> ,
                        <https://www.rfc-editor.org/rfc/rfc6455> ,
                        <https://www.rfc-editor.org/rfc/rfc6749> ,
                        <https://www.rfc-editor.org/rfc/rfc7636> ,
                        <https://www.rfc-editor.org/rfc/rfc8288> ,
                        <https://www.rfc-editor.org/rfc/rfc9110> ,
                        <https://www.rfc-editor.org/rfc/rfc9112> ,
                        <https://www.rfc-editor.org/rfc/rfc9207> ,
                        <https://www.rfc-editor.org/rfc/rfc9449> ,
                        <https://www.rfc-editor.org/rfc/rfc9700> ,
                        <https://www.w3.org/2005/Incubator/webid/spec/identity/> ,
                        <https://www.w3.org/2005/Incubator/webid/spec/tls/> ,
                        <https://www.w3.org/2024/09/linked-web-storage-wg-charter> ,
                        <https://www.w3.org/2026/09/14-lws-minutes.html> ,
                        <https://www.w3.org/2026/09/21-lws-minutes.html> ,
                        <https://www.w3.org/DesignIssues/CloudStorage.html> ,
                        <https://www.w3.org/DesignIssues/LinkedData.html> ,
                        <https://www.w3.org/DesignIssues/ReadWriteLinkedData.html> ,
                        <https://www.w3.org/TR/2026/WD-lws10-authn-ssi-cid-20260423/> ,
                        <https://www.w3.org/TR/activitystreams-vocabulary/> ,
                        <https://www.w3.org/TR/cooluris/> ,
                        <https://www.w3.org/TR/dwbp/> ,
                        <https://www.w3.org/TR/json-ld11-api/> ,
                        <https://www.w3.org/TR/json-ld11-framing/> ,
                        <https://www.w3.org/TR/json-ld11/> ,
                        <https://www.w3.org/TR/ldn/> ,
                        <https://www.w3.org/TR/ldp/> ,
                        <https://www.w3.org/TR/lws10-authn-openid/> ,
                        <https://www.w3.org/TR/lws10-core/> ,
                        <https://www.w3.org/TR/n-quads/> ,
                        <https://www.w3.org/TR/n-triples/> ,
                        <https://www.w3.org/TR/owl2-primer/> ,
                        <https://www.w3.org/TR/owl2-syntax/> ,
                        <https://www.w3.org/TR/prov-o/> ,
                        <https://www.w3.org/TR/rdf-schema/> ,
                        <https://www.w3.org/TR/rdf-syntax-grammar/> ,
                        <https://www.w3.org/TR/rdf11-concepts/> ,
                        <https://www.w3.org/TR/rdf11-mt/> ,
                        <https://www.w3.org/TR/rdf11-primer/> ,
                        <https://www.w3.org/TR/rdf12-concepts/> ,
                        <https://www.w3.org/TR/rdf12-primer/> ,
                        <https://www.w3.org/TR/rdf12-schema/> ,
                        <https://www.w3.org/TR/rdf12-semantics/> ,
                        <https://www.w3.org/TR/rdf12-turtle/> ,
                        <https://www.w3.org/TR/rdfa-primer/> ,
                        <https://www.w3.org/TR/shacl/> ,
                        <https://www.w3.org/TR/shacl12-core/> ,
                        <https://www.w3.org/TR/skos-reference/> ,
                        <https://www.w3.org/TR/sparql11-query/> ,
                        <https://www.w3.org/TR/sparql11-update/> ,
                        <https://www.w3.org/TR/sparql12-query/> ,
                        <https://www.w3.org/TR/swbp-vocab-pub/> ,
                        <https://www.w3.org/TR/trig/> ,
                        <https://www.w3.org/TR/turtle/> ,
                        <https://www.w3.org/TR/vcard-rdf/> ,
                        <https://www.w3.org/TR/vocab-dcat-3/> ,
                        <https://www.w3.org/TR/webarch/> ,
                        <https://www.w3.org/TeamSubmission/n3/> ,
                        <https://www.w3.org/community/solid/> ,
                        <https://www.w3.org/groups/wg/lws/charters/active/> ,
                        <https://www.w3.org/groups/wg/rdf-star/publications/> ,
                        <https://www.w3.org/news/2026/first-public-working-draft-linked-web-storage-protocol-1-0/> ,
                        <https://www.w3.org/news/2026/first-public-working-drafts-for-the-linked-web-storage-lws-1-0-authentication-suite/> ,
                        <https://www.w3.org/ns/auth/acl> ,
                        <https://www.w3.org/ns/pim/space> ,
                        <https://www.w3.org/ns/solid/oidc-context.jsonld> ,
                        <https://www.w3.org/ns/solid/terms> ,
                        <https://www.w3.org/standards/history/lws10-authn-openid/> ,
                        <https://www.w3.org/standards/history/lws10-core/> ,
                        <https://www.w3.org/standards/history/rdf12-concepts/> ,
                        <https://zenodo.org/records/7641620> ;
    prov:wasGeneratedBy <#compilation> ;
    dcterms:created "2026-10-07T00:00:00.000Z"^^xsd:dateTime ;
    dcat:theme <http://publications.europa.eu/resource/authority/data-theme/EDUC> ,
               topic:computing ,
               topic:linked-data ;
    dcat:keyword "Solid"@en ,
                 "linked data"@en ,
                 "RDF"@en ,
                 "Turtle"@en ,
                 "IRI"@en ,
                 "semantic web"@en ,
                 "Solid Protocol"@en ,
                 "pod"@en ,
                 "WebID"@en ,
                 "Solid-OIDC"@en ,
                 "Web Access Control"@en ,
                 "ACP"@en ,
                 "JSON-LD"@en ,
                 "Linked Web Storage"@en ,
                 "Solid"@sv ,
                 "länkade data"@sv ,
                 "RDF"@sv ,
                 "Turtle"@sv ,
                 "IRI"@sv ,
                 "semantiska webben"@sv ,
                 "Solid-protokollet"@sv ,
                 "pod"@sv ,
                 "WebID"@sv ,
                 "Solid-OIDC"@sv ,
                 "Web Access Control"@sv ,
                 "ACP"@sv ,
                 "JSON-LD"@sv ,
                 "Linked Web Storage"@sv ,
                 "Solid"@ko ,
                 "링크드 데이터"@ko ,
                 "RDF"@ko ,
                 "Turtle"@ko ,
                 "IRI"@ko ,
                 "시맨틱 웹"@ko ,
                 "Solid 프로토콜"@ko ,
                 "Pod"@ko ,
                 "WebID"@ko ,
                 "Solid-OIDC"@ko ,
                 "Web Access Control"@ko ,
                 "ACP"@ko ,
                 "JSON-LD"@ko ,
                 "Linked Web Storage"@ko ,
                 "Solid"@de ,
                 "Linked Data"@de ,
                 "RDF"@de ,
                 "Turtle"@de ,
                 "IRI"@de ,
                 "Semantic Web"@de ,
                 "Solid-Protokoll"@de ,
                 "Pod"@de ,
                 "WebID"@de ,
                 "Solid-OIDC"@de ,
                 "Web Access Control"@de ,
                 "ACP"@de ,
                 "JSON-LD"@de ,
                 "Linked Web Storage"@de ,
                 "Solid"@es ,
                 "datos enlazados"@es ,
                 "RDF"@es ,
                 "Turtle"@es ,
                 "IRI"@es ,
                 "web semántica"@es ,
                 "protocolo Solid"@es ,
                 "Pod"@es ,
                 "WebID"@es ,
                 "Solid-OIDC"@es ,
                 "Web Access Control"@es ,
                 "ACP"@es ,
                 "JSON-LD"@es ,
                 "Linked Web Storage"@es ,
                 "Solid"@fr ,
                 "données liées"@fr ,
                 "RDF"@fr ,
                 "Turtle"@fr ,
                 "IRI"@fr ,
                 "web sémantique"@fr ,
                 "protocole Solid"@fr ,
                 "Pod"@fr ,
                 "WebID"@fr ,
                 "Solid-OIDC"@fr ,
                 "Web Access Control"@fr ,
                 "ACP"@fr ,
                 "JSON-LD"@fr ,
                 "Linked Web Storage"@fr ;
    dcterms:language <http://publications.europa.eu/resource/authority/language/ENG> ;
    solid-memo:studyDirection solid-memo:frontToBack ;
    solid-memo:formatVersion 6 ;
    dcat:version "5" ;
    dcat:prev <https://solid-memo.com/decks/solid-fundamentals/v4.ttl> ;
    dcat:previousVersion <https://solid-memo.com/decks/solid-fundamentals/v4.ttl> ;
    dcterms:issued "2026-10-22T00:00:00Z"^^xsd:dateTime ;
    adms:versionNotes "10 more questions are asked so that each has one answer when studied flip-and-grade, without its options; wrong options that no longer fit are retired and replaced, and every chapter, step and card keeps its id." ;
    dcterms:publisher <https://solid-memo.com/decks/index.ttl#solid-memo> ;
    dcat:inSeries <https://solid-memo.com/decks/index.ttl#solid-fundamentals> ;
    dcat:isVersionOf <https://solid-memo.com/decks/index.ttl#solid-fundamentals> ;
    dcat:contactPoint <#contact> ;
    dcat:distribution <#turtle> .

<#anton-wiklund>
    a foaf:Agent ;
    foaf:name "Anton Wiklund" .

<#contact>
    a vcard:Kind ;
    vcard:hasURL <https://github.com/solid-memo/website/issues> .

<https://creativecommons.org/publicdomain/zero/1.0/>
    a dcterms:LicenseDocument .

# How this course was made (W3C PROV-O): written from the sources below,
# with examples recorded on real servers, then checked in the review rounds
# below.
<#compilation>
    a prov:Activity ;
    prov:endedAtTime "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    prov:used <http://xmlns.com/foaf/spec/> ,
              <https://5stardata.info/en/> ,
              <https://archives.iw3c2.org/www2016/WWW2016-Proceedings/companion/p223.pdf> ,
              <https://arxiv.org/abs/2302.06933> ,
              <https://blog.ldodds.com/2024/03/12/baffled-by-solid/> ,
              <https://cheatsheetseries.owasp.org/cheatsheets/Cross_Site_Scripting_Prevention_Cheat_Sheet.html> ,
              <https://cheatsheetseries.owasp.org/cheatsheets/Server_Side_Request_Forgery_Prevention_Cheat_Sheet.html> ,
              <https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/authorization-methods/> ,
              <https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/client-credentials/> ,
              <https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/example-requests/> ,
              <https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/identity-provider/> ,
              <https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/metadata/> ,
              <https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/notifications/> ,
              <https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/seeding-pods/> ,
              <https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/starting-server/> ,
              <https://comunica.dev/docs/query/advanced/solid/> ,
              <https://comunica.dev/research/link_traversal/> ,
              <https://dapsi.ngi.eu/success-story-pds-pod-migrator-migrating-your-solid-data/> ,
              <https://dev.solidproject.org/> ,
              <https://dev.solidproject.org/guides/authenticating_with_a_script/> ,
              <https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS> ,
              <https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS/Errors> ,
              <https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS/Errors/CORSDidNotSucceed> ,
              <https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP> ,
              <https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Access-Control-Expose-Headers> ,
              <https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy> ,
              <https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy> ,
              <https://docs.activitypods.org/architecture/application-interoperability/> ,
              <https://docs.inrupt.com/ess/2.7/services/service-notification/service-websocket> ,
              <https://docs.inrupt.com/ess/2.7/services/service-webid> ,
              <https://docs.inrupt.com/ess/latest/> ,
              <https://docs.inrupt.com/ess/releases.md> ,
              <https://docs.inrupt.com/ess/services/service-access-grant> ,
              <https://docs.inrupt.com/ess/services/service-access-grant/issue-endpoint> ,
              <https://docs.inrupt.com/guides/access-control-policies> ,
              <https://docs.inrupt.com/guides/authentication-in-solid/authentication-from-browser.md> ,
              <https://docs.inrupt.com/guides/authentication-in-solid/authentication-from-browser/session-restore-upon-browser-refresh.md> ,
              <https://docs.inrupt.com/guides/authentication-in-solid/authentication-server-side.md> ,
              <https://docs.inrupt.com/guides/authentication-in-solid/authentication-single-user-application.md> ,
              <https://docs.inrupt.com/guides/universal-api> ,
              <https://docs.inrupt.com/guides/webid-document-best-practices/managing-webid-profiles> ,
              <https://docs.inrupt.com/podspaces/podspaces.md> ,
              <https://docs.inrupt.com/sdk/javascript-sdk/authentication.md> ,
              <https://docs.inrupt.com/sdk/javascript-sdk/read-and-write-rdf-data.md> ,
              <https://docs.inrupt.com/sdk/javascript-sdk/tutorial> ,
              <https://docs.inrupt.com/security/authorization> ,
              <https://docs.inrupt.com/security/authorization/access-requests-grants.md> ,
              <https://docs.netlify.com/manage/routing/headers/> ,
              <https://forum.solidproject.org/t/acl-format-for-authorising-new-apps/1655> ,
              <https://forum.solidproject.org/t/how-to-authenticate-an-app-with-its-own-identity-e-g-webid/5946> ,
              <https://forum.solidproject.org/t/solid-interop-in-practice/7701> ,
              <https://forum.solidproject.org/t/upcoming-software-switch-for-solidcommunity-net/8608> ,
              <https://forum.solidproject.org/t/why-deprecate-direct-webid-tls/2953> ,
              <https://forum.solidproject.org/t/why-is-acl-trustedapp-visible-for-everyone-on-css/5603> ,
              <https://gdpr-info.eu/art-20-gdpr/> ,
              <https://github.com/CommunitySolidServer/CommunitySolidServer> ,
              <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/main/RELEASE_NOTES.md> ,
              <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/main/config/util/auxiliary/strategies/acl.json> ,
              <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/config/http/middleware/handlers/cors.json> ,
              <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/config/identity/handler/base/provider-factory.json> ,
              <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/src/authorization/OwnerPermissionReader.ts> ,
              <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/src/http/input/body/N3PatchBodyParser.ts> ,
              <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/src/identity/interaction/oidc/ConsentHandler.ts> ,
              <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/src/identity/interaction/webid/LinkWebIdHandler.ts> ,
              <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/src/identity/ownership/TokenOwnershipValidator.ts> ,
              <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/src/identity/storage/ClientIdAdapterFactory.ts> ,
              <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/src/init/SeededAccountInitializer.ts> ,
              <https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/templates/identity/account/link-webid.html.ejs> ,
              <https://github.com/CommunitySolidServer/CommunitySolidServer/tree/main/templates/pod> ,
              <https://github.com/CommunitySolidServer/CommunitySolidServer/tree/v7.2.0> ,
              <https://github.com/CommunitySolidServer/CommunitySolidServer/tree/v7.2.0/src/server/notifications/WebhookChannel2023> ,
              <https://github.com/CommunitySolidServer/access-token-verifier> ,
              <https://github.com/CommunitySolidServer/access-token-verifier/blob/v2.1.1/src/config/index.ts> ,
              <https://github.com/NoelDeMartin/media-kraken> ,
              <https://github.com/NoelDeMartin/umai> ,
              <https://github.com/SolidOS/mashlib> ,
              <https://github.com/SolidOS/solidos> ,
              <https://github.com/digitalbazaar/jsonld.js> ,
              <https://github.com/inrupt/solid-client-authn-js> ,
              <https://github.com/inrupt/solid-client-authn-js/blob/main/ARCHITECTURE.md> ,
              <https://github.com/inrupt/solid-client-authn-js/blob/main/packages/browser/src/Session.ts> ,
              <https://github.com/inrupt/solid-client-js/blob/main/CHANGELOG.md> ,
              <https://github.com/linkeddata/rdflib.js> ,
              <https://github.com/nodeSolidServer/node-solid-server> ,
              <https://github.com/nodeSolidServer/node-solid-server/releases> ,
              <https://github.com/nodeSolidServer/node-solid-server/tree/v6.0.0> ,
              <https://github.com/panva/node-oidc-provider/blob/v8.4.3/lib/helpers/defaults.js> ,
              <https://github.com/pdsinterop/solid-nextcloud> ,
              <https://github.com/rdf-ext/rdf-ext> ,
              <https://github.com/rdfjs/N3.js> ,
              <https://github.com/shapetrees/specification> ,
              <https://github.com/solid-contrib/conformance-test-harness> ,
              <https://github.com/solid-contrib/data-modules> ,
              <https://github.com/solid-contrib/pivot> ,
              <https://github.com/solid-contrib/pivot/tree/4bf3123ecab6f7e54f2471b8d014e8dffd7da7cb> ,
              <https://github.com/solid-contrib/specification-tests> ,
              <https://github.com/solid-memo/website> ,
              <https://github.com/solid/node-solid-server/blob/v6.0.0/lib/requests/create-account-request.mjs> ,
              <https://github.com/solid/solid-auth-client> ,
              <https://github.com/solid/solid-spec/blob/master/api-rest.md> ,
              <https://github.com/solid/solid-spec/blob/master/api-websockets.md> ,
              <https://github.com/solid/solidproject.org/wiki/Create-your-own-vocabulary> ,
              <https://github.com/solid/solidproject.org/wiki/Vocabularies-essential-to-solid> ,
              <https://github.com/solid/vocab> ,
              <https://github.com/solid/web-access-control-spec/issues/81> ,
              <https://github.com/solid/webid-oidc-spec> ,
              <https://imec-publications.be/entities/publication/60bf893e-54d1-4dd7-a596-6793b1e42ba5/full> ,
              <https://inrupt.com/blog/solid-achieves-major-milestone-in-web-standardization-process> ,
              <https://inrupt.com/blog/why-agentic-wallets> ,
              <https://inrupt.com/case-study/flanders-strengthens-trusted-data-economy> ,
              <https://inrupt.com/one-small-step-for-the-web> ,
              <https://ldkit.io/> ,
              <https://ldo.js.org/latest/> ,
              <https://lists.w3.org/Archives/Public/public-solid/2024Oct/0007.html> ,
              <https://lists.w3.org/Archives/Public/public-solid/2026Feb/0008.html> ,
              <https://lov.linkeddata.es/dataset> ,
              <https://lov.linkeddata.es/dataset/lov/vocabs/schema> ,
              <https://noeldemartin.com/blog/interoperable-serendipity> ,
              <https://noeldemartin.com/tasks/implementing-a-recipes-manager-using-solid> ,
              <https://openid.net/specs/openid-connect-core-1_0.html> ,
              <https://openid.net/specs/openid-connect-rpinitiated-1_0.html> ,
              <https://penny.vincenttunru.com/> ,
              <https://prefix.cc/> ,
              <https://registry.npmjs.org/> ,
              <https://registry.npmjs.org/solid-auth-client> ,
              <https://ruben.verborgh.org/articles/redecentralizing-the-web/> ,
              <https://ruben.verborgh.org/blog/2019/06/17/shaping-linked-data-apps/> ,
              <https://ruben.verborgh.org/blog/2022/12/30/lets-talk-about-pods/> ,
              <https://rubenverborgh.github.io/RDF-for-Solid-2022/> ,
              <https://sagroups.ieee.org/p3330> ,
              schema:children ,
              <https://schema.org/docs/datamodel.html> ,
              <https://schema.org/docs/faq.html> ,
              <https://schema.org/docs/schemas.html> ,
              schema:height ,
              <https://semantic-web-journal.net/content/community-solid-server-supporting-research-development-evolving-ecosystem-0> ,
              <https://shapetrees.github.io/specification/> ,
              <https://shex.io/shex-semantics/> ,
              <https://solid.github.io/authorization-panel/acp-specification/> ,
              <https://solid.github.io/data-interoperability-panel/primer/application.html> ,
              <https://solid.github.io/data-interoperability-panel/specification/> ,
              <https://solid.github.io/notifications/streaming-http-channel-2023> ,
              <https://solid.github.io/notifications/webhook-channel-2023> ,
              <https://solid.github.io/notifications/websocket-channel-2023> ,
              <https://solid.github.io/solid-oidc/> ,
              <https://solid.github.io/solid-oidc/primer/> ,
              <https://solid.github.io/type-indexes/> ,
              <https://solid.github.io/webid-profile/> ,
              <https://solidproject.org/ED/protocol> ,
              <https://solidproject.org/TR/> ,
              <https://solidproject.org/TR/2021/protocol-20211217> ,
              <https://solidproject.org/TR/2022/protocol-20221231> ,
              <https://solidproject.org/TR/acp> ,
              <https://solidproject.org/TR/notifications-protocol> ,
              <https://solidproject.org/TR/oidc> ,
              <https://solidproject.org/TR/protocol> ,
              <https://solidproject.org/TR/wac> ,
              <https://solidproject.org/about> ,
              <https://solidproject.org/apps> ,
              <https://solidproject.org/users/get-a-pod> ,
              <https://soukai.js.org/> ,
              <https://soukai.js.org/guide/advanced/interoperability.html> ,
              <https://strathprints.strath.ac.uk/92706> ,
              <https://thenextweb.com/news/web-inventor-tim-berners-lee-screw-web3-my-decentralized-internet-doesnt-need-blockchain> ,
              <https://theodi.org/news-and-events/news/odi-and-solid-come-together-to-give-individuals-greater-control-over-personal-data/> ,
              <https://url.spec.whatwg.org/> ,
              <https://w3c-cg.github.io/N3/spec/> ,
              <https://webfoundation.org/2019/03/web-birthday-30/> ,
              <https://www.dublincore.org/specifications/dublin-core/dcmi-terms/> ,
              <https://www.ietf.org/archive/id/draft-ietf-oauth-client-id-metadata-document-02.html> ,
              <https://www.inrupt.com/blog/inrupt-gives-support-as-the-open-data-institute-commits-to-the-solid-movement> ,
              <https://www.inrupt.com/case-study/bbc-embraces-future-of-personal-data-access-and-consent> ,
              <https://www.npmjs.com/package/@inrupt/solid-client-authn-browser/v/5.0.1> ,
              <https://www.npmjs.com/package/@inrupt/solid-client-authn-core/v/5.0.1> ,
              <https://www.rfc-editor.org/rfc/rfc3986> ,
              <https://www.rfc-editor.org/rfc/rfc3987> ,
              <https://www.rfc-editor.org/rfc/rfc5023> ,
              <https://www.rfc-editor.org/rfc/rfc5789> ,
              <https://www.rfc-editor.org/rfc/rfc6455> ,
              <https://www.rfc-editor.org/rfc/rfc6749> ,
              <https://www.rfc-editor.org/rfc/rfc7636> ,
              <https://www.rfc-editor.org/rfc/rfc8288> ,
              <https://www.rfc-editor.org/rfc/rfc9110> ,
              <https://www.rfc-editor.org/rfc/rfc9112> ,
              <https://www.rfc-editor.org/rfc/rfc9207> ,
              <https://www.rfc-editor.org/rfc/rfc9449> ,
              <https://www.rfc-editor.org/rfc/rfc9700> ,
              <https://www.w3.org/2005/Incubator/webid/spec/identity/> ,
              <https://www.w3.org/2005/Incubator/webid/spec/tls/> ,
              <https://www.w3.org/2024/09/linked-web-storage-wg-charter> ,
              <https://www.w3.org/2026/09/14-lws-minutes.html> ,
              <https://www.w3.org/2026/09/21-lws-minutes.html> ,
              <https://www.w3.org/DesignIssues/CloudStorage.html> ,
              <https://www.w3.org/DesignIssues/LinkedData.html> ,
              <https://www.w3.org/DesignIssues/ReadWriteLinkedData.html> ,
              <https://www.w3.org/TR/2026/WD-lws10-authn-ssi-cid-20260423/> ,
              <https://www.w3.org/TR/activitystreams-vocabulary/> ,
              <https://www.w3.org/TR/cooluris/> ,
              <https://www.w3.org/TR/dwbp/> ,
              <https://www.w3.org/TR/json-ld11-api/> ,
              <https://www.w3.org/TR/json-ld11-framing/> ,
              <https://www.w3.org/TR/json-ld11/> ,
              <https://www.w3.org/TR/ldn/> ,
              <https://www.w3.org/TR/ldp/> ,
              <https://www.w3.org/TR/lws10-authn-openid/> ,
              <https://www.w3.org/TR/lws10-core/> ,
              <https://www.w3.org/TR/n-quads/> ,
              <https://www.w3.org/TR/n-triples/> ,
              <https://www.w3.org/TR/owl2-primer/> ,
              <https://www.w3.org/TR/owl2-syntax/> ,
              <https://www.w3.org/TR/prov-o/> ,
              <https://www.w3.org/TR/rdf-schema/> ,
              <https://www.w3.org/TR/rdf-syntax-grammar/> ,
              <https://www.w3.org/TR/rdf11-concepts/> ,
              <https://www.w3.org/TR/rdf11-mt/> ,
              <https://www.w3.org/TR/rdf11-primer/> ,
              <https://www.w3.org/TR/rdf12-concepts/> ,
              <https://www.w3.org/TR/rdf12-primer/> ,
              <https://www.w3.org/TR/rdf12-schema/> ,
              <https://www.w3.org/TR/rdf12-semantics/> ,
              <https://www.w3.org/TR/rdf12-turtle/> ,
              <https://www.w3.org/TR/rdfa-primer/> ,
              <https://www.w3.org/TR/shacl/> ,
              <https://www.w3.org/TR/shacl12-core/> ,
              <https://www.w3.org/TR/skos-reference/> ,
              <https://www.w3.org/TR/sparql11-query/> ,
              <https://www.w3.org/TR/sparql11-update/> ,
              <https://www.w3.org/TR/sparql12-query/> ,
              <https://www.w3.org/TR/swbp-vocab-pub/> ,
              <https://www.w3.org/TR/trig/> ,
              <https://www.w3.org/TR/turtle/> ,
              <https://www.w3.org/TR/vcard-rdf/> ,
              <https://www.w3.org/TR/vocab-dcat-3/> ,
              <https://www.w3.org/TR/webarch/> ,
              <https://www.w3.org/TeamSubmission/n3/> ,
              <https://www.w3.org/community/solid/> ,
              <https://www.w3.org/groups/wg/lws/charters/active/> ,
              <https://www.w3.org/groups/wg/rdf-star/publications/> ,
              <https://www.w3.org/news/2026/first-public-working-draft-linked-web-storage-protocol-1-0/> ,
              <https://www.w3.org/news/2026/first-public-working-drafts-for-the-linked-web-storage-lws-1-0-authentication-suite/> ,
              <https://www.w3.org/ns/auth/acl> ,
              <https://www.w3.org/ns/pim/space> ,
              <https://www.w3.org/ns/solid/oidc-context.jsonld> ,
              <https://www.w3.org/ns/solid/terms> ,
              <https://www.w3.org/standards/history/lws10-authn-openid/> ,
              <https://www.w3.org/standards/history/lws10-core/> ,
              <https://www.w3.org/standards/history/rdf12-concepts/> ,
              <https://zenodo.org/records/7641620> ;
    prov:wasAssociatedWith <#anton-wiklund> ;
    prov:wasInformedBy <#recorded-runs> ,
                       <#review-0> ,
                       <#review-1> ,
                       <#review-2> ,
                       <#review-3> ,
                       <#review-4> ,
                       <#review-5> ,
                       <#review-6> ,
                       <#review-7> ,
                       <#review-8> ;
    rdfs:comment "Compiled by Anton Wiklund with the help of AI."@en ,
                 "Sammanställd av Anton Wiklund med hjälp av AI."@sv ,
                 "About this record: the course was written by AI agents from a source dossier of 342 entries compiled for it, in three rounds of research and writing, then rewritten for this release; the working notes, the dossier, the chapters as written and the scripts that recorded the examples are kept with the course's sources, not in the library. This record condenses them: the sources below are those the steps cite, and the activities say how the course was checked."@en ,
                 "The course was checked by machine (the app's SHACL and DCAT-AP validators, its course and Markdown checks) and by AI agents against the cited sources and the recorded runs; it has had no human review."@en ,
                 "Sources: every step was written from the sources its draft cites, 248 documents in all: the Solid specifications (the Solid Protocol, WAC, ACP, Solid-OIDC, the WebID profile, notifications, type indexes and others), the W3C standards around RDF, IETF RFCs, the servers' and libraries' documentation and code, governance records, papers and articles. Each source's comment below quotes the evidence for its licence, says what the course took from it, if anything, and gives how much weight the dossier says it can carry and what it was used for; most were read on 2026-10-07, and their licences on 2026-10-08. The facts that change with new versions were checked again, all of them, in the third round, and the course says \"as of October 2026\" where a fact may date."@en ,
                 "Structure: 17 chapters of 193 steps in all. Each step is a short theory text, with code, requests and tables where they help, and one or more multiple-choice questions on it; each chapter has review questions (101 in all) that combine its steps and are asked only in its final review. Every question has one correct option (the card's back) and three wrong options (its distractors) of similar length and form, each with a note on why it is wrong. Questions that show code have the code in the question; an option that is code has wrong options that are code too."@en ,
                 "Selection: the course as planned: why Solid exists, linked data, RDF and its syntaxes, semantics and vocabularies, pods and containers, reading and writing resources, identity and authentication, Web Access Control, sharing with ACP and app permissions, notifications, data-oriented design and interoperability, building Solid apps, security and backends, a minimal app read piece by piece, Solid Memo as a worked example, Solid's difficulties and open problems, and Linked Web Storage. Its drafts' hands-on parts (a lab pod, exercises run in a terminal, and a capstone project with a starter and a checker) are left out, since a course in the library has to stand on its own: what they showed is given as examples recorded on a server, and the capstone was dropped."@en ,
                 "Licensing: the course is CC0 1.0, like most of the library. The dedication covers what is the compiler's own: the theory, questions, options and notes, which state the facts of the sources in the course's own words, the examples written for the course, and the excerpts of Solid Memo's code in Chapter 15, whose copyright is the compiler's. Each source's comment below quotes the evidence for its licence and says what the course took from it; most were used to verify facts only. What the course took is of three kinds. First, code and examples from sources whose licences let them be republished: the Solid terms vocabulary and the early Solid specification repository, both CC0; the Solid Protocol editor's draft, whose code snippets are CC0; and Solid Community Group reports, whose contributors grant everyone a licence to reproduce, adapt, distribute and sublicense them under the W3C Community Contributor License Agreement. Second, a few lines of what Community Solid Server 7.2.0 and node-solid-server 6.0.0 wrote and answered in the recorded runs (Steps 6.2, 8.6, 12.3 and 14.13, among others), both servers MIT-licensed and the lines not a substantial portion of either. Third, short passages, each with its source named in the text, quoted for teaching as the right of quotation allows (Berne Convention article 10(1); 22 § of the Swedish Copyright Act), among them three examples abridged from the Linked Web Storage drafts; these stay their authors' and are not part of the dedication."@en .

<#recorded-runs>
    a prov:Activity ;
    prov:endedAtTime "2026-10-08T00:00:00Z"^^xsd:dateTime ;
    prov:used <https://github.com/CommunitySolidServer/CommunitySolidServer/releases/tag/v7.2.0> ,
              <https://github.com/nodeSolidServer/node-solid-server/releases/tag/v6.0.0> ;
    prov:wasAssociatedWith <#anton-wiklund> ;
    rdfs:label "Recorded runs on Community Solid Server 7.2"@en ;
    rdfs:comment "Scope: the requests, responses and server behaviour the course shows as recorded (\"On CSS 7.2 …\"), run by scripts on 2026-10-07 and 2026-10-08 against a local Community Solid Server 7.2.0, mostly, and node-solid-server 6.0.0 for comparison, with the libraries the steps name (such as @inrupt/solid-client 4.0.0). Some examples leave out headers that do not matter to the step, or write the local server's address as https://pod.example/. The scripts and their full transcripts are kept with the course's sources, not in the library."@en ,
                 "Runs: Primary observations made 2026-10-07; http WebIDs and a local CSS; WAC-Allow on GET; N3 Patch with blank nodes; NSS 6, ETag and If-Match; Notifications JSON-LD context URLs; A minimal app end to end on CSS 7.2; Chapter 14's notes app on CSS 7.2; The notes app on NSS 6 and on CSS 7.2 with ACP; The Try-it list for Chapters 5-10 and 13; Solid Notes, round 3: npm test on CSS 7.2 with WAC and ACP; Solid Notes, round 3: browser run (Playwright 1.63.0); Chapter 14 social Your-turn solutions on CSS 7.2; A linked external WebID on two CSS 7.2 servers; CSS 7.2 with a pod quota; Chapter 12 Try-its (Steps 12.3 and 12.4) on CSS 7.2; Snippet tests: the chapters' code run verbatim; Umai and Media Kraken against a CSS 7.2 pod (Step 12.14); Offline Try-its of Steps 3.7, 3.8 and 4.10; Every Try-it box of Chapters 5-10, 13 and 16 on CSS 7.2; Social Try-its on CSS 7.2 (Steps 9.7-9.10); First-hand HTTP check of https://shapetrees.org/TR/specification/; Chapter 5 Try-it transcript on CSS 7.2; Chapter 6 Try-it on CSS 7.2; File naming and formats on NSS 6; Chapter 7 login and profile tests on CSS 7.2; Owner lock-out and acl:agentGroup on CSS 7.2; Chapter 10 Try-it transcript on CSS 7.2; Local check of the safeFetch sketch; Owner rescue on two CSS 7.2 configs; ACP sharing by insert-only N3 Patch on CSS 7.2."@en ,
                 "Outcome: the transcripts are the evidence for every example the course gives as recorded, and the release review (review 4) compared the examples with them. Other servers, or other versions, may behave otherwise, and the course marks such behaviour with ⚠."@en .

<#review-0>
    a prov:Activity ;
    prov:endedAtTime "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    rdfs:label "Machine checks"@en ;
    rdfs:comment "Scope: the whole release, with the library checker (npm run library:check), which validates it against Solid Memo's shapes (library deck format 5, card format 5, chapter, step and distractor format 1), DCAT-AP and SKOS, with the reference data, checks the course's outline by its rules and its Markdown by the rules for a release."@en ,
                 "Outcome: The release conforms to every shape, profile and rule the checker applies to it."@en .

<#review-1>
    a prov:Activity ;
    prov:endedAtTime "2026-10-07T00:00:00Z"^^xsd:dateTime ;
    rdfs:label "Completeness (AI)"@en ;
    rdfs:comment "Scope: the drafted chapters, their research notes and the dossier, reviewed by an AI agent for whether a beginner who completes the course could build a Solid app, and for contradictions, broken references and unsupported claims; not a human review."@en ,
                 "Outcome: every citation resolved in the dossier. Missing topics (sharing as a workflow, the session lifecycle, security, working code), contradictions and broken cross-references were found; the second round of writing addressed them."@en .

<#review-2>
    a prov:Activity ;
    prov:endedAtTime "2026-10-07T00:00:00Z"^^xsd:dateTime ;
    rdfs:label "Second review and primary-source checks (AI)"@en ;
    rdfs:comment "Scope: the revised chapters, reviewed again by an AI agent with the same question, and the claims the first review doubted checked against the primary sources and on local servers; not a human review."@en ,
                 "Outcome: five contradictions or stale claims were found, and that the minimal app did not exercise everything the later chapters teach; the third round of writing addressed them, and its review found the gaps the second had named closed."@en .

<#review-3>
    a prov:Activity ;
    prov:endedAtTime "2026-10-08T00:00:00Z"^^xsd:dateTime ;
    rdfs:label "Third review and version recheck (AI)"@en ;
    rdfs:comment "Scope: every chapter, the dossier and the recorded runs, reviewed a third time by an AI agent; every version, date and address the course gives as of October 2026 re-read from the live page, registry or repository on 2026-10-07; not a human review."@en ,
                 "Outcome: two dates had moved and two statements were made more exact; two small correctness problems were found and fixed in the text, each fix checked against the transcripts and steps it concerned."@en .

<#review-4>
    a prov:Activity ;
    prov:endedAtTime "2026-10-08T00:00:00Z"^^xsd:dateTime ;
    rdfs:label "Release text: facts, questions and examples (AI)"@en ;
    rdfs:comment "Scope: each chapter as rewritten for this release (hands-on parts turned into recorded examples, questions made to stand alone), reviewed by an AI agent against the recorded transcripts, the research notes and the chapter as drafted; not a human review."@en ,
                 "Outcome: the findings (such as unqualified version details, examples that did not match their transcript, options whose length or wording gave the answer away, and notes that relied on another chapter) were fixed in the text, or kept with a reason, and recorded in the course's working notes."@en .

<#review-5>
    a prov:Activity ;
    prov:endedAtTime "2026-10-10T00:00:00Z"^^xsd:dateTime ;
    rdfs:label "Version 2: theory in chunks (AI)"@en ;
    rdfs:comment "Scope: every step's theory split by an AI agent into chunks read one at a time, with a Markdown thematic break where its topic turns, never between a request or code and the sentence that leads into it, nor before a sentence that points back at what an earlier chunk shows; the release compared by a script with version 1, which found the breaks and the release's own metadata the only changes, and checked by the library checker (no empty chunk); not a human review."@en ,
                 "Outcome: 139 steps are read in two chunks and 14 in three; the other 40, short enough to read at once, stay whole. No text was reworded, and every chapter, step, card and distractor keeps its id."@en .

<#review-6>
    a prov:Activity ;
    prov:endedAtTime "2026-10-10T00:00:00Z"^^xsd:dateTime ;
    rdfs:label "Version 3: title, description and keywords in Korean, German, Spanish and French (AI)"@en ;
    rdfs:comment "Scope: the deck’s title, description and keywords, translated by an AI agent from the English (the Swedish settling what was ambiguous) into Korean, German, Spanish and French, in the words the app itself uses, and checked by a second AI agent that translated every text back into English and fixed what had drifted; the release compared by a script with version 2, which found the new title, description and keywords and the release’s own metadata the only changes, and checked by the library checker; not a human review."@en ,
                 "Outcome: the title, description and keywords are in Korean, German, Spanish and French as well; no card, chapter, step or distractor changed."@en .

<#review-7>
    a prov:Activity ;
    prov:endedAtTime "2026-10-13T00:00:00Z"^^xsd:dateTime ;
    rdfs:label "Version 4: questions that work as flip cards too (AI)"@en ;
    rdfs:comment "Scope: every question of the course read by AI agents as it is later studied flip-and-grade, its front alone with no options, for questions whose answer is one of several valid ones or that make sense only with their options; each finding put to three more AI agents that tried to refute it. The questions upheld were rewritten by an AI agent and each revision checked by three others, for recall from the front alone, for the multiple choice (one correct option; wrong options plausible, of the same form and wrong for the new question) and for its facts against the step's theory, and rewritten until all three passed; the release checked by the library checker; not a human review."@en ,
                 "Outcome: of 466 questions, 20 are asked anew (7 with a back reworded to answer the new question, its meaning kept); 26 wrong options that no longer fitted are retired and 26 new ones added, and a few kept ones are reworded to the new question with the same wrong claim. Every chapter, step and card keeps its id."@en .

<#review-8>
    a prov:Activity ;
    prov:endedAtTime "2026-10-22T00:00:00Z"^^xsd:dateTime ;
    rdfs:label "Version 5: more questions that work as flip cards too (AI)"@en ;
    rdfs:comment "Scope: the review question on fetching a WebID with a hash, reported in the library's issue tracker as making sense only with its options in view, and then every question of the course read again by AI agents as it is later studied flip-and-grade, its front alone with no options, for questions whose answer is one of several valid ones, that make sense only with their options or that do not ask for what the back answers; each finding put to three more AI agents, and kept when two upheld it. The questions upheld were rewritten by an AI agent and each revision checked by three others, for recall from the front alone, for the multiple choice (one correct option; wrong options plausible, of the same form and length and wrong for the new question) and for its facts against the step's theory, and rewritten until all three passed; the release compared with version 4 and checked by the library checker; not a human review."@en ,
                 "Outcome: of 466 questions, 10 are asked anew (7 with a back reworded to answer the new question, its meaning kept); 14 wrong options that no longer fitted are retired and 14 new ones added, and 10 kept ones are reworded to the new question with the same wrong claim. Every chapter, step and card keeps its id."@en .

<http://xmlns.com/foaf/spec/>
    dcterms:title "FOAF Vocabulary Specification 0.99" ;
    dcterms:creator "Brickley & Miller" ;
    rdfs:comment "The document: \"Copyright © 2000-2014 Dan Brickley and Libby Miller This work is licensed under a Creative Commons Attribution License. This copyright applies to the FOAF Vocabulary Specification and accompanying documentation in RDF.\" Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"indicating some level of reciprocated interaction\". Otherwise used for facts only. Reliability: authoritative (de facto standard, not W3C). Used for: FOAF terms used in profiles; FOAF published in OWL."@en .

<https://5stardata.info/en/>
    dcterms:title "5 ★ Open Data" ;
    dcterms:creator "originally LATC project; maintained by James G. Kim and Michael Hausenblas" ;
    rdfs:comment "The page's footer: \"Unless noted, content on this site is freely available under the CC0 Public Domain Dedication.\" Used for facts only: nothing copied. Reliability: secondary. Used for: 5-star open data scale explained."@en .

<https://archives.iw3c2.org/www2016/WWW2016-Proceedings/companion/p223.pdf>
    dcterms:title "A Demonstration of the Solid Platform for Social Web Applications" ;
    dcterms:creator "Mansour, Sambra, Hawke, Zereba, Capadisli, Ghanem, Aboulnaga, Berners-Lee; WWW 2016 Companion, ACM" ;
    rdfs:comment "The paper's first page: \"Copyright is held by the author/owner(s). WWW'16 Companion, April 11–15, 2016, Montréal, Québec, Canada. ACM 978-1-4503-4144-8/16/04.\" No licence is given; it is treated as all rights reserved. Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"can have one or more pods from different pod providers, and can easily switch between providers\", \"none of these proposals has been widely adopted yet\". Otherwise used for facts only. Reliability: secondary (peer-reviewed). Used for: Data silos, their three consequences, Solid's original architecture and goals."@en .

<https://arxiv.org/abs/2302.06933>
    dcterms:title "Evaluation of Link Traversal Query Execution over Decentralized Environments with Structural Assumptions" ;
    dcterms:creator "Taelman, Verborgh; arXiv" ;
    rdfs:comment "The abstract page links the paper's licence, http://creativecommons.org/licenses/by/4.0/ (CC BY 4.0). Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"in the order of seconds for non-complex queries\". Otherwise used for facts only. Reliability: secondary (peer-reviewed). Used for: Link traversal query performance over simulated pods (\"in the order of seconds\")."@en .

<https://blog.ldodds.com/2024/03/12/baffled-by-solid/>
    dcterms:title "Baffled by Solid" ;
    dcterms:creator "Leigh Dodds" ;
    rdfs:comment "The blog's footer: \"This work is licensed under a Creative Commons Attribution 4.0 International License.\" Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"Solid has no built in understanding of any specific schemas or formats\", \"accidentally sharing sensitive information because they don't realise the extent of what they're sharing\". Otherwise used for facts only. Reliability: opinion (expert blog with comments). Used for: Outside critique: vocabulary fragmentation, unclear governance, developer confusion."@en .

<https://cheatsheetseries.owasp.org/cheatsheets/Cross_Site_Scripting_Prevention_Cheat_Sheet.html>
    dcterms:title "OWASP Cross Site Scripting Prevention Cheat Sheet" ;
    dcterms:creator "OWASP" ;
    rdfs:comment "The page's footer: \"©Copyright - Cheat Sheets Series Team - This work is licensed under Creative Commons Attribution-ShareAlike 4.0 International.\" Used for facts only: nothing copied. Reliability: authoritative (security guidance). Used for: Safe sinks such as textContent, URL scheme allow-lists, framework escape hatches, CSP as defence in depth."@en .

<https://cheatsheetseries.owasp.org/cheatsheets/Server_Side_Request_Forgery_Prevention_Cheat_Sheet.html>
    dcterms:title "OWASP Server-Side Request Forgery Prevention Cheat Sheet" ;
    dcterms:creator "OWASP" ;
    rdfs:comment "The page's footer: \"©Copyright - Cheat Sheets Series Team - This work is licensed under Creative Commons Attribution-ShareAlike 4.0 International.\" Used for facts only: nothing copied. Reliability: authoritative (security guidance). Used for: Validating resolved IPs, DNS rebinding, redirects and cloud metadata addresses when a server fetches user-given URLs."@en .

<https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/authorization-methods/>
    dcterms:title "CSS documentation: Authorization methods" ;
    dcterms:creator "Community Solid Server" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: CSS can run WAC or ACP; how it is configured."@en .

<https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/client-credentials/>
    dcterms:title "CSS docs: Client credentials" ;
    dcterms:creator "CSS project" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: Creating client credentials through the CSS account API."@en .

<https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/example-requests/>
    dcterms:title "Community Solid Server: Example HTTP requests" ;
    dcterms:creator "CSS project / imec" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: Concrete HTTP requests against CSS, SPARQL Update support."@en .

<https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/identity-provider/>
    dcterms:title "Community Solid Server docs: Identity Provider" ;
    dcterms:creator "CSS project" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: CSS identity provider: accounts, WebID linking, WebIDs hosted elsewhere."@en .

<https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/metadata/>
    dcterms:title "Community Solid Server: Editing metadata of resources" ;
    dcterms:creator "CSS project" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: CSS .meta resources and editable metadata."@en .

<https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/notifications/>
    dcterms:title "Community Solid Server: Receiving notifications" ;
    dcterms:creator "CSS project" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: CSS notifications: subscription service, channel lifetimes, state = ETag, Read on the topic."@en .

<https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/seeding-pods/>
    dcterms:title "CSS docs: Seeding pods" ;
    dcterms:creator "CSS project" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: Seeding pods from a JSON file of accounts."@en .

<https://communitysolidserver.github.io/CommunitySolidServer/latest/usage/starting-server/>
    dcterms:title "CSS docs: Starting the server" ;
    dcterms:creator "CSS project" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: Starting CSS: in-memory vs file configs, ports, base URL."@en .

<https://comunica.dev/docs/query/advanced/solid/>
    dcterms:title "Comunica — Querying Solid" ;
    dcterms:creator "Comunica" ;
    rdfs:comment "The page states no licence; its footer reads \"©2018 – 2026 Ghent University – imec, Belgium Source of this\"; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: Querying pods with Comunica, authenticated fetch as sources."@en .

<https://comunica.dev/research/link_traversal/>
    dcterms:title "Comunica — Link Traversal research" ;
    dcterms:creator "Comunica / IDLab" ;
    rdfs:comment "The page states no licence; its footer reads \"©2018 – 2026 Ghent University – imec, Belgium Source of this\"; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (research project page). Used for: Link traversal querying over pods."@en .

<https://dapsi.ngi.eu/success-story-pds-pod-migrator-migrating-your-solid-data/>
    dcterms:title "Success Story: PDS Pod Migrator – Migrating your Solid data" ;
    dcterms:creator "NGI DAPSI, c. 2022" ;
    rdfs:comment "The page states no licence; its footer reads \"Copyright © 2022 The DAPSI Consortium\"; it is treated as all rights reserved. Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"is a far cry from actually moving it to somewhere else and have everything continue to work as before\". Otherwise used for facts only. Reliability: secondary. Used for: Pod migration tooling and why moving a pod is hard."@en .

<https://dev.solidproject.org/>
    dcterms:title "Solid Developer Documentation, incl. \"Building your first Solid App with LDO & React\"" ;
    dcterms:creator "Solid Project" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: dev.solidproject.org and its LDO & React tutorial: a beginner app and its hard-coded container choice."@en .

<https://dev.solidproject.org/guides/authenticating_with_a_script/>
    dcterms:title "\"Authenticating with a Node.js Script\"" ;
    dcterms:creator "Solid Project" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: Authenticating a Node.js script with client credentials."@en .

<https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS>
    dcterms:title "Cross-Origin Resource Sharing (CORS)" ;
    dcterms:creator "MDN Web Docs" ;
    rdfs:comment "The page footer: \"Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license.\" MDN's licensing page (https://developer.mozilla.org/en-US/docs/MDN/Writing_guidelines/Attrib_copyright_license): \"the content is available under the terms of the Creative Commons Attribution-ShareAlike license (CC-BY-SA), v2.5 or any later version\". Used for facts only: nothing copied. Reliability: authoritative (MDN reference). Used for: CORS, credentials and the * restriction."@en .

<https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS/Errors>
    dcterms:title "CORS errors" ;
    dcterms:creator "MDN Web Docs" ;
    rdfs:comment "The page footer: \"Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license.\" MDN's licensing page (https://developer.mozilla.org/en-US/docs/MDN/Writing_guidelines/Attrib_copyright_license): \"the content is available under the terms of the Creative Commons Attribution-ShareAlike license (CC-BY-SA), v2.5 or any later version\". Used for facts only: nothing copied. Reliability: authoritative. Used for: CORS failure details are hidden from scripts and shown only in the browser console."@en .

<https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS/Errors/CORSDidNotSucceed>
    dcterms:title "Reason: CORS request did not succeed" ;
    dcterms:creator "MDN Web Docs" ;
    rdfs:comment "The page footer: \"Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license.\" MDN's licensing page (https://developer.mozilla.org/en-US/docs/MDN/Writing_guidelines/Attrib_copyright_license): \"the content is available under the terms of the Creative Commons Attribution-ShareAlike license (CC-BY-SA), v2.5 or any later version\". Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"CORS request did not succeed\". Otherwise used for facts only. Reliability: authoritative. Used for: Firefox reports DNS, connection and TLS failures as a CORS error."@en .

<https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP>
    dcterms:title "Content Security Policy (CSP) guide" ;
    dcterms:creator "MDN Web Docs" ;
    rdfs:comment "The page footer: \"Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license.\" MDN's licensing page (https://developer.mozilla.org/en-US/docs/MDN/Writing_guidelines/Attrib_copyright_license): \"the content is available under the terms of the Creative Commons Attribution-ShareAlike license (CC-BY-SA), v2.5 or any later version\". Used for facts only: nothing copied. Reliability: authoritative. Used for: Deliver CSP as a response header; the <meta> form lacks some features."@en .

<https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Access-Control-Expose-Headers>
    dcterms:title "Access-Control-Expose-Headers" ;
    dcterms:creator "MDN Web Docs" ;
    rdfs:comment "The page footer: \"Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license.\" MDN's licensing page (https://developer.mozilla.org/en-US/docs/MDN/Writing_guidelines/Attrib_copyright_license): \"the content is available under the terms of the Creative Commons Attribution-ShareAlike license (CC-BY-SA), v2.5 or any later version\". Used for facts only: nothing copied. Reliability: authoritative. Used for: Only safelisted response headers reach cross-origin scripts unless exposed."@en .

<https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy>
    dcterms:title "Content-Security-Policy" ;
    dcterms:creator "MDN Web Docs" ;
    rdfs:comment "The page footer: \"Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license.\" MDN's licensing page (https://developer.mozilla.org/en-US/docs/MDN/Writing_guidelines/Attrib_copyright_license): \"the content is available under the terms of the Creative Commons Attribution-ShareAlike license (CC-BY-SA), v2.5 or any later version\". Used for facts only: nothing copied. Reliability: authoritative. Used for: script-src, connect-src, default-src as fallback for img-src; scheme sources."@en .

<https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy>
    dcterms:title "Same-origin policy" ;
    dcterms:creator "MDN Web Docs" ;
    rdfs:comment "The page footer: \"Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license.\" MDN's licensing page (https://developer.mozilla.org/en-US/docs/MDN/Writing_guidelines/Attrib_copyright_license): \"the content is available under the terms of the Creative Commons Attribution-ShareAlike license (CC-BY-SA), v2.5 or any later version\". Used for facts only: nothing copied. Reliability: authoritative (MDN reference). Used for: Same-origin policy basics."@en .

<https://docs.activitypods.org/architecture/application-interoperability/>
    dcterms:title "ActivityPods: Application interoperability" ;
    dcterms:creator "ActivityPods" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: ActivityPods implements SAI application registrations."@en .

<https://docs.inrupt.com/ess/2.7/services/service-notification/service-websocket>
    dcterms:title "ESS WebSocket Notification Service" ;
    dcterms:creator "Inrupt, ESS 2.7 docs" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (vendor). Used for: ESS 2.x WebSocket service implemented an earlier protocol version (solid-0.2); ⚠ historical: ESS 3.0 (2026-05-27) removed this service in favour of the Notification Delivery Service."@en .

<https://docs.inrupt.com/ess/2.7/services/service-webid>
    dcterms:title "ESS 2.7 WebID Service" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (vendor). Used for: ESS WebID service restricts which apps edit profiles. Round 3: the service requires a solid:oidcIssuer triple naming the configured issuer in hosted profiles."@en .

<https://docs.inrupt.com/ess/latest/>
    dcterms:title "Inrupt ESS 3.3 docs and Services" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (vendor). Used for: Inrupt ESS 3.3 services overview."@en .

<https://docs.inrupt.com/ess/releases.md>
    dcterms:title "ESS Release Notes" ;
    dcterms:creator "Inrupt, ESS 3.3.0 released 2026-09-10" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (vendor). Used for: ESS 3.3.0 as the current release; ESS 3.0.0 (2026-05-27) removed the WebSocket Notification Service and made Access Grants independent of ACP. Round 3: re-read; 3.3.0 is still the latest release."@en .

<https://docs.inrupt.com/ess/services/service-access-grant>
    dcterms:title "ESS Access Grant Service" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (vendor). Used for: Access Grants as verifiable credentials, an Inrupt feature outside the Solid Protocol."@en .

<https://docs.inrupt.com/ess/services/service-access-grant/issue-endpoint>
    dcterms:title "ESS Access Grant Service: issue endpoint" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (vendor). Used for: Issuing access grants."@en .

<https://docs.inrupt.com/guides/access-control-policies>
    dcterms:title "Access Control Policies (guide)" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (vendor). Used for: Inrupt's ACP guide."@en .

<https://docs.inrupt.com/guides/authentication-in-solid/authentication-from-browser.md>
    dcterms:title "Inrupt: Authentication from the browser" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (vendor). Used for: Browser login: login(), handleIncomingRedirect(), dynamic client registration."@en .

<https://docs.inrupt.com/guides/authentication-in-solid/authentication-from-browser/session-restore-upon-browser-refresh.md>
    dcterms:title "Inrupt: Session restore upon browser refresh" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (vendor). Used for: Session restore after refresh, tokens kept only in memory."@en .

<https://docs.inrupt.com/guides/authentication-in-solid/authentication-server-side.md>
    dcterms:title "Inrupt: Authentication Server Side" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (vendor). Used for: Per-user login in a Node web server with @inrupt/solid-client-authn-node, session ids in cookies, persisting sessions."@en .

<https://docs.inrupt.com/guides/authentication-in-solid/authentication-single-user-application.md>
    dcterms:title "Inrupt: Authentication for single-user applications (client credentials)" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (vendor). Used for: Client credentials for single-user scripts."@en .

<https://docs.inrupt.com/guides/universal-api>
    dcterms:title "Universal API (guide)" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (vendor). Used for: universalAccess API hiding WAC/ACP differences."@en .

<https://docs.inrupt.com/guides/webid-document-best-practices/managing-webid-profiles>
    dcterms:title "Managing WebID Profiles" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (vendor). Used for: Managing WebID profiles in ESS."@en .

<https://docs.inrupt.com/podspaces/podspaces.md>
    dcterms:title "Inrupt PodSpaces docs" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"Do not use for production or for storing sensitive/personal data\". Otherwise used for facts only. Reliability: authoritative (vendor). Used for: PodSpaces: login.inrupt.com vs storage.inrupt.com, separate roles."@en .

<https://docs.inrupt.com/sdk/javascript-sdk/authentication.md>
    dcterms:title "Inrupt JavaScript SDK: Authentication (and \"Authentication in Solid\" overview https://docs.inrupt.com/guides/authentication-in-solid.md)" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (vendor). Used for: solid-client-authn overview and login options."@en .

<https://docs.inrupt.com/sdk/javascript-sdk/read-and-write-rdf-data.md>
    dcterms:title "Read and Write RDF Data (Inrupt JavaScript SDK docs)" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (vendor). Used for: How solid-client reads and writes RDF (Thing, SolidDataset)."@en .

<https://docs.inrupt.com/sdk/javascript-sdk/tutorial>
    dcterms:title "Inrupt JavaScript SDK tutorial" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (vendor). Used for: Anatomy of a Solid app; SolidDataset/Thing tutorial."@en .

<https://docs.inrupt.com/security/authorization>
    dcterms:title "Authorization (ESS)" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (vendor). Used for: ESS uses ACP and does not support WAC in production."@en .

<https://docs.inrupt.com/security/authorization/access-requests-grants.md>
    dcterms:title "Access Requests and Grants (security overview)" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (vendor). Used for: Security model of access requests and grants."@en .

<https://docs.netlify.com/manage/routing/headers/>
    dcterms:title "Custom headers (Netlify) and Headers (Cloudflare Pages)" ;
    dcterms:creator "Netlify and Cloudflare" ;
    rdfs:comment "The page states no licence; its footer reads \"© 2026 Netlify Ask Netlify Help\"; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (vendor). Used for: Setting response headers such as CSP for a static site with a _headers file."@en .

<https://forum.solidproject.org/t/acl-format-for-authorising-new-apps/1655>
    dcterms:title "\".acl format for authorising new apps\" (forum thread)" ;
    dcterms:creator "Solid Community Forum" ;
    rdfs:comment "The forum's Terms of Service (https://forum.solidproject.org/tos), section 3: \"User contributions are licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.\" Used for facts only: nothing copied. Reliability: opinion (forum). Used for: acl:trustedApp in profiles and app authorisation."@en .

<https://forum.solidproject.org/t/how-to-authenticate-an-app-with-its-own-identity-e-g-webid/5946>
    dcterms:title "\"How to authenticate an App with its own identity (e.g. WebID)?\" forum thread" ;
    dcterms:creator "Solid Community Forum" ;
    rdfs:comment "The forum's Terms of Service (https://forum.solidproject.org/tos), section 3: \"User contributions are licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.\" Used for facts only: nothing copied. Reliability: opinion (forum). Used for: Apps with their own identity."@en .

<https://forum.solidproject.org/t/solid-interop-in-practice/7701>
    dcterms:title "Solid Interop in Practice" ;
    dcterms:creator "Solid Forum, Rosano" ;
    rdfs:comment "The forum's Terms of Service (https://forum.solidproject.org/tos), section 3: \"User contributions are licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.\" Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"the only one you can use in practice\". Otherwise used for facts only. Reliability: opinion (forum). Used for: 2024 community summary: type indexes \"the only one you can use in practice\"."@en .

<https://forum.solidproject.org/t/upcoming-software-switch-for-solidcommunity-net/8608>
    dcterms:title "\"Upcoming software switch for solidcommunity.net\"" ;
    dcterms:creator "Solid forum, Michiel de Jong" ;
    rdfs:comment "The forum's Terms of Service (https://forum.solidproject.org/tos), section 3: \"User contributions are licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.\" Used for facts only: nothing copied. Reliability: authoritative (operator announcement). Used for: solidcommunity.net moving from NSS to Pivot (January 2025)."@en .

<https://forum.solidproject.org/t/why-deprecate-direct-webid-tls/2953>
    dcterms:title "\"Why deprecate direct webid-tls?\" forum thread" ;
    dcterms:creator "Solid Community Forum" ;
    rdfs:comment "The forum's Terms of Service (https://forum.solidproject.org/tos), section 3: \"User contributions are licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.\" Used for facts only: nothing copied. Reliability: opinion (forum). Used for: Why WebID-TLS was deprecated."@en .

<https://forum.solidproject.org/t/why-is-acl-trustedapp-visible-for-everyone-on-css/5603>
    dcterms:title "\"Why is ACL:TrustedApp visible for everyone? (on CSS)\" (forum thread)" ;
    dcterms:creator "Solid Community Forum" ;
    rdfs:comment "The forum's Terms of Service (https://forum.solidproject.org/tos), section 3: \"User contributions are licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.\" Used for facts only: nothing copied. Reliability: opinion (forum). Used for: trustedApp entries visible to everyone."@en .

<https://gdpr-info.eu/art-20-gdpr/>
    dcterms:title "Art. 20 GDPR – Right to data portability" ;
    dcterms:creator "Regulation (EU) 2016/679, via gdpr-info.eu" ;
    rdfs:comment "The page states no licence; the words quoted are those of Article 20 of Regulation (EU) 2016/679, an official legislative text. Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"in a structured, commonly used and machine-readable format\", \"where technically feasible\". Otherwise used for facts only. Reliability: normative (EU law). Used for: GDPR Art. 20 data portability wording."@en .

<https://github.com/CommunitySolidServer/access-token-verifier>
    dcterms:title "@solid/access-token-verifier README, plus CSS source DPoPWebIdExtractor.ts / BearerWebIdExtractor.ts" ;
    dcterms:creator "CSS project" ;
    rdfs:comment "The repository's licence file, LICENSE, is the MIT License: \"Copyright (c) 2020-2022 Solid and contributors\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative. Used for: Token verification: DPoP checks, http WebIDs rejected."@en .

<https://github.com/CommunitySolidServer/access-token-verifier/blob/v2.1.1/src/config/index.ts>
    dcterms:title "@solid/access-token-verifier 2.1.1: cache and DPoP settings" ;
    dcterms:creator "CommunitySolidServer" ;
    rdfs:comment "The repository's licence file, LICENSE, is the MIT License: \"Copyright (c) 2020-2022 Solid and contributors\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative (source code of the version CSS 7.2.0 bundles). Used for: A WebID's issuer list is cached for 120 s; DPoP proofs may be up to 120 s old, plus 120 s clock tolerance; ath is checked only when present."@en .

<https://github.com/CommunitySolidServer/CommunitySolidServer>
    dcterms:title "CommunitySolidServer README" ;
    dcterms:creator "imec / Inrupt" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright © 2019–2025 Inrupt Inc. and imec\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative. Used for: CSS features, licence, storage backends, WAC/ACP."@en .

<https://github.com/CommunitySolidServer/CommunitySolidServer/blob/main/config/util/auxiliary/strategies/acl.json>
    dcterms:title "Community Solid Server default config: ACL auxiliary strategy (config/util/auxiliary/strategies/acl.json)" ;
    dcterms:creator "CSS project" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright © 2019–2025 Inrupt Inc. and imec\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative. Used for: CSS .acl suffix convention for ACL auxiliary resources."@en .

<https://github.com/CommunitySolidServer/CommunitySolidServer/blob/main/RELEASE_NOTES.md>
    dcterms:title "CSS release notes and GitHub releases" ;
    dcterms:creator "CSS project" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright © 2019–2025 Inrupt Inc. and imec\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative. Used for: CSS release history: v7.2.0 current, v8 alpha."@en .

<https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/config/http/middleware/handlers/cors.json>
    dcterms:title "CSS 7.2.0 CORS handler and configuration" ;
    dcterms:creator "Community Solid Server" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright © 2019–2025 Inrupt Inc. and imec\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative (source code). Used for: Which origins, methods and exposed headers CSS 7.2 allows."@en .

<https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/config/identity/handler/base/provider-factory.json>
    dcterms:title "CSS 7.2.0 config: provider-factory.json" ;
    dcterms:creator "Community Solid Server" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright © 2019–2025 Inrupt Inc. and imec\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative (source code). Used for: Default scopes and token lifetimes (access token 3600 s, client credentials 600 s, refresh token 86400 s). Round 3: offline_access is among the scopes."@en .

<https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/src/authorization/OwnerPermissionReader.ts>
    dcterms:title "CSS 7.2.0 OwnerPermissionReader, WebAclReader and storage-location configs" ;
    dcterms:creator "CSS project" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright © 2019–2025 Inrupt Inc. and imec\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative (source code). Used for: why the owner rescue applies with storage/location/pod.json but not with the default root.json. Also the WebAclReader, for Chapter 8."@en .

<https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/src/http/input/body/N3PatchBodyParser.ts>
    dcterms:title "CSS 7.2.0 source: N3PatchBodyParser.ts" ;
    dcterms:creator "Community Solid Server" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright © 2019–2025 Inrupt Inc. and imec\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative (source code). Used for: CSS 7.2 rejects blank nodes in N3 Patch inserts and deletes with 422, following v0.11."@en .

<https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/src/identity/interaction/oidc/ConsentHandler.ts>
    dcterms:title "CSS 7.2.0 source: ConsentHandler.ts" ;
    dcterms:creator "CSS project" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright © 2019–2025 Inrupt Inc. and imec\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative (source code). Used for: \"Reject the offline_access scope if the user does not want to be remembered\": no refresh token unless \"Remember this client\" stays ticked."@en .

<https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/src/identity/interaction/webid/LinkWebIdHandler.ts>
    dcterms:title "CSS 7.2.0 source: LinkWebIdHandler.ts" ;
    dcterms:creator "Community Solid Server" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright © 2019–2025 Inrupt Inc. and imec\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative (source code of the version run). Used for: Ownership is checked only for WebIDs the account did not create; the response carries oidcIssuer: baseUrl."@en .

<https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/src/identity/ownership/TokenOwnershipValidator.ts>
    dcterms:title "CSS 7.2.0 source: TokenOwnershipValidator.ts" ;
    dcterms:creator "Community Solid Server" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright © 2019–2025 Inrupt Inc. and imec\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative (source code). Used for: Linking an external WebID to a CSS account needs a solid:oidcIssuerRegistrationToken triple in its profile, not solid:oidcIssuer."@en .

<https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/src/identity/storage/ClientIdAdapterFactory.ts>
    dcterms:title "CSS 7.2.0 source: ClientIdAdapterFactory.ts" ;
    dcterms:creator "Community Solid Server" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright © 2019–2025 Inrupt Inc. and imec\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"SSL is required for client_id authentication unless working locally.\". Otherwise used for facts only. Reliability: authoritative (source code). Used for: Client ID documents must be https or http://localhost and are fetched on each lookup."@en .

<https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/src/init/SeededAccountInitializer.ts>
    dcterms:title "CSS 7.2.0 source: SeededAccountInitializer.ts" ;
    dcterms:creator "Community Solid Server" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright © 2019–2025 Inrupt Inc. and imec\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative (source code). Used for: The seed-file schema and the log lines of a seeded start."@en .

<https://github.com/CommunitySolidServer/CommunitySolidServer/blob/v7.2.0/templates/identity/account/link-webid.html.ejs>
    dcterms:title "CSS 7.2.0 account page templates (link-webid.html.ejs, resource.html.ejs)" ;
    dcterms:creator "Community Solid Server" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright © 2019–2025 Inrupt Inc. and imec\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative (source code). Used for: \"You will need to manually add the following triple … to indicate that you trust this server as a login provider\"; the warning to remove solid:oidcIssuer after unlinking."@en .

<https://github.com/CommunitySolidServer/CommunitySolidServer/tree/main/templates/pod>
    dcterms:title "CSS pod templates (templates/pod/wac/.acl.hbs, templates/pod/wac/profile/card.acl.hbs, templates/pod/acp/.acr.hbs) and latest release v7.2.0" ;
    dcterms:creator "CommunitySolidServer on GitHub" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright © 2019–2025 Inrupt Inc. and imec\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative. Used for: CSS default pod ACL/ACR templates."@en .

<https://github.com/CommunitySolidServer/CommunitySolidServer/tree/v7.2.0>
    dcterms:title "Community Solid Server v7.2.0 source tree (notifications, quota)" ;
    dcterms:creator "CSS project" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright © 2019–2025 Inrupt Inc. and imec\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". The recorded runs show what Community Solid Server 7.2.0 wrote and answered: the root ACL it writes for a new pod (Step 8.6, comments removed), its log lines (Step 12.3) and its error messages (Steps 6.2, 6.5 and 6.10), a few lines of the server's output, not a substantial portion of the software. Reliability: authoritative (source code). Used for: Notification.ts sends the singular notification/v1 context, and the notifications docs pair it with the full type IRI; a write past a pod quota fails with 413 (PayloadHttpError) and is not stored (QuotaValidator, pod-quota-file.json)."@en .

<https://github.com/CommunitySolidServer/CommunitySolidServer/tree/v7.2.0/src/server/notifications/WebhookChannel2023>
    dcterms:title "CSS 7.2.0 source: WebhookChannel2023" ;
    dcterms:creator "Community Solid Server" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright © 2019–2025 Inrupt Inc. and imec\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative (source code). Used for: How CSS signs webhook POSTs (DPoP token, iss without trailing slash, the server's notification WebID)."@en .

<https://github.com/digitalbazaar/jsonld.js>
    dcterms:title "jsonld.js README" ;
    dcterms:creator "Digital Bazaar" ;
    rdfs:comment "The repository's licence file, LICENSE: \"You may use the jsonld.js project under the terms of the BSD License.\" Used for facts only: nothing copied. Reliability: authoritative. Used for: jsonld.compact, jsonld.expand and jsonld.frame in JavaScript."@en .

<https://github.com/inrupt/solid-client-authn-js>
    dcterms:title "inrupt/solid-client-authn-js repository, README and CHANGELOG (v5.0.1; npm registry metadata)" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The repository's licence file, LICENSE, is the MIT License: \"Copyright Inrupt Inc.\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative. Used for: solid-client-authn-js v5 packages and changes. Round 2: default scopes include offline_access, refresh 5 s before expiry, when sessionExpired fires."@en .

<https://github.com/inrupt/solid-client-authn-js/blob/main/ARCHITECTURE.md>
    dcterms:title "solid-client-authn-js ARCHITECTURE.md" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The repository's licence file, LICENSE, is the MIT License: \"Copyright Inrupt Inc.\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative. Used for: How the auth library implements DPoP, PKCE and token handling."@en .

<https://github.com/inrupt/solid-client-authn-js/blob/main/packages/browser/src/Session.ts>
    dcterms:title "solid-client-authn-js: browser Session.ts" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The repository's licence file, LICENSE, is the MIT License: \"Copyright Inrupt Inc.\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative (source code). Used for: App vs IdP logout, postLogoutUrl, restorePreviousSession and sessionRestore, the sessionExpired handler."@en .

<https://github.com/inrupt/solid-client-js/blob/main/CHANGELOG.md>
    dcterms:title "solid-client-js CHANGELOG" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The repository's licence file, LICENSE, is the MIT License: \"Copyright Inrupt Inc.\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative. Used for: solid-client-js v4 as the current major version."@en .

<https://github.com/linkeddata/rdflib.js>
    dcterms:title "rdflib.js README" ;
    dcterms:creator "linkeddata" ;
    rdfs:comment "The repository's licence file, MIT-LICENSE.txt, is the MIT License: \"Copyright 2000-2012 MIT and other contributors\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative. Used for: rdflib.js as the oldest library and SolidOS base."@en .

<https://github.com/nodeSolidServer/node-solid-server>
    dcterms:title "Node Solid Server README" ;
    dcterms:creator "NSS project" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright © 2014–present Arne Hassel, Nicola Greco, Kjetil Kjernsmo, Martin Martinez Rivera, Andrei Sambra, Ruben Taelman, Ruben Verborgh, and Dmitri Zagidulin\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative. Used for: NSS: legacy features, Updates-Via WebSockets, data browser."@en .

<https://github.com/nodeSolidServer/node-solid-server/releases>
    dcterms:title "node-solid-server releases" ;
    dcterms:creator "NSS project" ;
    rdfs:comment "A page of GitHub's own (a releases page), whose text no licence covers (the repository's MIT licence covers its files); it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: NSS v6.0.0 (January 2026)."@en .

<https://github.com/nodeSolidServer/node-solid-server/tree/v6.0.0>
    dcterms:title "node-solid-server v6.0.0 source" ;
    dcterms:creator "NSS project" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright © 2014–present Arne Hassel, Nicola Greco, Kjetil Kjernsmo, Martin Martinez Rivera, Andrei Sambra, Ruben Taelman, Ruben Verborgh, and Dmitri Zagidulin\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". The recorded runs show what node-solid-server 6.0.0 answered (Step 14.13): a few lines of the server's output, not a substantial portion of the software. Reliability: authoritative (source code). Used for: NSS 6 sets no ETag on stored-format reads, ignores If-Match, honours only If-None-Match: * on PUT; its new-account inbox ACL gives the public acl:Append on the inbox with no acl:default."@en .

<https://github.com/NoelDeMartin/media-kraken>
    dcterms:title "Media Kraken repository" ;
    dcterms:creator "Noel De Martin" ;
    rdfs:comment "The repository's licence file, LICENSE, is the GNU General Public License, version 3. Used for facts only: nothing copied. Reliability: authoritative. Used for: Media Kraken example app."@en .

<https://github.com/NoelDeMartin/umai>
    dcterms:title "Umai repository" ;
    dcterms:creator "Noel De Martin" ;
    rdfs:comment "The repository's licence file, LICENSE, is the GNU General Public License, version 3. Used for facts only: nothing copied. Reliability: authoritative. Used for: Umai example app."@en .

<https://github.com/panva/node-oidc-provider/blob/v8.4.3/lib/helpers/defaults.js>
    dcterms:title "node-oidc-provider 8.4.3: rotateRefreshToken()" ;
    dcterms:creator "Filip Skokan" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright (c) 2015 Filip Skokan\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative (source code). Used for: Refresh tokens of public clients that are not sender-constrained are rotated on every use; others only past 70% of their lifetime."@en .

<https://github.com/pdsinterop/solid-nextcloud>
    dcterms:title "solid-nextcloud README" ;
    dcterms:creator "PDS Interop" ;
    rdfs:comment "The repository's licence file, LICENSE, is the MIT License: \"Copyright (c) 2020 pdsinterop\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative. Used for: Solid-Nextcloud plugin."@en .

<https://github.com/rdf-ext/rdf-ext>
    dcterms:title "rdf-ext README" ;
    dcterms:creator "RDF-Ext" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright © 2012–2015 Thomas Bergwinkl\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative. Used for: rdf-ext, RDF/JS."@en .

<https://github.com/rdfjs/N3.js>
    dcterms:title "N3.js README" ;
    dcterms:creator "RDF/JS" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright ©2012–present N3.js contributors\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative. Used for: N3.js parser/store, RDF/JS."@en .

<https://github.com/shapetrees/specification>
    dcterms:title "shapetrees/specification repository" ;
    dcterms:creator "GitHub" ;
    rdfs:comment "The repository's licence file, LICENSE, names the W3C Software and Document License. Used for facts only: nothing copied. Reliability: authoritative. Used for: Shape Trees spec now on GitHub."@en .

<https://github.com/solid-contrib/conformance-test-harness>
    dcterms:title "Conformance Test Harness" ;
    dcterms:creator "solid-contrib" ;
    rdfs:comment "The repository's licence file, LICENSE, is the MIT License: \"Copyright (c) 2019 - 2022 W3C Solid Community Group\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative. Used for: Conformance Test Harness."@en .

<https://github.com/solid-contrib/data-modules>
    dcterms:title "Solid Data Modules" ;
    dcterms:creator "solid-contrib, NLnet/NGI0" ;
    rdfs:comment "The repository has no licence file; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: Solid Data Modules: the README's list of modules on 2026-10-07 (bookmarks, chats, contacts; profile a stub, tasks coming soon)."@en .

<https://github.com/solid-contrib/pivot>
    dcterms:title "Pivot README" ;
    dcterms:creator "solid-contrib" ;
    rdfs:comment "The repository's licence file, LICENSE, is the MIT License: \"Copyright (c) 2019-2025 Solid, CSS, and SolidOS Contributors, Inrupt Inc. and imec.\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative. Used for: Pivot: CSS wrapper running solidcommunity.net."@en .

<https://github.com/solid-contrib/pivot/tree/4bf3123ecab6f7e54f2471b8d014e8dffd7da7cb>
    dcterms:title "Pivot source and configuration (v1.8.2)" ;
    dcterms:creator "solid-contrib" ;
    rdfs:comment "The repository's licence file, LICENSE, is the MIT License: \"Copyright (c) 2019-2025 Solid, CSS, and SolidOS Contributors, Inrupt Inc. and imec.\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative (the software's own config). Used for: Pivot's 70 MB pod quota is CSS's PodQuotaStrategy; Pivot does not change write errors."@en .

<https://github.com/solid-contrib/specification-tests>
    dcterms:title "Solid specification-tests" ;
    dcterms:creator "solid-contrib" ;
    rdfs:comment "The repository's licence file, LICENSE, is the MIT License: \"Copyright (c) 2019 - 2022 W3C Solid Community Group\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative. Used for: Specification tests (Karate, alice/bob users)."@en .

<https://github.com/solid-memo/website>
    dcterms:title "Solid Memo repository: README, docs and source" ;
    dcterms:creator "Solid Memo" ;
    rdfs:comment "The repository's licence file, LICENSE, is the MIT License: \"Copyright (c) 2026 Anton Wiklund\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative (first-hand, this project). Used for: Worked example (Chapter 15): data model, shapes, vocabulary versioning, migrations, hexagonal architecture, authentication, SPARQL Update patches, cross-server e2e matrix and expected failures. Round 2: ports, login checks, discovery, type index writes, write discipline, 412 retries, the answer log, layers and vendor rules, bulk upgrade, user journeys. Round 3 (also at commit 3ca313f): the write discipline on node-solid-server (no strong ETag, If-Match ignored, If-None-Match: * honoured since 5.8.8, a large edit's PUT unconditional), and how the e2e job treats expected failures."@en .

<https://github.com/solid/node-solid-server/blob/v6.0.0/lib/requests/create-account-request.mjs>
    dcterms:title "node-solid-server 6.0.0 source: create-account-request.mjs" ;
    dcterms:creator "Solid project" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright © 2014–present Arne Hassel, Nicola Greco, Kjetil Kjernsmo, Martin Martinez Rivera, Andrei Sambra, Ruben Taelman, Ruben Verborgh, and Dmitri Zagidulin\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative (source code). Used for: NSS refuses external WebIDs: \"Linked users not currently supported\"."@en .

<https://github.com/solid/solid-auth-client>
    dcterms:title "solid-auth-client README" ;
    dcterms:creator "Solid project" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"MIT License Copyright (c) 2017 - present\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"a legacy browser library\". Otherwise used for facts only. Reliability: authoritative. Used for: The legacy login library and its own pointer to the newer, more secure DPoP mechanism."@en .

<https://github.com/solid/solid-spec/blob/master/api-rest.md>
    dcterms:title "Solid HTTPS REST API Spec (legacy solid-spec, archived)" ;
    dcterms:creator "Solid" ;
    rdfs:comment "The repository's licence file, LICENSE, is the CC0 1.0 Universal public domain dedication. Step 6.9 copies its SPARQL Update PATCH example, which the repository's CC0 dedication covers. Reliability: authoritative (archived, historical). Used for: Legacy REST API: POST with an LDP type link to create containers."@en .

<https://github.com/solid/solid-spec/blob/master/api-websockets.md>
    dcterms:title "Solid WebSockets API (legacy, solid-0.1)" ;
    dcterms:creator "Solid" ;
    rdfs:comment "The repository's licence file, LICENSE, is the CC0 1.0 Universal public domain dedication. Used for facts only: nothing copied. Reliability: authoritative (archived, historical). Used for: Legacy solid-0.1 WebSocket API discovered via Updates-Via."@en .

<https://github.com/solid/solidproject.org/wiki/Create-your-own-vocabulary>
    dcterms:title "Create your own vocabulary" ;
    dcterms:creator "solidproject.org wiki" ;
    rdfs:comment "A page of GitHub's own (a wiki page), whose text no licence covers; it is treated as all rights reserved. Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"for which nothing else exists\". Otherwise used for facts only. Reliability: secondary (community wiki, archived docs). Used for: Advice on minting your own vocabulary."@en .

<https://github.com/solid/solidproject.org/wiki/Vocabularies-essential-to-solid>
    dcterms:title "Vocabularies essential to Solid" ;
    dcterms:creator "solidproject.org wiki" ;
    rdfs:comment "A page of GitHub's own (a wiki page), whose text no licence covers; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: secondary (community wiki). Used for: Which vocabularies Solid relies on."@en .

<https://github.com/solid/vocab>
    dcterms:title "solid/vocab repository" ;
    dcterms:creator "Solid project, GitHub" ;
    rdfs:comment "The repository has no licence file; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: Solid vocabulary sources."@en .

<https://github.com/solid/web-access-control-spec/issues/81>
    dcterms:title "Client identification, issue #81" ;
    dcterms:creator "solid/web-access-control-spec on GitHub" ;
    rdfs:comment "A page of GitHub's own (an issue thread), whose text no licence covers; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: WAC issue on client identification and acl:origin."@en .

<https://github.com/solid/webid-oidc-spec>
    dcterms:title "solid/webid-oidc-spec repository (archived)" ;
    dcterms:creator "Solid project" ;
    rdfs:comment "The repository's licence file, LICENSE, is the MIT License: \"Copyright (c) 2017 Solid\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative. Used for: WebID-OIDC, Solid-OIDC's predecessor, is archived."@en .

<https://github.com/SolidOS/mashlib>
    dcterms:title "mashlib README and v3.0.0 release" ;
    dcterms:creator "SolidOS team" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright (c) 2016 - present Tim Berners-Lee and contributors\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative. Used for: mashlib v3 data browser bundle."@en .

<https://github.com/SolidOS/solidos>
    dcterms:title "SolidOS README" ;
    dcterms:creator "SolidOS team" ;
    rdfs:comment "The repository's licence file, LICENSE.md, is the MIT License: \"Copyright 2019 - present\". The MIT License grants permission \"to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies\", provided its notice is included \"in all copies or substantial portions of the Software\". Used for facts only: nothing copied. Reliability: authoritative. Used for: SolidOS data browser."@en .

<https://imec-publications.be/entities/publication/60bf893e-54d1-4dd7-a596-6793b1e42ba5/full>
    dcterms:title "Solid-enabled personal online data stores: uncovering UX implications for online data management" ;
    dcterms:creator "Theys, Haegemans, Mechant, Bourgeus, Saldien; IHSED 2024, doi:10.54941/ahfe1005533" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"a challenge of explainability rather than usability\". Otherwise used for facts only. Reliability: secondary (peer-reviewed). Used for: UX study: fears, brand trust, \"explainability rather than usability\"."@en .

<https://inrupt.com/blog/solid-achieves-major-milestone-in-web-standardization-process>
    dcterms:title "Solid achieves major milestone in web standardization process" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; its footer reads \"© 2020-2025 Inrupt, Inc\"; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: opinion (vendor). Used for: LWS WG approval announced."@en .

<https://inrupt.com/blog/why-agentic-wallets>
    dcterms:title "Why Agentic Wallets" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; its footer reads \"© 2020-2025 Inrupt, Inc\"; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: opinion (vendor). Used for: AI agents and data wallets."@en .

<https://inrupt.com/case-study/flanders-strengthens-trusted-data-economy>
    dcterms:title "Flanders Government strengthens a trusted data economy with Inrupt's Enterprise Solid Server" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; its footer reads \"© 2020-2025 Inrupt, Inc\"; it is treated as all rights reserved. Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"utility company for data\". Otherwise used for facts only. Reliability: opinion (vendor case study). Used for: Flemish government pods; GDPR compliance through governance."@en .

<https://inrupt.com/one-small-step-for-the-web>
    dcterms:title "One Small Step for the Web" ;
    dcterms:creator "Tim Berners-Lee / Inrupt" ;
    rdfs:comment "The page states no licence; its footer reads \"© 2020-2025 Inrupt, Inc\"; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: opinion (founder/vendor). Used for: Inrupt's founding (2018)."@en .

<https://ldkit.io/>
    dcterms:title "LDkit" ;
    dcterms:creator "Karel Klíma" ;
    rdfs:comment "The page states no licence; its footer reads \"© 2021 – present Karel Klima\"; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: LDkit library (library table)."@en .

<https://ldo.js.org/latest/>
    dcterms:title "LDO — Linked Data Objects" ;
    dcterms:creator "O.team, NLnet/NGI Zero Entrust" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: LDO: ShEx-to-TypeScript generation, build:ldo, React hooks, Solid guide."@en .

<https://lists.w3.org/Archives/Public/public-solid/2024Oct/0007.html>
    dcterms:title "Tim Berners-Lee, message to public-solid on ODI stewardship" ;
    dcterms:creator "W3C public-solid mailing list" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: Berners-Lee on ODI stewardship; the community had no legal body."@en .

<https://lists.w3.org/Archives/Public/public-solid/2026Feb/0008.html>
    dcterms:title "Melvin Carvalho, JavaScript Solid Server announcement" ;
    dcterms:creator "W3C public-solid list" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"an early MVP and not production-ready\". Otherwise used for facts only. Reliability: authoritative (author announcement). Used for: JavaScript Solid Server: early MVP, AGPL."@en .

<https://lov.linkeddata.es/dataset>
    dcterms:title "Linked Open Vocabularies (LOV)" ;
    dcterms:creator "LOV" ;
    rdfs:comment "The page links its licence with rel=\"license\": http://creativecommons.org/licenses/by/4.0/ (CC BY 4.0). Used for facts only: nothing copied. Reliability: authoritative (tool). Used for: Searching for an existing vocabulary term before minting one."@en .

<https://lov.linkeddata.es/dataset/lov/vocabs/schema>
    dcterms:title "LOV: schema.org vocabulary page" ;
    dcterms:creator "LOV" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (tool). Used for: Prefix schema with namespace http://schema.org/."@en .

<https://noeldemartin.com/blog/interoperable-serendipity>
    dcterms:title "Interoperable Serendipity" ;
    dcterms:creator "Noel De Martin" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"by pure serendipity\". Otherwise used for facts only. Reliability: opinion (developer blog). Used for: Interoperable serendipity: reusing vocabularies across apps."@en .

<https://noeldemartin.com/tasks/implementing-a-recipes-manager-using-solid>
    dcterms:title "Noel De Martin, \"Implementing a Recipes Manager using Solid\"" ;
    dcterms:creator "Noel De Martin, development journal for Umai" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: opinion (developer journal). Used for: Umai's design: schema.org Recipe, offline-first browser storage before syncing, both http and https schema.org."@en .

<https://openid.net/specs/openid-connect-core-1_0.html>
    dcterms:title "OpenID Connect Core 1.0" ;
    dcterms:creator "OpenID Foundation" ;
    rdfs:comment "The page states no licence; its footer reads \"Copyright (c) 2023 The OpenID Foundation\"; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: normative (OpenID Foundation final spec). Used for: OIDC basics: ID tokens, discovery metadata, authentication vs authorization."@en .

<https://openid.net/specs/openid-connect-rpinitiated-1_0.html>
    dcterms:title "OpenID Connect RP-Initiated Logout 1.0" ;
    dcterms:creator "OpenID Foundation" ;
    rdfs:comment "The page states no licence; its footer reads \"Copyright (c) 2022 The OpenID Foundation\"; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: normative (OpenID Foundation final specification). Used for: The term \"RP-initiated logout\", end_session_endpoint and post_logout_redirect_uri."@en .

<https://penny.vincenttunru.com/>
    dcterms:title "Penny" ;
    dcterms:creator "Vincent Tunru" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: Penny pod inspector."@en .

<https://prefix.cc/>
    dcterms:title "prefix.cc" ;
    dcterms:creator "prefix.cc" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (tool). Used for: Looking up the usual namespace for a prefix."@en .

<https://registry.npmjs.org/>
    dcterms:title "npm registry and GitHub REST API metadata for the packages and repositories named above" ;
    dcterms:creator "npm, Inc. and GitHub, Inc." ;
    rdfs:comment "The registry's root document is a JSON status object that states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (registry metadata). Used for: Version numbers and release dates of packages. Round 3: dist-tags and publish times re-read for every package the appendix names; all unchanged."@en .

<https://registry.npmjs.org/solid-auth-client>
    dcterms:title "solid-auth-client on the npm registry" ;
    dcterms:creator "npm" ;
    rdfs:comment "The registry document gives the package's licence for each version as \"license\": \"MIT\". Used for facts only: nothing copied. Reliability: authoritative (registry metadata). Used for: The library's last release, not marked deprecated."@en .

<https://ruben.verborgh.org/articles/redecentralizing-the-web/>
    dcterms:title "Re-decentralizing the Web, for good this time" ;
    dcterms:creator "Ruben Verborgh" ;
    rdfs:comment "The page's footer: \"© 2012–2026 Ruben Verborgh All text & images licensed under CC BY 4.0 except where otherwise noted.\" Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"separate competitions for storage and apps emerge\", \"views on top of our data pod and those of others\", \"enabling choice, by breaking up artificially coupled decisions into individual options\". Otherwise used for facts only. Reliability: opinion (expert essay). Used for: Re-decentralisation argument: separate competitions for storage and apps."@en .

<https://ruben.verborgh.org/blog/2019/06/17/shaping-linked-data-apps/>
    dcterms:title "Shaping Linked Data apps" ;
    dcterms:creator "Ruben Verborgh" ;
    rdfs:comment "The page's footer: \"© 2012–2026 Ruben Verborgh All text & images licensed under CC BY 4.0 except where otherwise noted.\" Used for facts only: nothing copied. Reliability: opinion (expert blog). Used for: Apps must agree on vocabulary, location and shapes; data and apps not yet separated."@en .

<https://ruben.verborgh.org/blog/2022/12/30/lets-talk-about-pods/>
    dcterms:title "Ruben Verborgh, \"Let's talk about pods\"" ;
    dcterms:creator "personal blog" ;
    rdfs:comment "The page's footer: \"© 2012–2026 Ruben Verborgh All text & images licensed under CC BY 4.0 except where otherwise noted.\" Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"data and apps are not really separated yet\". Otherwise used for facts only. Reliability: opinion (expert blog). Used for: What a pod is; document-centric granularity limits."@en .

<https://rubenverborgh.github.io/RDF-for-Solid-2022/>
    dcterms:title "In order to simplify: A pragmatic introduction to the power of RDF for Solid" ;
    dcterms:creator "Ruben Verborgh, Ghent University – imec, talk slides" ;
    rdfs:comment "The slides: \"©2022 Ruben Verborgh – Except where otherwise noted, the content of these slides is licensed under Creative Commons Attribution 4.0.\" Used for facts only: nothing copied. Reliability: opinion (expert talk slides). Used for: Pragmatic RDF for Solid: one graph, many syntaxes."@en .

<https://sagroups.ieee.org/p3330>
    dcterms:title "IEEE P3330 Shape Expression Schemas Working Group" ;
    dcterms:creator "IEEE SA; PAR approved 2022-12-03; see also https://standards.ieee.org/ieee/3330/11119" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: IEEE P3330 standardising ShEx."@en .

schema:children
    dcterms:title "schema:children" ;
    dcterms:creator "schema.org" ;
    rdfs:comment "Schema.org's terms of service (https://schema.org/docs/terms.html): \"The Sponsors' copyrights in the schema are licensed to website publishers and other third parties under the Creative Commons Attribution-ShareAlike License (version 3.0).\" Used for facts only: nothing copied. Reliability: authoritative. Used for: \"A child of the person\", expected value Person."@en .

<https://schema.org/docs/datamodel.html>
    dcterms:title "Schema.org Data Model" ;
    dcterms:creator "schema.org" ;
    rdfs:comment "Schema.org's terms of service (https://schema.org/docs/terms.html): \"The Sponsors' copyrights in the schema are licensed to website publishers and other third parties under the Creative Commons Attribution-ShareAlike License (version 3.0).\" Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"closer to 'guidelines' than to formal rules\". Otherwise used for facts only. Reliability: authoritative. Used for: schema.org data model (types, properties, multiple types)."@en .

<https://schema.org/docs/faq.html>
    dcterms:title "Schema.org FAQ (\"http or https?\")" ;
    dcterms:creator "schema.org" ;
    rdfs:comment "Schema.org's terms of service (https://schema.org/docs/terms.html): \"The Sponsors' copyrights in the schema are licensed to website publishers and other third parties under the Creative Commons Attribution-ShareAlike License (version 3.0).\" Used for facts only: nothing copied. Reliability: authoritative. Used for: http vs https schema.org IRIs."@en .

<https://schema.org/docs/schemas.html>
    dcterms:title "Schemas (Organization of Schemas)" ;
    dcterms:creator "schema.org" ;
    rdfs:comment "Schema.org's terms of service (https://schema.org/docs/terms.html): \"The Sponsors' copyrights in the schema are licensed to website publishers and other third parties under the Creative Commons Attribution-ShareAlike License (version 3.0).\" Used for facts only: nothing copied. Reliability: authoritative. Used for: Where to browse schema.org types and find terms."@en .

schema:height
    dcterms:title "schema:height" ;
    dcterms:creator "schema.org" ;
    rdfs:comment "Schema.org's terms of service (https://schema.org/docs/terms.html): \"The Sponsors' copyrights in the schema are licensed to website publishers and other third parties under the Creative Commons Attribution-ShareAlike License (version 3.0).\" Used for facts only: nothing copied. Reliability: authoritative. Used for: Expected values Distance or QuantitativeValue, so a bare decimal misuses it."@en .

<https://semantic-web-journal.net/content/community-solid-server-supporting-research-development-evolving-ecosystem-0>
    dcterms:title "Van Herwegen & Verborgh, \"The Community Solid Server: Supporting Research & Development in an Evolving Ecosystem\"" ;
    dcterms:creator "Semantic Web journal" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: secondary (peer-reviewed). Used for: CSS architecture: Components.js, modular configuration, role in research."@en .

<https://shapetrees.github.io/specification/>
    dcterms:title "Shape Trees Specification (Draft CG Report)" ;
    dcterms:creator "Solid Community Group" ;
    rdfs:comment "The page's header: \"Copyright © 2020 W3C® (MIT, ERCIM, Keio, Beihang). W3C liability, trademark and permissive document license rules apply.\" The permissive licence is the W3C Software and Document License (https://www.w3.org/copyright/software-license-2023/): \"Permission to copy, modify, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted\", provided its notice is included \"on ALL copies of the work or portions thereof\". Used for facts only: nothing copied. Reliability: normative (CG draft). Used for: Shape trees: templates for resource trees and the shapes they must match. Round 3: still dated 2 September 2026."@en .

<https://shex.io/shex-semantics/>
    dcterms:title "Shape Expressions Language 2.1" ;
    dcterms:creator "W3C ShEx Community Group" ;
    rdfs:comment "The document's header: \"Copyright © 2019 the Contributors to the Shape Expressions Language 2.1 Specification, published by the Shape Expressions Community Group under the W3C Community Contributor License Agreement (CLA).\" The CLA (https://www.w3.org/community/about/process/cla/), section 2.1, has each contributor grant \"a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license … to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution\". Used for facts only: nothing copied. Reliability: normative (CG final report, not a W3C Rec). Used for: ShEx: shape maps, how SAI and LDO use ShEx."@en .

<https://solid.github.io/authorization-panel/acp-specification/>
    dcterms:title "ACP Editor's Draft" ;
    dcterms:creator "Solid CG authorization panel" ;
    rdfs:comment "The document's header: \"Copyright © 2022 W3C Solid Community Group.\" Its status section: \"This document was produced by a group operating under the W3C Community Contributor License Agreement (CLA).\" The CLA (https://www.w3.org/community/about/process/cla/), section 2.1, has each contributor grant \"a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license … to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution\". Used for facts only: nothing copied. Reliability: normative (editor's draft). Used for: Checked against the ACP report for later changes. Round 3: still dated 2022-09-29."@en .

<https://solid.github.io/data-interoperability-panel/primer/application.html>
    dcterms:title "Solid Application Interoperability — Application Primer" ;
    dcterms:creator "Solid Community Group" ;
    rdfs:comment "The document's header: \"Copyright © 2026 the Contributors to the Solid Application Interoperability - Application Primer, published by the Solid Community Group under the W3C Community Contributor License Agreement (CLA).\" The CLA (https://www.w3.org/community/about/process/cla/), section 2.1, has each contributor grant \"a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license … to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution\". Used for facts only: nothing copied. Reliability: authoritative (non-normative primer). Used for: How an app interacts with an authorization agent under SAI."@en .

<https://solid.github.io/data-interoperability-panel/specification/>
    dcterms:title "Solid Application Interoperability (Draft CG Report, v0.2)" ;
    dcterms:creator "Solid Community Group" ;
    rdfs:comment "The document's header: \"Copyright © 2026 the Contributors to the Solid Application Interoperability, published by the Solid Community Group under the W3C Community Contributor License Agreement (CLA).\" The CLA (https://www.w3.org/community/about/process/cla/), section 2.1, has each contributor grant \"a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license … to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution\". Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"relatively flat hierarchy\". Otherwise used for facts only. Reliability: normative (CG draft). Used for: Solid Application Interoperability: authorization agents, registries, access needs and grants, its ShEx data model, versioning drift (0.2 vs 0.1.0 on TR). Round 3: version 0.2, 10 September 2026."@en .

<https://solid.github.io/notifications/streaming-http-channel-2023>
    dcterms:title "StreamingHTTPChannel2023 (Draft Community Group Report)" ;
    dcterms:creator "W3C Solid Community Group" ;
    rdfs:comment "The document's header: \"Copyright © 2026 the Contributors to the Solid StreamingHTTPChannel2023, published by the Solid Community Group under the W3C Community Contributor License Agreement (CLA).\" The CLA (https://www.w3.org/community/about/process/cla/), section 2.1, has each contributor grant \"a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license … to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution\". Used for facts only: nothing copied. Reliability: normative (CG draft). Used for: A notification channel over the Fetch API; its status as a Draft CG Report."@en .

<https://solid.github.io/notifications/webhook-channel-2023>
    dcterms:title "WebhookChannel2023 (Draft Community Group Report v0.1)" ;
    dcterms:creator "W3C Solid Community Group" ;
    rdfs:comment "The document's header: \"Copyright © 2026 the Contributors to the Solid WebhookChannel2023, published by the Solid Community Group under the W3C Community Contributor License Agreement (CLA).\" The CLA (https://www.w3.org/community/about/process/cla/), section 2.1, has each contributor grant \"a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license … to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution\". Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"using identity provided as sender\". Otherwise used for facts only. Reliability: normative (CG draft). Used for: WebhookChannel2023: delivery to an endpoint and sender authentication. Round 3: its examples still use the singular notification/v1 context."@en .

<https://solid.github.io/notifications/websocket-channel-2023>
    dcterms:title "WebSocketChannel2023 (Editor's Draft)" ;
    dcterms:creator "W3C Solid Community Group" ;
    rdfs:comment "The document's header: \"Copyright © 2022 W3C Solid Community Group.\" Its status section: \"This document was produced by a group operating under the W3C Community Contributor License Agreement (CLA).\" The CLA (https://www.w3.org/community/about/process/cla/), section 2.1, has each contributor grant \"a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license … to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution\". Step 10.3 adapts its WebSocketChannel2023 subscription request example, which the CLA's licence covers. Reliability: normative (editor's draft). Used for: WebSocketChannel2023: required channel fields, receiveFrom, subprotocol handling. Round 3: the draft is dated 2022-12-27, version 0.1.0."@en .

<https://solid.github.io/solid-oidc/>
    dcterms:title "Solid-OIDC, Editor's Draft (Draft Community Group Report)" ;
    dcterms:creator "W3C Solid Community Group" ;
    rdfs:comment "The document's header: \"Copyright © 2026 the Contributors to the Solid-OIDC, published by the Solid Community Group under the W3C Community Contributor License Agreement (CLA).\" The CLA (https://www.w3.org/community/about/process/cla/), section 2.1, has each contributor grant \"a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license … to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution\". Step 7.5 copies its example ID token claims (the janedoe WebID), which the CLA's licence covers. Reliability: normative (editor's draft). Used for: Solid-OIDC as of 2026: why Solid needs more than plain OIDC, issuer discovery, RFC 9207 iss check, client ID documents, client credentials, http WebIDs as open point. Round 3: still dated 20 July 2026; §10.1 UMA is a SHOULD."@en .

<https://solid.github.io/solid-oidc/primer/>
    dcterms:title "Solid-OIDC Primer (Editor's Draft; also v0.1.0 at https://solidproject.org/TR/oidc-primer)" ;
    dcterms:creator "W3C Solid Community Group" ;
    rdfs:comment "The document's header: \"Copyright © 2026 the Contributors to the Solid-OIDC Primer, published by the Solid Community Group under the W3C Community Contributor License Agreement (CLA).\" The CLA (https://www.w3.org/community/about/process/cla/), section 2.1, has each contributor grant \"a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license … to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution\". Used for facts only: nothing copied. Reliability: authoritative (non-normative primer). Used for: Step-by-step login flow walkthrough (OP metadata, PKCE, DPoP) used to sequence Chapter 7."@en .

<https://solid.github.io/type-indexes/>
    dcterms:title "Type Indexes (v1.0.0, Editor's Draft)" ;
    dcterms:creator "Solid Community Group" ;
    rdfs:comment "The document's header: \"Copyright © 2022 W3C Solid Community Group.\" Its status section: \"This document was produced by a group operating under the W3C Community Contributor License Agreement (CLA).\" The CLA (https://www.w3.org/community/about/process/cla/), section 2.1, has each contributor grant \"a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license … to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution\". Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"the visibility of different data types in the Public Type Index\". Otherwise used for facts only. Reliability: normative (editor's draft). Used for: Type indexes: public/private indexes, solid:TypeRegistration, forClass/instance/instanceContainer, privacy of public registrations. Round 3: \"Editor's Draft, 2023-03-13\"."@en .

<https://solid.github.io/webid-profile/>
    dcterms:title "Solid WebID Profile, Draft Community Group Report" ;
    dcterms:creator "W3C Solid Community Group" ;
    rdfs:comment "The document's header: \"Copyright © 2022–2024 the Contributors to Solid WebID Profile, Version 1.0.0, published by the Solid Community Group under the W3C Community Contributor License Agreement (CLA).\" The CLA (https://www.w3.org/community/about/process/cla/), section 2.1, has each contributor grant \"a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license … to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution\". Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"using any predicates\". Otherwise used for facts only. Reliability: normative (CG draft). Used for: WebID profile document structure, pim:storage, solid:oidcIssuer, extended profile documents, preferences file. Round 3: version 1.0.0, 28 January 2026."@en .

<https://solidproject.org/about>
    dcterms:title "About Solid" ;
    dcterms:creator "Solid Project / ODI" ;
    rdfs:comment "The site's licence page (https://solidproject.org/license): \"Solid software is co-licensed under the MIT license and the Creative Commons Attribution 4.0 International (CC BY 4.0) license to cover both code and copy, respectively.\" Used for facts only: nothing copied. Reliability: authoritative. Used for: Official description of Solid: pods, the rucksack metaphor, people/apps/AI agents as data users."@en .

<https://solidproject.org/apps>
    dcterms:title "Solid Apps" ;
    dcterms:creator "Solid Project / ODI" ;
    rdfs:comment "The site's licence page (https://solidproject.org/license): \"Solid software is co-licensed under the MIT license and the Creative Commons Attribution 4.0 International (CC BY 4.0) license to cover both code and copy, respectively.\" Used for facts only: nothing copied. Reliability: authoritative. Used for: App catalogue. Round 3: submission by email to the ODI and the listing criteria."@en .

<https://solidproject.org/ED/protocol>
    dcterms:title "Solid Protocol, Editor's Draft (v0.12.0)" ;
    dcterms:creator "W3C Solid Community Group" ;
    rdfs:comment "The document's header: \"Copyright © 2019–2024 the Contributors to Solid Protocol, Editor’s Draft, under the W3C Community Contributor License Agreement (CLA). A human-readable summary is available. All code snippets are in the public domain, CC0.\" The CLA (https://www.w3.org/community/about/process/cla/), section 2.1, has each contributor grant \"a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license … to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution\". Steps 3.10 and 6.7 adapt its N3 Patch example (the _:rename patch), a code snippet in the public domain by the line quoted. Reliability: normative (editor's draft, not endorsed). Used for: What v0.12 changes: mandatory Last-Modified, N3 Patch deletes without blank nodes. Round 2: blank nodes allowed in inserts but not deletes. Round 3: still dated 2026-09-09; blank-node and Last-Modified rules re-read."@en .

<https://solidproject.org/TR/>
    dcterms:title "Solid Technical Reports" ;
    dcterms:creator "W3C Solid Community Group" ;
    rdfs:comment "The page states no licence; its footer reads \"Copyright © 2019–2024 W3C Solid Community Group\"; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: Index of Solid CG reports and their maturity; Notification Channel Type Registry; still links the old Shape Trees address. Round 3: index modified 2026-04-27; still labels all three channel types \"Editor's Draft\" and SAI \"v0.1.0\"."@en .

<https://solidproject.org/TR/2021/protocol-20211217>
    dcterms:title "Solid Protocol, Version 0.9.0" ;
    dcterms:creator "W3C Solid Community Group" ;
    rdfs:comment "The document's header: \"Copyright © 2019–2021 W3C Solid Community Group.\" Its status section: \"This document was produced by a group operating under the W3C Community Contributor License Agreement (CLA).\" The CLA (https://www.w3.org/community/about/process/cla/), section 2.1, has each contributor grant \"a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license … to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution\". Used for facts only: nothing copied. Reliability: normative (superseded). Used for: Version history: SPARQL Update never required from v0.9 on."@en .

<https://solidproject.org/TR/2022/protocol-20221231>
    dcterms:title "Solid Protocol, Version 0.10.0" ;
    dcterms:creator "W3C Solid Community Group" ;
    rdfs:comment "The document's header: \"Copyright © 2019–2022 W3C Solid Community Group.\" Its status section: \"This document was produced by a group operating under the W3C Community Contributor License Agreement (CLA).\" The CLA (https://www.w3.org/community/about/process/cla/), section 2.1, has each contributor grant \"a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license … to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution\". Used for facts only: nothing copied. Reliability: normative (superseded). Used for: Version history: what v0.10 still required (POST with LDP type link, SPARQL Update not required)."@en .

<https://solidproject.org/TR/acp>
    dcterms:title "Access Control Policy (ACP), Version 0.9.0" ;
    dcterms:creator "W3C Solid Community Group" ;
    rdfs:comment "The document's header: \"Copyright © 2022 W3C Solid Community Group.\" Its status section: \"This document was produced by a group operating under the W3C Community Contributor License Agreement (CLA).\" The CLA (https://www.w3.org/community/about/process/cla/), section 2.1, has each contributor grant \"a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license … to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution\". Used for facts only: nothing copied. Reliability: normative (published by the Solid CG as an Editor's Draft, not a Draft CG Report). Used for: Access Control Policy: ACRs, policies, matchers, allOf/anyOf/noneOf, deny-wins, client and issuer matching. Its status section says the CG \"published [it] as an Editor's Draft\". Round 3: status \"Editor's Draft\" re-read."@en .

<https://solidproject.org/TR/notifications-protocol>
    dcterms:title "Solid Notifications Protocol, Version 0.3.0" ;
    dcterms:creator "W3C Solid Community Group" ;
    rdfs:comment "The document's header: \"Copyright © 2021–2024 the Contributors to Solid Protocol, Version 0.3.0, published by the Solid Community Group under the W3C Community Contributor License Agreement (CLA).\" The CLA (https://www.w3.org/community/about/process/cla/), section 2.1, has each contributor grant \"a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license … to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution\". Step 10.2 copies an excerpt of its storage description example (the subscription service), which the CLA's licence covers. Reliability: normative (CG draft). Used for: Solid Notifications Protocol: discovery, subscription and channel requests, notification shape, Read requirement on topics."@en .

<https://solidproject.org/TR/oidc>
    dcterms:title "Solid-OIDC, Version 0.1.0" ;
    dcterms:creator "W3C Solid Community Group" ;
    rdfs:comment "The document's header: \"Copyright © 2019–2022 W3C Solid Community Group.\" Its status section: \"This document was produced by a group operating under the W3C Community Contributor License Agreement (CLA).\" The CLA (https://www.w3.org/community/about/process/cla/), section 2.1, has each contributor grant \"a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license … to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution\". Used for facts only: nothing copied. Reliability: normative (CG report v0.1.0, 2022). Used for: Solid-OIDC as published: DPoP-bound tokens, webid claim, client identifiers; the \"still 0.1.0\" maturity point."@en .

<https://solidproject.org/TR/protocol>
    dcterms:title "Solid Protocol, Version 0.11.0 (Draft Community Group Report)" ;
    dcterms:creator "W3C Solid Community Group" ;
    rdfs:comment "The document's header: \"Copyright © 2019–2024 the Contributors to Solid Protocol, Version 0.11.0, published by the Solid Community Group under the W3C Community Contributor License Agreement (CLA).\" The CLA (https://www.w3.org/community/about/process/cla/), section 2.1, has each contributor grant \"a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license … to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution\". Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"it is not a W3C Standard nor is it on the W3C Standards Track\", \"connects a set of specifications that, together, provide applications with secure and permissioned access to externally stored data in an interoperable way\", \"implicitly has control over all resources in a storage\", \"A URI allocated to a WebID in a Solid storage does not imply that the WebID is the storage owner\", \"to avoid instant propagation of changes all the way to the root container\", \"Paths ending with a slash denote a container resource\", \"There is a 1-1 correspondence between containment triples and relative reference within the path name hierarchy.\", \"it is not possible to create orphan resources\", \"descriptive metadata, authorization conditions, data shape constraints, digital rights or provenance\", \"MUST NOT happen via CORS\", \"Servers MUST conform to either or both\". Otherwise used for facts only. Reliability: normative (CG draft, not W3C standards track). Used for: The backbone of the course: pods, storages, containers, slash semantics, auxiliary resources, Link headers, content negotiation, PUT/POST/PATCH/DELETE rules, N3 Patch, status codes, WAC-or-ACP requirement, WebID-TLS vs Solid-OIDC, and the \"not on the W3C Standards Track\" status. Round 2: §N3 Patch quoted for blank nodes and 422. Round 3: version, date and \"not on the W3C Standards Track\" re-read."@en .

<https://solidproject.org/TR/wac>
    dcterms:title "Web Access Control, Version 1.0.0 (Draft Community Group Report)" ;
    dcterms:creator "W3C Solid Community Group" ;
    rdfs:comment "The document's header: \"Copyright © 2021–2024 the Contributors to Web Access Control, Version 1.0.0, published by the Solid Community Group under the W3C Community Contributor License Agreement (CLA).\" The CLA (https://www.w3.org/community/about/process/cla/), section 2.1, has each contributor grant \"a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license … to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution\". Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"Clients MUST NOT derive the URI of the ACL resource through string operations on the URI of the resource.\", \"Having acl:Control does not imply that the agent has acl:Read or acl:Write access to the resource itself.\", \"MUST NOT cause increased access\", \"is not intended as client identification\". Otherwise used for facts only. Reliability: normative (CG draft). Used for: Web Access Control: ACL resources, modes and their implications, acl:agent/agentClass/agentGroup/origin, inheritance via acl:default, effective ACL, WAC-Allow header, \"not client identification\" warning. Round 3: version and date re-read."@en .

<https://solidproject.org/users/get-a-pod>
    dcterms:title "Get a Pod" ;
    dcterms:creator "Solid Project / ODI" ;
    rdfs:comment "The site's licence page (https://solidproject.org/license): \"Solid software is co-licensed under the MIT license and the Creative Commons Attribution 4.0 International (CC BY 4.0) license to cover both code and copy, respectively.\" Used for facts only: nothing copied. Reliability: authoritative. Used for: List of pod providers."@en .

<https://soukai.js.org/>
    dcterms:title "Soukai" ;
    dcterms:creator "Noel De Martin" ;
    rdfs:comment "The page states no licence; its footer reads \"Copyright © 2018-present Noel De Martin\"; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: Soukai models library."@en .

<https://soukai.js.org/guide/advanced/interoperability.html>
    dcterms:title "Soukai guide: Interoperability" ;
    dcterms:creator "Soukai / Noel De Martin" ;
    rdfs:comment "The page states no licence; its footer reads \"Copyright © 2018-present Noel De Martin\"; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: Soukai's approach to interoperability across vocabularies."@en .

<https://strathprints.strath.ac.uk/92706>
    dcterms:title "Forsyth & Horne, \"Clark-Wilson policies in ACP: controlling information flow between Solid apps\"" ;
    dcterms:creator "University of Strathclyde / CEUR-WS Vol. 3947, Solid Symposium 2024 proceedings" ;
    rdfs:comment "The record: \"License: Creative Commons Attribution 4.0\" (http://creativecommons.org/licenses/by/4.0/). Used for facts only: nothing copied. Reliability: secondary (peer-reviewed). Used for: Restricting information flow between apps with ACP; apps inheriting full user access."@en .

<https://thenextweb.com/news/web-inventor-tim-berners-lee-screw-web3-my-decentralized-internet-doesnt-need-blockchain>
    dcterms:title "Web inventor Tim Berners-Lee: Screw Web3 — my decentralized internet doesn't need blockchain" ;
    dcterms:creator "The Next Web" ;
    rdfs:comment "The page states no licence; its footer reads \"Copyright © 2006—2026, Cogneve, INC\"; it is treated as all rights reserved. Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"Nope\", \"it just doesn't work\". Otherwise used for facts only. Reliability: secondary (press interview). Used for: Berners-Lee on Web3 and blockchain."@en .

<https://theodi.org/news-and-events/news/odi-and-solid-come-together-to-give-individuals-greater-control-over-personal-data/>
    dcterms:title "ODI and Solid come together to give individuals greater control over personal data" ;
    dcterms:creator "Open Data Institute" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: ODI becomes Solid's steward (October 2024)."@en .

<https://url.spec.whatwg.org/>
    dcterms:title "URL Standard" ;
    dcterms:creator "WHATWG Living Standard" ;
    rdfs:comment "The standard: \"Copyright © WHATWG (Apple, Google, Mozilla, Microsoft). This work is licensed under a Creative Commons Attribution 4.0 International License.\" Used for facts only: nothing copied. Reliability: normative (WHATWG Living Standard). Used for: Browser view: \"URL\" as the single term."@en .

<https://w3c-cg.github.io/N3/spec/>
    dcterms:title "Notation3 Language" ;
    dcterms:creator "W3C Notation3 (N3) Community Group" ;
    rdfs:comment "The document's status section: \"Please note that under the W3C Community Contributor License Agreement (CLA) there is a limited opt-out and other conditions apply.\" The CLA (https://www.w3.org/community/about/process/cla/), section 2.1, has each contributor grant \"a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license … to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution\". Used for facts only: nothing copied. Reliability: normative (CG draft, not standards track). Used for: Current N3 language spec cited by the Solid Protocol; text/n3 media type."@en .

<https://webfoundation.org/2019/03/web-birthday-30/>
    dcterms:title "30 years on, what's next #ForTheWeb?" ;
    dcterms:creator "Tim Berners-Lee / World Wide Web Foundation" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: opinion (founder). Used for: Critique of ad-based models."@en .

<https://www.dublincore.org/specifications/dublin-core/dcmi-terms/>
    dcterms:title "DCMI Metadata Terms" ;
    dcterms:creator "DCMI Recommendation" ;
    rdfs:comment "The page's footer: \"Unless indicated otherwise, DCMI documents are licensed under a Creative Commons Attribution 4.0 International License.\" Used for facts only: nothing copied. Reliability: normative (DCMI Recommendation). Used for: Dublin Core terms (title, created, creator); dcam:rangeIncludes vs rdfs:range."@en .

<https://www.ietf.org/archive/id/draft-ietf-oauth-client-id-metadata-document-02.html>
    dcterms:title "OAuth Client ID Metadata Document, draft-ietf-oauth-client-id-metadata-document-02" ;
    dcterms:creator "IETF OAuth WG" ;
    rdfs:comment "The document's copyright notice: \"Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document.\" No licence to modify its text outside the IETF is given. Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"largely inspired by\". Otherwise used for facts only. Reliability: normative (IETF Internet-Draft). Used for: OAuth Client ID Metadata Documents: client IDs as URLs, what they do and do not prove."@en .

<https://www.inrupt.com/blog/inrupt-gives-support-as-the-open-data-institute-commits-to-the-solid-movement>
    dcterms:title "Inrupt gives support as the Open Data Institute commits to the Solid movement" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; its footer reads \"© 2020-2025 Inrupt, Inc\"; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: opinion (vendor). Used for: Inrupt as a vendor in the governance landscape."@en .

<https://www.inrupt.com/case-study/bbc-embraces-future-of-personal-data-access-and-consent>
    dcterms:title "The BBC shows its audience the future of personal data access and consent" ;
    dcterms:creator "Inrupt, c. 2022" ;
    rdfs:comment "The page states no licence; its footer reads \"© 2020-2025 Inrupt, Inc\"; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: opinion (vendor case study). Used for: BBC personal data pilot."@en .

<https://www.npmjs.com/package/@inrupt/solid-client-authn-browser/v/5.0.1>
    dcterms:title "@inrupt/solid-client-authn-browser 5.0.1: Session (dist)" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (source code). Used for: After sessionExpired the session is forgotten, so restorePreviousSession can't restore it; login() passes prompt on (default \"consent\")."@en .

<https://www.npmjs.com/package/@inrupt/solid-client-authn-core/v/5.0.1>
    dcterms:title "@inrupt/solid-client-authn-core 5.0.1: buildAuthenticatedFetch (dist)" ;
    dcterms:creator "Inrupt" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (source code). Used for: The token is refreshed 5 s before it expires; a refused refresh fires error and sessionExpired."@en .

<https://www.rfc-editor.org/rfc/rfc3986>
    dcterms:title "RFC 3986: Uniform Resource Identifier (URI): Generic Syntax" ;
    dcterms:creator "IETF, Berners-Lee/Fielding/Masinter" ;
    rdfs:comment "The document's copyright notice: \"Copyright (C) The Internet Society (2005). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.\" No licence to modify its text outside the IETF is given. Used for facts only: nothing copied. Reliability: normative (IETF RFC). Used for: URI generic syntax, fragments, relative reference resolution."@en .

<https://www.rfc-editor.org/rfc/rfc3987>
    dcterms:title "RFC 3987: Internationalized Resource Identifiers (IRIs)" ;
    dcterms:creator "IETF, Dürst & Suignard" ;
    rdfs:comment "The document's copyright notice: \"Copyright (C) The Internet Society (2005). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.\" No licence to modify its text outside the IETF is given. Used for facts only: nothing copied. Reliability: normative (IETF RFC). Used for: IRIs and their mapping to URIs (percent-encoding)."@en .

<https://www.rfc-editor.org/rfc/rfc5023>
    dcterms:title "RFC 5023: The Atom Publishing Protocol (§9.7 defines the Slug header, which LDP and Solid v0.10 reuse)" ;
    dcterms:creator "IETF, Proposed Standard" ;
    rdfs:comment "The document's copyright notice: \"Copyright (C) The IETF Trust (2007). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.\" No licence to modify its text outside the IETF is given. Used for facts only: nothing copied. Reliability: normative (IETF RFC). Used for: Slug header origin."@en .

<https://www.rfc-editor.org/rfc/rfc5789>
    dcterms:title "RFC 5789: PATCH Method for HTTP (§2: \"The server MUST apply the entire set of changes atomically\")" ;
    dcterms:creator "IETF, Proposed Standard" ;
    rdfs:comment "The document's copyright notice: \"Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document.\" No licence to modify its text outside the IETF is given. Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"apply the entire set of changes atomically\". Otherwise used for facts only. Reliability: normative (IETF RFC). Used for: PATCH atomicity per document."@en .

<https://www.rfc-editor.org/rfc/rfc6455>
    dcterms:title "RFC 6455: The WebSocket Protocol (§4.1 and §11.3.4, Sec-WebSocket-Protocol token syntax)" ;
    dcterms:creator "IETF" ;
    rdfs:comment "The document's copyright notice: \"Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document.\" No licence to modify its text outside the IETF is given. Used for facts only: nothing copied. Reliability: normative (IETF RFC). Used for: WebSocket subprotocol token syntax (why solid-0.1 style values fail in browsers)."@en .

<https://www.rfc-editor.org/rfc/rfc6749>
    dcterms:title "RFC 6749: The OAuth 2.0 Authorization Framework" ;
    dcterms:creator "IETF" ;
    rdfs:comment "The document's copyright notice: \"Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document.\" No licence to modify its text outside the IETF is given. Used for facts only: nothing copied. Reliability: normative (IETF RFC). Used for: §5.2: what an invalid_grant error means."@en .

<https://www.rfc-editor.org/rfc/rfc7636>
    dcterms:title "RFC 7636: Proof Key for Code Exchange by OAuth Public Clients (PKCE)" ;
    dcterms:creator "IETF" ;
    rdfs:comment "The document's copyright notice: \"Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document.\" No licence to modify its text outside the IETF is given. Used for facts only: nothing copied. Reliability: normative (IETF RFC). Used for: PKCE: code verifier/challenge against intercepted authorization codes."@en .

<https://www.rfc-editor.org/rfc/rfc8288>
    dcterms:title "RFC 8288: Web Linking" ;
    dcterms:creator "IETF, Proposed Standard" ;
    rdfs:comment "The document's copyright notice: \"Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document.\" No licence to modify its text outside the IETF is given. Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"a typed connection between two resources\". Otherwise used for facts only. Reliability: normative (IETF RFC). Used for: Web Linking: Link header context, rel and target."@en .

<https://www.rfc-editor.org/rfc/rfc9110>
    dcterms:title "RFC 9110: HTTP Semantics (§8.8 validators, §13.1 conditional requests)" ;
    dcterms:creator "IETF" ;
    rdfs:comment "The document's copyright notice: \"Copyright (c) 2022 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document.\" No licence to modify its text outside the IETF is given. Used for facts only: nothing copied. Reliability: normative (IETF RFC). Used for: HTTP semantics: Accept and q-values, 406, ETags and validators, conditional requests (If-Match, If-None-Match), 304 and 412. Round 3: §15.5.14, \"413 Content Too Large\"."@en .

<https://www.rfc-editor.org/rfc/rfc9112>
    dcterms:title "RFC 9112: HTTP/1.1" ;
    dcterms:creator "IETF" ;
    rdfs:comment "The document's copyright notice: \"Copyright (c) 2022 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document.\" No licence to modify its text outside the IETF is given. Used for facts only: nothing copied. Reliability: normative (IETF RFC). Used for: §5.2: senders must not fold header lines, so a CSP header stays on one line."@en .

<https://www.rfc-editor.org/rfc/rfc9207>
    dcterms:title "RFC 9207: OAuth 2.0 Authorization Server Issuer Identification" ;
    dcterms:creator "IETF" ;
    rdfs:comment "The document's copyright notice: \"Copyright (c) 2022 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document.\" No licence to modify its text outside the IETF is given. Used for facts only: nothing copied. Reliability: normative (IETF RFC). Used for: iss parameter against mix-up attacks."@en .

<https://www.rfc-editor.org/rfc/rfc9449>
    dcterms:title "RFC 9449: OAuth 2.0 Demonstrating Proof of Possession (DPoP)" ;
    dcterms:creator "IETF" ;
    rdfs:comment "The document's copyright notice: \"Copyright (c) 2023 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document.\" No licence to modify its text outside the IETF is given. Used for facts only: nothing copied. Reliability: normative (IETF RFC). Used for: DPoP: proof JWTs, htm/htu, cnf.jkt binding."@en .

<https://www.rfc-editor.org/rfc/rfc9700>
    dcterms:title "RFC 9700: Best Current Practice for OAuth 2.0 Security" ;
    dcterms:creator "IETF, BCP 240" ;
    rdfs:comment "The document's copyright notice: \"Copyright (c) 2025 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document.\" No licence to modify its text outside the IETF is given. Used for facts only: nothing copied. Reliability: normative (IETF BCP). Used for: §4.14: public clients' refresh tokens must be sender-constrained or rotated; expiry and revocation."@en .

<https://www.w3.org/2005/Incubator/webid/spec/identity/>
    dcterms:title "WebID 1.0: Web Identity and Discovery" ;
    dcterms:creator "W3C WebID Community Group" ;
    rdfs:comment "The document's header: \"Copyright © 2010-2014 the Contributors to the WebID 1.0 Specification, published by the WebID Community Group under the W3C Community Contributor License Agreement (CLA).\" The CLA (https://www.w3.org/community/about/process/cla/), section 2.1, has each contributor grant \"a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license … to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution\". Used for facts only: nothing copied. Reliability: normative (CG draft, 2014). Used for: WebID definition (an HTTP(S) URI denoting an agent), Turtle as required profile format, hash vs 303 URIs."@en .

<https://www.w3.org/2005/Incubator/webid/spec/tls/>
    dcterms:title "WebID Authentication over TLS (WebID-TLS)" ;
    dcterms:creator "W3C WebID Community Group" ;
    rdfs:comment "The document's header: \"Copyright © 2010-2014 the Contributors to the WebID-TLS Specification, published by the WebID Community Group under the W3C Community Contributor License Agreement (CLA).\" The CLA (https://www.w3.org/community/about/process/cla/), section 2.1, has each contributor grant \"a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license … to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution\". Used for facts only: nothing copied. Reliability: normative (CG draft, superseded in Solid). Used for: History: WebID-TLS and browser client certificates."@en .

<https://www.w3.org/2024/09/linked-web-storage-wg-charter>
    dcterms:title "Linked Web Storage Working Group Charter" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The page's header: \"Copyright © 2024 World Wide Web Consortium. W3C® liability, trademark and permissive document license rules apply.\" The permissive licence is the W3C Software and Document License (https://www.w3.org/copyright/software-license-2023/): \"Permission to copy, modify, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted\", provided its notice is included \"on ALL copies of the work or portions thereof\". Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"sometimes at the price of all past data\", \"enable the development of web applications where data storage, entity authentication, access control, and application provider are all loosely coupled\", \"at least two independent interoperable implementations of every feature\". Otherwise used for facts only. Reliability: authoritative. Used for: LWS WG mission (loosely coupled storage, authentication, access control, app provider), deliverables, two-implementations rule, Solid Protocol as input."@en .

<https://www.w3.org/2026/09/14-lws-minutes.html>
    dcterms:title "LWS WG minutes, 14 September 2026" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: LWS WG minutes: charter extension and rechartering. Round 3: \"administrative extension\" and the refinement and voting periods."@en .

<https://www.w3.org/2026/09/21-lws-minutes.html>
    dcterms:title "LWS WG minutes, 21 September 2026" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The page states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative. Used for: LWS WG minutes: rechartering continued. Round 3: \"charter refinement period, until Oct 5th\"."@en .

<https://www.w3.org/community/solid/>
    dcterms:title "Solid Community Group" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The page's footer: \"Copyright © 2026 World Wide Web Consortium. W3C® liability, trademark and permissive license rules apply.\" Its \"permissive license\" link leads to the W3C Document License (https://www.w3.org/copyright/document-license/), which allows copying unmodified but grants \"No right to create modifications or derivatives of W3C documents\". Used for facts only: nothing copied. Reliability: authoritative. Used for: What a W3C Community Group is (\"proposed and run by the community\")."@en .

<https://www.w3.org/DesignIssues/CloudStorage.html>
    dcterms:title "Socially Aware Cloud Storage (Design Issues)" ;
    dcterms:creator "Tim Berners-Lee / W3C" ;
    rdfs:comment "The page carries no licence or copyright notice; it is treated as all rights reserved. Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"separates the market for storage from the market for applications\". Otherwise used for facts only. Reliability: opinion (founder's design note). Used for: Separating storage and app markets."@en .

<https://www.w3.org/DesignIssues/LinkedData.html>
    dcterms:title "Linked Data (Design Issues)" ;
    dcterms:creator "Tim Berners-Lee / W3C" ;
    rdfs:comment "The page carries no licence or copyright notice; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (founder's design note). Used for: The four Linked Data rules and the 5-star scale."@en .

<https://www.w3.org/DesignIssues/ReadWriteLinkedData.html>
    dcterms:title "Read-Write Linked Data (Design Issues)" ;
    dcterms:creator "Tim Berners-Lee / W3C" ;
    rdfs:comment "The page carries no licence or copyright notice; it is treated as all rights reserved. Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"a collaborative space\", \"one does not want a data wiki in which anyone can write\". Otherwise used for facts only. Reliability: opinion (founder's design note). Used for: Read-write Linked Data; \"not a data wiki in which anyone can write\"."@en .

<https://www.w3.org/groups/wg/lws/charters/active/>
    dcterms:title "Linked Web Storage Working Group Charter (active, with extension)" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The page's header: \"Copyright © 2024 World Wide Web Consortium. W3C® liability, trademark and permissive document license rules apply.\" The permissive licence is the W3C Software and Document License (https://www.w3.org/copyright/software-license-2023/): \"Permission to copy, modify, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted\", provided its notice is included \"on ALL copies of the work or portions thereof\". Used for facts only: nothing copied. Reliability: authoritative. Used for: Active LWS charter: planned FPWD/Recommendation dates, extension to 2027-01-08, main input documents. Round 3: group page \"Chartered until 8 January 2027\"."@en .

<https://www.w3.org/groups/wg/rdf-star/publications/>
    dcterms:title "RDF & SPARQL Working Group — Publications" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The page's footer: \"Copyright © 2026 World Wide Web Consortium. W3C® liability, trademark and permissive license rules apply.\" Its \"permissive license\" link leads to the W3C Document License (https://www.w3.org/copyright/document-license/), which allows copying unmodified but grants \"No right to create modifications or derivatives of W3C documents\". Used for facts only: nothing copied. Reliability: authoritative. Used for: Publication status of RDF 1.2 documents."@en .

<https://www.w3.org/news/2026/first-public-working-draft-linked-web-storage-protocol-1-0/>
    dcterms:title "First Public Working Draft: Linked Web Storage Protocol 1.0" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The page's footer: \"Copyright © 2026 World Wide Web Consortium. W3C® liability, trademark and permissive license rules apply.\" Its \"permissive license\" link leads to the W3C Document License (https://www.w3.org/copyright/document-license/), which allows copying unmodified but grants \"No right to create modifications or derivatives of W3C documents\". Used for facts only: nothing copied. Reliability: authoritative. Used for: Date of the LWS Protocol FPWD (31 March 2026)."@en .

<https://www.w3.org/news/2026/first-public-working-drafts-for-the-linked-web-storage-lws-1-0-authentication-suite/>
    dcterms:title "First Public Working Drafts for the Linked Web Storage (LWS) 1.0 Authentication Suite" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The page's footer: \"Copyright © 2026 World Wide Web Consortium. W3C® liability, trademark and permissive license rules apply.\" Its \"permissive license\" link leads to the W3C Document License (https://www.w3.org/copyright/document-license/), which allows copying unmodified but grants \"No right to create modifications or derivatives of W3C documents\". Used for facts only: nothing copied. Reliability: authoritative. Used for: LWS authentication suite FPWDs (23 April 2026)."@en .

<https://www.w3.org/ns/auth/acl>
    dcterms:title "ACL ontology (acl: namespace document)" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The namespace document states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (namespace document). Used for: acl: terms, Write implies Append, acl:defaultForNew marked obsolete."@en .

<https://www.w3.org/ns/pim/space>
    dcterms:title "Workspace (PIM space) ontology" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The namespace document states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (namespace document). Used for: pim: terms: pim:storage, pim:Storage, preferencesFile."@en .

<https://www.w3.org/ns/solid/oidc-context.jsonld>
    dcterms:title "Solid-OIDC JSON-LD context" ;
    dcterms:creator "W3C Solid CG" ;
    rdfs:comment "The namespace document states no licence; it is treated as all rights reserved. Used for facts only: nothing copied. Reliability: authoritative (JSON-LD context). Used for: Solid-OIDC context for client ID documents."@en .

<https://www.w3.org/ns/solid/terms>
    dcterms:title "Solid Terms vocabulary" ;
    dcterms:creator "Solid CG / W3C namespace, terms dated 2015–2024" ;
    rdfs:comment "The vocabulary document states dc:license <https://creativecommons.org/publicdomain/zero/1.0/> (CC0 1.0 Universal). Step 4.12 copies the vocabulary's description of solid:inbox, ten lines of Turtle, verbatim. Reliability: authoritative (namespace document). Used for: solid: terms: oidcIssuer, type index classes, N3 Patch terms (InsertDeletePatch, where/inserts/deletes)."@en .

<https://www.w3.org/standards/history/lws10-authn-openid/>
    dcterms:title "LWS authentication suites and vocabulary, publication histories" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The page's footer: \"Copyright © 2026 World Wide Web Consortium. W3C® liability, trademark and permissive license rules apply.\" Its \"permissive license\" link leads to the W3C Document License (https://www.w3.org/copyright/document-license/), which allows copying unmodified but grants \"No right to create modifications or derivatives of W3C documents\". Used for facts only: nothing copied. Reliability: authoritative. Used for: Draft dates of the OpenID Connect, SAML 2.0 and self-signed identity suites; the did:key suite discontinued on 2026-09-29; the vocabulary Draft Note of 2026-07-14."@en .

<https://www.w3.org/standards/history/lws10-core/>
    dcterms:title "Linked Web Storage Protocol 1.0, publication history" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The page's footer: \"Copyright © 2026 World Wide Web Consortium. W3C® liability, trademark and permissive license rules apply.\" Its \"permissive license\" link leads to the W3C Document License (https://www.w3.org/copyright/document-license/), which allows copying unmodified but grants \"No right to create modifications or derivatives of W3C documents\". Used for facts only: nothing copied. Reliability: authoritative. Used for: LWS Protocol publication history (FPWD 2026-03-31, latest WD 2026-10-05). Round 3: loaded: 15 publications, the FPWD and 14 WDs (2026-06-05 to 2026-10-05)."@en .

<https://www.w3.org/standards/history/rdf12-concepts/>
    dcterms:title "W3C publication histories for RDF 1.2 Concepts, RDF 1.2 Semantics, SPARQL 1.2 Query and SHACL 1.2 Core" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The page's footer: \"Copyright © 2026 World Wide Web Consortium. W3C® liability, trademark and permissive license rules apply.\" Its \"permissive license\" link leads to the W3C Document License (https://www.w3.org/copyright/document-license/), which allows copying unmodified but grants \"No right to create modifications or derivatives of W3C documents\". Used for facts only: nothing copied. Reliability: authoritative. Used for: Latest publication of each RDF-family draft (CR 2026-04-07, CRD 2026-09-24, WD 2026-10-04, WD 2026-09-18)."@en .

<https://www.w3.org/TeamSubmission/n3/>
    dcterms:title "Notation3 (N3): A readable RDF syntax" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2008 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Used for facts only: nothing copied. Reliability: authoritative (W3C Team Submission, not a standard). Used for: Notation3 background for N3 Patch."@en .

<https://www.w3.org/TR/2026/WD-lws10-authn-ssi-cid-20260423/>
    dcterms:title "LWS 1.0 Authentication Suite: Self-signed Identity using Controlled Identifiers (FPWD)" ;
    dcterms:creator "W3C LWS WG" ;
    rdfs:comment "The page's header: \"Copyright © 2026 World Wide Web Consortium. W3C® liability, trademark and permissive document license rules apply.\" The permissive licence is the W3C Software and Document License (https://www.w3.org/copyright/software-license-2023/): \"Permission to copy, modify, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted\", provided its notice is included \"on ALL copies of the work or portions thereof\". Used for facts only: nothing copied. Reliability: normative (W3C FPWD). Used for: LWS authentication suite: self-signed identity with controlled identifiers, no identity provider needed."@en .

<https://www.w3.org/TR/activitystreams-vocabulary/>
    dcterms:title "Activity Vocabulary" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The page's header: \"Copyright © 2017 Activity Streams Working Group,IBM & W3C® (MIT, ERCIM, Keio, Beihang). W3C liability, trademark and permissive document license rules apply.\" The permissive licence is the W3C Software and Document License (https://www.w3.org/copyright/software-license-2023/): \"Permission to copy, modify, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted\", provided its notice is included \"on ALL copies of the work or portions thereof\". Used for facts only: nothing copied. Reliability: normative (W3C Recommendation). Used for: Activity Streams vocabulary used in notifications (as:Update etc.)."@en .

<https://www.w3.org/TR/cooluris/>
    dcterms:title "Cool URIs for the Semantic Web" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2008 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Used for facts only: nothing copied. Reliability: authoritative (W3C Interest Group Note). Used for: Hash vs 303 URIs, documents vs things, why WebIDs end in #me, content negotiation."@en .

<https://www.w3.org/TR/dwbp/>
    dcterms:title "Data on the Web Best Practices" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2017 W3C® (MIT, ERCIM, Keio, Beihang). W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"Use terms from shared vocabularies, preferably standardized ones\". Otherwise used for facts only. Reliability: normative (W3C Recommendation). Used for: BP15: reuse shared vocabularies."@en .

<https://www.w3.org/TR/json-ld11-api/>
    dcterms:title "JSON-LD 1.1 Processing Algorithms and API" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The page's header: \"Copyright © 2010-2020 W3C® (MIT, ERCIM, Keio, Beihang). W3C liability, trademark and permissive document license rules apply.\" The permissive licence is the W3C Software and Document License (https://www.w3.org/copyright/software-license-2023/): \"Permission to copy, modify, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted\", provided its notice is included \"on ALL copies of the work or portions thereof\". Used for facts only: nothing copied. Reliability: normative (W3C Recommendation). Used for: JSON-LD number/boolean round-tripping to xsd:double/integer/boolean."@en .

<https://www.w3.org/TR/json-ld11-framing/>
    dcterms:title "JSON-LD 1.1 Framing" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The page's header: \"Copyright © 2010-2020 W3C® (MIT, ERCIM, Keio, Beihang). W3C liability, trademark and permissive document license rules apply.\" The permissive licence is the W3C Software and Document License (https://www.w3.org/copyright/software-license-2023/): \"Permission to copy, modify, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted\", provided its notice is included \"on ALL copies of the work or portions thereof\". Used for facts only: nothing copied. Reliability: normative (W3C Recommendation). Used for: Framing as \"query by example\" that forces a tree layout; the frame's context compacts the output."@en .

<https://www.w3.org/TR/json-ld11/>
    dcterms:title "JSON-LD 1.1" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The page's header: \"Copyright © 2010-2020 W3C® (MIT, ERCIM, Keio, Beihang). W3C liability, trademark and permissive document license rules apply.\" The permissive licence is the W3C Software and Document License (https://www.w3.org/copyright/software-license-2023/): \"Permission to copy, modify, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted\", provided its notice is included \"on ALL copies of the work or portions thereof\". Used for facts only: nothing copied. Reliability: normative (W3C Recommendation). Used for: JSON-LD: @context, @id, @type, compaction, Turtle/JSON-LD equivalence."@en .

<https://www.w3.org/TR/ldn/>
    dcterms:title "Linked Data Notifications" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The page's header: \"Copyright © 2017 W3C® (MIT, ERCIM, Keio, Beihang). W3C liability, trademark and permissive document license rules apply.\" The permissive licence is the W3C Software and Document License (https://www.w3.org/copyright/software-license-2023/): \"Permission to copy, modify, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted\", provided its notice is included \"on ALL copies of the work or portions thereof\". Used for facts only: nothing copied. Reliability: normative (W3C Recommendation). Used for: Linked Data Notifications: inboxes, ldp:inbox, sending notifications; contrast with the Notifications Protocol."@en .

<https://www.w3.org/TR/ldp/>
    dcterms:title "Linked Data Platform 1.0" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2015 W3C® (MIT, ERCIM, Keio, Beihang). W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Used for facts only: nothing copied. Reliability: normative (W3C Recommendation). Used for: LDP: containers, ldp:contains, BasicContainer, RDF vs non-RDF sources; ldp: vocabulary."@en .

<https://www.w3.org/TR/lws10-authn-openid/>
    dcterms:title "LWS 1.0 Authentication Suite: OpenID Connect (Working Draft)" ;
    dcterms:creator "W3C LWS WG" ;
    rdfs:comment "The page's header: \"Copyright © 2026 World Wide Web Consortium. W3C® liability, trademark and permissive document license rules apply.\" The permissive licence is the W3C Software and Document License (https://www.w3.org/copyright/software-license-2023/): \"Permission to copy, modify, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted\", provided its notice is included \"on ALL copies of the work or portions thereof\". Used for facts only: nothing copied. Reliability: normative (W3C Working Draft). Used for: LWS authentication suite: OpenID Connect, OpenIdProvider service in the controlled identifier document."@en .

<https://www.w3.org/TR/lws10-core/>
    dcterms:title "Linked Web Storage Protocol 1.0 (W3C Working Draft)" ;
    dcterms:creator "W3C LWS WG" ;
    rdfs:comment "The page's header: \"Copyright © 2026 World Wide Web Consortium. W3C® liability, trademark and permissive document license rules apply.\" The permissive licence is the W3C Software and Document License (https://www.w3.org/copyright/software-license-2023/): \"Permission to copy, modify, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted\", provided its notice is included \"on ALL copies of the work or portions thereof\". Steps 17.3, 17.4 and 17.9 quote its examples (a container listing, a linkset and an access grant), abridged and with the draft named, as quotations for teaching. Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"This is an unofficial proposal\", \"updated, replaced, or obsoleted\", \"Clients SHOULD NOT assume that URI structure reflects containment\", \"a request by an agent for access to resources\", \"an authorization by a storage controller granting access to resources\". Otherwise used for facts only. Reliability: normative (W3C Working Draft). Used for: Linked Web Storage Protocol 1.0: what LWS keeps and changes, container listings as application/lws+json, linksets, storage description, credentials-for-token exchange, access requests/grants, \"unofficial proposal\" status text. Round 2 found the linkset \"Precondition Required\" (428) rule in the 28 July to 21 August drafts. Round 3: every dated draft fetched and searched: the FPWD and every WD up to 21 August hold two 428 rules (an unconditional PUT on a resource with ETags, and a linkset write without If-Match); the drafts of 14 and 21 September and 5 October hold neither."@en .

<https://www.w3.org/TR/n-quads/>
    dcterms:title "RDF 1.1 N-Quads" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2012-2014 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Used for facts only: nothing copied. Reliability: normative (W3C Recommendation). Used for: N-Quads syntax and media type."@en .

<https://www.w3.org/TR/n-triples/>
    dcterms:title "RDF 1.1 N-Triples" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2001-2014 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Used for facts only: nothing copied. Reliability: normative (W3C Recommendation). Used for: N-Triples syntax and media type."@en .

<https://www.w3.org/TR/owl2-primer/>
    dcterms:title "OWL 2 Web Ontology Language Primer (Second Edition)" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2012 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"may simply be missing (but possibly true)\", \"OWL does not make the assumption that different names are names for different individuals\". Otherwise used for facts only. Reliability: authoritative (W3C Recommendation, primer). Used for: OWL 2 for readers: classes, properties, equivalence, sameAs, open world, no unique name assumption, versioning annotations."@en .

<https://www.w3.org/TR/owl2-syntax/>
    dcterms:title "OWL 2 Web Ontology Language Structural Specification and Functional-Style Syntax" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2012 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Used for facts only: nothing copied. Reliability: normative (W3C Recommendation). Used for: OWL ontology versioning terms (owl:versionIRI, priorVersion, deprecated)."@en .

<https://www.w3.org/TR/prov-o/>
    dcterms:title "PROV-O: The PROV Ontology" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2011-2013 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Used for facts only: nothing copied. Reliability: normative (W3C Recommendation). Used for: PROV-O provenance terms."@en .

<https://www.w3.org/TR/rdf-schema/>
    dcterms:title "RDF Schema 1.1" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2004-2014 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Used for facts only: nothing copied. Reliability: normative (W3C Recommendation). Used for: RDFS: rdfs:Class, subClassOf, subPropertyOf, domain/range as inference, labels and comments."@en .

<https://www.w3.org/TR/rdf-syntax-grammar/>
    dcterms:title "RDF 1.1 XML Syntax" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2004-2014 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Used for facts only: nothing copied. Reliability: normative (W3C Recommendation). Used for: RDF/XML media type (syntax table)."@en .

<https://www.w3.org/TR/rdf11-concepts/>
    dcterms:title "RDF 1.1 Concepts and Abstract Syntax" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2004-2014 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"is not required to denote the graph\". Otherwise used for facts only. Reliability: normative (W3C Recommendation). Used for: RDF data model: triples, IRIs, literals, datatypes, language tags, blank nodes, graphs, datasets, named graphs without formal semantics."@en .

<https://www.w3.org/TR/rdf11-mt/>
    dcterms:title "RDF 1.1 Semantics" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2004-2014 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Used for facts only: nothing copied. Reliability: normative (W3C Recommendation). Used for: Formal meaning of blank nodes (existentials), entailment, why inference is not validation."@en .

<https://www.w3.org/TR/rdf11-primer/>
    dcterms:title "RDF 1.1 Primer" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2003-2014 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Used for facts only: nothing copied. Reliability: authoritative (W3C WG Note). Used for: Beginner-level explanations of triples, IRIs, blank nodes, multiple graphs."@en .

<https://www.w3.org/TR/rdf12-concepts/>
    dcterms:title "RDF 1.2 Concepts and Abstract Data Model" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The page's header: \"Copyright © 2004-2026 World Wide Web Consortium. W3C® liability, trademark and permissive document license rules apply.\" The permissive licence is the W3C Software and Document License (https://www.w3.org/copyright/software-license-2023/): \"Permission to copy, modify, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted\", provided its notice is included \"on ALL copies of the work or portions thereof\". Used for facts only: nothing copied. Reliability: normative (W3C Candidate Recommendation). Used for: RDF 1.2 changes: triple terms, base direction; status of RDF 1.2."@en .

<https://www.w3.org/TR/rdf12-primer/>
    dcterms:title "RDF 1.2 Primer" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The page's header: \"Copyright © 2003-2026 World Wide Web Consortium. W3C® liability, trademark and permissive document license rules apply.\" The permissive licence is the W3C Software and Document License (https://www.w3.org/copyright/software-license-2023/): \"Permission to copy, modify, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted\", provided its notice is included \"on ALL copies of the work or portions thereof\". Used for facts only: nothing copied. Reliability: authoritative (Group Note draft). Used for: RDF 1.2 triple terms explained for beginners."@en .

<https://www.w3.org/TR/rdf12-schema/>
    dcterms:title "RDF 1.2 Schema" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The page's header: \"Copyright © 2004-2026 World Wide Web Consortium. W3C® liability, trademark and permissive document license rules apply.\" The permissive licence is the W3C Software and Document License (https://www.w3.org/copyright/software-license-2023/): \"Permission to copy, modify, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted\", provided its notice is included \"on ALL copies of the work or portions thereof\". Used for facts only: nothing copied. Reliability: normative (W3C Working Draft). Used for: RDF 1.2 Schema: confirms RDFS terms unchanged."@en .

<https://www.w3.org/TR/rdf12-semantics/>
    dcterms:title "RDF 1.2 Semantics" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The page's header: \"Copyright © 2004-2026 World Wide Web Consortium. W3C® liability, trademark and permissive document license rules apply.\" The permissive licence is the W3C Software and Document License (https://www.w3.org/copyright/software-license-2023/): \"Permission to copy, modify, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted\", provided its notice is included \"on ALL copies of the work or portions thereof\". Used for facts only: nothing copied. Reliability: normative (W3C Candidate Recommendation draft). Used for: RDF 1.2 Semantics status; rules unchanged for the course's purposes."@en .

<https://www.w3.org/TR/rdf12-turtle/>
    dcterms:title "RDF 1.2 Turtle" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The page's header: \"Copyright © 2008-2026 World Wide Web Consortium. W3C® liability, trademark and permissive document license rules apply.\" The permissive licence is the W3C Software and Document License (https://www.w3.org/copyright/software-license-2023/): \"Permission to copy, modify, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted\", provided its notice is included \"on ALL copies of the work or portions thereof\". Used for facts only: nothing copied. Reliability: normative (W3C Working Draft). Used for: Turtle 1.2 additions and media type table."@en .

<https://www.w3.org/TR/rdfa-primer/>
    dcterms:title "RDFa 1.1 Primer – Third Edition" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2010-2015 W3C® (MIT, ERCIM, Keio, Beihang). W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Used for facts only: nothing copied. Reliability: authoritative (W3C WG Note). Used for: RDFa in HTML (syntax table)."@en .

<https://www.w3.org/TR/shacl/>
    dcterms:title "Shapes Constraint Language (SHACL)" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2017 W3C® (MIT, ERCIM, Keio, Beihang). W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Used for facts only: nothing copied. Reliability: normative (W3C Recommendation). Used for: SHACL: node and property shapes, targets, sh:path, validation reports, sh:conforms."@en .

<https://www.w3.org/TR/shacl12-core/>
    dcterms:title "SHACL 1.2 Core" ;
    dcterms:creator "W3C Data Shapes WG" ;
    rdfs:comment "The page's header: \"Copyright © 2026 World Wide Web Consortium. W3C® liability, trademark and permissive document license rules apply.\" The permissive licence is the W3C Software and Document License (https://www.w3.org/copyright/software-license-2023/): \"Permission to copy, modify, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted\", provided its notice is included \"on ALL copies of the work or portions thereof\". Used for facts only: nothing copied. Reliability: normative (W3C Working Draft). Used for: SHACL 1.2 status: do not depend on new features yet."@en .

<https://www.w3.org/TR/skos-reference/>
    dcterms:title "SKOS Simple Knowledge Organization System Reference" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2009 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"not used to make assertions\". Otherwise used for facts only. Reliability: normative (W3C Recommendation). Used for: SKOS concepts and broader/narrower."@en .

<https://www.w3.org/TR/sparql11-query/>
    dcterms:title "SPARQL 1.1 Query Language" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2013 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Used for facts only: nothing copied. Reliability: normative (W3C Recommendation). Used for: SPARQL 1.1 as the current query language; SPARQL Update syntax background."@en .

<https://www.w3.org/TR/sparql11-update/>
    dcterms:title "SPARQL 1.1 Update" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2013 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Used for facts only: nothing copied. Reliability: normative (W3C Recommendation). Used for: INSERT DATA / DELETE DATA (no variables, no blank nodes in DELETE DATA) vs DELETE/INSERT … WHERE and DELETE WHERE."@en .

<https://www.w3.org/TR/sparql12-query/>
    dcterms:title "SPARQL 1.2 Query Language" ;
    dcterms:creator "W3C RDF-star WG" ;
    rdfs:comment "The page's header: \"Copyright © 2008-2026 World Wide Web Consortium. W3C® liability, trademark and permissive document license rules apply.\" The permissive licence is the W3C Software and Document License (https://www.w3.org/copyright/software-license-2023/): \"Permission to copy, modify, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted\", provided its notice is included \"on ALL copies of the work or portions thereof\". Used for facts only: nothing copied. Reliability: normative (W3C Working Draft). Used for: SPARQL 1.2 status."@en .

<https://www.w3.org/TR/swbp-vocab-pub/>
    dcterms:title "Best Practice Recipes for Publishing RDF Vocabularies" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2008 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"The choice of URI namespace is a fundamental decision you make early in the design of your vocabulary.\". Otherwise used for facts only. Reliability: authoritative (W3C WG Note). Used for: Choosing a vocabulary namespace, hash vs slash, serving vocabularies."@en .

<https://www.w3.org/TR/trig/>
    dcterms:title "RDF 1.1 TriG" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2010-2014 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Used for facts only: nothing copied. Reliability: normative (W3C Recommendation). Used for: TriG syntax for datasets."@en .

<https://www.w3.org/TR/turtle/>
    dcterms:title "RDF 1.1 Turtle" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2008-2014 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Used for facts only: nothing copied. Reliability: normative (W3C Recommendation). Used for: Turtle 1.1 syntax: prefixes, ; and , abbreviations, a, literals, relative IRIs and base."@en .

<https://www.w3.org/TR/vcard-rdf/>
    dcterms:title "vCard Ontology — for describing People and Organizations" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2014 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. W3C liability, trademark and document use rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Used for facts only: nothing copied. Reliability: authoritative (W3C Interest Group Note). Used for: vCard ontology for contacts."@en .

<https://www.w3.org/TR/vocab-dcat-3/>
    dcterms:title "Data Catalog Vocabulary (DCAT) – Version 3" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The page's header: \"Copyright © 2024 World Wide Web Consortium. W3C® liability, trademark and permissive document license rules apply.\" The permissive licence is the W3C Software and Document License (https://www.w3.org/copyright/software-license-2023/): \"Permission to copy, modify, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted\", provided its notice is included \"on ALL copies of the work or portions thereof\". Used for facts only: nothing copied. Reliability: normative (W3C Recommendation). Used for: DCAT 3 catalog/dataset terms (reused by Solid Memo)."@en .

<https://www.w3.org/TR/webarch/>
    dcterms:title "Architecture of the World Wide Web, Volume One" ;
    dcterms:creator "W3C" ;
    rdfs:comment "The document's header: \"Copyright © 2002-2004 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply.\" Its document use rules are the W3C Document License (https://www.w3.org/copyright/document-license-2023/): \"Permission to copy, and distribute the contents of this document … in any medium for any purpose and without fee or royalty is hereby granted\", but \"No right to create modifications or derivatives of W3C documents is granted pursuant to this license\", except in software and its documentation, and code examples are under the W3C Software License. Used for facts only: nothing copied. Reliability: normative (W3C Recommendation). Used for: Web architecture: global naming and network effects, URI ownership."@en .

<https://zenodo.org/records/7641620>
    dcterms:title "Making Sense of Solid for Data Governance and GDPR" ;
    dcterms:creator "Harshvardhan J. Pandit; Information 14(2):114, MDPI" ;
    rdfs:comment "Zenodo's record gives its licence as cc-by-4.0 (Creative Commons Attribution 4.0 International). Quoted, with the source named in the text, as a short quotation for teaching (Berne Convention article 10(1); in Sweden, 22 § upphovsrättslagen): \"cannot be sufficient\", \"the determination of purpose would typically be performed by the apps\". Otherwise used for facts only. Reliability: secondary (peer-reviewed). Used for: Solid and GDPR: controllers, purposes decided by apps."@en .

<https://github.com/CommunitySolidServer/CommunitySolidServer/releases/tag/v7.2.0>
    dcterms:title "Community Solid Server v7.2.0" ;
    dcterms:creator "Community Solid Server project (imec, Inrupt)" .

<https://github.com/nodeSolidServer/node-solid-server/releases/tag/v6.0.0>
    dcterms:title "node-solid-server v6.0.0" ;
    dcterms:creator "node-solid-server project" .

# Chapter 1: Why Solid.
<#ch-why-solid>
    a solid-memo:Chapter ,
      schema:Syllabus ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <> ;
    schema:position 0 ;
    dcterms:title "Why Solid"@en ;
    dcterms:description "Why Solid exists: the data-silo problem, the idea of pods with apps as views on them, where Solid came from and who shapes it today. Ends with what a Solid app is made of and which spec governs each piece."@en ;
    solid-memo:reviewQuestion <#q-why-solid-r01> ,
                              <#q-why-solid-r02> ,
                              <#q-why-solid-r03> ,
                              <#q-why-solid-r04> ,
                              <#q-why-solid-r05> ,
                              <#q-why-solid-r06> .

<#ch-why-solid-1>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-why-solid> ;
    schema:position 0 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Data silos and the coupled stack

Think of a typical web app, say a photo-sharing site. One company runs the user interface, the database, the login system and the rules about who may see what. Your photos and tags live in that company's database, in its own schema, behind its own login. An early Solid paper, a demonstration at the WWW 2016 conference, called services built this way "data silos": each app controls its own data and often has its own login and access control.

---

The paper names three consequences:

1. Users cannot easily switch to a similar app and keep their data.
2. Users cannot move their data from one storage service to another.
3. Developers are tied to one platform's API, so writing an app that works across platforms is hard.

The W3C charter for Linked Web Storage (2024) describes the same problem: the storage, how you log in, who may access what, and the app provider are coupled, so changing one means changing all of them, "sometimes at the price of all past data". Solid's starting point is to pull these pieces apart."""@en ;
    solid-memo:checkedBy <#q-why-solid-1a> ,
                         <#q-why-solid-1b> .

<#q-why-solid-1a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Maya wants to leave her photo app for a better one, but her albums and tags exist only in the first app's database. Which feature of the coupled web-app stack causes this?"@en ;
    solid-memo:back "One company controls both the app and her data"@en ;
    solid-memo:backNote "In a coupled stack the app provider also owns the database, so leaving the app means leaving the data behind."@en ;
    solid-memo:distractor <#q-why-solid-1a-d1> ,
                          <#q-why-solid-1a-d2> ,
                          <#q-why-solid-1a-d3> .

<#q-why-solid-1a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Photo files are too large to move between services"@en ;
    solid-memo:distractorNote "The problem is who controls the data and its format, not file size."@en .

<#q-why-solid-1a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The new app is written in another programming language"@en ;
    solid-memo:distractorNote "The language an app is written in does not stop it reading data it can reach."@en .

<#q-why-solid-1a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Her photos are locked by the first app's encryption"@en ;
    solid-memo:distractorNote "Even unencrypted, the data sits in a database only that company controls; the obstacle is control, not encryption."@en .

<#q-why-solid-1b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "From a developer's point of view, what does the \"data silo\" model of web apps, the problem Solid sets out to solve, make hard?"@en ;
    solid-memo:back "Writing one app that works with data from many platforms"@en ;
    solid-memo:backNote "Each silo exposes its own API, so a cross-platform app needs a separate integration for every platform."@en ;
    solid-memo:distractor <#q-why-solid-1b-d1> ,
                          <#q-why-solid-1b-d2> ,
                          <#q-why-solid-1b-d3> .

<#q-why-solid-1b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Keeping user data private from other users of the same app"@en ;
    solid-memo:distractorNote "Each silo already controls who sees what inside its walls; the hard part is crossing between silos."@en .

<#q-why-solid-1b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Storing app data in a relational database"@en ;
    solid-memo:distractorNote "Silos make that easy; it is exactly what each silo does."@en .

<#q-why-solid-1b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Hosting an app's front end on a content delivery network"@en ;
    solid-memo:distractorNote "Front-end hosting has nothing to do with where user data is locked up."@en .

<#ch-why-solid-2>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-why-solid> ;
    schema:position 1 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Separation creates choice

When one company holds both your data and the app, switching apps is expensive: you lose your history, your contacts, your settings. Splitting data, apps and identity across independent providers, instead of one company, is what Solid means by **decentralisation**.

---

Ruben Verborgh, a long-time Solid contributor, argues that in the app-centric model companies compete on how much user data they collect, which builds dependency and switching costs. If data and apps are separated, "separate competitions for storage and apps emerge". Tim Berners-Lee made the same market argument in 2009: separating storage from apps "separates the market for storage from the market for applications", which should stimulate both. In 2019 Berners-Lee also criticised ad-based models that reward clickbait; an app that does not hold your data can no longer compete by hoarding it.

So decentralisation is not only about privacy. Verborgh puts it as "enabling choice, by breaking up artificially coupled decisions into individual options": you pick your storage, your apps and your identity separately."""@en ;
    solid-memo:checkedBy <#q-why-solid-2a> ,
                         <#q-why-solid-2b> .

<#q-why-solid-2a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "In the argument for Solid, why would separating data storage from apps create more competition?"@en ;
    solid-memo:back "Storage and apps can each be chosen and replaced separately"@en ;
    solid-memo:backNote "Once data does not belong to the app, users can switch apps without losing data and switch storage without losing apps, so each market competes on its own."@en ;
    solid-memo:distractor <#q-why-solid-2a-d1> ,
                          <#q-why-solid-2a-d2> ,
                          <#q-why-solid-2a-d3> .

<#q-why-solid-2a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Users can install more apps on the same device"@en ;
    solid-memo:distractorNote "How many apps fit on a device has nothing to do with it; separation means every app works on the storage you chose."@en .

<#q-why-solid-2a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Apps no longer store any data, so they cost less to build"@en ;
    solid-memo:distractorNote "Apps still read and write data; they just do it in the user's storage."@en .

<#q-why-solid-2a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "One provider can then offer storage and apps more cheaply together"@en ;
    solid-memo:distractorNote "That is the coupled model the argument wants to move away from."@en .

<#q-why-solid-2b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A colleague says, \"Solid's decentralisation is just a privacy feature.\" What is the better summary of the Solid view?"@en ;
    solid-memo:back "It is mainly about choice: you pick each part yourself"@en ;
    solid-memo:backNote "Privacy matters, but the core argument is about breaking up coupled decisions so users can choose storage, apps and identity independently."@en ;
    solid-memo:distractor <#q-why-solid-2b-d1> ,
                          <#q-why-solid-2b-d2> ,
                          <#q-why-solid-2b-d3> .

<#q-why-solid-2b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It is mainly about speed: many small servers load faster"@en ;
    solid-memo:distractorNote "Performance is not the argument; spreading data across servers can even make it slower."@en .

<#q-why-solid-2b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It is mainly about cost: users stop paying for online services"@en ;
    solid-memo:distractorNote "Someone still has to host storage; the point is that you choose who."@en .

<#q-why-solid-2b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It is mainly about anonymity: users never reveal who they are"@en ;
    solid-memo:distractorNote "Solid apps usually know who you are, because you log in with an identity."@en .

<#ch-why-solid-3>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-why-solid> ;
    schema:position 2 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Portability is not interoperability

Isn't this already solved by law? In the EU, Article 20 of the GDPR gives people the right to receive their personal data "in a structured, commonly used and machine-readable format", and to have it sent directly to another company "where technically feasible".

But that is a **one-off export**: you download a file, the new app may or may not understand it, and every later change has to be exported again.

---

Solid aims for **interoperability**. The data stays in one place, the user's storage, and many apps read and write it there, using shared data formats (RDF, Chapters 2-3) and shared protocols. If a calendar app and a to-do app understand the same data format, both work on the same appointment. When one updates it, the other sees the change the next time it reads the data, or at once if it subscribes to notifications (Chapter 10).

| Portability (GDPR Art. 20) | Interoperability (Solid's goal) |
|---|---|
| Copy data out, once | Data stays put |
| Each app keeps its own copy | Many apps share one copy |
| Format must be "machine-readable" | Format and protocol are shared standards |"""@en ;
    solid-memo:checkedBy <#q-why-solid-3a> .

<#q-why-solid-3a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Why is a data export under Article 20 of the EU's GDPR (data portability) not enough to give users the benefits Solid aims for?"@en ;
    solid-memo:back "Each app ends up with its own copy, and the copies drift apart"@en ;
    solid-memo:backNote "Portability gives you a snapshot; Solid wants many apps to work on one copy of the data where it lives."@en ;
    solid-memo:distractor <#q-why-solid-3a-d1> ,
                          <#q-why-solid-3a-d2> ,
                          <#q-why-solid-3a-d3> .

<#q-why-solid-3a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Exports are not machine-readable, so no app can import them"@en ;
    solid-memo:distractorNote "Article 20 requires a structured, commonly used and machine-readable format."@en .

<#q-why-solid-3a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Exports work, but only between apps from the same company"@en ;
    solid-memo:distractorNote "Article 20 allows sending the data directly to another company where technically feasible."@en .

<#q-why-solid-3a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An export includes the app's code, which the new app cannot run"@en ;
    solid-memo:distractorNote "An export holds your personal data, not the app's software."@en .

<#ch-why-solid-4>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-why-solid> ;
    schema:position 3 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## The Solid idea: pods and apps as views

Solid's answer is to give each person a **pod**: a personal online data store. The 2016 paper puts it this way: users' data is managed independently of the apps that create and use it; each user stores data in a pod, "can have one or more pods from different pod providers, and can easily switch between providers". That is the design goal; in practice moving a pod is still hard (Step 1.9).

---

Apps then become **views** on that data. Verborgh describes apps as "views on top of our data pod and those of others". An app reads and writes data where it lives, but only the parts the user has allowed. The Solid website explains this with a rucksack: your storage is like a rucksack with separate pockets, and each app can open only the pockets you allow. The Solid website also lists "AI agents" among those you can let read and edit your data: an AI agent is one more app asking to open a pocket.

The name comes from **So**cial **Li**nked **D**ata. "Linked Data" is the way the data is written so that different apps can understand it, the topic of Chapter 2."""@en ;
    solid-memo:checkedBy <#q-why-solid-4a> ,
                         <#q-why-solid-4b> .

<#q-why-solid-4a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "In Solid, what does it mean to call an app a \"view\" on your data?"@en ;
    solid-memo:back "The app works on the data in your pod, not its own copy"@en ;
    solid-memo:backNote "The data lives in the pod and outlives any one app; apps are interchangeable windows onto it."@en ;
    solid-memo:distractor <#q-why-solid-4a-d1> ,
                          <#q-why-solid-4a-d2> ,
                          <#q-why-solid-4a-d3> .

<#q-why-solid-4a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The app can only display data and may never change it"@en ;
    solid-memo:distractorNote "Solid apps can write data too, if the user grants write access."@en .

<#q-why-solid-4a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The app is a web page rather than an installed mobile program"@en ;
    solid-memo:distractorNote "A view in this sense can be any kind of app, web or native."@en .

<#q-why-solid-4a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The app downloads your whole pod once and then works offline"@en ;
    solid-memo:distractorNote "Apps read the parts they are allowed, where the data lives."@en .

<#q-why-solid-4b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "The Solid website compares your pod to a rucksack with separate pockets. What do the pockets stand for?"@en ;
    solid-memo:back "Parts of your data you can open to some apps but not others"@en ;
    solid-memo:backNote "Access is granted per part of your data, so each app only reaches the pockets you open for it."@en ;
    solid-memo:distractor <#q-why-solid-4b-d1> ,
                          <#q-why-solid-4b-d2> ,
                          <#q-why-solid-4b-d3> .

<#q-why-solid-4b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Separate pod providers that each keep a full copy of your data"@en ;
    solid-memo:distractorNote "Pockets are parts of one storage, not duplicate providers."@en .

<#q-why-solid-4b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Different file formats that Solid can store side by side"@en ;
    solid-memo:distractorNote "The metaphor is about permission, not formats."@en .

<#q-why-solid-4b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Backups that protect your data if one of them is lost"@en ;
    solid-memo:distractorNote "The pockets illustrate selective access, not redundancy."@en .

<#ch-why-solid-5>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-why-solid> ;
    schema:position 4 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Origins: older ideas, hard adoption

The ideas are older than the name. In August 2009 Berners-Lee wrote two notes in **Design Issues**, his personal series of notes on web architecture. **Read-Write Linked Data** recalled that the web was meant as "a collaborative space", described writing data with HTTP, and noted that "one does not want a data wiki in which anyone can write". **Socially Aware Cloud Storage** proposed separating apps from storage, identifying people with URLs, and controlling who may access what.

---

The work took shape at MIT, in the **Crosscloud** project, with the Qatar Computing Research Institute; the 2016 demonstration paper came out of it. That paper listed open questions, such as how apps agree on what data means and how they notify each other of changes. In this course's assessment, agreeing on data formats is still hard today (Chapters 4 and 16).

Solid was not the first attempt. The 2016 paper cites Diaspora, Musubi and WebBox, and notes that "none of these proposals has been widely adopted yet". Good ideas are not enough; adoption is hard."""@en ;
    solid-memo:checkedBy <#q-why-solid-5a> ,
                         <#q-why-solid-5b> .

<#q-why-solid-5a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Tim Berners-Lee's 2009 Design Issues note \"Socially Aware Cloud Storage\" foreshadowed Solid. Where did it propose keeping users' data, relative to the apps that use it?"@en ;
    solid-memo:back "In storage that is separate from the apps"@en ;
    solid-memo:backNote "The note proposed separating apps from storage. It also proposed identifying people with URLs and controlling who may access what. Separate storage became Solid's core idea."@en ;
    solid-memo:distractor <#q-why-solid-5a-d1> ,
                          <#q-why-solid-5a-d2> ,
                          <#q-why-solid-5a-d3> ,
                          <#q-why-solid-5a-d4> .

<#q-why-solid-5a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In a shared data wiki that anyone on the web can write to"@en ;
    solid-memo:distractorNote "His \"Read-Write Linked Data\" note of the same month says one does not want a data wiki anyone can write to."@en .

<#q-why-solid-5a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Inside each app, in its own private database"@en ;
    solid-memo:distractorNote "That is the data silo the note wanted to move away from."@en .

<#q-why-solid-5a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "Replace HTTP with a new protocol designed for writing data"@en ;
    solid-memo:distractorNote "His 2009 notes reuse HTTP for writing data."@en .

<#q-why-solid-5a-d4>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "On the same server that runs the apps"@en ;
    solid-memo:distractorNote "The note proposed separating apps from storage, not keeping them together."@en .

<#q-why-solid-5b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Diaspora, Musubi and WebBox were earlier decentralised-data projects that a 2016 Solid paper cites. What does their history suggest for Solid?"@en ;
    solid-memo:back "Technical design alone does not guarantee that people adopt it"@en ;
    solid-memo:backNote "The 2016 paper notes that none of these proposals had been widely adopted yet, a reminder that Solid must win users, not just be well designed."@en ;
    solid-memo:distractor <#q-why-solid-5b-d1> ,
                          <#q-why-solid-5b-d2> ,
                          <#q-why-solid-5b-d3> .

<#q-why-solid-5b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Decentralised systems are impossible to build with web technology"@en ;
    solid-memo:distractorNote "Those systems were built; the problem was adoption, not feasibility."@en .

<#q-why-solid-5b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Solid is a renamed version of those three projects"@en ;
    solid-memo:distractorNote "The 2016 paper cites them as earlier, separate attempts."@en .

<#q-why-solid-5b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Social networks cannot store data outside a company's servers"@en ;
    solid-memo:distractorNote "The projects show it can be done; they just were not widely used."@en .

<#ch-why-solid-6>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-why-solid> ;
    schema:position 5 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Who's who: Inrupt, the W3C Solid CG, the ODI and LWS

Anyone can start a W3C **Community Group (CG)**, and the reports it publishes are not standards. Only a chartered **Working Group (WG)** can take a document along the **standards track** to a **W3C Recommendation**, which is what a W3C Standard is.

| Body | Since | Role |
|---|---|---|
| **Inrupt** | 2018 | A company co-founded by Berners-Lee that sells Solid software, such as the Enterprise Solid Server (ESS) |
| **W3C Solid Community Group (CG)** | Oct 2018 | Writes and maintains the Solid specifications as CG reports |
| **Open Data Institute (ODI)** | Oct 2024 | Solid's steward: organisational home, events, roadmap and adoption |
| **W3C Linked Web Storage (LWS) Working Group** | Sep 2024 | Puts Solid's ideas on the standards track |

---

The Solid Protocol 0.11.0 says plainly that "it is not a W3C Standard nor is it on the W3C Standards Track". The LWS Working Group uses it as its main input. As of October 2026 its LWS Protocol 1.0 is a Working Draft. In practice you build against the Solid Protocol stack today, which existing servers implement, and watch LWS as the standard to come (Chapter 17)."""@en ;
    solid-memo:checkedBy <#q-why-solid-6a> ,
                         <#q-why-solid-6b> .

<#q-why-solid-6a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A friend says, \"Solid is Inrupt's product.\" What is the more accurate description?"@en ;
    solid-memo:back "Solid is open specs; Inrupt sells one implementation"@en ;
    solid-memo:backNote "Solid is open specs plus a community, stewarded by the Open Data Institute; Inrupt is one company among several implementers."@en ;
    solid-memo:distractor <#q-why-solid-6a-d1> ,
                          <#q-why-solid-6a-d2> ,
                          <#q-why-solid-6a-d3> .

<#q-why-solid-6a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Solid is Inrupt's spec; other vendors license it"@en ;
    solid-memo:distractorNote "The specs are written in a W3C Community Group and are open to everyone."@en .

<#q-why-solid-6a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Solid is an ODI product; Inrupt resells it"@en ;
    solid-memo:distractorNote "The ODI is a steward, not a product owner, and the specs are open."@en .

<#q-why-solid-6a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Solid is a W3C Standard; Inrupt hosts it for the W3C"@en ;
    solid-memo:distractorNote "The specs are Community Group reports, not W3C Standards, and many servers are not Inrupt's."@en .

<#q-why-solid-6b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "As of 2026, your manager will adopt only specs on the W3C standards track. Which group's documents should you follow for Solid's ideas?"@en ;
    solid-memo:back "The LWS Working Group"@en ;
    solid-memo:backNote "Only a chartered W3C Working Group produces standards-track documents; for Solid's ideas that is the Linked Web Storage WG, chartered in 2024."@en ;
    solid-memo:distractor <#q-why-solid-6b-d1> ,
                          <#q-why-solid-6b-d2> ,
                          <#q-why-solid-6b-d3> .

<#q-why-solid-6b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The Solid Community Group"@en ;
    solid-memo:distractorNote "Community Groups publish reports, but not on the standards track."@en .

<#q-why-solid-6b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The Open Data Institute"@en ;
    solid-memo:distractorNote "The ODI is Solid's steward, not a standards body."@en .

<#q-why-solid-6b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Inrupt's spec team"@en ;
    solid-memo:distractorNote "A company cannot put documents on the W3C standards track on its own."@en .

<#ch-why-solid-7>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-why-solid> ;
    schema:position 6 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Built from web standards

Solid does not invent a new internet. It reuses ordinary web standards:

- **HTTP** to read and write data (GET, PUT, POST, PATCH, DELETE),
- **URIs** to name people, documents and the things in them,
- **RDF** (Linked Data) as the shared data format,
- **OpenID Connect** for login, through the Solid-OIDC spec.

Login is the part that changed most. The 2016 platform used WebID-TLS, which relied on certificates in the browser; Solid later moved to Solid-OIDC.

Why reuse? Any HTTP client, web server or browser can already read and write pod data, and developers start from skills they already have. It is also why Solid is not built on a blockchain (more on blockchains in Step 1.9). The Solid Protocol "connects a set of specifications" into one stack; Step 1.12 maps them."""@en ;
    solid-memo:checkedBy <#q-why-solid-7a> .

<#q-why-solid-7a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Why does Solid build on HTTP, URIs and RDF instead of a new technology stack?"@en ;
    solid-memo:back "Existing web tools and apps already speak them"@en ;
    solid-memo:backNote "Building on the existing web keeps the bar low for developers and lets Solid data be reached with ordinary web requests."@en ;
    solid-memo:distractor <#q-why-solid-7a-d1> ,
                          <#q-why-solid-7a-d2> ,
                          <#q-why-solid-7a-d3> .

<#q-why-solid-7a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "RDF and HTTP are faster than a purpose-built protocol"@en ;
    solid-memo:distractorNote "The choice is about reach and reuse, not speed."@en .

<#q-why-solid-7a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Pods run in the browser, so only web tech works"@en ;
    solid-memo:distractorNote "Pods are servers, and Node.js apps and scripts use them too; reuse is a design choice."@en .

<#q-why-solid-7a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Web standards make every pod's data public by default"@en ;
    solid-memo:distractorNote "HTTP serves private data behind access control too; reuse is about reach."@en .

<#ch-why-solid-8>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-why-solid> ;
    schema:position 7 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## A first look at a profile

A **WebID** is a URL that names you, such as `https://alice.example/profile/card#me`. Fetching it gives your profile document (Chapter 2 explains the `#me`).

Here is a small profile in Turtle, written with the terms of today's Solid WebID Profile and Solid-OIDC specs:

```turtle
@prefix foaf:  <http://xmlns.com/foaf/0.1/> .
@prefix pim:   <http://www.w3.org/ns/pim/space#> .
@prefix solid: <http://www.w3.org/ns/solid/terms#> .

<https://alice.example/profile/card#me>
    a foaf:Person ;
    foaf:name "Alice" ;
    pim:storage <https://alice.example/> ;
    solid:oidcIssuer <https://idp.example/> .
```

It says Alice is a person, links to her storage with `pim:storage`, and names the server she logs in with through `solid:oidcIssuer`. Profiles usually link to storage this way, but not all do: on Community Solid Server (CSS) 7.2, as of October 2026, a freshly created pod's profile has no `pim:storage` triple, and apps find the storage another way (Step 5.5). Finding a pod by following links from a profile goes back to the 2016 platform; these exact terms came later. Don't worry about the syntax yet: Chapter 3 teaches it, and Chapter 7 covers login."""@en ;
    solid-memo:checkedBy <#q-why-solid-8a> .

<#q-why-solid-8a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app knows only Alice's WebID, such as `https://alice.example/profile/card#me`. How does it usually find where her data is stored?"@en ;
    solid-memo:back "It fetches her profile and follows its storage link"@en ;
    solid-memo:backNote "The profile is an ordinary RDF document on the web, and `pim:storage` typically links from it to Alice's pod; where it is missing, as on CSS 7.2 in 2026, the app walks up the path instead."@en ;
    solid-memo:distractor <#q-why-solid-8a-d1> ,
                          <#q-why-solid-8a-d2> ,
                          <#q-why-solid-8a-d3> .

<#q-why-solid-8a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It asks a central Solid registry for her pod address"@en ;
    solid-memo:distractorNote "There is no central registry; the profile itself links to the storage."@en .

<#q-why-solid-8a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It looks up her pod address on a public blockchain"@en ;
    solid-memo:distractorNote "Solid uses HTTP and RDF documents, not a blockchain."@en .

<#q-why-solid-8a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It assumes her data is on the app's own default server"@en ;
    solid-memo:distractorNote "The user chooses the pod provider, so the app must discover it."@en .

<#ch-why-solid-9>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-why-solid> ;
    schema:position 8 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Common misconceptions

Two mix-ups were covered in Step 1.6: Solid is not Inrupt, and it is not yet a W3C standard. Three more come up often.

**"Solid is Web3."** No. Solid uses HTTP, URIs, RDF and OpenID Connect. In 2022, asked whether he aligned with Web3, Berners-Lee answered "Nope", and said of building such systems on a blockchain: "it just doesn't work".

**"Solid means running a server at home."** No. Pods can be hosted by any provider, and the Flemish government makes pods available to its citizens. Self-hosting is possible, not required. Switching providers is a design goal, but moving a pod is still hard in practice (Chapter 16).

**"Data in a pod is public."** No. A pod holds private data too, and you decide which people, apps and agents may read or edit each part (Chapters 8-9)."""@en ;
    solid-memo:checkedBy <#q-why-solid-9a> ,
                         <#q-why-solid-9b> .

<#q-why-solid-9a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Sam wants to try Solid but has no spare computer to run a server. What should you tell him?"@en ;
    solid-memo:back "He can get a pod from a hosting provider; self-hosting is optional"@en ;
    solid-memo:backNote "Solid separates the choice of storage from the choice of apps; a hosted pod is a normal choice."@en ;
    solid-memo:distractor <#q-why-solid-9a-d1> ,
                          <#q-why-solid-9a-d2> ,
                          <#q-why-solid-9a-d3> .

<#q-why-solid-9a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "He needs a home server, because pod data must stay on his device"@en ;
    solid-memo:distractorNote "Pods can be hosted by any provider; the data need not be on your device."@en .

<#q-why-solid-9a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "He must buy a pod from Inrupt, the only official provider"@en ;
    solid-memo:distractorNote "There are several providers and servers, and none is the \"official\" one."@en .

<#q-why-solid-9a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "He can join a blockchain network that stores pods for everyone"@en ;
    solid-memo:distractorNote "Solid pods are web servers, not entries on a blockchain."@en .

<#q-why-solid-9b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Lena stores her medical notes in her Solid pod. Who can read them?"@en ;
    solid-memo:back "Only the people and apps she grants access to can read them"@en ;
    solid-memo:backNote "A pod is not a public website: each part of it can be opened only to the people, apps and agents its owner chooses. Access control governs requests to the pod, though, so the provider that stores the data must still be trusted."@en ;
    solid-memo:distractor <#q-why-solid-9b-d1> ,
                          <#q-why-solid-9b-d2> ,
                          <#q-why-solid-9b-d3> ,
                          <#q-why-solid-9b-d4> .

<#q-why-solid-9b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Anyone who knows the notes' URL can read them, as on any web page"@en ;
    solid-memo:distractorNote "A URL names the data; the server still checks who may read it."@en .

<#q-why-solid-9b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only the apps her pod provider approves can read them"@en ;
    solid-memo:distractorNote "The provider stores the data; Lena decides who gets access."@en .

<#q-why-solid-9b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "They must be encrypted on her phone before Solid can store them"@en ;
    solid-memo:distractorNote "Solid protects data with access control on the server; it does not require client-side encryption."@en .

<#q-why-solid-9b-d4>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only Lena herself, since a pod cannot be shared with others"@en ;
    solid-memo:distractorNote "A pod can be shared: Lena can open any part of it to the people, apps and agents she chooses."@en .

<#ch-why-solid-10>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-why-solid> ;
    schema:position 9 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Solid in the real world

Solid is used beyond research, mainly in pilots and public-sector projects:

- **Flanders (Belgium).** The government created **Athumi**, a public company that acts as a "utility company for data". According to Inrupt's case study, it makes pods available to the region's 6.5 million citizens, running on Inrupt's ESS. Uses include sharing diplomas with recruiters or only selected payroll data with a landlord.
- **BBC.** Inrupt's case study describes the **BBC Together + Data Pod** from BBC Research and Development, a "watch party" for iPlayer: detailed viewing data stayed in each user's pod, the BBC could not see it unless the user gave permission, and the pods ran on Inrupt's ESS.
- **NHS Greater Manchester.** The ODI lists NHS pilots in Greater Manchester among Solid's real-world projects.

---

A caution: these accounts come from Inrupt, the vendor, or the ODI, the steward. They are case studies, not independent evaluations. Several flagship projects also run on one vendor's server, an uncomfortable fit for a project about avoiding lock-in. In principle the data could move to another conforming server; in practice that is hard (Step 1.9)."""@en ;
    solid-memo:checkedBy <#q-why-solid-10a> ,
                         <#q-why-solid-10b> .

<#q-why-solid-10a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "In Flanders (Belgium), the public company Athumi makes Solid pods available to the region's citizens. What does this deployment show about who can host pods?"@en ;
    solid-memo:back "An organisation such as a government can host pods for many people"@en ;
    solid-memo:backNote "A \"personal\" data store does not have to be self-hosted; a trusted organisation can host it while the person controls access."@en ;
    solid-memo:distractor <#q-why-solid-10a-d1> ,
                          <#q-why-solid-10a-d2> ,
                          <#q-why-solid-10a-d3> .

<#q-why-solid-10a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Hosting by a government means the government controls access"@en ;
    solid-memo:distractorNote "The host stores the data; the person decides who may see it."@en .

<#q-why-solid-10a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Pods only work when each citizen runs their own server at home"@en ;
    solid-memo:distractorNote "Athumi makes pods available to Flanders' 6.5 million citizens."@en .

<#q-why-solid-10a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Pods can only hold public data, not personal records like diplomas"@en ;
    solid-memo:distractorNote "Flanders uses pods for personal data such as diplomas and payroll."@en .

<#q-why-solid-10b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "How should you treat the published Solid success stories from Flanders and the BBC, written by Inrupt or the Open Data Institute?"@en ;
    solid-memo:back "As case studies by interested parties, not neutral tests"@en ;
    solid-memo:backNote "Case studies by an interested party are useful evidence that Solid is used, but not neutral proof that it works well."@en ;
    solid-memo:distractor <#q-why-solid-10b-d1> ,
                          <#q-why-solid-10b-d2> ,
                          <#q-why-solid-10b-d3> .

<#q-why-solid-10b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "As peer-reviewed studies proving Solid improves privacy"@en ;
    solid-memo:distractorNote "They are published by Inrupt or the ODI, not peer-reviewed research."@en .

<#q-why-solid-10b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "As proof that Solid is ready for any production use"@en ;
    solid-memo:distractorNote "They describe particular pilots, written by interested parties; they do not show readiness everywhere."@en .

<#q-why-solid-10b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "As official W3C test reports showing which servers conform"@en ;
    solid-memo:distractorNote "They are case studies, not conformance results."@en .

<#ch-why-solid-11>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-why-solid> ;
    schema:position 10 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Anatomy of a Solid app

A Solid app is an ordinary web or Node.js application built from three pieces:

1. **An authenticated `fetch`.** The user logs in at the identity provider named in their profile (Step 1.8); the app gets a `fetch` that proves who the user is on every request, using **tokens** (short-lived proofs of who the user is; Solid-OIDC, Chapter 7).
2. **Plain HTTP to the pod.** The app reads and writes documents with GET, PUT, POST, PATCH and DELETE.
3. **An RDF library** that turns Linked Data into values for your code.

---

Usually there is **no backend database** for user data: it stays in the pod, where any app the user allows can open it. (Backends that act on their own are Chapter 13.)

```text
 Your app --login--> Identity provider --tokens--> Your app
 Your app --authenticated HTTP--> Pod server --RDF/files--> Your app
```

The **identity provider** issues tokens; the **pod server** stores the data and checks who may access it. One product often plays both roles, and the user picks the provider, not you."""@en ;
    solid-memo:checkedBy <#q-why-solid-11a> ,
                         <#q-why-solid-11b> .

<#q-why-solid-11a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "In a typical Solid app, where does the user's data live?"@en ;
    solid-memo:back "In the user's pod, read and written over HTTP"@en ;
    solid-memo:backNote "A Solid app works directly on the pod over HTTP, so any other app the user authorises can open the same data."@en ;
    solid-memo:distractor <#q-why-solid-11a-d1> ,
                          <#q-why-solid-11a-d2> ,
                          <#q-why-solid-11a-d3> .

<#q-why-solid-11a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In the app's own database, synced to the pod nightly"@en ;
    solid-memo:distractorNote "Solid apps usually have no backend database of their own for user data; they work on the pod directly."@en .

<#q-why-solid-11a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In the identity provider, next to the user's login"@en ;
    solid-memo:distractorNote "The identity provider issues tokens; it does not store app data."@en .

<#q-why-solid-11a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In the browser's localStorage, uploaded on logout"@en ;
    solid-memo:distractorNote "The pod is where the data lives; apps read and write it there over HTTP."@en .

<#q-why-solid-11b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "What does the identity provider contribute to a Solid app?"@en ;
    solid-memo:back "Tokens that prove who the user is to the pod"@en ;
    solid-memo:backNote "The identity provider authenticates the user and issues tokens; the pod server checks those tokens against its access rules."@en ;
    solid-memo:distractor <#q-why-solid-11b-d1> ,
                          <#q-why-solid-11b-d2> ,
                          <#q-why-solid-11b-d3> .

<#q-why-solid-11b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The list of documents stored in the user's pod"@en ;
    solid-memo:distractorNote "The pod server stores the documents and lists them; the identity provider only logs the user in."@en .

<#q-why-solid-11b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The access rules for each of the user's documents"@en ;
    solid-memo:distractorNote "The pod server stores and checks the access rules."@en .

<#q-why-solid-11b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A cached copy of the user's data for faster reads"@en ;
    solid-memo:distractorNote "The identity provider holds no pod data; it only authenticates."@en .

<#ch-why-solid-12>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-why-solid> ;
    schema:position 11 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## The specs behind each piece

Each piece of a Solid app follows a specification, and the **Solid Protocol** ties them together. The map below shows which spec governs each piece, its latest version as of October 2026 with its status, and where the course teaches it. None of the Solid specs is a W3C Standard: they are Community Group reports or drafts.

| Piece | Spec (latest version and status, October 2026) | Chapter |
|---|---|---|
| The data: Linked Data and RDF | RDF 1.1 (W3C Recommendation, 2014) | 2-4 |
| Pods, containers, reading and writing over HTTP | Solid Protocol 0.11.0 (Draft CG Report) | 5, 6 |
| Your identity document | Solid WebID Profile 1.0.0 (Draft CG Report, not under /TR) | 7 |
| Logging in, the authenticated `fetch` | Solid-OIDC 0.1.0 (2022); a 2026 Draft CG Report adds requirements | 7 |
| Who may access what, and sharing | WAC 1.0.0 (Draft CG Report) or ACP 0.9.0 (Editor's Draft): two alternatives | 8, 9 |
| Live updates | Solid Notifications Protocol 0.3.0 (Draft CG Report) | 10 |
| Data design, tools, security and backends | (practice, not one spec) | 11, 12-13 |
| A minimal app, read end to end | (all of the above) | 14 |
| A real app, open problems, the standard to come | (practice); LWS Protocol 1.0 (Working Draft) | 15-17 |

Spec versions move; check the current one before relying on a detail."""@en ;
    solid-memo:checkedBy <#q-why-solid-12a> .

<#q-why-solid-12a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Your Solid app must show changes another app makes to a pod resource, without the user reloading the page. Which Solid spec covers that?"@en ;
    solid-memo:back "Solid Notifications Protocol"@en ;
    solid-memo:backNote "The Solid Notifications Protocol lets an app subscribe to a resource and be told when it changes; the Solid Protocol requires servers to support it."@en ;
    solid-memo:distractor <#q-why-solid-12a-d1> ,
                          <#q-why-solid-12a-d2> ,
                          <#q-why-solid-12a-d3> .

<#q-why-solid-12a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Solid WebID Profile"@en ;
    solid-memo:distractorNote "The WebID Profile describes the document a WebID points to; it says nothing about changes to other resources."@en .

<#q-why-solid-12a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Web Access Control (WAC)"@en ;
    solid-memo:distractorNote "WAC decides who may read or change a resource; it tells no one when the resource changes."@en .

<#q-why-solid-12a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Solid-OIDC"@en ;
    solid-memo:distractorNote "Solid-OIDC logs the user in and proves who is asking; it says nothing about changes."@en .

<#q-why-solid-r01>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "An AI assistant wants to read your calendar stored in your Solid pod. In Solid terms, how should this be handled?"@en ;
    solid-memo:back "Like any other app: it gets access only to what you allow"@en ;
    solid-memo:backNote "Solid's model treats an AI agent as one more app that needs permission to open specific parts of your pod."@en ;
    solid-memo:distractor <#q-why-solid-r01-d1> ,
                          <#q-why-solid-r01-d2> ,
                          <#q-why-solid-r01-d3> .

<#q-why-solid-r01-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It first copies your pod into the AI company's own database"@en ;
    solid-memo:distractorNote "That recreates the data silo Solid tries to avoid."@en .

<#q-why-solid-r01-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It needs no permission, because AI agents are trusted by default"@en ;
    solid-memo:distractorNote "No app or agent is trusted by default; access must be granted."@en .

<#q-why-solid-r01-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only an agent built by Inrupt may read Solid data"@en ;
    solid-memo:distractorNote "Any developer can build an app or agent for Solid."@en .

<#q-why-solid-r02>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A notes app and a task app both understand the same appointment format and use the same appointment in your Solid pod. You edit it in one app. What happens in the other?"@en ;
    solid-memo:back "It sees the change on its next read, since there is one copy"@en ;
    solid-memo:backNote "Keeping one copy in the user's storage is what turns portability into interoperability."@en ;
    solid-memo:distractor <#q-why-solid-r02-d1> ,
                          <#q-why-solid-r02-d2> ,
                          <#q-why-solid-r02-d3> .

<#q-why-solid-r02-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing changes until you export and import the data again"@en ;
    solid-memo:distractorNote "That describes one-off portability, not shared data in a pod."@en .

<#q-why-solid-r02-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It receives the change at once, pushed automatically to every app"@en ;
    solid-memo:distractorNote "An app sees it when it next reads, or at once only if it subscribes to notifications."@en .

<#q-why-solid-r02-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It shows an error, because each app needs a pod of its own"@en ;
    solid-memo:distractorNote "One pod can serve many apps."@en .

<#q-why-solid-r03>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Today each web app keeps your data locked in its own database. What does Solid offer in its place?"@en ;
    solid-memo:back "A pod of your own that many apps share"@en ;
    solid-memo:backNote "The data silo is answered by moving data into user-chosen storage, a pod, that apps access with permission."@en ;
    solid-memo:distractor <#q-why-solid-r03-d1> ,
                          <#q-why-solid-r03-d2> ,
                          <#q-why-solid-r03-d3> ,
                          <#q-why-solid-r03-d4> ,
                          <#q-why-solid-r03-d5> .

<#q-why-solid-r03-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "Ad-funded incentives → a cryptocurrency that pays users for data"@en ;
    solid-memo:distractorNote "Solid has no token or payment system and does not use a blockchain."@en .

<#q-why-solid-r03-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "One global Solid server that every app uses"@en ;
    solid-memo:distractorNote "Solid lets users choose among many providers, not one server."@en .

<#q-why-solid-r03-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "Each app has its own login → each app keeps a copy of your password"@en ;
    solid-memo:distractorNote "You log in through an identity provider you choose, so apps never see your password."@en .

<#q-why-solid-r03-d4>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A one-off export from each app to the next"@en ;
    solid-memo:distractorNote "That is portability, as in GDPR Article 20; Solid aims for interoperability, where the data stays put and many apps use one copy."@en .

<#q-why-solid-r03-d5>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A blockchain ledger that every app writes to"@en ;
    solid-memo:distractorNote "Solid is built from ordinary web standards (HTTP, URIs, RDF, OpenID Connect), not on a blockchain."@en .

<#q-why-solid-r04>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Maya's photo albums live in her photo app's own database. Which change gives her both a choice of photo apps and a choice of where her albums are stored?"@en ;
    solid-memo:back "Keeping her data in a pod, separate from any app"@en ;
    solid-memo:backNote "Separating storage from apps turns one coupled decision into two free choices: the chain from silo to separation to choice."@en ;
    solid-memo:distractor <#q-why-solid-r04-d1> ,
                          <#q-why-solid-r04-d2> ,
                          <#q-why-solid-r04-d3> .

<#q-why-solid-r04-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Getting a GDPR export of her albums every month"@en ;
    solid-memo:distractorNote "Exports are one-off copies; each app still keeps its own data."@en .

<#q-why-solid-r04-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Asking her photo app to encrypt all of her albums"@en ;
    solid-memo:distractorNote "Encryption does not change who controls the storage."@en .

<#q-why-solid-r04-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Moving all her apps to one larger, more trusted provider"@en ;
    solid-memo:distractorNote "That is still a coupled stack, just a bigger one."@en .

<#q-why-solid-r05>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "According to Inrupt, Flanders' citizen pods and the BBC's pilot ran on Inrupt's Enterprise Solid Server (ESS). Why is that not lock-in in principle, and what is the catch?"@en ;
    solid-memo:back "Any conforming server could hold the data; the catch: moving is hard"@en ;
    solid-memo:backNote "Open specs mean any conforming server could host the same data, but moving a pod is still hard in practice. That both ran on ESS is Inrupt's own claim."@en ;
    solid-memo:distractor <#q-why-solid-r05-d1> ,
                          <#q-why-solid-r05-d2> ,
                          <#q-why-solid-r05-d3> .

<#q-why-solid-r05-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "ESS is open source, so anyone can run it; the catch is the licence fees"@en ;
    solid-memo:distractorNote "ESS is a commercial product sold by Inrupt; other servers are separate projects."@en .

<#q-why-solid-r05-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The W3C guarantees free migration; the catch is that it takes weeks"@en ;
    solid-memo:distractorNote "No W3C rule guarantees migration, and the Solid Protocol defines no way to move a pod."@en .

<#q-why-solid-r05-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The data sits on a blockchain; the catch is the transaction costs"@en ;
    solid-memo:distractorNote "Solid pods are web servers, not a blockchain."@en .

<#q-why-solid-r06>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app is given only Alice's WebID. Which sequence lets it read her private notes?"@en ;
    solid-memo:back "Read her profile, log in at its `solid:oidcIssuer`, find and fetch her storage"@en ;
    solid-memo:backNote "The profile names the identity provider and usually the storage; logging in there gives the app an authenticated `fetch`, which it then uses on the pod server."@en ;
    solid-memo:distractor <#q-why-solid-r06-d1> ,
                          <#q-why-solid-r06-d2> ,
                          <#q-why-solid-r06-d3> .

<#q-why-solid-r06-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Send her password to her pod server, then read her notes from it"@en ;
    solid-memo:distractorNote "Apps never handle the password; she logs in at the identity provider her profile names."@en .

<#q-why-solid-r06-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Ask a central registry for her pod, then log her in at that registry"@en ;
    solid-memo:distractorNote "There is no central registry; her profile names her identity provider and usually links to her storage."@en .

<#q-why-solid-r06-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Log her in at the app's own server, then copy her pod to its database"@en ;
    solid-memo:distractorNote "Her profile names the identity provider, and copying the pod recreates the silo."@en .

# Chapter 2: Linked Data.
<#ch-web-of-data>
    a solid-memo:Chapter ,
      schema:Syllabus ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <> ;
    schema:position 1 ;
    dcterms:title "Linked Data"@en ;
    dcterms:description "The idea underneath every Solid standard: Linked Data, a set of principles for naming, finding and connecting data with URIs, HTTP and RDF. It covers global identifiers, dereferencing, hash URIs and the triple as the unit of data."@en ;
    solid-memo:reviewQuestion <#q-web-of-data-r01> ,
                              <#q-web-of-data-r02> ,
                              <#q-web-of-data-r03> ,
                              <#q-web-of-data-r04> .

<#ch-web-of-data-1>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-web-of-data> ;
    schema:position 0 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## The four Linked Data rules (2006)

In 2006 Tim Berners-Lee wrote down four rules for putting data on the web:

1. Use URIs as names for things.
2. Use HTTP URIs, so that people can look those names up.
3. When someone looks up a URI, provide useful information, using the
   standards (such as RDF).
4. Include links to other URIs, so that they can discover more things.

Rule 1 is about *things*, not only web pages: people, books and ideas get
names too. Rule 2 makes a name something you can fetch. Rule 3 says that what
you get back should be machine-readable. Rule 4 turns separate datasets into
a web: from one piece of data you can follow links to more.

---

A Solid pod follows all four. Every resource in a pod has an HTTP(S) URL
(rules 1 and 2). Fetching a data document returns machine-readable data in a
standard RDF format such as Turtle (rule 3). RDF is the W3C's data model for
Linked Data, taught in Step 2.4. And documents point to other documents and
other pods: a WebID profile links to the owner's storage with `pim:storage`
(rule 4)."""@en ;
    solid-memo:checkedBy <#q-web-of-data-1a> ,
                         <#q-web-of-data-1b> .

<#q-web-of-data-1a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Why does the second of Berners-Lee's Linked Data rules (2006) ask for *HTTP* URIs rather than any kind of URI?"@en ;
    solid-memo:back "So a program can fetch the name and get data about it"@en ;
    solid-memo:backNote "An HTTP URI is a name you can dereference: put it in a GET request and you receive information about the thing it names."@en ;
    solid-memo:distractor <#q-web-of-data-1a-d1> ,
                          <#q-web-of-data-1a-d2> ,
                          <#q-web-of-data-1a-d3> .

<#q-web-of-data-1a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "So the data is encrypted while it is in transit"@en ;
    solid-memo:distractorNote "Encryption comes from HTTPS/TLS, and rule 2 is about lookup, not secrecy."@en .

<#q-web-of-data-1a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "So the name is guaranteed never to change"@en ;
    solid-memo:distractorNote "Keeping a name stable is a separate concern; an HTTP URI breaks if its owner stops serving it."@en .

<#q-web-of-data-1a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "So the server can choose which format the name uses"@en ;
    solid-memo:distractorNote "A URI is a name; format choice happens later, when the name is looked up."@en .

<#q-web-of-data-1b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid profile document contains `pim:storage <https://alice.example/>`. Which of Berners-Lee's four Linked Data rules does that line mainly put into practice?"@en ;
    solid-memo:back "Rule 4: link to other URIs so more can be discovered"@en ;
    solid-memo:backNote "A link from the profile to the storage lets an app discover a pod it did not know about, which is exactly rule 4."@en ;
    solid-memo:distractor <#q-web-of-data-1b-d1> ,
                          <#q-web-of-data-1b-d2> ,
                          <#q-web-of-data-1b-d3> .

<#q-web-of-data-1b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Rule 1: use URIs as names for things, not only pages"@en ;
    solid-memo:distractorNote "The line uses a name, but its purpose is to point the reader onward to another resource, which is what rule 4 asks for."@en .

<#q-web-of-data-1b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Rule 2: use HTTP URIs so names can be looked up"@en ;
    solid-memo:distractorNote "Rule 2 is about which kind of URI to use, not about linking one resource to another."@en .

<#q-web-of-data-1b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Rule 3: return standard data when looked up"@en ;
    solid-memo:distractorNote "Rule 3 is about what a server sends back when a URI is fetched, not about what a document links to."@en .

<#ch-web-of-data-2>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-web-of-data> ;
    schema:position 1 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## 5-star open data, and why Linked Data need not be open

In 2010 Berners-Lee added a 5-star scale for publishing *open* data:

| Stars | What you publish | Typical format |
|---|---|---|
| ★ | Anything on the web, with an open licence | PDF |
| ★★ | Machine-readable structured data | Excel |
| ★★★ | A non-proprietary format | CSV |
| ★★★★ | Open W3C standards, with URIs to identify things | RDF |
| ★★★★★ | Links to other people's data for context | RDF linking to other datasets |

In the words of 5stardata.info, at one and two stars the data is "locked up
in a document"; at three it is data *on* the web; at four it is data *in* the
web, and at five it is data in the web *linked to* other data.

---

The first star asks for an open licence, so this is a scale for open data.
The Linked Data rules themselves don't require openness. Global names,
lookups and links work just as well for data that only some people may read.
Solid is the main example: most pod data sits behind access control, and it is
still Linked Data."""@en ;
    solid-memo:checkedBy <#q-web-of-data-2a> ,
                         <#q-web-of-data-2b> .

<#q-web-of-data-2a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "On Berners-Lee's 5-star open data scale, a city publishes bus timetables as CSV files under an open licence. Which single change would move it from three stars to four?"@en ;
    solid-memo:back "Republish it as RDF with a URI for each stop"@en ;
    solid-memo:backNote "Four stars means using open W3C standards such as RDF, with URIs that identify things."@en ;
    solid-memo:distractor <#q-web-of-data-2a-d1> ,
                          <#q-web-of-data-2a-d2> ,
                          <#q-web-of-data-2a-d3> .

<#q-web-of-data-2a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Republish the same tables as Excel spreadsheets"@en ;
    solid-memo:distractorNote "Excel is proprietary, which is the two-star level, so this would be a step down."@en .

<#q-web-of-data-2a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Add links to another city's timetable PDFs"@en ;
    solid-memo:distractorNote "Linking is the five-star step, and it needs data that uses URIs (four stars) first."@en .

<#q-web-of-data-2a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Add a column of stop web-page URLs to the CSV"@en ;
    solid-memo:distractorNote "The file now contains URLs but is still CSV; four stars needs an open W3C standard such as RDF, where URIs name the stops themselves."@en .

<#q-web-of-data-2b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A Solid pod holds medical notes that only their owner and her doctor can read. Are those notes Linked Data?"@en ;
    solid-memo:back "Yes; naming and linking don't require openness"@en ;
    solid-memo:backNote "Linked Data is a way of naming and linking data, and it works the same for private, access-controlled pod data."@en ;
    solid-memo:distractor <#q-web-of-data-2b-d1> ,
                          <#q-web-of-data-2b-d2> ,
                          <#q-web-of-data-2b-d3> .

<#q-web-of-data-2b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "No; Linked Data must be published under an open licence"@en ;
    solid-memo:distractorNote "The open licence belongs to the 5-star open data scale, not to the four Linked Data rules."@en .

<#q-web-of-data-2b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "No; data protected by a login can't have URIs"@en ;
    solid-memo:distractorNote "A protected resource still has a URL; access control decides who may fetch it."@en .

<#q-web-of-data-2b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only if they also earn five stars on the open data scale"@en ;
    solid-memo:distractorNote "The star scale rates open publishing and does not decide what counts as Linked Data."@en .

<#ch-web-of-data-3>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-web-of-data> ;
    schema:position 2 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Global names: URI, URL, IRI

Linked Data names things with web identifiers, and those names are *global*.
In RDF, the same identifier in two places means the same thing, so anyone can
reuse your identifier to talk about the same thing. As the W3C's Web
architecture (2004) puts it, "global naming leads to global network
effects". If two apps that have never met both use Bob's WebID, their data is
about the same Bob.

You will see three names for these identifiers:

- **URI** (RFC 3986) is the general kind of identifier, such as `https://…`
  or `urn:isbn:…`.
- **URL** is a URI that also tells you how to *locate* the resource, for
  example over HTTP. `urn:isbn:…` is a URI that is not a URL.
- **IRI** (RFC 3987) generalises a URI so that it may contain Unicode
  characters, such as `https://example.org/résumé`. Mapping it to a URI writes
  those characters as escaped bytes: `r%C3%A9sum%C3%A9`.

---

RDF compares IRIs as strings, character for character. So `http` versus
`https`, `#` versus `/`, or a letter's case each make a different IRI: copy
IRIs exactly. RDF specs say IRI and Solid specs say URI or URL. In Solid code
you often parse them with the JavaScript `URL` class, but `URL` normalises what
it parses: it lower-cases the scheme and host, percent-encodes Unicode (`résumé`
becomes `r%C3%A9sum%C3%A9`) and adds `/` to an empty path. So compare IRIs as
the strings that appear in the data, not as `new URL(…).href`."""@en ;
    solid-memo:checkedBy <#q-web-of-data-3a> ,
                         <#q-web-of-data-3b> ,
                         <#q-web-of-data-3c> .

<#q-web-of-data-3a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Two apps that have never met both use the IRI `https://bob.example.org/profile#me` in their RDF data. What may a reader conclude?"@en ;
    solid-memo:back "Both apps are talking about the same thing"@en ;
    solid-memo:backNote "In RDF, two appearances of the same IRI denote the same resource, which is what makes global names useful for linking."@en ;
    solid-memo:distractor <#q-web-of-data-3a-d1> ,
                          <#q-web-of-data-3a-d2> ,
                          <#q-web-of-data-3a-d3> .

<#q-web-of-data-3a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing, because each app's data is separate"@en ;
    solid-memo:distractorNote "IRIs have global scope in RDF, so the same IRI means the same resource wherever it appears."@en .

<#q-web-of-data-3a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "They mean the same thing only if they share a server"@en ;
    solid-memo:distractorNote "Where the data is stored does not change what an IRI denotes."@en .

<#q-web-of-data-3a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The second app has copied the first app's data"@en ;
    solid-memo:distractorNote "Reusing a global name is normal and expected; it says nothing about copying."@en .

<#q-web-of-data-3b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "An RDF graph contains both `https://alice.example/profile/card#me` and `http://alice.example/profile/card#me`. Does RDF treat them as the same IRI?"@en ;
    solid-memo:back "No: RDF compares IRIs character for character"@en ;
    solid-memo:backNote "RDF compares IRIs as plain strings, so a different scheme, case or separator gives a different IRI; copy IRIs exactly."@en ;
    solid-memo:distractor <#q-web-of-data-3b-d1> ,
                          <#q-web-of-data-3b-d2> ,
                          <#q-web-of-data-3b-d3> .

<#q-web-of-data-3b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Yes: the scheme is ignored when IRIs are compared"@en ;
    solid-memo:distractorNote "The scheme is part of the string, and RDF compares the whole string."@en .

<#q-web-of-data-3b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Yes: both lead to the same document on one host"@en ;
    solid-memo:distractorNote "RDF never fetches IRIs to compare them; where they lead does not matter."@en .

<#q-web-of-data-3b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only if the server redirects one to the other"@en ;
    solid-memo:distractorNote "Server behaviour does not change IRI identity in RDF; the strings differ, so the IRIs differ."@en .

<#q-web-of-data-3c>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "How is an IRI (RFC 3987) different from a URI?"@en ;
    solid-memo:back "An IRI may contain Unicode characters"@en ;
    solid-memo:backNote "RFC 3987 defines IRIs as URIs extended with Unicode; every URI is also an IRI, and an IRI maps back to a URI by percent-encoding."@en ;
    solid-memo:distractor <#q-web-of-data-3c-d1> ,
                          <#q-web-of-data-3c-d2> ,
                          <#q-web-of-data-3c-d3> .

<#q-web-of-data-3c-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An IRI always starts with `http` or `https`"@en ;
    solid-memo:distractorNote "IRIs can use any scheme; being restricted to HTTP is a Solid habit, not part of the IRI definition."@en .

<#q-web-of-data-3c-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An IRI can't contain a `#` fragment"@en ;
    solid-memo:distractorNote "IRIs follow the same general syntax as URIs, fragments included."@en .

<#q-web-of-data-3c-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An IRI names a thing, while a URI names a document"@en ;
    solid-memo:distractorNote "Both can name anything; the difference is only in the allowed characters."@en .

<#ch-web-of-data-4>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-web-of-data> ;
    schema:position 3 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Triples and graphs

RDF, the data model behind Linked Data, stores every fact as a *triple*: a
subject, a predicate and an object. Think of it as an arrow with a label: the
subject points to the object, and the predicate is the label.

```turtle
<https://alice.example/profile/card#me>
    <http://xmlns.com/foaf/0.1/knows>
        <https://bob.example.org/profile#me> .
```

Here Alice *knows* Bob. An *RDF graph* is a **set** of triples. Since it is a
set, it has no order, and stating the same triple twice still gives one
triple.

---

The terms in a triple come in three kinds: IRIs (global names, Step 2.3),
*literals* (data values such as `"Alice"`) and *blank nodes* (nodes with no
global name, Step 2.8). Not every kind can go in every position:

| Position | Allowed terms |
|---|---|
| Subject | IRI or blank node |
| Predicate | IRI only |
| Object | IRI, blank node or literal |

So a literal such as `"Alice"` can never be a subject, and a predicate is
always an IRI, never a plain key like `name`. (RDF 1.2 adds one more kind of
object, covered in Chapter 3.)"""@en ;
    solid-memo:checkedBy <#q-web-of-data-4a> ,
                         <#q-web-of-data-4b> .

<#q-web-of-data-4a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Two apps both add the RDF triple \"Alice knows Bob\" to the same RDF graph. How many triples does the graph now hold about that fact?"@en ;
    solid-memo:back "One, because a graph is a set"@en ;
    solid-memo:backNote "An RDF graph is a set of triples, so duplicates collapse into one and order carries no meaning."@en ;
    solid-memo:distractor <#q-web-of-data-4a-d1> ,
                          <#q-web-of-data-4a-d2> ,
                          <#q-web-of-data-4a-d3> .

<#q-web-of-data-4a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Two, one for each app that added it"@en ;
    solid-memo:distractorNote "A graph is a set of triples, so an identical triple can't appear twice."@en .

<#q-web-of-data-4a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Zero, because the second add cancels the first"@en ;
    solid-memo:distractorNote "Adding a triple that is already there changes nothing, and nothing is removed."@en .

<#q-web-of-data-4a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Two, but readers see only the latest one"@en ;
    solid-memo:distractorNote "A graph keeps no order or history, so there is no \"latest\" copy, only one triple."@en .

<#q-web-of-data-4b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "In an RDF triple, which kinds of term may stand in each position: subject, predicate and object?"@en ;
    solid-memo:back "Subject: IRI or blank node; predicate: IRI only; object: IRI, blank node or literal"@en ;
    solid-memo:backNote "Subjects are IRIs or blank nodes, predicates are always IRIs, and only objects may be literals. (RDF 1.2 adds one more kind of object, covered in Chapter 3.)"@en ;
    solid-memo:distractor <#q-web-of-data-4b-d1> ,
                          <#q-web-of-data-4b-d2> ,
                          <#q-web-of-data-4b-d3> .

<#q-web-of-data-4b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Subject: IRI or literal; predicate: IRI only; object: IRI, blank node or literal"@en ;
    solid-memo:distractorNote "A literal may only be an object, never a subject; a subject is an IRI or a blank node."@en .

<#q-web-of-data-4b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Subject: IRI or blank node; predicate: IRI or literal; object: IRI, blank node or literal"@en ;
    solid-memo:distractorNote "A predicate must always be an IRI, never a literal."@en .

<#q-web-of-data-4b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Subject: IRI or blank node; predicate: IRI or blank node; object: IRI, blank node or literal"@en ;
    solid-memo:distractorNote "Blank nodes may be subjects or objects, but never predicates."@en .

<#ch-web-of-data-5>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-web-of-data> ;
    schema:position 4 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Dereferencing and content negotiation

To *dereference* a URI is to fetch a representation of the resource it names,
for example with an HTTP GET. One URI can have several representations, and
the client says which it prefers in the `Accept` header. An optional `q`
weight from 0 to 1 ranks the choices; no weight means 1:

```http
GET /profile/card HTTP/1.1
Host: alice.example
Accept: text/turtle, application/ld+json;q=0.9
```

```http
HTTP/1.1 200 OK
Content-Type: text/turtle

@prefix foaf: <http://xmlns.com/foaf/0.1/> .
<#me> a foaf:Person ; foaf:name "Alice" .
```

The body states two triples about `<#me>`, the `#me` inside this document
(Step 2.7): Alice is a person, and her name is "Alice". This client prefers
Turtle and will accept JSON-LD. The response's `Content-Type` says which
format it got. Under the Solid Protocol (v0.11, 2024), a server must be able
to return an RDF document either as Turtle (`text/turtle`) or as JSON-LD
(`application/ld+json`), depending on what the client asks for. Both carry
the same data; only the syntax differs. Chapter 3 teaches both formats."""@en ;
    solid-memo:checkedBy <#q-web-of-data-5a> ,
                         <#q-web-of-data-5b> .

<#q-web-of-data-5a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A client sends `Accept: application/ld+json, text/turtle;q=0.5` to a Solid server (Solid Protocol 0.11, 2024) for an RDF document. What should it expect back?"@en ;
    solid-memo:back "JSON-LD, because it carries the higher weight"@en ;
    solid-memo:backNote "A type with no `q` has weight 1, so JSON-LD outranks Turtle at 0.5, and a Solid server can serve either."@en ;
    solid-memo:distractor <#q-web-of-data-5a-d1> ,
                          <#q-web-of-data-5a-d2> ,
                          <#q-web-of-data-5a-d3> .

<#q-web-of-data-5a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Turtle, because Solid's default format is Turtle"@en ;
    solid-memo:distractorNote "The server follows the client's stated preferences, and JSON-LD has the implied weight of 1."@en .

<#q-web-of-data-5a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Both formats together in one response"@en ;
    solid-memo:distractorNote "One response carries one representation, named by its `Content-Type`."@en .

<#q-web-of-data-5a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An error, because two formats were listed"@en ;
    solid-memo:distractorNote "Listing several acceptable formats with weights is the normal use of `Accept`."@en .

<#q-web-of-data-5b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Under the Solid Protocol (v0.11, 2024), app A fetches an RDF contact document from a Solid pod with `Accept: text/turtle`; app B fetches the same URL with `Accept: application/ld+json`. What do they receive?"@en ;
    solid-memo:back "The same triples, written in two different syntaxes"@en ;
    solid-memo:backNote "Content negotiation picks a representation of one resource; Turtle and JSON-LD just write the same data differently."@en ;
    solid-memo:distractor <#q-web-of-data-5b-d1> ,
                          <#q-web-of-data-5b-d2> ,
                          <#q-web-of-data-5b-d3> .

<#q-web-of-data-5b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Two separate stored copies, one for each format"@en ;
    solid-memo:distractorNote "The server keeps one resource and writes it out in whichever format is asked for; there is no second copy."@en .

<#q-web-of-data-5b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "B gets an error, because the document was saved as Turtle"@en ;
    solid-memo:distractorNote "However it was stored, a Solid server can return an RDF document as Turtle or JSON-LD."@en .

<#q-web-of-data-5b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "B gets only the triples that were written in JSON-LD"@en ;
    solid-memo:distractorNote "The data is one set of triples; the server returns all of it in the syntax B asked for."@en .

<#ch-web-of-data-6>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-web-of-data> ;
    schema:position 5 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Documents versus things

Some resources can be sent whole in a message: a web page, an image, a
profile document. These are called *information resources*. Alice herself
can't be sent over HTTP. She is a person, and people, places and ideas are not
information resources. As the W3C's Cool URIs note puts it, "one URI can't
stand for both a Web document and a real-world object."

---

Suppose `https://alice.example/profile/card` named both the document and
Alice. Then these two triples would describe the same thing:

```turtle
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix schema: <https://schema.org/> .

<https://alice.example/profile/card> dcterms:created "2024-01-01" .
<https://alice.example/profile/card> schema:birthDate "1990-07-04" .
```

`dcterms:created` and `schema:birthDate` are abbreviated predicate IRIs from
shared vocabularies (Chapters 3 and 4); read them as "was created on" and "was
born on". A thing that was created in 2024 *and* born in 1990 makes no sense,
and an app could not tell which facts are about the file and which are about
the person. So the document and the person need different identifiers. In a
typical Solid profile, such as one on CSS, the document is `…/profile/card` and
Alice is `…/profile/card#me`.
The next step explains how that `#me` works."""@en ;
    solid-memo:checkedBy <#q-web-of-data-6a> .

<#q-web-of-data-6a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid, `https://alice.example/profile/card` is Alice's profile document. Why shouldn't that URL also be used as Alice's own identifier?"@en ;
    solid-memo:back "It already names the profile document, not the person"@en ;
    solid-memo:backNote "A document and the person it describes are different resources, so they need different URIs; otherwise facts about the file and about the person get mixed up."@en ;
    solid-memo:distractor <#q-web-of-data-6a-d1> ,
                          <#q-web-of-data-6a-d2> ,
                          <#q-web-of-data-6a-d3> .

<#q-web-of-data-6a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "URLs with no file extension can't be used to name people"@en ;
    solid-memo:distractorNote "The spelling of a URI says nothing about what it names; the problem is reusing one name for two things."@en .

<#q-web-of-data-6a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server would return HTML instead of RDF"@en ;
    solid-memo:distractorNote "The server returns the same representation either way; the problem lies in what the data then means."@en .

<#q-web-of-data-6a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only fragment IRIs may name things in RDF"@en ;
    solid-memo:distractorNote "Any IRI may name anything in RDF; the problem is that this one already names the document."@en .

<#ch-web-of-data-7>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-web-of-data> ;
    schema:position 6 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Hash URIs and the #me convention

The part after `#` is the *fragment*. A client removes it before sending the
request, so the server never sees it. Fetching
`https://bob.example.org/profile#me` sends `GET /profile`; the client then
looks for triples about `#me` inside the returned data. In RDF,
`…/profile#me` is simply a different IRI from `…/profile`, so one names Bob
and the other the document about him. This is the *hash URI* pattern. Inside
the document itself, `<#me>` is short for
`<https://bob.example.org/profile#me>`; Step 3.3 shows how such relative IRIs
are resolved.

---

The alternative is the *303 URI* pattern. A URI with no fragment, such as
`/id/alice`, answers `303 See Other` and redirects to a document that
describes Alice.

| | Hash URIs | 303 URIs |
|---|---|---|
| Requests | One | Two (redirect, then document) |
| Server | Static files are enough | Needs redirect setup |
| Best for | Small sets that change together | Large datasets; each 303 costs an extra request |

WebID 1.0 allows both. Many Solid servers, such as CSS and NSS, issue
`…/profile/card#me` WebIDs, but not every provider does: Inrupt's PodSpaces
(2026) uses WebIDs with no fragment, like `https://id.inrupt.com/alice`
(Chapter 7). Pod documents usually name their things with fragments of the
document URL."""@en ;
    solid-memo:checkedBy <#q-web-of-data-7a> ,
                         <#q-web-of-data-7b> .

<#q-web-of-data-7a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "An app dereferences the hash URI `https://bob.example.org/profile#me`. What does Bob's server receive?"@en ;
    solid-memo:back "A request for `/profile`, without the fragment"@en ;
    solid-memo:backNote "The fragment never reaches the server: the client fetches the document and then looks up the fragment in it."@en ;
    solid-memo:distractor <#q-web-of-data-7a-d1> ,
                          <#q-web-of-data-7a-d2> ,
                          <#q-web-of-data-7a-d3> .

<#q-web-of-data-7a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A request for `/profile#me`, fragment included"@en ;
    solid-memo:distractorNote "Clients strip the fragment before the request; it is handled only on the client side."@en .

<#q-web-of-data-7a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A request for `/profile`, then a second request for `#me`"@en ;
    solid-memo:distractorNote "There is no second request; the client finds `#me` in the document it already has."@en .

<#q-web-of-data-7a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A request that the server answers with 303 See Other"@en ;
    solid-memo:distractorNote "A 303 redirect belongs to the 303 URI pattern; hash URIs need just one ordinary GET."@en .

<#q-web-of-data-7b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Linked Data, why do hash URIs (such as `…/profile#me`) suit Solid pods well?"@en ;
    solid-memo:back "One plain GET returns the document describing the thing"@en ;
    solid-memo:backNote "A hash URI needs no redirect: one request fetches the document, which works with simple file-like storage such as a pod."@en ;
    solid-memo:distractor <#q-web-of-data-7b-d1> ,
                          <#q-web-of-data-7b-d2> ,
                          <#q-web-of-data-7b-d3> .

<#q-web-of-data-7b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "They keep the thing's data hidden from the server that stores it"@en ;
    solid-memo:distractorNote "The server stores and serves the whole document; only the fragment in the request is left out."@en .

<#q-web-of-data-7b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "They make each thing a separate file on the server"@en ;
    solid-memo:distractorNote "Many things can share one document, each named by its own fragment."@en .

<#q-web-of-data-7b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "They are the only identifier pattern that WebID 1.0 allows"@en ;
    solid-memo:distractorNote "WebID 1.0 accepts both hash URIs and 303 redirects."@en .

<#ch-web-of-data-8>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-web-of-data> ;
    schema:position 7 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Blank nodes and skolemization

**Blank nodes** are nodes with no global name. Formally, a blank node just
says that *something exists*, without naming it. "Alice lives at an address
whose city is Ghent" can use a blank node for the address.

```turtle
@prefix schema: <https://schema.org/> .

<#me> schema:address _:a .
_:a   schema:addressLocality "Ghent" .
```

The label `_:a` only means something inside this one document. No other
document can point to that address, so it can never be the target of a rule-4
link. When outside links are needed, a system can *skolemize*: replace each
blank node with a fresh IRI. RDF recommends the form
`http://example.com/.well-known/genid/<id>`. In practice, pod data usually
names such things with fragment IRIs like `<#address>` instead. N3 Patch, the
patch format of Solid Protocol 0.11 (Step 6.7), restricts blank nodes, so pod
data tends to avoid them."""@en ;
    solid-memo:checkedBy <#q-web-of-data-8a> ,
                         <#q-web-of-data-8b> .

<#q-web-of-data-8a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Alice's RDF profile document contains `<#me> schema:address _:a .` Another app wants to say something about that address `_:a`. What is the problem?"@en ;
    solid-memo:back "A blank node can't be referred to from outside its document"@en ;
    solid-memo:backNote "A blank node label is local to its document, so to be linkable the address needs an IRI, either a fragment like `<#address>` or a skolem IRI."@en ;
    solid-memo:distractor <#q-web-of-data-8a-d1> ,
                          <#q-web-of-data-8a-d2> ,
                          <#q-web-of-data-8a-d3> .

<#q-web-of-data-8a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Blank nodes may never appear as the subject of a triple"@en ;
    solid-memo:distractorNote "Blank nodes may be subjects or objects; `_:a` can be the subject of further triples in its own document."@en .

<#q-web-of-data-8a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The other app must first ask the server to rename it"@en ;
    solid-memo:distractorNote "Servers don't offer this; the label is local to the document by design."@en .

<#q-web-of-data-8a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Blank nodes can hold only literal values, never other nodes"@en ;
    solid-memo:distractorNote "A blank node is a node like any other and can have any kind of object."@en .

<#q-web-of-data-8b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "An app exports an RDF document containing the blank node `_:a` and wants other pods to be able to point at that node. Which change makes that possible while keeping the same facts?"@en ;
    solid-memo:back "Give `_:a` an IRI, such as `<#address>`"@en ;
    solid-memo:backNote "Giving a blank node a fresh IRI is called skolemization; RDF suggests `/.well-known/genid/` IRIs, and pod data usually uses fragment IRIs instead."@en ;
    solid-memo:distractor <#q-web-of-data-8b-d1> ,
                          <#q-web-of-data-8b-d2> ,
                          <#q-web-of-data-8b-d3> .

<#q-web-of-data-8b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Rename the label to something unique, such as `_:alice-address`"@en ;
    solid-memo:distractorNote "A blank node label stays local to its document, however unique it looks."@en .

<#q-web-of-data-8b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Replace `_:a` with the literal `\"Alice's address\"`"@en ;
    solid-memo:distractorNote "A literal can't be a subject, and a value is not a node others can link to."@en .

<#q-web-of-data-8b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Ask the other pods to copy the triples about `_:a`"@en ;
    solid-memo:distractorNote "Each copy makes a new, separate blank node; nothing links back to the original."@en .

<#q-web-of-data-r01>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "An app fetches Alice's Solid WebID `https://alice.example/profile/card#me` with `Accept: text/turtle`. Which path does the GET request name, and who picks out the triples about `#me`?"@en ;
    solid-memo:back "It GETs `/profile/card`, and the app picks out the triples about `#me`"@en ;
    solid-memo:backNote "Dereferencing a hash URI fetches the whole document (here as Turtle, by content negotiation), and the client reads the triples whose subject is `#me`."@en ;
    solid-memo:distractor <#q-web-of-data-r01-d1> ,
                          <#q-web-of-data-r01-d2> ,
                          <#q-web-of-data-r01-d3> ,
                          <#q-web-of-data-r01-d4> .

<#q-web-of-data-r01-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It GETs `/profile/card#me`, and the server returns only Alice's triples"@en ;
    solid-memo:distractorNote "The fragment is never sent, so the server returns the whole document."@en .

<#q-web-of-data-r01-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "The server replies 303 and redirects to the profile document"@en ;
    solid-memo:distractorNote "A hash URI needs no redirect; 303 belongs to the 303 URI pattern."@en .

<#q-web-of-data-r01-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It GETs `/profile/card`, and the server filters the response to Alice's triples"@en ;
    solid-memo:distractorNote "The server never sees `#me`, so it returns the whole document; the client does the picking."@en .

<#q-web-of-data-r01-d4>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It GETs `/profile/card#me`, and the app picks out the triples about `#me`"@en ;
    solid-memo:distractorNote "The app does the picking, but the fragment is never sent: the request names `/profile/card`."@en .

<#q-web-of-data-r02>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A note app writes `<#note1> ex:author <https://alice.example/profile/card#me> .` into Alice's Solid pod (`ex:` stands for some vocabulary). What two things does using Alice's WebID as the object, rather than a literal such as `\"Alice\"`, give the note?"@en ;
    solid-memo:back "A global name for Alice, and a link to her profile"@en ;
    solid-memo:backNote "Alice's WebID is an HTTP IRI, so reusing it as the object both names her globally and links the note to her profile (Linked Data rules 1, 2 and 4). A literal such as `\"Alice\"` is only a data value: it names no one globally and cannot be followed."@en ;
    solid-memo:distractor <#q-web-of-data-r02-d1> ,
                          <#q-web-of-data-r02-d2> ,
                          <#q-web-of-data-r02-d3> ,
                          <#q-web-of-data-r02-d4> ,
                          <#q-web-of-data-r02-d5> .

<#q-web-of-data-r02-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "A blank node standing for an unnamed author"@en ;
    solid-memo:distractorNote "Both terms are IRIs; nothing in the triple is a blank node."@en .

<#q-web-of-data-r02-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A global name for Alice, and a copy of her profile"@en ;
    solid-memo:distractorNote "The triple only names Alice; her profile stays in her own document, reached by following the link."@en .

<#q-web-of-data-r02-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "Data that must be open because it uses HTTP URIs"@en ;
    solid-memo:distractorNote "HTTP URIs make data linkable, not public; pod data is usually access-controlled."@en .

<#q-web-of-data-r02-d4>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A local name for Alice, and a link to her profile"@en ;
    solid-memo:distractorNote "A WebID is a global name, not one valid only in this pod: the same IRI means Alice in every document and pod, so any app can reuse it."@en .

<#q-web-of-data-r02-d5>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A local name for Alice, and a copy of her profile"@en ;
    solid-memo:distractorNote "A WebID is a global name, not one valid only in this pod. And the triple only names Alice: her profile stays in her own document."@en .

<#q-web-of-data-r03>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "An app loads Alice's and Bob's RDF profiles into one graph. Both documents mention `<https://bob.example.org/profile#me>`, and both contain a blank node labelled `_:a`. What does the combined graph hold?"@en ;
    solid-memo:back "One node for Bob, and two separate `_:a` nodes"@en ;
    solid-memo:backNote "Global IRIs join up across documents, which is how data from several pods combines; blank nodes stay apart, and identical triples collapse because a graph is a set."@en ;
    solid-memo:distractor <#q-web-of-data-r03-d1> ,
                          <#q-web-of-data-r03-d2> ,
                          <#q-web-of-data-r03-d3> .

<#q-web-of-data-r03-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "One node for Bob, and one shared `_:a` node"@en ;
    solid-memo:distractorNote "Blank node labels are local to each document, so the two `_:a` are different nodes even though the labels match."@en .

<#q-web-of-data-r03-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Two nodes for Bob, one from each document"@en ;
    solid-memo:distractorNote "The same IRI names the same thing wherever it appears, so the Bob IRIs join into one node."@en .

<#q-web-of-data-r03-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An error, because the label `_:a` is used twice"@en ;
    solid-memo:distractorNote "Combining graphs keeps blank nodes from different documents apart, renaming labels where needed; clashing labels are expected."@en .

<#q-web-of-data-r04>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In a Solid pod, a friends-only document `https://alice.example/clubs` describes Alice's running club as `<#club>`. Bob's public profile links to `https://alice.example/clubs#club`. Is Bob's link valid Linked Data, and who can look the club up through it?"@en ;
    solid-memo:back "Bob's link is valid Linked Data, but only people Alice allows can look the club up"@en ;
    solid-memo:backNote "Naming and linking work the same for private data: following the hash URI sends `GET /clubs`, and access control decides who receives the document."@en ;
    solid-memo:distractor <#q-web-of-data-r04-d1> ,
                          <#q-web-of-data-r04-d2> ,
                          <#q-web-of-data-r04-d3> ,
                          <#q-web-of-data-r04-d4> ,
                          <#q-web-of-data-r04-d5> .

<#q-web-of-data-r04-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It isn't valid Linked Data, because a friends-only document can't be linked to"@en ;
    solid-memo:distractorNote "Anyone may write the IRI; access control only decides who can fetch the document."@en .

<#q-web-of-data-r04-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "Alice's server gets a request for `/clubs#club` and checks access for `#club` alone"@en ;
    solid-memo:distractorNote "The fragment is never sent; access is checked for the whole `/clubs` document."@en .

<#q-web-of-data-r04-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "The club data earns five stars, since a public profile links to it"@en ;
    solid-memo:distractorNote "The stars rate open publishing; data behind access control lacks the open licence of the first star."@en .

<#q-web-of-data-r04-d4>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It is valid Linked Data, and anyone who can read Bob's profile can look the club up"@en ;
    solid-memo:distractorNote "A link grants no access: following it sends `GET /clubs`, and Alice's access control decides who receives the document."@en .

<#q-web-of-data-r04-d5>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It isn't followable until the club gets a URI without a `#` fragment"@en ;
    solid-memo:distractorNote "Hash URIs can be looked up: the client drops `#club`, fetches `/clubs` and finds the triples about `#club` in it."@en .

# Chapter 3: Writing RDF: Turtle, JSON-LD and friends.
<#ch-rdf-syntaxes>
    a solid-memo:Chapter ,
      schema:Syllabus ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <> ;
    schema:position 2 ;
    dcterms:title "Writing RDF: Turtle, JSON-LD and friends"@en ;
    dcterms:description "Read and write RDF in the formats Solid uses, use JSON-LD as plain JSON, read simple SPARQL and N3 Patch, and know what RDF 1.2 adds."@en ;
    solid-memo:reviewQuestion <#q-rdf-syntaxes-r01> ,
                              <#q-rdf-syntaxes-r02> ,
                              <#q-rdf-syntaxes-r03> ,
                              <#q-rdf-syntaxes-r04> ,
                              <#q-rdf-syntaxes-r05> ,
                              <#q-rdf-syntaxes-r06> ,
                              <#q-rdf-syntaxes-r07> ,
                              <#q-rdf-syntaxes-r08> .

<#ch-rdf-syntaxes-1>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-rdf-syntaxes> ;
    schema:position 0 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## One graph, many syntaxes

Chapter 2 described RDF as a graph of triples. That graph is an abstract model, not a file format: RDF is not "an XML thing", and RDF/XML is just one older way of writing it down. The same graph can be written in many interchangeable syntaxes:

| Syntax | Media type | Holds |
|---|---|---|
| Turtle | `text/turtle` | one graph |
| N-Triples | `application/n-triples` | one graph |
| TriG | `application/trig` | a dataset |
| N-Quads | `application/n-quads` | a dataset |
| JSON-LD | `application/ld+json` | a dataset |
| RDFa | inside HTML | one graph |
| RDF/XML | `application/rdf+xml` | one graph |
| N3 | `text/n3` | a graph, plus formulae and rules |

A dataset is several graphs side by side (Step 3.9).

---

For Solid, two of these matter most. When a client asks for an RDF document, a Solid server MUST be able to answer with `text/turtle` or `application/ld+json`, whichever the client requests in its `Accept` header. So you can write a document as Turtle and read it back as JSON-LD: the triples are the same, only the text differs."""@en ;
    solid-memo:checkedBy <#q-rdf-syntaxes-1a> .

<#q-rdf-syntaxes-1a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "An app stores a profile on a Solid server as Turtle. A second app sends `GET` with `Accept: application/ld+json`. What should it receive?"@en ;
    solid-memo:back "The same triples, written as JSON-LD"@en ;
    solid-memo:backNote "RDF is a graph, and Turtle and JSON-LD are two ways of writing it. A Solid server must serve RDF documents in either format, chosen by the client's `Accept` header."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-1a-d1> ,
                          <#q-rdf-syntaxes-1a-d2> ,
                          <#q-rdf-syntaxes-1a-d3> .

<#q-rdf-syntaxes-1a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A 406 Not Acceptable error, because the file was stored as Turtle"@en ;
    solid-memo:distractorNote "Solid servers must serve every RDF document as both Turtle and JSON-LD, whatever format was used to write it."@en .

<#q-rdf-syntaxes-1a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The original Turtle text with a JSON-LD content type"@en ;
    solid-memo:distractorNote "The server converts the representation; mislabelling Turtle as JSON-LD would break any JSON-LD parser."@en .

<#q-rdf-syntaxes-1a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A JSON-LD copy that leaves out triples JSON-LD can't express"@en ;
    solid-memo:distractorNote "JSON-LD can express any RDF 1.1 graph, so a conversion keeps all the triples."@en .

<#ch-rdf-syntaxes-2>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-rdf-syntaxes> ;
    schema:position 1 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Turtle basics

Turtle, the "Terse RDF Triple Language", is the format to master for Solid: servers must serve it, and WebID 1.0 makes it the required format for profiles. A few rules cover most files:

- `@prefix foaf: <http://xmlns.com/foaf/0.1/> .` lets you write `foaf:name` instead of the full IRI. The SPARQL-style `PREFIX foaf: <…>` (no `@`, no final dot) works too.
- `a` is short for `rdf:type`, which says what kind of thing the subject is, such as a person or an agent (Chapter 4 covers these classes).
- Every statement ends with `.`.
- `;` starts a new predicate for the same subject.
- `,` adds another object for the same subject and predicate.

---

Here is a typical WebID profile:

```turtle
@prefix foaf:  <http://xmlns.com/foaf/0.1/> .
@prefix pim:   <http://www.w3.org/ns/pim/space#> .
@prefix ldp:   <http://www.w3.org/ns/ldp#> .
@prefix solid: <http://www.w3.org/ns/solid/terms#> .

<https://alice.example/profile/card#me>
    a foaf:Agent ;
    foaf:name "Alice" ;
    foaf:knows <https://bob.example.org/profile#me>,
               <https://carol.example/#i> ;
    pim:storage <https://alice.example/> ;        # where Alice's pod is
    ldp:inbox <https://alice.example/inbox/> ;    # where to send her messages
    solid:oidcIssuer <https://idp.example/> .     # who logs Alice in
```

Read it aloud as "Alice's WebID is an agent, is named Alice, knows Bob and Carol, …". Every line is a triple about the same subject."""@en ;
    solid-memo:checkedBy <#q-rdf-syntaxes-2a> ,
                         <#q-rdf-syntaxes-2b> .

<#q-rdf-syntaxes-2a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front """How many RDF triples does this Turtle contain?

```turtle
<#me> a foaf:Person ; foaf:knows <#bob>, <#carol> .
```"""@en ;
    solid-memo:back "Three"@en ;
    solid-memo:backNote "`;` keeps the subject and `,` keeps the subject and predicate, so the statement expands to one `rdf:type` triple and two `foaf:knows` triples."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-2a-d1> ,
                          <#q-rdf-syntaxes-2a-d2> ,
                          <#q-rdf-syntaxes-2a-d3> .

<#q-rdf-syntaxes-2a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Two"@en ;
    solid-memo:distractorNote "Each object after a `,` is its own triple, repeating the subject and predicate."@en .

<#q-rdf-syntaxes-2a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "One"@en ;
    solid-memo:distractorNote "The `.` ends the whole statement, which `;` and `,` can stretch over several triples."@en .

<#q-rdf-syntaxes-2a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Four"@en ;
    solid-memo:distractorNote "`a` is just shorthand for `rdf:type`, so `<#me> a foaf:Person` is a single triple."@en .

<#q-rdf-syntaxes-2b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Turtle, which triple does `<#me> a foaf:Agent .` expand to?"@en ;
    solid-memo:back "`<#me> rdf:type foaf:Agent .`" ;
    solid-memo:backNote "`a` expands to `http://www.w3.org/1999/02/22-rdf-syntax-ns#type`, so the triple says that `<#me>` is a `foaf:Agent`."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-2b-d1> ,
                          <#q-rdf-syntaxes-2b-d2> ,
                          <#q-rdf-syntaxes-2b-d3> .

<#q-rdf-syntaxes-2b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`<#me> foaf:a foaf:Agent .`" ;
    solid-memo:distractorNote "`a` is a Turtle keyword, not a prefixed name; it never picks up a prefix."@en .

<#q-rdf-syntaxes-2b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`<#me> rdfs:subClassOf foaf:Agent .`" ;
    solid-memo:distractorNote "`rdfs:subClassOf` relates two classes; `a` always means `rdf:type`."@en .

<#q-rdf-syntaxes-2b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`foaf:Agent rdf:type <#me> .`" ;
    solid-memo:distractorNote "The subject stays first; `a` doesn't reverse the triple."@en .

<#ch-rdf-syntaxes-3>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-rdf-syntaxes> ;
    schema:position 2 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Relative IRIs and the base

Inside angle brackets, Turtle accepts relative IRIs, which a parser resolves against a base IRI. The base is usually the URL the document was fetched from, unless the file sets one with `@base` or `BASE`. Resolution follows RFC 3986, and browsers resolve links the same way for ordinary cases like these.

If the document lives at `https://alice.example/profile/card`:

| Written | Resolves to |
|---|---|
| `<#me>` | `https://alice.example/profile/card#me` |
| `<>` | `https://alice.example/profile/card` (the document itself) |
| `<../inbox/>` | `https://alice.example/inbox/` |

This is why a pod document can say `<#me>` without knowing its own absolute address: the same file works wherever it is served. It also ties in with Chapter 2's hash URIs. The "things" a document describes are usually fragments of its own URL, so `<#task1>` in `https://alice.example/todo/list.ttl` names `https://alice.example/todo/list.ttl#task1`.

---

A practical consequence: always parse a fetched document with its real URL as the base. A parser given the wrong base, or none, will produce the wrong IRIs, keep them relative, or fail. N3.js 2.13 (2026), for example, keeps `<#me>` as the relative `#me` when it is given no base (Step 3.8 shows why that output is not valid N-Triples)."""@en ;
    solid-memo:checkedBy <#q-rdf-syntaxes-3a> ,
                         <#q-rdf-syntaxes-3b> .

<#q-rdf-syntaxes-3a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "The Turtle document `https://alice.example/profile/card` contains the relative IRI `<../inbox/>`. Which IRI does it denote?"@en ;
    solid-memo:back "`https://alice.example/inbox/`" ;
    solid-memo:backNote "`card` sits in `/profile/`, `..` goes up to `/`, and `inbox/` is appended, giving `https://alice.example/inbox/`."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-3a-d1> ,
                          <#q-rdf-syntaxes-3a-d2> ,
                          <#q-rdf-syntaxes-3a-d3> .

<#q-rdf-syntaxes-3a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`https://alice.example/profile/inbox/`" ;
    solid-memo:distractorNote "`..` climbs one level above the folder `/profile/`, so the result is outside it."@en .

<#q-rdf-syntaxes-3a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`https://alice.example/profile/card/../inbox/`" ;
    solid-memo:distractorNote "A parser resolves the relative IRI fully; the `..` does not stay in the stored IRI."@en .

<#q-rdf-syntaxes-3a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`https://alice.example/profile/card/inbox/`" ;
    solid-memo:distractorNote "A relative path replaces the last segment `card`; it is not appended after it."@en .

<#q-rdf-syntaxes-3b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "An app fetches the Turtle document `https://bob.example/notes/a.ttl`, which contains `<#n1>`, and parses the text with N3.js 2.13 (2026) without passing a base IRI, so N3.js keeps relative IRIs as written. Later the app looks up `https://bob.example/notes/a.ttl#n1` in its store. Does it find the note?"@en ;
    solid-memo:back "No: the stored IRI is not the one the app looks up"@en ;
    solid-memo:backNote "Relative IRIs are resolved against whatever base the parser is given; pass the fetched URL so `<#n1>` becomes `https://bob.example/notes/a.ttl#n1`."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-3b-d1> ,
                          <#q-rdf-syntaxes-3b-d2> ,
                          <#q-rdf-syntaxes-3b-d3> .

<#q-rdf-syntaxes-3b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Yes: the parser fills in the base from the fetch"@en ;
    solid-memo:distractorNote "A parser only sees the text you hand it; it doesn't know where the text came from."@en .

<#q-rdf-syntaxes-3b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Yes: fragments match regardless of base"@en ;
    solid-memo:distractorNote "IRIs are compared as whole strings, so `#n1` and the full IRI differ."@en .

<#q-rdf-syntaxes-3b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "No: the parser drops triples with relative IRIs"@en ;
    solid-memo:distractorNote "N3.js keeps the triple, with the subject `#n1`; the triple is there, under the wrong IRI."@en .

<#ch-rdf-syntaxes-4>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-rdf-syntaxes> ;
    schema:position 3 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Literals, datatypes and language tags

Chapter 2 introduced literals as data values. In Turtle they look like this:

```turtle
@prefix xsd:    <http://www.w3.org/2001/XMLSchema#> .
@prefix schema: <https://schema.org/> .
@prefix ex:     <http://example.org/> .
<#me> schema:name       "Alice" ;                 # xsd:string
      schema:birthDate  "1990-07-04"^^xsd:date ;  # typed literal
      schema:jobTitle   "Ingénieure"@fr ;         # rdf:langString
      ex:heightInMetres 1.68 ;                    # xsd:decimal
      ex:childCount     2 .                       # xsd:integer
```

(`ex:` stands for an app's own vocabulary; schema.org's `height` and `children` expect a measurement and a person, not bare numbers.)

---

- A plain quoted string is an `xsd:string`.
- `^^` attaches a datatype, such as `xsd:date` or `xsd:boolean`. The `xsd:` namespace is `http://www.w3.org/2001/XMLSchema#` and `rdf:` is `http://www.w3.org/1999/02/22-rdf-syntax-ns#`; copy them exactly, since `http` versus `https` or `#` versus `/` makes a different IRI.
- Bare numbers are shorthands: `2` is `xsd:integer`, `1.68` is `xsd:decimal`, `1.6E3` is `xsd:double`, and `true`/`false` are `xsd:boolean`.
- A language tag (`@fr`) gives the datatype `rdf:langString`, not `xsd:string`.

A literal is its text (the lexical form) plus its datatype, so `"2"` and `2` are different literals, and code that looks for one will not find the other. Literal types are also not JavaScript types: integer and decimal are distinct, and links are IRIs, not strings. `"abc"^^xsd:integer` still parses, but it is an invalid value that tools may reject."""@en ;
    solid-memo:checkedBy <#q-rdf-syntaxes-4a> ,
                         <#q-rdf-syntaxes-4b> .

<#q-rdf-syntaxes-4a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In RDF, what is the datatype of the literal `\"Ingénieure\"@fr`?"@en ;
    solid-memo:back "`rdf:langString`" ;
    solid-memo:backNote "A literal with a language tag has the datatype `rdf:langString`; a plain string without a tag is an `xsd:string`."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-4a-d1> ,
                          <#q-rdf-syntaxes-4a-d2> ,
                          <#q-rdf-syntaxes-4a-d3> .

<#q-rdf-syntaxes-4a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`xsd:string`" ;
    solid-memo:distractorNote "Only untagged strings are `xsd:string`; a language tag changes the datatype."@en .

<#q-rdf-syntaxes-4a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`xsd:language`" ;
    solid-memo:distractorNote "`xsd:language` is a datatype for language codes themselves, such as `\"fr\"`, not for tagged text."@en .

<#q-rdf-syntaxes-4a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`xsd:normalizedString`" ;
    solid-memo:distractorNote "That is a string without line breaks or tabs; a language tag always gives `rdf:langString`."@en .

<#q-rdf-syntaxes-4b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "One app writes the Turtle `ex:count \"5\"` to a pod and another searches the pod for `ex:count 5`. Why does the search find nothing?"@en ;
    solid-memo:back "`\"5\"` is a string and `5` is an integer, so the literals differ"@en ;
    solid-memo:backNote "A literal is its text (lexical form) plus its datatype. `\"5\"` is an `xsd:string` and `5` is an `xsd:integer`, so they are different values."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-4b-d1> ,
                          <#q-rdf-syntaxes-4b-d2> ,
                          <#q-rdf-syntaxes-4b-d3> .

<#q-rdf-syntaxes-4b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Turtle forbids numbers as objects unless `^^` is used"@en ;
    solid-memo:distractorNote "Bare numbers are valid Turtle shorthands for integer, decimal or double literals."@en .

<#q-rdf-syntaxes-4b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server stores every value as text and loses types"@en ;
    solid-memo:distractorNote "A Solid server keeps the triples, datatypes included, and serves them back as written."@en .

<#q-rdf-syntaxes-4b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Numbers can only be compared in JSON-LD, not Turtle"@en ;
    solid-memo:distractorNote "Literal identity is defined by RDF, not by the syntax used to write it."@en .

<#ch-rdf-syntaxes-5>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-rdf-syntaxes> ;
    schema:position 4 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Blank nodes and collections in Turtle

Chapter 2 explained blank nodes as nodes with no global name. Turtle has two ways to write them:

```turtle
@prefix foaf:   <http://xmlns.com/foaf/0.1/> .
@prefix schema: <https://schema.org/> .

<#me> foaf:based_near [ foaf:name "Ghent" ] .     # anonymous: [ ]

<#me> schema:address _:addr .                       # labelled: _:addr
_:addr schema:addressLocality "Ghent" .
```

The label `_:addr` only matters inside this one document. The same label in another file is a different node.

Ordered lists use parentheses. `( "a" "b" "c" )` is shorthand for a chain of blank nodes linked with `rdf:first` (the item) and `rdf:rest` (the rest of the list), ending in `rdf:nil`; `()` alone is `rdf:nil`. Triples have no order, so this chain is how RDF records order.

Because blank nodes have no global name, they are hard to point at from outside their document. Step 3.10 shows what that means when you patch a document."""@en ;
    solid-memo:checkedBy <#q-rdf-syntaxes-5a> .

<#q-rdf-syntaxes-5a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "What does the Turtle collection `( \"a\" \"b\" )` produce in the RDF graph?"@en ;
    solid-memo:back "A chain of blank nodes linked by `rdf:first` and `rdf:rest`"@en ;
    solid-memo:backNote "A Turtle collection expands to blank nodes, each with an `rdf:first` item and an `rdf:rest` link, ending in `rdf:nil`."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-5a-d1> ,
                          <#q-rdf-syntaxes-5a-d2> ,
                          <#q-rdf-syntaxes-5a-d3> .

<#q-rdf-syntaxes-5a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "One literal holding a JSON-style array"@en ;
    solid-memo:distractorNote "RDF has no array literal; the list is built from ordinary triples."@en .

<#q-rdf-syntaxes-5a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Two triples whose order is fixed by the file"@en ;
    solid-memo:distractorNote "A graph is a set with no order, so order must be encoded with `rdf:rest` links."@en .

<#q-rdf-syntaxes-5a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A named graph containing the two strings"@en ;
    solid-memo:distractorNote "Parentheses build an RDF collection, not a named graph."@en .

<#ch-rdf-syntaxes-6>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-rdf-syntaxes> ;
    schema:position 5 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## JSON-LD

JSON-LD is JSON that is also RDF: you can treat a document as plain JSON or process it as triples. Its key words:

- `@context` maps short keys to IRIs;
- `@id` gives a node's IRI;
- `@type` gives a node's class (or a value's datatype);
- `@value` and `@language` spell out literals.

```json
{
  "@context": {
    "foaf": "http://xmlns.com/foaf/0.1/",
    "xsd": "http://www.w3.org/2001/XMLSchema#",
    "name": "foaf:name",
    "jobTitle": "https://schema.org/jobTitle",
    "height": "http://example.org/heightInMetres",
    "knows": { "@id": "foaf:knows", "@type": "@id" }
  },
  "@id": "https://alice.example/profile/card#me",
  "@type": "foaf:Person",
  "name": "Alice",
  "jobTitle": { "@value": "Ingénieure", "@language": "fr" },
  "height": { "@value": "1.68", "@type": "xsd:decimal" },
  "knows": "https://bob.example.org/profile#me"
}
```

The `"@type": "@id"` on `knows` tells processors that the string is an IRI. Leave it out and `knows` points to a string literal, not to Bob: the link silently breaks and still looks fine as JSON. A value object, like `jobTitle` and `height`, sets a literal's language or datatype. Native JSON numbers map differently: `2` becomes `xsd:integer`, but a bare `1.68` becomes `xsd:double`, not Turtle's `xsd:decimal`.

A context can be a URL that processors fetch. Remote contexts carry security and availability risks, so production apps should cache or pin the contexts they rely on."""@en ;
    solid-memo:checkedBy <#q-rdf-syntaxes-6a> ,
                         <#q-rdf-syntaxes-6b> .

<#q-rdf-syntaxes-6a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A JSON-LD context defines `\"knows\": \"foaf:knows\"` without `\"@type\": \"@id\"`, and the data says `\"knows\": \"https://bob.example.org/profile#me\"`. What is the object of the resulting triple?"@en ;
    solid-memo:back "A string literal that happens to look like a URL"@en ;
    solid-memo:backNote "Without `\"@type\": \"@id\"`, a string value is a literal. Apps following `foaf:knows` links will not find Bob."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-6a-d1> ,
                          <#q-rdf-syntaxes-6a-d2> ,
                          <#q-rdf-syntaxes-6a-d3> .

<#q-rdf-syntaxes-6a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Bob's WebID, because JSON-LD detects URLs automatically"@en ;
    solid-memo:distractorNote "Processors don't guess; without `\"@type\": \"@id\"` a JSON string becomes a literal."@en .

<#q-rdf-syntaxes-6a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing, because the processor rejects the document"@en ;
    solid-memo:distractorNote "The document is valid JSON-LD; the triple is just not the link you meant."@en .

<#q-rdf-syntaxes-6a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A blank node standing in for Bob"@en ;
    solid-memo:distractorNote "A plain string value produces a literal, not a blank node."@en .

<#q-rdf-syntaxes-6b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your app keeps compact JSON-LD documents that point to a remote context at `https://ctx.example/v1.jsonld`. The context's owner edits it so that `name` maps to a different IRI. What happens the next time your app processes those documents?"@en ;
    solid-memo:back "Their `name` values turn into triples with the new predicate"@en ;
    solid-memo:backNote "A remote context is a live dependency: if its host changes the file, your data means something else, and if the host is down, processing fails. Cache or pin the contexts you rely on."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-6b-d1> ,
                          <#q-rdf-syntaxes-6b-d2> ,
                          <#q-rdf-syntaxes-6b-d3> .

<#q-rdf-syntaxes-6b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The processor notices the change and keeps the old mapping"@en ;
    solid-memo:distractorNote "Processors apply whatever context they fetch; they don't track versions."@en .

<#q-rdf-syntaxes-6b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The processor rejects the documents as tampered with"@en ;
    solid-memo:distractorNote "JSON-LD has no built-in integrity check on remote contexts."@en .

<#q-rdf-syntaxes-6b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only documents written after the edit change meaning"@en ;
    solid-memo:distractorNote "Compact JSON stores only the key `name`; its IRI comes from the context each time."@en .

<#ch-rdf-syntaxes-7>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-rdf-syntaxes> ;
    schema:position 6 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Using JSON-LD as plain JSON: compaction and framing

One JSON-LD graph has several shapes. **Expanded** form has no context: every key is a full IRI and every value sits in an array. **Compacted** form applies a context, so keys become your own short terms. CSS 7.2 expands Turtle documents and returns JSON-LD documents as written; other servers may choose other shapes. So compact every response against **your own** context, for example with jsonld.js:

```js
import jsonld from 'jsonld';
const ctx = { name: 'http://xmlns.com/foaf/0.1/name',
  knows: { '@id': 'http://xmlns.com/foaf/0.1/knows', '@type': '@id' } };
const res = await fetch(url, { headers: { Accept: 'application/ld+json' } });
const doc = await jsonld.compact(await res.json(), ctx);
```

---

For a one-subject Turtle document in the pod `https://alice.example/`, CSS 7.2 (2026) returns:

```json
[{ "@id": "https://alice.example/public/me.ttl#me",
   "http://xmlns.com/foaf/0.1/name": [{ "@value": "Alice" }],
   "http://xmlns.com/foaf/0.1/knows": [{ "@id": "https://bob.example.org/profile#me" }] }]
```

After `jsonld.compact` (jsonld.js 9.0):

```json
{ "@context": { … },
  "@id": "https://alice.example/public/me.ttl#me",
  "knows": "https://bob.example.org/profile#me",
  "name": "Alice" }
```

Compacting the same input with `knows` left out of the context keeps `"http://xmlns.com/foaf/0.1/knows": { "@id": "https://bob.example.org/profile#me" }`. Undefined properties stay as full IRIs; keep them when writing back.

---

A document with several subjects (a profile) compacts to `{ "@graph": [ … ] }`, so `doc.name` is undefined: find your node by its `@id`. Compaction also turns one-element arrays into plain values, so a key may hold a value or an array. For a nested tree (a note with its author inside), use framing: `jsonld.frame(doc, frame)` picks nodes "by example" and nests related ones. On CSS 7.2, framing a profile with `{ "@context": ctx, "@id": webId }` returns the WebID's node, so `doc.name` is set."""@en ;
    solid-memo:checkedBy <#q-rdf-syntaxes-7a> ,
                         <#q-rdf-syntaxes-7b> .

<#q-rdf-syntaxes-7a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On Community Solid Server 7.2 (2026), your app GETs a note stored as Turtle with `Accept: application/ld+json`, parses it with `JSON.parse` and reads `data[0].title`. It gets `undefined`, though the note has a title. Why?"@en ;
    solid-memo:back "The response is expanded; compact it against your context first"@en ;
    solid-memo:backNote "CSS 7.2 converts a Turtle document to expanded JSON-LD, where keys are full IRIs such as `http://purl.org/dc/terms/title`. Compacting with your own context gives you the short keys your code expects, whatever shape the server chose."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-7a-d1> ,
                          <#q-rdf-syntaxes-7a-d2> ,
                          <#q-rdf-syntaxes-7a-d3> .

<#q-rdf-syntaxes-7a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "CSS drops some triples when it converts Turtle to JSON-LD"@en ;
    solid-memo:distractorNote "Conversion keeps every triple; only the shape of the text differs."@en .

<#q-rdf-syntaxes-7a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "CSS returns JSON-LD only for documents stored as JSON-LD"@en ;
    solid-memo:distractorNote "CSS 7.2 converts Turtle to JSON-LD on request; it is the shape that differs."@en .

<#q-rdf-syntaxes-7a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The `title` key is only created by framing, not compaction"@en ;
    solid-memo:distractorNote "Compaction alone maps the full IRI to your `title` term."@en .

<#q-rdf-syntaxes-7b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "After compacting a JSON-LD profile against a context that defines only `name`, your app also sees a key `http://xmlns.com/foaf/0.1/knows`. What is it, and what should the app do when it writes the profile back?"@en ;
    solid-memo:back "A real triple your context doesn't name; write it back unchanged"@en ;
    solid-memo:backNote "Compaction only renames what your context defines; everything else stays, under its full IRI. Keep those keys when you write back, or you erase data other apps rely on."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-7b-d1> ,
                          <#q-rdf-syntaxes-7b-d2> ,
                          <#q-rdf-syntaxes-7b-d3> .

<#q-rdf-syntaxes-7b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Leftover noise from compaction; delete it before saving"@en ;
    solid-memo:distractorNote "It is a triple from the document; dropping it deletes another app's data."@en .

<#q-rdf-syntaxes-7b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An error: the context must define every key it meets"@en ;
    solid-memo:distractorNote "Compaction keeps undefined properties as full IRIs instead of failing."@en .

<#q-rdf-syntaxes-7b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Server metadata that the server rebuilds on every write"@en ;
    solid-memo:distractorNote "It is part of the document's own data, which a full write replaces."@en .

<#ch-rdf-syntaxes-8>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-rdf-syntaxes> ;
    schema:position 7 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## N-Triples

N-Triples is the simplest RDF syntax: one triple per line, written out in full and ending with `.`. It has no prefixes, no `;` or `,` shortcuts and no relative IRIs: every IRI is absolute. It is a subset of Turtle, so any Turtle parser can read it; the reverse is not true. Literals use the double-quoted form with the datatype IRI in full, and none of Turtle's shortcuts: no bare numbers or `true`/`false`, and no `'…'` or `""\"…""\"` strings.

---

A converter shows the difference. This N3.js 2.13 script parses a short Turtle document, including a bare number, against the document's URL:

```js
import { Parser, Writer } from 'n3';
const turtle = `@prefix foaf: <http://xmlns.com/foaf/0.1/> .
<#me> a foaf:Person ; foaf:name "Alice" ;
  foaf:knows <https://bob.example.org/profile#me> .
<#me> <http://example.org/childCount> 2 .`;
const quads = new Parser({ baseIRI: 'https://alice.example/profile/card' }).parse(turtle);
console.log(new Writer({ format: 'N-Triples' }).quadsToString(quads));
```

It prints:

```text
<https://alice.example/profile/card#me> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://xmlns.com/foaf/0.1/Person> .
<https://alice.example/profile/card#me> <http://xmlns.com/foaf/0.1/name> "Alice" .
<https://alice.example/profile/card#me> <http://xmlns.com/foaf/0.1/knows> <https://bob.example.org/profile#me> .
<https://alice.example/profile/card#me> <http://example.org/childCount> "2"^^<http://www.w3.org/2001/XMLSchema#integer> .
```

Without `baseIRI`, the subjects stay `<#me>`, which is not valid N-Triples (Step 3.3).

Because each line stands alone, N-Triples suits diffs, streaming, `sort` and `grep`, and test fixtures. Its dataset counterpart, N-Quads, appears in the next step."""@en ;
    solid-memo:checkedBy <#q-rdf-syntaxes-8a> ,
                         <#q-rdf-syntaxes-8b> .

<#q-rdf-syntaxes-8a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Is the line `<#me> foaf:name \"Alice\" .` valid N-Triples?"@en ;
    solid-memo:back "No: it needs full absolute IRIs"@en ;
    solid-memo:backNote "N-Triples drops prefixes, `;`, `,` and relative IRIs. The line must spell out the subject's and the predicate's full IRIs, such as `<http://xmlns.com/foaf/0.1/name>`."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-8a-d1> ,
                          <#q-rdf-syntaxes-8a-d2> ,
                          <#q-rdf-syntaxes-8a-d3> .

<#q-rdf-syntaxes-8a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Yes: any line of valid Turtle is valid N-Triples"@en ;
    solid-memo:distractorNote "N-Triples is a subset of Turtle, not the other way round."@en .

<#q-rdf-syntaxes-8a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Yes, if the file first declares `@base`"@en ;
    solid-memo:distractorNote "N-Triples has no `@base` or `@prefix` directives."@en .

<#q-rdf-syntaxes-8a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "No: N-Triples can't hold literals like `\"Alice\"`"@en ;
    solid-memo:distractorNote "N-Triples can hold literals; it only spells them out in full."@en .

<#q-rdf-syntaxes-8b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front """N3.js parses this Turtle with the base `https://alice.example/profile/card` and writes it as N-Triples. How is the object `2` written?

```turtle
<#me> <http://example.org/childCount> 2 .
```"""@en ;
    solid-memo:back "`\"2\"^^<http://www.w3.org/2001/XMLSchema#integer>`" ;
    solid-memo:backNote "N-Triples has no bare numbers, so the Turtle shorthand `2` is spelled out as a typed literal with the full `xsd:integer` IRI."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-8b-d1> ,
                          <#q-rdf-syntaxes-8b-d2> ,
                          <#q-rdf-syntaxes-8b-d3> .

<#q-rdf-syntaxes-8b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`\"2\"^^<http://www.w3.org/2001/XMLSchema#decimal>`" ;
    solid-memo:distractorNote "Turtle's bare `2` is an integer; only a number with a `.`, such as `2.0`, is a decimal."@en .

<#q-rdf-syntaxes-8b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`\"2\"^^<http://www.w3.org/2001/XMLSchema#string>`" ;
    solid-memo:distractorNote "The bare `2` is a number, so its datatype is `xsd:integer`, not `xsd:string`."@en .

<#q-rdf-syntaxes-8b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`\"2\"^^xsd:integer`" ;
    solid-memo:distractorNote "N-Triples has no prefixes, so the datatype IRI is written in full."@en .

<#ch-rdf-syntaxes-9>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-rdf-syntaxes> ;
    schema:position 8 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Datasets and named graphs

An RDF dataset is one default graph plus zero or more named graphs, each a pair of a name (an IRI or blank node) and a graph. TriG extends Turtle with `GRAPH <iri> { … }` blocks, N-Quads adds an optional graph label to each N-Triples line, and JSON-LD can hold datasets too.

```trig
GRAPH <https://alice.example/profile/card> {
  <https://alice.example/profile/card#me> <http://xmlns.com/foaf/0.1/name> "Alice" .
}
```

Datasets fit Solid clients well. Each pod document is one graph at its own URL. An app that loads several documents into one store usually keeps each in its own named graph, so it still knows which document to write a change back to. This is common client practice, not a Solid Protocol rule.

⚠ Named graphs have no formal semantics: the name "is not required to denote the graph", it is only paired with it. Different systems use them for provenance, licensing or one-graph-per-source."""@en ;
    solid-memo:checkedBy <#q-rdf-syntaxes-9a> .

<#q-rdf-syntaxes-9a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "An RDF app loads five Solid pod documents into one local store. Why put each document's triples in its own named graph?"@en ;
    solid-memo:back "So the app knows which document each triple came from"@en ;
    solid-memo:backNote "Writes go to a specific document, so a client needs to remember where each triple came from. One named graph per document is a common way to do that."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-9a-d1> ,
                          <#q-rdf-syntaxes-9a-d2> ,
                          <#q-rdf-syntaxes-9a-d3> .

<#q-rdf-syntaxes-9a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Because the Solid Protocol requires clients to use TriG"@en ;
    solid-memo:distractorNote "Servers serve Turtle and JSON-LD; how a client stores data locally is its own choice."@en .

<#q-rdf-syntaxes-9a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Because two documents can't share an IRI otherwise"@en ;
    solid-memo:distractorNote "IRIs are global, so the same IRI may appear in many graphs without any conflict."@en .

<#q-rdf-syntaxes-9a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "So the server can merge the five documents on save"@en ;
    solid-memo:distractorNote "Each write goes to one document; the server never sees your local store."@en .

<#ch-rdf-syntaxes-10>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-rdf-syntaxes> ;
    schema:position 9 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## N3 and N3 Patch

Notation3 (N3) is a superset of Turtle with formulae (graphs in `{ }`), variables such as `?x`, and rules. It is a Community Group draft (Solid Protocol 0.11 cites its March 2024 version), not a W3C standard, and Solid uses it only for N3 Patch, sent as `text/n3` (applied in Steps 6.7-6.8):

```n3
@prefix solid: <http://www.w3.org/ns/solid/terms#> .
@prefix ex:    <http://www.example.org/terms#> .
_:rename a solid:InsertDeletePatch ;
  solid:where   { ?person ex:familyName "Garcia" . } ;
  solid:inserts { ?person ex:givenName "Alex" . } ;
  solid:deletes { ?person ex:givenName "Claudia" . } .
```

`?person` is a variable, as in SPARQL (Step 3.11): the server binds it by matching `where` against the document, and inserts and deletes may only use variables from `where`. `where` must match exactly one way; Step 6.8 shows what happens otherwise.

---

The patch itself may be a blank node (`_:rename`); the rule below concerns blank nodes inside `solid:inserts` and `solid:deletes`. A blank-node label is local to its document, so a patch can't use one to point at a stored node. Bind the node with a `where` variable or give it a fragment IRI such as `<#address>`.

Solid Protocol 0.11 answers 422 to a malformed patch: two patch resources, an unbound variable, or blank nodes in either formula. CSS 7.2 rejects blank nodes in either formula with 422. ⚠ The 2026 Editor's Draft allows fresh blank nodes in inserts, and NSS 6 accepts them."""@en ;
    solid-memo:checkedBy <#q-rdf-syntaxes-10a> ,
                         <#q-rdf-syntaxes-10b> .

<#q-rdf-syntaxes-10a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid pod document contains `<#me> schema:address [ schema:addressLocality \"Ghent\" ] .`. An app sends an N3 Patch whose `solid:deletes` is `{ _:a schema:addressLocality \"Ghent\" . }`. What does a server that follows Solid Protocol 0.11 do?"@en ;
    solid-memo:back "It rejects the patch, because deletes may not contain blank nodes"@en ;
    solid-memo:backNote "Blank-node labels are local to each document, so a patch can't use `_:a` to name a stored node, and the Solid Protocol forbids blank nodes in deletes. Bind the node with a variable in `where` instead, or give it an IRI such as `<#address>`."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-10a-d1> ,
                          <#q-rdf-syntaxes-10a-d2> ,
                          <#q-rdf-syntaxes-10a-d3> .

<#q-rdf-syntaxes-10a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It deletes the locality of every node in the document"@en ;
    solid-memo:distractorNote "A blank node in a patch is not a wildcard; use a variable bound in `where`."@en .

<#q-rdf-syntaxes-10a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It deletes the triple whose node is labelled `_:a` in the file"@en ;
    solid-memo:distractorNote "Labels are local to each document, and the stored node has no label to match."@en .

<#q-rdf-syntaxes-10a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It treats `_:a` as the variable `?a` and deletes the match"@en ;
    solid-memo:distractorNote "Blank nodes and variables differ; a variable such as `?a` must also be bound in `solid:where`."@en .

<#q-rdf-syntaxes-10b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front """A Solid server receives this N3 Patch. How does it know which node `?person` stands for?

```n3
_:rename a solid:InsertDeletePatch ;
  solid:where   { ?person ex:familyName "Garcia" . } ;
  solid:inserts { ?person ex:givenName "Alex" . } ;
  solid:deletes { ?person ex:givenName "Claudia" . } .
```"""@en ;
    solid-memo:back "It matches `where` against the document"@en ;
    solid-memo:backNote "N3 Patch variables work like SPARQL variables: the server matches the `where` patterns against the document, which must give exactly one binding, and reuses it in inserts and deletes."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-10b-d1> ,
                          <#q-rdf-syntaxes-10b-d2> ,
                          <#q-rdf-syntaxes-10b-d3> .

<#q-rdf-syntaxes-10b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It applies the inserts and deletes to every subject"@en ;
    solid-memo:distractorNote "A variable takes only the value found by matching `where`, which must match exactly once."@en .

<#q-rdf-syntaxes-10b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The client must swap `?person` for a real IRI first"@en ;
    solid-memo:distractorNote "Variables are part of N3 Patch; the server binds them itself."@en .

<#q-rdf-syntaxes-10b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It creates a new node, as for a blank node `_:person`"@en ;
    solid-memo:distractorNote "`?person` is a variable, not a blank node; it names a node that already exists."@en .

<#ch-rdf-syntaxes-11>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-rdf-syntaxes> ;
    schema:position 10 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## SPARQL in one step

**SPARQL** is the W3C query language for RDF. SPARQL 1.1 is the current Recommendation; 1.2 is a Working Draft as of October 2026. A query is a set of **triple patterns** written like Turtle, with **variables** that start with `?`, just like N3 Patch's (Step 3.10). The engine finds every way to fill them so all patterns match:

```sparql
PREFIX ex: <https://vocab.example.org/memo#>
SELECT ?card ?front ?back WHERE {
  ?card a ex:Card ; ex:front ?front .
  OPTIONAL { ?card ex:back ?back }
}
```

`a` and `;` work as in Turtle (Step 3.2). A `SELECT` returns a table: each **row** binds the variables to one match. Data may be missing: a plain pattern drops rows that lack the triple, while `OPTIONAL` keeps them with the variable unbound.

---

Two more forms appear later. A **property path** follows a link repeatedly: `?a ex:parent+ ?b` matches every ancestor of `?a` (`+` is one or more steps, `*` zero or more); Step 4.9 uses `skos:broader+` this way. **SPARQL Update** changes data. Its simplest forms, `INSERT DATA` and `DELETE DATA`, list exact triples to add and remove, with no variables; other forms add a `WHERE` clause with variables. Step 6.9 uses it:

```sparql
PREFIX ex: <https://vocab.example.org/memo#>
DELETE DATA { <#c1> ex:front "Hi" } ;
INSERT DATA { <#c1> ex:front "Hello" }
```

Step 12.12 shows how to query pod documents."""@en ;
    solid-memo:checkedBy <#q-rdf-syntaxes-11a> ,
                         <#q-rdf-syntaxes-11b> .

<#q-rdf-syntaxes-11a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front """What does this SPARQL query return?

```sparql
SELECT ?card ?front ?back WHERE {
  ?card a ex:Card ; ex:front ?front .
  OPTIONAL { ?card ex:back ?back }
}
```"""@en ;
    solid-memo:back "One row per match, giving values for `?card`, `?front` and `?back`"@en ;
    solid-memo:backNote "A SELECT query returns a table: each row binds the query's variables to values that make every pattern match."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-11a-d1> ,
                          <#q-rdf-syntaxes-11a-d2> ,
                          <#q-rdf-syntaxes-11a-d3> .

<#q-rdf-syntaxes-11a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A new Turtle document holding only the matching cards"@en ;
    solid-memo:distractorNote "That is what a CONSTRUCT query does; SELECT returns rows of variable bindings."@en .

<#q-rdf-syntaxes-11a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "True or false, depending on whether any card exists"@en ;
    solid-memo:distractorNote "That is an ASK query; SELECT returns the matches themselves."@en .

<#q-rdf-syntaxes-11a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The list of documents in which the cards are stored"@en ;
    solid-memo:distractorNote "SELECT returns values bound to the variables, not where they came from."@en .

<#q-rdf-syntaxes-11b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front """Why is `ex:back` inside `OPTIONAL` in this SPARQL query?

```sparql
SELECT ?card ?front ?back WHERE {
  ?card a ex:Card ; ex:front ?front .
  OPTIONAL { ?card ex:back ?back }
}
```"""@en ;
    solid-memo:back "So cards with no back triple still appear in the results"@en ;
    solid-memo:backNote "A missing triple just means the value isn't known. OPTIONAL keeps rows that lack the value instead of dropping them."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-11b-d1> ,
                          <#q-rdf-syntaxes-11b-d2> ,
                          <#q-rdf-syntaxes-11b-d3> .

<#q-rdf-syntaxes-11b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "So the server skips loading backs to save bandwidth"@en ;
    solid-memo:distractorNote "OPTIONAL is evaluated by the query engine and changes no network behaviour."@en .

<#q-rdf-syntaxes-11b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "So cards without a back are reported as invalid data"@en ;
    solid-memo:distractorNote "OPTIONAL keeps those rows; it does not validate anything."@en .

<#q-rdf-syntaxes-11b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "So the query also matches cards from other vocabularies"@en ;
    solid-memo:distractorNote "Only the `ex:` predicates are matched; OPTIONAL just tolerates a missing value."@en .

<#ch-rdf-syntaxes-12>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-rdf-syntaxes> ;
    schema:position 11 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## RDF 1.2 (what's coming)

RDF 1.2 is the next version of RDF. Its main addition is the triple term: a triple used as the object of another triple, written `<<( s p o )>>` in Turtle 1.2. A triple term names a claim without asserting it, so the data does not say the claim is true. Statements about the claim hang off a resource linked to the triple term with `rdf:reifies`.

---

Annotation syntax, written `{| … |}` after a triple, asserts the triple and describes it at once:

```turtle
@prefix :        <#> .
@prefix rdf:     <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix foaf:    <http://xmlns.com/foaf/0.1/> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix xsd:     <http://www.w3.org/2001/XMLSchema#> .

:bob foaf:knows :alice {| dcterms:date "2024-05-01"^^xsd:date |} .  # asserted, with a date
:claim rdf:reifies <<( :carol foaf:knows :alice )>> .               # only named
```

The first line says Bob knows Alice. The second says nothing about whether Carol does.

⚠ As of October 2026, RDF 1.2 Concepts is a Candidate Recommendation (April 2026) and Turtle 1.2 a Working Draft; RDF 1.1 (2014) is still the Recommendation. The Solid Protocol doesn't require any RDF 1.2 feature, so don't rely on it in pods yet."""@en ;
    solid-memo:checkedBy <#q-rdf-syntaxes-12a> ,
                         <#q-rdf-syntaxes-12b> .

<#q-rdf-syntaxes-12a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Turtle 1.2, which single line asserts that Dana knows Erik and also gives `:party` as the `dcterms:source` of that claim?"@en ;
    solid-memo:back "`:dana foaf:knows :erik {| dcterms:source :party |} .`" ;
    solid-memo:backNote "Annotation syntax asserts the triple and describes it. A triple term only talks about the claim, and a string or an N3 formula asserts nothing in RDF."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-12a-d1> ,
                          <#q-rdf-syntaxes-12a-d2> ,
                          <#q-rdf-syntaxes-12a-d3> .

<#q-rdf-syntaxes-12a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`:c1 rdf:reifies <<( :dana foaf:knows :erik )>> ; dcterms:source :party .`" ;
    solid-memo:distractorNote "A triple term only names the claim; it doesn't assert it."@en .

<#q-rdf-syntaxes-12a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`:c1 :text \":dana foaf:knows :erik\" ; dcterms:source :party .`" ;
    solid-memo:distractorNote "That object is just a string literal; no `foaf:knows` triple results."@en .

<#q-rdf-syntaxes-12a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`{ :dana foaf:knows :erik } dcterms:source :party .`" ;
    solid-memo:distractorNote "That is an N3 formula, which quotes a graph and isn't Turtle."@en .

<#q-rdf-syntaxes-12b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Should a Solid app written in October 2026 store RDF 1.2 triple terms in users' pods?"@en ;
    solid-memo:back "Not yet: servers and libraries may not parse them"@en ;
    solid-memo:backNote "In October 2026 RDF 1.2 Concepts was a Candidate Recommendation and Turtle 1.2 a Working Draft, and pod support depends on each server's RDF library. Treat RDF 1.2 as coming, not as something to build on."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-12b-d1> ,
                          <#q-rdf-syntaxes-12b-d2> ,
                          <#q-rdf-syntaxes-12b-d3> .

<#q-rdf-syntaxes-12b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Yes: the Solid Protocol requires RDF 1.2 support"@en ;
    solid-memo:distractorNote "The Solid Protocol v0.11 doesn't require any RDF 1.2 features."@en .

<#q-rdf-syntaxes-12b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Yes: Turtle 1.1 parsers simply skip triple terms"@en ;
    solid-memo:distractorNote "A 1.1 parser rejects the `<<( )>>` syntax as an error."@en .

<#q-rdf-syntaxes-12b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "No: triple terms can only be written in N3"@en ;
    solid-memo:distractorNote "Turtle 1.2, TriG 1.2 and other RDF 1.2 syntaxes define triple terms."@en .

<#q-rdf-syntaxes-r01>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A Turtle file and a JSON-LD file describe Alice. When are they \"the same RDF data\"?"@en ;
    solid-memo:back "When both parse to the same set of triples"@en ;
    solid-memo:backNote "Syntaxes are just ways of writing a graph. Two documents mean the same when they produce the same triples, which is how a server can turn Turtle into JSON-LD."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-r01-d1> ,
                          <#q-rdf-syntaxes-r01-d2> ,
                          <#q-rdf-syntaxes-r01-d3> .

<#q-rdf-syntaxes-r01-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "When both use the same IRI for the subject"@en ;
    solid-memo:distractorNote "They can share a subject and still say different things about it."@en .

<#q-rdf-syntaxes-r01-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "When the JSON-LD's keys match the Turtle's prefixed names"@en ;
    solid-memo:distractorNote "Prefixes and keys are shorthands; only the expanded IRIs and literals count."@en .

<#q-rdf-syntaxes-r01-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "When the server can convert one into the other"@en ;
    solid-memo:distractorNote "A server can convert any RDF document; that doesn't make two different documents equal."@en .

<#q-rdf-syntaxes-r02>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Turtle `ex:height 1.68` and JSON-LD `\"height\": 1.68` (with `height` mapped to `ex:height`) appear in two documents. Do they give the same RDF triple?"@en ;
    solid-memo:back "No: Turtle gives `xsd:decimal` and JSON gives `xsd:double`"@en ;
    solid-memo:backNote "A bare Turtle number with a decimal point is `xsd:decimal`, while a JSON number with a fraction becomes `xsd:double`. To agree, write the JSON-LD as a value object with a string value, `{\"@value\": \"1.68\", \"@type\": \"xsd:decimal\"}`; a context type alone still gives the invalid `\"1.68E0\"^^xsd:decimal`."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-r02-d1> ,
                          <#q-rdf-syntaxes-r02-d2> ,
                          <#q-rdf-syntaxes-r02-d3> .

<#q-rdf-syntaxes-r02-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Yes: `1.68` is the same number in every syntax"@en ;
    solid-memo:distractorNote "The datatype is part of the literal, and the two syntaxes pick different ones."@en .

<#q-rdf-syntaxes-r02-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "No: JSON-LD turns all numbers into strings"@en ;
    solid-memo:distractorNote "JSON numbers become numeric literals, `xsd:integer` or `xsd:double`."@en .

<#q-rdf-syntaxes-r02-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Yes: both syntaxes store numbers as JavaScript numbers"@en ;
    solid-memo:distractorNote "RDF literal types are not JavaScript types; the datatype is an IRI."@en .

<#q-rdf-syntaxes-r03>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "An RDF app loads two documents into one store, and both contain the blank node label `_:b1`. How should the store treat them?"@en ;
    solid-memo:back "As two different nodes, since labels are local to each document"@en ;
    solid-memo:backNote "`_:b1` in one file and `_:b1` in another are different nodes. If something needs to be referred to from outside its document, give it an IRI such as `<#address>`."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-r03-d1> ,
                          <#q-rdf-syntaxes-r03-d2> ,
                          <#q-rdf-syntaxes-r03-d3> .

<#q-rdf-syntaxes-r03-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "As one node, since the labels are identical"@en ;
    solid-memo:distractorNote "Blank-node labels are only meaningful inside the document they appear in."@en .

<#q-rdf-syntaxes-r03-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "As an error that the app must fix by renaming one"@en ;
    solid-memo:distractorNote "RDF libraries normally give each parsed document's blank nodes fresh identities, so nothing needs renaming by hand."@en .

<#q-rdf-syntaxes-r03-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "As the same node only if both documents are on one pod"@en ;
    solid-memo:distractorNote "Blank-node scope is the document, not the server or pod."@en .

<#q-rdf-syntaxes-r04>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid pod document at `https://alice.example/todo/list.ttl` contains `<#task1>`. An app GETs it with `Accept: application/ld+json` and parses the response with the document's URL as base. Which IRI does task1 denote after parsing?"@en ;
    solid-memo:back "`https://alice.example/todo/list.ttl#task1`" ;
    solid-memo:backNote "Changing the syntax doesn't change the graph. Whether the server writes the `@id` in full or as a relative `#task1`, parsing it against the document's URL gives the same IRI the Turtle named."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-r04-d1> ,
                          <#q-rdf-syntaxes-r04-d2> ,
                          <#q-rdf-syntaxes-r04-d3> .

<#q-rdf-syntaxes-r04-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`#task1`" ;
    solid-memo:distractorNote "JSON-LD resolves a relative `@id` against the base, just as Turtle does."@en .

<#q-rdf-syntaxes-r04-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`https://alice.example/todo/list.jsonld#task1`" ;
    solid-memo:distractorNote "The IRI comes from the document's URL, not from the format the server chose."@en .

<#q-rdf-syntaxes-r04-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`https://alice.example/todo/#task1`" ;
    solid-memo:distractorNote "A fragment doesn't replace the last path segment; it is added to the whole document URL."@en .

<#q-rdf-syntaxes-r05>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "An N3 Patch's `solid:where` contains `?card ex:front \"Hi\" .`, and a SPARQL `SELECT` contains `?card ex:front ?front .`. What does `?card` do in both?"@en ;
    solid-memo:back "It is a variable, bound to nodes that make the patterns match"@en ;
    solid-memo:backNote "N3 Patch borrowed SPARQL's variables: in both, `?card` is filled in by matching the patterns against the data. SELECT returns every match as a row, while an N3 Patch must match exactly once."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-r05-d1> ,
                          <#q-rdf-syntaxes-r05-d2> ,
                          <#q-rdf-syntaxes-r05-d3> .

<#q-rdf-syntaxes-r05-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It is a blank node, local to the patch or query"@en ;
    solid-memo:distractorNote "Blank nodes are written `_:card` or `[ ]`; `?card` is a variable that matches existing nodes."@en .

<#q-rdf-syntaxes-r05-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It creates a new card each time the request runs"@en ;
    solid-memo:distractorNote "Variables find nodes already in the data; they don't create any."@en .

<#q-rdf-syntaxes-r05-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It stands for the document URL the request is sent to"@en ;
    solid-memo:distractorNote "A variable can bind to any matching node, not to the request's target."@en .

<#q-rdf-syntaxes-r06>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A server returns JSON-LD as a flat list of nodes: a note, and separately its author, linked by `@id`. Your UI wants one object with the author nested inside the note. Which jsonld.js call gives that shape?"@en ;
    solid-memo:back "`jsonld.frame(doc, frame)`" ;
    solid-memo:backNote "Compaction fixes the names of keys; framing fixes the shape of the tree, matching nodes by example and embedding related ones, then compacting with the frame's context."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-r06-d1> ,
                          <#q-rdf-syntaxes-r06-d2> ,
                          <#q-rdf-syntaxes-r06-d3> .

<#q-rdf-syntaxes-r06-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`jsonld.compact(doc, ctx)`" ;
    solid-memo:distractorNote "Compaction shortens keys and values but keeps the nodes' layout."@en .

<#q-rdf-syntaxes-r06-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`jsonld.expand(doc)`" ;
    solid-memo:distractorNote "Expansion removes the context and gives full IRIs, still as separate nodes."@en .

<#q-rdf-syntaxes-r06-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`jsonld.flatten(doc)`" ;
    solid-memo:distractorNote "Flattening does the opposite: it pulls every node out into one flat list."@en .

<#q-rdf-syntaxes-r07>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front """A Turtle document at `https://alice.example/profile/card` declares the `foaf:` prefix. Which Turtle line gives the same triple as this N-Triples line?

```text
<https://alice.example/profile/card#me> <http://xmlns.com/foaf/0.1/age> "34"^^<http://www.w3.org/2001/XMLSchema#integer> .
```"""@en ;
    solid-memo:back "`<#me> foaf:age 34 .`" ;
    solid-memo:backNote "N-Triples spells everything out; Turtle shortens it with a base, prefixes and bare numbers. A bare `34` is exactly `\"34\"^^xsd:integer`, and `<#me>` resolves to the full IRI against the document's URL."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-r07-d1> ,
                          <#q-rdf-syntaxes-r07-d2> ,
                          <#q-rdf-syntaxes-r07-d3> .

<#q-rdf-syntaxes-r07-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`<#me> foaf:age \"34\" .`" ;
    solid-memo:distractorNote "A plain quoted `\"34\"` is an `xsd:string`, not an integer."@en .

<#q-rdf-syntaxes-r07-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`<#me> foaf:age 34.0 .`" ;
    solid-memo:distractorNote "`34.0` is an `xsd:decimal`, a different literal from the integer `34`."@en .

<#q-rdf-syntaxes-r07-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`<#me> foaf:age 3.4E1 .`" ;
    solid-memo:distractorNote "A number with an exponent is an `xsd:double`, a different literal from the integer `34`."@en .

<#q-rdf-syntaxes-r08>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "An RDF app keeps triples from `https://alice.example/profile/card` and `https://alice.example/notes/a.ttl` in one store. The user edits a note. What lets the app know which Solid document to send the change to?"@en ;
    solid-memo:back "Keeping each document in a named graph named after its URL"@en ;
    solid-memo:backNote "A dataset can hold one named graph per document. Naming each graph after the document's URL tells the app which document to write the change back to."@en ;
    solid-memo:distractor <#q-rdf-syntaxes-r08-d1> ,
                          <#q-rdf-syntaxes-r08-d2> ,
                          <#q-rdf-syntaxes-r08-d3> .

<#q-rdf-syntaxes-r08-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Looking up the subject's IRI in the default graph"@en ;
    solid-memo:distractorNote "Once merged into one graph, triples no longer say which document they came from."@en .

<#q-rdf-syntaxes-r08-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Asking the server which document holds the triple"@en ;
    solid-memo:distractorNote "A Solid server serves documents; it has no lookup for where a triple lives."@en .

<#q-rdf-syntaxes-r08-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Writing the change to every document it loaded"@en ;
    solid-memo:distractorNote "That would copy the triple into documents it doesn't belong to."@en .

# Chapter 4: Semantics and vocabularies.
<#ch-semantics>
    a solid-memo:Chapter ,
      schema:Syllabus ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <> ;
    schema:position 3 ;
    dcterms:title "Semantics and vocabularies"@en ;
    dcterms:description "What vocabularies give triples, how RDFS and OWL semantics behave in an open world, and how to pick, mint and evolve vocabularies for a Solid app."@en ;
    solid-memo:reviewQuestion <#q-semantics-r01> ,
                              <#q-semantics-r02> ,
                              <#q-semantics-r03> ,
                              <#q-semantics-r04> ,
                              <#q-semantics-r05> .

<#ch-semantics-1>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-semantics> ;
    schema:position 0 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Why vocabularies matter

A triple is subject, predicate and object, and its predicates and classes are IRIs. But a triple alone says nothing about what `foaf:name` *means*. A **vocabulary** (also called an ontology or schema) is a published set of IRIs with documented meanings, so two apps that have never met can agree on what `foaf:name` or `vcard:hasEmail` stands for. The RDF 1.1 Primer names FOAF, Dublin Core, schema.org and SKOS as common examples.

In Solid, shared vocabularies are the whole basis of interoperability, and the ecosystem explicitly encourages reusing standard vocabularies. The Solid specs only fix the **infrastructure** terms: where the user's storage is, who handles their login, what a folder contains, and who may read what. The WebID Profile spec explicitly allows triples "using any predicates". So whether an app stores your name as `foaf:name` or `vcard:fn` is not decided by Solid; it is decided by the vocabularies apps choose."""@en ;
    solid-memo:checkedBy <#q-semantics-1a> .

<#q-semantics-1a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "The Solid WebID Profile spec doesn't say which predicate holds a person's name. What does that mean for a Solid app developer?"@en ;
    solid-memo:back "Apps pick a vocabulary, such as `foaf:name` or `vcard:fn`."@en ;
    solid-memo:backNote "Solid fixes infrastructure terms (storage, login, folder contents, access control) and leaves domain data to whatever vocabularies apps choose, so vocabulary choice is an interoperability decision."@en ;
    solid-memo:distractor <#q-semantics-1a-d1> ,
                          <#q-semantics-1a-d2> ,
                          <#q-semantics-1a-d3> .

<#q-semantics-1a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Apps must use `foaf:name`, because profiles are FOAF documents."@en ;
    solid-memo:distractorNote "Profiles often use FOAF, but the spec allows triples using any predicates."@en .

<#q-semantics-1a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Apps must store the name under both `foaf:name` and `vcard:fn`."@en ;
    solid-memo:distractorNote "Nothing requires both; some apps write several for compatibility, by choice."@en .

<#q-semantics-1a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The Solid Protocol defines a `solid:name` predicate for this."@en ;
    solid-memo:distractorNote "The Solid specs standardise only infrastructure terms, not domain data like names."@en .

<#ch-semantics-2>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-semantics> ;
    schema:position 1 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## RDFS in one table

RDF Schema (RDFS) is a small vocabulary for describing classes and properties. Its terms live in two namespaces: `rdf:` is `http://www.w3.org/1999/02/22-rdf-syntax-ns#` and `rdfs:` is `http://www.w3.org/2000/01/rdf-schema#`. RDF 1.2 (still a draft as of October 2026) keeps these terms and their meaning, and adds a few new ones, such as `rdf:reifies` and `rdfs:Proposition`.

| Term | Meaning |
|---|---|
| `rdfs:Class` / `rdf:Property` | The class of all classes / of all properties |
| `rdf:type` (`a` in Turtle) | This resource is an instance of that class |
| `rdfs:subClassOf` | Every instance of A is also an instance of B; transitive (A→B and B→C give A→C) |
| `rdfs:subPropertyOf` | Every pair linked by P is also linked by Q |
| `rdfs:domain` / `rdfs:range` | Subjects / objects of triples with this predicate are instances of C |
| `rdfs:label` / `rdfs:comment` | Human-readable name / description |
| `rdfs:isDefinedBy` | The resource that defines this term |

---

A tiny flashcard vocabulary (prefixes omitted):

```turtle
ex:Card      a rdfs:Class ;
             rdfs:label "Flashcard"@en .
ex:ClozeCard rdfs:subClassOf ex:Card .
ex:front     a rdf:Property ;
             rdfs:domain ex:Card ;
             rdfs:range  xsd:string ;
             rdfs:isDefinedBy <https://vocab.example.org/memo> .
```"""@en ;
    solid-memo:checkedBy <#q-semantics-2a> ,
                         <#q-semantics-2b> .

<#q-semantics-2a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "An RDFS vocabulary says `ex:front rdfs:domain ex:Card`. What does that say about a triple `X ex:front Y`?"@en ;
    solid-memo:back "X is an `ex:Card`."@en ;
    solid-memo:backNote "`rdfs:domain` describes the subjects of a property's triples, and `rdfs:range` describes the objects."@en ;
    solid-memo:distractor <#q-semantics-2a-d1> ,
                          <#q-semantics-2a-d2> ,
                          <#q-semantics-2a-d3> .

<#q-semantics-2a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Y is an `ex:Card`."@en ;
    solid-memo:distractorNote "That would be `rdfs:range`; domain is about the subject."@en .

<#q-semantics-2a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`ex:front` is a subclass of `ex:Card`."@en ;
    solid-memo:distractorNote "`ex:front` is a property; domain links it to the class of its subjects, not to a class hierarchy."@en .

<#q-semantics-2a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`ex:front` can only have string values."@en ;
    solid-memo:distractorNote "Domain is about X, not Y. Even `ex:front rdfs:range xsd:string` would only let a reasoner infer that Y is a string; it never forbids other values."@en .

<#q-semantics-2b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A pod contains `<#c7> a ex:ClozeCard .` Given `ex:ClozeCard rdfs:subClassOf ex:Card`, what does RDFS say about `<#c7>`?"@en ;
    solid-memo:back "It is also an `ex:Card`."@en ;
    solid-memo:backNote "`rdfs:subClassOf` means every instance of the subclass is an instance of the superclass."@en ;
    solid-memo:distractor <#q-semantics-2b-d1> ,
                          <#q-semantics-2b-d2> ,
                          <#q-semantics-2b-d3> .

<#q-semantics-2b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It is no longer an `ex:ClozeCard`."@en ;
    solid-memo:distractorNote "Subclassing adds a type; it never removes the original one."@en .

<#q-semantics-2b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing, because subclass triples are only documentation."@en ;
    solid-memo:distractorNote "`rdfs:subClassOf` has formal meaning: instances of the subclass are instances of the superclass."@en .

<#q-semantics-2b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It is an `ex:Card` only if it has an `ex:front`."@en ;
    solid-memo:distractorNote "Subclass membership doesn't depend on which properties the resource has."@en .

<#ch-semantics-3>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-semantics> ;
    schema:position 2 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Domain and range infer; they do not validate

RDFS semantics come as **entailment rules**. A **reasoner** is software that applies them to a graph to add the triples they license.

| Rule | If you have | You may infer |
|---|---|---|
| rdfs2 | `P rdfs:domain C . x P y .` | `x a C .` |
| rdfs3 | `P rdfs:range C . x P y .` | `y a C .` |
| rdfs7 | `P rdfs:subPropertyOf Q . x P y .` | `x Q y .` |
| rdfs9 | `A rdfs:subClassOf B . x a A .` | `x a B .` |

---

Now someone writes `<#alice> ex:front "hi" .`, where `<#alice>` is a person and `ex:front` has the domain `ex:Card`. An RDFS reasoner reports no error: by rdfs2, **Alice is a flashcard**. Domain and range describe; they don't constrain. Checking data takes a shape language such as SHACL.

Entailment is **monotonic**: adding triples only adds conclusions, never retracts them.

No Solid spec requires a server to reason; it serves the triples you wrote. So an app that needs `x a ex:Card` mustn't assume the inferred triple is in the document."""@en ;
    solid-memo:checkedBy <#q-semantics-3a> ,
                         <#q-semantics-3b> .

<#q-semantics-3a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Given `ex:front rdfs:domain ex:Card`, an app writes `<#alice> ex:front \"hi\" .` about a person. What does an RDFS reasoner do?"@en ;
    solid-memo:back "It infers that `<#alice>` is an `ex:Card`."@en ;
    solid-memo:backNote "Rule rdfs2 turns a domain declaration into a new type triple for the subject; domain and range are inference, not validation."@en ;
    solid-memo:distractor <#q-semantics-3a-d1> ,
                          <#q-semantics-3a-d2> ,
                          <#q-semantics-3a-d3> .

<#q-semantics-3a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It reports a domain violation for `<#alice>`."@en ;
    solid-memo:distractorNote "RDFS has no notion of violation for domain; it only adds conclusions."@en .

<#q-semantics-3a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It deletes the triple because Alice is a person."@en ;
    solid-memo:distractorNote "Reasoners never remove triples; entailment is monotonic."@en .

<#q-semantics-3a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It ignores the triple because `<#alice>` lacks a type."@en ;
    solid-memo:distractorNote "rdfs2 applies to every subject of `ex:front`, typed or not; it simply adds the type."@en .

<#q-semantics-3b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app fetches a pod document and looks for resources typed `ex:Card`. The document only says `<#c7> a ex:ClozeCard`, and the vocabulary says `ex:ClozeCard rdfs:subClassOf ex:Card`. What happens?"@en ;
    solid-memo:back "The app misses `<#c7>`, since only `ex:ClozeCard` is stated."@en ;
    solid-memo:backNote "Inferred triples exist only if someone computes them, so unless the app applies the subclass rule itself it must look for every class it accepts."@en ;
    solid-memo:distractor <#q-semantics-3b-d1> ,
                          <#q-semantics-3b-d2> ,
                          <#q-semantics-3b-d3> .

<#q-semantics-3b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server adds `<#c7> a ex:Card` before sending the document."@en ;
    solid-memo:distractorNote "Solid servers aren't required to reason; they serve the triples that were written."@en .

<#q-semantics-3b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The app finds `<#c7>` because `ClozeCard` contains the word `Card`."@en ;
    solid-memo:distractorNote "IRIs are compared as whole strings; their spelling carries no meaning."@en .

<#q-semantics-3b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The app finds `<#c7>` because Turtle parsers expand subclasses."@en ;
    solid-memo:distractorNote "Parsers turn text into triples; they don't apply RDFS rules."@en .

<#ch-semantics-4>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-semantics> ;
    schema:position 3 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## A little OWL

OWL 2 adds richer modelling on top of RDFS. Its namespace is `http://www.w3.org/2002/07/owl#`, written `owl:`.

- `owl:equivalentClass` / `owl:equivalentProperty`: two classes have the same instances, or two properties link the same pairs.
- `owl:inverseOf`: if A `ex:hasChild` B, then B `ex:hasParent` A.
- `owl:FunctionalProperty`: each subject has at most one value for the property.
- `owl:sameAs`: two IRIs denote the same individual, so what's said of one holds for the other.
- `owl:differentFrom`: two individuals are explicitly distinct.

```turtle
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix ex:  <https://vocab.example.org/family#> .

ex:hasParent owl:inverseOf ex:hasChild .
```

Solid apps rarely run OWL reasoners. You still need to *read* OWL, because FOAF, vCard and PROV-O, which Solid apps reuse every day, are published in it."""@en ;
    solid-memo:checkedBy <#q-semantics-4a> ,
                         <#q-semantics-4b> .

<#q-semantics-4a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A vocabulary says `ex:hasParent owl:inverseOf ex:hasChild`, and the data says `<#ann> ex:hasChild <#bo>`. What may an OWL reasoner infer?"@en ;
    solid-memo:back "`<#bo> ex:hasParent <#ann>`" ;
    solid-memo:backNote "`owl:inverseOf` lets a reasoner derive the reverse relationship, with subject and object swapped."@en ;
    solid-memo:distractor <#q-semantics-4a-d1> ,
                          <#q-semantics-4a-d2> ,
                          <#q-semantics-4a-d3> .

<#q-semantics-4a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`<#ann> ex:hasParent <#bo>`" ;
    solid-memo:distractorNote "The inverse swaps subject and object, so Bo is the one with a parent."@en .

<#q-semantics-4a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`<#ann> owl:sameAs <#bo>`" ;
    solid-memo:distractorNote "Inverse properties say nothing about identity."@en .

<#q-semantics-4a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`<#bo> ex:hasChild <#ann>`" ;
    solid-memo:distractorNote "That reverses the data with the same property, making Bo Ann's parent."@en .

<#q-semantics-4b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Why should a Solid developer learn to read OWL even if their app runs no reasoner?"@en ;
    solid-memo:back "Vocabularies it reuses, like FOAF and vCard, are written in OWL."@en ;
    solid-memo:backNote "FOAF, vCard and PROV-O are published as OWL, so understanding their axioms tells you what the terms you reuse mean."@en ;
    solid-memo:distractor <#q-semantics-4b-d1> ,
                          <#q-semantics-4b-d2> ,
                          <#q-semantics-4b-d3> .

<#q-semantics-4b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Apps must declare an OWL class for every type they write."@en ;
    solid-memo:distractorNote "RDF needs no declarations; any IRI can be used as a class."@en .

<#q-semantics-4b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The Solid Protocol requires apps to send OWL with each write."@en ;
    solid-memo:distractorNote "Writes carry ordinary RDF data; there is no such requirement."@en .

<#q-semantics-4b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "OWL replaces Turtle as the storage format for pods."@en ;
    solid-memo:distractorNote "OWL is a vocabulary for modelling, not a serialisation; pods serve Turtle and JSON-LD."@en .

<#ch-semantics-5>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-semantics> ;
    schema:position 4 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Open world

A database usually treats a missing fact as false (the **closed-world** assumption). RDF and OWL follow the **open-world** assumption: a missing fact "may simply be missing (but possibly true)". A profile with no `vcard:hasEmail` doesn't mean Alice has no email. It means this document doesn't say.

Solid makes this very concrete. Access control hides some documents, and a server may even answer 404 rather than reveal that a document exists, so data you can't read can look exactly like data that doesn't exist. An app only ever sees the documents it fetched and was allowed to read, never "everything about Alice".

So an app should phrase what it shows carefully: "no email in this profile", not "Alice has no email". When it really needs a value, it can ask the user, or look in other documents the user points it to."""@en ;
    solid-memo:checkedBy <#q-semantics-5a> .

<#q-semantics-5a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app reads Bob's profile and finds no `vcard:hasEmail`. What can it conclude?"@en ;
    solid-memo:back "This document doesn't state an email for Bob."@en ;
    solid-memo:backNote "Under the open-world assumption a missing triple means \"unknown\", and in Solid it may live in a document the app can't read."@en ;
    solid-memo:distractor <#q-semantics-5a-d1> ,
                          <#q-semantics-5a-d2> ,
                          <#q-semantics-5a-d3> .

<#q-semantics-5a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Bob has no email address."@en ;
    solid-memo:distractorNote "Under the open-world assumption a missing triple means unknown, not false."@en .

<#q-semantics-5a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The profile is invalid and should be rejected."@en ;
    solid-memo:distractorNote "A missing optional triple doesn't make RDF data invalid."@en .

<#q-semantics-5a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Bob's email is in a document the app can't read."@en ;
    solid-memo:distractorNote "That is possible, but nothing in the data tells the app it is true."@en .

<#ch-semantics-6>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-semantics> ;
    schema:position 5 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## No unique names

OWL also makes **no unique name assumption**: "OWL does not make the assumption that different names are names for different individuals". That suits the web, where people coin IRIs for the same thing without knowing it. A person may have two WebIDs, or a contact may appear in two address books under different IRIs. If they are the same, someone has to say so with `owl:sameAs`, or the app has to handle it.

This combines with the open world in surprising ways. If `ex:hasHusband` is functional and a subject has two different IRIs as husbands, an OWL reasoner doesn't report an error. It concludes that the two IRIs name the same person. Only if the data also says the two are `owl:differentFrom` does it find a contradiction."""@en ;
    solid-memo:checkedBy <#q-semantics-6a> .

<#q-semantics-6a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "`ex:hasHusband` is an `owl:FunctionalProperty`. The data says `<#eve> ex:hasHusband <#adam>` and `<#eve> ex:hasHusband <#a2>`. What does an OWL reasoner conclude?"@en ;
    solid-memo:back "`<#adam>` and `<#a2>` are the same individual."@en ;
    solid-memo:backNote "With no unique name assumption, \"at most one value\" plus two IRIs means the IRIs name one individual; it would only be a contradiction if they were stated `owl:differentFrom`."@en ;
    solid-memo:distractor <#q-semantics-6a-d1> ,
                          <#q-semantics-6a-d2> ,
                          <#q-semantics-6a-d3> .

<#q-semantics-6a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The data is inconsistent and must be rejected."@en ;
    solid-memo:distractorNote "Without a unique name assumption, two IRIs can denote one person, so there's no clash."@en .

<#q-semantics-6a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The second triple overwrites the first one."@en ;
    solid-memo:distractorNote "RDF graphs are sets of triples; reasoning never overwrites data."@en .

<#q-semantics-6a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`<#eve>` has two husbands after all."@en ;
    solid-memo:distractorNote "A functional property allows at most one value, so the values must be the same individual."@en .

<#ch-semantics-7>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-semantics> ;
    schema:position 6 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Solid's infrastructure vocabularies

A handful of vocabularies make Solid itself work. Each comes back in later chapters:

| Prefix | Namespace | Used for |
|---|---|---|
| `ldp:` | `http://www.w3.org/ns/ldp#` | Containers and `ldp:contains`, and `ldp:inbox` |
| `pim:` | `http://www.w3.org/ns/pim/space#` | `pim:storage` and `pim:preferencesFile` in profiles |
| `solid:` | `http://www.w3.org/ns/solid/terms#` | `solid:oidcIssuer` (login), N3 Patch, type indexes |
| `acl:` | `http://www.w3.org/ns/auth/acl#` | Web Access Control (WAC) rules |
| `stat:` | `http://www.w3.org/ns/posix/stat#` | File-like metadata such as `stat:size` in container listings |
| `as:` | `https://www.w3.org/ns/activitystreams#` | Change notifications; also a general vocabulary of activities and objects |

---

Only the full IRI matters, not the prefix. On Community Solid Server (CSS) 7.2 (2026), for example, container listings bind the `stat:` namespace to the prefix `posix:` and write `posix:size`.

These vocabularies also reuse each other. A WAC rule that grants public access says `acl:agentClass foaf:Agent`, using FOAF's class of all agents."""@en ;
    solid-memo:checkedBy <#q-semantics-7a> .

<#q-semantics-7a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Why does a Solid Web Access Control (WAC) rule that makes a document public contain `foaf:Agent`?"@en ;
    solid-memo:back "The access control vocabulary reuses FOAF's class of all agents."@en ;
    solid-memo:backNote "`acl:agentClass foaf:Agent` grants access to every agent, a small example of one vocabulary reusing another."@en ;
    solid-memo:distractor <#q-semantics-7a-d1> ,
                          <#q-semantics-7a-d2> ,
                          <#q-semantics-7a-d3> .

<#q-semantics-7a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only people described with FOAF profiles get access."@en ;
    solid-memo:distractorNote "`acl:agentClass foaf:Agent` means everyone, whatever vocabulary describes them."@en .

<#q-semantics-7a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "FOAF is the access control language of Solid."@en ;
    solid-memo:distractorNote "The access control vocabulary is `acl:`; it only borrows one FOAF class."@en .

<#q-semantics-7a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server converts public rules into FOAF profiles."@en ;
    solid-memo:distractorNote "Nothing is converted; the rule simply names a FOAF class."@en .

<#ch-semantics-8>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-semantics> ;
    schema:position 7 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## General vocabularies you will reuse

Beyond the infrastructure terms, most app data is written with a few general vocabularies:

| Vocabulary | Namespace | Typical terms |
|---|---|---|
| FOAF | `http://xmlns.com/foaf/0.1/` | `foaf:name`, `foaf:knows` |
| vCard | `http://www.w3.org/2006/vcard/ns#` | `vcard:fn`, `vcard:hasEmail`, `vcard:Group` |
| schema.org | `https://schema.org/` | `schema:Person`, `schema:name` |
| Dublin Core (`dcterms:`) | `http://purl.org/dc/terms/` | `dcterms:title`, `dcterms:created` |
| SKOS | `http://www.w3.org/2004/02/skos/core#` | `skos:Concept`, `skos:broader` |
| PROV-O | `http://www.w3.org/ns/prov#` | `prov:Entity`, `prov:wasAttributedTo` |
| DCAT 3 | `http://www.w3.org/ns/dcat#` | `dcat:Catalog`, `dcat:Dataset` |

---

FOAF's last version is 0.99 (2014), but it's embedded in Solid profiles, and vCard is recommended for contacts in Solid. Dublin Core comes from the Dublin Core Metadata Initiative (DCMI). It has an older namespace, `dc:` (`http://purl.org/dc/elements/1.1/`), whose terms have no formal ranges, and the newer `dcterms:`, which DCMI encourages.

Prefixes can mislead here. On CSS 7.2 (2026), resource metadata binds the prefix `dc:` to `http://purl.org/dc/terms/`, the `dcterms:` namespace. Read the prefix declaration, not the prefix."""@en ;
    solid-memo:checkedBy <#q-semantics-8a> .

<#q-semantics-8a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app records who made a document and when. It uses two vocabularies from the usual set: the metadata vocabulary made for a document's title, creator and dates, and the W3C ontology for tracing in depth where data came from. Which two?"@en ;
    solid-memo:back "Dublin Core and PROV-O."@en ;
    solid-memo:backNote "Dublin Core is the document-metadata vocabulary, with creators and dates (`dcterms:creator`, `dcterms:created`), and PROV-O is the W3C provenance ontology (`prov:Entity`, `prov:wasAttributedTo`). Others can record creator and date too, such as schema.org (`schema:creator`, `schema:dateCreated`) and Activity Streams (`as:attributedTo`, `as:published`), but neither is the dedicated metadata or provenance vocabulary."@en ;
    solid-memo:distractor <#q-semantics-8a-d1> ,
                          <#q-semantics-8a-d2> ,
                          <#q-semantics-8a-d3> .

<#q-semantics-8a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "SKOS and vCard."@en ;
    solid-memo:distractorNote "SKOS organises topics and vCard describes contacts; neither records who made a document or when."@en .

<#q-semantics-8a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "FOAF and SKOS."@en ;
    solid-memo:distractorNote "FOAF describes people and SKOS organises topics; neither records when a document was made."@en .

<#q-semantics-8a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "FOAF and vCard."@en ;
    solid-memo:distractorNote "Both describe people and their contact details; neither records when a document was made."@en .

<#ch-semantics-9>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-semantics> ;
    schema:position 8 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Two traps in popular vocabularies

**Two schemes.** Both `http://schema.org/` and `https://schema.org/` are in use, and schema.org says both are fine. To RDF they are different IRIs, so a reader should accept both. As of October 2026, for example, the Linked Open Vocabularies (LOV) catalogue lists schema.org's namespace as `http://schema.org/`, while the table in the previous step uses `https://schema.org/`. Also, schema.org's expected types are "closer to 'guidelines' than to formal rules"; where a Person is expected you may get a text string.

---

**SKOS hierarchies.** `skos:broader` links a concept to its direct parent, and it is **not** transitive. SKOS defines `skos:broaderTransitive` as a transitive superproperty of `skos:broader`, but by convention it is "not used to make assertions"; it exists so that a reasoner can infer the full chain. Pods therefore hold only direct links (`skos:broader` / `skos:narrower`). With no reasoner, your app follows `skos:broader` hop by hop to get every ancestor. In SPARQL, the property path `skos:broader+` means one or more hops."""@en ;
    solid-memo:checkedBy <#q-semantics-9a> ,
                         <#q-semantics-9b> .

<#q-semantics-9a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app looks for `https://schema.org/name`, but another app wrote `http://schema.org/name`. What happens?"@en ;
    solid-memo:back "They don't match; read both forms to be safe."@en ;
    solid-memo:backNote "schema.org accepts both schemes, but to RDF they are different IRIs, so robust readers accept both."@en ;
    solid-memo:distractor <#q-semantics-9a-d1> ,
                          <#q-semantics-9a-d2> ,
                          <#q-semantics-9a-d3> .

<#q-semantics-9a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "They match because RDF ignores the scheme."@en ;
    solid-memo:distractorNote "IRIs are compared as whole strings, so http and https are different predicates."@en .

<#q-semantics-9a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "They match if both files bind the prefix `schema:`."@en ;
    solid-memo:distractorNote "A prefix is only shorthand; it expands to whichever full IRI it was bound to."@en .

<#q-semantics-9a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The http form is invalid and no app writes it."@en ;
    solid-memo:distractorNote "schema.org says both forms are fine, and both appear in real data."@en .

<#q-semantics-9b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A pod says `:French skos:broader :Languages` and `:Languages skos:broader :Humanities`. An app without a reasoner must list every topic under `:Humanities`, including `:French`. What should it do?"@en ;
    solid-memo:back "Follow `skos:broader` links repeatedly."@en ;
    solid-memo:backNote "`skos:broader` gives direct parents only; `skos:broaderTransitive` is for inference, so an app without a reasoner walks the `broader` chain itself."@en ;
    solid-memo:distractor <#q-semantics-9b-d1> ,
                          <#q-semantics-9b-d2> ,
                          <#q-semantics-9b-d3> .

<#q-semantics-9b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Query `skos:broader` once; it is transitive."@en ;
    solid-memo:distractorNote "`broader` isn't transitive, so one hop finds only `:Languages`."@en .

<#q-semantics-9b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Query the `skos:broaderTransitive` triples in the pod."@en ;
    solid-memo:distractorNote "By convention nobody writes them; they exist only if a reasoner infers them."@en .

<#q-semantics-9b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Query `rdfs:subClassOf` instead."@en ;
    solid-memo:distractorNote "SKOS concepts are individuals linked by SKOS properties, not classes."@en .

<#ch-semantics-10>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-semantics> ;
    schema:position 9 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Reuse first, mint last, and how to find terms

The W3C Data on the Web Best Practices say (BP15): "Use terms from shared vocabularies, preferably standardized ones". Solid guidance agrees: mint a custom vocabulary only for a domain "for which nothing else exists".

A practical checklist:
1. A Solid infrastructure term (`ldp:`, `pim:`, `solid:`, `acl:`)? Use it.
2. What do other Solid apps already write? As of October 2026, the Solid Data Modules package read/write code for bookmarks, chats and contacts, with profiles and tasks in progress, so their code shows the community's conventions.
3. A W3C, DCMI or schema.org term? Search Linked Open Vocabularies (LOV), which as of October 2026 indexes over 900 vocabularies and searches their terms, or schema.org's type list. prefix.cc maps a prefix to its namespace, but its certificate expired on 31 December 2025 and was still expired in October 2026; use LOV's vocabulary pages for prefixes instead, and don't click through a browser warning.
4. Only then mint your own, linked with `rdfs:subClassOf` or `rdfs:subPropertyOf`.

---

In October 2026, a LOV term search for `due date` listed, among its first results:

| Term | IRI | Label |
|---|---|---|
| `ocds:dueDate` | `http://purl.org/onto-ocds/ocds#dueDate` | Due date |
| `lto:P3013` | `https://w3id.org/lto#P3013` | due date |
| `ncal:due` | `http://www.semanticdesktop.org/ontologies/2007/04/02/ncal#due` | due |

Read a candidate's vocabulary before reusing it. Skipping all this costs interoperability: if one contacts app writes `vcard:fn` and another reads only `schema:name`, each sees an empty address book in the same pod."""@en ;
    solid-memo:checkedBy <#q-semantics-10a> ,
                         <#q-semantics-10b> .

<#q-semantics-10a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app saves bookmarks and needs a term for the bookmarked page's address. No Solid infrastructure term fits. Following reuse-first practice, where do you look next?"@en ;
    solid-memo:back "At what other Solid apps already write for bookmarks."@en ;
    solid-memo:backNote "Data other Solid apps already write is what yours must interoperate with, so their conventions (for bookmarks, the Solid Data Modules' code) come before general searches in LOV or schema.org."@en ;
    solid-memo:distractor <#q-semantics-10a-d1> ,
                          <#q-semantics-10a-d2> ,
                          <#q-semantics-10a-d3> .

<#q-semantics-10a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "At prefix.cc, which explains what each term means."@en ;
    solid-memo:distractorNote "prefix.cc maps prefixes to namespaces; it doesn't explain terms."@en .

<#q-semantics-10a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nowhere; mint `ex:url` and let other apps map it."@en ;
    solid-memo:distractorNote "Minting is the last step, after checking what already exists."@en .

<#q-semantics-10a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "At the Solid Protocol, which defines app data terms."@en ;
    solid-memo:distractorNote "Solid only standardises infrastructure terms, not domain data."@en .

<#q-semantics-10b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid flashcard app needs a \"review interval\" property, and no existing vocabulary has one. What's the best practice?"@en ;
    solid-memo:back "Mint it in your own namespace and document it."@en ;
    solid-memo:backNote "Reuse when a term really fits; when nothing exists, mint a term in a namespace you control, with labels and definitions."@en ;
    solid-memo:distractor <#q-semantics-10b-d1> ,
                          <#q-semantics-10b-d2> ,
                          <#q-semantics-10b-d3> .

<#q-semantics-10b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Reuse `foaf:age` because it is also a number."@en ;
    solid-memo:distractorNote "Reusing a term with a different meaning corrupts the data for every app that knows FOAF."@en .

<#q-semantics-10b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Store it in a plain JSON field beside the RDF."@en ;
    solid-memo:distractorNote "That hides it from every RDF reader and isn't Linked Data."@en .

<#q-semantics-10b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Add it to the `solid:` namespace yourself."@en ;
    solid-memo:distractorNote "You don't control that namespace, and it's for infrastructure terms."@en .

<#ch-semantics-11>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-semantics> ;
    schema:position 10 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Choosing a namespace

The W3C's Best Practice Recipes for Publishing RDF Vocabularies put it this way: "The choice of URI namespace is a fundamental decision you make early in the design of your vocabulary." With a **hash namespace** (`…/vocab#Term`, like SKOS) the whole vocabulary is one document, which suits small vocabularies. With a **slash namespace** (`…/vocab/Term`, like FOAF) each term can be served on its own, which suits large or fast-changing ones. Slash IRIs are usually served with a 303 redirect or content negotiation. Give every term `rdfs:label`, `rdfs:comment` and `rdfs:isDefinedBy`.

Term IRIs end up in every pod that ever used them, so host them on a domain you'll control for decades. As of October 2026 the `shapetrees.org` address of the Shape Trees spec redirects to an unrelated website, and the spec now lives on GitHub. The Solid technical reports index still links the old address, which shows how far a dead domain spreads."""@en ;
    solid-memo:checkedBy <#q-semantics-11a> ,
                         <#q-semantics-11b> .

<#q-semantics-11a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "You are publishing an RDF vocabulary of 2,000 terms that changes every month. Which namespace style fits?"@en ;
    solid-memo:back "Slash, so each term can be served on its own."@en ;
    solid-memo:backNote "The W3C recipes for publishing vocabularies recommend hash namespaces for small vocabularies and slash namespaces for large or frequently changing ones."@en ;
    solid-memo:distractor <#q-semantics-11a-d1> ,
                          <#q-semantics-11a-d2> ,
                          <#q-semantics-11a-d3> .

<#q-semantics-11a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Hash, so the whole vocabulary is one document."@en ;
    solid-memo:distractorNote "Every lookup would then fetch all 2,000 terms; hash suits small vocabularies."@en .

<#q-semantics-11a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Hash, because slash IRIs aren't allowed in RDF."@en ;
    solid-memo:distractorNote "Both are ordinary IRIs; RDF accepts either."@en .

<#q-semantics-11a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Either; you can switch styles later."@en ;
    solid-memo:distractorNote "Term IRIs end up in data, so the style is fixed once they are used."@en .

<#q-semantics-11b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Why does the domain that hosts an RDF vocabulary matter so much?"@en ;
    solid-memo:back "Its term IRIs stay in pod data for decades."@en ;
    solid-memo:backNote "Once data uses your IRIs they can't be changed, so a lost domain leaves those terms undocumented, as happened to the Shape Trees spec's old `shapetrees.org` address."@en ;
    solid-memo:distractor <#q-semantics-11b-d1> ,
                          <#q-semantics-11b-d2> ,
                          <#q-semantics-11b-d3> .

<#q-semantics-11b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Apps look up the domain's owner before trusting the terms."@en ;
    solid-memo:distractorNote "Apps match term IRIs as strings; no ownership check happens."@en .

<#q-semantics-11b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Each read of a triple fetches the vocabulary online."@en ;
    solid-memo:distractorNote "Apps match IRIs as strings and seldom dereference them."@en .

<#q-semantics-11b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only W3C domains may host RDF vocabularies."@en ;
    solid-memo:distractorNote "Anyone can publish a vocabulary on a domain they control."@en .

<#ch-semantics-12>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-semantics> ;
    schema:position 11 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Evolving a vocabulary

Never delete or redefine a term; mark it `owl:deprecated true` and point to its replacement. The Solid terms vocabulary does exactly this for `solid:inbox`, deprecated in favour of `ldp:inbox`. Fetched as Turtle from `http://www.w3.org/ns/solid/terms` in October 2026, the term reads (prefixes omitted; in this vocabulary `dc:` is bound to `http://purl.org/dc/terms/`, the `dcterms:` namespace):

```turtle
solid:inbox
    owl:deprecated true ;
    a rdf:Property ;
    dc:issued "2015-11-16"^^xsd:date ;
    dc:modified "2016-02-05"^^xsd:date ;
    dc:modified "2018-10-25"^^xsd:date ;
    owl:equivalentProperty ldp:inbox ;
    rdfs:subPropertyOf ldp:inbox ;
    rdfs:comment "Deprecated pointer to a Linked Data Notifications inbox; please use http://www.w3.org/ns/ldp#inbox instead."@en ;
    rdfs:isDefinedBy <http://www.w3.org/ns/solid/terms#> ;
    rdfs:label "inbox (deprecated)"@en .
```

`owl:equivalentProperty` fits because the meaning didn't change: old `solid:inbox` data still means an inbox. The `rdfs:subPropertyOf` line lets even a plain RDFS reasoner (rule rdfs7) read old `solid:inbox` data as `ldp:inbox`. When the successor means something different, say only "use this one now" with `dcterms:isReplacedBy`.

---

Putting a version in the namespace (`…/v2#front`) is a trade-off. It makes breaking changes explicit, but it splits the data: `…/v1#front` and `…/v2#front` are different IRIs, so readers of `v1` terms don't see `v2` data. One flashcard app, for example, adds new terms to its `v1` namespace and keeps a new namespace for breaking changes only."""@en ;
    solid-memo:checkedBy <#q-semantics-12a> ,
                         <#q-semantics-12b> ,
                         <#q-semantics-12c> .

<#q-semantics-12a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A term in your published RDF vocabulary turns out to be badly designed. What should you do?"@en ;
    solid-memo:back "Mark it `owl:deprecated` and point to a replacement."@en ;
    solid-memo:backNote "Term IRIs are baked into data you don't control, so deprecate and point onward instead of deleting or redefining."@en ;
    solid-memo:distractor <#q-semantics-12a-d1> ,
                          <#q-semantics-12a-d2> ,
                          <#q-semantics-12a-d3> .

<#q-semantics-12a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Delete it from the vocabulary document."@en ;
    solid-memo:distractorNote "Existing pods still contain it, and readers lose its meaning."@en .

<#q-semantics-12a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Quietly change its meaning to the better design."@en ;
    solid-memo:distractorNote "Old data would then be read with a meaning its writers never intended."@en .

<#q-semantics-12a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Rename it and update every pod yourself."@en ;
    solid-memo:distractorNote "You can't reach every pod, and other apps still use the old IRI."@en .

<#q-semantics-12b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "You move the RDF term `ex:front` from `…/v1#front` to `…/v2#front`. An older app reads only `v1` terms. What does it see in cards written with `v2`?"@en ;
    solid-memo:back "No fronts, because `v2#front` is a different predicate."@en ;
    solid-memo:backNote "A versioned namespace mints new IRIs, so readers of the old ones silently miss the new data."@en ;
    solid-memo:distractor <#q-semantics-12b-d1> ,
                          <#q-semantics-12b-d2> ,
                          <#q-semantics-12b-d3> .

<#q-semantics-12b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The same fronts, since only the version changed."@en ;
    solid-memo:distractorNote "IRIs are compared as whole strings, so `v1#front` and `v2#front` are different predicates."@en .

<#q-semantics-12b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The fronts, once it follows a redirect to `v2`."@en ;
    solid-memo:distractorNote "Apps match IRIs in the data; they don't follow redirects to rename predicates."@en .

<#q-semantics-12b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An error telling it to upgrade."@en ;
    solid-memo:distractorNote "Nothing reports the mismatch; the data simply doesn't match its query."@en .

<#q-semantics-12c>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A new Solid app advertises the user's inbox in their profile. Which predicate should it write?"@en ;
    solid-memo:back "`ldp:inbox`" ;
    solid-memo:backNote "The Solid terms vocabulary marks `solid:inbox` as deprecated and points to `ldp:inbox`, which the WebID Profile spec uses. When reading, also accept `solid:inbox` from older profiles."@en ;
    solid-memo:distractor <#q-semantics-12c-d1> ,
                          <#q-semantics-12c-d2> ,
                          <#q-semantics-12c-d3> .

<#q-semantics-12c-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`solid:inbox`" ;
    solid-memo:distractorNote "It is deprecated in the Solid terms vocabulary in favour of `ldp:inbox`."@en .

<#q-semantics-12c-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`pim:storage`" ;
    solid-memo:distractorNote "That points to the user's storage, not to a place for messages."@en .

<#q-semantics-12c-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`solid:oidcIssuer`" ;
    solid-memo:distractorNote "That names the login provider, not a mailbox."@en .

<#q-semantics-r01>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "An RDFS vocabulary says `ex:front rdfs:domain ex:Card`, and a Solid app needs every card to have a front. A pod holds `<#c1> a ex:Card` and nothing more. What can the app conclude?"@en ;
    solid-memo:back "Only that this document states no front for `<#c1>`."@en ;
    solid-memo:backNote "RDFS and OWL describe data in an open world: a missing value is unknown and nothing in them checks it is there, so the app tests for it itself or uses a shape language such as SHACL."@en ;
    solid-memo:distractor <#q-semantics-r01-d1> ,
                          <#q-semantics-r01-d2> ,
                          <#q-semantics-r01-d3> .

<#q-semantics-r01-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The data is invalid, because the domain declaration requires a front."@en ;
    solid-memo:distractorNote "Domain only licenses inferences about subjects; it never requires anything."@en .

<#q-semantics-r01-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`<#c1>` has no front, so the card can be deleted."@en ;
    solid-memo:distractorNote "Open world: a missing triple means unknown, not false."@en .

<#q-semantics-r01-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A reasoner will add the missing front by rule rdfs2."@en ;
    solid-memo:distractorNote "rdfs2 infers a type for subjects of `ex:front`; it can't invent values."@en .

<#q-semantics-r02>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "You mint `ex:Deck` and declare `ex:Deck rdfs:subClassOf dcat:Dataset`. How do you make sure Solid apps that only know DCAT find your decks?"@en ;
    solid-memo:back "Also type each deck as `dcat:Dataset` in the data."@en ;
    solid-memo:backNote "Linking your vocabulary documents the meaning, but readers without reasoners only see triples that are written, so write the reused type too."@en ;
    solid-memo:distractor <#q-semantics-r02-d1> ,
                          <#q-semantics-r02-d2> ,
                          <#q-semantics-r02-d3> .

<#q-semantics-r02-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing else; the server infers `dcat:Dataset`."@en ;
    solid-memo:distractorNote "Solid servers aren't required to reason, so the inferred type isn't there."@en .

<#q-semantics-r02-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Use `owl:sameAs` between `ex:Deck` and `dcat:Dataset`."@en ;
    solid-memo:distractorNote "`sameAs` is for individuals, and a deck class isn't identical to all datasets."@en .

<#q-semantics-r02-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Declare `ex:Deck owl:equivalentClass dcat:Dataset` instead."@en ;
    solid-memo:distractorNote "It would also claim every dataset is a deck, and without a reasoner the `dcat:Dataset` type still isn't in the data."@en .

<#q-semantics-r03>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "One person has two WebIDs, and a Solid contacts app shows them as two contacts. What would let the app merge them?"@en ;
    solid-memo:back "An `owl:sameAs` triple between them."@en ;
    solid-memo:backNote "Identity between IRIs must be stated, and since no Solid server reasons for you, the app has to act on `owl:sameAs` itself."@en ;
    solid-memo:distractor <#q-semantics-r03-d1> ,
                          <#q-semantics-r03-d2> ,
                          <#q-semantics-r03-d3> .

<#q-semantics-r03-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing; two IRIs always mean two things."@en ;
    solid-memo:distractorNote "RDF and OWL make no unique name assumption."@en .

<#q-semantics-r03-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Two contacts having the same `foaf:name`."@en ;
    solid-memo:distractorNote "Equal names don't prove identity; two people can share one."@en .

<#q-semantics-r03-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`owl:differentFrom` between the two WebIDs."@en ;
    solid-memo:distractorNote "That states they are distinct, the opposite of what you need."@en .

<#q-semantics-r04>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your published v1 vocabulary's `ex:author` holds an author's name as a string. From now on, apps should link to the author's WebID instead. What do you do?"@en ;
    solid-memo:back "Link WebIDs with `dcterms:creator`; mark `ex:author` `owl:deprecated`, point onward with `dcterms:isReplacedBy`; read both."@en ;
    solid-memo:backNote "A WebID link means something different from a name string, so it needs another property, and `dcterms:isReplacedBy` points onward without claiming equivalence. Keep reading both, since old data stays in pods."@en ;
    solid-memo:distractor <#q-semantics-r04-d1> ,
                          <#q-semantics-r04-d2> ,
                          <#q-semantics-r04-d3> .

<#q-semantics-r04-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Change the range of `ex:author` to `foaf:Agent`, so it holds WebIDs from now on, and keep reading only the new form."@en ;
    solid-memo:distractorNote "Old data would then be read with a meaning its writers never intended."@en .

<#q-semantics-r04-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Declare `ex:author owl:equivalentProperty dcterms:creator`, and write WebIDs in either of the two properties."@en ;
    solid-memo:distractorNote "Equivalence claims the same meaning, but a WebID link is not a name string."@en .

<#q-semantics-r04-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Write the WebID as a string in `ex:author`, so old readers still work, and keep the vocabulary unchanged."@en ;
    solid-memo:distractorNote "A string is a literal, not a link, so apps can't follow it."@en .

<#q-semantics-r05>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Carol's contacts were written by a Solid app that uses `schema:name` with `http://schema.org/`. Your app reads only `vcard:fn` and lists no contacts. What is the most likely cause, and the fix?"@en ;
    solid-memo:back "A vocabulary mismatch; also read the common alternative terms."@en ;
    solid-memo:backNote "Apps that chose different vocabularies see each other's data as missing, so read the common alternatives (here `vcard:fn` and both schemes of `schema:name`), or agree on terms first."@en ;
    solid-memo:distractor <#q-semantics-r05-d1> ,
                          <#q-semantics-r05-d2> ,
                          <#q-semantics-r05-d3> .

<#q-semantics-r05-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Carol has no contacts; show an empty list."@en ;
    solid-memo:distractorNote "Open world: missing triples mean unknown, and here the names are in the data under another predicate."@en .

<#q-semantics-r05-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A server filter; ask for schema.org access."@en ;
    solid-memo:distractorNote "Servers serve the triples that were written; they don't filter by vocabulary."@en .

<#q-semantics-r05-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Missing equivalence; add `owl:equivalentProperty` to Carol's pod."@en ;
    solid-memo:distractorNote "Your app runs no reasoner, so the triple changes nothing, and you may not control her pod."@en .

# Chapter 5: Pods, storages and containers.
<#ch-pods>
    a solid-memo:Chapter ,
      schema:Syllabus ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <> ;
    schema:position 4 ;
    dcterms:title "Pods, storages and containers"@en ;
    dcterms:description "How the Solid Protocol structures a pod into storages, containers and auxiliary resources, and how apps find their way around one by following `Link` headers instead of guessing URLs."@en ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:reviewQuestion <#q-pods-r01> ,
                              <#q-pods-r02> ,
                              <#q-pods-r03> ,
                              <#q-pods-r04> ,
                              <#q-pods-r05> .

<#ch-pods-1>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-pods> ;
    schema:position 0 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## A reference pod on CSS 7.2

The Solid Protocol says how any pod behaves, but servers differ in the details. So this course shows real exchanges, recorded in October 2026 on Community Solid Server (CSS) 7.2.0, the Solid community's open-source server. It ran at `http://localhost:3000/` with one pod, for an agent called alice:

| What | URL |
|---|---|
| Her pod | `http://localhost:3000/alice/` |
| Her WebID | `http://localhost:3000/alice/profile/card#me` |

---

Her profile is public, so an anonymous request reads it. On CSS 7.2 (prefixes and some triples left out):

```http
GET /alice/profile/card HTTP/1.1
Host: localhost:3000

HTTP/1.1 200 OK
Content-Type: text/turtle
WAC-Allow: user="read",public="read"

<http://localhost:3000/alice/profile/card#me>
    solid:oidcIssuer <http://localhost:3000/>;
    a foaf:Person.
```

A request for protected data must carry a login proof, made anew for every request (Chapter 7). Without one, CSS answers `401 Unauthorized`. Examples marked "as alice" carried her proof.

Two more CSS 7.2 behaviours are worth knowing. Its default configuration keeps every account and pod in memory, so a restart loses them; `-c @css:config/file.json -f data/` stores them in files instead (Step 12.3). And it accepts `http` WebIDs only on hosts ending in `localhost`: a request to `127.0.0.1` is silently treated as anonymous."""@en ;
    solid-memo:checkedBy <#q-pods-1a> ,
                         <#q-pods-1b> .

<#q-pods-1a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front """On Community Solid Server 7.2 (2026), an anonymous `HEAD` request for alice's private container `http://localhost:3000/alice/profile/` got this response. What must the client do to read the container?

```http
HTTP/1.1 401 Unauthorized
WWW-Authenticate: Bearer scope="openid webid"
```"""@en ;
    solid-memo:back "Send it again with a login proof from an agent allowed to read it"@en ;
    solid-memo:backNote "401 means \"who are you?\": the resource needs credentials the request didn't carry. Public data, such as her profile document `/alice/profile/card`, needs none."@en ;
    solid-memo:distractor <#q-pods-1a-d1> ,
                          <#q-pods-1a-d2> ,
                          <#q-pods-1a-d3> .

<#q-pods-1a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Send it again as `GET`, since a `HEAD` request always needs a login"@en ;
    solid-memo:distractorNote "The method doesn't decide whether you must log in; the access rules of the data do."@en .

<#q-pods-1a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Send it again to `/alice/profile`, without the trailing slash"@en ;
    solid-memo:distractorNote "That is a different URL; on CSS 7.2 nothing exists there, and anonymously it also gets 401."@en .

<#q-pods-1a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Send it again with `Accept: text/turtle` to ask for a public format"@en ;
    solid-memo:distractorNote "The format asked for doesn't change who may read the resource; only credentials do."@en .

<#q-pods-1b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Community Solid Server 7.2 (2026) was started with its default configuration, `npx @solid/community-server@7`. After a restart, every account and pod on it is gone. Why?"@en ;
    solid-memo:back "The default configuration keeps all data in memory only"@en ;
    solid-memo:backNote "Starting CSS with `-c @css:config/file.json -f data/` stores data in files instead, so it survives a restart."@en ;
    solid-memo:distractor <#q-pods-1b-d1> ,
                          <#q-pods-1b-d2> ,
                          <#q-pods-1b-d3> .

<#q-pods-1b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "CSS deletes pods that nobody has logged in to for an hour"@en ;
    solid-memo:distractorNote "There is no such expiry; the data lived only in the server process."@en .

<#q-pods-1b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The login credentials expired and now hide every pod"@en ;
    solid-memo:distractorNote "Expired credentials don't hide data; the pods themselves no longer exist."@en .

<#q-pods-1b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A restart resets all access rules, making every pod private"@en ;
    solid-memo:distractorNote "Access rules lived in memory too, but the pods are gone, not hidden."@en .

<#ch-pods-2>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-pods> ;
    schema:position 1 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## The Solid Protocol as a hub spec

The Solid Protocol tells server and app builders how a pod behaves. In its own words, it "connects a set of specifications that, together, provide applications with secure and permissioned access to externally stored data in an interoperable way". Think of it as a hub: it adds few new inventions and mostly ties existing standards together: data formats such as Turtle and JSON-LD (Chapter 3), containers via Linked Data Platform (this chapter), reading and editing over HTTP, including N3 Patch (Chapter 6), login with WebID and Solid-OIDC (Chapter 7), access control with WAC and ACP (Chapters 8-9), notifications (Step 5.11, Chapter 10) and browser rules such as CORS.

---

As of October 2026 the latest published version is **v0.11.0** (12 May 2024), a Draft Community Group Report. A **v0.12.0 editor's draft** (dated 9 September 2026 when checked in October 2026) exists but is not endorsed. The protocol is "not a W3C Standard nor is it on the W3C Standards Track".

Specs use MUST (required), SHOULD (expected unless there's a good reason) and MAY (optional), so a MAY feature might be missing on a given server."""@en ;
    solid-memo:checkedBy <#q-pods-2a> ,
                         <#q-pods-2b> .

<#q-pods-2a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A pod server follows HTTP, LDP, RDF formats, WebID, access-control and notification specs. What role does the Solid Protocol play among them?"@en ;
    solid-memo:back "A hub spec tying existing web standards together for pods"@en ;
    solid-memo:backNote "The Solid Protocol connects HTTP, LDP, RDF syntaxes, WebID, Solid-OIDC, WAC and ACP, and notifications into one coherent set of rules for storages and apps."@en ;
    solid-memo:distractor <#q-pods-2a-d1> ,
                          <#q-pods-2a-d2> ,
                          <#q-pods-2a-d3> ,
                          <#q-pods-2a-d4> .

<#q-pods-2a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A new network protocol that replaces HTTP for pods"@en ;
    solid-memo:distractorNote "Solid builds on HTTP (RFC 9110 and 9112) rather than replacing it."@en .

<#q-pods-2a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "A finished W3C Recommendation that every server must pass"@en ;
    solid-memo:distractorNote "As of 2026 it is a Community Group draft, not on the W3C Standards Track."@en .

<#q-pods-2a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A JavaScript library that apps install to talk to pods"@en ;
    solid-memo:distractorNote "It is a specification; libraries such as those in Chapter 12 implement it."@en .

<#q-pods-2a-d4>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A conformance test suite that checks servers against those specs"@en ;
    solid-memo:distractorNote "It is itself a specification that states the rules; it does not test servers."@en .

<#q-pods-2b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "The Solid Protocol marks a feature as MAY. What should an app assume about it?"@en ;
    solid-memo:back "Some servers may lack it, so check before relying on it"@en ;
    solid-memo:backNote "MUST is required, SHOULD is expected unless there's a good reason, and MAY is optional, so robust apps detect MAY features (often from headers) before using them."@en ;
    solid-memo:distractor <#q-pods-2b-d1> ,
                          <#q-pods-2b-d2> ,
                          <#q-pods-2b-d3> .

<#q-pods-2b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Every server has it, but users may switch it off for their pod"@en ;
    solid-memo:distractorNote "MAY means optional for the server, so it can be missing entirely."@en .

<#q-pods-2b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It is deprecated and will be removed in the next spec version"@en ;
    solid-memo:distractorNote "MAY says nothing about deprecation; it only marks the feature as optional."@en .

<#q-pods-2b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only apps that the pod owner has approved are allowed to use it"@en ;
    solid-memo:distractorNote "MAY concerns what servers implement, not which apps may call it."@en .

<#ch-pods-3>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-pods> ;
    schema:position 2 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Pod, storage, owner, agent

"Pod" is the everyday word: "Users have personal online data stores called Pods". The specification does not use "pod" normatively. It says **storage**: "a space of URIs that affords agents controlled access to resources". In this course both words mean the same thing.

Two more defined terms:

- **Agent**: a person, social entity or software identified by a URI. A WebID denotes an agent (Chapter 2).
- **Owner**: the person or social entity with the rights and responsibilities of a storage. The owner "implicitly has control over all resources in a storage". It is set when the storage is provisioned and can be changed.

---

A server MUST provide one or more storages, and different storages on one server use non-overlapping URI space. So a pod is not a server: one server hosts many pods, and one person can have several storages, since a profile can point to several (Step 5.5).

Watch out for one trap. "A URI allocated to a WebID in a Solid storage does not imply that the WebID is the storage owner". Your profile being hosted in a pod doesn't make you its owner."""@en ;
    solid-memo:checkedBy <#q-pods-3a> ,
                         <#q-pods-3b> .

<#q-pods-3a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In a Solid pod, Alice's WebID is `https://pods.example/alice/profile/card#me`. What does that tell you about who owns the storage at `https://pods.example/alice/`?"@en ;
    solid-memo:back "Nothing: the server records ownership, not the profile's URL"@en ;
    solid-memo:backNote "Ownership is set when the storage is provisioned and tracked by the server, which may also advertise it (Step 5.6). A WebID's URL alone proves nothing about ownership."@en ;
    solid-memo:distractor <#q-pods-3a-d1> ,
                          <#q-pods-3a-d2> ,
                          <#q-pods-3a-d3> .

<#q-pods-3a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Alice must be the owner, because her profile lives inside it"@en ;
    solid-memo:distractorNote "The spec says explicitly that a WebID's location does not imply ownership."@en .

<#q-pods-3a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server operator owns it, because the domain is theirs"@en ;
    solid-memo:distractorNote "Ownership is set when the storage is provisioned, not derived from the domain."@en .

<#q-pods-3a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing yet: no one owns it until Alice writes a resource there"@en ;
    solid-memo:distractorNote "Every storage has an owner from provisioning time onward."@en .

<#q-pods-3b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "In Solid, how many storages can one server host, and how many storages can one person have?"@en ;
    solid-memo:back "One server can host many storages, and a person can have several"@en ;
    solid-memo:backNote "\"Storage\" is a space of URIs, not a machine. Servers MUST provide one or more, and profiles can point to several."@en ;
    solid-memo:distractor <#q-pods-3b-d1> ,
                          <#q-pods-3b-d2> ,
                          <#q-pods-3b-d3> ,
                          <#q-pods-3b-d4> .

<#q-pods-3b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "One server hosts exactly one storage, which belongs to its operator"@en ;
    solid-memo:distractorNote "Servers MUST provide one or more storages, and usually host many people's."@en .

<#q-pods-3b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "One server can host many storages, but a person has exactly one"@en ;
    solid-memo:distractorNote "A profile can point to several storages, on any domain."@en .

<#q-pods-3b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "A pod is a physical machine that the user runs at home"@en ;
    solid-memo:distractorNote "A pod is a URI space on a server, which a provider can host."@en .

<#q-pods-3b-d4>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "One server can host many storages, and a person's storages must all be on one server"@en ;
    solid-memo:distractorNote "A profile can point to several storages, on any domain and any server."@en .

<#ch-pods-4>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-pods> ;
    schema:position 3 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## HTTP Link headers

Solid tells apps what a URL is, and where related resources live, mainly with the HTTP **`Link` header** from RFC 8288. A link is "a typed connection between two resources": a context (the URL you requested), a relation type (`rel`), and a target URL. A response can carry several links, as separate `Link` lines or comma-separated in one header. On CSS 7.2, a `HEAD` (a GET without the body) of alice's pod root answered, among other headers:

```http
HTTP/1.1 200 OK
Link: <http://www.w3.org/ns/pim/space#Storage>; rel="type"
Link: <http://www.w3.org/ns/ldp#BasicContainer>; rel="type"
Link: <http://localhost:3000/alice/.meta>; rel="describedby"
Link: <http://localhost:3000/alice/.acl>; rel="acl"
Link: <http://localhost:3000/.well-known/solid>; rel="http://www.w3.org/ns/solid/terms#storageDescription"
```

---

Registered relation types are short names; extension types are full URIs. The rels this chapter uses:

| `rel` | Target | Step |
|---|---|---|
| `type` | What kind of resource this is | 5.5, 5.7 |
| `acl` | Its access-control document | 5.10 |
| `describedby` | Its description resource | 5.10 |
| `…/solid/terms#storageDescription` | The storage description | 5.6 |
| `…/solid/terms#owner` | The owner's WebID (optional) | 5.6 |
| `…/ldp#inbox` | Its inbox | 5.11 |

The rule: **follow links, never guess URLs**. The `.acl` and `.meta` suffixes and the `/.well-known/solid` path are one server's choices; the spec leaves such names to each server and requires them to be advertised in `Link` headers."""@en ;
    solid-memo:checkedBy <#q-pods-4a> ,
                         <#q-pods-4b> ,
                         <#q-pods-4c> .

<#q-pods-4a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app wants the access-control document for `https://pod.example/notes/a.ttl`. What should it do?"@en ;
    solid-memo:back "Request the resource and follow its `Link` with `rel=\"acl\"`"@en ;
    solid-memo:backNote "Servers MUST advertise auxiliary resources such as the ACL with Link headers, and their naming is implementation-specific, so you discover the ACL by following `rel=\"acl\"`."@en ;
    solid-memo:distractor <#q-pods-4a-d1> ,
                          <#q-pods-4a-d2> ,
                          <#q-pods-4a-d3> .

<#q-pods-4a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Append `.acl` to the URL, since every server names ACLs that way"@en ;
    solid-memo:distractorNote "The `.acl` suffix is one server's convention; others may name it differently."@en .

<#q-pods-4a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Look for a file called `acl.ttl` in the folder above it"@en ;
    solid-memo:distractorNote "No such naming rule exists; only the advertised link is reliable."@en .

<#q-pods-4a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Read the owner's WebID profile, which lists all their ACLs"@en ;
    solid-memo:distractorNote "A profile describes an agent; each resource advertises its own ACL by Link header."@en .

<#q-pods-4b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid server's response carries `Link: <http://www.w3.org/ns/pim/space#Storage>; rel=\"type\"`. What is this link's context?"@en ;
    solid-memo:back "The URL that was requested, which the header describes"@en ;
    solid-memo:backNote "A link connects a context (the resource you asked for) to a target via a relation type. Here it says \"this URL is of type `pim:Storage`\"."@en ;
    solid-memo:distractor <#q-pods-4b-d1> ,
                          <#q-pods-4b-d2> ,
                          <#q-pods-4b-d3> .

<#q-pods-4b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The `pim:Storage` URI, which the header describes"@en ;
    solid-memo:distractorNote "That is the link target; the context is the resource whose response carries the header."@en .

<#q-pods-4b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The relation type `type`, which names what is described"@en ;
    solid-memo:distractorNote "`type` is the relation; the context is the resource it is about."@en .

<#q-pods-4b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server's origin, since headers describe the whole host"@en ;
    solid-memo:distractorNote "Links in a response are about the requested resource, not the whole server."@en .

<#q-pods-4c>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Why should a Solid app follow the links and headers a server sends instead of building URLs from a known server's layout?"@en ;
    solid-memo:back "Layouts vary by server and version; headers say what's true"@en ;
    solid-memo:backNote "The spec leaves names such as the ACL's to each server and requires them to be advertised in `Link` headers. The habit also carries over to Linked Web Storage (LWS), the draft successor to the Solid Protocol (Chapter 17)."@en ;
    solid-memo:distractor <#q-pods-4c-d1> ,
                          <#q-pods-4c-d2> ,
                          <#q-pods-4c-d3> .

<#q-pods-4c-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Hard-coded URLs are forbidden by the HTTP specification itself"@en ;
    solid-memo:distractorNote "HTTP does not forbid them; the problem is that guessed URLs are often wrong."@en .

<#q-pods-4c-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Headers are faster to parse than any URL string in JavaScript"@en ;
    solid-memo:distractorNote "Speed is not the reason; correctness across servers and versions is."@en .

<#q-pods-4c-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Servers reject any request whose URL was not copied from a header"@en ;
    solid-memo:distractorNote "Servers cannot tell where a URL came from; a guessed URL simply may not exist."@en .

<#ch-pods-5>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-pods> ;
    schema:position 4 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Finding the storage

An app often holds a URL and needs to know which storage it belongs to. The protocol gives three ways:

1. **Ask the URL itself.** A storage root MUST answer with `Link: <http://www.w3.org/ns/pim/space#Storage>; rel="type"`.
2. **Walk up the path.** From `/a/b/c`, try `/a/b/`, then `/a/`, then `/`, until a response carries that link.
3. **Read RDF.** Look for a `pim:storage` triple. Nothing requires an ordinary document to contain one; in practice this is the WebID profile (Chapter 7), which may list zero or more storages:

```turtle
@prefix pim: <http://www.w3.org/ns/pim/space#> .

<https://alice.example/profile/card#me>
    pim:storage <https://alice.example/> .
```

Mind the capital letter. **`pim:Storage`** is a *class* (what a storage root is). **`pim:storage`** is a *property* linking an agent to their storage. IRIs are case-sensitive.

---

⚠ As of October 2026, a fresh CSS 7.2 profile has no `pim:storage`, so only the walk-up finds the storage. Recorded on CSS 7.2:

```text
GET  /alice/profile/card            200, no pim:storage triple
HEAD /alice/profile/                401, no rel="type" link (private)
HEAD /alice/profile/  (as alice)    200, ldp:Container types, no pim:Storage
HEAD /alice/                        200, Link: <…/pim/space#Storage>; rel="type"
```"""@en ;
    solid-memo:checkedBy <#q-pods-5a> ,
                         <#q-pods-5b> .

<#q-pods-5a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app has `https://pod.example/alice/notes/today.ttl` and no profile. How can it find the storage root?"@en ;
    solid-memo:back "Walk up the path until a response has a `pim:Storage` type link"@en ;
    solid-memo:backNote "Walking up the path and checking each response for a `pim:Storage` type link is one of the three discovery methods the Solid Protocol defines."@en ;
    solid-memo:distractor <#q-pods-5a-d1> ,
                          <#q-pods-5a-d2> ,
                          <#q-pods-5a-d3> .

<#q-pods-5a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Take the URL's origin, since the storage root is always `/`"@en ;
    solid-memo:distractorNote "A server can host many storages under different paths, so `/` may not be the root."@en .

<#q-pods-5a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Strip the last segment once, since files sit directly in the root"@en ;
    solid-memo:distractorNote "Resources can be nested several levels deep below the root."@en .

<#q-pods-5a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Follow today.ttl's `rel=\"acl\"` link, which points to the root"@en ;
    solid-memo:distractorNote "The `acl` link leads to the document's access rules, not to its storage."@en .

<#q-pods-5b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid's vocabulary, what is the difference between `pim:Storage` and `pim:storage`?"@en ;
    solid-memo:back "The first is a storage-root class; the second is a property"@en ;
    solid-memo:backNote "`pim:Storage` is the type a storage root advertises; `pim:storage` is the property a profile uses to point at a storage."@en ;
    solid-memo:distractor <#q-pods-5b-d1> ,
                          <#q-pods-5b-d2> ,
                          <#q-pods-5b-d3> .

<#q-pods-5b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "They are two spellings of the same term, and either one works"@en ;
    solid-memo:distractorNote "RDF IRIs are case-sensitive, so these are two different terms."@en .

<#q-pods-5b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The first is the newer name; the second is a deprecated alias"@en ;
    solid-memo:distractorNote "Both are current, with different jobs."@en .

<#q-pods-5b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The first is used in Turtle and the second in JSON-LD"@en ;
    solid-memo:distractorNote "The syntax doesn't change the term; both appear in both formats."@en .

<#ch-pods-6>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-pods> ;
    schema:position 5 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## The storage description

Once you know a storage, you'll want to know what it offers. Every resource in a storage links to the **storage description** with `rel="http://www.w3.org/ns/solid/terms#storageDescription"`, on GET, HEAD and OPTIONS. So one request to any URL in a pod is enough to find it.

⚠ As of October 2026, CSS 7.2 leaves this link out of `401` responses, so the request must be one you're allowed to make: an anonymous request for a private URL finds nothing to follow.

The storage description is an RDF document about the storage, including that it is a `pim:Storage`. It is also where notification services are advertised (Chapter 10). CSS serves it at `/.well-known/solid`, but that's an implementation choice: follow the link.

A server may also say who owns the storage. If it does, the root's response carries `rel="http://www.w3.org/ns/solid/terms#owner"` pointing to the owner's WebID. This link is optional, so apps can't rely on finding it.

---

On CSS 7.2 the description read, in part:

```turtle
<http://localhost:3000/> a <http://www.w3.org/ns/pim/space#Storage>;
    <http://www.w3.org/ns/solid/notifications#subscription>
        <http://localhost:3000/.notifications/WebSocketChannel2023/>,
        <http://localhost:3000/.notifications/WebhookChannel2023/>.
```

⚠ As of October 2026 it is server-wide: it names the server root, not alice's pod, as the `pim:Storage`. That clashes with the non-overlapping rule of Step 5.3, since `/alice/` is a storage too. On CSS 7, trust the type link on the pod root (Step 5.5) to find the root."""@en ;
    solid-memo:checkedBy <#q-pods-6a> .

<#q-pods-6a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app holding any URL in a pod wants to find which notification services the server offers. Which `Link` header does it follow?"@en ;
    solid-memo:back "The one with `rel=\"…#storageDescription\"`, on every resource"@en ;
    solid-memo:backNote "Every resource in a storage links to the storage description, an RDF document about the storage that also advertises notification services. ⚠ CSS 7.2 (2026) leaves the link out of `401` responses, so request a URL you may read."@en ;
    solid-memo:distractor <#q-pods-6a-d1> ,
                          <#q-pods-6a-d2> ,
                          <#q-pods-6a-d3> .

<#q-pods-6a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The one with `rel=\"type\"`, whose target is `pim:Storage`, on the root"@en ;
    solid-memo:distractorNote "That link says what the root is, not what the server offers."@en .

<#q-pods-6a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The one with `rel=\"acl\"`, which lists the storage's features"@en ;
    solid-memo:distractorNote "The ACL holds access rules for one resource, not a feature list."@en .

<#q-pods-6a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The one with `rel=\"…#owner\"`, on every resource"@en ;
    solid-memo:distractorNote "The owner link is optional, sits on the root, and names a WebID."@en .

<#ch-pods-7>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-pods> ;
    schema:position 6 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Containers and LDP

Solid's containers, folder-like resources that list others, come from **Linked Data Platform (LDP)**, a 2015 W3C Recommendation. LDP splits resources into **RDF sources** (state fully in RDF, such as a Turtle document) and **non-RDF sources** (images, PDFs, plain text). LDP has three container kinds (Basic, Direct, Indirect), but Solid uses only **Basic Containers**.

---

GET a container and you receive RDF that lists its members with `ldp:contains`. These statements are its **containment triples**. Servers SHOULD add metadata about each member, such as its size, last-modified time and media type, and protect it from edits. Exact triples vary between servers. On CSS 7.2, GET of alice's fresh pod root returned:

```turtle
@prefix dc: <http://purl.org/dc/terms/>.
@prefix ldp: <http://www.w3.org/ns/ldp#>.
@prefix posix: <http://www.w3.org/ns/posix/stat#>.
@prefix xsd: <http://www.w3.org/2001/XMLSchema#>.

<> a <http://www.w3.org/ns/pim/space#Storage>, ldp:Container, ldp:BasicContainer, ldp:Resource;
    dc:modified "2026-10-07T21:33:04.276Z"^^xsd:dateTime.
<profile/> a ldp:Container, ldp:BasicContainer, ldp:Resource;
    dc:modified "2026-10-07T21:33:04.271Z"^^xsd:dateTime.
<README> a ldp:Resource;
    dc:modified "2026-10-07T21:33:04.272Z"^^xsd:dateTime;
    <http://www.w3.org/ns/ma-ont#format> "text/markdown";
    posix:size "980".
<> ldp:contains <profile/>, <README>.
```

Recall that `<>` means "this document". ⚠ As of October 2026, CSS 7.2 binds `dc:` to the Dublin Core *terms* namespace (often written `dcterms:`) and writes `posix:` for the namespace often written `stat:`. Prefix labels are local; check each declaration."""@en ;
    solid-memo:checkedBy <#q-pods-7a> ,
                         <#q-pods-7b> .

<#q-pods-7a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A user uploads a holiday photo to their Solid pod. In Linked Data Platform (LDP) terms, what is it?"@en ;
    solid-memo:back "A non-RDF source, which the pod returns byte for byte as stored"@en ;
    solid-memo:backNote "LDP distinguishes RDF sources from non-RDF sources such as images; Solid servers return non-RDF resources as stored."@en ;
    solid-memo:distractor <#q-pods-7a-d1> ,
                          <#q-pods-7a-d2> ,
                          <#q-pods-7a-d3> .

<#q-pods-7a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An RDF source, because everything in a pod is converted to RDF"@en ;
    solid-memo:distractorNote "Pods store images, PDFs and text as they are; only their listing entry is RDF."@en .

<#q-pods-7a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A Basic Container, because it can hold image metadata inside it"@en ;
    solid-memo:distractorNote "Containers list other resources; a photo is not one."@en .

<#q-pods-7a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A Direct Container, because it has binary members of its own"@en ;
    solid-memo:distractorNote "Solid uses only Basic Containers, and a photo is not a container."@en .

<#q-pods-7b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "How does a Solid app find out what is in the container `/notes/`?"@en ;
    solid-memo:back "GET `/notes/` and read its `ldp:contains` triples"@en ;
    solid-memo:backNote "A container is an RDF source whose body lists its members with `ldp:contains`, plus server-managed metadata about each one."@en ;
    solid-memo:distractor <#q-pods-7b-d1> ,
                          <#q-pods-7b-d2> ,
                          <#q-pods-7b-d3> .

<#q-pods-7b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "GET `/notes/index.ttl`, the file every container keeps"@en ;
    solid-memo:distractorNote "No such file is defined; the container itself returns the listing."@en .

<#q-pods-7b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Send a LIST request, the HTTP method for folders"@en ;
    solid-memo:distractorNote "HTTP has no LIST method; a container is read with GET."@en .

<#q-pods-7b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Read the `Link` headers of `/notes/`, one per member"@en ;
    solid-memo:distractorNote "Members are listed in the RDF body, not in headers."@en .

<#ch-pods-8>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-pods> ;
    schema:position 7 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## A container's Last-Modified

`Last-Modified` is the HTTP header that says when a resource last changed. For containers, Solid has a surprise. The spec lets servers base a container's `Last-Modified` on changes to its **containment triples** only, meaning something was added or removed. Its note says editing a member, or anything deeper, does not change it, "to avoid instant propagation of changes all the way to the root container". The note adds that this design may be revisited in future versions.

There is a version detail too. v0.11 does not require servers to send `Last-Modified` at all. The v0.12 editor's draft, as of October 2026, adds that servers MUST send it on GET and HEAD.

Either way, don't use a container's `Last-Modified` to detect changes in a whole tree. Chapter 10 covers the tools for that."""@en ;
    solid-memo:checkedBy <#q-pods-8a> .

<#q-pods-8a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In a Solid pod, you edit `/notes/shopping.ttl`. What does the Solid Protocol let you conclude about the `Last-Modified` of the container `/notes/`?"@en ;
    solid-memo:back "It need not change: servers may count only added or removed members"@en ;
    solid-memo:backNote "A container's `Last-Modified` may reflect changes to its containment triples only, so it is not a recursive change detector."@en ;
    solid-memo:distractor <#q-pods-8a-d1> ,
                          <#q-pods-8a-d2> ,
                          <#q-pods-8a-d3> .

<#q-pods-8a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It must update, because the spec requires recursive change tracking"@en ;
    solid-memo:distractorNote "The spec requires no such thing; it lets servers count only containment changes."@en .

<#q-pods-8a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It must update, along with every container up to the root"@en ;
    solid-memo:distractorNote "The spec's note says its design avoids exactly this propagation to the root."@en .

<#q-pods-8a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It updates, but only after the server's cache has expired"@en ;
    solid-memo:distractorNote "Caching isn't involved; servers may ignore edits to members entirely."@en .

<#ch-pods-9>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-pods> ;
    schema:position 8 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Slash semantics

In Solid the URL path carries meaning. "Paths ending with a slash denote a container resource", and slashes mark hierarchy. So `https://alice.example/notes/` is a container, while `https://alice.example/notes/shopping.ttl` is a resource inside it.

Two rules follow:

- **No twins.** If two URIs differ only in the trailing slash and one of them is a resource, the other MUST NOT be a different resource. `/notes` and `/notes/` can't both exist as separate things. The server may redirect (301) from one to the other.
- **Containment mirrors the path.** "There is a 1-1 correspondence between containment triples and relative reference within the path name hierarchy." So "it is not possible to create orphan resources". When you PUT `/a/b/c.ttl`, the server creates `/a/` and `/a/b/` if needed (Chapter 6).

---

On CSS 7.2, as alice, `HEAD /alice/profile` and `HEAD /alice/profile/card/` both got `404 Not Found`: the slash twins of a container and a document don't exist, and CSS answers 404 instead of redirecting. Anonymously both got `401`, since the server checks access before saying whether anything exists.

LWS, the draft successor to the Solid Protocol (Chapter 17), drops this rule: clients "SHOULD NOT assume that URI structure reflects containment"."""@en ;
    solid-memo:checkedBy <#q-pods-9a> ,
                         <#q-pods-9b> .

<#q-pods-9a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid pod already holds a document at `/notes`. What happens with `/notes/`?"@en ;
    solid-memo:back "It may redirect to `/notes`, but can never be a second resource"@en ;
    solid-memo:backNote "Slash semantics forbids `/notes` and `/notes/` from being two different resources; the server may 301-redirect between them or, like CSS 7.2 (2026), answer 404."@en ;
    solid-memo:distractor <#q-pods-9a-d1> ,
                          <#q-pods-9a-d2> ,
                          <#q-pods-9a-d3> .

<#q-pods-9a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It becomes an independent container you can fill with documents"@en ;
    solid-memo:distractorNote "Two URIs that differ only in the trailing slash must not name different resources."@en .

<#q-pods-9a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It holds the description resource for `/notes`, by convention"@en ;
    solid-memo:distractorNote "Metadata resources are found through links (Step 5.10), not by adding a slash."@en .

<#q-pods-9a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It may become a container later, once `/notes` has been emptied"@en ;
    solid-memo:distractorNote "Emptying a document changes nothing; while `/notes` exists, `/notes/` can't be a different resource."@en .

<#q-pods-9b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Why can't a Solid pod contain an \"orphan\" resource that no container lists?"@en ;
    solid-memo:back "Containment follows the path, so each resource is listed"@en ;
    solid-memo:backNote "There is a 1-1 correspondence between containment triples and the path hierarchy, so all resources are discoverable from a container."@en ;
    solid-memo:distractor <#q-pods-9b-d1> ,
                          <#q-pods-9b-d2> ,
                          <#q-pods-9b-d3> .

<#q-pods-9b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server adds a containment triple only if the app asks for one"@en ;
    solid-memo:distractorNote "The server adds it for every new resource; no request is needed."@en .

<#q-pods-9b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Apps must manually add each new resource to its container listing"@en ;
    solid-memo:distractorNote "The server keeps containment triples itself and apps can't edit them."@en .

<#q-pods-9b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Orphans are allowed, but only the owner is permitted to see them"@en ;
    solid-memo:distractorNote "The spec says orphan resources cannot be created at all."@en .

<#ch-pods-10>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-pods> ;
    schema:position 9 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Auxiliary resources

Some resources exist only to say something about another resource, its **subject**. The Solid Protocol calls them **auxiliary resources**: they supply "descriptive metadata, authorization conditions, data shape constraints, digital rights or provenance". Two types are defined:

| Type | Link rel | Holds |
|---|---|---|
| Web Access Control (ACL) | `acl` | Who may do what with the subject (Chapter 8) |
| Description resource | `describedby` | Metadata about the subject |

Rules worth remembering:

- Servers MUST advertise them with `Link` headers, and they are RDF documents.
- A subject has **at most one** description resource, which follows the subject's authorization rules. It may link back with `rel="describes"`; ⚠ as of October 2026, CSS 7.2 doesn't send that link.
- When the subject is deleted, its auxiliary resources are deleted too.
- An auxiliary resource may even live on a different origin from its subject.

---

CSS uses the suffixes `.acl` and `.meta`, only a server convention. On CSS 7.2, alice's public profile advertised:

```http
Link: <http://localhost:3000/alice/profile/card.meta>; rel="describedby"
Link: <http://localhost:3000/alice/profile/card.acl>; rel="acl"
```

The description resource was public too, and described its subject (prefixes as in Step 5.7):

```turtle
<http://localhost:3000/alice/profile/card> <http://www.w3.org/ns/ma-ont#format> "text/turtle";
    a ldp:Resource;
    dc:modified "2026-10-07T21:33:04.266Z"^^xsd:dateTime;
    posix:size "438".
```

Its ACL answered anonymous visitors `401 Unauthorized` (Chapter 8)."""@en ;
    solid-memo:checkedBy <#q-pods-10a> ,
                         <#q-pods-10b> .

<#q-pods-10a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In a Solid pod, you delete `/notes/shopping.ttl`. What happens to its ACL and description resource?"@en ;
    solid-memo:back "The server deletes them along with the resource itself"@en ;
    solid-memo:backNote "Deleting a resource MUST also delete its auxiliary resources, so they never outlive their subject."@en ;
    solid-memo:distractor <#q-pods-10a-d1> ,
                          <#q-pods-10a-d2> ,
                          <#q-pods-10a-d3> .

<#q-pods-10a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "They stay behind as orphans until the owner removes them"@en ;
    solid-memo:distractorNote "The spec requires auxiliary resources to be deleted with their subject."@en .

<#q-pods-10a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "They move up to the parent container's auxiliary resources"@en ;
    solid-memo:distractorNote "Nothing is moved; they are deleted."@en .

<#q-pods-10a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The DELETE fails until the app has deleted them first"@en ;
    solid-memo:distractorNote "The server removes them itself as part of deleting the subject."@en .

<#q-pods-10b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "An app wants to attach a title and creator to a photo in a Solid pod as RDF, without changing the image file. Where should it write them?"@en ;
    solid-memo:back "In its description resource, found via `rel=\"describedby\"`"@en ;
    solid-memo:backNote "A description resource is the auxiliary resource for metadata about its subject, and clients find it through the `describedby` link."@en ;
    solid-memo:distractor <#q-pods-10b-d1> ,
                          <#q-pods-10b-d2> ,
                          <#q-pods-10b-d3> .

<#q-pods-10b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In the photo's ACL, which holds any RDF about the photo"@en ;
    solid-memo:distractorNote "The ACL holds authorization rules, not general metadata."@en .

<#q-pods-10b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In a file made by appending `.meta` to the photo's URL"@en ;
    solid-memo:distractorNote "`.meta` is one server's naming convention; follow `describedby` instead."@en .

<#q-pods-10b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In the container listing, by PUTting extra triples into it"@en ;
    solid-memo:distractorNote "Apps can't change a container's server-managed listing that way."@en .

<#ch-pods-11>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-pods> ;
    schema:position 10 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Inboxes in brief

Sometimes another person or app needs to tell you something: "I commented on your photo" or "here is an invitation". Solid uses **Linked Data Notifications (LDN)**, a 2017 W3C Recommendation, for this. An **inbox** is a container that works like a mailbox.

- **Discovery.** A sender finds a resource's inbox through a `Link` header with `rel="http://www.w3.org/ns/ldp#inbox"` or an `ldp:inbox` triple in its RDF. Profiles usually list one: "zero or one `ldp:inbox`".
- **Sending.** The sender POSTs the notification to the inbox, in JSON-LD unless another RDF syntax was negotiated, and gets `201 Created` or `202 Accepted`.
- **Reading.** A consumer GETs the inbox and finds the messages through `ldp:contains`, like any container listing.

---

Solid servers MUST implement the receiving side, and Solid clients the sending or consuming side. Chapter 4 noted that `solid:inbox` is deprecated in favour of `ldp:inbox`. ⚠ As of October 2026, CSS 7.2 creates no inbox; Step 9.6 shows how an app can make one.

Don't confuse this with **Solid Notifications** (Chapter 10). An LDN inbox holds messages *between agents* that wait until read. Solid Notifications push live *change events about resources* to subscribed apps."""@en ;
    solid-memo:checkedBy <#q-pods-11a> ,
                         <#q-pods-11b> .

<#q-pods-11a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid, Bob's app wants to tell Alice that he shared a document with her. What does it do?"@en ;
    solid-memo:back "Find Alice's inbox from her profile and POST a notification to it"@en ;
    solid-memo:backNote "Linked Data Notifications senders discover the inbox via `ldp:inbox` and deliver with POST; Alice's apps later read it like any container."@en ;
    solid-memo:distractor <#q-pods-11a-d1> ,
                          <#q-pods-11a-d2> ,
                          <#q-pods-11a-d3> .

<#q-pods-11a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "PUT the message into Alice's profile document as a new triple"@en ;
    solid-memo:distractorNote "Others usually can't write to a profile; the inbox is the place for incoming messages."@en .

<#q-pods-11a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Subscribe to Alice's pod with a WebSocket channel and send it there"@en ;
    solid-memo:distractorNote "Notification channels deliver change events from a server, not messages to a person."@en .

<#q-pods-11a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "PATCH a new triple into Alice's inbox container listing"@en ;
    solid-memo:distractorNote "Container listings are server-managed; new messages are created with POST."@en .

<#q-pods-11b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "In Solid, what is the main difference between a Linked Data Notifications (LDN) inbox and Solid Notifications?"@en ;
    solid-memo:back "Inboxes hold agents' messages; Notifications report resource changes"@en ;
    solid-memo:backNote "An inbox is a mailbox that agents POST messages to, read later. Solid Notifications deliver live events such as \"this resource was updated\" (Chapter 10)."@en ;
    solid-memo:distractor <#q-pods-11b-d1> ,
                          <#q-pods-11b-d2> ,
                          <#q-pods-11b-d3> .

<#q-pods-11b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Inboxes are the new standard; Solid Notifications are the deprecated one"@en ;
    solid-memo:distractorNote "Both are current; they serve different purposes."@en .

<#q-pods-11b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Inboxes are for apps; Solid Notifications are only for human users"@en ;
    solid-memo:distractorNote "Both are used by apps; the difference is what kind of message they carry."@en .

<#q-pods-11b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Inboxes use WebSockets; Solid Notifications use plain HTTP POST"@en ;
    solid-memo:distractorNote "LDN uses POST to a container; WebSockets are one Notifications channel type."@en .

<#q-pods-r01>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app holds only the URL `https://host.example/u/bob/data/x.ttl`. Which plan finds Bob's storage description without guessing any path?"@en ;
    solid-memo:back "Request `x.ttl` and follow its `storageDescription` link"@en ;
    solid-memo:backNote "Servers MUST send a `storageDescription` Link header on GET, HEAD and OPTIONS of any resource in a storage, so one request is enough if you may read `x.ttl`. ⚠ On CSS 7.2 (2026) a `401` answer omits the link, and the link leads to a server-wide description (Step 5.6)."@en ;
    solid-memo:distractor <#q-pods-r01-d1> ,
                          <#q-pods-r01-d2> ,
                          <#q-pods-r01-d3> .

<#q-pods-r01-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Fetch `/.well-known/solid`, which every server uses"@en ;
    solid-memo:distractorNote "That path is one server's choice; the link header is what servers must send."@en .

<#q-pods-r01-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Walk up to `/` and append `description.ttl` to it"@en ;
    solid-memo:distractorNote "No spec defines that name; the description is found by its link."@en .

<#q-pods-r01-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Walk up to the storage root and read its `pim:storage` triple"@en ;
    solid-memo:distractorNote "Nothing requires the root's data to contain `pim:storage`; the description is linked from any resource."@en .

<#q-pods-r02>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Alice keeps her notes in a `notes/` container in her Solid storage. Starting from her WebID only, which plan lists them?"@en ;
    solid-memo:back "Get `pim:storage` from her profile, GET `notes/` there, read `ldp:contains`"@en ;
    solid-memo:backNote "Each step follows data the profile or server publishes. If the profile has no `pim:storage`, as on a fresh CSS 7.2 pod (2026), walk up from the profile's URL to the container with the `pim:Storage` type link instead."@en ;
    solid-memo:distractor <#q-pods-r02-d1> ,
                          <#q-pods-r02-d2> ,
                          <#q-pods-r02-d3> .

<#q-pods-r02-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "GET `notes/` on her WebID's host and read the files listed there"@en ;
    solid-memo:distractorNote "A WebID's location says nothing certain about where her storage is."@en .

<#q-pods-r02-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Get `pim:Storage` from her profile, GET `notes/` there, read `ldp:contains`"@en ;
    solid-memo:distractorNote "`pim:Storage` is a class; the profile points to storage with `pim:storage`."@en .

<#q-pods-r02-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Read `notes/.meta`, which lists every member of the container"@en ;
    solid-memo:distractorNote "`.meta` is a server convention for metadata; members come from `ldp:contains`."@en .

<#q-pods-r03>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Bob uploads a PDF to the container `/shared/` in his Solid pod and wants Alice to know. What kind of resource is the PDF, who lists it in `/shared/`, and how does Bob tell Alice?"@en ;
    solid-memo:back "A non-RDF source that the server lists in `/shared/`; Bob POSTs to Alice's `ldp:inbox`"@en ;
    solid-memo:backNote "A PDF is a non-RDF source. The server adds it to its container's listing automatically, and Bob tells Alice by POSTing to the inbox her profile advertises with `ldp:inbox`."@en ;
    solid-memo:distractor <#q-pods-r03-d1> ,
                          <#q-pods-r03-d2> ,
                          <#q-pods-r03-d3> .

<#q-pods-r03-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An RDF source, so that `/shared/` can list it; Bob POSTs to Alice's `ldp:inbox`"@en ;
    solid-memo:distractorNote "Pods keep PDFs as non-RDF sources; only the listing entry is RDF."@en .

<#q-pods-r03-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A non-RDF source, listed once Bob adds `ldp:contains`; Bob POSTs to Alice's `ldp:inbox`"@en ;
    solid-memo:distractorNote "The server adds containment triples itself, following the path."@en .

<#q-pods-r03-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A non-RDF source that the server lists in `/shared/`; Bob subscribes Alice to its notifications"@en ;
    solid-memo:distractorNote "Bob can't subscribe for Alice; a message to her inbox is how agents tell each other."@en .

<#q-pods-r04>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app stores an RDF caption for the photo `/notes/cat.png`. Later it wants to spot new photos in `/notes/` without subscribing to notifications. Where does it write the caption, and what does it read to find the new photos?"@en ;
    solid-memo:back "Write it where `describedby` points; re-read `/notes/`'s `ldp:contains`"@en ;
    solid-memo:backNote "Metadata about a non-RDF source goes in its description resource. New photos show up as new containment triples, so re-reading the listing finds them (Chapter 10 shows how to be told instead)."@en ;
    solid-memo:distractor <#q-pods-r04-d1> ,
                          <#q-pods-r04-d2> ,
                          <#q-pods-r04-d3> ,
                          <#q-pods-r04-d4> .

<#q-pods-r04-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "Write it to `cat.png.meta`; poll `/notes/`'s `Last-Modified` for caption edits"@en ;
    solid-memo:distractorNote "`.meta` is one server's name, and a container's `Last-Modified` tracks added or removed members, not edits to a member's metadata."@en .

<#q-pods-r04-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Write it into `cat.png`'s ACL; re-read `/notes/`'s `ldp:contains`"@en ;
    solid-memo:distractorNote "The ACL holds access rules for the photo, not metadata about it."@en .

<#q-pods-r04-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "PATCH the caption into `/notes/`'s listing; re-read its `ldp:contains`"@en ;
    solid-memo:distractorNote "Containment triples and their metadata are managed by the server, not written by apps."@en .

<#q-pods-r04-d4>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Write it to `cat.png.meta`; watch the pod root's `Last-Modified`"@en ;
    solid-memo:distractorNote "`.meta` is one server's name for the description resource; follow `describedby` instead. A server may base a container's `Last-Modified` on its own added or removed members only, so a new photo in `/notes/` need not change the root's."@en .

<#q-pods-r05>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "You PUT `/notes/2026/today.ttl` into a Solid pod where `/notes/` doesn't exist yet. What is now true?"@en ;
    solid-memo:back "`/notes/` and `/notes/2026/` exist, each listing the next level"@en ;
    solid-memo:backNote "Containment mirrors the path: the server creates the intermediate containers and their containment triples, so no resource is an orphan."@en ;
    solid-memo:distractor <#q-pods-r05-d1> ,
                          <#q-pods-r05-d2> ,
                          <#q-pods-r05-d3> .

<#q-pods-r05-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The PUT fails until you create `/notes/` and `/notes/2026/` first"@en ;
    solid-memo:distractorNote "The server creates missing containers itself, so no orphan can arise."@en .

<#q-pods-r05-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`today.ttl` exists, but no container lists it until you add it"@en ;
    solid-memo:distractorNote "Containment mirrors the path, so `/notes/2026/` lists it at once."@en .

<#q-pods-r05-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`/notes/2026` (no slash) also exists, as a separate document"@en ;
    solid-memo:distractorNote "Slash twins can't be different resources; `/notes/2026/` is the container."@en .

# Chapter 6: Reading and writing resources.
<#ch-read-write>
    a solid-memo:Chapter ,
      schema:Syllabus ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <> ;
    schema:position 5 ;
    dcterms:title "Reading and writing resources"@en ;
    dcterms:description "Every CRUD operation on a Solid pod: reading, content negotiation, `PUT`, `POST`, containers, files, N3 Patch, SPARQL Update and `DELETE`, ending with safe concurrent writes using ETags."@en ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:reviewQuestion <#q-read-write-r01> ,
                              <#q-read-write-r02> ,
                              <#q-read-write-r03> ,
                              <#q-read-write-r04> ,
                              <#q-read-write-r05> .

<#ch-read-write-1>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-write> ;
    schema:position 0 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Reading: GET, HEAD, OPTIONS

Every Solid server must support `GET` (fetch the representation), `HEAD` (the same headers, no body) and `OPTIONS` (what can I do here?); an unsupported method gets `405 Method Not Allowed`. Any request can be redirected (`301`, `307`, `308`); `307` and `308` mean "repeat the same request, write included, at the new URL".

---

Successful responses must carry `Allow`, the methods allowed here. An authorized read must also say which formats each write method in `Allow` accepts, in `Accept-Patch`, `Accept-Post` and `Accept-Put` (a Solid invention). A cheap `HEAD` tells you what you may send before you send it. On CSS 7.2 (October 2026), a HEAD on a Turtle document returned (some headers trimmed):

```http
HEAD /alice/notes/first.ttl HTTP/1.1

HTTP/1.1 200 OK
Content-Type: text/turtle
Allow: OPTIONS, HEAD, GET, PATCH, PUT, DELETE
Accept-Patch: text/n3, application/sparql-update
Accept-Put: */*
ETag: "1791408808150-text/turtle"
WAC-Allow: user="append control read write"
```

There is no `Accept-Post`, because CSS leaves POST out of a document's `Allow`. node-solid-server (NSS) 6.0.0, the older server early pod providers ran, lists POST and sends `Accept-Post`. Servers using Web Access Control (Chapter 8) also send `WAC-Allow`.

⚠ CSS 7.2 answers a bare `OPTIONS` with `204 No Content` and no `Allow`, taking it for a browser's cross-origin check (CORS, Step 8.8), so use HEAD."""@en ;
    solid-memo:checkedBy <#q-read-write-1a> ,
                         <#q-read-write-1b> .

<#q-read-write-1a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Before writing to a resource on a Solid server, your app wants to know which PATCH formats the server accepts, without downloading the body. What should it do?"@en ;
    solid-memo:back "Send a HEAD and read the `Accept-Patch` header"@en ;
    solid-memo:backNote "Authorized reads must advertise `Accept-Patch`, `Accept-Post` or `Accept-Put` for each of those write methods listed in `Allow`, so a HEAD gives the write formats without the body. CSS 7.2 answers a bare OPTIONS without them, another reason to use HEAD."@en ;
    solid-memo:distractor <#q-read-write-1a-d1> ,
                          <#q-read-write-1a-d2> ,
                          <#q-read-write-1a-d3> .

<#q-read-write-1a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Send a GET and read the `Content-Type` header"@en ;
    solid-memo:distractorNote "`Content-Type` describes the body you received, not the formats a PATCH may use."@en .

<#q-read-write-1a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Send a HEAD and read the `Accept-Post` header"@en ;
    solid-memo:distractorNote "`Accept-Post` lists formats for POST, not for PATCH."@en .

<#q-read-write-1a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Send a test PATCH and see whether it gets a `405`"@en ;
    solid-memo:distractorNote "405 means the method is not supported at all, and trial and error risks changing data."@en .

<#q-read-write-1b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On Community Solid Server 7.2 (2026), a HEAD on the Turtle document `/notes/shopping.ttl` returns `Allow: OPTIONS, HEAD, GET, PATCH, PUT, DELETE` with `Accept-Patch` and `Accept-Put`, but no `Accept-Post`. Why?"@en ;
    solid-memo:back "POST isn't in this document's `Allow` header"@en ;
    solid-memo:backNote "The `Accept-*` headers mirror the write methods in `Allow`, and POST goes to containers, so CSS 7.2 sends no `Accept-Post` on a document. NSS 6.0.0 lists POST on documents too, and then sends `Accept-Post`."@en ;
    solid-memo:distractor <#q-read-write-1b-d1> ,
                          <#q-read-write-1b-d2> ,
                          <#q-read-write-1b-d3> .

<#q-read-write-1b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server does not support POST on any resource at all"@en ;
    solid-memo:distractorNote "Servers must support POST; it just is not allowed on a plain document."@en .

<#q-read-write-1b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`Accept-Post` is optional, and servers usually leave it out"@en ;
    solid-memo:distractorNote "When POST is listed in `Allow`, `Accept-Post` must be sent too."@en .

<#q-read-write-1b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`Accept-Put` also covers the formats of POST requests"@en ;
    solid-memo:distractorNote "Each write method has its own header; `Accept-Put` is only about PUT."@en .

<#ch-read-write-2>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-write> ;
    schema:position 1 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Content negotiation in practice

Chapter 2 showed that the `Accept` header asks for a format. Solid makes this concrete: when a resource is created as RDF (by PUT, POST or PATCH), the server must serve it as both `text/turtle` and `application/ld+json`, whichever of the two created it. On CSS 7.2 (October 2026), a document written as Turtle was read back as JSON-LD:

```http
PUT /alice/notes/first.ttl HTTP/1.1
Content-Type: text/turtle

<#it> <http://schema.org/text> "Hello, Solid" .

HTTP/1.1 201 Created

GET /alice/notes/first.ttl HTTP/1.1
Accept: application/ld+json

HTTP/1.1 200 OK
Content-Type: application/ld+json
ETag: "1791408808150-application/ld+json"

[ { "@id": "https://pod.example/alice/notes/first.ttl#it",
    "http://schema.org/text": [ { "@value": "Hello, Solid" } ] } ]
```

The ETag has the Turtle one's number but its own suffix (Step 6.11).

---

For writers the reverse direction matters most: clients must send `Content-Type` on any PUT, POST or PATCH with a body, and servers must reject such a request without it with `400 Bad Request` (CSS 7.2 says "HTTP request body was passed without a Content-Type header").

Negotiation only converts RDF. A non-RDF file (Step 6.6) comes back as stored, or as an error if the server can't meet your `Accept`. HTTP suggests `406 Not Acceptable`, which NSS 6.0.0 sends. ⚠ CSS 7.2 answers `501 Not Implemented`: "No conversion path could be made from image/png to text/turtle"."""@en ;
    solid-memo:checkedBy <#q-read-write-2a> ,
                         <#q-read-write-2b> .

<#q-read-write-2a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On a Solid pod, one app saves a document by PUTting JSON-LD. A second app that only parses Turtle later GETs it with `Accept: text/turtle`. What does a conforming server do?"@en ;
    solid-memo:back "It returns the same triples serialized as Turtle"@en ;
    solid-memo:backNote "Solid servers must serve any RDF source created by PUT, POST or PATCH as both `text/turtle` and `application/ld+json`, so apps never need to agree on which of the two to write."@en ;
    solid-memo:distractor <#q-read-write-2a-d1> ,
                          <#q-read-write-2a-d2> ,
                          <#q-read-write-2a-d3> .

<#q-read-write-2a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It returns 406 because the document was stored as JSON-LD"@en ;
    solid-memo:distractorNote "Servers must serve RDF sources in both Turtle and JSON-LD, whatever format created them."@en .

<#q-read-write-2a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It returns the original JSON-LD text unchanged"@en ;
    solid-memo:distractorNote "That ignores the client's `Accept` header, which the server must honour for these two formats."@en .

<#q-read-write-2a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It redirects to a separate `.ttl` copy of the document"@en ;
    solid-memo:distractorNote "There is one resource; the format is chosen by negotiation, not by a second file."@en .

<#q-read-write-2b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A PUT with a valid Turtle body fails with `400 Bad Request` on a Solid server. What is the most likely cause?"@en ;
    solid-memo:back "The request had no `Content-Type` header"@en ;
    solid-memo:backNote "Solid servers must reject a PUT, POST or PATCH that carries a body without a `Content-Type` with 400."@en ;
    solid-memo:distractor <#q-read-write-2b-d1> ,
                          <#q-read-write-2b-d2> ,
                          <#q-read-write-2b-d3> .

<#q-read-write-2b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The request had no `Accept` header"@en ;
    solid-memo:distractorNote "`Accept` is about the response format and is not required on a write."@en .

<#q-read-write-2b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The URL did not end in `.ttl`"@en ;
    solid-memo:distractorNote "Solid does not use file extensions to decide formats; headers do."@en .

<#q-read-write-2b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The request had no `Link` type header"@en ;
    solid-memo:distractorNote "A plain document needs no type link; leaving it out does not make the request malformed."@en .

<#ch-read-write-3>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-write> ;
    schema:position 2 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## PUT: you choose the URL

Use `PUT` when you know the URL you want. HTTP defines it as "make the resource at this URL look like this body": it creates the resource if nothing is there and replaces it entirely if something is. Replacing means the old content is gone: any triple you leave out of the new body is deleted.

A create answers `201 Created`. For a replace HTTP expects `200` or `204`, and NSS 6.0.0 answers `204`. ⚠ CSS 7.2 answers a successful replace, PATCH or DELETE with `205 Reset Content`: on CSS 7.2 (October 2026), sending the PUT of Step 6.2 a second time got `205`, where the first had got `201`. Treat any 2xx as success.

---

You don't need to create folders first. A server must create any missing intermediate containers from the URL path, with their containment triples, so `PUT /a/b/c.ttl` also creates `/a/` and `/a/b/`. Step 6.2's first PUT created `notes/` this way.

To make a PUT create-only, add `If-None-Match: *`. The request then succeeds only if no representation exists; otherwise it fails with `412 Precondition Failed` instead of overwriting.

```http
PUT /notes/shopping.ttl HTTP/1.1
Content-Type: text/turtle
If-None-Match: *

<#milk> a <http://schema.org/Product> .
```"""@en ;
    solid-memo:checkedBy <#q-read-write-3a> ,
                         <#q-read-write-3b> .

<#q-read-write-3a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your app PUTs `/recipes/2026/soup.ttl` into a Solid pod where only the root container exists. What happens on a conforming server?"@en ;
    solid-memo:back "It also creates `/recipes/` and `/recipes/2026/`"@en ;
    solid-memo:backNote "Solid servers must create the missing intermediate containers, with their containment triples, from the URL path of a PUT or PATCH."@en ;
    solid-memo:distractor <#q-read-write-3a-d1> ,
                          <#q-read-write-3a-d2> ,
                          <#q-read-write-3a-d3> .

<#q-read-write-3a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server answers 404 because the parent container does not exist"@en ;
    solid-memo:distractorNote "Servers must create intermediate containers for PUT and PATCH."@en .

<#q-read-write-3a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server answers 409 because containers must be created first"@en ;
    solid-memo:distractorNote "Nested creation is not a conflict; the server must create the missing containers."@en .

<#q-read-write-3a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server stores the document as `/soup.ttl` in the root container"@en ;
    solid-memo:distractorNote "With PUT the client chooses the URL; the server does not move it."@en .

<#q-read-write-3b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Two devices might create the same settings document in a Solid pod at the same moment. Which header stops the second PUT from overwriting the first?"@en ;
    solid-memo:back "`If-None-Match: *`" ;
    solid-memo:backNote "With `If-None-Match: *` the server refuses a PUT or PATCH with 412 when a current representation exists, so a create cannot clobber existing data."@en ;
    solid-memo:distractor <#q-read-write-3b-d1> ,
                          <#q-read-write-3b-d2> ,
                          <#q-read-write-3b-d3> .

<#q-read-write-3b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`Accept: text/turtle`" ;
    solid-memo:distractorNote "`Accept` chooses the format of the response; it does not make the server check whether the resource exists."@en .

<#q-read-write-3b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`Content-Type: text/turtle`" ;
    solid-memo:distractorNote "It names the body's format and adds no protection against overwriting."@en .

<#q-read-write-3b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`Cache-Control: no-store`" ;
    solid-memo:distractorNote "Caching directives do not make the server check whether the resource exists."@en .

<#ch-read-write-4>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-write> ;
    schema:position 3 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## POST: the server chooses the URL

Use `POST` when you don't care about the exact name, such as adding a new message or log entry. You POST to a container, and the server picks the URL: a POST to `/foo/` creates `/foo/{id}`, directly inside `/foo/`. A successful create answers `201 Created`, and the `Location` header holds the new resource's URL. On CSS 7.2 (October 2026):

```http
POST /alice/notes/ HTTP/1.1
Content-Type: text/turtle
Slug: second

<#it> <http://schema.org/text> "Second note" .

HTTP/1.1 201 Created
Location: https://pod.example/alice/notes/second
```

The `Slug` header (defined in AtomPub, RFC 5023, and adopted by LDP as a client hint) lets you suggest a name. It is only a hint, and current Solid specs do not require servers to honour it. A server may use it, change it or ignore it, so always read the URL from `Location`. ⚠ CSS 7.2 happens to keep a Slug exactly and adds no extension, as above; that is no promise for other servers (Step 6.6 shows NSS 6.0.0 adding one).

POST is only meaningful on something that exists: a POST to a URL with no existing representation gets `404 Not Found`."""@en ;
    solid-memo:checkedBy <#q-read-write-4a> ,
                         <#q-read-write-4b> .

<#q-read-write-4a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your app POSTs a new note to the Solid container `/notes/` with `Slug: groceries`. How should it learn the new note's URL?"@en ;
    solid-memo:back "Read the `Location` header of the 201 response"@en ;
    solid-memo:backNote "With POST the server assigns the URL and reports it in the `Location` header of the `201 Created` response; a Slug never guarantees the name."@en ;
    solid-memo:distractor <#q-read-write-4a-d1> ,
                          <#q-read-write-4a-d2> ,
                          <#q-read-write-4a-d3> .

<#q-read-write-4a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Assume it is `/notes/groceries` because of the Slug"@en ;
    solid-memo:distractorNote "A Slug is only a hint; servers may change or ignore it."@en .

<#q-read-write-4a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "List `/notes/` again and take the newest entry"@en ;
    solid-memo:distractorNote "That is slow, and racy when other clients also add notes."@en .

<#q-read-write-4a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Generate a UUID in the app and use `/notes/{uuid}`"@en ;
    solid-memo:distractorNote "With POST the server, not the client, names the resource."@en .

<#q-read-write-4b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "On a Solid server, when is POST the better choice than PUT for creating a resource?"@en ;
    solid-memo:back "When the app doesn't need to pick the URL"@en ;
    solid-memo:backNote "Clients use PUT (and PATCH) to choose a URL themselves, and POST to have the server assign one."@en ;
    solid-memo:distractor <#q-read-write-4b-d1> ,
                          <#q-read-write-4b-d2> ,
                          <#q-read-write-4b-d3> .

<#q-read-write-4b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "When the app needs to replace an existing document"@en ;
    solid-memo:distractorNote "Replacing at a known URL is exactly what PUT is for."@en .

<#q-read-write-4b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "When the parent container does not exist yet"@en ;
    solid-memo:distractorNote "A POST to a missing container gets 404; PUT is the one that creates intermediate containers."@en .

<#q-read-write-4b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "When the body is RDF rather than an image"@en ;
    solid-memo:distractorNote "Both methods accept RDF and non-RDF bodies; the difference is who chooses the URL."@en .

<#ch-read-write-5>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-write> ;
    schema:position 4 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Creating containers

Solid has no "mkdir", but there are three routes.

1. **PUT (or PATCH) something inside it.** Servers must create intermediate containers, so writing `/photos/2026/cat.jpg` also creates `/photos/` and `/photos/2026/`.
2. **PUT to a URL ending in `/`.** The trailing slash names a container (Chapter 5), so the spec covers this too. CSS 7.2 ignores the body. ⚠ CSS 7.2 answers a PUT to an existing container with `409 Conflict` ("Existing containers cannot be updated via PUT."), even with `If-None-Match: *`, where you might expect 412. Send no body, and never use it to "update" a container.
3. **POST with an LDP type link.** Send a POST to the parent with `Link: <http://www.w3.org/ns/ldp#BasicContainer>; rel="type"` and usually a `Slug`. Solid Protocol v0.10 required this; v0.11 dropped the requirement. Many servers still accept it (on CSS 7.2, `Slug: sub` got `201` with a `Location` ending in `/notes/sub/`), but don't rely on it.

Nor can you write a container's membership: containment mirrors the URL paths (Chapter 5), so a PUT or PATCH that changes `ldp:contains` triples gets `409 Conflict`. Never send a listing; create or delete the contents instead."""@en ;
    solid-memo:checkedBy <#q-read-write-5a> ,
                         <#q-read-write-5b> .

<#q-read-write-5a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Which way of creating a container is NOT guaranteed to work on every server that follows Solid Protocol v0.11?"@en ;
    solid-memo:back "POST to the parent with an `ldp:BasicContainer` type link"@en ;
    solid-memo:backNote "Writing inside a container and PUT to a slash URL both rest on spec requirements. POST with a type link was a MUST up to v0.10, and many servers still support it, but v0.11 dropped the requirement."@en ;
    solid-memo:distractor <#q-read-write-5a-d1> ,
                          <#q-read-write-5a-d2> ,
                          <#q-read-write-5a-d3> .

<#q-read-write-5a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "PUT a resource whose URL lies inside the new container"@en ;
    solid-memo:distractorNote "Servers must create intermediate containers from a PUT's path."@en .

<#q-read-write-5a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "PATCH a new resource whose URL lies inside the new container"@en ;
    solid-memo:distractorNote "Intermediate containers are created for PATCH as well as PUT."@en .

<#q-read-write-5a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "PUT with no body to the new container's URL ending in `/`"@en ;
    solid-memo:distractorNote "Slash semantics makes that URL a container, which servers must support."@en .

<#q-read-write-5b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your app PUTs each note to a URL it chooses inside the Solid container `/notes/`, which may not exist yet. What is the simplest portable way to make sure the container exists?"@en ;
    solid-memo:back "Just PUT the note, and the server creates `/notes/`"@en ;
    solid-memo:backNote "Servers must create missing intermediate containers for PUT and PATCH, so writing the note is enough. A separate container PUT adds a request, and CSS 7.2 even refuses it with 409 once the container exists."@en ;
    solid-memo:distractor <#q-read-write-5b-d1> ,
                          <#q-read-write-5b-d2> ,
                          <#q-read-write-5b-d3> .

<#q-read-write-5b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "PUT `/notes/` itself before every note"@en ;
    solid-memo:distractorNote "It is unneeded, and on CSS 7.2 a PUT to an existing container gets 409."@en .

<#q-read-write-5b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "POST to the root with an `ldp:BasicContainer` type link first"@en ;
    solid-memo:distractorNote "Solid Protocol v0.11 no longer guarantees that route, and it is unneeded."@en .

<#q-read-write-5b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "GET `/notes/` and stop with an error on 404"@en ;
    solid-memo:distractorNote "A 404 only means it doesn't exist yet; a PUT inside it creates it."@en .

<#ch-read-write-6>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-write> ;
    schema:position 5 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Files and other non-RDF resources

Images, PDFs and other files are non-RDF resources. You write them like documents, by PUT or POST, with the file's real media type in the required `Content-Type` (Step 6.2). A GET returns the bytes and the type they were stored under.

---

Metadata goes in the file's description resource, which the server links with `rel="describedby"` (Step 5.10). Its name is the server's choice, so follow the link: CSS 7.2 names it `photo.meta`, and NSS 6.0.0 `photo.png.meta`, because there the file itself became `photo.png`. NSS 6.0.0 also spells the relation `describedBy`; relation names compare case-insensitively, so match them that way. On CSS 7.2 (October 2026), uploading a one-pixel PNG and captioning it with an N3 Patch (Step 6.7) went like this (headers trimmed):

```http
POST /alice/notes/ HTTP/1.1
Content-Type: image/png
Slug: photo

<70 bytes of PNG data>

HTTP/1.1 201 Created
Location: https://pod.example/alice/notes/photo

HEAD /alice/notes/photo HTTP/1.1

HTTP/1.1 200 OK
Content-Type: image/png
Link: <https://pod.example/alice/notes/photo.meta>; rel="describedby"

PATCH /alice/notes/photo.meta HTTP/1.1
Content-Type: text/n3

@prefix solid: <http://www.w3.org/ns/solid/terms#>.
@prefix schema: <http://schema.org/>.
_:patch a solid:InsertDeletePatch;
  solid:inserts { <photo> schema:description "A one-pixel test image" . }.

HTTP/1.1 205 Reset Content
```

---

A GET on `photo.meta` then returned the server-managed triples plus the caption:

```turtle
@prefix dc: <http://purl.org/dc/terms/>.
@prefix ldp: <http://www.w3.org/ns/ldp#>.
@prefix posix: <http://www.w3.org/ns/posix/stat#>.
@prefix xsd: <http://www.w3.org/2001/XMLSchema#>.

<https://pod.example/alice/notes/photo> <http://www.w3.org/ns/ma-ont#format> "image/png";
    a ldp:Resource;
    dc:modified "2026-10-07T21:33:28.927Z"^^xsd:dateTime;
    posix:size "70";
    <http://schema.org/description> "A one-pixel test image".
```

A GET on that description resource lists `Allow: OPTIONS, HEAD, GET, PATCH`, with no PUT; a PUT to it gets `405` ("use PATCH instead"), whose `Allow` also lists `DELETE`.

⚠ URL and type can disagree. CSS 7.2 kept `Slug: photo` as `…/notes/photo`, served as `image/png`. NSS 6.0.0 adds an extension from the type: `photo.png`. Never infer the type from the URL: read `Content-Type`."""@en ;
    solid-memo:checkedBy <#q-read-write-6a> ,
                         <#q-read-write-6b> .

<#q-read-write-6a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your app POSTs a photo to a Solid container with `Slug: holiday` and `Content-Type: image/jpeg`. The `Location` is `/photos/holiday`, with no extension. How should a gallery app later tell that it is a JPEG?"@en ;
    solid-memo:back "From the `Content-Type` of a HEAD or GET on it"@en ;
    solid-memo:backNote "A HEAD or GET returns the type the file was stored under in `Content-Type`. URLs need not carry an extension and servers name files differently (NSS 6.0.0 turns `Slug: note` with `text/turtle` into `note.ttl`), so never infer the type from them. As of October 2026 the JavaScript Solid Server (JSS) even serves an extensionless Turtle document received by PUT as `application/octet-stream`, so a surprising type may be the server's doing."@en ;
    solid-memo:distractor <#q-read-write-6a-d1> ,
                          <#q-read-write-6a-d2> ,
                          <#q-read-write-6a-d3> .

<#q-read-write-6a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "From the URL's file extension, defaulting to JPEG"@en ;
    solid-memo:distractorNote "There is none here, and on other servers the URL and type can disagree."@en .

<#q-read-write-6a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "From the Slug, since servers keep it as sent"@en ;
    solid-memo:distractorNote "A Slug is only a name hint and says nothing reliable about the type."@en .

<#q-read-write-6a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "By sending `Accept: image/jpeg` and seeing if it works"@en ;
    solid-memo:distractorNote "For a non-RDF file the server returns the stored bytes or an error; `Content-Type` already tells you."@en .

<#q-read-write-6b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On Community Solid Server 7.2 (2026), your app PUTs a Turtle caption to a photo's description resource, the URL from its `describedby` link, and gets `405 Method Not Allowed`. Why?"@en ;
    solid-memo:back "PUT isn't allowed there, so send an N3 Patch instead"@en ;
    solid-memo:backNote "On CSS 7.2 a GET on a description resource lists `Allow: OPTIONS, HEAD, GET, PATCH`, with no PUT. A PUT gets 405 (\"use PATCH instead\"), and an N3 Patch adds your triples next to the server-managed ones (205)."@en ;
    solid-memo:distractor <#q-read-write-6b-d1> ,
                          <#q-read-write-6b-d2> ,
                          <#q-read-write-6b-d3> .

<#q-read-write-6b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The body would overwrite the server-managed `posix:size` triple"@en ;
    solid-memo:distractorNote "405 means the method itself is not allowed here, whatever the body says."@en .

<#q-read-write-6b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Captions belong in the photo's ACL, not in its description"@en ;
    solid-memo:distractorNote "The ACL holds access rules; descriptive metadata belongs in the description resource."@en .

<#q-read-write-6b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The PUT needed a `Slug` header to name the caption"@en ;
    solid-memo:distractorNote "A Slug is a naming hint for POST; it plays no part in a PUT."@en .

<#ch-read-write-7>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-write> ;
    schema:position 6 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## The shape of an N3 Patch

`PUT` replaces the whole document; `PATCH` changes part of it. For RDF documents, servers must accept an **N3 Patch** with media type `text/n3` and list it in `Accept-Patch`. It is written in N3 (Step 3.10): Turtle plus `{ }` formulas (groups of triples) and variables such as `?person`, which stand for "whatever node fits here".

---

The body describes one change, the **patch resource**, typed `solid:InsertDeletePatch`. It has at most one each of `solid:where` (what must be true now), `solid:deletes` (triples to remove) and `solid:inserts` (triples to add):

```n3
@prefix solid: <http://www.w3.org/ns/solid/terms#>.
@prefix ex: <http://www.example.org/terms#>.

_:rename a solid:InsertDeletePatch;
  solid:where   { ?person ex:familyName "Garcia". };
  solid:inserts { ?person ex:givenName "Alex". };
  solid:deletes { ?person ex:givenName "Claudia". }.
```

The server finds the node that makes `where` true and uses it for `?person` in `inserts` and `deletes`. A patch that breaks the format rules gets `422`: for example two patch resources, a variable in `inserts` or `deletes` that never appears in `where`, or blank nodes in `inserts` or `deletes` (Step 6.8 has the version details). HTTP now calls 422 "Unprocessable Content"; CSS 7.2 still sends the older text, "Unprocessable Entity"."""@en ;
    solid-memo:checkedBy <#q-read-write-7a> ,
                         <#q-read-write-7b> .

<#q-read-write-7a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid, which `Content-Type` must a PATCH request carry to send an N3 Patch?"@en ;
    solid-memo:back "`text/n3`" ;
    solid-memo:backNote "N3 Patch uses the media type `text/n3`, and Solid servers must list it in `Accept-Patch` for RDF documents."@en ;
    solid-memo:distractor <#q-read-write-7a-d1> ,
                          <#q-read-write-7a-d2> ,
                          <#q-read-write-7a-d3> .

<#q-read-write-7a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`text/turtle`" ;
    solid-memo:distractorNote "Turtle has no formulas or variables, so it cannot express `where`, `inserts` and `deletes`."@en .

<#q-read-write-7a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`application/ld+json`" ;
    solid-memo:distractorNote "JSON-LD is a format for RDF data, not a patch language."@en .

<#q-read-write-7a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`application/json-patch+json`" ;
    solid-memo:distractorNote "JSON Patch edits JSON trees; Solid's required patch format is N3 Patch."@en .

<#q-read-write-7b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your Solid N3 Patch uses `?item` in `solid:inserts`, but its `solid:where` never mentions `?item`. What does the server answer?"@en ;
    solid-memo:back "422, because the patch itself is malformed"@en ;
    solid-memo:backNote "Variables in `inserts` and `deletes` must appear in `where`; a patch that breaks the structural rules gets 422."@en ;
    solid-memo:distractor <#q-read-write-7b-d1> ,
                          <#q-read-write-7b-d2> ,
                          <#q-read-write-7b-d3> .

<#q-read-write-7b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "409, because nothing in the document matched `?item`"@en ;
    solid-memo:distractorNote "409 is about the document's current state; this patch is broken whatever the document holds."@en .

<#q-read-write-7b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "204, after inserting a fresh node for `?item`"@en ;
    solid-memo:distractorNote "Variables are only filled from `where`; an unbound one is an error."@en .

<#q-read-write-7b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "400, because the request body is not valid N3"@en ;
    solid-memo:distractorNote "The N3 syntax is fine; the patch breaks N3 Patch's rules, which gives 422."@en .

<#ch-read-write-8>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-write> ;
    schema:position 7 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## How the server applies an N3 Patch

The server processes a valid patch in order:
1. Start from the document's triples, or an **empty** graph if it doesn't exist yet, so a PATCH can create a resource.
2. Match `where`. If it is true zero times, or more than once, answer `409 Conflict`. A missing `where` counts as empty, which is true exactly once, so insert-only patches always pass this step.
3. If any triple to delete is not present, answer `409`. (A missing `deletes` deletes nothing.)
4. Delete, then insert, and answer with success (⚠ `205` on CSS 7.2, `200` on NSS 6.0.0).

---

So `409` means "the document is not in the state your patch expected", while `422` means "your patch itself is broken". On CSS 7.2 (October 2026), three patches to a document holding `<#it> schema:text "Hello, Solid"` got:

```text
inserts { <#it> schema:keywords "solid" . }               -> 205 Reset Content
deletes { <#it> schema:text "Not in the document" . }     -> 409 Conflict
inserts { <#it> schema:author _:someone .
          _:someone schema:name "Bob" . }                 -> 422 Unprocessable Entity
```

**Blank nodes** ⚠. Solid Protocol v0.11, which CSS 7.2 follows, refuses them in inserts and deletes with 422, as above. The 2026 editor's draft allows fresh ones in inserts only; NSS 6.0.0 accepts them. Portable alternatives (Step 3.10): fragment IRIs such as `<#author>`, or a blank node written with PUT and reached through a `where` variable."""@en ;
    solid-memo:checkedBy <#q-read-write-8a> ,
                         <#q-read-write-8b> .

<#q-read-write-8a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid N3 Patch's `where` clause matches two different people in the target document. What does the server do?"@en ;
    solid-memo:back "It rejects the patch with 409 and changes nothing"@en ;
    solid-memo:backNote "If `where` matches zero times or several times, the server must answer 409 and not apply the patch."@en ;
    solid-memo:distractor <#q-read-write-8a-d1> ,
                          <#q-read-write-8a-d2> ,
                          <#q-read-write-8a-d3> .

<#q-read-write-8a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It applies the patch to both matching people"@en ;
    solid-memo:distractorNote "N3 Patch requires exactly one match, so multiple matches are a conflict."@en .

<#q-read-write-8a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It applies the patch to the first match only, in document order"@en ;
    solid-memo:distractorNote "The server never picks a match for you; ambiguity is refused."@en .

<#q-read-write-8a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It rejects the patch with 422 as malformed"@en ;
    solid-memo:distractorNote "422 is for a patch that breaks the format rules; this patch is well formed."@en .

<#q-read-write-8b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "You send a Solid N3 Patch with only `solid:inserts` to a URL where no document exists yet. What happens on a conforming server?"@en ;
    solid-memo:back "The document is created, containing the inserted triples"@en ;
    solid-memo:backNote "N3 Patch processing begins with the target's triples, or an empty graph if the resource does not exist, so an insert-only PATCH can create a document."@en ;
    solid-memo:distractor <#q-read-write-8b-d1> ,
                          <#q-read-write-8b-d2> ,
                          <#q-read-write-8b-d3> .

<#q-read-write-8b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server answers 404, because PATCH needs an existing target"@en ;
    solid-memo:distractorNote "Processing starts from an empty graph when the target does not exist."@en .

<#q-read-write-8b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server answers 409, because there is nothing to match"@en ;
    solid-memo:distractorNote "A missing `where` counts as empty, which matches exactly once."@en .

<#q-read-write-8b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The document is created empty, and the inserts are ignored"@en ;
    solid-memo:distractorNote "The inserts are applied to the empty starting graph, so they are stored."@en .

<#ch-read-write-9>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-write> ;
    schema:position 8 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## SPARQL Update: the legacy format

Before N3 Patch, Solid servers patched with SPARQL Update, media type `application/sparql-update`. SPARQL is RDF's query language (Step 3.11); its update forms `DELETE DATA` and `INSERT DATA` list exact triples to remove and add. The archived early Solid REST API document used it like this:

```http
PATCH /data/ HTTP/1.1
Content-Type: application/sparql-update

DELETE DATA { <> <http://purl.org/dc/terms/title> "Basic container" };
INSERT DATA { <> <http://purl.org/dc/terms/title> "My data container" }
```

---

It is still widely supported (Community Solid Server accepts it, for example), and many existing libraries send it. But Solid Protocol v0.9 to v0.11 never require it; only N3 Patch is required.

Support is also uneven in practice. As of October 2026, multi-server tests recorded the JavaScript Solid Server (JSS) deleting nothing on `DELETE DATA` yet answering `204`, and Solid-Nextcloud deleting every value of the named subject and predicate, not just the one triple. The portable habit is to read `Accept-Patch` first, prefer `text/n3` when it is listed, and fall back to SPARQL Update only if the server advertises nothing else."""@en ;
    solid-memo:checkedBy <#q-read-write-9a> ,
                         <#q-read-write-9b> .

<#q-read-write-9a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid server's `Accept-Patch` header lists `text/n3, application/sparql-update`. Which format should a portable app use for its patches?"@en ;
    solid-memo:back "N3 Patch, because it is the format every server must accept"@en ;
    solid-memo:backNote "Solid servers must accept N3 Patch (`text/n3`) for RDF documents; SPARQL Update is widely supported but not required, so check `Accept-Patch` and prefer N3."@en ;
    solid-memo:distractor <#q-read-write-9a-d1> ,
                          <#q-read-write-9a-d2> ,
                          <#q-read-write-9a-d3> .

<#q-read-write-9a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "SPARQL Update, because it is the official Solid patch format"@en ;
    solid-memo:distractorNote "The Solid Protocol requires N3 Patch; SPARQL Update is a legacy format."@en .

<#q-read-write-9a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Either one, because the specs define them identically"@en ;
    solid-memo:distractorNote "They are different languages, and only N3 Patch is in the Solid Protocol."@en .

<#q-read-write-9a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Neither, because a full PUT is always the safer write"@en ;
    solid-memo:distractorNote "A PUT replaces the whole document and risks erasing other apps' triples."@en .

<#q-read-write-9b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A document in a Solid pod gives a card two `ex:tag` values. Your app sends a SPARQL Update `DELETE DATA` naming one of them. On one server both tags disappear, yet the server answered with success. What should the app learn from this?"@en ;
    solid-memo:back "SPARQL Update support varies; prefer N3 Patch where offered"@en ;
    solid-memo:backNote "As of October 2026, multi-server tests recorded Solid-Nextcloud deleting every value of the named subject and predicate, and JSS deleting nothing while answering 204. SPARQL Update is optional, so read `Accept-Patch` and prefer `text/n3`."@en ;
    solid-memo:distractor <#q-read-write-9b-d1> ,
                          <#q-read-write-9b-d2> ,
                          <#q-read-write-9b-d3> .

<#q-read-write-9b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`DELETE DATA` is defined to remove every value of the predicate"@en ;
    solid-memo:distractorNote "It removes only the triples it lists; deleting both is that server's deviation."@en .

<#q-read-write-9b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The app should send `INSERT DATA` before `DELETE DATA`"@en ;
    solid-memo:distractorNote "The order is not the problem; the server applied the delete too broadly."@en .

<#q-read-write-9b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A 2xx answer proves the patch was applied as written"@en ;
    solid-memo:distractorNote "Tests have recorded success answers for patches applied wrongly or not at all."@en .

<#ch-read-write-10>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-write> ;
    schema:position 9 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## DELETE

Servers must support `DELETE`. Deleting a resource also removes its containment triple from the parent container and deletes its auxiliary resources, such as its ACL and description resource (Chapter 5).

Two deletes are refused:
- A **non-empty container** gets `409 Conflict`. Solid has no recursive delete, so to remove a folder tree you delete depth-first: the files first, then the deepest containers, then their parents.
- The **storage root** (and its ACL) gets `405 Method Not Allowed`, and `DELETE` is left out of its `Allow` header.

```text
DELETE /notes/             -> 409 (still contains shopping.ttl)
DELETE /notes/shopping.ttl -> 204 (205 on CSS 7.2)
DELETE /notes/             -> 204 (205 on CSS 7.2)
DELETE /                   -> 405
```

---

On CSS 7.2 (October 2026), a DELETE of a `notes/` container that still held three resources got `409 Conflict` with the message "Can only delete empty containers.", and nothing was deleted. Deleting a document, then its emptied container, then that container's emptied parent got `205` each time.

After a successful delete, GET usually returns `404 Not Found` or `410 Gone`; the spec suggests servers should not reuse URLs and may use 410 to signal permanent removal."""@en ;
    solid-memo:checkedBy <#q-read-write-10a> ,
                         <#q-read-write-10b> .

<#q-read-write-10a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your app must remove the Solid container `/project/`, which contains `/project/a.ttl` and the container `/project/img/` with one photo inside. Which order of DELETEs works?"@en ;
    solid-memo:back "The photo, then `/project/img/`, then `a.ttl`, then `/project/`"@en ;
    solid-memo:backNote "Only empty containers can be deleted, so a client must remove children depth-first before their containers."@en ;
    solid-memo:distractor <#q-read-write-10a-d1> ,
                          <#q-read-write-10a-d2> ,
                          <#q-read-write-10a-d3> .

<#q-read-write-10a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Just `/project/`, which removes its contents along with it"@en ;
    solid-memo:distractorNote "A DELETE of a non-empty container gets 409; Solid has no recursive delete."@en .

<#q-read-write-10a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`/project/`, then `/project/img/`, then the photo, then `a.ttl`"@en ;
    solid-memo:distractorNote "`/project/` is not empty yet, so the first request gets 409."@en .

<#q-read-write-10a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`/project/img/`, then the photo, then `a.ttl`, then `/project/`"@en ;
    solid-memo:distractorNote "`/project/img/` still holds the photo, so deleting it first gets 409."@en .

<#q-read-write-10b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your cleanup script empties a test Solid pod and then sends `DELETE /` for the storage root. What does a conforming server answer?"@en ;
    solid-memo:back "405, with `DELETE` left out of its `Allow`"@en ;
    solid-memo:backNote "Solid servers must not allow DELETE on the storage root or its ACL; they answer 405 and leave DELETE out of `Allow`."@en ;
    solid-memo:distractor <#q-read-write-10b-d1> ,
                          <#q-read-write-10b-d2> ,
                          <#q-read-write-10b-d3> .

<#q-read-write-10b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "204, because the root is now empty"@en ;
    solid-memo:distractorNote "Emptiness is not enough; the storage root can never be deleted."@en .

<#q-read-write-10b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "409, because the root still holds its ACL"@en ;
    solid-memo:distractorNote "409 is for containers with contained resources; the root is refused for a different reason."@en .

<#q-read-write-10b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "403, because only the owner may delete the root"@en ;
    solid-memo:distractorNote "Even the owner is refused: the protocol forbids deleting the root itself."@en .

<#ch-read-write-11>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-write> ;
    schema:position 10 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Lost updates and conditional requests

Pods have no locks. Two apps can read a document, edit it and write it back, and the later write silently erases the earlier one: a *lost update*.

HTTP's answer is conditional requests. A server MAY send an `ETag`, a version tag for the current representation. Echo it in `If-Match` when you write; if the document changed or was deleted since, the server answers `412 Precondition Failed` instead:

```text
# Tabs A and B both read
GET /decks/catalog.ttl                  -> 200, ETag: "v7"
# A writes first
PUT /decks/catalog.ttl  If-Match: "v7"  -> 2xx (now "v8")
# B writes with its stale tag
PUT /decks/catalog.ttl  If-Match: "v7"  -> 412
```

On 412, B re-reads, reapplies its change and retries. For creates, `If-None-Match: *` does the same job (Step 6.3). On CSS 7.2 (October 2026), two identical PATCHes sending `If-Match: "1791408809120-text/turtle"` got `205`, then `412`. Send the tag exactly as received: wrapped in a second pair of quotes it never matches.

---

Limits ⚠: CSS 7.2's strong ETag includes the media type, so Turtle and JSON-LD differ. NSS 6.0.0 sends no ETag on a GET in the stored format; the weak `W/"…"` ETags on its HEAD and converted responses are hashes of that response's body, not version tags. It ignores `If-Match` and honours `If-None-Match: *`.

A single PATCH is all-or-nothing, but Solid has no transactions, so a change touching two documents can be left half done."""@en ;
    solid-memo:checkedBy <#q-read-write-11a> ,
                         <#q-read-write-11b> .

<#q-read-write-11a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your app read a Solid document with `ETag: \"v7\"` and now PUTs an edit with `If-Match: \"v7\"`, but gets `412 Precondition Failed`. What does that tell you?"@en ;
    solid-memo:back "The document changed or was deleted since your read"@en ;
    solid-memo:backNote "`If-Match` makes the write conditional on the current ETag, and a 412 means the representation changed or is gone, so re-read, merge and retry."@en ;
    solid-memo:distractor <#q-read-write-11a-d1> ,
                          <#q-read-write-11a-d2> ,
                          <#q-read-write-11a-d3> .

<#q-read-write-11a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Your app lacks write permission on the document"@en ;
    solid-memo:distractorNote "Missing permission is refused with 401 or 403, not 412."@en .

<#q-read-write-11a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server does not support ETags at all"@en ;
    solid-memo:distractorNote "A server without ETags would not have sent one; a 412 means the tag no longer matches."@en .

<#q-read-write-11a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The request body is not valid Turtle for this document"@en ;
    solid-memo:distractorNote "A syntax problem is a client error such as 400, unrelated to the precondition."@en .

<#q-read-write-11b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "An app moves a card from deck A's document to deck B's document in a Solid pod, with two PATCHes. Why can this still go wrong even if each PATCH succeeds or fails cleanly?"@en ;
    solid-memo:back "Each PATCH is all-or-nothing for its own document only"@en ;
    solid-memo:backNote "Solid offers no transactions across documents, so if the first PATCH succeeds and the second fails, the card can end up in both decks or neither."@en ;
    solid-memo:distractor <#q-read-write-11b-d1> ,
                          <#q-read-write-11b-d2> ,
                          <#q-read-write-11b-d3> .

<#q-read-write-11b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "PATCH requests are never all-or-nothing, even within one document"@en ;
    solid-memo:distractorNote "Each PATCH applies wholly or not at all to its one document."@en .

<#q-read-write-11b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`If-Match` on both PATCHes would make the pair all-or-nothing"@en ;
    solid-memo:distractorNote "`If-Match` protects each document separately; the first PATCH can still succeed while the second fails."@en .

<#q-read-write-11b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "ETags are required, and the second PATCH sent no ETag"@en ;
    solid-memo:distractorNote "ETags are a MAY in Solid, and they protect one document, not a pair."@en .

<#q-read-write-r01>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your app wants to change one triple in a shared Solid document without erasing triples other apps added since it last read it. Which write is best?"@en ;
    solid-memo:back "An N3 Patch that deletes the expected old value"@en ;
    solid-memo:backNote "A PATCH touches only the named triples, and its `where` and `deletes` make it fail with 409 instead of overwriting a value that changed since you read it."@en ;
    solid-memo:distractor <#q-read-write-r01-d1> ,
                          <#q-read-write-r01-d2> ,
                          <#q-read-write-r01-d3> .

<#q-read-write-r01-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A PUT of the app's own copy of the full document"@en ;
    solid-memo:distractorNote "PUT replaces everything, so other apps' newer triples would be lost."@en .

<#q-read-write-r01-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A POST of the new triple to the document's own URL"@en ;
    solid-memo:distractorNote "POST creates a new resource in a container; it does not edit a document."@en .

<#q-read-write-r01-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A DELETE of the document followed by a fresh PUT"@en ;
    solid-memo:distractorNote "That loses other apps' triples and leaves a moment where the data is gone."@en .

<#q-read-write-r02>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "When writing to a Solid pod, which pair of status codes usually means the resource is no longer in the state your app read, so it should re-read before trying again?"@en ;
    solid-memo:back "409 from an N3 Patch and 412 from an `If-Match` write"@en ;
    solid-memo:backNote "A patch whose `where` or `deletes` no longer match gets 409, and a stale `If-Match` gets 412; both usually mean \"re-read and retry\". A 409 from a `where` that matches twice needs a sharper `where`, not a retry."@en ;
    solid-memo:distractor <#q-read-write-r02-d1> ,
                          <#q-read-write-r02-d2> ,
                          <#q-read-write-r02-d3> .

<#q-read-write-r02-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "400 from a missing `Content-Type` and 422 from a bad patch"@en ;
    solid-memo:distractorNote "Both mean the request itself is malformed, whatever the server state."@en .

<#q-read-write-r02-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "405 from deleting the root and 404 from a POST to nothing"@en ;
    solid-memo:distractorNote "These say the method is never allowed or the target does not exist; retrying will not help."@en .

<#q-read-write-r02-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "301 and 308 from a redirect to the resource's new URL"@en ;
    solid-memo:distractorNote "A redirect says where to send the request; it says nothing about the resource's state."@en .

<#q-read-write-r03>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A new user's Solid pod has only the root container. Your app must create `/journal/2026/entry-1.ttl` at that exact URL. What is the simplest portable request?"@en ;
    solid-memo:back "One PUT to `/journal/2026/entry-1.ttl` with `If-None-Match: *`"@en ;
    solid-memo:backNote "PUT lets you choose the URL, the server creates the missing intermediate containers, and `If-None-Match: *` avoids overwriting an existing entry."@en ;
    solid-memo:distractor <#q-read-write-r03-d1> ,
                          <#q-read-write-r03-d2> ,
                          <#q-read-write-r03-d3> .

<#q-read-write-r03-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "One POST to `/journal/2026/` with `Slug: entry-1.ttl`"@en ;
    solid-memo:distractorNote "The container doesn't exist (404), and a Slug would not guarantee the name."@en .

<#q-read-write-r03-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A POST per container with an LDP type link, then a PUT"@en ;
    solid-memo:distractorNote "Solid Protocol v0.11 no longer guarantees that route, and it is unnecessary."@en .

<#q-read-write-r03-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "One PATCH to `/journal/` adding an `ldp:contains` triple for the entry"@en ;
    solid-memo:distractorNote "Containment triples cannot be written directly; the server answers 409."@en .

<#q-read-write-r04>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your app's PATCHes work on one Solid server but get `415 Unsupported Media Type` on another, which does list PATCH in `Allow`. What should it check?"@en ;
    solid-memo:back "The `Accept-Patch` header the second server advertises"@en ;
    solid-memo:backNote "415 means the server does not take the patch's media type, and it lists the ones it does take in `Accept-Patch`. N3 Patch is required, SPARQL Update is optional, and real servers differ, so read the header rather than assume."@en ;
    solid-memo:distractor <#q-read-write-r04-d1> ,
                          <#q-read-write-r04-d2> ,
                          <#q-read-write-r04-d3> .

<#q-read-write-r04-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Whether the second server serves JSON-LD"@en ;
    solid-memo:distractorNote "All servers must serve JSON-LD for RDF sources, and it doesn't affect patching."@en .

<#q-read-write-r04-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Whether the second server requires `If-Match` on every PATCH"@en ;
    solid-memo:distractorNote "A server that required a conditional request would answer `428 Precondition Required`, not 415."@en .

<#q-read-write-r04-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Whether the app has write access to the document"@en ;
    solid-memo:distractorNote "Missing permission is refused with 401 or 403, not 415."@en .

<#q-read-write-r05>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your app uploads a photo to a Solid pod and wants to record who took it, in the most portable way. Which sequence fits?"@en ;
    solid-memo:back "Upload with its `Content-Type`, then N3 Patch its `describedby` resource"@en ;
    solid-memo:backNote "Files are written with their real media type, and metadata about them goes into the description resource the server advertises with `rel=\"describedby\"` (compared case-insensitively; NSS 6.0.0 sends `describedBy`), which accepts an N3 Patch. The protocol does not promise every server such a link, so check that it is there."@en ;
    solid-memo:distractor <#q-read-write-r05-d1> ,
                          <#q-read-write-r05-d2> ,
                          <#q-read-write-r05-d3> .

<#q-read-write-r05-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Upload the bytes, then PUT the creator to the photo's URL with `.meta` appended"@en ;
    solid-memo:distractorNote "The protocol doesn't fix the description resource's name, and on CSS 7.2 a PUT there gets 405; follow the `describedby` link and PATCH."@en .

<#q-read-write-r05-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Upload the bytes as `text/turtle` with the creator triple added at the end"@en ;
    solid-memo:distractorNote "That corrupts the image and stores it under the wrong media type."@en .

<#q-read-write-r05-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Upload the bytes without a `Content-Type`, so the server detects the type itself"@en ;
    solid-memo:distractorNote "A body without `Content-Type` is rejected with 400."@en .

# Chapter 7: Identity and authentication.
<#ch-identity>
    a solid-memo:Chapter ,
      schema:Syllabus ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <> ;
    schema:position 6 ;
    dcterms:title "Identity and authentication"@en ;
    dcterms:description "How Solid logs people in: WebIDs and their profiles, the Solid-OIDC login flow, the trust anchor `solid:oidcIssuer`, and the four defences (PKCE, the `iss` check, DPoP and Client ID Documents) that make one login safe to use at many pods."@en ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:reviewQuestion <#q-identity-r01> ,
                              <#q-identity-r02> ,
                              <#q-identity-r03> ,
                              <#q-identity-r04> ,
                              <#q-identity-r05> ,
                              <#q-identity-r06> ,
                              <#q-identity-r07> ,
                              <#q-identity-r08> .

<#ch-identity-1>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-identity> ;
    schema:position 0 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Why identity is different in Solid

A classic web app keeps its own accounts, or offers "Sign in with X" for a few providers it registered with in advance. An **identity provider** is the server where you log in. After login it hands the app a **token**: a signed note the app can show to other servers as proof of who you are.

---

Solid wants something different: the user chooses their storage, their identity provider and their apps separately. A pod then has **no existing trust relationship** with the user's identity provider, and apps are often **ephemeral**: nobody registered them with the pod or the provider beforehand. To solve these two problems, Solid needs four things that classic logins don't:

1. a **global user identifier** that anyone can look up (the WebID);
2. a way to **discover which identity provider** may vouch for that identifier (`solid:oidcIssuer`);
3. a **global client identifier**, so an app (the *client*) can say who it is without registering first (a Client ID Document);
4. **tokens that can't be replayed**, that is, reused by whoever receives them, because one token is shown to many pods (DPoP).

This chapter takes them one at a time, then puts them together."""@en ;
    solid-memo:checkedBy <#q-identity-1a> .

<#q-identity-1a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A Solid pod receives a request from an app it has never heard of, on behalf of a user whose identity provider it has never heard of. Why can't the pod rely on a pre-registered list?"@en ;
    solid-memo:back "Users pick providers and apps the pod has never seen"@en ;
    solid-memo:backNote "Users pick providers and apps freely, so a pod meets providers and apps it has never seen before. Solid-OIDC names these two gaps (no prior trust, ephemeral clients) as its design drivers."@en ;
    solid-memo:distractor <#q-identity-1a-d1> ,
                          <#q-identity-1a-d2> ,
                          <#q-identity-1a-d3> .

<#q-identity-1a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Pods can only check users stored on the same server"@en ;
    solid-memo:distractorNote "Solid users log in with a provider anywhere on the web; the pod's job is to check identities that come from elsewhere."@en .

<#q-identity-1a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Apps must first copy the data into their own database"@en ;
    solid-memo:distractorNote "Solid separates apps from storage; apps read the data from the pod."@en .

<#q-identity-1a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A list of all providers would be too large to download"@en ;
    solid-memo:distractorNote "Size isn't the issue; no such list can exist when anyone may run a provider or write an app."@en .

<#ch-identity-2>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-identity> ;
    schema:position 1 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## WebID and the profile document

A **WebID** is an HTTP(S) URI that denotes an **agent**: a person, an organisation, a group or a piece of software. Looking it up gives the **WebID profile document**, an RDF document that describes that agent. This is the documents-versus-things split from Chapter 2: in `https://alice.example/profile/card#me`, the part before `#` names the document and `#me` names Alice herself.

```text
https://alice.example/profile/card      ← the profile document
https://alice.example/profile/card#me   ← Alice (her WebID)
```

---

Profiles are served as Turtle or JSON-LD (Chapter 3); readers ask for either with the `Accept` header (Chapter 2). Use **HTTPS** WebIDs: Solid-OIDC requires tokens to travel only over HTTPS. ⚠ Local test servers are the exception: as of October 2026, CSS 7.2 accepts `http` WebIDs and issuers only when the host name is `localhost` or ends in `.localhost` (so not `127.0.0.1`), which is why the examples in this chapter use `http://localhost:3000/`.

A WebID is just a URL, so **it doesn't have to live in your pod**. Inrupt's PodSpaces issues WebIDs on `id.inrupt.com` while pods live on `storage.inrupt.com`, and CSS can link an account to a WebID hosted elsewhere."""@en ;
    solid-memo:checkedBy <#q-identity-2a> ,
                         <#q-identity-2b> .

<#q-identity-2a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "What does the Solid WebID `https://alice.example/profile/card#me` identify?"@en ;
    solid-memo:back "Alice, the agent the profile describes"@en ;
    solid-memo:backNote "A WebID denotes an agent; dereferencing it gives the profile document that describes that agent."@en ;
    solid-memo:distractor <#q-identity-2a-d1> ,
                          <#q-identity-2a-d2> ,
                          <#q-identity-2a-d3> .

<#q-identity-2a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The profile document at that address"@en ;
    solid-memo:distractorNote "The document is the URL without `#me`; the WebID names the agent it describes."@en .

<#q-identity-2a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Alice's pod and everything stored in it"@en ;
    solid-memo:distractorNote "A pod is a storage found through `pim:storage`, not the WebID itself."@en .

<#q-identity-2a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Alice's login account at her identity provider"@en ;
    solid-memo:distractorNote "The account and its credentials live at the provider; the WebID is a public identifier."@en .

<#q-identity-2b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app assumes a user's pod is always at the same origin as their WebID. Why is that a bug?"@en ;
    solid-memo:back "The WebID can be hosted somewhere other than the pod"@en ;
    solid-memo:backNote "A WebID is only a URL; PodSpaces, for example, uses `id.inrupt.com` for WebIDs and `storage.inrupt.com` for pods. Find the storage by following `pim:storage` or Link headers."@en ;
    solid-memo:distractor <#q-identity-2b-d1> ,
                          <#q-identity-2b-d2> ,
                          <#q-identity-2b-d3> .

<#q-identity-2b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Pods are always hosted on the identity provider's origin"@en ;
    solid-memo:distractorNote "The provider, the WebID host and the storage can all be different servers."@en .

<#q-identity-2b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The pod is always found by appending `/storage/` to the WebID"@en ;
    solid-memo:distractorNote "There is no fixed path, and guessing URLs is exactly what Solid apps must not do."@en .

<#q-identity-2b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Browsers block apps from reading a WebID's origin"@en ;
    solid-memo:distractorNote "The origin of any URL is easy to read; the problem is that it tells you nothing about the pod."@en .

<#ch-identity-3>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-identity> ;
    schema:position 2 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## What a profile contains

The Solid WebID Profile draft (v1.0.0, a Draft Community Group Report of January 2026) lists what a profile holds:

```turtle
PREFIX solid: <http://www.w3.org/ns/solid/terms#>
PREFIX foaf:  <http://xmlns.com/foaf/0.1/>
PREFIX pim:   <http://www.w3.org/ns/pim/space#>
PREFIX ldp:   <http://www.w3.org/ns/ldp#>
PREFIX rdfs:  <http://www.w3.org/2000/01/rdf-schema#>

<#me> a foaf:Agent ;
    solid:oidcIssuer   <https://idp.example> ;                 # who may log me in
    pim:storage        <https://alice.pod.example/> ;          # my pods (0 or more)
    pim:preferencesFile <https://alice.pod.example/settings/prefs.ttl> ;  # private
    ldp:inbox          <https://alice.pod.example/inbox/> ;    # 0 or 1
    rdfs:seeAlso       <https://alice.pod.example/profile/extended.ttl> ;
    foaf:isPrimaryTopicOf <https://alice.pod.example/profile/extended.ttl> .
```

`solid:oidcIssuer` names the identity providers allowed to log in as you (Step 7.9). `pim:storage` points to your pods, and `ldp:inbox` to an inbox others can post to. The **preferences file** holds settings, such as the link to the private type index, and is meant to be readable only by the owner's logged-in apps. `rdfs:seeAlso` and `foaf:isPrimaryTopicOf` point to **extended profile documents** holding more data.

---

The draft makes `pim:storage`, `ldp:inbox` and the extended-profile links optional (it allows zero `pim:storage` triples), and some servers write none. On CSS 7.2 (recorded October 2026), a new account's profile is only this:

```turtle
@prefix foaf: <http://xmlns.com/foaf/0.1/>.
@prefix solid: <http://www.w3.org/ns/solid/terms#>.
@prefix pim: <http://www.w3.org/ns/pim/space#>.

<>
    a foaf:PersonalProfileDocument;
    foaf:maker <http://localhost:3000/alice/profile/card#me>;
    foaf:primaryTopic <http://localhost:3000/alice/profile/card#me>.

<http://localhost:3000/alice/profile/card#me>
    solid:oidcIssuer <http://localhost:3000/>;
    a foaf:Person.
```

There is no `pim:storage`, and not even the `pim:preferencesFile` the draft requires, so apps must not count on any of these links: they fall back to walking the Link headers up to the storage root (Chapter 5)."""@en ;
    solid-memo:checkedBy <#q-identity-3a> .

<#q-identity-3a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app has a user's WebID and needs to know where to save their notes. Which profile predicate should it follow?"@en ;
    solid-memo:back "`pim:storage`" ;
    solid-memo:backNote "`pim:storage` links the agent to their storages (pods); a profile may list zero or more, so apps also need a fallback."@en ;
    solid-memo:distractor <#q-identity-3a-d1> ,
                          <#q-identity-3a-d2> ,
                          <#q-identity-3a-d3> .

<#q-identity-3a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`solid:oidcIssuer`" ;
    solid-memo:distractorNote "That names the identity provider, which need not store any data."@en .

<#q-identity-3a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`pim:preferencesFile`" ;
    solid-memo:distractorNote "That is a private settings document, not the storage root."@en .

<#q-identity-3a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`rdfs:seeAlso`" ;
    solid-memo:distractorNote "That points to more profile data, not to where data should be saved."@en .

<#ch-identity-4>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-identity> ;
    schema:position 3 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Protected profile data

`solid:oidcIssuer` decides who may log in as you. So the Solid WebID Profile draft calls it a **protected triple**: servers MUST refuse a PUT or PATCH that changes it, with **409 Conflict**. Other profile data can be written where the server allows it.

⚠ As of October 2026, CSS 7.2 does not enforce this: the owner's N3 Patch that swaps `solid:oidcIssuer` succeeds with `205 Reset Content`. Treat the profile as something only the user and apps she trusts should be able to write.

Some servers go further. Inrupt's **Enterprise Solid Server (ESS)** issues WebIDs (like `https://id.inrupt.com/alice`) from a separate WebID service. Apps cannot rely on the Solid Protocol to edit those documents, and ESS restricts which apps may modify them. So Inrupt advises apps to write profile data to the **extended profile**, an ordinary resource in the pod linked from the WebID."""@en ;
    solid-memo:checkedBy <#q-identity-4a> ,
                         <#q-identity-4b> .

<#q-identity-4a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Why does the Solid WebID Profile draft require servers to refuse a PATCH that changes `solid:oidcIssuer`?"@en ;
    solid-memo:back "Changing it would change who may log in as that person"@en ;
    solid-memo:backNote "`solid:oidcIssuer` names the providers trusted to vouch for the WebID, so an attacker who could edit it could log in as you. The draft says servers MUST answer such writes with 409, though CSS 7.2 (2026) still accepts them."@en ;
    solid-memo:distractor <#q-identity-4a-d1> ,
                          <#q-identity-4a-d2> ,
                          <#q-identity-4a-d3> .

<#q-identity-4a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The triple is generated from the pod's ACL and can't be stored"@en ;
    solid-memo:distractorNote "It is ordinary profile data; it is protected because of what it controls."@en .

<#q-identity-4a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Profiles must be read-only on every Solid server"@en ;
    solid-memo:distractorNote "The draft protects only certain triples; other profile data can be written where the server allows it."@en .

<#q-identity-4a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "N3 Patch can't express a change to an IRI object"@en ;
    solid-memo:distractorNote "N3 Patch can insert and delete any triple without blank nodes."@en .

<#q-identity-4b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app wants to save a link in the profile of a user whose WebID is hosted by Inrupt's Enterprise Solid Server (ESS). Where should it write?"@en ;
    solid-memo:back "To the user's extended profile document in their pod"@en ;
    solid-memo:backNote "ESS restricts editing the WebID document, so Inrupt recommends writing to the extended profile, which is a normal pod resource linked from the WebID."@en ;
    solid-memo:distractor <#q-identity-4b-d1> ,
                          <#q-identity-4b-d2> ,
                          <#q-identity-4b-d3> .

<#q-identity-4b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Into the WebID document itself with a PUT"@en ;
    solid-memo:distractorNote "ESS restricts WebID edits to its own WebID service and to approved apps; ordinary apps can't rely on writing it."@en .

<#q-identity-4b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Into the identity provider's metadata document"@en ;
    solid-memo:distractorNote "That document describes the provider, and apps can't write to it."@en .

<#q-identity-4b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Into a new `.meta` resource next to the WebID"@en ;
    solid-memo:distractorNote "Description resources aren't part of the profile, and the WebID isn't in the pod anyway."@en .

<#ch-identity-5>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-identity> ;
    schema:position 4 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Access tokens and ID tokens

Two older standards do the heavy lifting. **OAuth 2.0** is about *authorization*: getting an **access token** that a client presents to a server to reach a resource. **OpenID Connect (OIDC)** adds *authentication* on top: an **ID token** that says who logged in. The server that logs people in is the **OpenID Provider (OP)**; Inrupt calls it the "Solid Identity Provider".

---

Both tokens are usually **JWTs**: a JSON object signed by its issuer, so anyone can check it wasn't altered. Its fields are called **claims**. A Solid-OIDC ID token looks like this:

```json
{ "webid": "https://janedoe.com/web#id",
  "iss": "https://idp.example.com",
  "sub": "janedoe",
  "aud": ["https://client.example.com/client_id", "solid"],
  "azp": "https://client.example.com/client_id",
  "iat": 1311280970, "exp": 1311281970 }
```

`iss` is who issued it; `sub` is only the user's local ID at that provider; `webid` is Solid's global identity; `iat`/`exp` are the issue and expiry times. `aud` says who it's for: the app (`azp`) and also `"solid"`, because any Solid server on the web may receive it.

---

Access tokens for Solid carry `aud` `"solid"` too. On CSS 7.2 (recorded October 2026), an access token issued to a script through client credentials (Step 13.5) had these claims; there was no ID token, so the access token itself carries `webid`. Its `sub` is the client's ID, not the WebID:

```json
{ "webid": "http://localhost:3000/alice/profile/card#me",
  "jti": "JbJ9i9K3kLSM-viA9zClg",
  "sub": "solid-curl_2814e0d3-…",
  "iss": "http://localhost:3000/",
  "aud": "solid",
  "client_id": "solid-curl_2814e0d3-…",
  "cnf": { "jkt": "w6cV4pf5zwfXr7oTQUrK6EcSZQ8a1Sxi6j88VCv5SXw" },
  "iat": 1791408787, "exp": 1791409387 }
```

It expires after 600 s; `cnf.jkt` is explained in Step 7.10."""@en ;
    solid-memo:checkedBy <#q-identity-5a> ,
                         <#q-identity-5b> .

<#q-identity-5a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In OAuth 2.0 and OpenID Connect, what is the difference between an ID token and an access token?"@en ;
    solid-memo:back "An ID token says who logged in; an access token grants access"@en ;
    solid-memo:backNote "OAuth 2.0 issues access tokens for authorization; OpenID Connect adds the ID token, which carries claims about the authenticated user."@en ;
    solid-memo:distractor <#q-identity-5a-d1> ,
                          <#q-identity-5a-d2> ,
                          <#q-identity-5a-d3> .

<#q-identity-5a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An ID token grants access to the pod; an access token says who you are"@en ;
    solid-memo:distractorNote "The purposes are the other way round."@en .

<#q-identity-5a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An ID token is unsigned; an access token is a signed JWT"@en ;
    solid-memo:distractorNote "In Solid-OIDC the ID token is a signed JWT too; the two tokens differ in purpose, not in being signed."@en .

<#q-identity-5a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An ID token lasts forever; an access token expires"@en ;
    solid-memo:distractorNote "ID tokens carry a required `exp` claim and expire too."@en .

<#q-identity-5b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid server receives a Solid-OIDC access token whose `aud` claim names only the app's client ID. Why might it reject it?"@en ;
    solid-memo:back "Its `aud` lacks `\"solid\"`, so it isn't for pods"@en ;
    solid-memo:backNote "In Solid a token's audience is the client plus any Solid server, so `aud` must include `\"solid\"`; CSS's verifier checks this on the access token."@en ;
    solid-memo:distractor <#q-identity-5b-d1> ,
                          <#q-identity-5b-d2> ,
                          <#q-identity-5b-d3> .

<#q-identity-5b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Its `aud` must hold the pod's own URL instead"@en ;
    solid-memo:distractorNote "`\"solid\"` is a fixed string that covers every Solid server, so no pod URL is needed."@en .

<#q-identity-5b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Its `aud` tells pods to skip checking the issuer"@en ;
    solid-memo:distractorNote "Nothing in `aud` switches off the issuer check; it always applies."@en .

<#q-identity-5b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Its `aud` should name the user's WebID instead"@en ;
    solid-memo:distractorNote "The WebID goes in the `webid` claim; `aud` names who the token is for."@en .

<#ch-identity-6>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-identity> ;
    schema:position 5 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## The authorization code flow

Solid uses OIDC's **authorization code flow**:

1. The app redirects the user to the OP.
2. The user logs in there (password, passkey… the app never sees it) and consents.
3. The OP redirects back to the app with a one-time **code**.
4. The app swaps the code for tokens at the OP's **token endpoint**.

---

The app finds the OP's endpoints and signing keys in the OP's metadata at `/.well-known/openid-configuration`. On CSS 7.2 (recorded October 2026) it includes these keys, and further ones for the `issuer`, the `token_endpoint` and the DPoP signing algorithms the OP accepts:

```json
{"authorization_endpoint":"http://localhost:3000/.oidc/auth",
 "claims_supported":["azp","sub","webid","sid","auth_time","iss"],
 "code_challenge_methods_supported":["S256"]}
```

In step 1 the app sends **scopes**: what the app asks for. `openid` asks for an ID token. Solid adds a `webid` scope for the `webid` claim; an OP that supports Solid-OIDC advertises it in `scopes_supported`. `offline_access` asks for a **refresh token**, which gets new tokens later without the user present (Step 13.7)."""@en ;
    solid-memo:checkedBy <#q-identity-6a> ,
                         <#q-identity-6b> .

<#q-identity-6a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "In the OpenID Connect authorization code flow, what does the app receive when the user is redirected back from the OP?"@en ;
    solid-memo:back "A one-time code it exchanges for tokens"@en ;
    solid-memo:backNote "The redirect carries a short-lived code; the app then calls the token endpoint to exchange it for the ID token (and access and refresh tokens)."@en ;
    solid-memo:distractor <#q-identity-6a-d1> ,
                          <#q-identity-6a-d2> ,
                          <#q-identity-6a-d3> .

<#q-identity-6a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The user's password, encrypted for the app"@en ;
    solid-memo:distractorNote "The user authenticates at the OP and the app never sees credentials."@en .

<#q-identity-6a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An access token valid for every pod"@en ;
    solid-memo:distractorNote "Tokens come from the token endpoint after the code exchange, not in the redirect."@en .

<#q-identity-6a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The user's WebID profile document"@en ;
    solid-memo:distractorNote "The app fetches the profile itself; the redirect carries the code, not the profile."@en .

<#q-identity-6b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Which scope makes a Solid-OIDC provider put the user's WebID in the ID token?"@en ;
    solid-memo:back "`webid`" ;
    solid-memo:backNote "Solid-OIDC adds the `webid` scope, which requests the `webid` claim; a conformant OP lists it in `scopes_supported`."@en ;
    solid-memo:distractor <#q-identity-6b-d1> ,
                          <#q-identity-6b-d2> ,
                          <#q-identity-6b-d3> .

<#q-identity-6b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`openid`" ;
    solid-memo:distractorNote "It asks for an ID token, but the `webid` claim needs the `webid` scope."@en .

<#q-identity-6b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`profile`" ;
    solid-memo:distractorNote "A standard OIDC scope for name and picture, not Solid's global identity."@en .

<#q-identity-6b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`offline_access`" ;
    solid-memo:distractorNote "It asks for a refresh token, not for any identity claim."@en .

<#ch-identity-7>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-identity> ;
    schema:position 6 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## PKCE: protecting the code

Browser apps are **public clients**: they can't keep a secret. Without extra protection, an attacker who intercepts the redirect's code could exchange it for tokens. **PKCE** (RFC 7636) stops this.

A **hash** is a one-way fingerprint: easy to compute from the input, impossible to reverse. PKCE uses the SHA-256 hash, and BASE64URL turns the result into URL-safe text:

1. Before redirecting, the app makes a random **code verifier** (43-128 characters) and keeps it.
2. It sends `code_challenge = BASE64URL(SHA256(verifier))` with `code_challenge_method=S256`.
3. At the token endpoint it sends the verifier, and the OP recomputes the hash and compares.

The attacker has the code and maybe the challenge, but not the verifier, and the hash can't be reversed to get it. An OP that supports this lists `S256` in `code_challenge_methods_supported` in its metadata (Step 7.6)."""@en ;
    solid-memo:checkedBy <#q-identity-7a> ,
                         <#q-identity-7b> .

<#q-identity-7a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "In an OAuth login, an attacker intercepts the authorization code on its way to a PKCE-using app. Why can't they redeem it?"@en ;
    solid-memo:back "They lack the code verifier that only the app holds"@en ;
    solid-memo:backNote "The token endpoint requires the verifier whose S256 hash matches the challenge sent earlier, and only the app has it."@en ;
    solid-memo:distractor <#q-identity-7a-d1> ,
                          <#q-identity-7a-d2> ,
                          <#q-identity-7a-d3> .

<#q-identity-7a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The code is encrypted with the user's password"@en ;
    solid-memo:distractorNote "Codes aren't encrypted with passwords; PKCE works by proving knowledge of the verifier."@en .

<#q-identity-7a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The OP accepts codes only from the user's IP address"@en ;
    solid-memo:distractorNote "PKCE has nothing to do with IP addresses."@en .

<#q-identity-7a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The code challenge is secret and never leaves the app"@en ;
    solid-memo:distractorNote "The challenge is sent in the authorization request; it's the verifier that stays secret."@en .

<#q-identity-7b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In PKCE (RFC 7636), what does the app send with the redirect, and what does it keep for the token request?"@en ;
    solid-memo:back "It sends the challenge and keeps the verifier"@en ;
    solid-memo:backNote "The app sends `code_challenge` (the S256 hash) up front and reveals the verifier only at the token endpoint, where the OP recomputes the hash."@en ;
    solid-memo:distractor <#q-identity-7b-d1> ,
                          <#q-identity-7b-d2> ,
                          <#q-identity-7b-d3> .

<#q-identity-7b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It sends the verifier and keeps the challenge"@en ;
    solid-memo:distractorNote "The other way round; the verifier must not travel through the browser redirect."@en .

<#q-identity-7b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It sends both and keeps neither for later"@en ;
    solid-memo:distractorNote "Then an interceptor would hold everything needed to redeem the code."@en .

<#q-identity-7b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It sends a password hash and keeps the code"@en ;
    solid-memo:distractorNote "The app never handles the user's password; the OP does."@en .

<#ch-identity-8>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-identity> ;
    schema:position 7 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## The `iss` check: stopping mix-up

A second attack, **mix-up**, targets apps that talk to many OPs, as Solid apps do: the attacker tricks the app into sending a code to the wrong provider. Say a user picks an honest provider, but an attacker makes the app believe she chose the attacker's provider, which the app also supports. She logs in at the honest provider, its code comes back, and the app sends that code to the attacker's token endpoint. RFC 9207 adds an `iss` parameter to the redirect back, naming the OP that issued the code:

```http
Location: https://app.example/callback?code=m-OrTP...&iss=https%3A%2F%2Fidp.example
```

In the example, `iss` names the honest provider, not the one the app expected, so the app stops. The Solid-OIDC draft of July 2026 makes this mandatory: the OP must include `iss`, and the app must check it equals the OP it sent the user to, by exact string match, and must not redeem the code otherwise.

⚠ As of October 2026 this rule is in the July 2026 draft but not in the published Solid-OIDC v0.1.0 of March 2022. Inrupt's and solidcommunity.net's OPs already advertise support for `iss`."""@en ;
    solid-memo:checkedBy <#q-identity-8a> ,
                         <#q-identity-8b> .

<#q-identity-8a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In a Solid-OIDC login, what should an app do when the `iss` in the redirect doesn't match the OP it sent the user to?"@en ;
    solid-memo:back "Refuse to redeem the code and abort the login"@en ;
    solid-memo:backNote "Under the July 2026 Solid-OIDC draft and RFC 9207, a missing or mismatched `iss` means the code must not be redeemed."@en ;
    solid-memo:distractor <#q-identity-8a-d1> ,
                          <#q-identity-8a-d2> ,
                          <#q-identity-8a-d3> .

<#q-identity-8a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Redeem the code at the OP named in `iss`"@en ;
    solid-memo:distractorNote "That is exactly what a mix-up attacker wants."@en .

<#q-identity-8a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Ignore `iss`, because PKCE already covers this"@en ;
    solid-memo:distractorNote "PKCE stops code interception, not mix-up between providers."@en .

<#q-identity-8a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Redeem it, then check the ID token's issuer later"@en ;
    solid-memo:distractorNote "The code would already have been sent to the wrong party."@en .

<#q-identity-8b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Why does the OAuth mix-up attack matter more for Solid apps than for an app with one \"Sign in with X\" button?"@en ;
    solid-memo:back "Solid apps talk to many OPs, which mix-up exploits"@en ;
    solid-memo:backNote "Mix-up tricks an app that works with several providers into sending a code to the wrong one; Solid apps meet whatever OP each user chose."@en ;
    solid-memo:distractor <#q-identity-8b-d1> ,
                          <#q-identity-8b-d2> ,
                          <#q-identity-8b-d3> .

<#q-identity-8b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Solid OPs skip PKCE, so codes are unprotected"@en ;
    solid-memo:distractorNote "Solid-OIDC assumes the code flow with PKCE."@en .

<#q-identity-8b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Solid apps redeem codes at the pod, not the OP"@en ;
    solid-memo:distractorNote "Codes are always redeemed at the OP's token endpoint."@en .

<#q-identity-8b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In Solid the `iss` value is the user's WebID"@en ;
    solid-memo:distractorNote "`iss` names the provider that issued the code, not the user."@en .

<#ch-identity-9>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-identity> ;
    schema:position 8 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Issuer discovery: the trust anchor

Anyone can run an OP and sign a token saying `"webid": "https://alice.example/profile/card#me"`. Solid is safe because **a token is believed only if Alice's own profile lists its issuer** in `solid:oidcIssuer`. A verifier fetches the `webid`'s profile, checks the token's `iss` is listed, then checks the signature.

Apps use the same link to **start** a login. A provider list or a typed issuer URL is fine too: the pod still checks `iss`. Never **guess** the OP from the WebID's domain or assume a default; WebID host, OP and pod are often different servers.

---

The match is exact, trailing slash included. On CSS 7.2 (recorded October 2026), the two agree character for character:

```text
profile:      solid:oidcIssuer <http://localhost:3000/>
OP metadata:  "issuer":"http://localhost:3000/"
```

⚠ As of October 2026, CSS 7.2, NSS 6 and, by its documented default, ESS 2.7 issue tokens only for WebIDs of their own accounts or linked to one. On CSS 7.2 a linked WebID gets tokens before its profile lists that provider: pods answer 401 until it does, and CSS pods keep doing so for up to two minutes more, as they cache issuer lists. So after login, compare `iss` exactly with the profile's issuers (`https://solidcommunity.net/` has a trailing slash, `https://login.inrupt.com` none) and show a clear error (Step 12.6)."""@en ;
    solid-memo:checkedBy <#q-identity-9a> ,
                         <#q-identity-9b> .

<#q-identity-9a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid, a malicious OpenID Provider signs a valid-looking token claiming Alice's WebID. What stops a pod from accepting it?"@en ;
    solid-memo:back "Alice's profile doesn't list that OP as an issuer"@en ;
    solid-memo:backNote "Verifiers fetch the WebID profile and accept the token only if its `iss` appears in a `solid:oidcIssuer` triple there."@en ;
    solid-memo:distractor <#q-identity-9a-d1> ,
                          <#q-identity-9a-d2> ,
                          <#q-identity-9a-d3> .

<#q-identity-9a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Every pod keeps a central list of approved OPs"@en ;
    solid-memo:distractorNote "Solid deliberately has no central list; trust comes from each user's profile."@en .

<#q-identity-9a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The token's signature can only be made by Alice"@en ;
    solid-memo:distractorNote "The OP signs the token, not Alice."@en .

<#q-identity-9a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "OPs may only issue tokens for WebIDs on their own domain"@en ;
    solid-memo:distractorNote "Some OPs restrict themselves this way, but nothing makes a malicious OP do so; only the profile check stops it."@en .

<#q-identity-9b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A user logs into a Solid app by entering the WebID `https://id.inrupt.com/alice`. How should the app find her OpenID Provider?"@en ;
    solid-memo:back "Read `solid:oidcIssuer` from her WebID profile"@en ;
    solid-memo:backNote "The profile's `solid:oidcIssuer` is the authoritative pointer to the user's OP, and apps must not infer it from the WebID's domain or assume a default."@en ;
    solid-memo:distractor <#q-identity-9b-d1> ,
                          <#q-identity-9b-d2> ,
                          <#q-identity-9b-d3> .

<#q-identity-9b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Use the WebID's origin, `https://id.inrupt.com`"@en ;
    solid-memo:distractorNote "The OP may be on a different origin; guessing can send her to the wrong server."@en .

<#q-identity-9b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Ask the pod for its `/.well-known/openid-configuration`"@en ;
    solid-memo:distractorNote "Pods don't have to be OPs, and the app doesn't know the pod yet."@en .

<#q-identity-9b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Use the app's default provider unless she objects"@en ;
    solid-memo:distractorNote "That is guessing; her profile may list a different OP."@en .

<#ch-identity-10>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-identity> ;
    schema:position 9 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## DPoP: tokens bound to a key

An ordinary OAuth token is a **bearer** token: whoever holds it can use it. Solid shows one token to many pods, so a malicious pod could replay it elsewhere. Solid-OIDC therefore requires **DPoP** (RFC 9449), optional in plain OAuth.

The app makes a key pair and keeps the private key; the OP puts a **thumbprint** (a short hash) of its public key in the token's `cnf.jkt` claim. For **every request**, the app signs a **DPoP proof**, a short JWT holding the method (`htm`), the URL (`htu`), the time (`iat`), a unique id (`jti`) and, with a token, its hash (`ath`). The server checks the proof's key against `cnf.jkt`, and its `htm`/`htu` against this request. A pod that saw your token lacks that key.

---

On CSS 7.2 (recorded October 2026), reading a private note without, then with, a token:

```http
GET /alice/notes/first.ttl HTTP/1.1

HTTP/1.1 401 Unauthorized
WWW-Authenticate: Bearer scope="openid webid"

GET /alice/notes/first.ttl HTTP/1.1
Authorization: DPoP eyJhbGciOiJFUzI…
DPoP: eyJhbGciOiJFUzI1NiIs…

HTTP/1.1 200 OK
```

Each login makes a new key, so a new `jkt`.

⚠ As of October 2026, CSS 7.2 accepts proofs up to about 120 s old (plus 120 s clock tolerance), blocks reused `jti`s and checks `ath` only if present.

DPoP does **not** stop **XSS** (cross-site scripting: an attacker's script in your app), which can sign with the app's key."""@en ;
    solid-memo:checkedBy <#q-identity-10a> ,
                         <#q-identity-10b> .

<#q-identity-10a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid, a malicious pod records a DPoP-bound token you sent it. Why can't it use the token at your real pod?"@en ;
    solid-memo:back "It cannot sign proofs without your app's private key"@en ;
    solid-memo:backNote "The token's `cnf.jkt` binds it to the app's key; every request needs a fresh proof signed with the private key, which the malicious pod never had."@en ;
    solid-memo:distractor <#q-identity-10a-d1> ,
                          <#q-identity-10a-d2> ,
                          <#q-identity-10a-d3> .

<#q-identity-10a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The token is encrypted so only the OP can read it"@en ;
    solid-memo:distractorNote "The pod can read the token; what it lacks is the key to make proofs."@en .

<#q-identity-10a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Tokens are valid only on the pod that requested them"@en ;
    solid-memo:distractorNote "In Solid one token is shown to many pods, which is why DPoP is needed."@en .

<#q-identity-10a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Your real pod blocks requests from other servers' IPs"@en ;
    solid-memo:distractorNote "The protection is cryptographic, not based on network addresses."@en .

<#q-identity-10b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "An attacker injects a script into a Solid notes app (XSS). The app's tokens are DPoP-bound with a non-exportable key. What can the script do?"@en ;
    solid-memo:back "Make requests to the user's pod as the app"@en ;
    solid-memo:backNote "RFC 9449 says plainly that DPoP is no defence against XSS: malicious code in the app can have the browser sign with the app's key. Preventing XSS is a separate job."@en ;
    solid-memo:distractor <#q-identity-10b-d1> ,
                          <#q-identity-10b-d2> ,
                          <#q-identity-10b-d3> .

<#q-identity-10b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing, because the token is bound to the app's key"@en ;
    solid-memo:distractorNote "The script runs inside the app, so it can ask the browser to sign with that key."@en .

<#q-identity-10b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only read the token, never use it"@en ;
    solid-memo:distractorNote "It doesn't need to take the key away; it can make fresh proofs in place."@en .

<#q-identity-10b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only reach pods on the app's own origin"@en ;
    solid-memo:distractorNote "The app talks to pods on any origin, and so can the script."@en .

<#ch-identity-11>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-identity> ;
    schema:position 10 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## How an app identifies itself

The OP must know which app (the **client**) is asking. Solid gives three options:

1. **Client ID Document** (recommended): the `client_id` is an HTTPS URL that serves JSON-LD describing the app.
2. **Dynamic registration**: the app registers itself at the OP at runtime and gets an opaque `client_id`.
3. **Static registration**: a developer registers the app with an OP in advance and gets an ID and secret, typical for scripts (Step 13.5).

---

A Client ID Document uses the context `https://www.w3.org/ns/solid/oidc-context.jsonld`:

```json
{ "@context": ["https://www.w3.org/ns/solid/oidc-context.jsonld"],
  "client_id": "https://app.example/id",
  "client_name": "My Notes",
  "redirect_uris": ["https://app.example/callback"],
  "scope": "openid webid offline_access",
  "grant_types": ["refresh_token", "authorization_code"],
  "response_types": ["code"] }
```

The OP fetches the Client ID Document and refuses a `redirect_uri` that isn't listed. So the document proves that **tokens for this client ID only go to the redirect URIs its URL's owner chose**: another site can't receive them. It does **not** prove the app behaves well. An IETF draft, the **Client ID Metadata Document (CIMD)**, generalises the idea to all of OAuth. It calls itself "largely inspired by" Solid-OIDC, and also lists IndieAuth and OpenID Federation as earlier specs that used URLs as client IDs."""@en ;
    solid-memo:checkedBy <#q-identity-11a> ,
                         <#q-identity-11b> .

<#q-identity-11a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid-OIDC, what does a Client ID Document actually guarantee?"@en ;
    solid-memo:back "Tokens go only to redirect URIs its owner listed"@en ;
    solid-memo:backNote "The OP matches the `redirect_uri` against the document at the client ID URL, so only that URL's controller can receive tokens for it. It says nothing about whether the app is trustworthy."@en ;
    solid-memo:distractor <#q-identity-11a-d1> ,
                          <#q-identity-11a-d2> ,
                          <#q-identity-11a-d3> .

<#q-identity-11a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The app has been reviewed and is safe to use"@en ;
    solid-memo:distractorNote "Nobody vouches for the app's behaviour; the document only fixes where tokens go."@en .

<#q-identity-11a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The app can only read the data the user chooses"@en ;
    solid-memo:distractorNote "Limiting what apps can access is an authorization problem, handled by access control."@en .

<#q-identity-11a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Its tokens can't be replayed at other pods"@en ;
    solid-memo:distractorNote "Stopping replay is DPoP's job, not the client ID's."@en .

<#q-identity-11b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid-OIDC, which `client_id` value is valid for a Client ID Document?"@en ;
    solid-memo:back "An HTTPS URL that serves the app's JSON-LD document"@en ;
    solid-memo:backNote "The client ID is an HTTPS URL that the OP dereferences to get the client's metadata, including its redirect URIs."@en ;
    solid-memo:distractor <#q-identity-11b-d1> ,
                          <#q-identity-11b-d2> ,
                          <#q-identity-11b-d3> .

<#q-identity-11b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The app's display name, such as \"My Notes\""@en ;
    solid-memo:distractorNote "A name goes in `client_name`; the ID must be a dereferenceable URL."@en .

<#q-identity-11b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The WebID of the developer who wrote the app"@en ;
    solid-memo:distractorNote "The client ID identifies the app, not the person who wrote it."@en .

<#q-identity-11b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A random string generated in the browser"@en ;
    solid-memo:distractorNote "A random string can't be dereferenced; that would need registration."@en .

<#ch-identity-12>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-identity> ;
    schema:position 11 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## The whole login, and what the pod learns

Putting it together, a browser login runs like this:

1. The app learns the OP: from `solid:oidcIssuer` in the user's profile, or from the provider the user picked (Step 7.9).
2. The app fetches the OP's `/.well-known/openid-configuration`.
3. It creates a PKCE verifier and redirects to the OP with `scope=openid webid offline_access`, its `client_id` and the challenge.
4. The OP fetches the Client ID Document and checks the redirect URI; the user logs in and consents.
5. The OP redirects back with a code and `iss`; the app checks `iss`.
6. The app makes a DPoP key pair and redeems the code with the verifier and a DPoP proof.
7. It gets a DPoP-bound ID token (and access and refresh tokens).
8. For each pod request, it sends a token plus a fresh DPoP proof.

---

The trust anchor and each defence answer a different attack:

| Mechanism | Stops | Step |
|---|---|---|
| PKCE | an intercepted code being redeemed | 7.7 |
| `iss` check | mix-up between providers | 7.8 |
| `solid:oidcIssuer` (trust anchor) | a provider vouching for someone else's WebID | 7.9 |
| DPoP | a pod replaying your token elsewhere | 7.10 |
| Client ID Document | tokens reaching another site | 7.11 |

After verifying a request, the pod knows three things: the **WebID**, the **client** and the **issuer**. Chapters 8-9 use them in access rules; ACP can match all three (Step 9.1)."""@en ;
    solid-memo:checkedBy <#q-identity-12a> .

<#q-identity-12a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "After a Solid pod verifies a Solid-OIDC request, which facts can its access rules use?"@en ;
    solid-memo:back "The user's WebID, the client ID and the issuer"@en ;
    solid-memo:backNote "A verified request yields the WebID, the client and the issuer; ACP rules can match all three, while WAC matches only the WebID (plus the browser's Origin)."@en ;
    solid-memo:distractor <#q-identity-12a-d1> ,
                          <#q-identity-12a-d2> ,
                          <#q-identity-12a-d3> .

<#q-identity-12a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The user's password and their OP account name"@en ;
    solid-memo:distractorNote "The pod never sees credentials; the OP handles them."@en .

<#q-identity-12a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only the user's WebID, since apps are anonymous"@en ;
    solid-memo:distractorNote "The client ID (`azp`/`client_id`) also reaches the pod."@en .

<#q-identity-12a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The user's IP address and browser fingerprint"@en ;
    solid-memo:distractorNote "Solid-OIDC carries no such data; it identifies the WebID, client and issuer."@en .

<#ch-identity-13>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-identity> ;
    schema:position 12 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Spec vs practice: UMA

The last item of the login in Step 7.12, sending a token to the pod, hides a gap between spec and servers. Solid-OIDC (v0.1.0 and the July 2026 draft alike) says a pod's authorization server SHOULD use **UMA** (User-Managed Access, an OAuth extension in which the pod points apps to an authorization server that issues tokens for that pod). The app trades its ID token there for a pod-specific access token. Deployed servers like CSS instead accept DPoP-bound access tokens directly: the OP's access token carries a `webid` claim, as in the example of Step 7.5. The checks are the same either way: WebID, issuer listed in the profile, signature, DPoP binding. Libraries hide the difference (Step 12.5)."""@en ;
    solid-memo:checkedBy <#q-identity-13a> .

<#q-identity-13a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On CSS 7.2 (2026), a Solid app sends a valid DPoP-bound access token straight to the pod, without any UMA exchange. What happens?"@en ;
    solid-memo:back "CSS accepts it and runs the usual checks on it"@en ;
    solid-memo:backNote "Solid-OIDC says pods SHOULD use UMA, but in 2026 deployed servers like CSS verify DPoP-bound access tokens with a `webid` claim directly, running the same checks."@en ;
    solid-memo:distractor <#q-identity-13a-d1> ,
                          <#q-identity-13a-d2> ,
                          <#q-identity-13a-d3> .

<#q-identity-13a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "CSS rejects it until the app trades an ID token via UMA"@en ;
    solid-memo:distractorNote "The spec says SHOULD use UMA, but CSS accepts the OP's access token directly."@en .

<#q-identity-13a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "CSS accepts it but skips the issuer check"@en ;
    solid-memo:distractorNote "The WebID, issuer, signature and DPoP checks all run on the access token."@en .

<#q-identity-13a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "CSS asks the OP to re-issue it for this pod"@en ;
    solid-memo:distractorNote "No such exchange exists; the pod verifies the token it was given."@en .

<#ch-identity-14>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-identity> ;
    schema:position 13 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Older login methods

Older mechanisms still turn up in tutorials. **WebID-TLS** used browser client certificates instead of an OP. The ecosystem first relied on it; the Solid Protocol now recommends Solid-OIDC and keeps WebID-TLS only as an optional additional method. **WebID-OIDC** was Solid-OIDC's predecessor; its spec repository was archived in 2021. The `solid-auth-client` library calls itself "a legacy browser library" and tells new projects to use `solid-client-authn` instead; its last release was in June 2021. If a tutorial imports `solid-auth-client`, its login code predates DPoP: look for a newer one."""@en ;
    solid-memo:checkedBy <#q-identity-14a> .

<#q-identity-14a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "You find a tutorial that logs users into Solid with WebID-TLS client certificates. What should you conclude?"@en ;
    solid-memo:back "It is outdated; Solid now recommends Solid-OIDC"@en ;
    solid-memo:backNote "The Solid Protocol says the ecosystem first relied on WebID-TLS and now recommends Solid-OIDC, keeping WebID-TLS only as an optional additional method."@en ;
    solid-memo:distractor <#q-identity-14a-d1> ,
                          <#q-identity-14a-d2> ,
                          <#q-identity-14a-d3> .

<#q-identity-14a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It is the newer method that replaces Solid-OIDC"@en ;
    solid-memo:distractorNote "WebID-TLS came first and was superseded, not the other way round."@en .

<#q-identity-14a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It is required for every Solid server to work"@en ;
    solid-memo:distractorNote "The Protocol recommends Solid-OIDC; WebID-TLS remains only as an optional additional method."@en .

<#q-identity-14a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It is the same as Solid-OIDC with another name"@en ;
    solid-memo:distractorNote "WebID-TLS uses client certificates and no OP at all."@en .

<#q-identity-r01>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid login starts from the user's WebID. What is the app's first step, before it knows where to send her to log in?"@en ;
    solid-memo:back "The app reads `solid:oidcIssuer` from the profile"@en ;
    solid-memo:backNote "The app can't start the login until it knows the OP, so reading `solid:oidcIssuer` comes first; the redirect and `iss` check, the code exchange and DPoP-signed pod requests follow."@en ;
    solid-memo:distractor <#q-identity-r01-d1> ,
                          <#q-identity-r01-d2> ,
                          <#q-identity-r01-d3> .

<#q-identity-r01-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The app redeems the code at the token endpoint"@en ;
    solid-memo:distractorNote "A code only exists after the OP redirects back, so the app must know the OP first."@en .

<#q-identity-r01-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The app checks the `iss` in the redirect"@en ;
    solid-memo:distractorNote "The redirect comes after the user has logged in at the OP."@en .

<#q-identity-r01-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The app sends a DPoP proof to the pod"@en ;
    solid-memo:distractorNote "Pod requests come last, once the app holds tokens."@en .

<#q-identity-r02>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid-OIDC, which mechanism lets an app that nobody registered say who it is?"@en ;
    solid-memo:back "A Client ID Document at an HTTPS URL"@en ;
    solid-memo:backNote "Of Solid's four login needs, the global client identifier is met by the Client ID Document; the WebID is the global user ID, `solid:oidcIssuer` finds the provider, and DPoP stops replay."@en ;
    solid-memo:distractor <#q-identity-r02-d1> ,
                          <#q-identity-r02-d2> ,
                          <#q-identity-r02-d3> .

<#q-identity-r02-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A WebID in the user's profile"@en ;
    solid-memo:distractorNote "A WebID identifies the user (or another agent), not the app making the request."@en .

<#q-identity-r02-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A DPoP key pair made by the app"@en ;
    solid-memo:distractorNote "DPoP binds tokens to a key so they can't be replayed; it doesn't name the app."@en .

<#q-identity-r02-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A PKCE verifier sent at login"@en ;
    solid-memo:distractorNote "PKCE protects the code exchange; it doesn't identify the app."@en .

<#q-identity-r03>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid pod receives a request with a valid DPoP-bound token, from an app whose redirect URI is listed in its Client ID Document. But the token's issuer isn't listed in the user's profile. What happens?"@en ;
    solid-memo:back "The pod doesn't believe the token's WebID"@en ;
    solid-memo:backNote "Each piece answers a different question; only the profile's `solid:oidcIssuer` decides which providers may vouch for a WebID, so a token from an unlisted issuer is not believed."@en ;
    solid-memo:distractor <#q-identity-r03-d1> ,
                          <#q-identity-r03-d2> ,
                          <#q-identity-r03-d3> .

<#q-identity-r03-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The pod accepts it, because the app's ID checks out"@en ;
    solid-memo:distractorNote "The Client ID Document says where tokens may go; it can't vouch for the user's identity."@en .

<#q-identity-r03-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The pod accepts it, because DPoP proves it genuine"@en ;
    solid-memo:distractorNote "DPoP proves the sender holds the key, not that the issuer may speak for this WebID."@en .

<#q-identity-r03-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The pod adds the issuer to the profile and goes on"@en ;
    solid-memo:distractorNote "Pods never edit a user's trusted issuers; those are protected triples."@en .

<#q-identity-r04>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid, a user's WebID is `https://id.example/alice`, her OpenID Provider is `https://login.example` and her pod is `https://pods.example/alice/`. Is this setup valid?"@en ;
    solid-memo:back "Yes; all three may be on different hosts"@en ;
    solid-memo:backNote "Solid decouples identity, issuer and storage; the profile links them with `solid:oidcIssuer` and `pim:storage`."@en ;
    solid-memo:distractor <#q-identity-r04-d1> ,
                          <#q-identity-r04-d2> ,
                          <#q-identity-r04-d3> .

<#q-identity-r04-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "No; the OP must be on the WebID's origin"@en ;
    solid-memo:distractorNote "The profile names the OP, which can be anywhere."@en .

<#q-identity-r04-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "No; the WebID must live inside the pod"@en ;
    solid-memo:distractorNote "A WebID is just a URL and can be hosted anywhere."@en .

<#q-identity-r04-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only if the pod's server also runs the OP"@en ;
    solid-memo:distractorNote "Pods and OPs are separate roles that may be on different servers."@en .

<#q-identity-r05>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Which part of a Solid-OIDC login carries the user's global identity?"@en ;
    solid-memo:back "The token's `webid` claim"@en ;
    solid-memo:backNote "Solid-OIDC adds a `webid` claim for the global identity; `sub` is only the OP's local subject. The WebID is trusted once its profile lists the token's issuer."@en ;
    solid-memo:distractor <#q-identity-r05-d1> ,
                          <#q-identity-r05-d2> ,
                          <#q-identity-r05-d3> .

<#q-identity-r05-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The token's `sub` claim"@en ;
    solid-memo:distractorNote "`sub` is only a local ID at the OP and may differ from the WebID."@en .

<#q-identity-r05-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The login request's `client_id`"@en ;
    solid-memo:distractorNote "That identifies the app, not the user."@en .

<#q-identity-r05-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The redirect's `iss` parameter"@en ;
    solid-memo:distractorNote "`iss` names the provider, not the user."@en .

<#q-identity-r06>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In a Solid-OIDC login, which attack does DPoP stop?"@en ;
    solid-memo:back "A pod replaying your token at another pod"@en ;
    solid-memo:backNote "DPoP binds the token to the app's key, so a pod that saw it can't make the proofs needed to use it elsewhere. PKCE protects the code, the `iss` check stops mix-up, and the Client ID Document fixes where tokens go."@en ;
    solid-memo:distractor <#q-identity-r06-d1> ,
                          <#q-identity-r06-d2> ,
                          <#q-identity-r06-d3> .

<#q-identity-r06-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An attacker redeeming an intercepted code"@en ;
    solid-memo:distractorNote "That is PKCE's job: only the app holds the code verifier."@en .

<#q-identity-r06-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An app sending its code to the wrong provider"@en ;
    solid-memo:distractorNote "That is mix-up, which the `iss` check stops."@en .

<#q-identity-r06-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Tokens being sent to another site's callback"@en ;
    solid-memo:distractorNote "The Client ID Document's listed redirect URIs stop that."@en .

<#q-identity-r07>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A user picks provider X from a Solid app's list, but her WebID profile lists only provider Y. Login at X succeeds and the token's `webid` is her WebID. What should the app do?"@en ;
    solid-memo:back "Check `iss` against her profile and show a clear error"@en ;
    solid-memo:backNote "Pods won't accept a token from an issuer her profile doesn't list, so checking `iss` against `solid:oidcIssuer` lets the app show a clear error instead of unexplained 401s. The fix is hers: add X to her profile, or log in at Y."@en ;
    solid-memo:distractor <#q-identity-r07-d1> ,
                          <#q-identity-r07-d2> ,
                          <#q-identity-r07-d3> .

<#q-identity-r07-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing; a successful login means pods will accept her"@en ;
    solid-memo:distractorNote "Pods accept the token only if her profile lists its issuer, and X isn't listed."@en .

<#q-identity-r07-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Add X to her profile's `solid:oidcIssuer` for her"@en ;
    solid-memo:distractorNote "That changes who may log in as her, which only she should decide."@en .

<#q-identity-r07-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Retry the login at X until the pod accepts the token"@en ;
    solid-memo:distractorNote "Every token from X fails the same issuer check at the pod."@en .

<#q-identity-r08>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Which way of finding a Solid user's OpenID Provider counts as guessing it from her WebID?"@en ;
    solid-memo:back "Taking the OP from the WebID's domain"@en ;
    solid-memo:backNote "Guessing means deriving the issuer from the WebID's domain or assuming a default. Issuer-first logins are fine, because verifiers accept a token only if the user's profile lists its issuer."@en ;
    solid-memo:distractor <#q-identity-r08-d1> ,
                          <#q-identity-r08-d2> ,
                          <#q-identity-r08-d3> .

<#q-identity-r08-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Showing a list of providers to pick from"@en ;
    solid-memo:distractorNote "Legitimate; the pod still checks the token's issuer against the profile."@en .

<#q-identity-r08-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Letting the user type their provider's URL"@en ;
    solid-memo:distractorNote "Legitimate for the same reason: the profile has the final say."@en .

<#q-identity-r08-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Reading `solid:oidcIssuer` from the profile"@en ;
    solid-memo:distractorNote "That is the authoritative pointer, not a guess."@en .

# Chapter 8: Web Access Control.
<#ch-wac>
    a solid-memo:Chapter ,
      schema:Syllabus ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <> ;
    schema:position 7 ;
    dcterms:title "Web Access Control"@en ;
    dcterms:description "Write, read and debug Web Access Control (WAC) rules in a Solid pod, and know what a client sees when access is checked."@en ;
    solid-memo:reviewQuestion <#q-wac-r01> ,
                              <#q-wac-r02> ,
                              <#q-wac-r03> ,
                              <#q-wac-r04> ,
                              <#q-wac-r05> .

<#ch-wac-1>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-wac> ;
    schema:position 0 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Authentication vs authorization; rules are data

Chapter 7 answered "who are you?" (*authentication*): after Solid-OIDC login, each request carries a token naming the user's WebID, the app and the issuer. This chapter answers "what may you do?" (*authorization*). Solid keeps them apart: the WAC spec "does not specify mechanisms for authentication".

The rules are ordinary RDF documents (usually Turtle) stored in the pod next to the data they protect, and read and written with the HTTP requests of Chapter 6.

---

Solid has two rule languages. **Web Access Control (WAC)** is older, simpler and the most widely supported; this chapter teaches it. **Access Control Policy (ACP)** is newer and more expressive; Inrupt's ESS uses it, and the Community Solid Server (CSS) offers it as an option. Chapter 9 teaches it. Every Solid server must implement WAC, ACP or both, while clients must conform to both, so a portable app has to cope with either.

Neither is a W3C standard. As of 2026, WAC 1.0.0 (2024-05-12) is a Draft Community Group Report, and ACP 0.9.0 (2022) is an Editor's Draft. CSS 7.2 uses WAC by default."""@en ;
    solid-memo:checkedBy <#q-wac-1a> ,
                         <#q-wac-1b> .

<#q-wac-1a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A user has logged in to a Solid app with Solid-OIDC. What does the pod server still have to decide before answering their request?"@en ;
    solid-memo:back "Whether the stored access rules let that identity do this operation"@en ;
    solid-memo:backNote "Authentication establishes who is asking; authorization then checks that identity against the rule documents stored with the data."@en ;
    solid-memo:distractor <#q-wac-1a-d1> ,
                          <#q-wac-1a-d2> ,
                          <#q-wac-1a-d3> .

<#q-wac-1a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Whether the user's identity provider is registered with the pod"@en ;
    solid-memo:distractorNote "Solid pods keep no registry of approved identity providers; ACP can match on the issuer, but only as part of the stored rules."@en .

<#q-wac-1a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Whether the user's password matches the one stored in the pod"@en ;
    solid-memo:distractorNote "Pods never see passwords; the identity provider handles login."@en .

<#q-wac-1a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Whether the app was installed from the pod's app store"@en ;
    solid-memo:distractorNote "There is no app store; apps are unregistered and identify themselves by a client ID."@en .

<#q-wac-1b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "You are writing a sharing feature for a Solid app that must work on any Solid server. Which access control languages does it need to handle?"@en ;
    solid-memo:back "Both WAC and ACP, because a server may use either"@en ;
    solid-memo:backNote "Every Solid server must implement WAC, ACP or both, so a portable client has to detect which one it faces and handle it."@en ;
    solid-memo:distractor <#q-wac-1b-d1> ,
                          <#q-wac-1b-d2> ,
                          <#q-wac-1b-d3> .

<#q-wac-1b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only WAC, because every server is required to support it"@en ;
    solid-memo:distractorNote "The Solid Protocol allows ACP-only servers, such as Inrupt's ESS."@en .

<#q-wac-1b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only ACP, because WAC has been deprecated"@en ;
    solid-memo:distractorNote "WAC is not deprecated; it is the most widely deployed language."@en .

<#q-wac-1b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Neither, because sharing is handled by the identity provider"@en ;
    solid-memo:distractorNote "Access rules live in the pod and are enforced by the pod server, not the identity provider."@en .

<#ch-wac-2>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-wac> ;
    schema:position 1 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## WAC: finding the ACL

In WAC the rules for a resource live in an **ACL resource**, one of the auxiliary resources of Chapter 5. A server advertises it with a `Link` header whose `rel` is `acl`.

The spec is blunt: "Clients MUST NOT derive the URI of the ACL resource through string operations on the URI of the resource." Appending `.acl` happens to work on CSS and NSS, but it is only their convention, and the ACL may even be on a different server. Always follow the link.

---

On CSS 7.2 (recorded in 2026, other headers left out), Alice, logged in, sent a HEAD on her new note and a GET on its ACL. The note links its ACL, but the ACL doesn't exist yet: the note has no rules of its own, and `Allow` shows that one can be created.

```http
HEAD /alice/notes/first.ttl HTTP/1.1
Authorization: DPoP …
DPoP: …

HTTP/1.1 200 OK
Link: <http://localhost:3000/alice/notes/first.ttl.acl>; rel="acl"

GET /alice/notes/first.ttl.acl HTTP/1.1
Authorization: DPoP …
DPoP: …

HTTP/1.1 404 Not Found
Allow: PATCH, PUT
```

---

A server attaches at most one ACL directly to a resource. Inside it is an unordered set of **authorizations** (`acl:Authorization`), any one of which can permit a request. Each says *what* can be accessed, *how* (the modes) and *who* may do it:

```turtle
@prefix acl: <http://www.w3.org/ns/auth/acl#>.

<#bob-reads>
    a acl:Authorization;
    acl:accessTo <todo.ttl>;                          # what
    acl:mode acl:Read;                                # how
    acl:agent <https://bob.example/profile/card#me>.  # who
```"""@en ;
    solid-memo:checkedBy <#q-wac-2a> ,
                         <#q-wac-2b> .

<#q-wac-2a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your Solid app needs the Web Access Control (WAC) ACL of `https://pod.example/photos/cat.jpg`. How should it find the ACL's URL?"@en ;
    solid-memo:back "Read the `Link` header with `rel=\"acl\"` from a HEAD or GET on the photo"@en ;
    solid-memo:backNote "WAC requires clients to discover the ACL through `Link: rel=\"acl\"`; the `.acl` suffix is only some servers' convention."@en ;
    solid-memo:distractor <#q-wac-2a-d1> ,
                          <#q-wac-2a-d2> ,
                          <#q-wac-2a-d3> .

<#q-wac-2a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Append `.acl` to the photo's URL, as Solid servers name ACLs that way"@en ;
    solid-memo:distractorNote "That is only a convention of some servers; clients must not build the URL by string operations."@en .

<#q-wac-2a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Fetch `/.acl` at the pod root, which holds every rule for the pod"@en ;
    solid-memo:distractorNote "Each resource can have its own ACL; the root ACL is only used when nothing nearer exists."@en .

<#q-wac-2a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Look for an `acl:accessControl` triple in the user's WebID profile"@en ;
    solid-memo:distractorNote "Profiles don't point to ACLs; the resource itself advertises its ACL in a `Link` header."@en .

<#q-wac-2b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front """In this Solid Web Access Control (WAC) authorization, which line decides *who* gets access?

```turtle
@prefix acl: <http://www.w3.org/ns/auth/acl#>.

<#team> a acl:Authorization;
    acl:accessTo <plan.ttl>;
    acl:mode acl:Write;
    acl:agent <https://carol.example/profile/card#me>.
```"""@en ;
    solid-memo:back "`acl:agent <https://carol.example/profile/card#me>`" ;
    solid-memo:backNote "Every authorization says what (`acl:accessTo`), how (`acl:mode`) and who (`acl:agent` and its relatives); it never names servers or identity providers."@en ;
    solid-memo:distractor <#q-wac-2b-d1> ,
                          <#q-wac-2b-d2> ,
                          <#q-wac-2b-d3> .

<#q-wac-2b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`acl:accessTo <plan.ttl>`" ;
    solid-memo:distractorNote "That names what can be accessed, not who."@en .

<#q-wac-2b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`acl:mode acl:Write`" ;
    solid-memo:distractorNote "That names how the resource may be used, not who."@en .

<#q-wac-2b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`a acl:Authorization`" ;
    solid-memo:distractorNote "That only marks the description as an authorization; it names nobody."@en .

<#ch-wac-3>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-wac> ;
    schema:position 2 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## The four modes

WAC has four access modes:

| Mode | Lets you |
|---|---|
| `acl:Read` | view the resource (GET) |
| `acl:Write` | create, change or delete it (PUT, POST, PATCH, DELETE) |
| `acl:Append` | add information but not remove it (POST, PATCH) |
| `acl:Control` | read and write the resource's ACL |

---

Two relationships cause most confusion. First, **Append is a subclass of Write**: if a request needs Append, an agent with Write is allowed too. The reverse is not true; Append never gives Write. Append alone is what you want for a drop box such as an inbox, where people may add messages but not read or remove others' messages.

Second, **Control covers only the ACL**. "Having acl:Control does not imply that the agent has acl:Read or acl:Write access to the resource itself." An owner can even remove their own Write to avoid accidental overwrites, and add it back later because they still have Control.

Finally, if an ACL contains a mode the server doesn't understand, it must carry on as if that mode were not there. Unknown modes "MUST NOT cause increased access"."""@en ;
    solid-memo:checkedBy <#q-wac-3a> ,
                         <#q-wac-3b> .

<#q-wac-3a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid's Web Access Control (WAC), Bob has `acl:Write`, and no other mode, on a container and on everything inside it. Can he POST a new item into it?"@en ;
    solid-memo:back "Yes, because whatever Append allows, Write allows too"@en ;
    solid-memo:backNote "A request needing `acl:Append` is also allowed for agents with `acl:Write`, but not the other way round. Bob's Write covers both the container and the new item."@en ;
    solid-memo:distractor <#q-wac-3a-d1> ,
                          <#q-wac-3a-d2> ,
                          <#q-wac-3a-d3> .

<#q-wac-3a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "No, because Append must always be granted in its own rule"@en ;
    solid-memo:distractorNote "Write already includes Append; listing Append separately is unnecessary."@en .

<#q-wac-3a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "No, because POST requires Control on the container"@en ;
    solid-memo:distractorNote "Control is only for the ACL; POST needs Append or Write."@en .

<#q-wac-3a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only if he also has Read, because writing requires reading"@en ;
    solid-memo:distractorNote "Neither Write nor Append depends on Read."@en .

<#q-wac-3b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid's Web Access Control (WAC), Carol has `acl:Control` but no other mode on a document. What can she do right now, without changing any rules?"@en ;
    solid-memo:back "Read and edit its ACL, but not the document"@en ;
    solid-memo:backNote "Control gives access to the ACL only, but because she can edit the ACL, Carol can give herself Read or Write."@en ;
    solid-memo:distractor <#q-wac-3b-d1> ,
                          <#q-wac-3b-d2> ,
                          <#q-wac-3b-d3> .

<#q-wac-3b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Read and edit the document, since Control includes every mode"@en ;
    solid-memo:distractorNote "Control does not imply Read or Write on the resource itself."@en .

<#q-wac-3b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Read the document but not change it"@en ;
    solid-memo:distractorNote "Control gives no Read on the resource, only access to its ACL."@en .

<#q-wac-3b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Delete the document, since Control is the owner's mode"@en ;
    solid-memo:distractorNote "Deleting needs Write; Control only covers the ACL."@en .

<#ch-wac-4>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-wac> ;
    schema:position 3 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Who and what

**Who** (access subjects):
- `acl:agent <WebID>`: one specific agent.
- `acl:agentClass foaf:Agent`: **everyone**, including requests with no login at all.
- `acl:agentClass acl:AuthenticatedAgent`: anyone who is logged in, with any WebID.
- `acl:agentGroup <group>`: the members of a `vcard:Group`, listed with `vcard:hasMember` in a separate document, which has its own ACL (Step 9.8 puts groups to work).

**What** (access objects): `acl:accessTo <r>` covers resource `r` itself. `acl:default <container/>` is inherited by the container's descendants that have no ACL of their own (Step 8.6).

---

An authorization applies only if it has all four of these: `a acl:Authorization`, at least one `accessTo` or `default`, at least one `acl:mode`, and at least one `acl:agent`, `acl:agentGroup` or `acl:agentClass` (or the `acl:origin` restriction of Step 9.11). Leave one out and the rule silently does nothing.

```turtle
@prefix acl: <http://www.w3.org/ns/auth/acl#>.

# Logged-in users may drop items in this inbox but not read it
<#inbox> a acl:Authorization;
    acl:agentClass acl:AuthenticatedAgent;
    acl:accessTo <./>;
    acl:mode acl:Append.
```

Access is granted when a matching authorization exists, and denied otherwise (the spec also adds an `Origin` check for browser requests, which servers apply unevenly; see Step 9.11). WAC only grants: it has **no deny rules**, so you can't say "everyone except Mallory". To exclude someone, grant to a narrower set instead."""@en ;
    solid-memo:checkedBy <#q-wac-4a> ,
                         <#q-wac-4b> ,
                         <#q-wac-4c> .

<#q-wac-4a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid's Web Access Control (WAC), which authorization makes a document readable by people who have not logged in?"@en ;
    solid-memo:back "One with `acl:agentClass foaf:Agent`"@en ;
    solid-memo:backNote "`foaf:Agent` means every agent, logged in or not; `acl:AuthenticatedAgent` means only logged-in ones."@en ;
    solid-memo:distractor <#q-wac-4a-d1> ,
                          <#q-wac-4a-d2> ,
                          <#q-wac-4a-d3> .

<#q-wac-4a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "One with `acl:agentClass acl:AuthenticatedAgent`"@en ;
    solid-memo:distractorNote "That class requires a logged-in agent; anonymous requests don't match."@en .

<#q-wac-4a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "One with `acl:agentGroup` pointing to a public group"@en ;
    solid-memo:distractorNote "Groups contain specific listed members, not anonymous visitors."@en .

<#q-wac-4a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "One with no `acl:agent`, `acl:agentClass` or `acl:agentGroup` line"@en ;
    solid-memo:distractorNote "An authorization without any subject never applies."@en .

<#q-wac-4b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front """Alice wrote this Solid Web Access Control (WAC) rule, but Bob still gets 403 when he reads the file. What is wrong?

```turtle
@prefix acl: <http://www.w3.org/ns/auth/acl#>.

<#bob> acl:agent <https://bob.example/profile/card#me>;
    acl:accessTo <report.ttl>;
    acl:mode acl:Read.
```"""@en ;
    solid-memo:back "It lacks `a acl:Authorization`, so the rule doesn't apply"@en ;
    solid-memo:backNote "An authorization applies only when it is typed `acl:Authorization` and has a target, a mode and a subject; a missing type silently disables it."@en ;
    solid-memo:distractor <#q-wac-4b-d1> ,
                          <#q-wac-4b-d2> ,
                          <#q-wac-4b-d3> .

<#q-wac-4b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It lacks `acl:default`, which every rule needs"@en ;
    solid-memo:distractorNote "`accessTo` alone is enough to target the file itself."@en .

<#q-wac-4b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Its `accessTo` needs a full URL, as ACLs don't allow relative ones"@en ;
    solid-memo:distractorNote "Relative IRIs are resolved against the ACL's own URL, so `<report.ttl>` is fine."@en .

<#q-wac-4b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Bob must be put in a group, because `acl:agent` is obsolete"@en ;
    solid-memo:distractorNote "`acl:agent` is a current way to name a single WebID."@en .

<#q-wac-4c>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid's Web Access Control (WAC), Alice wants a folder to be readable by every logged-in user except Mallory. What can she do?"@en ;
    solid-memo:back "Only approximate it: grant Read to a listed group that omits Mallory"@en ;
    solid-memo:backNote "WAC only grants, so \"everyone except X\" can't be expressed, and nobody can list every logged-in user. The closest is granting to an explicit list or group that leaves X out."@en ;
    solid-memo:distractor <#q-wac-4c-d1> ,
                          <#q-wac-4c-d2> ,
                          <#q-wac-4c-d3> .

<#q-wac-4c-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Add a rule with `acl:mode acl:Deny` that names Mallory's WebID"@en ;
    solid-memo:distractorNote "WAC defines no Deny mode, and unknown modes never change access."@en .

<#q-wac-4c-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Give Mallory a rule with no modes, which overrides her other rules"@en ;
    solid-memo:distractorNote "An authorization without a mode does not apply at all."@en .

<#q-wac-4c-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Put Mallory's rule first in the ACL, since the first match wins"@en ;
    solid-memo:distractorNote "Authorizations are unordered; any matching one grants access."@en .

<#ch-wac-5>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-wac> ;
    schema:position 4 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Method-to-mode mapping

Each request of Chapter 6 needs these modes:

| Request | Modes needed |
|---|---|
| GET, HEAD | Read on the resource |
| POST into a container | Append or Write on the new resource (its rights come from the container's `acl:default`) |
| PUT that creates | Write on the new resource; Append or Write on its container |
| PUT that replaces | Write on the resource |
| DELETE | Write on the resource **and** on its container |
| Anything on the ACL | Control |

A new resource has no ACL yet, so its rights come from its container's `acl:default` rules (Step 8.6). Creating and deleting change the container's `ldp:contains` listing, hence the container rights.

⚠ On CSS 7.2 (2026), POST is checked only against the container, so Append on an inbox itself is enough there (Step 9.6). Don't rely on this elsewhere.

---

N3 Patch is checked part by part:
- a non-empty `where` needs **Read**;
- non-empty `inserts` need **Append**;
- non-empty `deletes` need **Read and Write**.

So an insert-only patch with no `where` needs only Append, which suits logs and inboxes."""@en ;
    solid-memo:checkedBy <#q-wac-5a> ,
                         <#q-wac-5b> .

<#q-wac-5a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid's Web Access Control (WAC), Bob has Write on `/shared/doc.ttl` but only Read on the `/shared/` container. What happens when he sends DELETE for the document?"@en ;
    solid-memo:back "It is refused, because DELETE also needs Write on the container"@en ;
    solid-memo:backNote "WAC requires Write on both the resource and its container to delete, because deleting changes the container's listing."@en ;
    solid-memo:distractor <#q-wac-5a-d1> ,
                          <#q-wac-5a-d2> ,
                          <#q-wac-5a-d3> .

<#q-wac-5a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It succeeds, because Write on the document is all DELETE needs"@en ;
    solid-memo:distractorNote "Deleting changes the container's listing, so the container needs Write too."@en .

<#q-wac-5a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It succeeds, because Read on the container lets him see the item"@en ;
    solid-memo:distractorNote "Read on the container doesn't allow changing its membership."@en .

<#q-wac-5a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It is refused, because DELETE always requires Control"@en ;
    solid-memo:distractorNote "Control is needed only for the ACL, not for deleting resources."@en .

<#q-wac-5b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On a Solid pod using Web Access Control (WAC), an app has only Append on a log document. Which N3 Patch can it apply?"@en ;
    solid-memo:back "One with only `inserts`, and no `where` or `deletes`"@en ;
    solid-memo:backNote "N3 Patch needs Read for `where`, Append for `inserts` and Read plus Write for `deletes`, so pure inserts work with Append alone."@en ;
    solid-memo:distractor <#q-wac-5b-d1> ,
                          <#q-wac-5b-d2> ,
                          <#q-wac-5b-d3> .

<#q-wac-5b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "One with a `where` and `inserts`, to add after a check"@en ;
    solid-memo:distractorNote "A non-empty `where` needs Read, which the app lacks."@en .

<#q-wac-5b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "One with `deletes` only, to remove its own old entries"@en ;
    solid-memo:distractorNote "Deletes need Read and Write."@en .

<#q-wac-5b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "None, because every PATCH needs Write"@en ;
    solid-memo:distractorNote "An insert-only N3 Patch needs only Append."@en .

<#ch-wac-6>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-wac> ;
    schema:position 5 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Inheritance: the effective ACL

The server uses a resource's **effective ACL**: its own ACL or, if it has none, the nearest ancestor container's ACL, up to the root, using only its `acl:default` rules.

Inheritance is **replacement, not addition**: once `/photos/cat.jpg` has its own ACL, nothing from `/photos/` or `/` applies, so it must restate the owner's rule, Control included. The spec allows servers to merge (union) instead; CSS 7.2 doesn't.

⚠ WAC doesn't require implicit owner Control. CSS 7.2 (2026) gives it only with a pod-based storage config; by default, an owner left out of an ACL gets 403 even on that ACL.

---

A container's ACL usually needs both `acl:accessTo <./>` (the container) and `acl:default <./>` (everything below it). The root ACL must exist and grant `acl:Control` to someone. CSS 7.2 writes this one for a new pod (comments removed):

```turtle
@prefix acl: <http://www.w3.org/ns/auth/acl#>.
@prefix foaf: <http://xmlns.com/foaf/0.1/>.

<#public> a acl:Authorization;
    acl:agentClass foaf:Agent;
    acl:accessTo <./>;
    acl:mode acl:Read.

<#owner> a acl:Authorization;
    acl:agent <http://localhost:3000/alice/profile/card#me>;
    acl:accessTo <./>;
    acl:default <./>;
    acl:mode acl:Read, acl:Write, acl:Control.
```

---

The public rule has no `acl:default`: anyone can read the root listing, but nothing below inherits it; the profile has its own public ACL. On CSS 7.2 (recorded in 2026), Alice made her note `notes/open.ttl` public by PUTting this ACL at its `rel="acl"` URL:

```turtle
@prefix acl: <http://www.w3.org/ns/auth/acl#>.
@prefix foaf: <http://xmlns.com/foaf/0.1/>.

<#owner> a acl:Authorization;
    acl:agent <http://localhost:3000/alice/profile/card#me>;
    acl:accessTo <open.ttl>;
    acl:mode acl:Read, acl:Write, acl:Control.

<#public> a acl:Authorization;
    acl:agentClass foaf:Agent;
    acl:accessTo <open.ttl>;
    acl:mode acl:Read.
```

Anonymous HEADs on the note:

```text
before the ACL                        401 Unauthorized
PUT the ACL (as Alice)                201 Created
after the ACL                         200 OK, WAC-Allow: user="read",public="read"
PUT it again, "<#public>" untyped     205 Reset Content
after the broken ACL                  401 Unauthorized
```

Untyped, the public rule silently did nothing."""@en ;
    solid-memo:checkedBy <#q-wac-6a> ,
                         <#q-wac-6b> .

<#q-wac-6a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid's Web Access Control (WAC), the ACL of the `/docs/` container gives Bob Read with `acl:default <./>`. Alice then creates an ACL for `/docs/plan.ttl` that only grants herself full access. Can Bob still read `plan.ttl`?"@en ;
    solid-memo:back "No, because the file's own ACL replaces the inherited rules"@en ;
    solid-memo:backNote "The effective ACL is the nearest one that exists; once `plan.ttl` has its own ACL, none of the ancestor rules apply."@en ;
    solid-memo:distractor <#q-wac-6a-d1> ,
                          <#q-wac-6a-d2> ,
                          <#q-wac-6a-d3> .

<#q-wac-6a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Yes, because the container's rules are added to the file's rules"@en ;
    solid-memo:distractorNote "In WAC's standard algorithm, inheritance is replacement; the nearest existing ACL is the only one used."@en .

<#q-wac-6a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Yes, because `acl:default` rules always take priority"@en ;
    solid-memo:distractorNote "Default rules apply only when no nearer ACL exists."@en .

<#q-wac-6a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "No, because `acl:default` never applies to files, only containers"@en ;
    solid-memo:distractorNote "Default rules are inherited by all descendants without their own ACL, files included."@en .

<#q-wac-6b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid's Web Access Control (WAC), a container's ACL has one rule giving Bob `acl:Read` with `acl:default <./>` and no `acl:accessTo`. What can Bob read?"@en ;
    solid-memo:back "The resources inside the container, but not its own listing"@en ;
    solid-memo:backNote "`acl:accessTo <./>` covers the container itself and `acl:default <./>` covers its descendants, which is why container ACLs normally use both."@en ;
    solid-memo:distractor <#q-wac-6b-d1> ,
                          <#q-wac-6b-d2> ,
                          <#q-wac-6b-d3> .

<#q-wac-6b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The container listing and everything inside it"@en ;
    solid-memo:distractorNote "`default` covers descendants; the container itself needs `accessTo`."@en .

<#q-wac-6b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only the container listing, not the resources inside it"@en ;
    solid-memo:distractorNote "That is the reverse of what `default` does."@en .

<#q-wac-6b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing, because `default` only works on the root container"@en ;
    solid-memo:distractorNote "`acl:default` can appear in any container's ACL."@en .

<#ch-wac-7>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-wac> ;
    schema:position 6 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## What the client sees: status codes and WAC-Allow

When access is refused, the server answers:
- **401**: no valid credentials, and the resource needs some.
- **403**: you are known, but not allowed.
- **404**: "not found". The Solid Protocol lets a server send it instead of 401 "for security reasons", and HTTP lets it replace 403 to hide that a forbidden resource exists.

After a 403 or 404 a client may retry with other credentials. To grey out an Edit button, an app needs its permissions *before* trying, but reading the ACL needs Control. Instead, WAC servers MUST send a `WAC-Allow` header on GET and HEAD: `user` lists the requester's modes and `public` everyone's; clients ignore unknown groups or modes. It is a UI hint; the server still checks every request. ACP defines no such header; without it, an app offers the action and handles a 401 or 403.

---

On CSS 7.2 (recorded in 2026), a private note answered an anonymous HEAD, then Alice's:

```http
HTTP/1.1 401 Unauthorized
WWW-Authenticate: Bearer scope="openid webid"

HTTP/1.1 200 OK
WAC-Allow: user="append control read write"
```

No `public=` entry: the note isn't public. CSS 7.2 and NSS 6.0.0 send no `WAC-Allow` on errors (CSS 7.2 none on 201 or 205 either), so a refusal carries no hint."""@en ;
    solid-memo:checkedBy <#q-wac-7a> ,
                         <#q-wac-7b> .

<#q-wac-7a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A logged-in user of a Solid app requests a private file in someone else's pod and gets 404. What can the app conclude?"@en ;
    solid-memo:back "The file may exist; the server may be hiding it from this user"@en ;
    solid-memo:backNote "A server may answer 404 instead of 401 (Solid Protocol) or 403 (HTTP) so it does not reveal that a protected resource exists."@en ;
    solid-memo:distractor <#q-wac-7a-d1> ,
                          <#q-wac-7a-d2> ,
                          <#q-wac-7a-d3> .

<#q-wac-7a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The file definitely doesn't exist, because 404 means not found"@en ;
    solid-memo:distractorNote "Servers may use 404 instead of 401 or 403 to hide existence."@en .

<#q-wac-7a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The user's token has expired and must be refreshed"@en ;
    solid-memo:distractorNote "404 can't tell you the token expired; even an expired token's 401 may be hidden as 404."@en .

<#q-wac-7a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The user lacks Read, so the server was required to answer 404"@en ;
    solid-memo:distractorNote "Lacking Read gives 403, or 404 only if the server chooses to hide existence."@en .

<#q-wac-7b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "How should a Solid app decide whether to show an \"Edit\" button for a document in a pod?"@en ;
    solid-memo:back "Read the `user` modes in the `WAC-Allow` response header"@en ;
    solid-memo:backNote "`WAC-Allow` tells the client its own and the public's modes on GET and HEAD. ACP doesn't define it, so when it is missing, send the real request and handle 401 or 403."@en ;
    solid-memo:distractor <#q-wac-7b-d1> ,
                          <#q-wac-7b-d2> ,
                          <#q-wac-7b-d3> .

<#q-wac-7b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Fetch and parse the document's ACL to look for a Write rule"@en ;
    solid-memo:distractorNote "Reading the ACL needs Control, which most users won't have."@en .

<#q-wac-7b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Send a test PUT and see whether it fails"@en ;
    solid-memo:distractorNote "A test write could change data; without the header, try the user's real edit and handle 401 or 403."@en .

<#q-wac-7b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Check the user's profile for a list of documents they can edit"@en ;
    solid-memo:distractorNote "Profiles don't list permissions; the pod does."@en .

<#ch-wac-8>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-wac> ;
    schema:position 7 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## CORS: why pods let every app in

An **origin** is the scheme, host and port of a URL: `https://app.example` and `https://alice.example` are different origins. By default, a browser's *same-origin policy* stops a page's script from reading responses from another origin. A server can relax this with CORS headers: the response's `Access-Control-Allow-Origin` names the origin that may read it.

Solid apps are hosted on one origin and read pods on many others, so Solid servers open CORS completely: they repeat the request's `Origin` in `Access-Control-Allow-Origin`. They don't send `*` ("anyone"), because browsers reject `*` for requests sent with credentials. Servers must also list headers apps need, such as `Link` and `WAC-Allow`, in `Access-Control-Expose-Headers`, or browser apps can't read them.

The Protocol says blocking "MUST NOT happen via CORS". Who may do what is decided by access control and answered with 401, 403 or 404.

---

On CSS 7.2 (recorded in 2026, other headers left out), an anonymous HEAD on a public profile got:

```http
HEAD /alice/profile/card HTTP/1.1
Origin: https://app.example

HTTP/1.1 200 OK
Access-Control-Allow-Origin: https://app.example
Access-Control-Allow-Credentials: true
Access-Control-Expose-Headers: Accept-Patch,Accept-Post,Accept-Put,Allow,Content-Range,ETag,Last-Modified,Link,Location,Updates-Via,WAC-Allow,Www-Authenticate
Vary: Accept,Authorization,Origin
```

Without an `Origin` header, CSS 7.2 answered `Access-Control-Allow-Origin: *` instead; that is harmless, because no browser sent the request."""@en ;
    solid-memo:checkedBy <#q-wac-8a> .

<#q-wac-8a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Why does a Solid pod server repeat any request's `Origin` in its `Access-Control-Allow-Origin` response header?"@en ;
    solid-memo:back "Access is enforced by authorization, so CORS must not block apps"@en ;
    solid-memo:backNote "Solid apps are hosted on many origins, so servers open CORS fully and rely on 401, 403 or 404 from access control instead."@en ;
    solid-memo:distractor <#q-wac-8a-d1> ,
                          <#q-wac-8a-d2> ,
                          <#q-wac-8a-d3> .

<#q-wac-8a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Repeating the Origin proves which app is making the request"@en ;
    solid-memo:distractorNote "Origin is not client identification; non-browser clients can send any value."@en .

<#q-wac-8a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It is a temporary fallback until servers support `*`"@en ;
    solid-memo:distractorNote "Browsers reject `*` for requests with credentials, so repeating the origin is the lasting answer."@en .

<#q-wac-8a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "CORS checks the user's WebID against the ACL"@en ;
    solid-memo:distractorNote "CORS knows nothing about WebIDs or ACLs."@en .

<#q-wac-r01>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid's Web Access Control (WAC), Bob can read every file in `/team/` through an inherited `acl:default` rule. Alice adds an ACL to one file that grants only Bob Write. What can Bob now do with that file?"@en ;
    solid-memo:back "Write it but not read it, because the new ACL replaces the inherited Read"@en ;
    solid-memo:backNote "The file's own ACL is now its effective ACL, and it grants only Write; Write covers Append but not Read."@en ;
    solid-memo:distractor <#q-wac-r01-d1> ,
                          <#q-wac-r01-d2> ,
                          <#q-wac-r01-d3> .

<#q-wac-r01-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Read and write it, because new rules are added to inherited ones"@en ;
    solid-memo:distractorNote "In WAC's standard algorithm, inheritance is replacement, not union."@en .

<#q-wac-r01-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only read it, because inherited rules beat local ones"@en ;
    solid-memo:distractorNote "Once the file has its own ACL, inherited rules no longer apply."@en .

<#q-wac-r01-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Write and read it, because Write implies Read"@en ;
    solid-memo:distractorNote "Write does not imply Read; it only implies Append."@en .

<#q-wac-r02>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A GET on a shared notes document in a Solid pod returns `WAC-Allow: user=\"read append\"`. Which action should the app's UI offer?"@en ;
    solid-memo:back "Adding a note with an insert-only N3 Patch"@en ;
    solid-memo:backNote "With Read and Append the user can add triples (even with a `where`), but deleting, replacing or changing the ACL needs Write or Control."@en ;
    solid-memo:distractor <#q-wac-r02-d1> ,
                          <#q-wac-r02-d2> ,
                          <#q-wac-r02-d3> .

<#q-wac-r02-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Editing an existing note with an N3 Patch that deletes and inserts"@en ;
    solid-memo:distractorNote "Deletes need Write, which the user lacks."@en .

<#q-wac-r02-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Replacing the document with PUT"@en ;
    solid-memo:distractorNote "Replacing a resource needs Write."@en .

<#q-wac-r02-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Changing who can see the document"@en ;
    solid-memo:distractorNote "Editing the ACL needs Control."@en .

<#q-wac-r03>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid's Web Access Control (WAC), the ACL of the `/notes/` container has one rule giving Bob `acl:Write` with `acl:default <./>` and no `acl:accessTo`. No file inside has its own ACL. Can Bob delete `/notes/a.ttl`?"@en ;
    solid-memo:back "No, because he lacks Write on the `/notes/` container itself"@en ;
    solid-memo:backNote "The `default` rule gives Bob Write on `a.ttl`, but deleting changes the listing of `/notes/`, and Write on the container would need `acl:accessTo <./>`."@en ;
    solid-memo:distractor <#q-wac-r03-d1> ,
                          <#q-wac-r03-d2> ,
                          <#q-wac-r03-d3> .

<#q-wac-r03-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Yes, because the inherited Write on `a.ttl` is all DELETE needs"@en ;
    solid-memo:distractorNote "DELETE also needs Write on the container, whose listing changes."@en .

<#q-wac-r03-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Yes, because `acl:default` also covers the container itself"@en ;
    solid-memo:distractorNote "`default` covers only descendants; the container needs `accessTo`."@en .

<#q-wac-r03-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "No, because DELETE needs Control on the file"@en ;
    solid-memo:distractorNote "Control is only for the ACL; DELETE needs Write."@en .

<#q-wac-r04>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Bob's browser app sends a GET for Alice's note on a Solid pod that uses Web Access Control (WAC), and gets 403 with no `WAC-Allow` header. What does the 403 tell the app about Bob, and should the app send him through login again or tell him he lacks access?"@en ;
    solid-memo:back "Bob is logged in but not allowed; tell him he lacks access to the note"@en ;
    solid-memo:backNote "403 means authenticated but not authorized: the server knew who he was, so logging in again as Bob gets the same answer. Missing or unusable credentials give 401 (or a hiding 404). On CSS 7.2 (2026), errors carry no `WAC-Allow` header."@en ;
    solid-memo:distractor <#q-wac-r04-d1> ,
                          <#q-wac-r04-d2> ,
                          <#q-wac-r04-d3> ,
                          <#q-wac-r04-d4> ,
                          <#q-wac-r04-d5> .

<#q-wac-r04-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "The browser's CORS policy blocked it; retry from another origin"@en ;
    solid-memo:distractorNote "Solid servers never block through CORS, and a CORS block would hide the status from the app altogether."@en .

<#q-wac-r04-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Bob's token has expired; send him through login again"@en ;
    solid-memo:distractorNote "A missing or unusable token gives 401 (or a hiding 404); 403 means the server knew who he was."@en .

<#q-wac-r04-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "GET the note's URL plus `.acl` to find which rule is missing"@en ;
    solid-memo:distractorNote "That builds the ACL URL by string, and reading an ACL needs Control, which a reader rarely has."@en .

<#q-wac-r04-d4>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Bob is logged in but not allowed; send him through login again"@en ;
    solid-memo:distractorNote "The server already knew him; a new login as Bob brings the same identity and the same 403."@en .

<#q-wac-r04-d5>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Bob's token has expired; tell him he lacks access to the note"@en ;
    solid-memo:distractorNote "A missing or unusable token gives 401 (or a hiding 404); 403 means the server knew who he was."@en .

<#q-wac-r05>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid's Web Access Control (WAC), Alice shares `/notes/a.ttl` with Bob by giving the file its own ACL. Besides Bob's Read rule, what must that new ACL contain?"@en ;
    solid-memo:back "A rule restating Alice's own access, Control included"@en ;
    solid-memo:backNote "Once a resource has its own ACL, no inherited rule applies, so the owner must restate her own rule, Control included, or lose access."@en ;
    solid-memo:distractor <#q-wac-r05-d1> ,
                          <#q-wac-r05-d2> ,
                          <#q-wac-r05-d3> .

<#q-wac-r05-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing else, because her `acl:default` rule in the root ACL still applies"@en ;
    solid-memo:distractorNote "A resource's own ACL replaces inheritance entirely."@en .

<#q-wac-r05-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A copy of the root's public rule, so the file stays readable"@en ;
    solid-memo:distractorNote "Sharing with Bob doesn't call for public access, and Alice would still be locked out."@en .

<#q-wac-r05-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An `acl:default` rule for Bob, so his grant reaches the file"@en ;
    solid-memo:distractorNote "`acl:default` is for a container's descendants; a file needs `acl:accessTo`."@en .

# Chapter 9: Sharing in practice, ACP and app permissions.
<#ch-sharing>
    a solid-memo:Chapter ,
      schema:Syllabus ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <> ;
    schema:position 8 ;
    dcterms:title "Sharing in practice, ACP and app permissions"@en ;
    dcterms:description "Read ACP policies, share resources with people and groups on WAC and ACP pods, and tell them about it through their inbox. Then work across other people's pods and see where app permissions still fall short."@en ;
    solid-memo:reviewQuestion <#q-sharing-r01> ,
                              <#q-sharing-r02> ,
                              <#q-sharing-r03> ,
                              <#q-sharing-r04> ,
                              <#q-sharing-r05> ,
                              <#q-sharing-r06> ,
                              <#q-sharing-r07> .

<#ch-sharing-1>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-sharing> ;
    schema:position 0 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## ACP's building blocks

ACP (Access Control Policy) builds rules from four layers:

**Access Control Resource (ACR)** → **Access Control** → **Policy** → **Matcher**

The ACR is linked from the resource with the same `rel="acl"` as WAC. Its `acp:accessControl` applies to the resource itself; its `acp:memberAccessControl` applies to all descendants. An access control lists the policies it applies with `acp:apply`. A **policy** lists modes to `acp:allow` or `acp:deny`, reusing `acl:Read` and the other WAC modes, and names the matchers that must match. A **matcher** tests the request: `acp:agent` (the WebID), `acp:client` (the app's client ID) or `acp:issuer` (the identity provider).

---

`acp:agent` can also take the special values `acp:PublicAgent` (anyone) and `acp:AuthenticatedAgent` (anyone logged in), the ACP versions of WAC's `foaf:Agent` and `acl:AuthenticatedAgent`.

```turtle
@prefix acl: <http://www.w3.org/ns/auth/acl#>.
@prefix acp: <http://www.w3.org/ns/solid/acp#>.

<#noWritesFromAppY> a acp:Policy;
    acp:deny acl:Write;
    # anyOf: the policy applies if any listed matcher matches (Step 9.2)
    acp:anyOf [ a acp:Matcher; acp:client <https://appy.example/id> ].
```

---

To tell which system you face, follow `rel="acl"` and check the response: an ACR carries `Link: <http://www.w3.org/ns/solid/acp#AccessControlResource>; rel="type"`.

⚠ As of October 2026, ACP's latest published version is 0.9.0 (May 2022), an Editor's Draft of the Solid Community Group; its editor's draft was last updated in September 2022. Inrupt's ESS uses it; on the Community Solid Server (CSS) it is an option."""@en ;
    solid-memo:checkedBy <#q-sharing-1a> ,
                         <#q-sharing-1b> .

<#q-sharing-1a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid, your app followed a resource's `rel=\"acl\"` link and fetched the rule document. How can it tell that the server uses ACP rather than WAC?"@en ;
    solid-memo:back "A `rel=\"type\"` link to `acp:AccessControlResource`"@en ;
    solid-memo:backNote "An ACR response must carry a type link to `acp:AccessControlResource`; that is the reliable way to detect ACP."@en ;
    solid-memo:distractor <#q-sharing-1a-d1> ,
                          <#q-sharing-1a-d2> ,
                          <#q-sharing-1a-d3> .

<#q-sharing-1a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The document's URL ends in `.acr` instead of `.acl`"@en ;
    solid-memo:distractorNote "File names are server conventions and must not be relied on."@en .

<#q-sharing-1a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server answers with `rel=\"acp\"` instead of `rel=\"acl\"`"@en ;
    solid-memo:distractorNote "ACP uses the same `rel=\"acl\"` link as WAC."@en .

<#q-sharing-1a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The response is JSON-LD rather than Turtle"@en ;
    solid-memo:distractorNote "Both kinds of rule document are RDF, in any RDF syntax the server offers."@en .

<#q-sharing-1b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In a Solid ACP policy, which matcher makes a resource readable by anyone, logged in or not?"@en ;
    solid-memo:back "One with `acp:agent acp:PublicAgent`"@en ;
    solid-memo:backNote "`acp:PublicAgent` is ACP's \"everyone\", like WAC's `foaf:Agent`; `acp:AuthenticatedAgent` means anyone logged in."@en ;
    solid-memo:distractor <#q-sharing-1b-d1> ,
                          <#q-sharing-1b-d2> ,
                          <#q-sharing-1b-d3> .

<#q-sharing-1b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "One with `acp:agent acp:AuthenticatedAgent`"@en ;
    solid-memo:distractorNote "That matches only requests with a logged-in agent."@en .

<#q-sharing-1b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "One with `acl:agentClass foaf:Agent`"@en ;
    solid-memo:distractorNote "That is WAC's way; ACP matchers use `acp:agent acp:PublicAgent`."@en .

<#q-sharing-1b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "One with no attributes at all"@en ;
    solid-memo:distractorNote "An empty matcher never matches anything."@en .

<#ch-sharing-2>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-sharing> ;
    schema:position 1 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## How ACP decides

A policy names its matchers in three lists:
- `acp:allOf`: every matcher must match;
- `acp:anyOf`: at least one must match;
- `acp:noneOf`: none may match.

A policy is *satisfied* when all three conditions hold. It must also have at least one `allOf` or `anyOf` matcher, so **a policy with only `noneOf` is never satisfied**. Inside one matcher, several values of the same attribute are alternatives (any one may match), while different attributes must all match. An empty matcher never matches.

A mode is granted only if some satisfied policy allows it and **no satisfied policy denies it**: deny overrides allow. WAC has no deny at all.

Which policies count? The resource's own `acp:accessControl` policies plus the `acp:memberAccessControl` policies of **every ancestor**. Unlike WAC, where the nearest ACL replaces the others, ACP's member policies **accumulate**: a resource's own ACR doesn't switch them off."""@en ;
    solid-memo:checkedBy <#q-sharing-2a> ,
                         <#q-sharing-2b> ,
                         <#q-sharing-2c> .

<#q-sharing-2a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "On a Solid ACP server, a satisfied policy allows Read and Write for Bob, and another satisfied policy denies Write for the app he uses. What can Bob do through that app?"@en ;
    solid-memo:back "Read only, because deny overrides allow"@en ;
    solid-memo:backNote "An ACP mode is granted only if a satisfied policy allows it and no satisfied policy denies it."@en ;
    solid-memo:distractor <#q-sharing-2a-d1> ,
                          <#q-sharing-2a-d2> ,
                          <#q-sharing-2a-d3> .

<#q-sharing-2a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Read and Write, because allows are checked first"@en ;
    solid-memo:distractorNote "In ACP a satisfied deny always wins over an allow."@en .

<#q-sharing-2a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing, because a conflict denies every mode"@en ;
    solid-memo:distractorNote "Only the denied mode is removed; Read is still allowed."@en .

<#q-sharing-2a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Read and Write, because agent rules beat client rules"@en ;
    solid-memo:distractorNote "ACP gives no priority to agent matchers over client matchers."@en .

<#q-sharing-2b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid ACP policy allows Read with `acp:allOf` naming two matchers: one for Bob's WebID and one for the client ID of app X. When can Bob read?"@en ;
    solid-memo:back "Only when he uses app X"@en ;
    solid-memo:backNote "`allOf` requires every listed matcher to match; with `anyOf`, either Bob or app X alone would have been enough."@en ;
    solid-memo:distractor <#q-sharing-2b-d1> ,
                          <#q-sharing-2b-d2> ,
                          <#q-sharing-2b-d3> .

<#q-sharing-2b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Whenever he is logged in, with any app"@en ;
    solid-memo:distractorNote "With `allOf`, the client matcher must match too."@en .

<#q-sharing-2b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Whenever anyone uses app X"@en ;
    solid-memo:distractorNote "With `allOf`, the agent matcher must match too."@en .

<#q-sharing-2b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Never, since a policy can't test agent and client"@en ;
    solid-memo:distractorNote "A policy can combine any matchers."@en .

<#q-sharing-2c>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid's ACP, a container's ACR applies a policy to its members with `acp:memberAccessControl`. A file inside has its own ACR with its own policies. Which policies apply to the file?"@en ;
    solid-memo:back "Both the file's own and the container's member policies"@en ;
    solid-memo:backNote "In ACP the effective policies are the resource's own plus every ancestor's member access controls."@en ;
    solid-memo:distractor <#q-sharing-2c-d1> ,
                          <#q-sharing-2c-d2> ,
                          <#q-sharing-2c-d3> .

<#q-sharing-2c-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only the file's own, since the nearest ACR replaces the others"@en ;
    solid-memo:distractorNote "That is WAC's rule; ACP member policies accumulate."@en .

<#q-sharing-2c-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only the container's, since members can't have their own ACR"@en ;
    solid-memo:distractorNote "Every resource can have an ACR with its own access controls."@en .

<#q-sharing-2c-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Neither, until the file's ACR copies the container's policies"@en ;
    solid-memo:distractorNote "Ancestor member policies apply without being copied."@en .

<#ch-sharing-3>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-sharing> ;
    schema:position 2 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Sharing a resource with WAC

Alice wants Bob to read one note. On a WAC pod that takes four steps:

1. **Find the ACL.** HEAD the note and follow its `rel="acl"` link (Step 8.2). Never build the URL yourself.
2. **Check for Control.** Only Control lets you edit an ACL, so look for `control` in `WAC-Allow: user="…"` (Step 8.7).
3. **Read the ACL.** A 404 means the note has no ACL of its own and inherits one (Step 8.6).
4. **Write the ACL.** A new ACL replaces inheritance, so first restate the inherited rules you still want, above all the owner's Read, Write and Control. Then add Bob's rule and PUT the whole document as `text/turtle`. If the ACL already exists, an N3 Patch also works.

```turtle
@prefix acl: <http://www.w3.org/ns/auth/acl#>.
<#owner> a acl:Authorization;
  acl:agent <http://localhost:3000/alice/profile/card#me>;
  acl:accessTo <http://localhost:3000/alice/notes/first.ttl>;
  acl:mode acl:Read, acl:Write, acl:Control.
<#bob> a acl:Authorization;
  acl:agent <http://localhost:3000/bob/profile/card#me>;
  acl:accessTo <http://localhost:3000/alice/notes/first.ttl>;
  acl:mode acl:Read.
```

---

This chapter's recordings ran on a local CSS 7.2 (October 2026) at `localhost:3000`. Sharing went like this:

```text
HEAD  /alice/notes/first.ttl      as Alice → 200
      wac-allow: user="append control read write"
      link: <http://localhost:3000/alice/notes/first.ttl.acl>; rel="acl"
GET   /alice/notes/first.ttl      as Bob   → 403
PUT   /alice/notes/first.ttl.acl  as Alice → 201
GET   /alice/notes/first.ttl      as Bob   → 200, wac-allow: user="read"
PATCH /alice/notes/first.ttl      as Bob   → 403 (Read gives no Append)
```

**Pitfall:** leave out `#owner` and Alice may lock herself out of the note and its ACL. The storage owner "implicitly has control" (Step 5.3), and servers may use that to rescue owners, but you can't count on it. ⚠ CSS 7.2 doesn't: Alice loses the note and its ACL, and even a DELETE of the ACL gets 403."""@en ;
    solid-memo:checkedBy <#q-sharing-3a> ,
                         <#q-sharing-3b> .

<#q-sharing-3a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On a Solid WAC pod, Alice's note inherits its rules from the pod root. Her app PUTs a new ACL for the note that contains only a rule giving Bob Read. What is the result?"@en ;
    solid-memo:back "Bob can read the note, but Alice's own rules no longer apply to it"@en ;
    solid-memo:backNote "The note's new ACL is now its effective ACL, so the root's owner rule no longer applies. Always restate the owner's Read, Write and Control."@en ;
    solid-memo:distractor <#q-sharing-3a-d1> ,
                          <#q-sharing-3a-d2> ,
                          <#q-sharing-3a-d3> .

<#q-sharing-3a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Bob can read it, and Alice keeps full access through the root ACL"@en ;
    solid-memo:distractorNote "A resource's own ACL replaces all inherited rules."@en .

<#q-sharing-3a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing changes until Bob's rule also has `acl:default`"@en ;
    solid-memo:distractorNote "`acl:accessTo` covers the note; `acl:default` is for a container's descendants."@en .

<#q-sharing-3a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Bob can read it, and Alice keeps access because she created it"@en ;
    solid-memo:distractorNote "WAC has no creator rule; only the effective ACL counts."@en .

<#q-sharing-3b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Before offering a \"Share\" button, how can an app check that the user may change a document's ACL on a Solid WAC pod?"@en ;
    solid-memo:back "Look for `control` in the `user` part of its `WAC-Allow` header"@en ;
    solid-memo:backNote "`WAC-Allow` lists the requester's modes on GET and HEAD, and only `control` allows editing the ACL."@en ;
    solid-memo:distractor <#q-sharing-3b-d1> ,
                          <#q-sharing-3b-d2> ,
                          <#q-sharing-3b-d3> .

<#q-sharing-3b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Look for `write` in its `WAC-Allow` header, since Write covers the ACL"@en ;
    solid-memo:distractorNote "Write applies to the document; editing its ACL needs Control."@en .

<#q-sharing-3b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "GET the pod root's ACL and search it for the user's WebID"@en ;
    solid-memo:distractorNote "The effective ACL may be elsewhere, and reading an ACL needs Control."@en .

<#q-sharing-3b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Check whether the document's triples mention the user's WebID"@en ;
    solid-memo:distractorNote "Data triples grant nothing; access comes from the ACL."@en .

<#ch-sharing-4>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-sharing> ;
    schema:position 3 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Sharing a resource with ACP

On an ACP pod the same `rel="acl"` link leads to an Access Control Resource, which you recognise by its `acp:AccessControlResource` type link (Step 9.1). To share, add an access control with a policy for the friend, and list it in the ACR under `acp:accessControl` (this resource only) or `acp:memberAccessControl` (everything inside a container). The edited ACR of a note can look like this (on CSS 7.2 a new note has no ACR until the first share creates one; the owner's access comes from the root's member policy):

```turtle
@prefix acl: <http://www.w3.org/ns/auth/acl#>.
@prefix acp: <http://www.w3.org/ns/solid/acp#>.

<> a acp:AccessControlResource;
  acp:resource <https://alice.example/notes/note.ttl>;
  acp:accessControl <#ownerControl>, <#bobReads>.   # added: <#bobReads>

# <#ownerControl> ...: if the ACR already had it, keep it unchanged

<#bobReads> a acp:AccessControl;
  acp:apply [ a acp:Policy;
    acp:allow acl:Read;
    acp:anyOf [ a acp:Matcher;
      acp:agent <https://bob.example/profile/card#me> ] ].
```

---

How this differs from WAC:
- **You only add.** Ancestors' member policies keep applying (Step 9.2), so you need not restate the owner's access. If you rewrite the whole ACR, keep the access controls already in it.
- **Control means control of the ACR.** In CSS 7.2's ACP template (2026), the owner's policy allows `acl:Control`, and that is what lets the owner change the ACR. The ACP spec does not say which HTTP requests edit an ACR.
- **No `WAC-Allow` to check first.** ACP does not define the header (Step 8.7). Try the change and handle a 403.

Step 9.5 shows an API meant to write both kinds of rule."""@en ;
    solid-memo:checkedBy <#q-sharing-4a> ,
                         <#q-sharing-4b> .

<#q-sharing-4a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "You share one file with Bob on a Solid ACP pod. Which step from the WAC sharing workflow can you skip?"@en ;
    solid-memo:back "Restating the owner's inherited access"@en ;
    solid-memo:backNote "In ACP, ancestors' member policies keep applying, so a new policy only adds access. In WAC, a new ACL replaces everything inherited."@en ;
    solid-memo:distractor <#q-sharing-4a-d1> ,
                          <#q-sharing-4a-d2> ,
                          <#q-sharing-4a-d3> .

<#q-sharing-4a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Finding the rule document through `rel=\"acl\"`"@en ;
    solid-memo:distractorNote "ACP uses the same link to find the ACR."@en .

<#q-sharing-4a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Naming Bob's WebID in the new rule"@en ;
    solid-memo:distractorNote "The matcher's `acp:agent` is what identifies Bob."@en .

<#q-sharing-4a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Having control over the rule document"@en ;
    solid-memo:distractorNote "You still need control to change the ACR."@en .

<#q-sharing-4b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On a Solid ACP pod, where does your app attach Bob's new access control so that it covers one file and nothing else?"@en ;
    solid-memo:back "In the file's ACR, under `acp:accessControl`"@en ;
    solid-memo:backNote "`acp:accessControl` applies to the resource itself, and `acp:memberAccessControl` to a container's descendants."@en ;
    solid-memo:distractor <#q-sharing-4b-d1> ,
                          <#q-sharing-4b-d2> ,
                          <#q-sharing-4b-d3> .

<#q-sharing-4b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In the file's ACR, under `acp:memberAccessControl`"@en ;
    solid-memo:distractorNote "That applies to members, and only containers have them."@en .

<#q-sharing-4b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In the file itself, as an `acp:agent` triple"@en ;
    solid-memo:distractorNote "Rules live in the ACR, not in the data."@en .

<#q-sharing-4b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In Bob's profile, as an `acp:apply` triple"@en ;
    solid-memo:distractorNote "Only the pod's own ACRs grant access to its resources."@en .

<#ch-sharing-5>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-sharing> ;
    schema:position 4 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## One API for both: universal access

Clients must cope with both WAC and ACP, and hand-writing both kinds of rule is error-prone. Inrupt's `@inrupt/solid-client` (Step 12.10) has a **universal access API** that is meant to work on both. Inrupt recommends it where it fits:

```js
import { universalAccess } from "@inrupt/solid-client";

// fetch: the logged-in fetch from your auth library
await universalAccess.setAgentAccess(noteUrl, bobWebId,
  { read: true, append: false, write: false }, { fetch });
const bobs = await universalAccess.getAgentAccess(noteUrl, bobWebId, { fetch });
```

`setPublicAccess(url, access, { fetch })` does the same for everyone. Access is described by an object `{ read, append, write }`. A `null` result means the access could not be read, or cannot be expressed this way.

---

⚠ In a test in October 2026, `setAgentAccess` worked on CSS 7.2 with WAC. On CSS 7.2 with ACP, for a resource with no ACR yet, it returned `null` and shared nothing. Always check the result.

Its limits:
- It reports only access **set directly** on that resource for that agent (or the public). Inherited or group access is not shown, so Bob may be able to do more than `getAgentAccess` says.
- It acts on one resource, not on its children.
- Anything beyond the shared model, such as ACP deny rules or client matchers, needs the WAC- or ACP-specific APIs."""@en ;
    solid-memo:checkedBy <#q-sharing-5a> ,
                         <#q-sharing-5b> .

<#q-sharing-5a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Inrupt's universal access API (`getAgentAccess`) reports `read: false` for Bob on a file in a Solid pod, yet Bob can read it. What is the likely reason?"@en ;
    solid-memo:back "His Read comes from a container's inherited rules"@en ;
    solid-memo:backNote "The universal access API reports only access set directly on that resource, not inherited or indirect access."@en ;
    solid-memo:distractor <#q-sharing-5a-d1> ,
                          <#q-sharing-5a-d2> ,
                          <#q-sharing-5a-d3> .

<#q-sharing-5a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The API reads only ACP rules, and this pod uses WAC"@en ;
    solid-memo:distractorNote "It is meant to read both WAC and ACP rules, and it does read WAC rules."@en .

<#q-sharing-5a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The pod remembers an earlier grant that was removed"@en ;
    solid-memo:distractorNote "The pod checks the current rules on every request."@en .

<#q-sharing-5a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Bob reads through an app that the API ignores"@en ;
    solid-memo:distractorNote "The API reports agent access; the app does not change that."@en .

<#q-sharing-5b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On an ACP pod, Alice wants to stop one app from writing to her notes, whoever is using it. Inrupt's universal access API can't express this. Which two ACP features does the rule need?"@en ;
    solid-memo:back "Deny rules and client matchers"@en ;
    solid-memo:backNote "Stopping Write takes an ACP deny rule, and singling out an app takes a client matcher. The universal model only allows read, append and write for agents and the public, so this rule needs the ACP-specific API (as does any other ACP feature beyond the shared model)."@en ;
    solid-memo:distractor <#q-sharing-5b-d1> ,
                          <#q-sharing-5b-d2> ,
                          <#q-sharing-5b-d3> ,
                          <#q-sharing-5b-d4> ,
                          <#q-sharing-5b-d5> ,
                          <#q-sharing-5b-d6> .

<#q-sharing-5b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "Letting a friend read one document"@en ;
    solid-memo:distractorNote "That is exactly what `setAgentAccess` does."@en .

<#q-sharing-5b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "Making a single document public"@en ;
    solid-memo:distractorNote "`setPublicAccess` does this."@en .

<#q-sharing-5b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "Checking what Bob was granted on a file"@en ;
    solid-memo:distractorNote "`getAgentAccess` does this, for direct grants."@en .

<#q-sharing-5b-d4>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Allow rules and client matchers"@en ;
    solid-memo:distractorNote "A client matcher picks out the app, but an allow rule can only grant access; stopping Write needs a deny rule."@en .

<#q-sharing-5b-d5>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Deny rules and agent matchers"@en ;
    solid-memo:distractorNote "An agent matcher tests the user's WebID, not the app, so it can't stop one app whoever is using it."@en .

<#q-sharing-5b-d6>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Deny rules and issuer matchers"@en ;
    solid-memo:distractorNote "An issuer matcher tests the identity provider that issued the login, not the app; a client matcher picks out the app."@en .

<#ch-sharing-6>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-sharing> ;
    schema:position 5 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Telling the recipient: a message to their inbox

Bob doesn't know about the share. Tell him through his inbox (Step 5.11): read `ldp:inbox` from his profile and POST a message. In Activity Streams 2.0, an `Announce` calls the `target`'s attention to the `object`; `Offer` and `Invite` suit proposals.

```json
{"@context": "https://www.w3.org/ns/activitystreams",
 "type": "Announce",
 "actor": "http://localhost:3000/alice/profile/card#me",
 "object": "http://localhost:3000/alice/notes/first.ttl",
 "target": "http://localhost:3000/bob/profile/card#me",
 "summary": "alice shared a note with you"}
```

---

**Bob's side: creating an inbox.** A CSS 7 profile has no `ldp:inbox`, and only Bob's own app can add one: PUT the container, PUT its ACL, then add `ldp:inbox` to his profile with an insert-only N3 Patch. A typical inbox ACL:

```turtle
@prefix acl: <http://www.w3.org/ns/auth/acl#>.
@prefix foaf: <http://xmlns.com/foaf/0.1/>.
<#owner> a acl:Authorization;
  acl:agent <http://localhost:3000/bob/profile/card#me>;
  acl:accessTo <http://localhost:3000/bob/inbox/>;
  acl:default <http://localhost:3000/bob/inbox/>;
  acl:mode acl:Read, acl:Write, acl:Control.
<#public> a acl:Authorization;
  acl:agentClass foaf:Agent;
  acl:accessTo <http://localhost:3000/bob/inbox/>;
  acl:mode acl:Append.
```

---

On CSS 7.2 (October 2026):

```text
POST /bob/inbox/            as Alice → 201
     location: http://localhost:3000/bob/inbox/58f88a45-…
GET  /bob/inbox/58f88a45-…  as Alice → 403
GET  /bob/inbox/58f88a45-…  as Bob   → 200, the Announce
```

The public rule has no `acl:default`, so each message inherits only Bob's rule. node-solid-server 6 gives every new account this same inbox ACL.

⚠ WAC 1.0 also wants Append or Write on the new resource (Step 8.5). CSS 7.2 checks only the container for POST, so this ACL works there. A strict server would need `acl:default` on the public rule; senders then get Append, but not Read, on every message."""@en ;
    solid-memo:checkedBy <#q-sharing-6a> ,
                         <#q-sharing-6b> .

<#q-sharing-6a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front """A Solid inbox has this WAC ACL. Alice POSTs an `Announce` to the inbox and gets 201 with a `Location`; her GET on that URL then returns 403. What does this tell her?
```turtle
@prefix acl: <http://www.w3.org/ns/auth/acl#>.
@prefix foaf: <http://xmlns.com/foaf/0.1/>.
<#owner> a acl:Authorization;
  acl:agent <https://bob.example/profile/card#me>;
  acl:accessTo <./>; acl:default <./>;
  acl:mode acl:Read, acl:Write, acl:Control.
<#public> a acl:Authorization;
  acl:agentClass foaf:Agent;
  acl:accessTo <./>;
  acl:mode acl:Append.
```"""@en ;
    solid-memo:back "It arrived, but senders can't read messages back"@en ;
    solid-memo:backNote "Only Bob's rule has `acl:default`, so each new message inherits it alone: senders can deliver but can't read anything back, their own messages included."@en ;
    solid-memo:distractor <#q-sharing-6a-d1> ,
                          <#q-sharing-6a-d2> ,
                          <#q-sharing-6a-d3> .

<#q-sharing-6a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It was stored, then rejected by Bob's spam filter"@en ;
    solid-memo:distractorNote "201 means it was created; the 403 is about reading."@en .

<#q-sharing-6a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Her token expired between the two requests"@en ;
    solid-memo:distractorNote "An unusable token gives 401, not 403."@en .

<#q-sharing-6a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It will exist only once Bob has accepted it"@en ;
    solid-memo:distractorNote "LDN has no acceptance step; the POST stores the message."@en .

<#q-sharing-6b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Alice's Solid app wants to notify Bob of a share, but Bob's WebID profile lists no `ldp:inbox`. What should the app do?"@en ;
    solid-memo:back "Not send, and suggest Alice tell Bob another way"@en ;
    solid-memo:backNote "Senders find the inbox through `ldp:inbox`. Creating and linking one needs write access to Bob's pod and profile, so only Bob's own app can do it."@en ;
    solid-memo:distractor <#q-sharing-6b-d1> ,
                          <#q-sharing-6b-d2> ,
                          <#q-sharing-6b-d3> .

<#q-sharing-6b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "POST to `inbox/` at the root of Bob's pod"@en ;
    solid-memo:distractorNote "That guesses a path; an inbox must be discovered."@en .

<#q-sharing-6b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Create an inbox in Bob's pod on his behalf"@en ;
    solid-memo:distractorNote "Only Bob can create it and link it from his profile."@en .

<#q-sharing-6b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "PATCH the message into Bob's profile document"@en ;
    solid-memo:distractorNote "Others can't write his profile, and it isn't a mailbox."@en .

<#ch-sharing-7>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-sharing> ;
    schema:position 6 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Processing an inbox

Bob's app reads his inbox like any container: GET it, follow `ldp:contains` to each message and GET that. Once it has acted on a message, a common pattern is to DELETE it (Step 6.10) or move it to an archive container, so the inbox holds only new mail.

Anyone with Append can post, so every message is an **unverified claim**. The `actor` field is text the sender wrote, so Alice's WebID in it proves nothing. LDN advises receivers to verify senders and filter unwanted notifications.

---

General advice (not a spec rule):
- **Check against the source.** For "Alice shared a note", fetch the `object` with Bob's own login. A 200 proves the share; the message does not.
- **Treat text as data.** In Activity Streams, `summary` may contain HTML. Insert it with `textContent`, never `innerHTML`, and don't follow `javascript:` links (Step 13.1).
- **Limit spam.** Show messages from unknown senders separately or not at all, and cap how many you process at a time. Or give Append only to people you trust (Step 9.8 shows how to name a group).

Bob's app processing Alice's message on CSS 7.2 (October 2026):

```text
GET    /bob/inbox/               → 200, ldp:contains <58f88a45-…>
GET    /bob/inbox/58f88a45-…     → 200, Announce, object …/alice/notes/first.ttl
GET    /alice/notes/first.ttl    → 200, wac-allow: user="read"   (the proof)
DELETE /bob/inbox/58f88a45-…     → 205 Reset Content
GET    /bob/inbox/               → 200, no ldp:contains left
```"""@en ;
    solid-memo:checkedBy <#q-sharing-7a> ,
                         <#q-sharing-7b> .

<#q-sharing-7a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A message in Bob's Solid inbox says Alice shared `https://alice.example/plan.ttl` with him. How should his app check the claim?"@en ;
    solid-memo:back "GET that URL with Bob's login and see whether it succeeds"@en ;
    solid-memo:backNote "A message is only a claim. The pod holding the object decides whether Bob really has access, so ask it."@en ;
    solid-memo:distractor <#q-sharing-7a-d1> ,
                          <#q-sharing-7a-d2> ,
                          <#q-sharing-7a-d3> .

<#q-sharing-7a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Check that the message's `actor` is Alice's WebID"@en ;
    solid-memo:distractorNote "Any sender can put any WebID in `actor`."@en .

<#q-sharing-7a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Trust it, since only Alice may post to Bob's inbox"@en ;
    solid-memo:distractorNote "Inboxes usually let anyone append."@en .

<#q-sharing-7a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Look for the shared file in Alice's public profile"@en ;
    solid-memo:distractorNote "Profiles don't list shares; the pod's answer to Bob is what counts."@en .

<#q-sharing-7b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Bob's Solid app lists the `summary` of each Activity Streams message in his inbox. How should it display the summary?"@en ;
    solid-memo:back "As plain text, for example with `textContent`"@en ;
    solid-memo:backNote "Inbox content comes from strangers, so it is untrusted input. Render it as text, never as markup."@en ;
    solid-memo:distractor <#q-sharing-7b-d1> ,
                          <#q-sharing-7b-d2> ,
                          <#q-sharing-7b-d3> .

<#q-sharing-7b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "With `innerHTML`, because summaries are HTML"@en ;
    solid-memo:distractorNote "Anyone can post, so this lets strangers inject script."@en .

<#q-sharing-7b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "As HTML after stripping `<script>` tags with a regex"@en ;
    solid-memo:distractorNote "Attributes such as `onerror` and `javascript:` links still run code; filtering by pattern is unreliable."@en .

<#q-sharing-7b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "As HTML, but only when the actor is a WebID Bob trusts"@en ;
    solid-memo:distractorNote "Anyone can put any WebID in `actor`, and even a real friend's message may carry hostile markup."@en .

<#ch-sharing-8>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-sharing> ;
    schema:position 7 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Groups: sharing with many people at once

Sharing with a team one WebID at a time means editing many ACLs whenever the team changes. WAC's `acl:agentGroup` (Step 8.4) points to a group instead: a `vcard:Group` whose members are listed with `vcard:hasMember` in an ordinary RDF document:

```turtle
# https://alice.example/groups/friends.ttl
@prefix vcard: <http://www.w3.org/2006/vcard/ns#>.
<#group> a vcard:Group;
  vcard:hasMember <https://bob.example/profile/card#me>,
                  <https://carol.example/profile/card#me>.
```
```turtle
# in a container's ACL
@prefix acl: <http://www.w3.org/ns/auth/acl#>.
<#friends-read> a acl:Authorization;
  acl:agentGroup <https://alice.example/groups/friends.ttl#group>;
  acl:accessTo <./>; acl:default <./>;
  acl:mode acl:Read.
```

To give Dave Read on everything that uses the group, add him to `friends.ttl`; no ACL changes. The flip side: **whoever can write the group document decides who gets that access**, so keep write access to it tight with its own ACL.

⚠ CSS 7.2 fetches the group document anonymously, so it must be publicly readable. In a test in October 2026, a note shared with the group above went like this for Bob:

| Group document readable by | Bob's GET of the note |
|---|---|
| Alice only | 403 |
| Alice, Bob and Carol | 403 |
| Everyone | 200, `wac-allow: user="read"` |

The privacy cost: anyone can read who is in the group.

---

ACP matchers have no group attribute; they test agent, client or issuer (Step 9.1). One matcher can list several `acp:agent` values, any of which may match, and Inrupt's ESS 2.0 dropped group matching by URL. So on ACP, keep the WebIDs in the policy itself."""@en ;
    solid-memo:checkedBy <#q-sharing-8a> ,
                         <#q-sharing-8b> ,
                         <#q-sharing-8c> .

<#q-sharing-8a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid WAC, Alice's ACL grants Read to `acl:agentGroup <…/friends.ttl#group>`. Carol may write `friends.ttl` but has no Control on the ACL. What can Carol do?"@en ;
    solid-memo:back "Give anyone Read by adding them to the group"@en ;
    solid-memo:backNote "Group membership is data in the group document, so write access to it amounts to control over who the group's authorizations cover."@en ;
    solid-memo:distractor <#q-sharing-8a-d1> ,
                          <#q-sharing-8a-d2> ,
                          <#q-sharing-8a-d3> .

<#q-sharing-8a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing extra, since she can't edit the ACL"@en ;
    solid-memo:distractorNote "Editing the group changes whom the ACL grants access to."@en .

<#q-sharing-8a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Change which modes the group's members get"@en ;
    solid-memo:distractorNote "Modes are in the ACL, which needs Control."@en .

<#q-sharing-8a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Add members, but only once Alice approves them"@en ;
    solid-memo:distractorNote "WAC has no approval step for group changes."@en .

<#q-sharing-8b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On a Solid ACP pod, how do you let three friends read one document?"@en ;
    solid-memo:back "A policy whose matcher lists their three WebIDs as `acp:agent`"@en ;
    solid-memo:backNote "Several values of one matcher attribute are alternatives, so one matcher listing three WebIDs matches any of them."@en ;
    solid-memo:distractor <#q-sharing-8b-d1> ,
                          <#q-sharing-8b-d2> ,
                          <#q-sharing-8b-d3> .

<#q-sharing-8b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A policy whose matcher uses `acl:agentGroup` and a vCard group"@en ;
    solid-memo:distractorNote "That is a WAC subject; ACP matchers have no group attribute."@en .

<#q-sharing-8b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A policy whose `acp:allOf` names three single-agent matchers"@en ;
    solid-memo:distractorNote "`allOf` needs all to match at once, but a request has one agent."@en .

<#q-sharing-8b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A policy whose matcher uses `acp:agent acp:AuthenticatedAgent`"@en ;
    solid-memo:distractorNote "That lets anyone who is logged in read the document."@en .

<#q-sharing-8c>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front """On CSS 7.2 (2026), Alice's note grants Read to `acl:agentGroup <groups/friends.ttl#group>`, and the group lists Bob. The group document's own ACL is below. Bob still gets 403 on the note. To keep using `acl:agentGroup`, what must Alice change?
```turtle
@prefix acl: <http://www.w3.org/ns/auth/acl#>.
<#owner> a acl:Authorization;
  acl:agent <https://alice.example/profile/card#me>;
  acl:accessTo <friends.ttl>;
  acl:mode acl:Read, acl:Write, acl:Control.
<#members> a acl:Authorization;
  acl:agent <https://bob.example/profile/card#me>,
            <https://carol.example/profile/card#me>;
  acl:accessTo <friends.ttl>;
  acl:mode acl:Read.
```"""@en ;
    solid-memo:back "Make the group document publicly readable"@en ;
    solid-memo:backNote "⚠ CSS 7.2 fetches the group document anonymously, so a group document only members can read grants nothing. `acl:agentGroup` works there only when that document is public, and then anyone can read who is in the group."@en ;
    solid-memo:distractor <#q-sharing-8c-d1> ,
                          <#q-sharing-8c-d2> ,
                          <#q-sharing-8c-d3> .

<#q-sharing-8c-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Give the group's members Write on the group document"@en ;
    solid-memo:distractorNote "Members need no access to it; only the server reads it, and Write would let them change the group."@en .

<#q-sharing-8c-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Have each member read the group document once"@en ;
    solid-memo:distractorNote "CSS reads it itself, anonymously; members' own reads play no part."@en .

<#q-sharing-8c-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Move the group document next to the note"@en ;
    solid-memo:distractorNote "Any URL works; the group document's location is not the problem."@en .

<#ch-sharing-9>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-sharing> ;
    schema:position 8 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Friends and data across pods

"Solid" began as **So**cial **Li**nked **D**ata. A profile can list the people its owner knows with `foaf:knows`, which FOAF describes as "indicating some level of reciprocated interaction":

```turtle
@prefix foaf: <http://xmlns.com/foaf/0.1/>.
<#me> foaf:knows <https://bob.example/profile/card#me>,
                 <https://carol.example/profile/card#me>.
```

It is a claim that grants nothing. To show friends' data, an app follows each WebID to its profile and then to the data. It reads `pim:storage` for the pod (Step 5.5) and, where there is one, the public type index, which lists which container holds which kind of data (Step 11.4). Many profiles have neither: fall back or skip.

---

One logged-in `fetch` works everywhere. The token says who the user is, and every pod checks it against its own rules. Each friend's pod returns only what that friend shared with this user or with the public. For everything else it answers 403 or 404 (Step 8.7); show that as "not shared", not as an error. A 401 means the pod didn't accept the login, such as an expired token (Chapter 7). Some pods use ACP; some are slow or offline.

On CSS 7.2 (October 2026), Bob's requests to Alice's pod:

```text
GET /alice/notes/            → 403   (before and after Alice adds foaf:knows Bob)
GET /alice/notes/first.ttl   → 200   (the note she shared with him)
```

On CSS 7.2 (2026) a new profile lacks `pim:storage`, so apps walk up to the `pim:Storage` root (Step 5.5)."""@en ;
    solid-memo:checkedBy <#q-sharing-9a> ,
                         <#q-sharing-9b> .

<#q-sharing-9a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid, Alice's WebID profile lists Bob with `foaf:knows`. What does that let Alice's app do on Bob's pod?"@en ;
    solid-memo:back "Nothing extra; it only tells the app where to look"@en ;
    solid-memo:backNote "`foaf:knows` is a statement in Alice's profile. Access to Bob's data is decided only by Bob's pod."@en ;
    solid-memo:distractor <#q-sharing-9a-d1> ,
                          <#q-sharing-9a-d2> ,
                          <#q-sharing-9a-d3> .

<#q-sharing-9a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Read Bob's private data, since he is Alice's friend"@en ;
    solid-memo:distractorNote "`foaf:knows` grants nothing; Bob's pod applies its own rules."@en .

<#q-sharing-9a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Post to Bob's inbox even without an Append rule"@en ;
    solid-memo:distractorNote "Inbox access depends on Bob's ACL, not Alice's profile."@en .

<#q-sharing-9a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Append to any of Bob's containers"@en ;
    solid-memo:distractorNote "Only Bob's ACLs can grant Append; Alice's profile can't."@en .

<#q-sharing-9b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A Solid app reads five friends' pods with the user's logged-in fetch. Two return 403. What should it do?"@en ;
    solid-memo:back "Show those two as not shared with this user"@en ;
    solid-memo:backNote "Each pod decides for itself what this user may see, so seeing some friends' data and not others' is normal."@en ;
    solid-memo:distractor <#q-sharing-9b-d1> ,
                          <#q-sharing-9b-d2> ,
                          <#q-sharing-9b-d3> .

<#q-sharing-9b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Log the user in again separately for those two pods"@en ;
    solid-memo:distractorNote "The same login works for every pod; 403 means \"not allowed\"."@en .

<#q-sharing-9b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Retry anonymously, in case the data is public"@en ;
    solid-memo:distractorNote "Public data is already readable with the user's login."@en .

<#q-sharing-9b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Stop and report that the friends list is broken"@en ;
    solid-memo:distractorNote "Partial access is normal across pods."@en .

<#ch-sharing-10>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-sharing> ;
    schema:position 9 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## One document, several writers

A shared shopping list lives in Alice's pod, but Bob and Carol should edit it too. Alice's ACL lists them, or a group (Step 9.8), with the modes they need:

```turtle
# alongside the #owner rule from Step 9.3
@prefix acl: <http://www.w3.org/ns/auth/acl#>.
<#editors> a acl:Authorization;
  acl:agent <https://bob.example/profile/card#me>,
            <https://carol.example/profile/card#me>;
  acl:accessTo <list.ttl>;
  acl:mode acl:Read, acl:Append.
```

Grant the least that works. An N3 Patch with only `inserts` needs just Append, while `deletes` need Read and Write (Step 8.5). People who only add items can have Append, and then they can't erase anyone's items. On CSS 7.2 (October 2026), with this ACL:

```text
PATCH list.ttl  inserts "Milk"   as Bob → 205 Reset Content
PATCH list.ttl  deletes "Bread"  as Bob → 403 Forbidden
PUT   list.ttl  "Only mine"      as Bob → 403 Forbidden
GET   list.ttl                   as Bob → 200, wac-allow: user="append read"
                                          "Bread", "Milk"
```

---

Several writers make lost updates likely (Step 6.11). Patch only the triples you change rather than PUTting the whole document. Insert-only patches can't lose others' changes, so `If-Match` matters most for patches with `deletes` and for PUT: send the ETag you read, and on 412 re-read, reapply and retry. ⚠ node-solid-server 6.0.0 ignores `If-Match`, so a stale PUT silently overwrites. A stale patch is caught only when its `deletes` no longer match (409).

An **invitation** combines this chapter: change the access (Steps 9.3-9.5), then post an `Invite` or `Announce` naming the list as its `object` to each friend's inbox (Step 9.6)."""@en ;
    solid-memo:checkedBy <#q-sharing-10a> ,
                         <#q-sharing-10b> .

<#q-sharing-10a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Bob should be able to add items to Alice's shared list in her Solid pod, but not remove anyone's. Which WAC modes does he need?"@en ;
    solid-memo:back "Read and Append"@en ;
    solid-memo:backNote "Insert-only N3 Patches need only Append, so Read plus Append lets Bob see and add but not delete."@en ;
    solid-memo:distractor <#q-sharing-10a-d1> ,
                          <#q-sharing-10a-d2> ,
                          <#q-sharing-10a-d3> .

<#q-sharing-10a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Read and Write"@en ;
    solid-memo:distractorNote "Write also lets him delete or change others' items."@en .

<#q-sharing-10a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Append and Control"@en ;
    solid-memo:distractorNote "Control lets him edit the ACL and give himself Write."@en .

<#q-sharing-10a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Write only"@en ;
    solid-memo:distractorNote "Write allows deleting, and without Read he can't see the list."@en .

<#q-sharing-10b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On a Solid server that honours `If-Match`, such as CSS 7.2 (2026), Bob and Carol both rename the same item on a shared list. Each sends a PATCH that deletes the old name and inserts a new one, with `If-Match` and the same ETag. Carol's request arrives second. What happens?"@en ;
    solid-memo:back "She gets 412; her app re-reads and retries her change"@en ;
    solid-memo:backNote "Bob's patch changed the ETag, so Carol's `If-Match` no longer matches and the server answers 412 Precondition Failed. ⚠ node-solid-server 6.0.0 ignores `If-Match`, so you can't rely on this check there."@en ;
    solid-memo:distractor <#q-sharing-10b-d1> ,
                          <#q-sharing-10b-d2> ,
                          <#q-sharing-10b-d3> .

<#q-sharing-10b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Her patch overwrites Bob's change, and both get 205"@en ;
    solid-memo:distractorNote "`If-Match` makes the server refuse a write based on a stale version."@en .

<#q-sharing-10b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "She gets 409; her app should ask Bob to undo his change"@en ;
    solid-memo:distractorNote "A failed precondition is 412, and the fix is to retry on fresh data."@en .

<#q-sharing-10b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server merges both patches and sends her the new ETag"@en ;
    solid-memo:distractorNote "The server compares tags; it does not merge."@en .

<#ch-sharing-11>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-sharing> ;
    schema:position 10 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Apps vs users: the unsolved part

Plain WAC grants access to *people*. An app you log into acts with your WebID, so it gets **all** of your access, not just what it needs. Fixes tried so far:

- **`acl:origin`** limits a rule to a web origin, compared with the `Origin` header browsers send (Step 8.8). The spec warns this "is not intended as client identification": other clients can send any value.
- **`acl:trustedApp`** (old NSS only) listed trusted apps by origin in the user's public profile, pod-wide, revealing which apps a person uses. It is not in the WAC spec or the ACL ontology.
- **ACP client matchers** check the authenticated client ID from the login (`client_id` in the access token, `azp` in the ID token; Step 7.5): much stronger, but only on ACP servers.
- **Access requests and grants** (Inrupt ESS) give another agent scoped, expiring, revocable access, recorded as Verifiable Credentials: an Inrupt feature, not part of the Solid Protocol.
- **SAI** (a CG draft, covered in Step 11.8) adds an Authorization Agent that grants apps access by data type; adoption is narrow.

The universal access API (Step 9.5) can't help: it never names an app."""@en ;
    solid-memo:checkedBy <#q-sharing-11a> ,
                         <#q-sharing-11b> ,
                         <#q-sharing-11c> .

<#q-sharing-11a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Alice logs into a new to-do app on a Solid WAC pod with no origin or client rules. What can the app access?"@en ;
    solid-memo:back "Everything Alice herself can access"@en ;
    solid-memo:backNote "Plain WAC grants access to agents, and an app acting for a user carries that user's WebID, so it inherits all of the user's access."@en ;
    solid-memo:distractor <#q-sharing-11a-d1> ,
                          <#q-sharing-11a-d2> ,
                          <#q-sharing-11a-d3> .

<#q-sharing-11a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only the to-do data it created itself"@en ;
    solid-memo:distractorNote "Plain WAC does not limit apps to their own data."@en .

<#q-sharing-11a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only resources Alice approved for this app at login"@en ;
    solid-memo:distractorNote "Plain WAC has no per-app consent step."@en .

<#q-sharing-11a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing, until Alice adds the app to her ACLs"@en ;
    solid-memo:distractorNote "The app acts as Alice, so her own authorizations already apply."@en .

<#q-sharing-11b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Why is WAC's `acl:origin` a weak way to restrict which app may access data in a Solid pod?"@en ;
    solid-memo:back "Any non-browser client can send any `Origin` value"@en ;
    solid-memo:backNote "Browsers set `Origin`, but the WAC spec says it is not client identification, and other clients can send any value."@en ;
    solid-memo:distractor <#q-sharing-11b-d1> ,
                          <#q-sharing-11b-d2> ,
                          <#q-sharing-11b-d3> .

<#q-sharing-11b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It only works for public resources, not private ones"@en ;
    solid-memo:distractorNote "It can be combined with any agent rule; its problem is trust in the header."@en .

<#q-sharing-11b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It was removed from the WAC spec in 2024"@en ;
    solid-memo:distractorNote "It is still in WAC 1.0.0."@en .

<#q-sharing-11b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It stores the list of allowed apps in the public profile"@en ;
    solid-memo:distractorNote "That was the problem with `acl:trustedApp`, not `acl:origin`."@en .

<#q-sharing-11c>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid, which mechanism restricts a specific app by its authenticated client ID and is defined in an open Solid spec?"@en ;
    solid-memo:back "An ACP policy with an `acp:client` matcher"@en ;
    solid-memo:backNote "ACP matchers can test the client ID from the Solid-OIDC login, which is far stronger than the Origin header; it works only on servers that use ACP."@en ;
    solid-memo:distractor <#q-sharing-11c-d1> ,
                          <#q-sharing-11c-d2> ,
                          <#q-sharing-11c-d3> .

<#q-sharing-11c-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An Inrupt Access Grant naming the app"@en ;
    solid-memo:distractorNote "Access grants are a vendor feature of ESS, not part of an open Solid spec."@en .

<#q-sharing-11c-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A WAC authorization with `acl:origin`"@en ;
    solid-memo:distractorNote "It checks the browser's `Origin` header, which is not an authenticated client ID."@en .

<#q-sharing-11c-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An `acl:trustedApp` entry in the user's profile"@en ;
    solid-memo:distractorNote "It was a legacy NSS feature listed in the public profile, and it is not in the WAC spec."@en .

<#q-sharing-r01>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A WAC rule can only ever add access. What kind of ACP rule has no WAC counterpart because it works the other way?"@en ;
    solid-memo:back "Deny rules that override allows"@en ;
    solid-memo:backNote "WAC is purely additive, while ACP has `acp:deny`, which overrides any allow."@en ;
    solid-memo:distractor <#q-sharing-r01-d1> ,
                          <#q-sharing-r01-d2> ,
                          <#q-sharing-r01-d3> ,
                          <#q-sharing-r01-d4> ,
                          <#q-sharing-r01-d5> ,
                          <#q-sharing-r01-d6> .

<#q-sharing-r01-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "Separate rule documents linked with `rel=\"acl\"`"@en ;
    solid-memo:distractorNote "Both use rule documents linked with `rel=\"acl\"`."@en .

<#q-sharing-r01-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "A mode for appending without writing"@en ;
    solid-memo:distractorNote "Both use the same modes, including `acl:Append`."@en .

<#q-sharing-r01-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "Rules for anonymous public access"@en ;
    solid-memo:distractorNote "WAC has `foaf:Agent`; ACP has `acp:PublicAgent`."@en .

<#q-sharing-r01-d4>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`noneOf` matchers that cancel other grants"@en ;
    solid-memo:distractorNote "`acp:noneOf` only keeps its own policy from being satisfied; it can't cancel another policy's allow."@en .

<#q-sharing-r01-d5>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Own policies that replace inherited ones"@en ;
    solid-memo:distractorNote "That's WAC, where the nearest ACL replaces the others; ACP's member policies accumulate."@en .

<#q-sharing-r01-d6>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Expiry dates that end a grant"@en ;
    solid-memo:distractorNote "Expiring access comes from Inrupt's access requests and grants, not from ACP."@en .

<#q-sharing-r02>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "As of October 2026, are Solid's ways of restricting what an app may access complete or only partial, and does any of them work on every Solid server?"@en ;
    solid-memo:back "Only partial solutions exist, none on every server"@en ;
    solid-memo:backNote "`acl:origin`, trusted apps, ACP client matchers, access grants and SAI each cover part of the problem, and none works everywhere; LWS is working on a standard answer."@en ;
    solid-memo:distractor <#q-sharing-r02-d1> ,
                          <#q-sharing-r02-d2> ,
                          <#q-sharing-r02-d3> ,
                          <#q-sharing-r02-d4> .

<#q-sharing-r02-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "ACP client matchers solve it fully, on most servers"@en ;
    solid-memo:distractorNote "Client matchers work only on ACP servers, and WAC, which has no client matchers, is still the more widely deployed language."@en .

<#q-sharing-r02-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The Protocol's 2024 app grant solves it fully, on every server"@en ;
    solid-memo:distractorNote "The Solid Protocol defines no app-permission mechanism; LWS is working on one."@en .

<#q-sharing-r02-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "Apps can never be restricted; only users can be"@en ;
    solid-memo:distractorNote "ACP client matchers restrict apps by client ID where ACP is used."@en .

<#q-sharing-r02-d4>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only partial solutions exist, but `acl:origin` works on every server"@en ;
    solid-memo:distractorNote "`acl:origin` is a WAC rule, and it is not client identification: other clients can send any `Origin` value. No fix works on every server."@en .

<#q-sharing-r03>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "After Solid-OIDC login, the pod knows Alice's WebID, the app's client ID and the issuer. Which of these can a plain WAC rule check, and which can an ACP matcher check?"@en ;
    solid-memo:back "WAC checks only the WebID; ACP can check all three"@en ;
    solid-memo:backNote "The access token carries the WebID, the client ID (`client_id`; the ID token calls it `azp`) and the issuer. Plain WAC rules name agents only, while ACP matchers can test `acp:agent`, `acp:client` and `acp:issuer`."@en ;
    solid-memo:distractor <#q-sharing-r03-d1> ,
                          <#q-sharing-r03-d2> ,
                          <#q-sharing-r03-d3> .

<#q-sharing-r03-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "WAC and ACP can both check all three"@en ;
    solid-memo:distractorNote "WAC subjects name agents, groups and classes; it has no client or issuer subject."@en .

<#q-sharing-r03-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "WAC checks the WebID and client ID; only ACP checks the issuer"@en ;
    solid-memo:distractorNote "WAC has no client matcher; `acl:origin` uses the browser's Origin header, not the client ID."@en .

<#q-sharing-r03-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Both check only the WebID; the client ID is for login only"@en ;
    solid-memo:distractorNote "ACP's `acp:client` and `acp:issuer` matchers test the client ID and issuer."@en .

<#q-sharing-r04>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your Solid app must let a user share one document with a friend, on both WAC and ACP pods. Which single API call is *meant* to do this on both?"@en ;
    solid-memo:back "The universal access API's `setAgentAccess`"@en ;
    solid-memo:backNote "The universal access API is meant to hide whether a pod uses WAC or ACP, but check the result: on a fresh CSS 7.2 ACP resource (2026) it returned `null` and shared nothing. Then fall back to writing the rule yourself."@en ;
    solid-memo:distractor <#q-sharing-r04-d1> ,
                          <#q-sharing-r04-d2> ,
                          <#q-sharing-r04-d3> .

<#q-sharing-r04-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Writing a WAC `.acl` file next to the document"@en ;
    solid-memo:distractorNote "ACP pods do not use WAC ACL documents, and the ACL URL must be discovered, not built."@en .

<#q-sharing-r04-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Issuing an Inrupt Access Grant to the friend"@en ;
    solid-memo:distractorNote "Access Grants are an ESS feature, not available on CSS or other non-ESS servers."@en .

<#q-sharing-r04-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Adding the friend's WebID to the document's triples"@en ;
    solid-memo:distractorNote "Data triples grant nothing; access is decided by the server's ACL or ACR."@en .

<#q-sharing-r05>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Alice gives Bob Read on a note in two Solid pods, and neither change restates her own access. On her ACP pod she adds an access control for Bob to the note's ACR. On her WAC pod she PUTs a new ACL for the note that holds only Bob's rule. Where does she lose access to the note?"@en ;
    solid-memo:back "Only on the WAC pod"@en ;
    solid-memo:backNote "A WAC ACL replaces everything the note inherited, so it must restate the owner's rule. ACP member policies accumulate, so a new access control only adds."@en ;
    solid-memo:distractor <#q-sharing-r05-d1> ,
                          <#q-sharing-r05-d2> ,
                          <#q-sharing-r05-d3> .

<#q-sharing-r05-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only on the ACP pod"@en ;
    solid-memo:distractorNote "ACP ancestors' member policies keep applying, so adding a policy removes nothing."@en .

<#q-sharing-r05-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "On both pods"@en ;
    solid-memo:distractorNote "In ACP a new access control only adds; the WAC pod is the one where inheritance is replaced."@en .

<#q-sharing-r05-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "On neither pod"@en ;
    solid-memo:distractorNote "Implicit owner control isn't guaranteed, and CSS 7.2 (2026) does lock the owner out."@en .

<#q-sharing-r06>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Alice's Solid app shares a note with Bob on a WAC pod and then tells him about it. What does it do, in order, how does it find each URL, and what does it check before writing the ACL? And how does Bob's app then confirm the share?"@en ;
    solid-memo:back "Follow `rel=\"acl\"`, check `control` in `WAC-Allow`, write the ACL, find Bob's `ldp:inbox`, POST an `Announce`; Bob's app then GETs the note with his login"@en ;
    solid-memo:backNote "Discover the ACL and check Control, then grant; discover the inbox and announce. The recipient verifies by asking the pod, not by trusting the message."@en ;
    solid-memo:distractor <#q-sharing-r06-d1> ,
                          <#q-sharing-r06-d2> ,
                          <#q-sharing-r06-d3> ,
                          <#q-sharing-r06-d4> ,
                          <#q-sharing-r06-d5> ,
                          <#q-sharing-r06-d6> .

<#q-sharing-r06-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "Find Bob's `ldp:inbox`, POST an `Announce`, then follow `rel=\"acl\"`, check `control` in `WAC-Allow` and write the ACL; Bob's app then GETs the note"@en ;
    solid-memo:distractorNote "The message would announce a share that doesn't exist yet; grant first, then tell."@en .

<#q-sharing-r06-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "Follow `rel=\"acl\"`, check `control` in `WAC-Allow`, write the ACL, POST an `Announce`; Bob's app trusts it because its `actor` is Alice's WebID"@en ;
    solid-memo:distractorNote "The sender writes `actor`; Bob's app must check by fetching the note."@en .

<#q-sharing-r06-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "Add `.acl` to the note's URL, write the ACL, POST an `Announce` to `inbox/` at the root of Bob's pod; Bob's app then GETs the note with his login"@en ;
    solid-memo:distractorNote "Both URLs must be discovered: the ACL through `rel=\"acl\"`, the inbox through `ldp:inbox`."@en .

<#q-sharing-r06-d4>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Add `inbox/` to Bob's pod URL, POST an `Announce`, then add `.acl` to the note's URL, check `control` in `WAC-Allow`, write the ACL; Bob's app then GETs the note"@en ;
    solid-memo:distractorNote "Two errors. The message would announce a share that doesn't exist yet; grant first, then tell. And both URLs must be discovered, not guessed: the ACL through `rel=\"acl\"`, the inbox through `ldp:inbox`."@en .

<#q-sharing-r06-d5>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Find Bob's `ldp:inbox`, POST an `Announce`, then follow `rel=\"acl\"`, check `control` in `WAC-Allow`, write the ACL; Bob's app trusts the `actor`, Alice's WebID"@en ;
    solid-memo:distractorNote "Two errors. The message would announce a share that doesn't exist yet; grant first, then tell. And the sender writes `actor`; Bob's app should check by fetching the note."@en .

<#q-sharing-r06-d6>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Add `.acl` to the note's URL, check `control` in `WAC-Allow`, write the ACL, add `inbox/` to Bob's pod URL, POST an `Announce`; Bob's app trusts the `actor`"@en ;
    solid-memo:distractorNote "Two errors. Both URLs must be discovered, not guessed: the ACL through `rel=\"acl\"`, the inbox through `ldp:inbox`. And the sender writes `actor`; Bob's app should check by fetching the note."@en .

<#q-sharing-r07>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Alice shares a shopping list in her Solid pod with her book club through WAC's `acl:agentGroup`. Members should add items but never remove anyone's. Which setup fits?"@en ;
    solid-memo:back "Read and Append for the group, and members' apps send insert-only N3 Patches"@en ;
    solid-memo:backNote "The group says who and the modes say what. Insert-only N3 Patches need only Append, so Read plus Append lets members see and add items but not delete them."@en ;
    solid-memo:distractor <#q-sharing-r07-d1> ,
                          <#q-sharing-r07-d2> ,
                          <#q-sharing-r07-d3> .

<#q-sharing-r07-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Read and Write for the group, and members' apps send insert-only N3 Patches"@en ;
    solid-memo:distractorNote "Write still lets any member delete items with another patch; the modes, not the app, must set the limit."@en .

<#q-sharing-r07-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Append only for the group, and members' apps PUT the whole list"@en ;
    solid-memo:distractorNote "Replacing an existing document needs Write, and without Read members can't see the list."@en .

<#q-sharing-r07-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Read and Control for the group, so members manage their own entries"@en ;
    solid-memo:distractorNote "Control lets members edit the ACL and give themselves Write."@en .

# Chapter 10: Notifications and live updates.
<#ch-notifications>
    a solid-memo:Chapter ,
      schema:Syllabus ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <> ;
    schema:position 9 ;
    dcterms:title "Notifications and live updates"@en ;
    dcterms:description "Keep an app in sync with changing pod data using the Solid Notifications Protocol: discover a subscription service, open a channel, read its messages, and refetch what changed."@en ;
    solid-memo:reviewQuestion <#q-notifications-r01> ,
                              <#q-notifications-r02> ,
                              <#q-notifications-r03> ,
                              <#q-notifications-r04> ,
                              <#q-notifications-r05> .

<#ch-notifications-1>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-notifications> ;
    schema:position 0 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Two kinds of notification

Solid uses the word "notification" for two different things. In Steps 5.11 and 9.6–9.7 you met **Linked Data Notifications (LDN)**, a W3C Recommendation from 2017: an inbox, found through `ldp:inbox`, that other agents POST messages to, like a mailbox. A Solid server must act as an LDN receiver. Those messages are *between agents*: "Bob shared a photo with you".

---

The **Solid Notifications Protocol** is about something else: *change events about resources*. Your app says "tell me when `/notes/shopping.ttl` changes", and the server tells it when that happens. This is what keeps an open app up to date when another app, or another device, edits the same data. Often the events arrive over a **WebSocket**, a connection the browser keeps open so the server can push messages to it.

| | LDN | Solid Notifications |
|---|---|---|
| Carries | messages an agent chose to send | change events about a resource |
| Found through | `ldp:inbox` | the resource's description links |
| Typical use | "I shared this with you" | "`shopping.ttl` was updated" |

Older servers offered an unauthenticated WebSocket API, `solid-0.1`, so anyone could learn when a private resource changed. The Solid Protocol now requires the Solid Notifications Protocol instead."""@en ;
    solid-memo:checkedBy <#q-notifications-1a> ,
                         <#q-notifications-1b> .

<#q-notifications-1a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app shows a shared to-do list stored in a pod and should redraw it when a teammate's app edits the list. Which mechanism fits?"@en ;
    solid-memo:back "Open a Solid Notifications channel on the list resource"@en ;
    solid-memo:backNote "Solid Notifications are change events about a resource you subscribed to; LDN inboxes are mailboxes for messages between agents."@en ;
    solid-memo:distractor <#q-notifications-1a-d1> ,
                          <#q-notifications-1a-d2> ,
                          <#q-notifications-1a-d3> .

<#q-notifications-1a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Read new items from the user's LDN inbox as they arrive"@en ;
    solid-memo:distractorNote "The inbox holds messages other agents chose to send, not automatic change events about a resource."@en .

<#q-notifications-1a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Have the teammate's app POST to your app's inbox after each edit"@en ;
    solid-memo:distractorNote "That couples the two apps and misses edits from any other app; the server should report changes."@en .

<#q-notifications-1a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Re-read the WebID profile until its `ldp:inbox` changes"@en ;
    solid-memo:distractorNote "That predicate only says where the inbox is; it says nothing about changes to the list."@en .

<#q-notifications-1b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Why did Solid replace the old `solid-0.1` WebSocket API for live updates with the Solid Notifications Protocol?"@en ;
    solid-memo:back "Anyone could subscribe, with no authentication"@en ;
    solid-memo:backNote "The legacy API let any client subscribe without proving who it was, so anyone could learn when a private resource changed."@en ;
    solid-memo:distractor <#q-notifications-1b-d1> ,
                          <#q-notifications-1b-d2> ,
                          <#q-notifications-1b-d3> .

<#q-notifications-1b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "WebSockets are not supported by modern browsers"@en ;
    solid-memo:distractorNote "Browsers support WebSockets, and the new protocol's main channel type still uses them."@en .

<#q-notifications-1b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It could only watch containers, not documents"@en ;
    solid-memo:distractorNote "It accepted any resource URL; the problem was who could subscribe."@en .

<#q-notifications-1b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It sent the full new content, which was too large"@en ;
    solid-memo:distractorNote "It sent only the URL of what changed."@en .

<#ch-notifications-2>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-notifications> ;
    schema:position 1 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Discovery: finding a subscription service

You never guess where to subscribe. Discovery starts from the **topic resource**, the resource you want to hear about. From its `Link` headers (Step 5.4) follow `rel="describedby"` to its description resource, or `rel="http://www.w3.org/ns/solid/terms#storageDescription"` to the storage description. Either must be available as JSON-LD. Follow the link rather than hard-coding a path.

The description lists **subscription services**, each with a `channelType` and the optional `feature`s it supports, and may list ready-made `channel`s. The terms live in the `notify:` namespace, `http://www.w3.org/ns/solid/notifications#`. The spec's examples show compact JSON-LD (Step 3.7):

```json
"subscription": [{
  "id": "https://websocket.example/subscription",
  "channelType": "WebSocketChannel2023",
  "feature": ["endAt", "rate", "state"]
}]
```

---

On CSS 7.2 (October 2026), a profile document's headers included:

```http
Link: <http://localhost:3000/alice/profile/card.meta>; rel="describedby"
Link: <http://localhost:3000/.notifications/StreamingHTTPChannel2023/http%3A%2F%2Flocalhost%3A3000%2Falice%2Fprofile%2Fcard>; rel="http://www.w3.org/ns/solid/terms#updatesViaStreamingHttp2023"
Link: <http://localhost:3000/.well-known/solid>; rel="http://www.w3.org/ns/solid/terms#storageDescription"
```

---

The storage description, `/.well-known/solid` (Step 5.6), came back *expanded*, every key a full IRI:

```json
{ "@id": "http://localhost:3000/.notifications/WebSocketChannel2023/",
  "http://www.w3.org/ns/solid/notifications#channelType": [
    { "@id": "http://www.w3.org/ns/solid/notifications#WebSocketChannel2023" } ],
  "http://www.w3.org/ns/solid/notifications#feature": [
    { "@id": "…#accept" }, { "@id": "…#endAt" }, { "@id": "…#rate" },
    { "@id": "…#startAt" }, { "@id": "…#state" } ] }
```

It listed a second service, `…/.notifications/WebhookChannel2023/`, with the same five features.

⚠ On CSS 7.2 only the storage description lists subscription services. The `describedby` resource (`card.meta`, Step 5.10) lists none, so an app should try both links."""@en ;
    solid-memo:checkedBy <#q-notifications-2a> ,
                         <#q-notifications-2b> .

<#q-notifications-2a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app wants live updates for `https://alice.example/notes/a.ttl` via the Solid Notifications Protocol. What should it do first?"@en ;
    solid-memo:back "Follow the topic's `describedby` or storage description link"@en ;
    solid-memo:backNote "Discovery starts at the topic and follows its links to a JSON-LD description that lists subscription services. On CSS 7.2 (2026) only the storage description lists them, so try both."@en ;
    solid-memo:distractor <#q-notifications-2a-d1> ,
                          <#q-notifications-2a-d2> ,
                          <#q-notifications-2a-d3> .

<#q-notifications-2a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "POST a subscription to `https://alice.example/notes/a.ttl` itself"@en ;
    solid-memo:distractorNote "The topic resource is what you watch, not the service that creates channels."@en .

<#q-notifications-2a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Open a WebSocket to `wss://alice.example/` and send `sub`"@en ;
    solid-memo:distractorNote "That is the legacy unauthenticated API, not the current protocol."@en .

<#q-notifications-2a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Look up the subscription URL in Alice's WebID profile"@en ;
    solid-memo:distractorNote "Subscription services are advertised in description resources, not the profile."@en .

<#q-notifications-2b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid Notifications, a description resource lists a subscription service with `\"channelType\": \"WebhookChannel2023\"` and `\"feature\": [\"rate\"]`. What does that tell your app?"@en ;
    solid-memo:back "It can create webhook channels there and may ask for a `rate`"@en ;
    solid-memo:backNote "A subscription service states which channel type it creates and which optional features a client may set when subscribing."@en ;
    solid-memo:distractor <#q-notifications-2b-d1> ,
                          <#q-notifications-2b-d2> ,
                          <#q-notifications-2b-d3> .

<#q-notifications-2b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It must set a `rate` in every request it sends there"@en ;
    solid-memo:distractorNote "Features are optional; the list only says what a client may ask for."@en .

<#q-notifications-2b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server sends webhooks to every app at the given rate"@en ;
    solid-memo:distractorNote "Nothing is sent until a client subscribes and asks for a channel."@en .

<#q-notifications-2b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It must use WebSockets, because `rate` needs a live connection"@en ;
    solid-memo:distractorNote "`rate` is a shared feature that is not tied to one channel type."@en .

<#ch-notifications-3>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-notifications> ;
    schema:position 2 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Subscribing: request and permissions

To subscribe, POST a JSON-LD **channel request** to the subscription service. For a WebSocket channel only `type` and `topic` are required:

```http
POST /subscription
Authorization: DPoP <token>
DPoP: <proof>
Content-Type: application/ld+json

{
  "@context": ["https://www.w3.org/ns/solid/notifications-context/v1"],
  "type": "WebSocketChannel2023",
  "topic": "https://alice.example/notes/a.ttl"
}
```

Use the protocol's context, as here (Step 10.8 explains why). It lets you write the short `WebSocketChannel2023`; the full IRI `http://www.w3.org/ns/solid/notifications#WebSocketChannel2023` works too. CSS 7.2 accepts both forms of this request. The response describes the new channel, including how to receive from it (Step 10.5).

---

The protocol leaves authentication and authorization to implementations, but the main servers use what you learned in Chapters 7 and 8: CSS needs a Solid-OIDC request and **Read** permission on the topic, and Inrupt's ESS 2.x WebSocket service also needed Read. ESS 3.0 removed that service in May 2026 (Step 10.8). You can only watch what you could read, because even the timing of changes to a private resource reveals information."""@en ;
    solid-memo:checkedBy <#q-notifications-3a> .

<#q-notifications-3a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On the Community Solid Server (CSS 7.2, 2026), Bob can read Alice's `/photos/` container but not her `/diary.ttl`. Which Solid Notifications subscriptions will succeed for Bob?"@en ;
    solid-memo:back "One on `/photos/` only, because subscribing needs Read on the topic"@en ;
    solid-memo:backNote "CSS requires an authenticated subscription request and Read permission on the topic resource, as ESS 2.x's WebSocket service did before it."@en ;
    solid-memo:distractor <#q-notifications-3a-d1> ,
                          <#q-notifications-3a-d2> ,
                          <#q-notifications-3a-d3> .

<#q-notifications-3a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Both, because subscribing reveals no content, only events"@en ;
    solid-memo:distractorNote "Change events about a private resource still leak information, so CSS checks Read."@en .

<#q-notifications-3a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Neither, because only the pod owner may subscribe to changes"@en ;
    solid-memo:distractorNote "Any authenticated agent with Read on the topic can subscribe."@en .

<#q-notifications-3a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Both, because CSS checks the subscription service's ACL instead"@en ;
    solid-memo:distractorNote "CSS checks Read on the topic resource itself, not on the service."@en .

<#ch-notifications-4>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-notifications> ;
    schema:position 3 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Channel features and errors

A channel request may add the **features** the service listed:

- `startAt` and `endAt`: when the channel starts and ends, as date-times such as `"2026-10-08T12:00:00Z"`.
- `state`: the last state of the topic you know, such as its ETag.
- `rate`: the minimum time between two notifications, written as an ISO 8601 duration: `PT10S` is ten seconds, `PT1M` is one minute.
- `accept`: the media type you want messages in.

---

CSS 7.2 advertises all five. A request the server cannot process gets **422 Unprocessable Content** (its older name is Unprocessable Entity, which CSS uses, as in Step 6.7). The protocol's example is a JSON-LD context the server does not know; on CSS a `type` it cannot read gets 422 too. So a 422 points at your request body, not at your login or permissions. A request whose media type has a `profile` parameter the server does not support gets **415 Unsupported Media Type** instead.

On CSS 7.2 (October 2026), a request with the singular context `https://www.w3.org/ns/solid/notification/v1` and the short type `WebSocketChannel2023` (Step 10.8) got:

```http
HTTP/1.1 422 Unprocessable Entity
content-type: application/json

{"name":"UnprocessableEntityHttpError","message":"Unable to process notification channel: Missing expected value <http://www.w3.org/ns/solid/notifications#WebSocketChannel2023> - http://www.w3.org/1999/02/22-rdf-syntax-ns#type","statusCode":422,"errorCode":"H422","details":{}}
```"""@en ;
    solid-memo:checkedBy <#q-notifications-4a> ,
                         <#q-notifications-4b> .

<#q-notifications-4a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In a Solid Notifications channel request, what does the feature `\"rate\": \"PT1M\"` ask for?"@en ;
    solid-memo:back "At most one notification per minute on the channel"@en ;
    solid-memo:backNote "`rate` is an ISO 8601 duration giving the minimum time that must pass between notifications sent to the receiver."@en ;
    solid-memo:distractor <#q-notifications-4a-d1> ,
                          <#q-notifications-4a-d2> ,
                          <#q-notifications-4a-d3> .

<#q-notifications-4a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The channel closes after one minute"@en ;
    solid-memo:distractorNote "The channel's end is set with `endAt`, not `rate`."@en .

<#q-notifications-4a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server polls the resource once a minute"@en ;
    solid-memo:distractorNote "`rate` limits how often notifications are sent, not how changes are detected."@en .

<#q-notifications-4a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Every notification is delayed by exactly one minute"@en ;
    solid-memo:distractorNote "It is a minimum gap between notifications, not a fixed delay."@en .

<#q-notifications-4b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app's notification channel request (a JSON-LD POST to a subscription service) gets `422 Unprocessable Entity`. Where should it look first?"@en ;
    solid-memo:back "At the request body's `@context` and `type`"@en ;
    solid-memo:backNote "A 422 means the server could not process what was sent: check the `@context` (use the protocol's own), the `type` and any feature values."@en ;
    solid-memo:distractor <#q-notifications-4b-d1> ,
                          <#q-notifications-4b-d2> ,
                          <#q-notifications-4b-d3> .

<#q-notifications-4b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "At its WebID's Read permission on the topic"@en ;
    solid-memo:distractorNote "A missing permission is an authorization error (401 or 403), not an unprocessable request."@en .

<#q-notifications-4b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "At the server's load, and retry in a minute"@en ;
    solid-memo:distractorNote "Retrying the same body won't help; the server could not process its content."@en .

<#q-notifications-4b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "At the `Content-Type`, and switch to `text/turtle`"@en ;
    solid-memo:distractorNote "Subscription services expect `application/ld+json`; the body's content is the problem."@en .

<#ch-notifications-5>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-notifications> ;
    schema:position 4 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## WebSocket channels

A channel either lets your app **receive from** the server or has the server **send to** your app.

**WebSocketChannel2023** is receive-from: the response holds a `receiveFrom` URL, and your app connects to it. On CSS 7.2 (October 2026), a request like the one in Step 10.3, with a profile document as topic, got this answer, with `type` expanded to the full IRI and `endAt` two weeks ahead by default:

```http
HTTP/1.1 200 OK
content-type: application/ld+json

{"@context":["https://www.w3.org/ns/solid/notification/v1"],
 "id":"http://localhost:3000/.notifications/WebSocketChannel2023/3ee7eea4-…",
 "type":"http://www.w3.org/ns/solid/notifications#WebSocketChannel2023",
 "topic":"http://localhost:3000/alice/profile/card",
 "receiveFrom":"ws://localhost:3000/.notifications/WebSocketChannel2023/3ee7eea4-…",
 "endAt":"2026-10-21T21:33:13.394Z"}
```

```js
const ws = new WebSocket(channel.receiveFrom);
ws.onmessage = (event) => {
  const message = JSON.parse(event.data);
  console.log(message.type, message.object); // Step 10.7: what to do next
};
```

---

Call `new WebSocket(receiveFrom)` with one argument. The draft suggests passing the channel type's IRI as a second argument, but browsers reject that with a `SyntaxError`, and CSS doesn't need it.

`receiveFrom` is a **capability URL**: whoever knows it can listen, so keep it secret. Closing the socket stops delivery, but on CSS the channel remains until it expires or you DELETE its `id`. On CSS 7.2, after the socket was closed:

```text
DELETE <channel id>          → 205 Reset Content
DELETE <channel id> again    → 404 Not Found
```"""@en ;
    solid-memo:checkedBy <#q-notifications-5a> .

<#q-notifications-5a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Why should a Solid app treat a WebSocketChannel2023 notification channel's `receiveFrom` URL as a secret?"@en ;
    solid-memo:back "Whoever knows the URL can listen to that channel"@en ;
    solid-memo:backNote "The subscription response can contain a capability URL that protects the channel, so possessing the URL is what grants access."@en ;
    solid-memo:distractor <#q-notifications-5a-d1> ,
                          <#q-notifications-5a-d2> ,
                          <#q-notifications-5a-d3> .

<#q-notifications-5a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It holds the user's access token, so it works on any pod"@en ;
    solid-memo:distractorNote "The URL only stands for this one channel; access tokens are DPoP-bound and go in headers."@en .

<#q-notifications-5a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Whoever knows it can edit the topic resource"@en ;
    solid-memo:distractorNote "It only gives access to the notifications, not to writing the resource."@en .

<#q-notifications-5a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It reveals the user's identity provider"@en ;
    solid-memo:distractorNote "It points at the notification sender, not the identity provider."@en .

<#ch-notifications-6>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-notifications> ;
    schema:position 5 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Webhook channels, and the other types

**WebhookChannel2023** is send-to, for backends: the request adds an https `sendTo` URL, and the server POSTs each notification there, authenticating itself. It suits a server that has a public HTTPS endpoint but can't keep a socket open; a browser tab has no such endpoint. Unsubscribe explicitly (on CSS, DELETE the `id`); Step 13.8 covers receiving those POSTs safely.

| | Receive-from | Send-to |
|---|---|---|
| Example type | WebSocketChannel2023 | WebhookChannel2023 |
| Address | `receiveFrom`, in the response | `sendTo`, in the request |
| Suits | browser apps | backends with an HTTPS endpoint |

---

Other channel types are registered. As of October 2026 the protocol and every channel type are still drafts:

| Spec | Status, October 2026 |
|---|---|
| Solid Notifications Protocol | Draft CG Report 0.3.0, 2024-05-12 |
| WebSocketChannel2023 | Editor's Draft, 2022-12-27 |
| WebhookChannel2023 | Draft CG Report v0.1, 2026-08-04 |
| StreamingHTTPChannel2023 | Draft CG Report v0.1, 2026-08-04 |

Each row gives the status in the spec's own heading; the W3C TR index (April 2026) still labels all three channel types Editor's Drafts.

---

⚠ You have seen one of them already. Every CSS 7.2 resource advertises, in the `Link` headers of a GET or HEAD, a link with `rel="http://www.w3.org/ns/solid/terms#updatesViaStreamingHttp2023"` (Step 10.2). It points to a ready-made **StreamingHTTPChannel2023** channel for that resource: no subscription, just a request that needs the same permission as reading the resource, whose response stays open and streams notifications as Turtle. This course doesn't use it."""@en ;
    solid-memo:checkedBy <#q-notifications-6a> ,
                         <#q-notifications-6b> .

<#q-notifications-6a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "You are building a browser-only Solid app with no backend and want live updates. Which Solid Notifications channel type suits it?"@en ;
    solid-memo:back "WebSocketChannel2023, since the app connects out to `receiveFrom`"@en ;
    solid-memo:backNote "Receive-from channels like WebSocketChannel2023 let a client open the connection itself; send-to channels need a reachable endpoint."@en ;
    solid-memo:distractor <#q-notifications-6a-d1> ,
                          <#q-notifications-6a-d2> ,
                          <#q-notifications-6a-d3> .

<#q-notifications-6a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "WebhookChannel2023, since the server pushes straight to the browser"@en ;
    solid-memo:distractorNote "A webhook needs an HTTPS endpoint the server can POST to, which a browser tab does not provide."@en .

<#q-notifications-6a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The user's LDN inbox, since every pod can have one"@en ;
    solid-memo:distractorNote "An inbox holds messages that agents chose to send, not change events about a resource."@en .

<#q-notifications-6a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Any type, since the server picks the channel for you"@en ;
    solid-memo:distractorNote "The client chooses a subscription service whose channel type it can handle."@en .

<#q-notifications-6b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On CSS 7.2 (2026), a backend subscribed to a Solid resource with a WebhookChannel2023 channel and no longer needs updates. What should it do?"@en ;
    solid-memo:back "Send DELETE to the channel's `id` to unsubscribe"@en ;
    solid-memo:backNote "A webhook channel must be unsubscribed explicitly; CSS does this with DELETE on the channel's `id` from the subscription response, and other servers may differ."@en ;
    solid-memo:distractor <#q-notifications-6b-d1> ,
                          <#q-notifications-6b-d2> ,
                          <#q-notifications-6b-d3> .

<#q-notifications-6b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Stop answering the webhook POSTs it receives"@en ;
    solid-memo:distractorNote "The server keeps the channel and keeps sending until it is removed or expires."@en .

<#q-notifications-6b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Wait for the channel's `endAt` to pass"@en ;
    solid-memo:distractorNote "Until then the server keeps POSTing to the endpoint; on CSS 7.2 that is two weeks by default."@en .

<#q-notifications-6b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Remove its own Read permission on the topic"@en ;
    solid-memo:distractorNote "That is a roundabout side effect, not how a channel is ended."@en .

<#ch-notifications-7>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-notifications> ;
    schema:position 6 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Notification messages

A notification is an **Activity Streams 2.0** activity in JSON-LD (Chapter 4's `as:`). It must have an `id`, a `type`, an `object` (what changed) and a `published` time; `target` and `state` are optional. CSS sends `Create`, `Update` and `Delete` about a resource, and `Add` or `Remove` with a container as `target`. A message says **what changed, not the new content**: refetch, or skip that when `state` matches the ETag you hold.

---

On CSS 7.2 (October 2026), with a WebSocket channel on a note, `/alice/notes/scratch.ttl`, a PATCH to that note got `205 Reset Content` and the socket received:

```json
{ "@context": ["https://www.w3.org/ns/activitystreams",
               "https://www.w3.org/ns/solid/notification/v1"],
  "id": "urn:1791391461222:http://localhost:3000/alice/notes/scratch.ttl",
  "type": "Update",
  "object": "http://localhost:3000/alice/notes/scratch.ttl",
  "state": "\\"1791391461219-text/turtle\\"",
  "published": "2026-10-07T16:44:21.222Z" }
```

A Turtle HEAD then returned `ETag: "1791391461219-text/turtle"`, the same value. Deleting the note produced a `Delete` message with no `state`.

So on CSS, `state` is the new ETag, quotes included, of the *Turtle* representation: compare it with the ETag from a Turtle GET or HEAD, not a JSON-LD one (Step 6.11). CSS answers a PUT or PATCH without an ETag, so read the resource back to learn yours.

Treat a message as a hint to refetch. Check that `object` is a resource you subscribed to, and never render message fields without escaping (Step 13.1)."""@en ;
    solid-memo:checkedBy <#q-notifications-7a> ,
                         <#q-notifications-7b> ,
                         <#q-notifications-7c> .

<#q-notifications-7a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app receives the notification `{\"type\": \"Update\", \"object\": \".../notes/a.ttl\", ...}` on its channel. What should it do next?"@en ;
    solid-memo:back "GET `a.ttl` again and redraw from the fresh data"@en ;
    solid-memo:backNote "Solid notifications report that `object` changed, not its new content, so the client fetches the resource to get its current state."@en ;
    solid-memo:distractor <#q-notifications-7a-d1> ,
                          <#q-notifications-7a-d2> ,
                          <#q-notifications-7a-d3> .

<#q-notifications-7a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Apply the triples carried in the message to its copy"@en ;
    solid-memo:distractorNote "A notification carries no triples; it only says the resource changed."@en .

<#q-notifications-7a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Fetch `/notes/` to learn which triples changed"@en ;
    solid-memo:distractorNote "The container lists members; it doesn't describe edits inside a document."@en .

<#q-notifications-7a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Resubscribe, because an `Update` ends the channel"@en ;
    solid-memo:distractorNote "A channel stays open across many notifications until it ends or expires."@en .

<#q-notifications-7b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On CSS 7.2 (2026), a Solid Notifications channel watching the container `/photos/` receives `\"type\": \"Add\"` with `\"target\": \".../photos/\"`. What happened?"@en ;
    solid-memo:back "A new member was added to the `/photos/` container"@en ;
    solid-memo:backNote "CSS uses `Add` and `Remove` for changes to a container's contents, with the container as `target` and the member as `object`."@en ;
    solid-memo:distractor <#q-notifications-7b-d1> ,
                          <#q-notifications-7b-d2> ,
                          <#q-notifications-7b-d3> .

<#q-notifications-7b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Someone PATCHed new triples into the `/photos/` listing"@en ;
    solid-memo:distractorNote "Container membership can't be PATCHed directly; it changes when members are created."@en .

<#q-notifications-7b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The `/photos/` container itself was just created"@en ;
    solid-memo:distractorNote "Creating a resource is reported with `Create` about that resource."@en .

<#q-notifications-7b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Your channel gained `/photos/` as a second topic"@en ;
    solid-memo:distractorNote "Activity types describe changes to resources, not to channels."@en .

<#q-notifications-7c>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On CSS 7.2 (2026), an app saves `a.ttl`, then reads it back as Turtle and gets ETag `\"1791391461219-text/turtle\"`. A Solid notification for `a.ttl` then arrives whose `state` is `\"1791391461219-text/turtle\"`. What can the app conclude?"@en ;
    solid-memo:back "Its copy is current, so it can skip the refetch"@en ;
    solid-memo:backNote "On CSS a notification's `state` is the ETag of the Turtle representation, so a match means the cached version is the latest; here the event is the app's own save."@en ;
    solid-memo:distractor <#q-notifications-7c-d1> ,
                          <#q-notifications-7c-d2> ,
                          <#q-notifications-7c-d3> .

<#q-notifications-7c-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Another app overwrote its save, so it must refetch and merge"@en ;
    solid-memo:distractorNote "A matching state means the current version is the one it read."@en .

<#q-notifications-7c-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It must refetch, because `state` is a random message id"@en ;
    solid-memo:distractorNote "The message id is `id`; on CSS `state` is the resource's ETag."@en .

<#q-notifications-7c-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server is asking it to send its ETag back"@en ;
    solid-memo:distractorNote "`state` is information from the server, not a request."@en .

<#ch-notifications-8>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-notifications> ;
    schema:position 7 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Servers differ

The protocol and its channel types are drafts (Step 10.6), and servers differ:

- Inrupt ESS 2.x offered a WebSocket service for "an earlier version" of the protocol, with the subprotocol `solid-0.2`. ESS 3.0 (27 May 2026) removed it for its own Notification Delivery Service.
- Older servers such as Node Solid Server (NSS) offer live updates only through the legacy, unauthenticated `solid-0.1` WebSocket API (Step 10.1), found via an `Updates-Via` header.
- ⚠ Context URLs differ. On 2026-10-07 the protocol's context, `https://www.w3.org/ns/solid/notifications-context/v1`, returned 200, while the singular `https://www.w3.org/ns/solid/notification/v1`, used by the channel drafts and CSS's docs, returned 404.

---

CSS 7.2 accepts the singular context too, but only with the full type IRI, as in its docs. Its recorded answers to a channel request:

| `@context` | short `type` | full type IRI |
|---|---|---|
| `…/notifications-context/v1` | 200 | 200 |
| `…/notification/v1` | 422 | 200 |

Its responses and messages carry the singular URL anyway. Read them as plain JSON (Step 3.7): a JSON-LD processor would try to load that URL and fail.

So keep a fallback. When no supported channel is found, keep working by polling: reread what you display now and then (Step 10.9 makes that cheap)."""@en ;
    solid-memo:checkedBy <#q-notifications-8a> ,
                         <#q-notifications-8b> .

<#q-notifications-8a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app uses Solid Notifications on CSS. Another server advertises no subscription service, only an `Updates-Via` header, and the app's data has change times that must stay private. How should the app keep its view current there?"@en ;
    solid-memo:back "Fall back to polling: reread what the app shows now and then"@en ;
    solid-memo:backNote "Polling works on every server. `Updates-Via` marks the legacy `solid-0.1` API, which anyone can listen to, so it suits only data whose change times aren't sensitive."@en ;
    solid-memo:distractor <#q-notifications-8a-d1> ,
                          <#q-notifications-8a-d2> ,
                          <#q-notifications-8a-d3> .

<#q-notifications-8a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Refuse to run there, since the server isn't a Solid server"@en ;
    solid-memo:distractorNote "Older deployed servers still offer only the legacy API, and the app can keep working by polling."@en .

<#q-notifications-8a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "POST a WebSocketChannel2023 request to the `Updates-Via` URL"@en ;
    solid-memo:distractorNote "That URL is a legacy WebSocket endpoint, not a subscription service."@en .

<#q-notifications-8a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Keep retrying discovery every few seconds until a service appears"@en ;
    solid-memo:distractorNote "A server does not add a subscription service on request; it is advertised or it is not."@en .

<#q-notifications-8b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "CSS 7.2 (2026) answers a Solid Notifications channel request with a body whose `@context` is `https://www.w3.org/ns/solid/notification/v1`, a URL that returned 404 in October 2026. How should the app read the reply?"@en ;
    solid-memo:back "As plain JSON, reading `receiveFrom` and the other keys by name"@en ;
    solid-memo:backNote "The reply's keys are fixed, so plain JSON is enough; a JSON-LD processor would fetch the broken context and fail."@en ;
    solid-memo:distractor <#q-notifications-8b-d1> ,
                          <#q-notifications-8b-d2> ,
                          <#q-notifications-8b-d3> .

<#q-notifications-8b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Expand it with a JSON-LD processor before reading any keys"@en ;
    solid-memo:distractorNote "The processor would try to load the context URL, get a 404 and fail."@en .

<#q-notifications-8b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Resubscribe with that context, so the reply comes back valid"@en ;
    solid-memo:distractorNote "The reply carries the singular URL whatever the request used."@en .

<#q-notifications-8b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Treat the reply as an error, since its context cannot load"@en ;
    solid-memo:distractorNote "The channel was created; only the context URL is broken."@en .

<#ch-notifications-9>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-notifications> ;
    schema:position 8 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## A hint, not a log

Treat notifications as a **hint, not a log**. Sockets drop, laptops sleep, and channels end, and nothing replays the events you missed. When you reconnect or resubscribe, refetch what you display.

ETags (Step 6.11) keep this cheap. Send the ETag you hold in `If-None-Match`; if nothing changed, the server answers **304 Not Modified** with no body. This is new: Step 6.3 used `If-None-Match: *` on a write.

| Header | Sent on | Means | Otherwise |
|---|---|---|---|
| `If-None-Match: *` | a write | only if nothing exists yet | 412 |
| `If-None-Match: "<etag>"` | a GET | only if it changed since this version | 304 |

---

On CSS 7.2 (October 2026), a profile document's ETag was `"1791391528575-text/turtle"`, and a GET sending it back got:

```http
GET /alice/profile/card
If-None-Match: "1791391528575-text/turtle"

HTTP/1.1 304 Not Modified
ETag: "1791391528575-text/turtle"
```

On CSS you can also resubscribe with `state` set to your cached ETag; if the resource changed meanwhile, a notification is sent at once."""@en ;
    solid-memo:checkedBy <#q-notifications-9a> ,
                         <#q-notifications-9b> .

<#q-notifications-9a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app keeps a list current with a WebSocket notification channel. The user's laptop sleeps for an hour and the socket drops. What should the app do when it wakes?"@en ;
    solid-memo:back "Re-establish its channel and refetch the resources it shows"@en ;
    solid-memo:backNote "Events sent while the app was away are not replayed, so it reconnects or resubscribes (perhaps with `state`) and refetches, using ETags to avoid needless downloads."@en ;
    solid-memo:distractor <#q-notifications-9a-d1> ,
                          <#q-notifications-9a-d2> ,
                          <#q-notifications-9a-d3> .

<#q-notifications-9a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Wait for the server to replay the missed notifications"@en ;
    solid-memo:distractorNote "Nothing in the protocol replays events for a closed connection."@en .

<#q-notifications-9a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Reconnect and wait for the next notification to redraw"@en ;
    solid-memo:distractorNote "Changes made during the gap produced no message it received."@en .

<#q-notifications-9a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Show the cached data, since delivery is guaranteed"@en ;
    solid-memo:distractorNote "Notifications are best-effort hints, so the cache may be stale."@en .

<#q-notifications-9b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app holds `a.ttl` with ETag `\"abc-text/turtle\"` and wants to check it is current without downloading it again. Which request fits?"@en ;
    solid-memo:back "GET with `If-None-Match: \"abc-text/turtle\"`; 304 means it is"@en ;
    solid-memo:backNote "A GET with the held ETag in `If-None-Match` returns 304 Not Modified with no body when nothing changed, and the new representation otherwise."@en ;
    solid-memo:distractor <#q-notifications-9b-d1> ,
                          <#q-notifications-9b-d2> ,
                          <#q-notifications-9b-d3> .

<#q-notifications-9b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "GET with `If-None-Match: *`; 304 means it is"@en ;
    solid-memo:distractorNote "`*` matches any existing version, so it can't tell whether yours is current."@en .

<#q-notifications-9b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "PUT the copy with `If-Match: \"abc-text/turtle\"`; 200 means it is"@en ;
    solid-memo:distractorNote "That writes data just to check it; a check should only read."@en .

<#q-notifications-9b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "HEAD with `If-Match: \"abc-text/turtle\"`; 412 means it is"@en ;
    solid-memo:distractorNote "412 from `If-Match` means the ETag no longer matches, the opposite; the reading check is `If-None-Match`."@en .

<#q-notifications-r01>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In the Solid Notifications Protocol, what is the right order of the live-update flow for a resource?"@en ;
    solid-memo:back "Discover the service, subscribe, use the channel, then refetch on a new state"@en ;
    solid-memo:backNote "Follow the topic's links to a subscription service, POST a channel request, use the returned channel, and refetch when a notification reports a state you don't hold."@en ;
    solid-memo:distractor <#q-notifications-r01-d1> ,
                          <#q-notifications-r01-d2> ,
                          <#q-notifications-r01-d3> .

<#q-notifications-r01-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Subscribe at the resource, read its inbox, then apply the diffs"@en ;
    solid-memo:distractorNote "You subscribe at a discovered service, and messages carry no diffs."@en .

<#q-notifications-r01-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Connect to `receiveFrom`, discover the service, then subscribe"@en ;
    solid-memo:distractorNote "You only get `receiveFrom` from the subscription response."@en .

<#q-notifications-r01-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Discover the service, subscribe, then read new content from messages"@en ;
    solid-memo:distractorNote "Messages say what changed; the content must be fetched."@en .

<#q-notifications-r02>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "In Solid, Alice shares a deck with Bob and wants Bob's app to learn about it. Alice's open app should also update when Bob edits the deck. Which mechanisms fit?"@en ;
    solid-memo:back "An LDN message to Bob's inbox; a notification channel on the deck for Alice's app"@en ;
    solid-memo:backNote "An LDN inbox is a mailbox other agents POST to, good for \"I shared this with you\"; the Solid Notifications Protocol reports changes to resources you already know about."@en ;
    solid-memo:distractor <#q-notifications-r02-d1> ,
                          <#q-notifications-r02-d2> ,
                          <#q-notifications-r02-d3> .

<#q-notifications-r02-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A notification channel for Bob's app; an LDN message to Alice's inbox after each edit"@en ;
    solid-memo:distractorNote "This swaps them: Bob's app can't subscribe to a deck it doesn't know about, and the server reports edits without Bob sending anything."@en .

<#q-notifications-r02-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A notification channel on the deck for both Bob's app and Alice's app"@en ;
    solid-memo:distractorNote "Bob's app doesn't know the deck's URL yet, so it has nothing to subscribe to; someone has to tell it."@en .

<#q-notifications-r02-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "LDN messages to both inboxes, one per share and one per edit"@en ;
    solid-memo:distractorNote "Bob's app would have to send a message after every edit, and edits from any other app would go unreported."@en .

<#q-notifications-r03>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Why do current Solid servers such as CSS check a notification subscriber's identity and Read permission, when the legacy `solid-0.1` API did not?"@en ;
    solid-memo:back "Knowing when private data changes is itself sensitive"@en ;
    solid-memo:backNote "Even \"this changed at 3am\" can reveal private information, so servers authenticate subscribers, check Read on the topic, and expose no more than needed."@en ;
    solid-memo:distractor <#q-notifications-r03-d1> ,
                          <#q-notifications-r03-d2> ,
                          <#q-notifications-r03-d3> .

<#q-notifications-r03-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Notifications now include the resource's full content"@en ;
    solid-memo:distractorNote "Messages still say which resource changed, not its content."@en .

<#q-notifications-r03-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Webhooks need a WebID to know where to POST"@en ;
    solid-memo:distractorNote "The webhook destination is the `sendTo` URL in the request."@en .

<#q-notifications-r03-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "WebSockets cannot be opened without a DPoP token"@en ;
    solid-memo:distractorNote "The WebSocket connects with a capability URL; the checks happen at subscription."@en .

<#q-notifications-r04>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A Solid server lists subscription services for both WebSocketChannel2023 and WebhookChannel2023. An app has a browser UI and a backend that emails the user as soon as a shared deck changes. What is a sensible setup?"@en ;
    solid-memo:back "WebSocket for the browser UI, webhook for the backend"@en ;
    solid-memo:backNote "Receive-from WebSocket channels suit clients that stay connected; send-to webhook channels suit backends with an HTTPS endpoint that may not hold a connection."@en ;
    solid-memo:distractor <#q-notifications-r04-d1> ,
                          <#q-notifications-r04-d2> ,
                          <#q-notifications-r04-d3> .

<#q-notifications-r04-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Webhook for both, since webhooks need no subscription"@en ;
    solid-memo:distractorNote "Webhooks also need an authenticated subscription, and a browser has no HTTPS endpoint."@en .

<#q-notifications-r04-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "WebSocket for both, since webhooks are legacy"@en ;
    solid-memo:distractorNote "Webhooks are a current registered channel type, suited to backends that can't keep a socket open."@en .

<#q-notifications-r04-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "One shared channel, since a topic allows only one"@en ;
    solid-memo:distractorNote "Nothing limits a topic to one channel; each client subscribes on its own."@en .

<#q-notifications-r05>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A user is editing a note in a Solid app when a Solid Notifications `Update` message for that note arrives. What should the app do before saving?"@en ;
    solid-memo:back "Refetch, merge, then save with `If-Match` on the new ETag"@en ;
    solid-memo:backNote "A notification warns that the copy is stale; the lost-update rule still applies, so refetch, merge, and write conditionally with `If-Match`."@en ;
    solid-memo:distractor <#q-notifications-r05-d1> ,
                          <#q-notifications-r05-d2> ,
                          <#q-notifications-r05-d3> .

<#q-notifications-r05-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Save immediately, since the notification proves the latest ETag"@en ;
    solid-memo:distractorNote "The notification only says the note changed; saving over it would lose the other edit."@en .

<#q-notifications-r05-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Refetch, replace the editor's text with the server's, then save"@en ;
    solid-memo:distractorNote "That throws away the user's unsaved edit; merge the two instead."@en .

<#q-notifications-r05-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "PATCH without `If-Match`, since PATCH is atomic"@en ;
    solid-memo:distractorNote "Atomic means applied all at once, not that it checks for someone else's newer change."@en .

# Chapter 11: Data-oriented design and interoperability.
<#ch-interop>
    a solid-memo:Chapter ,
      schema:Syllabus ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <> ;
    schema:position 10 ;
    dcterms:title "Data-oriented design and interoperability"@en ;
    dcterms:description "Design an app's data so that other apps, and future versions of the same app, can find it, understand it and safely change it."@en ;
    solid-memo:reviewQuestion <#q-interop-r01> ,
                              <#q-interop-r02> ,
                              <#q-interop-r03> ,
                              <#q-interop-r04> ,
                              <#q-interop-r05> .

<#ch-interop-1>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-interop> ;
    schema:position 0 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Thinking data-first

In a classic web app, the company owns the database and its data model is private. In Solid the user owns the storage, and apps become *views* over that data, the way several image editors can open the same photo file. The promised benefit is no lock-in: when you replace the app, the data stays.

That changes how you design:

| Classic app | Solid app |
|---|---|
| The data model is private | The data model is shared with other apps and should describe itself (the data itself can still be private) |
| Schema changes are internal | Schema changes affect every app that reads the data |
| Unknown columns don't exist | Unknown triples exist and must be preserved |

The last row matters every time you save. Another app may have added triples to "your" subject, so a write must change only what your app means to change.

Noel De Martin calls the goal *interoperable serendipity*: many apps that work together "by pure serendipity", without their developers ever having coordinated."""@en ;
    solid-memo:checkedBy <#q-interop-1a> ,
                         <#q-interop-1b> .

<#q-interop-1a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "In a Solid pod, your notes app loads a note that has a triple with a predicate your app doesn't know. The user edits the title and saves. What should the app write?"@en ;
    solid-memo:back "The new title, leaving the unknown triple in place."@en ;
    solid-memo:backNote "In a pod, many apps may describe the same subject. Change only the triples you mean to change, so other apps' data survives your writes."@en ;
    solid-memo:distractor <#q-interop-1a-d1> ,
                          <#q-interop-1a-d2> ,
                          <#q-interop-1a-d3> .

<#q-interop-1a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The note without the unknown triple, since the app doesn't use it."@en ;
    solid-memo:distractorNote "Another app wrote that triple and would lose its data."@en .

<#q-interop-1a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing, because the note doesn't match the app's schema."@en ;
    solid-memo:distractorNote "Extra triples are normal in an open world and are no reason to refuse."@en .

<#q-interop-1a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The note, with the unknown triple moved to a separate document."@en ;
    solid-memo:distractorNote "The other app looks for its triple on the original subject and would no longer find it."@en .

<#q-interop-1b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "In Solid app design, what does Noel De Martin's term \"interoperable serendipity\" describe?"@en ;
    solid-memo:back "Apps working on the same data without their developers coordinating."@en ;
    solid-memo:backNote "The term names the goal of many independent apps that work together because they follow shared conventions: where data is, what it means and what shape it has."@en ;
    solid-memo:distractor <#q-interop-1b-d1> ,
                          <#q-interop-1b-d2> ,
                          <#q-interop-1b-d3> .

<#q-interop-1b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Apps finding users' pods at random through a public search engine."@en ;
    solid-memo:distractorNote "It is about apps sharing data, not about finding pods."@en .

<#q-interop-1b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Servers translating between vocabularies automatically."@en ;
    solid-memo:distractorNote "Solid servers don't translate vocabularies; apps must agree on them."@en .

<#q-interop-1b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Pods copying data between each other in the background."@en ;
    solid-memo:distractorNote "It describes apps reading the same pod, not pods syncing."@en .

<#ch-interop-2>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-interop> ;
    schema:position 1 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Three things apps must agree on

Ruben Verborgh warns that in today's Solid, "data and apps are not really separated yet", because each app still picks its own document layout. For app B to use app A's data, they must agree on three things:

1. **Where** the data is (discovery): a type index, a newer SAI registry, or a hard-coded path.
2. **What it means** (vocabulary): the classes and predicates, such as `vcard:AddressBook`.
3. **What shape it has** (contract): required properties, how many values, which datatypes, written as a SHACL or ShEx shape.

---

RDF alone gives only a common data model. In Step 4.10, vCard contacts and schema.org contacts were both valid RDF, yet neither app saw the other's. As Leigh Dodds puts it, "Solid has no built in understanding of any specific schemas or formats".

The Solid Protocol prescribes no app layout, which is why type indexes exist; even popular tutorials hard-code a folder such as `my-solid-app/` for simplicity.

This chapter's worked example is **Solid Memo**, an open-source flashcard app whose published data policy shows one app's practice (Chapter 15 walks through its code). Its rules are good habits, not spec requirements."""@en ;
    solid-memo:checkedBy <#q-interop-2a> ,
                         <#q-interop-2b> .

<#q-interop-2a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Solid apps A and B both store address books as `vcard:AddressBook` in Turtle in the same pod, yet B never shows A's address books. Which layer has most likely failed?"@en ;
    solid-memo:back "Discovery: B doesn't know where A put them."@en ;
    solid-memo:backNote "Sharing a vocabulary doesn't help if B can't find the documents. Discovery is a separate agreement, usually made through a type index."@en ;
    solid-memo:distractor <#q-interop-2a-d1> ,
                          <#q-interop-2a-d2> ,
                          <#q-interop-2a-d3> .

<#q-interop-2a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Vocabulary: B expects schema.org names for each contact."@en ;
    solid-memo:distractorNote "The class matches, and a mismatch would hide fields, not whole books."@en .

<#q-interop-2a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Syntax: B needs JSON-LD instead of Turtle."@en ;
    solid-memo:distractorNote "A Solid server serves the same RDF as Turtle or JSON-LD on request."@en .

<#q-interop-2a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Access: B needs Control on the address book."@en ;
    solid-memo:distractorNote "Control is about editing the ACL, and reading needs only Read."@en .

<#q-interop-2b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Why isn't \"we store everything as RDF\" enough for two Solid apps to share data?"@en ;
    solid-memo:back "They must also agree on location, terms and shape."@en ;
    solid-memo:backNote "RDF is the common model, but interoperability needs discovery, a shared vocabulary and a shared shape on top of it."@en ;
    solid-memo:distractor <#q-interop-2b-d1> ,
                          <#q-interop-2b-d2> ,
                          <#q-interop-2b-d3> .

<#q-interop-2b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Each Solid server stores RDF in its own incompatible dialect."@en ;
    solid-memo:distractorNote "Servers exchange standard Turtle and JSON-LD."@en .

<#q-interop-2b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "RDF data can't be read by browser JavaScript."@en ;
    solid-memo:distractorNote "JavaScript RDF libraries run in the browser."@en .

<#q-interop-2b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The Protocol fixes one folder per kind of data."@en ;
    solid-memo:distractorNote "The Protocol prescribes no app layout at all."@en .

<#ch-interop-3>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-interop> ;
    schema:position 2 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## The profile as the entry point

An app usually starts with only a WebID. Chapter 7 covered what a profile contains; here is how to walk it:

1. **The WebID document.** Look for `pim:storage`, `solid:publicTypeIndex` and `pim:preferencesFile`.
2. **Extended profiles,** linked with `rdfs:seeAlso` or `foaf:isPrimaryTopicOf`. The same links may live there instead.
3. **The preferences file.** It is private, so fetch it signed in. It may link the private type index.
4. **The storage.** Failing `pim:storage`, walk up the URL path from a resource known to be in the pod (such as the extended profile) until a response carries the `pim:Storage` type link (Step 5.5).

---

A fresh CSS 7.2 profile has no `pim:storage`. Walking up from `/alice/profile/card`, an anonymous `HEAD /alice/profile/` gets `401` with no type links, so keep going; the pod root answers (abridged):

```http
HEAD /alice/ HTTP/1.1

HTTP/1.1 200 OK
Link: <http://www.w3.org/ns/pim/space#Storage>; rel="type"
Link: <http://www.w3.org/ns/ldp#Container>; rel="type"
…
```

Real profiles differ. On Inrupt ESS 2.x the WebID document isn't in the pod, apps can't rely on writing it, and by default it holds little more than `a foaf:Agent` and `solid:oidcIssuer`. Profile data belongs in the extended profile.

So read *every* profile document before deciding a link is missing. To add a link, write it to the WebID document if writable, otherwise to the first writable extended profile."""@en ;
    solid-memo:checkedBy <#q-interop-3a> ,
                         <#q-interop-3b> .

<#q-interop-3a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A user's Solid WebID document has `foaf:isPrimaryTopicOf` pointing to an extended profile, but no `solid:publicTypeIndex`. What should your app do next?"@en ;
    solid-memo:back "Check the extended profile before deciding the link is missing."@en ;
    solid-memo:backNote "Profile links can be split across the WebID document and extended profiles, so check all of them first."@en ;
    solid-memo:distractor <#q-interop-3a-d1> ,
                          <#q-interop-3a-d2> ,
                          <#q-interop-3a-d3> .

<#q-interop-3a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Create a new public type index and link it from the WebID document."@en ;
    solid-memo:distractorNote "The index may exist elsewhere, and the WebID document may be read-only."@en .

<#q-interop-3a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Try `/settings/publicTypeIndex.ttl` on the WebID's domain."@en ;
    solid-memo:distractorNote "Guessing URLs is unreliable, and the WebID may not even be hosted in the pod."@en .

<#q-interop-3a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Ask the user's OIDC issuer where the index is."@en ;
    solid-memo:distractorNote "The issuer handles login and doesn't describe where data lives."@en .

<#q-interop-3b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "None of a user's Solid profile documents contains `pim:storage`. How can an app still find the storage root?"@en ;
    solid-memo:back "Walk up the path until a response has the `pim:Storage` type link."@en ;
    solid-memo:backNote "A Solid server marks a storage root with `Link: <http://www.w3.org/ns/pim/space#Storage>; rel=\"type\"`, so checking each level of the path above a resource in the pod finds the root without guessing."@en ;
    solid-memo:distractor <#q-interop-3b-d1> ,
                          <#q-interop-3b-d2> ,
                          <#q-interop-3b-d3> .

<#q-interop-3b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Assume the root of the WebID's origin is the storage."@en ;
    solid-memo:distractorNote "The WebID may be hosted somewhere other than the pod."@en .

<#q-interop-3b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Fetch `/.well-known/solid` on the WebID's host and use the storage it names."@en ;
    solid-memo:distractorNote "On CSS 7.2 (2026) that description is server-wide and names the server root, not the pod, and the WebID may live elsewhere."@en .

<#q-interop-3b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Read the storage URL from the ID token's claims."@en ;
    solid-memo:distractorNote "Solid-OIDC tokens identify the user, not their storage."@en .

<#ch-interop-4>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-interop> ;
    schema:position 3 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Type indexes: finding data

A type index maps RDF classes to locations. It is an Editor's Draft (v1.0.0, March 2023), not a W3C standard, but it is the discovery mechanism apps actually use.

There are two indexes:

- The **public** index is linked from the WebID profile by `solid:publicTypeIndex`, is typed `solid:ListedDocument`, and should be publicly readable.
- The **private** index is linked from the preferences file by `solid:privateTypeIndex`, is typed `solid:UnlistedDocument`, and should be readable only by the owner. The preferences file is private too, so only the owner's apps can even follow the link.

---

Each index holds registrations:

```turtle
<#r1> a solid:TypeRegistration ;
    solid:forClass schema:Recipe ;
    solid:instanceContainer </recipes/> .
```

`solid:instance` points at one resource; `solid:instanceContainer` points at a container the client must list. Discovery is: profile → index → registration for your class → the resource, or the container's `ldp:contains`.

A registration names a class, not a shape: it tells you where `schema:Recipe` data lives, not which properties each recipe has."""@en ;
    solid-memo:checkedBy <#q-interop-4a> ,
                         <#q-interop-4b> .

<#q-interop-4a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A registration in a Solid type index says `solid:instanceContainer </recipes/>`. How does an app get the recipes?"@en ;
    solid-memo:back "List the container and fetch the documents it contains."@en ;
    solid-memo:backNote "`instanceContainer` means \"data of this class lives in documents inside this container\", so the client reads `ldp:contains` and then each document."@en ;
    solid-memo:distractor <#q-interop-4a-d1> ,
                          <#q-interop-4a-d2> ,
                          <#q-interop-4a-d3> .

<#q-interop-4a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "GET `/recipes/` and expect every recipe triple in that reply."@en ;
    solid-memo:distractorNote "A container listing gives membership, not the contents of each document."@en .

<#q-interop-4a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Treat `/recipes/` itself as the single recipe document."@en ;
    solid-memo:distractorNote "That is what `solid:instance` means, not `instanceContainer`."@en .

<#q-interop-4a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Look up a separate registration for each recipe."@en ;
    solid-memo:distractorNote "One registration covers the whole container."@en .

<#q-interop-4b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Where does the Solid Type Indexes spec (Editor's Draft, 2023) put the links to a user's public and private type indexes?"@en ;
    solid-memo:back "Public: the profile; private: the preferences file."@en ;
    solid-memo:backNote "The profile links the public index with `solid:publicTypeIndex`; the private one is reached through `pim:preferencesFile`, then `solid:privateTypeIndex`, with an authenticated request. Some real profiles also carry `solid:privateTypeIndex` directly, which is why apps read every profile document."@en ;
    solid-memo:distractor <#q-interop-4b-d1> ,
                          <#q-interop-4b-d2> ,
                          <#q-interop-4b-d3> .

<#q-interop-4b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Public: the profile; private: the profile too."@en ;
    solid-memo:distractorNote "The spec keeps the private link out of the public profile, in the private preferences file."@en .

<#q-interop-4b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Public: the preferences file; private: the preferences file too."@en ;
    solid-memo:distractorNote "The public index must be findable by anyone, and the preferences file is private."@en .

<#q-interop-4b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Public: the storage description; private: the preferences file."@en ;
    solid-memo:distractorNote "The storage description at `/.well-known/solid` describes the storage, not one user's indexes."@en .

<#ch-interop-5>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-interop> ;
    schema:position 4 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Registering, and creating a missing index

Registering is app behaviour, not protocol: ask the user where to store data, then register it. Use the private index unless others must discover the data: a public registration reveals *that* the user keeps a kind of data, and where, even when the data is protected.

Other apps edit the same index, so never PUT an existing one: an insert-only PATCH keeps their registrations and needs no `If-Match`. A patch that also deletes needs `If-Match` (Step 6.11).

Pick a fragment that won't clash, such as `<#reg-notes-9f3c1a>`: an insert into an existing subject merges with it, so two apps using `<#notes>` would corrupt each other's registration. Not a blank node: CSS 7.2 rejects those in inserts with `422` (Step 6.8).

---

A fresh CSS 7.2 pod has no preferences file or index. Ask the user first (Step 15.4), then:

1. PUT `settings/privateTypeIndex.ttl` and `settings/prefs.ttl`, which links it, with `If-None-Match: *` (Step 6.3). Both inherit the root's owner-only rule (Step 8.6).
2. Link `settings/prefs.ttl` from the profile with an insert-only N3 Patch.
3. Insert the registration; make no public index.

On CSS 7.2 the insert answers `205 Reset Content` (adapted from a recorded run that used `<#notes>` in a fresh pod):

```http
PATCH /alice/settings/privateTypeIndex.ttl HTTP/1.1
Content-Type: text/n3

@prefix solid: <http://www.w3.org/ns/solid/terms#>.
@prefix schema: <http://schema.org/>.
_:patch a solid:InsertDeletePatch;
  solid:inserts { <#reg-notes-9f3c1a> a solid:TypeRegistration;
    solid:forClass schema:NoteDigitalDocument;
    solid:instanceContainer </alice/notes/> . }.

HTTP/1.1 205 Reset Content
```"""@en ;
    solid-memo:checkedBy <#q-interop-5a> ,
                         <#q-interop-5b> ,
                         <#q-interop-5c> .

<#q-interop-5a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A health app adds a public Solid type index registration for `health:MedicationLog` pointing at a private container. What does anyone on the web learn?"@en ;
    solid-memo:back "That the user keeps medication logs, and where."@en ;
    solid-memo:backNote "Registering publicly doesn't expose the data, but it does expose the category and location. Use the private index unless others must discover the data."@en ;
    solid-memo:distractor <#q-interop-5a-d1> ,
                          <#q-interop-5a-d2> ,
                          <#q-interop-5a-d3> .

<#q-interop-5a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The contents of the medication logs, entry by entry."@en ;
    solid-memo:distractorNote "The logs are still protected by their own access rules."@en .

<#q-interop-5a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing, because the container is private."@en ;
    solid-memo:distractorNote "The registration itself sits in a publicly readable document."@en .

<#q-interop-5a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The names of the files in the container."@en ;
    solid-memo:distractorNote "The listing is protected by the container's own access rules."@en .

<#q-interop-5b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your Solid app adds a registration to the private type index in the user's CSS 7.2 pod, which other apps also use. What kind of request should it send, and what kind of subject should the new registration get?"@en ;
    solid-memo:back "An insert-only N3 Patch, and a fragment unlikely to clash, such as `<#reg-notes-9f3c1a>`."@en ;
    solid-memo:backNote "An insert-only patch adds to the index without touching other apps' registrations and needs no `If-Match`. An insert into an existing subject merges with it, so a fragment no one else is likely to pick keeps yours separate. Not a blank node: CSS 7.2 rejects those in inserts with `422`."@en ;
    solid-memo:distractor <#q-interop-5b-d1> ,
                          <#q-interop-5b-d2> ,
                          <#q-interop-5b-d3> ,
                          <#q-interop-5b-d4> ,
                          <#q-interop-5b-d5> .

<#q-interop-5b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A PUT of the index with only your registration, and a fragment unlikely to clash, such as `<#reg-notes-9f3c1a>`."@en ;
    solid-memo:distractorNote "A PUT replaces the document, deleting other apps' registrations."@en .

<#q-interop-5b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "An insert-only N3 Patch with `<#notes> a solid:TypeRegistration; …`."@en ;
    solid-memo:distractorNote "Another app may already use `<#notes>`, and your triples would merge into its registration."@en .

<#q-interop-5b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "A POST of `<#reg-notes-9f3c1a> a solid:TypeRegistration; …` to the index's URL."@en ;
    solid-memo:distractorNote "POST creates a new resource in a container; the index is a document."@en .

<#q-interop-5b-d4>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An insert-only N3 Patch, and a blank node, which no other app's IRI can clash with."@en ;
    solid-memo:distractorNote "CSS 7.2 rejects blank nodes in inserts with `422`, so the patch fails."@en .

<#q-interop-5b-d5>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A PUT of the index with only your registration, and a blank node, which no other app's IRI can clash with."@en ;
    solid-memo:distractorNote "A PUT replaces the document, deleting other apps' registrations."@en .

<#q-interop-5c>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On Community Solid Server (CSS) 7.2 (2026), a user's fresh pod has no preferences file and no type index. What should your app do before registering its data?"@en ;
    solid-memo:back "Ask the user, then create both under `settings/` with `If-None-Match: *`."@en ;
    solid-memo:backNote "Creating settings files changes the user's pod, so ask first. `If-None-Match: *` makes the PUT create-only, and under `settings/` the new files inherit the root's owner-only rule, so they stay private."@en ;
    solid-memo:distractor <#q-interop-5c-d1> ,
                          <#q-interop-5c-d2> ,
                          <#q-interop-5c-d3> .

<#q-interop-5c-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Create both under `settings/` silently, since every app needs them."@en ;
    solid-memo:distractorNote "They live in the user's pod; creating them is the user's choice, so ask first."@en .

<#q-interop-5c-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Create a public type index in the profile, so other apps can find the data."@en ;
    solid-memo:distractorNote "Use the private index unless others must discover the data; a public one reveals what the user keeps."@en .

<#q-interop-5c-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Keep the registration in `localStorage` until the user makes an index."@en ;
    solid-memo:distractorNote "Another device or app could never find it; the registration belongs in the pod."@en .

<#ch-interop-6>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-interop> ;
    schema:position 5 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Shapes as contracts: SHACL

A pod is open: the server has no built-in understanding of your app's schema, so any app with write access can store any triples. Chapter 4 showed that `rdfs:range` infers rather than rejects. To say "a card has exactly one front, and it is a string", you need a **shape**.

SHACL is a W3C Recommendation (2017). A *node shape* describes a *focus node* (the subject being checked), and a *property shape* (identified by `sh:path`) constrains one property. A *target* such as `sh:targetClass` says which nodes are focus nodes:

```turtle
ex:CardShape a sh:NodeShape ;
  sh:targetClass ex:Card ;
  sh:property [ sh:path ex:front ; sh:minCount 1 ; sh:maxCount 1 ;
                sh:datatype xsd:string ] ;
  sh:property [ sh:path ex:back ; sh:minCount 1 ;
                sh:datatype xsd:string ] .
```

A validator checks a data graph against the shapes and returns a report. Here every `ex:Card` in the data is checked. `sh:conforms` is true exactly when the report has no results. A validator can also be handed a focus node directly, and then the shape's targets are ignored.

---

Shapes are **open by default**: properties a shape doesn't mention are allowed. Only `sh:closed true` forbids them. On shared data, keep shapes open, or every triple another app adds becomes a violation.

As of October 2026, SHACL 1.2 Core is a Working Draft (September 2026), so don't depend on its new features yet."""@en ;
    solid-memo:checkedBy <#q-interop-6a> ,
                         <#q-interop-6b> .

<#q-interop-6a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A SHACL shape targets `ex:Card` and requires exactly one `ex:front` with `sh:datatype xsd:string`. A card in the data graph has `ex:front 42` (an integer). What does validation produce?"@en ;
    solid-memo:back "A validation result, so `sh:conforms` is false."@en ;
    solid-memo:backNote "The target makes the card a focus node, and SHACL lists every mismatch between it and the shape. One mismatch makes `sh:conforms` false."@en ;
    solid-memo:distractor <#q-interop-6a-d1> ,
                          <#q-interop-6a-d2> ,
                          <#q-interop-6a-d3> .

<#q-interop-6a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An inferred triple saying `42` is a string."@en ;
    solid-memo:distractorNote "That is RDFS inference; SHACL reports violations."@en .

<#q-interop-6a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A 400 error from the pod when the card was saved."@en ;
    solid-memo:distractorNote "A standard Solid server doesn't check app data against your shapes."@en .

<#q-interop-6a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The literal silently converted to `\"42\"`."@en ;
    solid-memo:distractorNote "Validation reports problems and never changes the data."@en .

<#q-interop-6b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Another Solid app adds `dcterms:created` to one of your cards. Your SHACL `CardShape` doesn't mention that property. Does the card still conform?"@en ;
    solid-memo:back "Yes, because shapes allow extra properties unless closed."@en ;
    solid-memo:backNote "SHACL shapes are open by default, which is what lets several apps add to the same subject without breaking each other's validation."@en ;
    solid-memo:distractor <#q-interop-6b-d1> ,
                          <#q-interop-6b-d2> ,
                          <#q-interop-6b-d3> .

<#q-interop-6b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "No, because every property must be declared in the shape."@en ;
    solid-memo:distractorNote "That only holds for shapes with `sh:closed true`."@en .

<#q-interop-6b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "No, because `sh:targetClass ex:Card` covers every property of a card."@en ;
    solid-memo:distractorNote "Targeting chooses which nodes to check, not which properties are allowed."@en .

<#q-interop-6b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only if the other app also publishes a shape."@en ;
    solid-memo:distractorNote "Validation uses your shape and the data, nothing else."@en .

<#ch-interop-7>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-interop> ;
    schema:position 6 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## ShEx and shapes-to-code

ShEx (Shape Expressions) is the second shape language. ShEx 2.1 is a Final Community Group Report (2019), not a W3C Recommendation, and IEEE P3330 is working on a standard for it. Its compact syntax, ShExC, reads like a schema:

```shex
ex:CardShape {
  ex:front xsd:string ;
  ex:back  xsd:string +
}
```

Here each listed property must appear exactly once by default, and `+` means one or more. Like SHACL, ShEx allows properties a shape doesn't mention unless the shape is marked `CLOSED`. Instead of targets in the schema, ShEx uses a **ShapeMap**: you say which node to check against which shape when you run the validation.

---

Shapes can also generate code. LDO, a TypeScript library for Solid, compiles ShEx into TypeScript types (the LDO guide runs `build:ldo`), so app code reads `person.name` rather than building triples by hand. Solid Memo generates its record types from SHACL. Either way, one published contract drives both validation and your types. Types only check your own code at compile time, though; data from a pod arrives at run time, written by any app, so still validate what you read."""@en ;
    solid-memo:checkedBy <#q-interop-7a> ,
                         <#q-interop-7b> .

<#q-interop-7a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In ShEx (Shape Expressions), how do you say which node should be checked against which shape?"@en ;
    solid-memo:back "With a ShapeMap supplied when you validate."@en ;
    solid-memo:backNote "A ShapeMap pairs nodes with shape labels for one validation run, and the result is pass or fail per node."@en ;
    solid-memo:distractor <#q-interop-7a-d1> ,
                          <#q-interop-7a-d2> ,
                          <#q-interop-7a-d3> .

<#q-interop-7a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "With `sh:targetClass` inside the schema."@en ;
    solid-memo:distractorNote "That is how SHACL selects nodes, not ShEx."@en .

<#q-interop-7a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "With a list of focus nodes inside each shape."@en ;
    solid-memo:distractorNote "ShEx keeps node selection out of the schema, in the ShapeMap."@en .

<#q-interop-7a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "With no list: every typed node is checked."@en ;
    solid-memo:distractorNote "ShEx checks only the node and shape pairs you name."@en .

<#q-interop-7b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Your Solid app's TypeScript types are generated from its ShEx shapes with LDO. What does that give you?"@en ;
    solid-memo:back "Code that is typed against the published data contract."@en ;
    solid-memo:backNote "Generating types from the shapes keeps the code and the published contract in step, but it can't control what other apps put in the pod."@en ;
    solid-memo:distractor <#q-interop-7b-d1> ,
                          <#q-interop-7b-d2> ,
                          <#q-interop-7b-d3> .

<#q-interop-7b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A guarantee that any data read from the pod is valid at run time."@en ;
    solid-memo:distractorNote "Other apps may have written anything; you still validate at run time."@en .

<#q-interop-7b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Shape validation on the server for every write."@en ;
    solid-memo:distractorNote "Code generation runs in your build, not on the pod."@en .

<#q-interop-7b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Automatic migration of data in older formats."@en ;
    solid-memo:distractorNote "Migrations are code you write separately."@en .

<#ch-interop-8>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-interop> ;
    schema:position 7 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## SAI and Shape Trees: the next model

Solid Application Interoperability (SAI), a draft Community Group report (as of October 2026), rethinks discovery and access together. Three ideas carry it:

- **An Authorization Agent.** The user's profile names an app that manages access for them (`interop:hasAuthorizationAgent`).
- **Data organised by shape tree.** Data lives in registrations, each a container whose contents conform to one **shape tree**: a template for a tree of resources and the ShEx or SHACL shapes they must match.
- **Need → decision → grant.** An app declares what it needs by shape tree and access mode; the user decides in their agent, which grants the app exactly that data.

| | Type index | SAI |
|---|---|---|
| Unit of agreement | RDF class | Shape tree |
| Who writes it | Each app | The Authorization Agent |
| Access | Separate (WAC/ACP) | Built in: need → decision → grant |

---

SAI addresses Chapter 9's apps-versus-users problem (Step 9.11), but adoption is narrow: ActivityPods, a Solid-based ActivityPub server, implements its application registrations, and a 2024 community summary found type indexes "the only one you can use in practice"."""@en ;
    solid-memo:checkedBy <#q-interop-8a> ,
                         <#q-interop-8b> .

<#q-interop-8a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Compared with a Solid app that uses type indexes, what does a Solid Application Interoperability (SAI) app ask for?"@en ;
    solid-memo:back "Access to data by shape tree, granted by the user's agent."@en ;
    solid-memo:backNote "In SAI the agreement moves from \"where\" and \"what class\" to \"what shaped tree of data\", and the user's Authorization Agent decides and issues the grants."@en ;
    solid-memo:distractor <#q-interop-8a-d1> ,
                          <#q-interop-8a-d2> ,
                          <#q-interop-8a-d3> .

<#q-interop-8a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Access to a list of container paths it promises to write to."@en ;
    solid-memo:distractorNote "In SAI, an app's Access Needs name shape trees, not paths."@en .

<#q-interop-8a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A `forClass` registration in the user's public index."@en ;
    solid-memo:distractorNote "That is the type-index mechanism SAI replaces."@en .

<#q-interop-8a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Control access on the root of the user's storage."@en ;
    solid-memo:distractorNote "SAI grants scoped access to registrations, not full control."@en .

<#q-interop-8b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "As of 2026, why should a new Solid app still support type indexes, even though Solid Application Interoperability (SAI) exists?"@en ;
    solid-memo:back "Most existing apps rely on them, not on SAI."@en ;
    solid-memo:backNote "Both are drafts, but type indexes are the de-facto mechanism, while SAI lacks server support and has only a few implementations."@en ;
    solid-memo:distractor <#q-interop-8b-d1> ,
                          <#q-interop-8b-d2> ,
                          <#q-interop-8b-d3> .

<#q-interop-8b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "SAI was withdrawn by the Solid Community Group."@en ;
    solid-memo:distractorNote "SAI is still an active draft, updated in 2026."@en .

<#q-interop-8b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Type indexes are a W3C Recommendation."@en ;
    solid-memo:distractorNote "The Type Indexes spec is an Editor's Draft."@en .

<#q-interop-8b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "SAI works only on Inrupt's ESS."@en ;
    solid-memo:distractorNote "It is a Community Group draft, and ActivityPods implements parts of it."@en .

<#ch-interop-9>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-interop> ;
    schema:position 8 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Pod layout: granularity

Verborgh's "contacts conundrum" shows why no single folder layout suits every app: an address book wants one document per contact, while a birthday app wants one birthday list for family and another for work. So choose document boundaries with care. A document is the unit of fetching and of access control: you read it whole, and you share it whole.

Three rules follow, shown with a flashcard app such as Solid Memo:

- **Group what is read together.** The Protocol has no batch requests or queries, so every document costs one GET. Solid Memo keeps one deck in one document, so opening a deck is one request.
- **Separate fast from slow data.** Card text rarely changes; review state changes every session. Keeping them in separate documents means studying never rewrites the cards. `<cards.ttl#c1>` and `<reviews.ttl#c1>` are different IRIs: the app pairs them by their shared fragment, and the deck links both documents (`sm:cardsDocument`, `sm:reviewsDocument`) so other apps can find the pair.
- **Split growing logs by period.** An append-only history grows forever. One history document per month keeps each write small, and a year of statistics is still only twelve GETs."""@en ;
    solid-memo:checkedBy <#q-interop-9a> .

<#q-interop-9a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A flashcard app on Solid stores card text, which rarely changes, and review state, which changes every session. Which pod layout fits best?"@en ;
    solid-memo:back "Separate card and review documents, linked from the deck."@en ;
    solid-memo:backNote "Splitting fast- from slow-changing data keeps frequent writes small and leaves the stable data untouched."@en ;
    solid-memo:distractor <#q-interop-9a-d1> ,
                          <#q-interop-9a-d2> ,
                          <#q-interop-9a-d3> .

<#q-interop-9a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "One document per card, holding both its text and its reviews."@en ;
    solid-memo:distractorNote "Each study session rewrites cards and needs one GET per card."@en .

<#q-interop-9a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Everything in one document for the whole pod."@en ;
    solid-memo:distractorNote "Every review rewrites everything and conflicts with any other edit."@en .

<#q-interop-9a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "One review-log document per card, next to the cards."@en ;
    solid-memo:distractorNote "Each session then writes many documents."@en .

<#ch-interop-10>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-interop> ;
    schema:position 9 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Pod layout: discoverability

Other apps, and your app on a new device, must find and recognise your data. Solid Memo follows four rules:

- **A configurable, registered root.** Use a default container such as `<storage>myapp/`, let the user change it, and register it in a type index.
- **A self-describing container.** Put a small document in the container (Solid Memo calls it `myapp/meta.ttl`), saying what it holds. If the registration is lost, an app given the container's URL still recognises the data. It is an ordinary resource your app writes, not the server's `.meta` from Chapter 5.
- **Links over names.** Link documents to each other by URL rather than relying on file names, so files can be renamed or moved.
- **No access rules you don't need.** On WAC, a resource without an ACL inherits its ancestors' rules (Chapter 8); an extra ACL replaces them, so a faulty one can lock the owner out. On ACP, ancestors' member policies keep applying (Step 9.2), so an extra policy adds to them, and since a deny overrides any allow, a careless one can expose data or lock people out.

SAI likewise prefers a "relatively flat hierarchy"."""@en ;
    solid-memo:checkedBy <#q-interop-10a> .

<#q-interop-10a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Your Solid app creates a new container for its data in the user's pod. Should it also write access rules (an ACL or ACR policies) for it?"@en ;
    solid-memo:back "Only if it needs access different from the parent's."@en ;
    solid-memo:backNote "Inheritance already protects the new container. On WAC an extra ACL replaces the inherited rules and a mistake can lock the owner out; on ACP an extra policy adds allows or denies on top, and a mistake can expose data or block access."@en ;
    solid-memo:distractor <#q-interop-10a-d1> ,
                          <#q-interop-10a-d2> ,
                          <#q-interop-10a-d3> .

<#q-interop-10a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Always, because containers without their own rules are public."@en ;
    solid-memo:distractorNote "They inherit their ancestors' rules (WAC) or member policies (ACP)."@en .

<#q-interop-10a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Always, because the server rejects writes without one."@en ;
    solid-memo:distractorNote "Servers don't require an ACL for each resource."@en .

<#q-interop-10a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Never, because apps aren't allowed to write ACLs."@en ;
    solid-memo:distractorNote "Apps with Control may write ACLs; they just shouldn't need to."@en .

<#ch-interop-11>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-interop> ;
    schema:position 10 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Evolving a vocabulary

Step 4.12 covered the vocabulary side: never delete or redefine a term, but deprecate it and name its successor. This step is the app side: what your code does when it meets a deprecated term.

Solid Memo's decks once stated their study direction with `sm:direction`, a string such as `"front-to-back"`. Version 1.6 of its vocabulary deprecated it for `sm:studyDirection`, whose value is a concept from `sm:StudyDirections`, such as `sm:frontToBack`. The values differ, so `dcterms:isReplacedBy` fits: it says only *use this one now*. `owl:equivalentProperty` would claim that old data reads unchanged as the new term, which is false here.

---

An app that meets the old term should:

- **Read both.** Prefer the new term; otherwise read the old one and translate its value. Old pods hold it, and older installs still write it.
- **Write only the new term**, when the user saves that subject.
- **Never strip it on read.** Whether a save may drop the old term depends on whether older readers still need it, which is a format question (Step 11.12). Solid Memo's deck format 3 drops `sm:direction`, and its version bump warns older readers."""@en ;
    solid-memo:checkedBy <#q-interop-11a> ,
                         <#q-interop-11b> .

<#q-interop-11a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Solid Memo's vocabulary deprecated `sm:direction` (a string) for `sm:studyDirection` (a concept). An app reads a deck that has `sm:direction \"front-to-back\"` but no `sm:studyDirection`. What should it do?"@en ;
    solid-memo:back "Fall back to `sm:direction`; write `sm:studyDirection` on save."@en ;
    solid-memo:backNote "A deprecated term lives on in old data. Read it as a fallback, translate its value, and write the new term only when the user saves that subject."@en ;
    solid-memo:distractor <#q-interop-11a-d1> ,
                          <#q-interop-11a-d2> ,
                          <#q-interop-11a-d3> .

<#q-interop-11a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Skip the deck until it is upgraded to `sm:studyDirection`."@en ;
    solid-memo:distractorNote "Old data must stay readable; that is why the term was deprecated, not deleted."@en .

<#q-interop-11a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Read `sm:direction`, and delete it from the pod right away."@en ;
    solid-memo:distractorNote "Reading should never change the pod, and older apps may still rely on the old term."@en .

<#q-interop-11a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Copy the string unchanged into `sm:studyDirection` and save the deck."@en ;
    solid-memo:distractorNote "The new term takes a concept such as `sm:frontToBack`, not the old string."@en .

<#q-interop-11b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In RDF, `ex:nextReview` means exactly what the deprecated `ex:dueDate` meant. Which triple lets a reasoner read old `ex:dueDate` data as `ex:nextReview` data?"@en ;
    solid-memo:back "`ex:dueDate owl:equivalentProperty ex:nextReview`" ;
    solid-memo:backNote "`owl:equivalentProperty` is a claim about meaning, as with `solid:inbox` and `ldp:inbox`. `dcterms:isReplacedBy` only says which term to use now, so it also fits a successor that means something slightly different."@en ;
    solid-memo:distractor <#q-interop-11b-d1> ,
                          <#q-interop-11b-d2> ,
                          <#q-interop-11b-d3> .

<#q-interop-11b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`ex:dueDate dcterms:isReplacedBy ex:nextReview`" ;
    solid-memo:distractorNote "It says to use the new term, not that both mean the same."@en .

<#q-interop-11b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`ex:dueDate owl:deprecated true`" ;
    solid-memo:distractorNote "It marks the old term as obsolete but names no successor."@en .

<#q-interop-11b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`ex:dueDate owl:priorVersion ex:nextReview`" ;
    solid-memo:distractorNote "`owl:priorVersion` links versions of an ontology, not two terms."@en .

<#ch-interop-12>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-interop> ;
    schema:position 11 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Format versions and migrations

The vocabulary says what terms mean; a **format version** says how they are put together. In Solid Memo each subject carries one. Raise it only when an older reader would *misread* the new data. Optional terms an old reader can ignore need no bump. (Solid Memo also picks which shape to validate a subject with by its type and format version.)

- **Reading:** never refuse old data. Migrate it in memory through a chain of steps, one per version. Data *newer* than your app should pass through: read what you understand, never downgrade its version, and keep its unknown triples when you write.
- **Writing:** save in the current format, editing subjects in place so foreign triples survive. Saving one edited subject this way is fine: the user asked for that change, and it touches only that subject.

---

Rewriting the whole pod is different, and is the **user's** decision. Copy the data, upgrade and validate the copy, check the original didn't change meanwhile (compare its ETag, Step 6.11), and switch the type index registration last as the single commit point. The original stays in the pod as a backup."""@en ;
    solid-memo:checkedBy <#q-interop-12a> ,
                         <#q-interop-12b> .

<#q-interop-12a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A Solid flashcard app writes deck format 3 and opens a pod holding format-1 decks. What should it do by default?"@en ;
    solid-memo:back "Migrate them in memory and save the new format only on edit."@en ;
    solid-memo:backNote "In-memory migrations keep the app working without touching the pod. Saving one edited deck changes only what the user chose, while a bulk rewrite changes every deck without asking, so it is the user's call."@en ;
    solid-memo:distractor <#q-interop-12a-d1> ,
                          <#q-interop-12a-d2> ,
                          <#q-interop-12a-d3> .

<#q-interop-12a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Refuse to open them until the user upgrades them."@en ;
    solid-memo:distractorNote "Apps should never refuse older data."@en .

<#q-interop-12a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Rewrite every deck in the pod to the current format on startup."@en ;
    solid-memo:distractorNote "Other apps or older installs may still read format 1, and a bulk rewrite is the user's call."@en .

<#q-interop-12a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Open them read-only so they can never be edited."@en ;
    solid-memo:distractorNote "Edits are fine; they are saved in the current format."@en .

<#q-interop-12b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "When should the format version of a Solid app's data go up?"@en ;
    solid-memo:back "When an older reader would misread the new data."@en ;
    solid-memo:backNote "The version exists to warn readers. Raise it only when ignoring the change would make an old reader get the data wrong."@en ;
    solid-memo:distractor <#q-interop-12b-d1> ,
                          <#q-interop-12b-d2> ,
                          <#q-interop-12b-d3> .

<#q-interop-12b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "With every release of the app that writes the data."@en ;
    solid-memo:distractorNote "Most releases don't change what the data means to readers."@en .

<#q-interop-12b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Whenever an optional property is added."@en ;
    solid-memo:distractorNote "Optional terms an old reader can safely ignore need no bump."@en .

<#q-interop-12b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only when the vocabulary namespace changes."@en ;
    solid-memo:distractorNote "A format can change in ways that break readers without a new namespace."@en .

<#q-interop-r01>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A user moves from Solid recipe app A to recipe app B; the recipes are in the user's pod. What must B do to show A's recipes?"@en ;
    solid-memo:back "Find the recipes through the user's type index, then validate them."@en ;
    solid-memo:backNote "The three agreements work together: the profile and type index give the location, the class gives the meaning, and a shape checks the structure."@en ;
    solid-memo:distractor <#q-interop-r01-d1> ,
                          <#q-interop-r01-d2> ,
                          <#q-interop-r01-d3> .

<#q-interop-r01-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Ask app A's developers for an export, then import it."@en ;
    solid-memo:distractorNote "The data is already in the user's pod; B reads it there."@en .

<#q-interop-r01-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Fetch every document in the pod, then keep the ones that look like recipes."@en ;
    solid-memo:distractorNote "That ignores discovery and is far too slow on a real pod."@en .

<#q-interop-r01-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Use the folder name app A hard-coded, then read it."@en ;
    solid-memo:distractorNote "Hard-coded paths break as soon as an app or user picks another location."@en .

<#q-interop-r02>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "In Solid, what does a type index registration tell another app, and what does a shape (SHACL or ShEx) tell it?"@en ;
    solid-memo:back "The registration says where data is; the shape says how it is structured."@en ;
    solid-memo:backNote "Type indexes map classes to locations and say nothing about shape, which is why apps also need SHACL or ShEx contracts."@en ;
    solid-memo:distractor <#q-interop-r02-d1> ,
                          <#q-interop-r02-d2> ,
                          <#q-interop-r02-d3> .

<#q-interop-r02-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The registration gives access; the shape says where the data is."@en ;
    solid-memo:distractorNote "Registrations don't grant access, and shapes don't locate data."@en .

<#q-interop-r02-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The registration says what the class means; the shape says where it lives."@en ;
    solid-memo:distractorNote "Meaning comes from the vocabulary, location from the index."@en .

<#q-interop-r02-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The registration says which shape data follows; the shape says what the class means."@en ;
    solid-memo:distractorNote "Registrations name a class, not a shape, and meaning comes from the vocabulary."@en .

<#q-interop-r03>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid flashcard app makes two changes to decks: it adds an optional property for tags, and it replaces `sm:direction` with `sm:studyDirection`, dropping the old term from saved decks. Older readers assume front-to-back when a deck has no `sm:direction`. Which change needs a format-version bump?"@en ;
    solid-memo:back "Only the second: older readers would misread the direction."@en ;
    solid-memo:backNote "Deprecation tells developers which term to use; the format version tells readers of the data whether they would get it wrong. An old reader that finds no `sm:direction` assumes front-to-back and studies a bidirectional deck one way only."@en ;
    solid-memo:distractor <#q-interop-r03-d1> ,
                          <#q-interop-r03-d2> ,
                          <#q-interop-r03-d3> .

<#q-interop-r03-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only the first: it adds a term that older readers don't know."@en ;
    solid-memo:distractorNote "An optional term an old reader can ignore needs no bump."@en .

<#q-interop-r03-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Both: each of them changes the vocabulary the decks use."@en ;
    solid-memo:distractorNote "Adding a term doesn't change how old readers read the data."@en .

<#q-interop-r03-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Neither: deprecating `sm:direction` already warns older readers."@en ;
    solid-memo:distractorNote "Deprecation is in the vocabulary; an old app reading the deck just sees the term missing."@en .

<#q-interop-r04>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A user-requested format upgrade of a Solid app's data copies the data, upgrades the copy and switches the type index registration last. Why last?"@en ;
    solid-memo:back "Until the switch, every app still finds the original data."@en ;
    solid-memo:backNote "Switching the registration is a single commit point: if anything fails before it, apps keep using the untouched original."@en ;
    solid-memo:distractor <#q-interop-r04-d1> ,
                          <#q-interop-r04-d2> ,
                          <#q-interop-r04-d3> .

<#q-interop-r04-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Type indexes can only be written after containers."@en ;
    solid-memo:distractorNote "Nothing in the spec fixes that order."@en .

<#q-interop-r04-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The switch deletes the original data automatically."@en ;
    solid-memo:distractorNote "Switching a registration only changes a link; the original stays as a backup."@en .

<#q-interop-r04-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "So the copy can be validated before any other app writes to it."@en ;
    solid-memo:distractorNote "Validation does come before the switch, but the order exists so that one step decides which data apps use."@en .

<#q-interop-r05>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "In Solid app design, why do open shapes and preserving foreign triples on write belong together?"@en ;
    solid-memo:back "Both let several apps add to the same data safely."@en ;
    solid-memo:backNote "An open shape accepts another app's extra triples, and preserving them on write keeps them in the pod, so shared data stays usable by everyone."@en ;
    solid-memo:distractor <#q-interop-r05-d1> ,
                          <#q-interop-r05-d2> ,
                          <#q-interop-r05-d3> .

<#q-interop-r05-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Both make reads faster by skipping unknown properties."@en ;
    solid-memo:distractorNote "They are about coexistence, not speed."@en .

<#q-interop-r05-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Both are required by the Solid Protocol on every write."@en ;
    solid-memo:distractorNote "The Protocol doesn't require shapes, or that clients keep other apps' triples."@en .

<#q-interop-r05-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Both stop other apps from writing to your subjects."@en ;
    solid-memo:distractorNote "They do the opposite: they welcome other apps' additions."@en .

# Chapter 12: Building Solid apps: servers, libraries, workflow.
<#ch-building-apps>
    a solid-memo:Chapter ,
      schema:Syllabus ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <> ;
    schema:position 11 ;
    dcterms:title "Building Solid apps: servers, libraries, workflow"@en ;
    dcterms:description "Choose a pod server and provider to develop against, log users in properly from the browser, pick the right libraries, and debug and test a Solid app. Version numbers are as of October 2026 and will drift."@en ;
    solid-memo:reviewQuestion <#q-building-apps-r01> ,
                              <#q-building-apps-r02> ,
                              <#q-building-apps-r03> ,
                              <#q-building-apps-r04> ,
                              <#q-building-apps-r05> ,
                              <#q-building-apps-r06> ,
                              <#q-building-apps-r07> .

<#ch-building-apps-1>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-building-apps> ;
    schema:position 0 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Pod servers

A pod server implements the Solid Protocol, and the Protocol requires it to support WAC, ACP or both. These are the servers you'll meet (October 2026):

| Server | Notes |
|---|---|
| **Community Solid Server (CSS)** | TypeScript, MIT, v7.2.0 (v8 only as alpha). WAC or ACP; memory, file or SPARQL storage |
| **Node Solid Server (NSS)** | The original server, published on npm as `solid-server`. Still maintained: v6.0.0 shipped in January 2026. WAC, bundles the data browser |
| **Pivot** | A thin wrapper around CSS that runs solidcommunity.net. WAC, quotas |
| **Inrupt ESS** | Enterprise Solid Server, commercial (v3.3). ACP plus Access Grants |
| **Solid-Nextcloud** | A plugin that turns Nextcloud into a pod server and identity provider |
| **JavaScript Solid Server (JSS)** | New in 2026, AGPL, "an early MVP and not production-ready" |

---

CSS is built on **Components.js**, a framework that assembles a program from separate parts listed in a configuration file (this is called dependency injection). Authentication, authorization and storage are modules wired together by JSON configuration files, so you can swap them by changing the config rather than the code. That makes CSS the usual choice for local development and research."""@en ;
    solid-memo:checkedBy <#q-building-apps-1a> ,
                         <#q-building-apps-1b> .

<#q-building-apps-1a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "How can one release of the Community Solid Server (CSS) run with WAC on one machine and ACP on another?"@en ;
    solid-memo:back "Its Components.js config wires in different modules"@en ;
    solid-memo:backNote "CSS is assembled through Components.js dependency injection, so authorization, authentication and storage are chosen in JSON config."@en ;
    solid-memo:distractor <#q-building-apps-1a-d1> ,
                          <#q-building-apps-1a-d2> ,
                          <#q-building-apps-1a-d3> .

<#q-building-apps-1a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Separate builds of CSS are published for each variant"@en ;
    solid-memo:distractorNote "It is one package; the configuration file selects the modules."@en .

<#q-building-apps-1a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Each client picks the mechanism with a request header"@en ;
    solid-memo:distractorNote "The server operator picks the mechanism in configuration, not the client."@en .

<#q-building-apps-1a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It copies the setting from the user's identity provider"@en ;
    solid-memo:distractorNote "Access control is a pod-server setting, unrelated to the identity provider."@en .

<#q-building-apps-1b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "As of 2026, your Solid app's sharing feature works on a Pivot pod (solidcommunity.net). A user whose pod is on Inrupt's Enterprise Solid Server (ESS) tries it. What should you expect to handle?"@en ;
    solid-memo:back "ACP access rules instead of WAC ACL documents"@en ;
    solid-memo:backNote "As of 2026, Pivot uses WAC and ESS uses ACP, so a portable app must handle both access-control systems."@en ;
    solid-memo:distractor <#q-building-apps-1b-d1> ,
                          <#q-building-apps-1b-d2> ,
                          <#q-building-apps-1b-d3> .

<#q-building-apps-1b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "SPARQL queries instead of HTTP document reads"@en ;
    solid-memo:distractorNote "ESS is still a document-based Solid server; neither server needs SPARQL for reads."@en .

<#q-building-apps-1b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Sharing through `acl:trustedApp` entries in the profile"@en ;
    solid-memo:distractorNote "That was a legacy NSS feature, not part of WAC and not used by ESS."@en .

<#q-building-apps-1b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A different patch format, since ESS rejects N3 Patch"@en ;
    solid-memo:distractorNote "Every conforming Solid server must accept N3 Patch; what differs for sharing is the access-control language."@en .

<#ch-building-apps-2>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-building-apps> ;
    schema:position 1 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Pod providers

Most users won't run a server. They sign up with a **pod provider**. solidproject.org lists hosted providers such as solidcommunity.net (run by the ODI), solidweb.org, Data Pod by iGrant.io, use.id, TrinPod and Inrupt's **PodSpaces**. PodSpaces is a **Developer Preview**: "Do not use for production or for storing sensitive/personal data".

---

Providers don't all lay things out the same way. On PodSpaces a WebID looks like `https://id.inrupt.com/alice`, its issuer is `https://login.inrupt.com`, and the pod lives at `https://storage.inrupt.com/{id}`. The **WebID host, the storage host and the identity provider can all differ**. For example, a WebID on `alice.datapod.igrant.io` names `datapod.igrant.io` as its issuer.

So your app must never derive one from another. Read `solid:oidcIssuer` and `pim:storage` from the WebID profile, and fall back to a `Link`-header walk-up for the storage: on CSS 7.2 a fresh profile has no `pim:storage` at all. Test with accounts from more than one provider, because each one's URLs and access control (ACP on PodSpaces, WAC on solidcommunity.net) differ."""@en ;
    solid-memo:checkedBy <#q-building-apps-2a> ,
                         <#q-building-apps-2b> .

<#q-building-apps-2a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A user types the WebID `https://id.inrupt.com/alice` into your Solid app's login form. How should the app find her identity provider (issuer) and her pod storage?"@en ;
    solid-memo:back "Read them from the triples in her WebID profile"@en ;
    solid-memo:backNote "The profile states `solid:oidcIssuer` and `pim:storage`. Guessing them from the WebID's domain fails whenever the hosts differ, as on PodSpaces."@en ;
    solid-memo:distractor <#q-building-apps-2a-d1> ,
                          <#q-building-apps-2a-d2> ,
                          <#q-building-apps-2a-d3> .

<#q-building-apps-2a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Derive both from the domain name in her WebID"@en ;
    solid-memo:distractorNote "The issuer and storage can be on different hosts from the WebID, as on PodSpaces."@en .

<#q-building-apps-2a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Ask the provider's own REST API for the pod address"@en ;
    solid-memo:distractorNote "Solid discovery is done through the profile and `Link` headers, not provider-specific APIs."@en .

<#q-building-apps-2a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Map her WebID's domain to a storage URL with a built-in table"@en ;
    solid-memo:distractorNote "A hard-coded table breaks for any provider or self-hosted server it does not know."@en .

<#q-building-apps-2b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "As of 2026, given its status and the access control it uses, what is an Inrupt PodSpaces account good for while you build a Solid app?"@en ;
    solid-memo:back "Trying out your app against an ACP server"@en ;
    solid-memo:backNote "PodSpaces is a developer preview that uses ACP: a good place to test against ACP, but not for real or sensitive data."@en ;
    solid-memo:distractor <#q-building-apps-2b-d1> ,
                          <#q-building-apps-2b-d2> ,
                          <#q-building-apps-2b-d3> .

<#q-building-apps-2b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Storing a clinic's patient records in production"@en ;
    solid-memo:distractorNote "PodSpaces is a developer preview, not meant for production or sensitive data."@en .

<#q-building-apps-2b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Running your WAC-specific ACL tests on it"@en ;
    solid-memo:distractorNote "PodSpaces uses ACP, so WAC ACL documents do not apply there."@en .

<#q-building-apps-2b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Hosting your app's launch data for its first real users"@en ;
    solid-memo:distractorNote "A developer preview is not for production."@en .

<#ch-building-apps-3>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-building-apps> ;
    schema:position 2 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## The local development loop

Started with no options, CSS keeps everything in memory. Two more start options matter once you build an app:

```sh
# file-backed: data survives restarts in ./data/
npx @solid/community-server@7 -c @css:config/file.json -f data/
# create known accounts and pods at start-up, e.g. in CI
npx @solid/community-server@7 --seedConfig seed.json
```

A seed file is a JSON list of accounts. Each entry needs `email` and `password`; `pods` is optional:

```json
[{ "email": "alice@example.com", "password": "alice123",
   "pods": [{ "name": "alice" }] }]
```

The seeded WebID is `http://localhost:3000/alice/profile/card#me`, with issuer `http://localhost:3000/`. Use `localhost`, never `127.0.0.1`: CSS 7.2 accepts `http` WebIDs only on hosts ending in `localhost`.

---

On CSS 7.2, starting a file-backed, seeded server twice logged:

```text
first start:
  [SeededAccountInitializer] info: Creating account for alice@example.com
  [SeededAccountInitializer] info: Creating pod with name alice
  [SeededAccountInitializer] info: Initialized 1 accounts and 1 pods.
second start, same command:
  [SeededAccountInitializer] info: Creating account for alice@example.com
  [SeededAccountInitializer] warn: Error while initializing seeded account: There already is a login for this e-mail address.
  [SeededAccountInitializer] info: Initialized 0 accounts and 0 pods.
```

An account `bob`, created between the two starts, still answered `200 OK`. In memory, the restart lost bob (`404 Not Found`) and seeding made alice again with a fresh, empty pod, so alice's `200 OK` alone proves nothing.

---

**Docker pitfall.** In a container, CSS's base URL must also resolve *inside* the container: CSS fetches the WebID profile to check the issuer, and if that fails, tokens are silently ignored. Keep the inner and outer ports equal.

To inspect what your app wrote, open the pod in **Penny** or the **SolidOS data browser**."""@en ;
    solid-memo:checkedBy <#q-building-apps-3a> ,
                         <#q-building-apps-3b> .

<#q-building-apps-3a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On Community Solid Server 7.2 (2026), you restart a file-backed server with the same `--seedConfig` file. The log says `Initialized 0 accounts and 0 pods.` What does that mean?"@en ;
    solid-memo:back "The accounts already exist on disk, so seeding skipped them"@en ;
    solid-memo:backNote "Seeding tries to create each listed account at every start. With `file.json` the first run's accounts are still on disk, so CSS logs a warning for each and creates nothing."@en ;
    solid-memo:distractor <#q-building-apps-3a-d1> ,
                          <#q-building-apps-3a-d2> ,
                          <#q-building-apps-3a-d3> .

<#q-building-apps-3a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The seed file is invalid, so the server ignored it"@en ;
    solid-memo:distractorNote "An invalid seed file stops the server with an error."@en .

<#q-building-apps-3a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The restart wiped the pods, and seeding failed to recreate them"@en ;
    solid-memo:distractorNote "File-backed data survives restarts; the accounts were still there."@en .

<#q-building-apps-3a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Seeding only runs on the very first start of a server"@en ;
    solid-memo:distractorNote "It runs on every start; it simply cannot create an account that exists."@en .

<#q-building-apps-3b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Why start a Community Solid Server for your app's tests with `--seedConfig`?"@en ;
    solid-memo:back "So every run begins with the same known accounts and pods"@en ;
    solid-memo:backNote "A seed file creates the listed accounts and pods at start-up, so tests always start from a known state."@en ;
    solid-memo:distractor <#q-building-apps-3b-d1> ,
                          <#q-building-apps-3b-d2> ,
                          <#q-building-apps-3b-d3> .

<#q-building-apps-3b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "So the server copies data in from a production pod"@en ;
    solid-memo:distractorNote "Seeding creates accounts and pods from a JSON file; it imports no remote data."@en .

<#q-building-apps-3b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "So authentication is switched off during the tests"@en ;
    solid-memo:distractorNote "Seeded accounts still log in normally; seeding does not disable auth."@en .

<#q-building-apps-3b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "So the server writes all its data to disk instead of memory"@en ;
    solid-memo:distractorNote "Storage is chosen by the config (`file.json`), not by seeding."@en .

<#ch-building-apps-4>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-building-apps> ;
    schema:position 3 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## A debugging toolkit

Most Solid bugs show up in HTTP headers. Read them with `curl -i` or in the browser's Network panel. On CSS 7.2 an anonymous GET of a fresh pod root answered (excerpt):

```http
HTTP/1.1 200 OK
Access-Control-Expose-Headers: Accept-Patch,Accept-Post,Accept-Put,Allow,Content-Range,ETag,Last-Modified,Link,Location,Updates-Via,WAC-Allow,Www-Authenticate
WAC-Allow: user="read",public="read"
Accept-Post: */*
Link: <http://www.w3.org/ns/pim/space#Storage>; rel="type"
Link: <http://www.w3.org/ns/ldp#Container>; rel="type"
Link: <http://localhost:3000/alice/.meta>; rel="describedby"
Link: <http://localhost:3000/alice/.acl>; rel="acl"
ETag: "1791410637631-text/turtle"
```

The same GET with the owner's token got `user="append control read write"`. Also look for `Accept-Patch`, `ETag` (for `If-Match`), the `describedby` link to the resource's metadata, and `Location` after a POST.

---

Then tell the failures apart:

- **401 or 403** is a response your code can read: "who are you?" versus "I know you, and no".
- **A CORS failure** gives your code no response, only an error; the reason is in the console. Firefox also reports DNS errors and refused connections as "CORS request did not succeed". A header visible in the Network panel but `null` from `res.headers.get()` is missing from `Access-Control-Expose-Headers`.
- **Silently anonymous:** a token was sent, yet the answer is 401 or public data. Read the server log. On CSS 7.2, a pod at `http://127.0.0.1:3001/` answered its owner with `WAC-Allow: user="read"` and logged:

```text
[DPoPWebIdExtractor] warn: Error verifying WebID via DPoP-bound access token: The URI claim could not be verified as secure.
```"""@en ;
    solid-memo:checkedBy <#q-building-apps-4a> ,
                         <#q-building-apps-4b> .

<#q-building-apps-4a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app's request to a pod on another origin gives your code no status code: `fetch()` rejects with `TypeError: NetworkError`. The same request from `curl` gets an answer. What most likely happened?"@en ;
    solid-memo:back "A CORS failure: the browser hid the response"@en ;
    solid-memo:backNote "For security, browsers hide the details of a CORS failure from JavaScript; only the console says what went wrong. 401, 403 and 500 are ordinary responses with a readable status and headers."@en ;
    solid-memo:distractor <#q-building-apps-4a-d1> ,
                          <#q-building-apps-4a-d2> ,
                          <#q-building-apps-4a-d3> .

<#q-building-apps-4a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A 401: the request carried no access token"@en ;
    solid-memo:distractorNote "A 401 is a normal response with a status your code can read."@en .

<#q-building-apps-4a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A 403: the user lacks Read on the resource"@en ;
    solid-memo:distractorNote "A 403 is also a readable response; here your code got none."@en .

<#q-building-apps-4a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A 500: the pod crashed while answering"@en ;
    solid-memo:distractorNote "A 500 still reaches your code as a response with a status."@en .

<#q-building-apps-4b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On Community Solid Server 7.2 (2026), a user logged in through a pod at `http://127.0.0.1:3000/`, and every private request gets 401 although your app sends its access token. Where do you find out why?"@en ;
    solid-memo:back "In the Community Solid Server's log"@en ;
    solid-memo:backNote "CSS 7.2 accepts `http` WebIDs only on hosts ending in `localhost`; with `127.0.0.1` it logs a warning and answers as if no token was sent. Use `localhost`."@en ;
    solid-memo:distractor <#q-building-apps-4b-d1> ,
                          <#q-building-apps-4b-d2> ,
                          <#q-building-apps-4b-d3> .

<#q-building-apps-4b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In the body of the 401 response your app received"@en ;
    solid-memo:distractorNote "CSS treats the request as anonymous; the reason appears only in its log."@en .

<#q-building-apps-4b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In the `WAC-Allow` header of the 401 response"@en ;
    solid-memo:distractorNote "CSS 7.2 sends no `WAC-Allow` on errors, and it would not explain a rejected token."@en .

<#q-building-apps-4b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In the browser console's list of CORS errors"@en ;
    solid-memo:distractorNote "The 401 reached your code; nothing was blocked by CORS."@en .

<#ch-building-apps-5>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-building-apps> ;
    schema:position 4 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Logging in from the browser

`@inrupt/solid-client-authn-browser` (v5) runs the Solid-OIDC login flow for you:

```js
import { login, handleIncomingRedirect, getDefaultSession }
  from "@inrupt/solid-client-authn-browser";

const session = getDefaultSession();
await handleIncomingRedirect();             // on every page load
if (!session.info.isLoggedIn) {
  await login({
    oidcIssuer: issuer,                     // where to log in: see "Two ways in"
    redirectUrl: new URL("/", location.href).toString(),
    clientName: "My application",
    // clientId: "https://myapp.example/id"  // a Client ID Document
  });
}
// from here on, use session.fetch for every pod request
```

---

`login()` navigates away to the identity provider. The user signs in there and is sent back to your `redirectUrl` with a one-time code in the URL. The login completes only when `handleIncomingRedirect()` runs on that page and exchanges the code for tokens. After that, `session.fetch` sends authenticated requests.

So the redirect URL must load your app, with this same script. In a single-page app the simplest choice is the app's own start page, as here; a `/callback` route your host doesn't serve never runs `handleIncomingRedirect()`.

If you pass a `clientId` URL, the identity provider reads your Client ID Document. Without one, the library registers the app dynamically, and `clientName` is just the name shown on the consent screen."""@en ;
    solid-memo:checkedBy <#q-building-apps-5a> ,
                         <#q-building-apps-5b> .

<#q-building-apps-5a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "With `@inrupt/solid-client-authn-browser`, a user logs in at the identity provider and is sent back to your app, but `session.info.isLoggedIn` is still `false`. The page never calls `handleIncomingRedirect()`. What went wrong?"@en ;
    solid-memo:back "Nobody exchanged the returned code for tokens"@en ;
    solid-memo:backNote "The redirect brings back a code. `handleIncomingRedirect()` exchanges it for tokens and marks the session as logged in, so call it on every page load."@en ;
    solid-memo:distractor <#q-building-apps-5a-d1> ,
                          <#q-building-apps-5a-d2> ,
                          <#q-building-apps-5a-d3> .

<#q-building-apps-5a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The identity provider rejected the redirect URL"@en ;
    solid-memo:distractorNote "A rejected redirect URL stops the flow at the provider; here the user did come back."@en .

<#q-building-apps-5a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The app must call `login()` again after returning"@en ;
    solid-memo:distractorNote "Calling `login()` again just sends the user back to the provider."@en .

<#q-building-apps-5a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The pod has not yet granted the app access"@en ;
    solid-memo:distractorNote "Logging in involves only the app and the identity provider; the pod is not asked."@en .

<#q-building-apps-5b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In `@inrupt/solid-client-authn-browser`, you set `clientId: \"https://myapp.example/id\"` in `login()`. What changes compared with only setting `clientName`?"@en ;
    solid-memo:back "The provider fetches your Client ID Document"@en ;
    solid-memo:backNote "With a `clientId` URL the identity provider dereferences that JSON-LD document and checks the `redirect_uri` against it. With only `clientName`, the library registers the app dynamically."@en ;
    solid-memo:distractor <#q-building-apps-5b-d1> ,
                          <#q-building-apps-5b-d2> ,
                          <#q-building-apps-5b-d3> .

<#q-building-apps-5b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The app gets its own WebID separate from the user"@en ;
    solid-memo:distractorNote "A client ID identifies the app to the identity provider; it is not a WebID, and the app still acts for the user."@en .

<#q-building-apps-5b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The pod automatically trusts everything the app does"@en ;
    solid-memo:distractorNote "A Client ID Document proves who controls the redirect URIs, not that the app behaves well."@en .

<#q-building-apps-5b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The user no longer has to consent to the app"@en ;
    solid-memo:distractorNote "The consent screen is still shown; the ID only tells the provider which app is asking."@en .

<#ch-building-apps-6>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-building-apps> ;
    schema:position 5 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Two ways in: coding the login form

A pod accepts a token only if the user's profile lists its issuer, so both entry points are safe, and a good login form offers both.

**WebID first.** Fetch the profile and collect every `solid:oidcIssuer`:

```js
import { getSolidDataset, getThing, getUrlAll } from "@inrupt/solid-client";
const OIDC_ISSUER = "http://www.w3.org/ns/solid/terms#oidcIssuer";

async function issuersOf(webId) {      // profiles are public: plain fetch
  const profile = await getSolidDataset(webId, { fetch });
  const me = getThing(profile, webId);  // null if the WebID isn't in it
  return me ? getUrlAll(me, OIDC_ISSUER) : [];
}
```

`getSolidDataset` reads one RDF document and `getThing` picks out one subject (see "Reading and writing with @inrupt/solid-client"). Then:

- **No issuer:** say the profile names no provider; don't fall back to a default.
- **One issuer:** pass it to `login()` exactly as returned. Don't add or strip a trailing slash: issuer strings are compared exactly.
- **Several issuers:** let the user choose; each is equally trusted.

---

**Issuer first.** Show a few provider buttons **plus a free-text field** for any other issuer URL, and pass the choice as `oidcIssuer`. Without the field, users of unlisted and self-hosted providers are locked out.

Either way, take the WebID from `session.info.webId` after login and continue discovery from its profile. If the user picked a provider their profile doesn't list, login works but pods treat them as anonymous, so check the profile's issuers and explain."""@en ;
    solid-memo:checkedBy <#q-building-apps-6a> ,
                         <#q-building-apps-6b> .

<#q-building-apps-6a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Your Solid app's login page lists three identity providers and logs the user in with the one she picks. Is that \"guessing the issuer\"?"@en ;
    solid-memo:back "No: she chose it, and the pod checks it against her profile"@en ;
    solid-memo:backNote "Starting from a provider list is fine. The token is accepted only if the user's own profile lists that issuer, so a wrong choice just fails."@en ;
    solid-memo:distractor <#q-building-apps-6a-d1> ,
                          <#q-building-apps-6a-d2> ,
                          <#q-building-apps-6a-d3> .

<#q-building-apps-6a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Yes: a Solid login must always start from the WebID"@en ;
    solid-memo:distractorNote "Issuer-first login is legitimate; only deriving or assuming the issuer is guessing."@en .

<#q-building-apps-6a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "No, but only if the Solid project has approved the list"@en ;
    solid-memo:distractorNote "There is no approved list; safety comes from the pod's check against the profile."@en .

<#q-building-apps-6a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Yes, unless the app reads her WebID profile before the redirect"@en ;
    solid-memo:distractorNote "The app learns her WebID after login; the pod's check is what makes it safe."@en .

<#q-building-apps-6b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In a Solid app's WebID-first login, a user types her WebID and her profile lists two `solid:oidcIssuer` values. What should your code do?"@en ;
    solid-memo:back "Ask her which of the two to log in with"@en ;
    solid-memo:backNote "Every issuer the profile lists can log her in, and only she knows which account she uses, so let her choose."@en ;
    solid-memo:distractor <#q-building-apps-6b-d1> ,
                          <#q-building-apps-6b-d2> ,
                          <#q-building-apps-6b-d3> .

<#q-building-apps-6b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Use the first one, since the profile lists it first"@en ;
    solid-memo:distractorNote "RDF triples have no order; \"first\" is just whatever the parser returned."@en .

<#q-building-apps-6b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Refuse to log in until the profile lists only one"@en ;
    solid-memo:distractorNote "Several issuers are allowed; the pod trusts each of them."@en .

<#q-building-apps-6b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Pick the one on the same host as her WebID"@en ;
    solid-memo:distractorNote "That is guessing the issuer from the domain, which breaks whenever the hosts differ."@en .

<#ch-building-apps-7>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-building-apps> ;
    schema:position 6 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Sessions: restore, refresh and expiry

The browser library keeps tokens **only in memory**, so a page reload logs the user out; tokens kept in storage could be stolen by injected scripts. Pass `restorePreviousSession: true` to `handleIncomingRedirect()`: it does a silent redirect to the provider and brings the user back logged in if the provider session is alive.

While the page stays open, tokens renew themselves. The library asks for `offline_access`, so the provider also issues a **refresh token**, and shortly before the access token expires the library silently gets a new one. On CSS 7.2 a browser login's access token lasted 3600 s and came with a refresh token, because "Remember this client" was left ticked on CSS's consent page; untick it and no refresh token is issued, so the session ends after an hour.

---

`session.info.expirationDate` says when the current token ends. If a refresh fails, or no refresh token was issued, the library fires `sessionExpired` and logs out locally. From then on `session.fetch` sends **anonymous** requests, so private resources answer 401. Listen for the event:

```js
import { EVENTS } from "@inrupt/solid-client-authn-browser";
session.events.on(EVENTS.SESSION_EXPIRED, () => showLoginPrompt());
```

Never retry a 401 in a loop: try one silent restore, then ask the user to log in. After a reload, `restorePreviousSession` does it. After `sessionExpired`, authn-browser 5.0.1 has already forgotten the session, so your app makes the silent attempt itself: call `login({ oidcIssuer, redirectUrl, prompt: "none" })` (`prompt` is passed through although 5.0.1's typings omit it)."""@en ;
    solid-memo:checkedBy <#q-building-apps-7a> ,
                         <#q-building-apps-7b> .

<#q-building-apps-7a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A user reloads your Solid app's page and appears logged out. The app uses `@inrupt/solid-client-authn-browser`. What is the reason, and the intended fix (v5, 2026)?"@en ;
    solid-memo:back "Tokens are memory-only; use `restorePreviousSession`"@en ;
    solid-memo:backNote "The browser library keeps tokens in memory for security. `restorePreviousSession: true` silently re-authenticates if the identity provider still has a session."@en ;
    solid-memo:distractor <#q-building-apps-7a-d1> ,
                          <#q-building-apps-7a-d2> ,
                          <#q-building-apps-7a-d3> .

<#q-building-apps-7a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The DPoP key expired; ask the pod for a new key"@en ;
    solid-memo:distractorNote "DPoP keys are made by the client and the pod issues none; the tokens were simply lost from memory."@en .

<#q-building-apps-7a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The pod revoked access; reapply the ACL rules"@en ;
    solid-memo:distractorNote "Nothing was revoked; the in-memory tokens disappeared with the page."@en .

<#q-building-apps-7a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "localStorage was cleared; store tokens yourself"@en ;
    solid-memo:distractorNote "The library avoids persistent storage on purpose, because injected scripts could steal tokens kept there."@en .

<#q-building-apps-7b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In a Solid app using `@inrupt/solid-client-authn-browser` (v5, 2026), a token refresh failed and the app received `sessionExpired`. Saving a note now returns 401, although the code uses `session.fetch`. What should the app do?"@en ;
    solid-memo:back "Try one silent restore, then ask the user to log in"@en ;
    solid-memo:backNote "Once a refresh fails, the library logs out locally and `session.fetch` goes anonymous, so retries cannot succeed. Try one silent restore, then send the user to log in."@en ;
    solid-memo:distractor <#q-building-apps-7b-d1> ,
                          <#q-building-apps-7b-d2> ,
                          <#q-building-apps-7b-d3> .

<#q-building-apps-7b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Reapply the ACL rules, since the user's access was revoked"@en ;
    solid-memo:distractorNote "Missing permission gives 403 to a logged-in user; 401 means no valid token arrived."@en .

<#q-building-apps-7b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Retry the save until the server accepts it"@en ;
    solid-memo:distractorNote "The request is now anonymous, so every retry gets 401 again."@en .

<#q-building-apps-7b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Wait for the library's next automatic refresh"@en ;
    solid-memo:distractorNote "After `sessionExpired` the library has logged out locally; nothing more is refreshed."@en .

<#ch-building-apps-8>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-building-apps> ;
    schema:position 7 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Logout, and surviving the login redirect

Logout has two levels:

```js
await session.logout({ logoutType: "app" }); // forget the session here
await session.logout({ logoutType: "idp", postLogoutUrl }); // also at the provider
```

After app logout, the provider session lives on, so the next login needs no password. Provider logout (OpenID "RP-initiated logout") sends the browser to the provider's `end_session_endpoint`, which ends that session and returns to `postLogoutUrl`; it must be listed in the Client ID Document's `post_logout_redirect_uris`.

⚠ On CSS 7.2 the next login still skipped the password after provider logout, because CSS's account page keeps its own `css-account` cookie until the user logs out there too.

---

`login()` and a silent restore both leave the page, and memory goes with it. So save what the user would miss, the current route and unsaved edits (never tokens), in `sessionStorage` first, and put it back on return. This is an app pattern: the library itself only hands back the previous URL, in its `sessionRestore` event.

```js
function logIn(issuer) {
  sessionStorage.setItem("pending",
    JSON.stringify({ route: location.hash, draft: editor.value }));
  return login({ oidcIssuer: issuer, redirectUrl: new URL("/", location.href).toString() });
}
// on every page load:
await handleIncomingRedirect({ restorePreviousSession: true });
const pending = JSON.parse(sessionStorage.getItem("pending") ?? "null");
if (pending) {
  sessionStorage.removeItem("pending");
  location.hash = pending.route; editor.value = pending.draft;
}
```"""@en ;
    solid-memo:checkedBy <#q-building-apps-8a> ,
                         <#q-building-apps-8b> .

<#q-building-apps-8a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A user has typed a long note in your Solid app when it sends her to the identity provider to log in. How do you keep the note?"@en ;
    solid-memo:back "Save it in `sessionStorage`, restore it after login"@en ;
    solid-memo:backNote "The login redirect unloads your page. `sessionStorage` survives it within the same tab, so save the route and draft there and restore them once `handleIncomingRedirect()` has run."@en ;
    solid-memo:distractor <#q-building-apps-8a-d1> ,
                          <#q-building-apps-8a-d2> ,
                          <#q-building-apps-8a-d3> .

<#q-building-apps-8a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Keep it in a JavaScript variable until she returns"@en ;
    solid-memo:distractorNote "`login()` leaves the page, and memory goes with it."@en .

<#q-building-apps-8a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Save it to her pod first, then send her to log in"@en ;
    solid-memo:distractorNote "She is not logged in yet, so the pod would refuse the write."@en .

<#q-building-apps-8a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Put it in `redirectUrl` so it comes back to you"@en ;
    solid-memo:distractorNote "URLs end up in logs and history, and redirect URLs must match exactly."@en .

<#q-building-apps-8b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On a shared computer, a user clicks \"Log out\" in a Solid app, which calls `logout({ logoutType: \"app\" })`. The next person clicks \"Log in\" and is in her account without typing a password. Why?"@en ;
    solid-memo:back "Her provider session is still alive"@en ;
    solid-memo:backNote "App logout forgets the session in your app only; offer provider logout (`logoutType: \"idp\"`) to end it at the provider too. ⚠ On CSS 7.2 (2026) the password returned only after she also logged out on its account page."@en ;
    solid-memo:distractor <#q-building-apps-8b-d1> ,
                          <#q-building-apps-8b-d2> ,
                          <#q-building-apps-8b-d3> .

<#q-building-apps-8b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The library kept her tokens in localStorage"@en ;
    solid-memo:distractorNote "The library keeps tokens in memory only, and app logout cleared them."@en .

<#q-building-apps-8b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The pod remembered her from her last request"@en ;
    solid-memo:distractorNote "Pods check each request's token; they hold no login session."@en .

<#q-building-apps-8b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Her DPoP key was still cached with the page"@en ;
    solid-memo:distractorNote "A key alone is no login; the provider issued fresh tokens."@en .

<#ch-building-apps-9>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-building-apps> ;
    schema:position 8 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Hosting a Client ID Document

A Client ID Document describes your app to identity providers. Hosting one has four rules:

1. **Its URL is the `client_id`** you pass to `login()`. Serve it over HTTPS, with `client_id` inside set to exactly that URL.
2. **Serve JSON-LD:** `Content-Type: application/ld+json`, with the context `https://www.w3.org/ns/solid/oidc-context.jsonld`.
3. **List redirect URIs exactly.** Providers compare a `redirect_uri` with `redirect_uris` as exact strings, so `/callback` and `/callback/` differ. Add `post_logout_redirect_uris` for provider logout.
4. **Keep it reachable.** Providers fetch it at login, so while it is down nobody can log in.

⚠ CSS 7.2 keeps no copy and can fetch it again at every lookup, which normally includes silent restores and token refreshes, so there an outage can also end each session at its next refresh (within the access token's 3600 s). Other providers may cache it.

---

On CSS 7.2, a login with a `redirect_uri` the document didn't list was refused before any token existed:

```text
400 {"name":"InvalidRedirectUri","message":"invalid_redirect_uri", …}
```

**Local development.** The spec requires HTTPS, and a hosted provider cannot reach your `localhost`. So develop with `clientName` (dynamic registration), and switch to the Client ID Document when you deploy.

⚠ CSS 7.2 also accepts an `http://localhost` client ID such as `http://localhost:5173/id.jsonld`, but answers an `http://127.0.0.1` client ID with a 500 error ("SSL is required for client_id authentication unless working locally.")."""@en ;
    solid-memo:checkedBy <#q-building-apps-9a> ,
                         <#q-building-apps-9b> .

<#q-building-apps-9a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app's Client ID Document lists `https://notes.example/callback`, but the app calls `login()` with `redirectUrl: \"https://notes.example/callback/\"`. What happens?"@en ;
    solid-memo:back "The provider refuses the login: the URIs don't match"@en ;
    solid-memo:backNote "The provider dereferences the client ID and accepts only a `redirect_uri` listed in `redirect_uris`, character for character."@en ;
    solid-memo:distractor <#q-building-apps-9a-d1> ,
                          <#q-building-apps-9a-d2> ,
                          <#q-building-apps-9a-d3> .

<#q-building-apps-9a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It works, because providers ignore a trailing slash"@en ;
    solid-memo:distractorNote "Redirect URIs are compared as exact strings."@en .

<#q-building-apps-9a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It works: the library registers the app again"@en ;
    solid-memo:distractorNote "With a `clientId`, the provider checks the published document."@en .

<#q-building-apps-9a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Login succeeds, but the pod rejects the token later"@en ;
    solid-memo:distractorNote "The check happens at the provider, before any token exists."@en .

<#q-building-apps-9b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "You are developing a Solid app at `http://localhost:5173` and want logins to work with any identity provider. What is the simplest setup?"@en ;
    solid-memo:back "Pass `clientName` and let the library register dynamically"@en ;
    solid-memo:backNote "Dynamic registration needs no hosted document, so it works with every provider during local work. Switch to the Client ID Document when the app is deployed over HTTPS."@en ;
    solid-memo:distractor <#q-building-apps-9b-d1> ,
                          <#q-building-apps-9b-d2> ,
                          <#q-building-apps-9b-d3> .

<#q-building-apps-9b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Pass `clientId: \"file:///home/me/app/id.json\"` to `login()`"@en ;
    solid-memo:distractorNote "A provider fetches the client ID over the web; it cannot read a file on your disk."@en .

<#q-building-apps-9b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Reuse the production `clientId` while developing locally"@en ;
    solid-memo:distractorNote "Its `redirect_uris` list the production site, so a localhost redirect is refused."@en .

<#q-building-apps-9b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Skip `login()` and read the pod with the global `fetch`"@en ;
    solid-memo:distractorNote "That sends anonymous requests, which see only public data."@en .

<#ch-building-apps-10>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-building-apps> ;
    schema:position 9 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Reading and writing with @inrupt/solid-client

`@inrupt/solid-client` (v4) models an RDF document as a **SolidDataset** and one subject inside it as a **Thing**. Both are **immutable**: every setter returns a *new* object, and nothing reaches the pod until you save.

```js
import { getSolidDataset, getThing, setStringNoLocale, setThing,
  saveSolidDatasetAt } from "@inrupt/solid-client";

const NAME = "http://schema.org/name";      // a predicate is just an IRI
let ds = await getSolidDataset(url, { fetch: session.fetch });   // read
let card = getThing(ds, `${url}#card1`);  // null if the Thing isn't in the document
card = setStringNoLocale(card, NAME, "Bonjour");                  // new Thing
ds = setThing(ds, card);                                          // new dataset
await saveSolidDatasetAt(url, ds, { fetch: session.fetch });      // write
```

Change the Thing, put it back with `setThing`, then save. Skip `setThing` and the change is silently lost. If the document has no `#card1`, the setter throws `Expected a Thing, but received: [null].`, so check for `null` first and create a missing Thing with `createThing`.

---

Notice `{ fetch: session.fetch }` on every call that talks to the pod. The browser's built-in `fetch` is not authenticated. Leave the option out, or pass the global `fetch` by mistake, and the library sends anonymous requests that see only public data: a classic beginner bug.

For sharing, use the library's universal access API, and check what `universalAccess.setAgentAccess` returns: on CSS 7.2 with ACP, for a resource with no ACR yet, it returned `null` and shared nothing."""@en ;
    solid-memo:checkedBy <#q-building-apps-10a> ,
                         <#q-building-apps-10b> .

<#q-building-apps-10a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front """This `@inrupt/solid-client` (v4) code runs without error, but the pod never changes. What is missing?

```js
let ds = await getSolidDataset(url, { fetch: session.fetch });
let card = getThing(ds, `${url}#card1`);
card = setStringNoLocale(card, "http://schema.org/name", "Bonjour");
await saveSolidDatasetAt(url, ds, { fetch: session.fetch });
```"""@en ;
    solid-memo:back "Putting the changed Thing back with `setThing`"@en ;
    solid-memo:backNote "Setters return new immutable objects, so the dataset saved here still holds the original Thing. `ds = setThing(ds, card)` fixes it."@en ;
    solid-memo:distractor <#q-building-apps-10a-d1> ,
                          <#q-building-apps-10a-d2> ,
                          <#q-building-apps-10a-d3> .

<#q-building-apps-10a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A call that commits the Thing to the pod directly"@en ;
    solid-memo:distractorNote "Things are saved only as part of a dataset; the dataset still holds the old Thing."@en .

<#q-building-apps-10a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A `fetch` option on the `setStringNoLocale` call"@en ;
    solid-memo:distractorNote "Setters work locally and need no fetch; only reads and saves talk to the pod."@en .

<#q-building-apps-10a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Reloading the dataset before saving it again"@en ;
    solid-memo:distractorNote "Reloading would only fetch the unchanged data; the edit must be placed into the dataset."@en .

<#q-building-apps-10b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A logged-in user's private document returns 401 when your Solid app calls `getSolidDataset(url)` from `@inrupt/solid-client` (v4). What is the most likely cause?"@en ;
    solid-memo:back "The session's `fetch` was not passed to the call"@en ;
    solid-memo:backNote "Without `{ fetch: session.fetch }` the request is anonymous, so private resources answer 401."@en ;
    solid-memo:distractor <#q-building-apps-10b-d1> ,
                          <#q-building-apps-10b-d2> ,
                          <#q-building-apps-10b-d3> .

<#q-building-apps-10b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`getSolidDataset` can only read public documents"@en ;
    solid-memo:distractorNote "It reads private documents when given an authenticated fetch."@en .

<#q-building-apps-10b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The user lacks Read access to the document"@en ;
    solid-memo:distractorNote "That would give 403 to an authenticated request; 401 means no valid credentials reached the server."@en .

<#q-building-apps-10b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The user has to log in again before every request"@en ;
    solid-memo:distractorNote "One login serves many requests through the session's fetch."@en .

<#ch-building-apps-11>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-building-apps> ;
    schema:position 10 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Other libraries and how to choose

Most JavaScript RDF libraries implement **RDF/JS**, shared interfaces for terms, `Quad` and `DatasetCore`, so quads from N3.js, rdf-ext or Comunica can pass between them. The ones this course uses, as of October 2026:

| Need | Good fit |
|---|---|
| Browser login | `@inrupt/solid-client-authn-browser` 5.0 |
| CRUD on Things | `@inrupt/solid-client` 4.0 |
| Types from ShEx shapes, React hooks | **LDO** (`@ldo/connected-solid`, 1.0.0-alpha) |
| Parsing, writing, an in-memory store | **N3.js** |
| SPARQL over pod documents | **Comunica** 5.x |

---

Others you'll meet: **Soukai** (models that save themselves, with offline sync) and **LDkit** (a typed schema that generates SPARQL).

Install LDO's Solid support as `@ldo/connected-solid`; `@ldo/solid` stopped at 1.0.0-alpha.1 (March 2025). LDO is used in the official "first Solid app" guide, and its CLI turns a ShEx shape into TypeScript types. If you build on SolidOS, use **rdflib.js**, the oldest Solid library and the base of SolidOS."""@en ;
    solid-memo:checkedBy <#q-building-apps-11a> ,
                         <#q-building-apps-11b> .

<#q-building-apps-11a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "You are starting a React Solid app and want TypeScript types generated from the ShEx shapes in your data contract. Which library fits best (2026)?"@en ;
    solid-memo:back "LDO, which generates types from ShEx shapes"@en ;
    solid-memo:backNote "LDO's CLI generates TypeScript from ShEx shapes, and it offers React hooks for loading data. Install it through `@ldo/connected-solid`."@en ;
    solid-memo:distractor <#q-building-apps-11a-d1> ,
                          <#q-building-apps-11a-d2> ,
                          <#q-building-apps-11a-d3> .

<#q-building-apps-11a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "N3.js, which turns Turtle into typed classes"@en ;
    solid-memo:distractorNote "N3.js parses and writes RDF into quads; it generates no types from shapes."@en .

<#q-building-apps-11a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "rdflib.js, which builds types from its store"@en ;
    solid-memo:distractorNote "rdflib.js is a quad store and fetcher; it does not generate types from shapes."@en .

<#q-building-apps-11a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Comunica, which infers types from SPARQL queries"@en ;
    solid-memo:distractorNote "Comunica is a query engine; it does not generate TypeScript types."@en .

<#q-building-apps-11b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Why does it matter that the JavaScript libraries N3.js, rdf-ext and Comunica all implement RDF/JS?"@en ;
    solid-memo:back "Their quads and terms can be passed between them"@en ;
    solid-memo:backNote "RDF/JS defines common interfaces such as `Quad` and `DatasetCore`, so data parsed by one library can be stored or queried by another."@en ;
    solid-memo:distractor <#q-building-apps-11b-d1> ,
                          <#q-building-apps-11b-d2> ,
                          <#q-building-apps-11b-d3> .

<#q-building-apps-11b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "They all reach pods through the same SPARQL endpoint"@en ;
    solid-memo:distractorNote "Pods have no SPARQL endpoint; RDF/JS is about in-code data interfaces."@en .

<#q-building-apps-11b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "They all share one common login session automatically"@en ;
    solid-memo:distractorNote "RDF/JS defines data structures, not authentication."@en .

<#q-building-apps-11b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "They can all validate data against SHACL shapes"@en ;
    solid-memo:distractorNote "RDF/JS covers terms, quads and datasets, not validation."@en .

<#ch-building-apps-12>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-building-apps> ;
    schema:position 11 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Querying pods client-side

**A pod is not a SPARQL endpoint.** The Solid Protocol serves documents over HTTP and requires no query service. To query, the client fetches documents and runs SPARQL over them itself.

**Comunica** is the reference client-side engine. `@comunica/query-sparql` takes document URLs as `sources`, and you pass the authenticated `fetch` to reach private data:

```js
import { QueryEngine } from "@comunica/query-sparql";
const engine = new QueryEngine();
const query = "SELECT ?name WHERE { ?card <http://schema.org/name> ?name }";
const stream = await engine.queryBindings(query,
  { sources: [deckUrl], fetch: session.fetch });
const rows = await stream.toArray();
rows.forEach((b) => console.log(b.get("name").value));
```

---

If you don't know in advance which documents hold the data, `@comunica/query-sparql-link-traversal-solid` follows links *during* the query. From a WebID it can follow `pim:storage` and then `ldp:contains` through the containers, or follow the type indexes to just the registered documents. Using the type index takes far fewer requests than walking every container. Either way, traversal finds only documents that some link leads to. It is experimental, with answers "in the order of seconds for non-complex queries"."""@en ;
    solid-memo:checkedBy <#q-building-apps-12a> ,
                         <#q-building-apps-12b> .

<#q-building-apps-12a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "How do you run a SPARQL query over data in a user's Solid pod?"@en ;
    solid-memo:back "Fetch the documents and run the query on the client"@en ;
    solid-memo:backNote "A pod serves documents, so an engine such as Comunica fetches them with the authenticated `fetch` and evaluates SPARQL locally."@en ;
    solid-memo:distractor <#q-building-apps-12a-d1> ,
                          <#q-building-apps-12a-d2> ,
                          <#q-building-apps-12a-d3> .

<#q-building-apps-12a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "POST the query to the pod's `/sparql` endpoint over HTTP"@en ;
    solid-memo:distractorNote "The Solid Protocol defines no query endpoint; any such feature is server-specific."@en .

<#q-building-apps-12a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Put the query into an N3 Patch `where` clause"@en ;
    solid-memo:distractorNote "N3 Patch changes one document; it does not return query results."@en .

<#q-building-apps-12a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Ask the identity provider to run it on the pod"@en ;
    solid-memo:distractorNote "The identity provider issues tokens and does not query pod data."@en .

<#q-building-apps-12b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A link-traversal SPARQL query (Comunica) must find a user's notes in a large Solid pod. Which links should it follow to need the fewest requests?"@en ;
    solid-memo:back "The type index registrations for the notes class"@en ;
    solid-memo:backNote "A type registration points straight at the container or documents holding a class, so traversal reads far fewer documents than a walk through every container."@en ;
    solid-memo:distractor <#q-building-apps-12b-d1> ,
                          <#q-building-apps-12b-d2> ,
                          <#q-building-apps-12b-d3> .

<#q-building-apps-12b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`ldp:contains` from the storage root through every container"@en ;
    solid-memo:distractorNote "That finds the notes too, but only after reading every container."@en .

<#q-building-apps-12b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The `acl` links of every resource in the pod"@en ;
    solid-memo:distractorNote "ACL documents hold access rules, not pointers to the data."@en .

<#q-building-apps-12b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The issuer named in the user's WebID profile"@en ;
    solid-memo:distractorNote "The identity provider holds no pod data to traverse."@en .

<#ch-building-apps-13>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-building-apps> ;
    schema:position 12 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Testing for interoperability

Test at four levels.

**Your logic, without a pod.** Put pod access behind a **port**, an interface your own code defines and calls, such as `loadDeck(url)`, and unit-test against an in-memory fake that implements it. Solid Memo keeps its domain and use cases free of Solid code this way.

**The real login.** Start a local server with known accounts, seeded or created through CSS's account API, and let a browser-automation tool fill in the provider's login form. As of 2026, Solid Memo runs such journeys in CI with Playwright against CSS 7, creating a fresh account, pod and WebID for each.

---

**The server.** The **Conformance Test Harness** (CTH) runs the community's spec tests with two users, alice and bob, and reports in **EARL**, a W3C RDF vocabulary for test results. It tells you how well a *server* follows the specs, not whether your app works.

**Your app on many servers.** Servers differ in PATCH handling, paths and concurrent writes. Run your end-to-end suite against several in Docker (CSS, NSS, Solid-Nextcloud, JSS), and keep a per-server list of expected failures so a known deviation doesn't hide a new regression."""@en ;
    solid-memo:checkedBy <#q-building-apps-13a> ,
                         <#q-building-apps-13b> .

<#q-building-apps-13a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "What does the Solid Conformance Test Harness (CTH) tell you?"@en ;
    solid-memo:back "How well a pod server follows the Solid specs"@en ;
    solid-memo:backNote "CTH runs the specification tests (with users alice and bob) against a server and reports the results in EARL."@en ;
    solid-memo:distractor <#q-building-apps-13a-d1> ,
                          <#q-building-apps-13a-d2> ,
                          <#q-building-apps-13a-d3> .

<#q-building-apps-13a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Whether your app's user interface works in browsers"@en ;
    solid-memo:distractorNote "CTH tests servers over HTTP; it does not exercise app UIs."@en .

<#q-building-apps-13a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Whether your RDF data conforms to your SHACL shapes"@en ;
    solid-memo:distractorNote "That is data validation; CTH checks server behaviour against the specs."@en .

<#q-building-apps-13a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "How quickly a server answers under heavy load"@en ;
    solid-memo:distractorNote "CTH checks conformance, not performance."@en .

<#q-building-apps-13b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Your Solid app's end-to-end tests all pass against the Community Solid Server (CSS). What can you conclude?"@en ;
    solid-memo:back "It works on CSS; run the suite on other servers too"@en ;
    solid-memo:backNote "\"Works on my pod\" is not \"works on Solid\". Run the same suite against several servers and track expected failures per server."@en ;
    solid-memo:distractor <#q-building-apps-13b-d1> ,
                          <#q-building-apps-13b-d2> ,
                          <#q-building-apps-13b-d3> .

<#q-building-apps-13b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It works on every Solid server, since all follow one spec"@en ;
    solid-memo:distractorNote "Servers deviate in practice, so passing on one doesn't prove it works on the others."@en .

<#q-building-apps-13b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It needs no more testing once CSS has passed CTH"@en ;
    solid-memo:distractorNote "CTH tests the server's conformance, not your app's behaviour on other servers."@en .

<#q-building-apps-13b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It is proven correct for ACP pods as well as WAC"@en ;
    solid-memo:distractorNote "A CSS instance runs one configuration, usually WAC; ACP servers need their own runs."@en .

<#ch-building-apps-14>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-building-apps> ;
    schema:position 13 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Learning from real apps

Other apps' code and data show how the conventions work in practice.

- **Media Kraken** tracks your movies: search them, collect them, mark them as watched. It is an offline-first web app built with Vue and Soukai.
- **Umai** manages recipes local-first: you can use it in the browser before connecting a pod, and it syncs later. It stores recipes with schema.org's `Recipe` vocabulary, and accepts both `http://` and `https://schema.org` IRIs because other data uses either.
- **SolidOS** shows any RDF it meets through **panes**: viewers and editors chosen by the type of the data, such as profile, contacts, chat or folder.

---

Media Kraken and Umai are open source (GPLv3). In October 2026, Umai v0.1.13 on a CSS 7.2 pod linked `solid:privateTypeIndex` straight from the public profile (no preferences file) and wrote:

```turtle
# settings/privateTypeIndex
<#8a902a3a-7dd2-458a-9173-880d38d1519e> a <http://www.w3.org/ns/solid/terms#TypeRegistration>;
    <http://www.w3.org/ns/solid/terms#forClass> <https://schema.org/Recipe>;
    <http://www.w3.org/ns/solid/terms#instanceContainer> <http://localhost:4030/alice/cookbook/>.
# cookbook/pancakes
<#it> a <https://schema.org/Recipe>;
    <https://schema.org/name> "Pancakes".
```

Both documents answered `401` without a token: the link to the index is public, but the index and recipes stay private, so another app reads them only while the user (alice) is logged in."""@en ;
    solid-memo:checkedBy <#q-building-apps-14a> ,
                         <#q-building-apps-14b> .

<#q-building-apps-14a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "You want your Solid app to show the recipes a user saved with Umai, another Solid app. What must your app agree on with Umai?"@en ;
    solid-memo:back "Where the data is, its vocabulary and shape"@en ;
    solid-memo:backNote "Apps interoperate by agreeing on discovery, vocabulary and shape, not on code."@en ;
    solid-memo:distractor <#q-building-apps-14a-d1> ,
                          <#q-building-apps-14a-d2> ,
                          <#q-building-apps-14a-d3> .

<#q-building-apps-14a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An API key issued by Umai's developer"@en ;
    solid-memo:distractorNote "The data is in the user's pod; Umai runs no API in between."@en .

<#q-building-apps-14a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The same RDF library as Umai, Soukai, for reading"@en ;
    solid-memo:distractorNote "Any RDF library reads the same triples; the library is not part of the contract."@en .

<#q-building-apps-14a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A login session shared with Umai"@en ;
    solid-memo:distractorNote "Each app logs the user in itself; the pod checks each one's token."@en .

<#q-building-apps-14b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "What decides which SolidOS pane displays a resource in the Solid data browser?"@en ;
    solid-memo:back "The type of the data in the resource"@en ;
    solid-memo:backNote "Panes are viewers and editors chosen by the kind of data, which is why one generic tool can show many apps' data."@en ;
    solid-memo:distractor <#q-building-apps-14b-d1> ,
                          <#q-building-apps-14b-d2> ,
                          <#q-building-apps-14b-d3> .

<#q-building-apps-14b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The app that originally wrote the resource"@en ;
    solid-memo:distractorNote "SolidOS does not track the writing app; it looks at the data."@en .

<#q-building-apps-14b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The file extension in the resource's URL"@en ;
    solid-memo:distractorNote "Panes are chosen by the data's type, not by its URL."@en .

<#q-building-apps-14b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A setting in the pod server's configuration"@en ;
    solid-memo:distractorNote "The data browser picks panes itself, on any server."@en .

<#q-building-apps-r01>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your Solid app works on a local Community Solid Server, but fails for an Inrupt PodSpaces user as soon as she logs in. Which two differences should you check first?"@en ;
    solid-memo:back "Issuer and storage on other hosts, and ACP instead of WAC"@en ;
    solid-memo:backNote "A local CSS often puts WebID, issuer and storage on one host and uses WAC. PodSpaces puts WebIDs on `id.inrupt.com`, the issuer on `login.inrupt.com` and pods on `storage.inrupt.com`, and uses ACP."@en ;
    solid-memo:distractor <#q-building-apps-r01-d1> ,
                          <#q-building-apps-r01-d2> ,
                          <#q-building-apps-r01-d3> .

<#q-building-apps-r01-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "PodSpaces requires a Client ID Document, and N3 Patch"@en ;
    solid-memo:distractorNote "Dynamic registration works there too, and every Solid server takes N3 Patch."@en .

<#q-building-apps-r01-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "PodSpaces has no identity provider, and it allows no writes"@en ;
    solid-memo:distractorNote "PodSpaces has an issuer and writable storage; they are just on different hosts."@en .

<#q-building-apps-r01-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Your CSS ran over HTTP, and PodSpaces forbids DPoP"@en ;
    solid-memo:distractorNote "DPoP is part of Solid-OIDC on every server; the differences are hosts and access control."@en .

<#q-building-apps-r02>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A CI job for a Solid app must start a fresh pod server and run end-to-end tests that log in through a real browser, the way users do. Which setup fits?"@en ;
    solid-memo:back "A fresh local CSS with known accounts, and browser automation"@en ;
    solid-memo:backNote "Seeding, or creating accounts through the account API, gives known accounts on every run, and browser automation drives the provider's real login page. Fakes belong to unit tests behind a port."@en ;
    solid-memo:distractor <#q-building-apps-r02-d1> ,
                          <#q-building-apps-r02-d2> ,
                          <#q-building-apps-r02-d3> .

<#q-building-apps-r02-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A shared PodSpaces account that someone resets by hand each run"@en ;
    solid-memo:distractorNote "A developer-preview account shared across runs gives neither a fresh state nor automation."@en .

<#q-building-apps-r02-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A file-backed CSS whose data folder is never cleared"@en ;
    solid-memo:distractorNote "Leftover data from earlier runs means tests don't start from a known state."@en .

<#q-building-apps-r02-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A fake pod in memory, so that no login is needed at all"@en ;
    solid-memo:distractorNote "A fake suits unit tests, but it cannot test the real login."@en .

<#q-building-apps-r03>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Another app stores a user's notes in a second Solid pod on a different server. Her WebID profile lists only her first pod under `pim:storage`, and no type index entry points to the second. Why does a link-traversal query starting from her WebID miss the notes?"@en ;
    solid-memo:back "No link from anything the query reads leads to the second pod"@en ;
    solid-memo:backNote "Link traversal discovers data by following links such as `pim:storage`, type indexes and `ldp:contains`. Data that no link reaches is invisible to it."@en ;
    solid-memo:distractor <#q-building-apps-r03-d1> ,
                          <#q-building-apps-r03-d2> ,
                          <#q-building-apps-r03-d3> .

<#q-building-apps-r03-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Link traversal only reads documents that are public"@en ;
    solid-memo:distractorNote "With an authenticated fetch it can read private documents too; the problem is that no link leads there."@en .

<#q-building-apps-r03-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Comunica refuses to query vocabularies that it does not recognise"@en ;
    solid-memo:distractorNote "Comunica queries any triples; it needs links to find the documents in the first place."@en .

<#q-building-apps-r03-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Traversal never follows `ldp:contains`, only type indexes"@en ;
    solid-memo:distractorNote "It can follow `ldp:contains`, but only inside storages it was led to, and nothing leads to the second pod."@en .

<#q-building-apps-r04>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app's user says saves fail after a while. The Network panel shows her PUTs answered with 401, and they carry no `Authorization` header. Which two fixes apply?"@en ;
    solid-memo:back "Pass `session.fetch` everywhere; handle `sessionExpired`"@en ;
    solid-memo:backNote "A request without `Authorization` is anonymous: either a call used the global `fetch`, or the session ended and `session.fetch` went anonymous. On `sessionExpired`, try one silent restore, then ask her to log in."@en ;
    solid-memo:distractor <#q-building-apps-r04-d1> ,
                          <#q-building-apps-r04-d2> ,
                          <#q-building-apps-r04-d3> .

<#q-building-apps-r04-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Grant her Write in the ACL; retry each failed PUT"@en ;
    solid-memo:distractorNote "No token reached the pod, so it can't tell who she is; permissions are not the problem yet."@en .

<#q-building-apps-r04-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Fix the pod's CORS headers; send the token in the request body"@en ;
    solid-memo:distractorNote "The 401 was readable, so CORS let it through, and tokens go in headers."@en .

<#q-building-apps-r04-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Store tokens in localStorage; refresh them by hand"@en ;
    solid-memo:distractorNote "Stored tokens can be stolen, and the library already refreshes them."@en .

<#q-building-apps-r05>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "The server hosting your Solid app's Client ID Document is down for an hour, and your users' identity provider keeps no cached copy of it. What happens?"@en ;
    solid-memo:back "New logins to your app fail until the document is back"@en ;
    solid-memo:backNote "Providers dereference the client ID during login. ⚠ Community Solid Server 7.2 (2026) can fetch it again (it keeps no copy), which normally includes silent restores and token refreshes, so the document must stay reachable over HTTPS."@en ;
    solid-memo:distractor <#q-building-apps-r05-d1> ,
                          <#q-building-apps-r05-d2> ,
                          <#q-building-apps-r05-d3> .

<#q-building-apps-r05-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Every logged-in user is cut off at once"@en ;
    solid-memo:distractorNote "Requests with a still-valid access token keep working; on a provider that keeps no copy, such as CSS 7.2, refreshes and restores can fail meanwhile too."@en .

<#q-building-apps-r05-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Providers switch the app to dynamic registration"@en ;
    solid-memo:distractorNote "The provider needs your document to check the redirect URI; it does not swap methods."@en .

<#q-building-apps-r05-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Users log in, but see only public data meanwhile"@en ;
    solid-memo:distractorNote "Without the document the provider cannot complete the login at all."@en .

<#q-building-apps-r06>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In the browser's Network panel, a cross-origin response from a Solid pod shows `WAC-Allow: user=\"read\"`, but your code's `res.headers.get(\"WAC-Allow\")` returns `null`. Why?"@en ;
    solid-memo:back "The server's CORS headers don't expose it to scripts"@en ;
    solid-memo:backNote "Cross-origin scripts see only safelisted headers and those listed in `Access-Control-Expose-Headers`. Community Solid Server 7.2 (2026) lists `WAC-Allow`; a server that doesn't hides it from your code."@en ;
    solid-memo:distractor <#q-building-apps-r06-d1> ,
                          <#q-building-apps-r06-d2> ,
                          <#q-building-apps-r06-d3> .

<#q-building-apps-r06-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`WAC-Allow` is sent only on HEAD requests, never on GET"@en ;
    solid-memo:distractorNote "WAC servers send it on GET and on HEAD."@en .

<#q-building-apps-r06-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The token was ignored, so the response was anonymous"@en ;
    solid-memo:distractorNote "The header is there in the panel; the question is whether scripts may read it."@en .

<#q-building-apps-r06-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Header names are case-sensitive, so the lookup missed it"@en ;
    solid-memo:distractorNote "`headers.get()` ignores case; the header was hidden from scripts."@en .

<#q-building-apps-r07>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front """A Solid app's WebID-first login reads the profile with `@inrupt/solid-client` (v4) like this, and `getThing` throws a `ValidThingUrlExpectedError`. What is wrong?

```js
const profile = await getSolidDataset(webId, { fetch });
const me = getThing(profile, "#me");
```"""@en ;
    solid-memo:back "`getThing` needs the full WebID, not the fragment alone"@en ;
    solid-memo:backNote "Things are looked up by their full IRI, here the WebID itself: `getThing(profile, webId)`. `getThing` throws for a string that is not a URL, and returns `null` for a valid IRI that isn't in the document."@en ;
    solid-memo:distractor <#q-building-apps-r07-d1> ,
                          <#q-building-apps-r07-d2> ,
                          <#q-building-apps-r07-d3> .

<#q-building-apps-r07-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The profile is private, so `fetch` returned nothing"@en ;
    solid-memo:distractorNote "Profiles are public, and the error is about the Thing's URL, not the read."@en .

<#q-building-apps-r07-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`getSolidDataset` cannot read a URL that has a fragment in it"@en ;
    solid-memo:distractorNote "It reads the document the WebID points into; the fragment only names a subject."@en .

<#q-building-apps-r07-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The dataset must be saved before Things can be read"@en ;
    solid-memo:distractorNote "Reading needs no save; datasets are only saved to write."@en .

# Chapter 13: Security, backends and going live.
<#ch-security>
    a solid-memo:Chapter ,
      schema:Syllabus ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <> ;
    schema:position 12 ;
    dcterms:title "Security, backends and going live"@en ;
    dcterms:description "Keep a Solid app and its users safe, run code that acts without a browser, and publish the app."@en ;
    solid-memo:reviewQuestion <#q-security-r01> ,
                              <#q-security-r02> ,
                              <#q-security-r03> ,
                              <#q-security-r04> ,
                              <#q-security-r05> ,
                              <#q-security-r06> ,
                              <#q-security-r07> .

<#ch-security-1>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-security> ;
    schema:position 0 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Pod data is untrusted input

Everything your app reads from a pod was written by someone: the user, any app the user authorised, or, in an inbox, anyone with Append. Treat it like form input from a stranger.

A literal can hold `<img src=x onerror="…">`. Insert it with `textContent`, or let your framework escape it; never use `innerHTML` or escape hatches such as React's `dangerouslySetInnerHTML`. Links are worse: `javascript:…` is a syntactically valid IRI, so an RDF parser accepts it, and clicking it runs script in your app. Allow only `http:` and `https:`:

```js
function linkFromRdf(iri, label) {
  const a = document.createElement("a");
  a.textContent = label;                 // text, never HTML
  let url;
  try { url = new URL(iri); } catch { return a; }
  if (url.protocol === "https:" || url.protocol === "http:") a.href = url.href;
  return a;
}
```

---

The pod doesn't filter markup. On CSS 7.2 (October 2026), this PUT, made as alice, got `201 Created`, and a later GET returned the literal exactly as written:

```http
PUT /alice/notes/xss.ttl HTTP/1.1
Host: localhost:3000
Authorization: DPoP <alice's access token>
DPoP: <proof>
Content-Type: text/turtle

<#it> <http://schema.org/name> "<img src=x onerror=alert(1)>" .
```

```js
const title = '<img src=x onerror=alert(1)>';  // the literal read back
document.body.textContent = title;  // shows the characters <img src=x onerror=alert(1)>
document.body.innerHTML = title;    // runs alert(1): the data has become script
```

Two more habits. Don't automatically fetch, embed or `<iframe>` URLs found in data; let the user choose to follow them. And bound sizes: cap how many bytes you download and how many triples you render, because nothing stops a writer from making a resource huge."""@en ;
    solid-memo:checkedBy <#q-security-1a> ,
                         <#q-security-1b> .

<#q-security-1a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A note's title in a Solid pod is `<img src=x onerror=\"steal()\">`. Your web app shows it with `el.innerHTML = title`. What happens?"@en ;
    solid-memo:back "`steal()` runs inside your app, with the user's session"@en ;
    solid-memo:backNote "`innerHTML` turns data into markup, so an event handler in a literal runs as your app. Set text with `textContent` or framework escaping."@en ;
    solid-memo:distractor <#q-security-1a-d1> ,
                          <#q-security-1a-d2> ,
                          <#q-security-1a-d3> .

<#q-security-1a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing, since the pod rejects literals containing markup"@en ;
    solid-memo:distractorNote "A literal can be any string; the pod stores it as written."@en .

<#q-security-1a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing, since DPoP-bound tokens can't be used by scripts"@en ;
    solid-memo:distractorNote "DPoP doesn't stop script running in your own page from using the tokens."@en .

<#q-security-1a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The browser blocks it, as the data came from another origin"@en ;
    solid-memo:distractorNote "Once inserted into your page, the markup runs in your origin."@en .

<#q-security-1b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In a Solid app, a contact's `foaf:homepage` read from a pod is `javascript:steal()`. How should the app render it?"@en ;
    solid-memo:back "As a link only if its scheme is `http` or `https`"@en ;
    solid-memo:backNote "Validate the scheme of every URL taken from data against an allow-list (`http`, `https`) before putting it in `href` or `src`."@en ;
    solid-memo:distractor <#q-security-1b-d1> ,
                          <#q-security-1b-d2> ,
                          <#q-security-1b-d3> .

<#q-security-1b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "As a link, since the Turtle containing it parsed without errors"@en ;
    solid-memo:distractorNote "Valid RDF says nothing about whether a link is safe to click."@en .

<#q-security-1b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "As a link, after removing the word `javascript` from the IRI"@en ;
    solid-memo:distractorNote "A block-list misses other dangerous forms; allow-list the safe schemes."@en .

<#q-security-1b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "As a link, if the contact's profile was served over HTTPS"@en ;
    solid-memo:distractorNote "HTTPS protects the transfer, not the content someone wrote."@en .

<#ch-security-2>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-security> ;
    schema:position 1 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Content Security Policy

Escaping (Step 13.1) is the first defence against injected markup. DPoP is none: script in your page can use its tokens, even ones kept in memory. A **Content Security Policy** (CSP) is a second defence: a response header telling the browser where scripts may come from and what the page may load and connect to. It must be one line:

```http
Content-Security-Policy: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'none'; img-src 'self' https: data:; connect-src 'self' https: wss:
```

`script-src 'self'` refuses inline scripts and scripts from other hosts, so injected markup can't easily load code. `default-src 'self'` covers every directive you leave out, so without `img-src` pod images would be blocked. `connect-src` is the trade-off: each user's pod and issuer can be on any host, so it usually allows any `https:` origin. CSP limits what script runs, not where data goes; don't rely on it alone.

---

**Sending it.** Static hosts set headers in their configuration, such as a `_headers` file on Netlify or Cloudflare Pages. A `<meta http-equiv="Content-Security-Policy">` tag needs no server but lacks some features. A local development pod at `http://localhost:3000` matches neither `https:` nor `wss:`, so in development add `http://localhost:3000` to `img-src`, and it and `ws://localhost:3000` to `connect-src`, or send no CSP. `default-src 'self'` also blocks inline styles, so keep them in a stylesheet."""@en ;
    solid-memo:checkedBy <#q-security-2a> ,
                         <#q-security-2b> .

<#q-security-2a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Why does a typical Solid app's Content Security Policy allow `connect-src https:` rather than a short list of hosts?"@en ;
    solid-memo:back "Each user's pod and issuer can be on any host"@en ;
    solid-memo:backNote "A Solid app can't know its users' pod and issuer hosts ahead of time, so `connect-src` stays broad; `script-src` is where CSP helps most."@en ;
    solid-memo:distractor <#q-security-2a-d1> ,
                          <#q-security-2a-d2> ,
                          <#q-security-2a-d3> .

<#q-security-2a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "CSP can't list hosts in `connect-src`, only schemes"@en ;
    solid-memo:distractorNote "Host sources are allowed; the problem is not knowing the hosts in advance."@en .

<#q-security-2a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Pods refuse requests from pages with a strict CSP"@en ;
    solid-memo:distractorNote "CSP is enforced by the browser on your page; the pod never sees it."@en .

<#q-security-2a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It stops injected script from sending data to other hosts"@en ;
    solid-memo:distractorNote "Allowing every `https:` origin is exactly what lets it send data anywhere."@en .

<#q-security-2b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front """A Solid app sends this Content Security Policy while you develop it against a local pod at `http://localhost:3000`. Logging in and loading notes now fail, and the browser console reports blocked requests. Why?

```http
Content-Security-Policy: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'none'; img-src 'self' https: data:; connect-src 'self' https: wss:
```"""@en ;
    solid-memo:back "`connect-src` allows `https:` and `wss:`, which don't match `http://localhost:3000`"@en ;
    solid-memo:backNote "A scheme source matches only that scheme, so a local `http` and `ws` pod must be listed for development, or the CSP left off locally. The browser console names the directive behind each blocked request."@en ;
    solid-memo:distractor <#q-security-2b-d1> ,
                          <#q-security-2b-d2> ,
                          <#q-security-2b-d3> .

<#q-security-2b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`script-src 'self'` blocks the login library loaded from your bundle"@en ;
    solid-memo:distractorNote "Your bundled library is served from your own origin, which `'self'` allows."@en .

<#q-security-2b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`base-uri 'none'` stops the app from resolving the pod's relative URLs"@en ;
    solid-memo:distractorNote "`base-uri` only limits the page's `<base>` element; it doesn't touch `fetch` or RDF parsing."@en .

<#q-security-2b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`object-src 'none'` blocks the pod's Turtle and JSON-LD responses"@en ;
    solid-memo:distractorNote "`object-src` covers plugins such as `<object>`, not `fetch`."@en .

<#ch-security-3>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-security> ;
    schema:position 2 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Phishing: look-alike issuers and WebIDs

A login can start from data an attacker wrote. Say your app accepts a pre-filled issuer. He sends a link such as `https://notes.example/login?issuer=https://solidcommunity.net.login-check.example/`, or asks the user to log in with a WebID he controls, whose profile names that issuer (WebID-first login). Your app redirects to a perfect copy of the real login page, and a user who types her password there has given it away.

Solid's trust check protects pods, not passwords. A pod believes a token only if the WebID's own profile lists its issuer, so a fake issuer can log in only as WebIDs that list it: the attacker's own. The danger is to the user's account at the real provider.

---

What your app can do:

- Before redirecting, show the issuer's host in full and stress its **registrable domain**, the part someone actually registered: "You'll sign in at solidcommunity.net.**login-check.example**". A familiar name at the start proves nothing.
- In issuer-first login, offer known providers to pick from.
- In sharing screens, show the **full WebID** next to the name. A profile's `foaf:name` and photo are claims anyone can copy; WAC warns servers not to trust them for access decisions."""@en ;
    solid-memo:checkedBy <#q-security-3a> ,
                         <#q-security-3b> .

<#q-security-3a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "An attacker runs a look-alike Solid-OIDC issuer at `solidcommunity.net.login-check.example` and sends links to your app with that issuer pre-filled. Some users log in through it, among them Alice, whose WebID profile lists `solidcommunity.net`. What can that issuer achieve?"@en ;
    solid-memo:back "Collect passwords typed into its copied login page"@en ;
    solid-memo:backNote "The profile check stops a fake issuer from speaking for other WebIDs, but a look-alike login page can still steal what users type. Showing the issuer's registrable domain helps users notice."@en ;
    solid-memo:distractor <#q-security-3a-d1> ,
                          <#q-security-3a-d2> ,
                          <#q-security-3a-d3> .

<#q-security-3a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Issue its own tokens that Alice's pod accepts as Alice"@en ;
    solid-memo:distractorNote "Alice's profile doesn't list that issuer, so her pod rejects its tokens."@en .

<#q-security-3a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Be trusted for Alice's WebID without her profile changing"@en ;
    solid-memo:distractorNote "Pods trust an issuer for a WebID only if that WebID's profile lists it."@en .

<#q-security-3a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Read every pod that trusts tokens from any issuer"@en ;
    solid-memo:distractorNote "Pods trust an issuer only for WebIDs whose profiles list it."@en .

<#q-security-3b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app's share dialog finds a WebID profile whose `foaf:name` is \"Alice Smith\". What should it show the user?"@en ;
    solid-memo:back "The name together with the full WebID"@en ;
    solid-memo:backNote "Names and photos are self-asserted. The WebID is what access rules use, so the user should see exactly which one they are granting."@en ;
    solid-memo:distractor <#q-security-3b-d1> ,
                          <#q-security-3b-d2> ,
                          <#q-security-3b-d3> .

<#q-security-3b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The name alone, since the pod verified the profile"@en ;
    solid-memo:distractorNote "Pods don't verify what profiles claim; anyone can write that name."@en .

<#q-security-3b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The name alone, since it was read over HTTPS"@en ;
    solid-memo:distractorNote "HTTPS proves which host sent it, not who the person is."@en .

<#q-security-3b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The photo alone, since it's harder to copy"@en ;
    solid-memo:distractorNote "A photo is just a URL in the profile and is as easy to copy as a name."@en .

<#ch-security-4>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-security> ;
    schema:position 3 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## SSRF: when your server fetches URLs for users

A browser app fetches from the user's machine. A **backend** fetches from inside your network, where it can reach what the public can't: a cloud metadata service at `http://169.254.169.254/`, an admin port on `localhost`, a database. **Server-side request forgery** (SSRF) is making your server fetch such an address for an attacker.

Solid backends fetch user-supplied URLs all the time: WebIDs, issuers, `pim:storage`, inboxes, webhook `sendTo` URLs, Client ID Documents. Guard every such fetch, following OWASP's SSRF guidance (the IETF Client ID Metadata Document draft, July 2026, requires the address and size checks):

- Allow only `https`; the sketch refuses even a local `http` pod.
- Resolve the host, refuse private, loopback and link-local addresses, and connect to the address you checked, so DNS can't change the answer in between.
- Don't follow redirects automatically; check each hop, or refuse them.
- Set a timeout and a maximum response size.

---

Node's `fetch` can't pin the connection itself, but accepts an undici `Agent` whose `lookup` checks every address before connecting. URLs with an IP address skip the lookup, so check those first. This sketch uses `undici` and `ipaddr.js`:

```js
import { Agent } from "undici";
import { lookup } from "node:dns";
import ipaddr from "ipaddr.js";

const isPublic = (ip) => ipaddr.process(ip).range() === "unicast";
const agent = new Agent({ connect: { lookup(host, opts, cb) {
  lookup(host, { ...opts, all: true }, (err, addrs) => {
    if (err) return cb(err);
    if (!addrs.every((a) => isPublic(a.address))) return cb(new Error(`blocked: ${host}`));
    opts.all ? cb(null, addrs) : cb(null, addrs[0].address, addrs[0].family);
  });
} } });

async function safeFetch(url) {
  const u = new URL(url);
  if (u.protocol !== "https:") throw new Error("https only");
  const host = u.hostname.replace(/^\\[|\\]$/g, "");
  if (ipaddr.isValid(host) && !isPublic(host)) throw new Error("blocked"); // IP literals skip lookup
  return fetch(u, { dispatcher: agent, redirect: "manual", signal: AbortSignal.timeout(5000) });
}
```

With `redirect: "manual"`, pass a 3xx response's `Location` through `safeFetch` again, or refuse it."""@en ;
    solid-memo:checkedBy <#q-security-4a> ,
                         <#q-security-4b> .

<#q-security-4a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your Solid backend fetches the WebID a user types, to show their name. Someone enters `https://meta.attacker.example/latest/meta-data/`, and that host name's DNS record points to `169.254.169.254`. Which defence stops this?"@en ;
    solid-memo:back "Refusing hosts that resolve to non-public addresses"@en ;
    solid-memo:backNote "SSRF is stopped before connecting: allow-list schemes, check the resolved address, and connect only to the address you checked. An egress proxy that enforces the same block list is another way."@en ;
    solid-memo:distractor <#q-security-4a-d1> ,
                          <#q-security-4a-d2> ,
                          <#q-security-4a-d3> .

<#q-security-4a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Accepting only responses that parse as valid Turtle"@en ;
    solid-memo:distractorNote "The request has already reached the internal service by then."@en .

<#q-security-4a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Checking that the URL's scheme is `https` and its port 443"@en ;
    solid-memo:distractorNote "This URL passes both; its host name still resolves to an internal address."@en .

<#q-security-4a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Accepting only WebIDs whose IRI ends in `#me`"@en ;
    solid-memo:distractorNote "A fragment is easy to add and is never sent to the server."@en .

<#q-security-4b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your Solid backend checks that a user-supplied URL's host resolves to a public address, then fetches it with automatic redirects on. Why is that still unsafe?"@en ;
    solid-memo:back "The public server can redirect the request to an internal address"@en ;
    solid-memo:backNote "Disable automatic redirects, or validate every hop exactly as you validated the first URL."@en ;
    solid-memo:distractor <#q-security-4b-d1> ,
                          <#q-security-4b-d2> ,
                          <#q-security-4b-d3> .

<#q-security-4b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Redirects always switch from `https` to `http`, which leaks data"@en ;
    solid-memo:distractorNote "A redirect can keep the scheme; the risk is where it points."@en .

<#q-security-4b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Public addresses may belong to another user's pod"@en ;
    solid-memo:distractorNote "Fetching a public pod is what the backend is for."@en .

<#q-security-4b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Redirects make the response too large to parse"@en ;
    solid-memo:distractorNote "Size is a separate limit; redirects change the destination."@en .

<#ch-security-5>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-security> ;
    schema:position 4 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Scripts that act as you: client credentials

Scripts, bots and CI jobs can't use a browser. They log in with **client credentials**: an id and secret pair that `@inrupt/solid-client-authn-node` exchanges for tokens. The tokens then carry the WebID of the user who created the credentials. On CSS 7.2 (October 2026), this code logged in and read a private container:

```js
import { Session } from "@inrupt/solid-client-authn-node";
const session = new Session();
await session.login({
  clientId: process.env.SOLID_CLIENT_ID,          // never in the source code
  clientSecret: process.env.SOLID_CLIENT_SECRET,
  oidcIssuer: process.env.SOLID_OIDC_ISSUER,      // e.g. "http://localhost:3000/" for a local CSS
});
const res = await session.fetch("http://localhost:3000/alice/notes/"); // a private container
console.log(res.status, await res.text());
```

---

Where do the id and secret come from? On CSS v7 the account owner creates them, in the account web page or through the JSON account API at `/.account/`, after logging in to that account with its email and password: a POST of `{"name": …, "webId": …}` to the account's client-credentials URL returns an `id` and a `secret`. Only WebIDs linked to the account can be chosen, and a DELETE on the credentials' URL revokes them. Seeding a CSS account creates no credentials, so a CI job makes them through the API after the server starts.

⚠ On CSS 7.2 (October 2026) a client-credentials token lasts 600 seconds and comes with no refresh token, so a script simply requests a new one with the same id and secret. A token recorded there, decoded:

```json
{
  "webid": "http://localhost:3000/alice/profile/card#me",
  "iss": "http://localhost:3000/",
  "aud": "solid",
  "iat": 1791408795,
  "exp": 1791409395
}
```"""@en ;
    solid-memo:checkedBy <#q-security-5a> ,
                         <#q-security-5b> .

<#q-security-5a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A nightly script must back up your own Solid pod. How should it authenticate?"@en ;
    solid-memo:back "With client credentials, acting as your WebID"@en ;
    solid-memo:backNote "`session.login({ clientId, clientSecret, oidcIssuer })` in `@inrupt/solid-client-authn-node` gets tokens carrying the registering user's WebID. Keep the secret out of the source code."@en ;
    solid-memo:distractor <#q-security-5a-d1> ,
                          <#q-security-5a-d2> ,
                          <#q-security-5a-d3> .

<#q-security-5a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "With the browser library opened in a hidden window"@en ;
    solid-memo:distractorNote "Scripts use the Node library's client-credentials login, not a browser flow."@en .

<#q-security-5a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "With your account password sent on each pod request"@en ;
    solid-memo:distractorNote "Pod requests carry tokens; on servers such as CSS, a password is used at most once, to create the client credentials."@en .

<#q-security-5a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "With no login, since the pod owner can always read"@en ;
    solid-memo:distractorNote "Without a token the request is anonymous and gets only public access."@en .

<#q-security-5b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "On Community Solid Server 7.2 (October 2026), your script's client-credentials token expires after 600 seconds, halfway through a long job. What should it do?"@en ;
    solid-memo:back "Request a new token with the same id and secret"@en ;
    solid-memo:backNote "The client-credentials grant can be repeated whenever a token runs out. As of October 2026, Inrupt's Node library (v5) does this for you in the background."@en ;
    solid-memo:distractor <#q-security-5b-d1> ,
                          <#q-security-5b-d2> ,
                          <#q-security-5b-d3> .

<#q-security-5b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Send the refresh token from the first token response"@en ;
    solid-memo:distractorNote "CSS 7.2 returns no refresh token for client credentials."@en .

<#q-security-5b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Keep the old token and sign a fresh DPoP proof"@en ;
    solid-memo:distractorNote "A new proof doesn't extend the token; the server checks its expiry."@en .

<#q-security-5b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Open a browser so the owner can log in again"@en ;
    solid-memo:distractorNote "The credentials exist so that no person has to log in."@en .

<#ch-security-6>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-security> ;
    schema:position 5 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Bots and services with their own WebID

Start from **least privilege**: give every agent only the access its job needs. Your app shares exactly the resource and modes the user chose, and never widens ACLs, grants Control or makes data public by default. Code that runs alone is no different.

Client credentials make a script act **as you**, with all your access. That suits your own backups, not a service many people use, such as a backup service, a feed aggregator or an AI assistant.

Such a service should be **an agent of its own**: its own WebID, usually with an account and pod on some server, and client credentials created for that WebID. Users grant that WebID access like anyone else's, with an `acl:agent` authorization or an ACP matcher, and only the modes it needs. The user can then see, narrow and revoke the service's access without touching her own; its tokens carry its WebID, not hers, so a pod can tell its requests from hers; and she never hands over her own credentials.

---

On CSS 7.2 (October 2026), Alice gave a service account, backupbot, Read on one resource:

```turtle
@prefix acl: <http://www.w3.org/ns/auth/acl#>.

<#owner> a acl:Authorization;
  acl:agent <http://localhost:3000/alice/profile/card#me>;
  acl:accessTo <http://localhost:3000/alice/backup/a.ttl>;
  acl:mode acl:Read, acl:Write, acl:Control.

<#backupbot> a acl:Authorization;
  acl:agent <http://localhost:3000/backupbot/profile/card#me>;
  acl:accessTo <http://localhost:3000/alice/backup/a.ttl>;
  acl:mode acl:Read.
```

backupbot's own requests then got:

```text
GET /alice/backup/a.ttl    200 OK          wac-allow: user="read"
GET /alice/private/b.ttl   403 Forbidden
its token's webid          http://localhost:3000/backupbot/profile/card#me
```"""@en ;
    solid-memo:checkedBy <#q-security-6a> ,
                         <#q-security-6b> .

<#q-security-6a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "You run a backup service for Solid pods that many people sign up for. How should it get access to their pods?"@en ;
    solid-memo:back "Each user grants the service's own WebID Read on her data"@en ;
    solid-memo:backNote "A shared service is its own agent: its own WebID and credentials, granted access by each user like anyone else."@en ;
    solid-memo:distractor <#q-security-6a-d1> ,
                          <#q-security-6a-d2> ,
                          <#q-security-6a-d3> .

<#q-security-6a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Each user gives it client credentials for her own WebID"@en ;
    solid-memo:distractorNote "Then it acts as her, with all her access, and looks like her."@en .

<#q-security-6a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Each user makes the data to be backed up public"@en ;
    solid-memo:distractorNote "That exposes the data to everyone, not only to the service."@en .

<#q-security-6a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Each user hands the service a refresh token from her own login"@en ;
    solid-memo:distractorNote "It would act as her, so her pod can't tell its requests from hers and she can't narrow them."@en .

<#q-security-6b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "An AI assistant with its own WebID has Read on Alice's calendar in her Solid pod. She wants to stop it but keep her own access. What does she do?"@en ;
    solid-memo:back "Remove the authorization that names the assistant's WebID"@en ;
    solid-memo:backNote "Because the assistant is a separate agent, its access is a separate rule that can be removed on its own."@en ;
    solid-memo:distractor <#q-security-6b-d1> ,
                          <#q-security-6b-d2> ,
                          <#q-security-6b-d3> .

<#q-security-6b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Delete the client credentials she created for her own scripts"@en ;
    solid-memo:distractorNote "The assistant logs in with its own credentials, not hers."@en .

<#q-security-6b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Log out of her identity provider in every browser"@en ;
    solid-memo:distractorNote "That ends her sessions; the assistant's access comes from the rule."@en .

<#q-security-6b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Remove her own WebID from the calendar's ACL"@en ;
    solid-memo:distractorNote "That removes her access and leaves the assistant's untouched."@en .

<#ch-security-7>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-security> ;
    schema:position 6 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Acting for a user over time: offline_access and refresh tokens

A backend sometimes must act **as a particular user** while she is away; otherwise give it its own WebID (Step 13.6). Add the `offline_access` scope to the code flow. A provider that supports it returns a **refresh token**, which the backend exchanges for new access tokens later.

⚠ On CSS 7.2 (October 2026), refresh tokens last a day and come only if the user leaves "Remember this client" ticked.

⚠ As of October 2026, Inrupt's Node library (v5.0.1) requests `offline_access` by default.

---

**The backend runs the login itself**, keeping the tokens and DPoP key on the server. On CSS 7.2 (October 2026), with a local origin for `notes.example`, this code got a refresh token:

```js
import { Session, EVENTS, refreshTokens } from "@inrupt/solid-client-authn-node";
// GET /login (Express-style): one Session per user, its id kept in a cookie
const session = new Session({ keepAlive: false });
await session.login({
  oidcIssuer, clientId: "https://notes.example/id.jsonld",  // your Client ID Document
  redirectUrl: "https://notes.example/auth/callback",
  handleRedirect: (url) => res.redirect(url),                 // send her to her provider
});
// GET /auth/callback: get her Session back from a Map keyed by the cookie's id,
// keep her tokens with session.events.on(EVENTS.NEW_TOKENS, (tokens) => store(tokens)), then
await session.handleIncomingRedirect(`https://notes.example${req.url}`);
```

Later, `refreshTokens(stored)` returns new tokens, and `buildAuthenticatedFetch(accessToken, { dpopKey })` from `@inrupt/solid-client-authn-core` reads her pod with them.

---

Treat a refresh token like a password:

- Keep it **server-side**, encrypted, with its DPoP key.
- Expect **rotation**: a refresh may return a new token and invalidate the old one; store the newest.
- On `invalid_grant`, delete the token and ask her to log in again.

⚠ On CSS 7.2 (October 2026), a DPoP-bound refresh token rotates only after 70% of its lifetime; elsewhere, possibly on every refresh."""@en ;
    solid-memo:checkedBy <#q-security-7a> ,
                         <#q-security-7b> .

<#q-security-7a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Where should a Solid sync backend keep a user's refresh token?"@en ;
    solid-memo:back "In its own database, encrypted, with its DPoP key"@en ;
    solid-memo:backNote "A refresh token lets its holder act as the user, so it stays on the server, encrypted, with the key it is bound to. Tokens from a browser login can't be moved there anyway: they are bound to the browser's DPoP key."@en ;
    solid-memo:distractor <#q-security-7a-d1> ,
                          <#q-security-7a-d2> ,
                          <#q-security-7a-d3> .

<#q-security-7a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In the browser's `localStorage`, so the page can hand it over"@en ;
    solid-memo:distractorNote "Script in the page could read it there; it belongs on the server."@en .

<#q-security-7a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In a resource in the user's pod, next to her data"@en ;
    solid-memo:distractorNote "Any agent or app with Read on that resource would get it."@en .

<#q-security-7a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In the redirect URL, so it survives the login round trip"@en ;
    solid-memo:distractorNote "URLs end up in logs and browser history."@en .

<#q-security-7b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid backend's refresh-token request to the user's OpenID provider fails with `invalid_grant`. What should it do?"@en ;
    solid-memo:back "Drop the stored token and ask the user to log in again"@en ;
    solid-memo:backNote "A failed refresh means the grant is gone, for example revoked after disuse, logout or a password change. Only the user can start a new one, by logging in again with `offline_access`."@en ;
    solid-memo:distractor <#q-security-7b-d1> ,
                          <#q-security-7b-d2> ,
                          <#q-security-7b-d3> .

<#q-security-7b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Retry the same refresh token every minute until it works"@en ;
    solid-memo:distractorNote "It is expired or revoked, and reusing a rotated token can get the whole grant revoked."@en .

<#q-security-7b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Continue with the last access token until the provider recovers"@en ;
    solid-memo:distractorNote "Access tokens expire quickly, and the pod checks expiry."@en .

<#q-security-7b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Switch to the service's own client credentials and keep syncing"@en ;
    solid-memo:distractorNote "That silently switches identity; the job was agreed to run as her."@en .

<#ch-security-8>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-security> ;
    schema:position 7 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Receiving webhooks safely

With **WebhookChannel2023** your backend subscribes with an `https` `sendTo` URL, and the server POSTs notifications there. The response's `sender` names the WebID the server will authenticate as, and the draft requires an authenticated request "using identity provided as *sender*". How a receiver checks that is left open in the Notifications specification's issue tracker (issue #155).

⚠ On CSS 7.2 (October 2026), the server sends `Authorization: DPoP <token>` with a DPoP proof; the token's `webid` is a WebID the server serves for itself, naming the server as issuer. Verify it as a pod does, with a library such as `@solid/access-token-verifier`, and test against each server. On CSS this token's `iss` has no trailing slash (`http://localhost:3000`), unlike its login issuer, so an exact string comparison rejects genuine webhooks.

---

So don't rely on sender checks alone:

- Use an **unguessable URL per subscription**, such as `https://hooks.example/solid/3f9c…`, and reject POSTs to unknown ones.
- Treat the body as a **hint**. Refetch the topic with your own credentials; a DPoP proof doesn't cover the body anyway.
- **Answer quickly** with a 2xx and do the work afterwards.
- **Unsubscribe** when done; on CSS, DELETE the channel's `id`."""@en ;
    solid-memo:checkedBy <#q-security-8a> ,
                         <#q-security-8b> .

<#q-security-8a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A Solid WebhookChannel2023 POST tells your backend that a resource it watches was updated. What should the backend do next?"@en ;
    solid-memo:back "Refetch the resource with its own credentials"@en ;
    solid-memo:backNote "A notification says something changed. What changed, and whether it really did, comes from reading the resource yourself."@en ;
    solid-memo:distractor <#q-security-8a-d1> ,
                          <#q-security-8a-d2> ,
                          <#q-security-8a-d3> .

<#q-security-8a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Store the POST body as the resource's new content"@en ;
    solid-memo:distractorNote "A notification doesn't carry the content and could be forged."@en .

<#q-security-8a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Reply only after the whole sync has finished"@en ;
    solid-memo:distractorNote "Answer fast and work afterwards, so the sender doesn't time out."@en .

<#q-security-8a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Fetch the resource with the token from the POST"@en ;
    solid-memo:distractorNote "That token identifies the pod server, not your backend."@en .

<#q-security-8b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "How a Solid WebhookChannel2023 receiver checks the sender isn't standardised, and servers differ. Which defence works whatever server sends the POST?"@en ;
    solid-memo:back "An unguessable URL per subscription, plus refetching the topic"@en ;
    solid-memo:backNote "A secret URL keeps strangers from reaching your handler, and refetching means a forged POST can at most make you read the resource again. Verify the sender's token too where the server supports it."@en ;
    solid-memo:distractor <#q-security-8b-d1> ,
                          <#q-security-8b-d2> ,
                          <#q-security-8b-d3> .

<#q-security-8b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Checking for an `Authorization` header, then trusting the body"@en ;
    solid-memo:distractorNote "Anyone can add a header; only a verified token means something, and the body is a hint anyway."@en .

<#q-security-8b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Accepting POSTs only from the pod server's IP address"@en ;
    solid-memo:distractorNote "Servers may send from other or shared addresses, and an address says nothing about the body."@en .

<#q-security-8b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Requiring a signature made with a secret you and the server share"@en ;
    solid-memo:distractorNote "WebhookChannel2023 defines no shared secret, so servers don't send one."@en .

<#ch-security-9>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-security> ;
    schema:position 8 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Deploying and publishing your app

A browser-only Solid app is static files, so any static host that serves HTTPS will do; Solid-OIDC requires tokens and credentials to travel only over TLS. Before going live:

- **Client ID Document.** Host it at a stable `https` URL, usually on your app's origin. Its `client_id` must equal that URL, and `redirect_uris` must list your production redirect URLs, which providers match exactly. With a development server on `localhost`, keep using `clientName` instead.
- **Keep it reachable.** Providers fetch it when a user logs in, and may cache it for a while; if it moves or goes down, logins fail.
- **Redirect back to one fixed page**, listed in `redirect_uris`, where `handleIncomingRedirect()` runs; route onward from there, saving the route first. Providers reject unlisted URLs.
- **Send your CSP header** (Step 13.2).
- **Test with accounts from several providers.**

Once live, you can ask for a listing in the app catalogue on solidproject.org.

⚠ As of October 2026, the catalogue takes requests by email, and its criteria include WebID login at a provider of the user's choice and keeping the app's data in pods."""@en ;
    solid-memo:checkedBy <#q-security-9a> ,
                         <#q-security-9b> .

<#q-security-9a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "After deploying a Solid app to `https://notes.example/`, logins fail with a redirect URI error, though they worked on `localhost`. What is the likely cause?"@en ;
    solid-memo:back "The Client ID Document doesn't list the production redirect URL"@en ;
    solid-memo:backNote "Providers compare the redirect URL exactly with the `redirect_uris` in the Client ID Document, so production URLs must be listed."@en ;
    solid-memo:distractor <#q-security-9a-d1> ,
                          <#q-security-9a-d2> ,
                          <#q-security-9a-d3> .

<#q-security-9a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The pod refuses requests from origins it hasn't seen before"@en ;
    solid-memo:distractorNote "Pods allow every origin through CORS; this error comes from the provider."@en .

<#q-security-9a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Static hosts can't serve the redirect page of a login"@en ;
    solid-memo:distractorNote "The redirect page is an ordinary page of your app."@en .

<#q-security-9a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Providers accept logins only from apps in the catalogue"@en ;
    solid-memo:distractorNote "The catalogue is a directory, not a requirement for logging in."@en .

<#q-security-9b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A deployed Solid app's Client ID Document is at `https://notes.example/id.jsonld`. What must hold for users to keep logging in?"@en ;
    solid-memo:back "It stays reachable and lists the redirect URL in use"@en ;
    solid-memo:backNote "Providers fetch the `client_id` URL when a user logs in, possibly from a cache, and check the redirect URL against it, so the document must stay reachable and up to date."@en ;
    solid-memo:distractor <#q-security-9b-d1> ,
                          <#q-security-9b-d2> ,
                          <#q-security-9b-d3> .

<#q-security-9b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Each user's pod holds a copy and checks the redirect URL"@en ;
    solid-memo:distractorNote "The provider fetches the `client_id` URL itself and checks the redirect; the pod isn't involved."@en .

<#q-security-9b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It carries the app's signature for providers to check"@en ;
    solid-memo:distractorNote "No signature is defined; the provider trusts the document because it fetched it from the `client_id` URL over https."@en .

<#q-security-9b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It is served from the same origin as the users' pods"@en ;
    solid-memo:distractorNote "Apps and pods can be on any hosts; pods allow every origin through CORS."@en .

<#q-security-r01>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your Solid backend's webhook handler learns that a post changed, refetches it and finds an `as:image` IRI to make a thumbnail from. What is safe?"@en ;
    solid-memo:back "Fetch the image only after checking its scheme and resolved address"@en ;
    solid-memo:backNote "Data in a pod is untrusted input, and a backend that fetches URLs from it needs SSRF checks."@en ;
    solid-memo:distractor <#q-security-r01-d1> ,
                          <#q-security-r01-d2> ,
                          <#q-security-r01-d3> .

<#q-security-r01-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Fetch the image at once, since the post came from your user's pod"@en ;
    solid-memo:distractorNote "Any agent with write access may have written it, and the IRI may point inside your network."@en .

<#q-security-r01-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Fetch the image only if the webhook POST carried a valid token"@en ;
    solid-memo:distractorNote "That token says who sent the notification, not where the IRI points."@en .

<#q-security-r01-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Fetch the image only if its IRI parsed as valid RDF"@en ;
    solid-memo:distractorNote "An internal address is a perfectly valid IRI."@en .

<#q-security-r02>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "An attacker's literal in a Solid pod, `<img src=x onerror=\"…\">`, ran as script in your web app. What is the first defense against injected markup like this, with a strict CSP only the second?"@en ;
    solid-memo:back "Escaping literals by rendering them with `textContent`"@en ;
    solid-memo:backNote "Escaping output stops the injection: `textContent` shows the characters as text, so the markup never runs. DPoP and memory-only tokens don't stop it, and CSP only backs escaping up."@en ;
    solid-memo:distractor <#q-security-r02-d1> ,
                          <#q-security-r02-d2> ,
                          <#q-security-r02-d3> .

<#q-security-r02-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Using DPoP-bound access tokens"@en ;
    solid-memo:distractorNote "DPoP doesn't stop script running in your page."@en .

<#q-security-r02-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Keeping tokens only in memory"@en ;
    solid-memo:distractorNote "That limits theft, but the script still runs."@en .

<#q-security-r02-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Allowing only `http:` and `https:` link schemes"@en ;
    solid-memo:distractorNote "That stops `javascript:` links, not markup inside a literal."@en .

<#q-security-r03>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Three Solid jobs: (1) a nightly backup of your own pod; (2) a public service many people use; (3) syncing one user's pod, acting as her, while she is away. Which pairing fits?"@en ;
    solid-memo:back "(1) client credentials as you; (2) its own WebID; (3) a refresh token"@en ;
    solid-memo:backNote "Act as yourself with client credentials, as another user with her refresh token, and as a service with its own WebID. Prefer the service's own WebID whenever the user can grant it narrow access, since its actions stay separate and revocable."@en ;
    solid-memo:distractor <#q-security-r03-d1> ,
                          <#q-security-r03-d2> ,
                          <#q-security-r03-d3> .

<#q-security-r03-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "(1) a refresh token; (2) client credentials as you; (3) its own WebID"@en ;
    solid-memo:distractorNote "A public service acting as you would use your access for everyone."@en .

<#q-security-r03-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "(1) its own WebID; (2) a refresh token; (3) client credentials as you"@en ;
    solid-memo:distractorNote "Client credentials act as you, not as the user being synced."@en .

<#q-security-r03-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "(1) client credentials as you; (2) a refresh token; (3) its own WebID"@en ;
    solid-memo:distractorNote "A service holding everyone's refresh tokens acts as each of them."@en .

<#q-security-r04>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A look-alike Solid-OIDC issuer copies a real provider's login page. Which protects the pod, and which protects the user?"@en ;
    solid-memo:back "Pod: the profile must list the issuer; user: seeing the issuer's host"@en ;
    solid-memo:backNote "The `solid:oidcIssuer` check stops a fake issuer from logging in as other WebIDs; only the user, helped by your app showing the host, can avoid typing her password into it."@en ;
    solid-memo:distractor <#q-security-r04-d1> ,
                          <#q-security-r04-d2> ,
                          <#q-security-r04-d3> .

<#q-security-r04-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Pod: DPoP proofs; user: the `iss` check after the redirect"@en ;
    solid-memo:distractorNote "Neither stops a user typing her password into a fake page."@en .

<#q-security-r04-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Pod: PKCE; user: the profile listing the issuer"@en ;
    solid-memo:distractorNote "PKCE protects the code; the profile check protects pods, not passwords."@en .

<#q-security-r04-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Pod: CORS; user: a strict Content Security Policy"@en ;
    solid-memo:distractorNote "CORS doesn't decide which tokens a pod believes, and CSP can't spot a fake site."@en .

<#q-security-r05>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A logging bot with its own WebID must add entries to one log resource in your Solid pod. What should you grant?"@en ;
    solid-memo:back "Append on that resource, to the bot's WebID"@en ;
    solid-memo:backNote "Give the bot's own WebID the smallest mode on the smallest resource that does the job."@en ;
    solid-memo:distractor <#q-security-r05-d1> ,
                          <#q-security-r05-d2> ,
                          <#q-security-r05-d3> .

<#q-security-r05-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Write on your whole pod, to the bot's WebID"@en ;
    solid-memo:distractorNote "Far more resources and modes than adding entries needs."@en .

<#q-security-r05-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Append on that resource, to everyone"@en ;
    solid-memo:distractorNote "Anyone could then add entries, not just the bot."@en .

<#q-security-r05-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Your own client credentials, given to the bot"@en ;
    solid-memo:distractorNote "It would act as you, with all your access."@en .

<#q-security-r06>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your Solid app moves from `https://old.example/` to `https://app.example/`. What must change for logins to keep working?"@en ;
    solid-memo:back "A reachable Client ID Document listing the new redirect URLs"@en ;
    solid-memo:backNote "The `client_id` is the document's URL and its `redirect_uris` must match exactly. Apps usually publish a new document on the new origin; updating the old one also works while it stays reachable."@en ;
    solid-memo:distractor <#q-security-r06-d1> ,
                          <#q-security-r06-d2> ,
                          <#q-security-r06-d3> .

<#q-security-r06-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Every user's WebID profile, to list the new app"@en ;
    solid-memo:distractorNote "Profiles list issuers, not the apps a user uses."@en .

<#q-security-r06-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The pods' CORS settings, to allow the new origin"@en ;
    solid-memo:distractorNote "Pods already allow every origin."@en .

<#q-security-r06-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only an HTTP redirect from the old origin to the new one"@en ;
    solid-memo:distractorNote "The provider still checks the new callback URL against the document's `redirect_uris`, which don't list it."@en .

<#q-security-r07>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A user asks your Solid app to let bob read one note in her pod. Which change follows least privilege?"@en ;
    solid-memo:back "An authorization giving bob Read on that note only"@en ;
    solid-memo:backNote "Grant exactly the resource and modes the user picked. Wider grants are hard to notice and easy to forget."@en ;
    solid-memo:distractor <#q-security-r07-d1> ,
                          <#q-security-r07-d2> ,
                          <#q-security-r07-d3> .

<#q-security-r07-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Making the notes container readable by everyone"@en ;
    solid-memo:distractorNote "That exposes every note to the whole web, not just one to bob."@en .

<#q-security-r07-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Giving bob Read and Write on the container, to save asking later"@en ;
    solid-memo:distractorNote "It grants more resources and modes than the user chose."@en .

<#q-security-r07-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Giving bob Control on the note, so he can manage it himself"@en ;
    solid-memo:distractorNote "Control lets bob rewrite the rules, far more than reading."@en .

# Chapter 14: Read a minimal Solid app.
<#ch-read-an-app>
    a solid-memo:Chapter ,
      schema:Syllabus ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <> ;
    schema:position 13 ;
    dcterms:title "Read a minimal Solid app"@en ;
    dcterms:description "Read, one piece at a time, the code of Solid Notes, a small notes app that uses every core piece of Solid from Chapters 5-13, with what it did on Community Solid Server 7.2. It ends with keeping the login healthy, serving the app the way it would go live, and checking who logged in."@en ;
    solid-memo:reviewQuestion <#q-read-an-app-r01> ,
                              <#q-read-an-app-r02> ,
                              <#q-read-an-app-r03> ,
                              <#q-read-an-app-r04> ,
                              <#q-read-an-app-r05> ,
                              <#q-read-an-app-r06> ,
                              <#q-read-an-app-r07> ,
                              <#q-read-an-app-r08> ,
                              <#q-read-an-app-r09> .

<#ch-read-an-app-1>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-an-app> ;
    schema:position 0 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## What the app does, and its one design rule

**Solid Notes** is a small notes app written for this course. **alice** owns the notes; **bob** is her friend. The app logs alice in, finds her storage, registers where notes live, creates and edits notes, uploads a picture, shares a note with bob, posts to his inbox, follows changes live and keeps its login healthy. Every piece comes from Chapters 5-13. Its code is a few small ES modules, a browser page and a test suite that runs in Node.

---

The key design choice: **every function that talks to the pod takes a `fetch` parameter**. In the browser it is `session.fetch`, which adds the DPoP-bound token (Step 7.10); in the tests, a client-credentials login (Step 13.5). So the same pod logic is tested in Node and shipped to the browser.

```js
// src/notes.js
export async function createNote(container, text, fetch, slug = 'note') {
  // …
}
```

The worked examples in this chapter were recorded in 2026 on Community Solid Server (CSS) 7.2 in its default configuration (WAC, data in memory), unless they say otherwise. Each test run made fresh accounts, so names such as `alice40742` differ between examples."""@en ;
    solid-memo:checkedBy <#q-read-an-app-1a> .

<#q-read-an-app-1a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In the Solid Notes example app, why does every function that talks to the pod take a `fetch` argument instead of calling the global `fetch`?"@en ;
    solid-memo:back "So the same code runs with the browser's login or the tests' login"@en ;
    solid-memo:backNote "The authenticated fetch is the only thing that differs between the browser (`session.fetch`) and the tests (a client-credentials login), so passing it in keeps the pod logic identical in both."@en ;
    solid-memo:distractor <#q-read-an-app-1a-d1> ,
                          <#q-read-an-app-1a-d2> ,
                          <#q-read-an-app-1a-d3> .

<#q-read-an-app-1a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Because the global `fetch` cannot send PATCH requests to a Solid pod"@en ;
    solid-memo:distractorNote "The global fetch sends any method; it just carries no Solid login."@en .

<#q-read-an-app-1a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "So the app can switch between Turtle and JSON-LD at runtime"@en ;
    solid-memo:distractorNote "Content negotiation is done with the Accept header, not by swapping fetch."@en .

<#q-read-an-app-1a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Because Node has no global `fetch`, so the tests need a polyfill"@en ;
    solid-memo:distractorNote "Node 22 has a global fetch; the parameter is about who is logged in."@en .

<#ch-read-an-app-2>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-an-app> ;
    schema:position 1 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Logging in: a provider or a WebID

The login form offers both entry points from Step 12.6. **Issuer-first**: the user picks a provider from a list or types any provider's URL; without that field, users of unlisted providers are locked out. **WebID-first**: the user types a WebID and the app reads the profile's `solid:oidcIssuer`. One issuer: log in there. Several: the app lists *those* issuers and lets the user pick. None: pick or type one. Both are safe because the pod checks the token's issuer against the profile (Step 7.9). Never *guess* the issuer from the WebID's domain.

---

```js
// src/main.js (WebID-first)
  const issuers = await issuersOf($('webid').value); // the profile's solid:oidcIssuer values
  if (issuers.length === 1) return startLogin(issuers[0], { pending: pendingNow() });
  if (issuers.length === 0) return status('Your profile names no provider: pick or type one above.');
  $('provider').replaceChildren(...issuers.map((issuer) => new Option(issuer, issuer)));
```

`startLogin` calls `login` from `@inrupt/solid-client-authn-browser` 5.0.1; back from the provider, `handleIncomingRedirect` finishes the login. Steps 14.14-14.18 handle the rest of the session. A test can't click through a login page, so the Node tests log in with client credentials made through the CSS account API (Step 13.5). On CSS 7.2 a browser test logged in all three ways: WebID-first, a listed provider and a typed provider URL."""@en ;
    solid-memo:checkedBy <#q-read-an-app-2a> ,
                         <#q-read-an-app-2b> .

<#q-read-an-app-2a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In the Solid Notes example app, alice's WebID profile lists two `solid:oidcIssuer` values. What does the app do when she logs in with her WebID?"@en ;
    solid-memo:back "Lists those two issuers and lets her pick one to log in with"@en ;
    solid-memo:backNote "Every issuer the profile lists is trusted, so the user chooses; the app offers exactly those, not its own provider list."@en ;
    solid-memo:distractor <#q-read-an-app-2a-d1> ,
                          <#q-read-an-app-2a-d2> ,
                          <#q-read-an-app-2a-d3> .

<#q-read-an-app-2a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Picks the first issuer, since profile order shows preference"@en ;
    solid-memo:distractorNote "RDF triples have no order, so \"first\" means nothing."@en .

<#q-read-an-app-2a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Uses the issuer whose host matches her WebID's host"@en ;
    solid-memo:distractorNote "Solid-OIDC takes the issuers from the profile's `solid:oidcIssuer`; the WebID's domain says nothing about them."@en .

<#q-read-an-app-2a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Refuses, because a WebID may trust only one issuer"@en ;
    solid-memo:distractorNote "A profile may list several; the pod accepts a token from any of them."@en .

<#q-read-an-app-2b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "The Node tests of the Solid Notes example app run against Community Solid Server 7. How do they log alice in without a browser?"@en ;
    solid-memo:back "With client credentials made through the CSS account API"@en ;
    solid-memo:backNote "The test setup creates an account, a pod and client credentials; `Session.login({ clientId, clientSecret, oidcIssuer })` then gives a `session.fetch` that adds a DPoP-bound access token."@en ;
    solid-memo:distractor <#q-read-an-app-2b-d1> ,
                          <#q-read-an-app-2b-d2> ,
                          <#q-read-an-app-2b-d3> .

<#q-read-an-app-2b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "By sending alice's email and password along with every request"@en ;
    solid-memo:distractorNote "Pods never see passwords; only the identity provider does."@en .

<#q-read-an-app-2b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "By reusing the session cookie from the last manual browser login"@en ;
    solid-memo:distractorNote "The tests start fresh; that cookie belongs to the identity provider's pages."@en .

<#q-read-an-app-2b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "By making the notes container public while the tests run"@en ;
    solid-memo:distractorNote "The tests log in for real, so access control is exercised too."@en .

<#ch-read-an-app-3>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-an-app> ;
    schema:position 2 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Finding the storage

Once alice is logged in, the app needs the root of her storage. Step 5.5 gave the rule: use `pim:storage` from the profile if it is there; otherwise walk up from the profile document, one container at a time, until a response carries `Link: <http://www.w3.org/ns/pim/space#Storage>; rel="type"`. A fresh CSS 7.2 profile has no `pim:storage`, so there the walk-up is what works.

---

```js
// src/notes.js
export async function findStorage(webId, fetch) {
  const { quads } = await readTurtle(webId, fetch);
  const [storage] = objects(quads, webId, `${ns.pim}storage`);
  if (storage) return storage;
  for (let url = new URL('./', webId).href; ; url = new URL('../', url).href) {
    const res = await fetch(url, { method: 'HEAD' });
    if (linksOf(res, 'type', url).includes(`${ns.pim}Storage`)) return url;
    if (new URL(url).pathname === '/') throw new Error(`no storage above ${webId}`);
  }
}
```

`readTurtle` GETs the document with `Accept: text/turtle` and parses it with the `n3` library. `linksOf` reads one relation from the `Link` header, ignoring the relation's case, and resolves it against the URL that was fetched, because some servers send relative targets.

On CSS 7.2, for the WebID `http://localhost:3000/alice40742/profile/card#me`, the walk-up started at `…/alice40742/profile/` (no Storage link) and stopped at `http://localhost:3000/alice40742/`."""@en ;
    solid-memo:checkedBy <#q-read-an-app-3a> .

<#q-read-an-app-3a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On Community Solid Server 7.2 (2026), a fresh WebID profile has no `pim:storage`. How does the Solid Notes example app's `findStorage` find the user's storage?"@en ;
    solid-memo:back "It HEADs each parent container until one has a `pim:Storage` type link"@en ;
    solid-memo:backNote "Without `pim:storage`, the app walks up from the profile document until a container's Link header says `rel=\"type\"` `pim:Storage`."@en ;
    solid-memo:distractor <#q-read-an-app-3a-d1> ,
                          <#q-read-an-app-3a-d2> ,
                          <#q-read-an-app-3a-d3> .

<#q-read-an-app-3a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It reads `/.well-known/solid` at the server root and takes its storage"@en ;
    solid-memo:distractorNote "On CSS 7.2's default configuration that names the server root, not alice's pod."@en .

<#q-read-an-app-3a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It takes the first path segment of the WebID as the pod's name"@en ;
    solid-memo:distractorNote "URL patterns differ between servers; only the type link is reliable."@en .

<#q-read-an-app-3a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It asks the identity provider which pod belongs to the WebID"@en ;
    solid-memo:distractorNote "The identity provider issues tokens; it doesn't know where the data is."@en .

<#ch-read-an-app-4>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-an-app> ;
    schema:position 3 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Finding or creating the type registration

Following Steps 11.3-11.5, `findRegistration` only reads: the profile, the preferences file if the profile links one, and every public and private type index linked from either. The first registration of `schema:NoteDigitalDocument` with a `solid:instanceContainer` wins, even if another app wrote it.

```js
// src/notes.js (findRegistration)
  for (const index of [...indexes(`${ns.solid}publicTypeIndex`), ...indexes(`${ns.solid}privateTypeIndex`)]) {
    const { quads } = await readTurtle(index, fetch);
    for (const q of quads.filter((t) => t.predicate.value === `${ns.solid}forClass` && t.object.value === NOTE)) {
      const [container] = objects(quads, q.subject.value, `${ns.solid}instanceContainer`);
      if (container) return { ...found, container, registration: q.subject.value };
    }
  }
```

---

A fresh CSS 7.2 pod has neither a type index nor a preferences file. Creating them changes the user's settings, so the app asks first: "Your pod has no private type index. Create one in settings/?" If she agrees, `createRegistration` PUTs `settings/privateTypeIndex.ttl` and `settings/prefs.ttl` with `If-None-Match: *` and links the preferences file from the profile with an insert-only N3 Patch. Both inherit the root's owner-only rule, so the private index is private. An existing private index is only added to. If she says no, notes go unregistered in `notes/`.

The registration is another insert-only patch. It needs an IRI, because CSS 7.2 answers 422 to blank nodes in `solid:inserts` (Step 6.8), and a fragment no other app is likely to pick: an insert into an existing subject would merge with it.

```js
// src/notes.js (createRegistration)
  const index = privateIndex ?? await createPrivateIndex(webId, storage, prefs, fetch);
  const registration = `${index}#reg-notes-${crypto.randomUUID().slice(0, 8)}`;
  await patch(index, n3Patch({
    inserts: `<${registration}> a solid:TypeRegistration; solid:forClass schema:NoteDigitalDocument; solid:instanceContainer <${container}>.`,
  }), fetch);
```

---

On CSS 7.2 the private index then held:

```turtle
<> a <http://www.w3.org/ns/solid/terms#TypeIndex>, <http://www.w3.org/ns/solid/terms#UnlistedDocument>.
<#reg-notes-24f500a3> a <http://www.w3.org/ns/solid/terms#TypeRegistration>;
    <http://www.w3.org/ns/solid/terms#forClass> <http://schema.org/NoteDigitalDocument>;
    <http://www.w3.org/ns/solid/terms#instanceContainer> <../notes/>.
```

In another pod, beside another app's `<#notes>` registering `schema:Recipe`, the new `<#reg-notes-…>` left `<#notes>` as it was."""@en ;
    solid-memo:checkedBy <#q-read-an-app-4a> ,
                         <#q-read-an-app-4b> ,
                         <#q-read-an-app-4c> .

<#q-read-an-app-4a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "When writing to Community Solid Server 7.2 (2026), why does the Solid Notes example app give its type registration a fragment IRI (`<#reg-notes-…>`) instead of a blank node?"@en ;
    solid-memo:back "CSS 7.2 answers 422 to blank nodes in `solid:inserts`"@en ;
    solid-memo:backNote "Following the Solid Protocol 0.11 rule, CSS 7.2 answers 422 to a blank node in inserts or deletes, so new nodes get IRIs; the fragment resolves against the type index's URL."@en ;
    solid-memo:distractor <#q-read-an-app-4a-d1> ,
                          <#q-read-an-app-4a-d2> ,
                          <#q-read-an-app-4a-d3> .

<#q-read-an-app-4a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Blank nodes cannot have an `rdf:type` when written in Turtle"@en ;
    solid-memo:distractorNote "A blank node can have any properties, including a type."@en .

<#q-read-an-app-4a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A type index may hold only one registration per document"@en ;
    solid-memo:distractorNote "A type index can hold many registrations."@en .

<#q-read-an-app-4a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The fragment tells other apps which app owns the registration"@en ;
    solid-memo:distractorNote "The name carries no ownership; any app may use the registration."@en .

<#q-read-an-app-4b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On Community Solid Server 7.2 (2026) a fresh pod has no type index. What does the Solid Notes example app do before it registers the user's notes?"@en ;
    solid-memo:back "Asks her, then creates a private type index and a preferences file"@en ;
    solid-memo:backNote "New `settings/` files change her pod, so the app asks first; if she agrees, it creates both files, links the preferences file from the profile, then registers `schema:NoteDigitalDocument` in the private index."@en ;
    solid-memo:distractor <#q-read-an-app-4b-d1> ,
                          <#q-read-an-app-4b-d2> ,
                          <#q-read-an-app-4b-d3> .

<#q-read-an-app-4b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Creates a public type index, linked from the pod root's ACL"@en ;
    solid-memo:distractorNote "Indexes are linked from the profile or preferences file, and the app asks first."@en .

<#q-read-an-app-4b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing, because CSS 7 creates both type indexes with every pod"@en ;
    solid-memo:distractorNote "A fresh CSS 7.2 profile has no type index and no preferences file."@en .

<#q-read-an-app-4b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Writes a shape tree that declares where the notes container lives"@en ;
    solid-memo:distractorNote "Shape Trees are not used by CSS 7.2 or by this app."@en .

<#q-read-an-app-4c>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid user's private type index already has another app's `<#notes>` subject, which registers recipes. What happens when the Solid Notes example app registers its notes there?"@en ;
    solid-memo:back "It adds a new subject, `<#reg-notes-…>`; `<#notes>` stays as it was"@en ;
    solid-memo:backNote "An insert into an existing subject merges with it, so the app inserts under a fragment no other app is likely to use; on CSS 7.2 `<#notes>` still registered only `schema:Recipe` afterwards."@en ;
    solid-memo:distractor <#q-read-an-app-4c-d1> ,
                          <#q-read-an-app-4c-d2> ,
                          <#q-read-an-app-4c-d3> .

<#q-read-an-app-4c-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Its triples merge into `<#notes>`, which then registers both classes"@en ;
    solid-memo:distractorNote "That is what a shared fragment would do; Solid Notes picks a random one."@en .

<#q-read-an-app-4c-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "CSS refuses the patch, because `<#notes>` already exists there"@en ;
    solid-memo:distractorNote "An insert-only patch may add to any subject; the server doesn't check meaning."@en .

<#q-read-an-app-4c-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It PUTs a new index that holds only its own registration"@en ;
    solid-memo:distractorNote "That would delete the other app's registration; the app only inserts."@en .

<#ch-read-an-app-5>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-an-app> ;
    schema:position 4 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Creating a container and a document

With the container URL from the registration, the app makes sure the container exists, then adds a note. A container is created with PUT on a URL ending in `/`. A second PUT on an existing container gets 409 on CSS (Step 6.5), so the app checks with HEAD first. A note is created with POST to the container: the server picks the URL, the `Slug` header is only a hint, and the app must read `Location` (Step 6.4).

```js
// src/notes.js
export async function createNotesContainer(container, fetch) {
  const head = await fetch(container, { method: 'HEAD' });
  if (head.ok) return container;
  if (head.status !== 404) throw new HttpError('HEAD', container, head);
  ok('PUT', container, await fetch(container, { method: 'PUT', headers: { 'content-type': 'text/turtle' } }));
  return container;
}

export async function createNote(container, text, fetch, slug = 'note') {
  const res = ok('POST', container, await fetch(container, {
    method: 'POST',
    headers: { 'content-type': 'text/turtle', slug },
    body: `<#it> a <${NOTE}>; <${ns.schema}text> ${literal(text)}.`,
  }));
  return new URL(res.headers.get('location'), container).href;
}
```

`ok` throws unless the status is 2xx. `literal` is `JSON.stringify(String(text))`: JSON's escapes (`\\"`, `\\\\`, `\\n`, `\\uXXXX`) are also valid Turtle, so text the user types can't break out of the string.

---

With `Slug: first`, CSS 7.2 answered `Location: http://localhost:3000/alice40742/notes/first`; node-solid-server 6.0.0 answered `…/notes/first.ttl`.

Deleting works the same way as editing (Step 6.11): send the ETag you read in `If-Match`. On CSS 7.2 a DELETE with a stale ETag got 412, the one with the fresh ETag got 205, and a GET afterwards got 404."""@en ;
    solid-memo:checkedBy <#q-read-an-app-5a> ,
                         <#q-read-an-app-5b> .

<#q-read-an-app-5a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app POSTs a note to a container with `Slug: first`. Why does it read `Location` instead of building the URL from the container and the slug?"@en ;
    solid-memo:back "The slug is only a hint; the server picks the final URL"@en ;
    solid-memo:backNote "POST lets the server choose the URL; CSS 7.2 kept the slug exactly and node-solid-server 6 added `.ttl`, so the app always uses `Location`."@en ;
    solid-memo:distractor <#q-read-an-app-5a-d1> ,
                          <#q-read-an-app-5a-d2> ,
                          <#q-read-an-app-5a-d3> .

<#q-read-an-app-5a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`Location` also tells the app the note's ETag for later edits"@en ;
    solid-memo:distractorNote "Location carries only the URL; the ETag comes from a GET or HEAD."@en .

<#q-read-an-app-5a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`Location` is needed only on NSS; CSS always keeps the slug"@en ;
    solid-memo:distractorNote "CSS kept it here, but no server promises to."@en .

<#q-read-an-app-5a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A slug must be percent-encoded, so the stored name always differs"@en ;
    solid-memo:distractorNote "A plain slug like `first` is used as is when the server accepts it."@en .

<#q-read-an-app-5b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front """On Community Solid Server 7.2 (2026), a Solid app deletes a note with the function below (`ok` throws unless the status is 2xx). Another user edited the note after `etag` was read. What happens?

```js
export async function deleteNote(url, fetch, etag) {
  const headers = etag ? { 'if-match': etag } : {};
  return ok('DELETE', url, await fetch(url, { method: 'DELETE', headers }));
}
```"""@en ;
    solid-memo:back "The server answers 412 and `ok` throws; the note stays"@en ;
    solid-memo:backNote "In HTTP, `If-Match` makes the DELETE conditional on the version that was read; on CSS 7.2 the stale ETag got 412 and the fresh one deleted the note with 205. A server that ignores `If-Match` (node-solid-server 6 did on PATCH) gives no such guard."@en ;
    solid-memo:distractor <#q-read-an-app-5b-d1> ,
                          <#q-read-an-app-5b-d2> ,
                          <#q-read-an-app-5b-d3> .

<#q-read-an-app-5b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The DELETE succeeds, since servers ignore `If-Match` on DELETE"@en ;
    solid-memo:distractorNote "Conditional headers apply to every method; CSS 7.2 refused it with 412."@en .

<#q-read-an-app-5b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server answers 409 and `ok` throws; the note stays"@en ;
    solid-memo:distractorNote "A failed precondition is 412; 409 is for a conflicting request body."@en .

<#q-read-an-app-5b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The note is deleted, then the server answers 412 as a warning"@en ;
    solid-memo:distractorNote "The precondition is checked before anything changes."@en .

<#ch-read-an-app-6>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-an-app> ;
    schema:position 5 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Reading and rendering safely

`readNotes` GETs the container and follows each `ldp:contains`. It skips anything whose `Content-Type` isn't `text/turtle` (such as pictures), parses each note with the `n3` library, and keeps a document only if it has a subject typed `schema:NoteDigitalDocument`. Parsing Turtle with an RDF library gives the same triples from any server; CSS's JSON-LD comes out expanded, in a shape a plain-JSON reader would have to special-case.

---

What it reads is **untrusted input** (Step 13.1): any app that can write to the pod could have put HTML or a `javascript:` URL in a note. `renderNote` therefore sets text with `textContent` and only turns `http:`/`https:` values into links.

```js
// src/render.js
export function renderNote(note, document) {
  const li = document.createElement('li');
  const text = document.createElement('span');
  text.textContent = note.text; // never innerHTML: "<img onerror=…>" stays text
  li.append(text);
  if (note.link && /^https?:$/.test(safeProtocol(note.link))) {
    const a = document.createElement('a');
    a.href = note.link;
    a.rel = 'noopener noreferrer';
    a.textContent = new URL(note.link).host;
    li.append(' ', a);
  }
  return li;
}

const safeProtocol = (url) => {
  try { return new URL(url).protocol; } catch { return ''; } // javascript:, data:, junk
};
```

---

A test wrote a hostile note (`schema:text "<img src=x onerror=alert(1)>"`, `schema:url "javascript:alert(1)"`) and a safe one, and rendered both:

```text
<li><span>&lt;img src=x onerror=alert(1)&gt;</span></li>
<li><span>docs</span> <a rel="noopener noreferrer" href="https://solidproject.org/">solidproject.org</a></li>
```

No `<img>` element and no link for the hostile note. The values `data:text/html,…`, `not a url`, `JavaScript:alert(1)` and `ftp://example.org/x` gave no link either."""@en ;
    solid-memo:checkedBy <#q-read-an-app-6a> ,
                         <#q-read-an-app-6b> ,
                         <#q-read-an-app-6c> ,
                         <#q-read-an-app-6d> .

<#q-read-an-app-6a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A note in a Solid pod has the text `<img src=x onerror=alert(1)>`. Which way of showing it in a web app keeps it harmless?"@en ;
    solid-memo:back "Setting `textContent`, which shows the string without parsing markup"@en ;
    solid-memo:backNote "`textContent` never parses markup, so the string is shown as text; pod data is untrusted input whoever wrote it."@en ;
    solid-memo:distractor <#q-read-an-app-6a-d1> ,
                          <#q-read-an-app-6a-d2> ,
                          <#q-read-an-app-6a-d3> .

<#q-read-an-app-6a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Setting `innerHTML`, since only logged-in users can write to the pod"@en ;
    solid-memo:distractorNote "Logged-in users and their apps can still write hostile strings."@en .

<#q-read-an-app-6a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Setting `innerHTML` once the note's `Content-Type` is `text/turtle`"@en ;
    solid-memo:distractorNote "The media type says nothing about what the literal contains."@en .

<#q-read-an-app-6a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Stripping `<script>` tags with a regular expression, then `innerHTML`"@en ;
    solid-memo:distractorNote "The attack uses an event handler on an img tag, not a script tag."@en .

<#q-read-an-app-6b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In the Solid Notes example app, a note's `schema:url` is `javascript:alert(1)`. What does `renderNote` do with it?"@en ;
    solid-memo:back "Shows no link: only `http:` and `https:` values become links"@en ;
    solid-memo:backNote "`renderNote` parses the value and allows only the `http:` and `https:` protocols, so `javascript:`, `data:` and junk values are dropped."@en ;
    solid-memo:distractor <#q-read-an-app-6b-d1> ,
                          <#q-read-an-app-6b-d2> ,
                          <#q-read-an-app-6b-d3> .

<#q-read-an-app-6b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Shows a link with `rel=\"noopener\"`, which blocks the script"@en ;
    solid-memo:distractorNote "noopener isolates the opened window; it doesn't stop javascript: URLs."@en .

<#q-read-an-app-6b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Shows a link, because browsers block `javascript:` in `href`"@en ;
    solid-memo:distractorNote "Browsers run javascript: URLs when such a link is clicked."@en .

<#q-read-an-app-6b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Throws, because `new URL` rejects the `javascript:` scheme"@en ;
    solid-memo:distractorNote "new URL parses it fine; the app checks the protocol itself."@en .

<#q-read-an-app-6c>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid notes container holds a PNG picture next to Turtle notes. What does the Solid Notes example app's `readNotes` do with the PNG?"@en ;
    solid-memo:back "Skips it, because its `Content-Type` isn't `text/turtle`"@en ;
    solid-memo:backNote "`readNotes` keeps only Turtle documents with a `schema:NoteDigitalDocument` subject; on CSS 7.2, after an upload it still listed 2 notes and not the picture."@en ;
    solid-memo:distractor <#q-read-an-app-6c-d1> ,
                          <#q-read-an-app-6c-d2> ,
                          <#q-read-an-app-6c-d3> .

<#q-read-an-app-6c-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Parses it as Turtle, and the whole list fails with an error"@en ;
    solid-memo:distractorNote "readNotes checks the media type first and moves on."@en .

<#q-read-an-app-6c-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Lists it as a note whose text is the picture's description"@en ;
    solid-memo:distractorNote "The description lives in a separate resource that readNotes never reads."@en .

<#q-read-an-app-6c-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Asks for it as JSON-LD, since every resource has an RDF form"@en ;
    solid-memo:distractorNote "A PNG has no RDF form; only its description resource does."@en .

<#q-read-an-app-6d>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front """A Solid app turns a note's link into an HTML link only when this check passes. Does `HTTPS://example.org/x`, with an uppercase scheme, pass, and why?

```js
const safeProtocol = (url) => {
  try { return new URL(url).protocol; } catch { return ''; }
};
const linkable = (url) => /^https?:$/.test(safeProtocol(url));
```"""@en ;
    solid-memo:back "Yes: the URL parser lowercases the scheme to `https:`"@en ;
    solid-memo:backNote "The URL parser lowercases the scheme, so `HTTPS:` becomes `https:` and matches the pattern. The same lowercasing turns `JavaScript:` into `javascript:`, which fails."@en ;
    solid-memo:distractor <#q-read-an-app-6d-d1> ,
                          <#q-read-an-app-6d-d2> ,
                          <#q-read-an-app-6d-d3> ,
                          <#q-read-an-app-6d-d4> ,
                          <#q-read-an-app-6d-d5> ,
                          <#q-read-an-app-6d-d6> .

<#q-read-an-app-6d-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "`JavaScript:alert(1)`" ;
    solid-memo:distractorNote "Its protocol is `javascript:` once parsed, which the pattern rejects."@en .

<#q-read-an-app-6d-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "`ftp://example.org/x`" ;
    solid-memo:distractorNote "`ftp:` is a valid protocol but not `http:` or `https:`."@en .

<#q-read-an-app-6d-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "`//example.org/x`" ;
    solid-memo:distractorNote "Without a base, `new URL` throws, so the protocol is empty."@en .

<#q-read-an-app-6d-d4>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "No: the pattern has no `i` flag, so `HTTPS:` never matches"@en ;
    solid-memo:distractorNote "The pattern never sees `HTTPS:`: `new URL` has already lowercased the protocol to `https:`, which matches."@en .

<#q-read-an-app-6d-d5>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "No: `new URL` throws on it, so the protocol is empty"@en ;
    solid-memo:distractorNote "An uppercase scheme is valid; `new URL` parses it and returns the protocol `https:`."@en .

<#q-read-an-app-6d-d6>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Yes: `test` matches letters without regard to case"@en ;
    solid-memo:distractorNote "`test` is case-sensitive unless the pattern has the `i` flag. It passes because the parser lowercased the scheme first."@en .

<#ch-read-an-app-7>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-an-app> ;
    schema:position 6 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Editing with N3 Patch and `If-Match`

Editing a note means replacing one triple: delete the old `schema:text`, insert the new one (Steps 6.7-6.8). To avoid lost updates the app sends the ETag it read in `If-Match` (Step 6.11). If someone changed the note in between, CSS answers **412**; the app reads the note again, applies the user's change to the *fresh* text, and retries once.

```js
// src/notes.js
export async function editNote(url, change, fetch) {
  let retriedAfter;
  for (let attempt = 1; ; attempt += 1) {
    const { quads, etag } = await readTurtle(url, fetch);
    const it = `${url}#it`;
    const [old] = objects(quads, it, `${ns.schema}text`);
    const body = n3Patch({
      deletes: `<${it}> schema:text ${literal(old)}.`,
      inserts: `<${it}> schema:text ${literal(change(old))}.`,
    });
    // node-solid-server 6 sends no ETag on GET: then only the deletes guard the edit.
    const headers = etag ? { 'if-match': etag } : {};
    try {
      const res = await patch(url, body, fetch, headers);
      return { status: res.status, attempt, retriedAfter, conditional: Boolean(etag) };
    } catch (e) {
      // 412: stale ETag. 409: the text we delete is no longer there. Both mean "changed".
      if (![409, 412].includes(e.status) || attempt === 2) throw e;
      retriedAfter = e.status;
    }
  }
}
```

---

`change` is a function, not a value, so the retry can decide what to do with whatever text is there now. A change that returns the typed text no matter what would overwrite the other edit: the very lost update `If-Match` caught. So the Edit button asks when the fresh text isn't what the user saw:

```js
// src/main.js (Edit)
await editNote(note.url, (fresh) => (fresh === note.text
  || window.confirm(`Someone changed this note to:\\n\\n${fresh}\\n\\nReplace it with your text?`)
  ? text : fresh), fetch);
```

On CSS 7.2, with another edit made between the read and the PATCH:

```text
plain edit: {"status":205,"attempt":1,"conditional":true}
edit that lost a race, then retried: {"status":205,"attempt":2,"retriedAfter":412,"conditional":true}
text now: Edited elsewhere (and by me)
```

CSS answers a successful PATCH with 205; both edits survive."""@en ;
    solid-memo:checkedBy <#q-read-an-app-7a> ,
                         <#q-read-an-app-7b> ,
                         <#q-read-an-app-7c> .

<#q-read-an-app-7a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In the Solid Notes example app, `editNote`'s conditional PATCH comes back 412 Precondition Failed. What does it do next?"@en ;
    solid-memo:back "Rereads the note and reapplies the change"@en ;
    solid-memo:backNote "412 says the ETag is stale, so the app must base its change on the current state: read, recompute the patch, retry with the new ETag."@en ;
    solid-memo:distractor <#q-read-an-app-7a-d1> ,
                          <#q-read-an-app-7a-d2> ,
                          <#q-read-an-app-7a-d3> .

<#q-read-an-app-7a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Sends the same PATCH again without `If-Match`"@en ;
    solid-memo:distractorNote "That would overwrite the other edit, the lost update If-Match prevents."@en .

<#q-read-an-app-7a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Waits for a notification, then sends the same PATCH"@en ;
    solid-memo:distractorNote "The PATCH would still delete text that is gone, so it fails with 409."@en .

<#q-read-an-app-7a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Gives up, because 412 means the user lacks Write access"@en ;
    solid-memo:distractorNote "Missing access is 403; 412 means the resource changed."@en .

<#q-read-an-app-7b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "In the Solid Notes example app in the browser, alice's edit is retried and finds that bob changed the note in the meantime. What does the app do?"@en ;
    solid-memo:back "Asks alice whether to replace bob's text with hers"@en ;
    solid-memo:backNote "The Edit button's change function keeps the typed text only if the fresh text is what alice saw, or if she confirms; otherwise it writes the fresh text back unchanged."@en ;
    solid-memo:distractor <#q-read-an-app-7b-d1> ,
                          <#q-read-an-app-7b-d2> ,
                          <#q-read-an-app-7b-d3> .

<#q-read-an-app-7b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Overwrites bob's text, because alice pressed Edit first"@en ;
    solid-memo:distractorNote "That is the lost update; who clicked first doesn't matter."@en .

<#q-read-an-app-7b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Merges both texts line by line without asking either user"@en ;
    solid-memo:distractorNote "That would need a merging change function; the Edit button asks."@en .

<#q-read-an-app-7b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Shows an error and throws away the text alice typed"@en ;
    solid-memo:distractorNote "editNote retries, and the change function decides what to write."@en .

<#q-read-an-app-7c>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front """A Solid app's `editNote(url, change, fetch)` reads a note, writes `change(text)` with `If-Match`, and on a 412 rereads and calls `change` with the fresh text. The note says `Shopping`; another user appends a line `milk` before the first PATCH arrives. What does the note say after this call?

```js
const appendLine = (line) => (text) => (text ? `${text}\\n${line}` : line);
await editNote(url, appendLine('bread'), fetch);
```"""@en ;
    solid-memo:back "`Shopping`, `milk` and `bread`, one per line"@en ;
    solid-memo:backNote "The retry applies the change to the fresh text, so both appended lines survive and nobody has to be asked; on CSS 7.2 the result was `Shopping\\nmilk\\nbread` after a 412 and a second attempt."@en ;
    solid-memo:distractor <#q-read-an-app-7c-d1> ,
                          <#q-read-an-app-7c-d2> ,
                          <#q-read-an-app-7c-d3> .

<#q-read-an-app-7c-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`Shopping` and `bread`, one per line; `milk` is lost"@en ;
    solid-memo:distractorNote "That is the lost update; the retry rereads the text that includes milk."@en .

<#q-read-an-app-7c-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`Shopping` and `milk`, one per line; the edit fails"@en ;
    solid-memo:distractorNote "editNote retries once after a 412, and the retry succeeds."@en .

<#q-read-an-app-7c-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`Shopping`, `bread` and `milk`, one per line"@en ;
    solid-memo:distractorNote "milk was already there when the retry appended bread."@en .

<#ch-read-an-app-8>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-an-app> ;
    schema:position 7 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Uploading a picture

A picture is a non-RDF resource (Step 6.6): POST the bytes with their own `Content-Type` (in the browser, the file input's `file.type`) and read `Location`. Its metadata can't go inside a PNG, so the app writes it to the picture's description resource, using an N3 Patch.

The app doesn't build that resource's URL by appending `.meta`: the name is the server's choice (`pixel.meta` on CSS 7.2, `pixel.png.meta` on node-solid-server 6), so it HEADs the picture and follows `rel="describedby"`. It compares relation names without regard to case, because NSS 6 sends `describedBy`. And it only PATCHes: CSS 7.2 allows no PUT on a description resource, whose `Allow` header lists only `OPTIONS, HEAD, GET, PATCH`.

```js
// src/notes.js
export async function uploadPicture(container, bytes, description, fetch, { slug = 'picture', type = 'image/png' } = {}) {
  const res = ok('POST', container, await fetch(container, {
    method: 'POST', headers: { 'content-type': type, slug }, body: bytes,
  }));
  const url = new URL(res.headers.get('location'), container).href;
  const [describedBy] = linksOf(await fetch(url, { method: 'HEAD' }), 'describedby', url);
  if (describedBy) {
    await patch(describedBy, n3Patch({ inserts: `<${url}> schema:description ${literal(description)}.` }), fetch);
  }
  return { url, describedBy };
}
```

---

On CSS 7.2 a one-pixel PNG posted with `Slug: pixel` became `…/notes/pixel`, described by `…/notes/pixel.meta`, which then read (`<pixel>` is relative to `…/notes/pixel.meta`):

```turtle
@prefix dc: <http://purl.org/dc/terms/>.
@prefix ldp: <http://www.w3.org/ns/ldp#>.
@prefix posix: <http://www.w3.org/ns/posix/stat#>.
@prefix xsd: <http://www.w3.org/2001/XMLSchema#>.

<pixel> <http://www.w3.org/ns/ma-ont#format> "image/png";
    a ldp:Resource;
    dc:modified "2026-10-07T21:49:02.189Z"^^xsd:dateTime;
    posix:size "70";
    <http://schema.org/description> "A one-pixel test image".
```

NSS 6 stored `pixel.png` and answered GET on its `.meta` with 404, although the PATCH was stored. To list pictures, an app HEADs each contained resource, keeps those whose `Content-Type` starts with `image/`, and reads `schema:description` from the `describedby` target."""@en ;
    solid-memo:checkedBy <#q-read-an-app-8a> .

<#q-read-an-app-8a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Where does the Solid Notes example app store the text description of a PNG it uploaded to a Solid pod?"@en ;
    solid-memo:back "In the resource the PNG's `describedby` link points to, via N3 Patch"@en ;
    solid-memo:backNote "A binary resource's metadata lives in its description resource, found through `Link` `rel=\"describedby\"`, and is edited with an N3 Patch."@en ;
    solid-memo:distractor <#q-read-an-app-8a-d1> ,
                          <#q-read-an-app-8a-d2> ,
                          <#q-read-an-app-8a-d3> .

<#q-read-an-app-8a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In the PNG itself, via a PATCH sent with `Content-Type: image/png`"@en ;
    solid-memo:distractorNote "N3 Patch edits RDF; the PNG's bytes are not RDF."@en .

<#q-read-an-app-8a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In the container listing, as a triple added with a PUT"@en ;
    solid-memo:distractorNote "PUT on an existing container is a 409 on CSS, and the listing is server-managed."@en .

<#q-read-an-app-8a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "At the PNG's URL plus `.meta`, written with a PUT of Turtle"@en ;
    solid-memo:distractorNote "The name is the server's choice (NSS 6: `pixel.png.meta`), and CSS 7.2 allows no PUT there."@en .

<#ch-read-an-app-9>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-an-app> ;
    schema:position 8 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Sharing a note (WAC)

To share a note, `shareNote` follows Step 9.3: check `WAC-Allow` for Control, follow `rel="acl"`, then add a rule to the existing ACL with an insert-only N3 Patch, or create one. A new ACL replaces inheritance (Step 8.6), so it **restates alice's own Read, Write and Control**. An ACP server gets another branch (Step 14.12).

```js
// src/share.js (WAC branch)
  const reader = `<#reader-${crypto.randomUUID()}> a acl:Authorization;
  acl:agent <${friend}>; acl:accessTo <${url}>; acl:mode acl:Read.`;
  if (existing.ok) {
    await patch(rules, n3Patch({ inserts: reader }), fetch); // add to the ACL it already has
  } else {
    // A resource's own ACL replaces the inherited rules (Step 8.6), so restate the owner.
    await put(rules, `@prefix acl: <${ns.acl}>.
<#owner> a acl:Authorization;
  acl:agent <${owner}>; acl:accessTo <${url}>; acl:mode acl:Read, acl:Write, acl:Control.
${reader}`, fetch);
  }
```

On CSS 7.2, bob's GET then got 200 with `WAC-Allow: user="read"`, and his PATCH 403.

---

⚠ An ACL with only a public-Read rule left alice `WAC-Allow: user="read",public="read"`: PUT on the note, and GET, PUT and DELETE on its ACL, all got 403. CSS 7.2's owner rescue applies only to configurations with storages at the pods, not the default. WAC promises no rescue.

To unshare, the app deletes the friend's authorization triples with one N3 Patch, copied from the ACL it just read: deletes must match exactly. A list several people add to (Step 9.10) needs only Append: each add is an insert-only patch with a fresh `<#item-…>` IRI. On CSS 7.2 bob, with Append and Read, got 205 for an add, 403 for PUT and for deletes, and 422 for a blank node. Two simultaneous adds, by bob and carol, were both kept."""@en ;
    solid-memo:checkedBy <#q-read-an-app-9a> ,
                         <#q-read-an-app-9b> ,
                         <#q-read-an-app-9c> .

<#q-read-an-app-9a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In WAC, a Solid app creates the first ACL for alice's note to share it with bob. Why does that ACL also contain a rule giving alice Read, Write and Control?"@en ;
    solid-memo:back "The note's own ACL replaces inherited rules; she'd lose access"@en ;
    solid-memo:backNote "Once a document has its own ACL, inherited `acl:default` rules no longer apply to it; on CSS 7.2's default configuration, leaving her out cost alice Write on the note and all access to its ACL."@en ;
    solid-memo:distractor <#q-read-an-app-9a-d1> ,
                          <#q-read-an-app-9a-d2> ,
                          <#q-read-an-app-9a-d3> .

<#q-read-an-app-9a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "WAC rejects any ACL that doesn't name the pod's owner"@en ;
    solid-memo:distractorNote "WAC has no such rule; CSS 7.2 accepted such an ACL with 201."@en .

<#q-read-an-app-9a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It records who shared the note, so bob can see the sender"@en ;
    solid-memo:distractorNote "Bob can't read the ACL; the sender goes in the inbox message."@en .

<#q-read-an-app-9a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Bob's Read works only if someone with Write is listed too"@en ;
    solid-memo:distractorNote "Each authorization stands alone; Read needs no other rule."@en .

<#q-read-an-app-9b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "In WAC, a note's ACL already exists when its owner shares it with a second friend. How does the Solid Notes example app add the friend?"@en ;
    solid-memo:back "With an insert-only N3 Patch adding one authorization"@en ;
    solid-memo:backNote "An insert-only patch keeps the existing rules, including the owner's Control and the first friend's Read."@en ;
    solid-memo:distractor <#q-read-an-app-9b-d1> ,
                          <#q-read-an-app-9b-d2> ,
                          <#q-read-an-app-9b-d3> .

<#q-read-an-app-9b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "With a PUT of a new ACL that lists only the second friend"@en ;
    solid-memo:distractorNote "That would drop the owner and the first friend from the ACL."@en .

<#q-read-an-app-9b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "With a POST to the ACL, the way messages go to an inbox"@en ;
    solid-memo:distractorNote "ACLs are documents edited with PUT or PATCH, not containers."@en .

<#q-read-an-app-9b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "By adding the friend to the pod root's ACL instead"@en ;
    solid-memo:distractorNote "The root's rules no longer apply once the note has its own ACL."@en .

<#q-read-an-app-9c>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "To unshare a note in WAC, a Solid app sends an N3 Patch whose `solid:deletes` lists the friend's authorization triples. Why does it build those triples from the ACL it has just read?"@en ;
    solid-memo:back "Deletes must match stored triples exactly, or the patch fails with 409"@en ;
    solid-memo:backNote "An N3 Patch whose deletes aren't all in the document is refused with 409, so the app copies the triples it read; on CSS 7.2 bob's GET went back to 403 and alice kept 200."@en ;
    solid-memo:distractor <#q-read-an-app-9c-d1> ,
                          <#q-read-an-app-9c-d2> ,
                          <#q-read-an-app-9c-d3> .

<#q-read-an-app-9c-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Deletes may name only subjects, so it needs the rule's fragment"@en ;
    solid-memo:distractorNote "N3 Patch deletes whole triples, not subjects."@en .

<#q-read-an-app-9c-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Each GET of an ACL renames its rules, so old names are stale"@en ;
    solid-memo:distractorNote "Servers keep the fragment IRIs that were written."@en .

<#q-read-an-app-9c-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server ignores deletes unless they come with `If-Match`"@en ;
    solid-memo:distractorNote "If-Match is optional; the exact match of deletes is the check."@en .

<#ch-read-an-app-10>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-an-app> ;
    schema:position 9 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Telling the friend: an inbox message

Bob can now read the note, but he doesn't know it exists. `notifyFriend` reads his profile, finds `ldp:inbox` and POSTs an Activity Streams `Announce` there (Step 9.6). The server names the message and returns `Location`.

```js
// src/share.js
  const [inbox] = objects(quads, friend, `${ns.ldp}inbox`);
  if (!inbox) throw new Error(`${friend} has no ldp:inbox`);
  const res = ok('POST', inbox, await fetch(inbox, {
    method: 'POST',
    headers: { 'content-type': 'application/ld+json' },
    body: JSON.stringify({ '@context': 'https://www.w3.org/ns/activitystreams',
      type: 'Announce', actor, object, target: friend, summary: 'A note was shared with you' }),
  }));
```

---

CSS 7.2 creates no inbox, so the test setup makes one in bob's pod, with an ACL that gives the public Append and bob Read, Write and Control (with `acl:default`, so it covers the messages too). Anyone can drop a message in; only bob can read them: alice's GET on her own message got 403, bob's 200.

On bob's side, a message is only a claim (Step 9.7). An app can mark it `verified` when its `object` lies in the actor's storage **and** bob's own fetch gets it. On CSS 7.2 a message about a never-shared note and one pointing into a third pod failed that check, but a forged message about alice's public profile passed. To tidy the inbox, copy a message into an archive with `If-None-Match: *`, and only then DELETE it."""@en ;
    solid-memo:checkedBy <#q-read-an-app-10a> ,
                         <#q-read-an-app-10b> ,
                         <#q-read-an-app-10c> .

<#q-read-an-app-10a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In a Solid pod, bob's inbox gives the public Append and only bob Read. Alice POSTs an `Announce` there and then GETs the message's URL. Why does she get 403?"@en ;
    solid-memo:back "The inbox gives the public Append only, not Read"@en ;
    solid-memo:backNote "The inbox's ACL lets anyone append (post) but only bob read, so senders can deliver messages without seeing each other's."@en ;
    solid-memo:distractor <#q-read-an-app-10a-d1> ,
                          <#q-read-an-app-10a-d2> ,
                          <#q-read-an-app-10a-d3> .

<#q-read-an-app-10a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "CSS deletes inbox messages as soon as they are delivered"@en ;
    solid-memo:distractorNote "Bob read the same message afterwards with a 200."@en .

<#q-read-an-app-10a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Her token is valid only for resources in her own pod"@en ;
    solid-memo:distractorNote "She got 403, not 401: the pod recognised her token but gives her no Read."@en .

<#q-read-an-app-10a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Messages in an inbox are readable by apps only, not users"@en ;
    solid-memo:distractorNote "Rules name agents; bob reads his messages with his own login."@en .

<#q-read-an-app-10b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app archives an inbox message by PUTting a copy into an archive container with `If-None-Match: *`, then DELETEing the original. On a retry, a 412 on the PUT with the same bytes already there means it goes on to the DELETE. The PUT succeeds, but the DELETE fails with a network error. What does the user have?"@en ;
    solid-memo:back "The message twice, in the inbox and in the archive"@en ;
    solid-memo:backNote "Copying first means a failure in between leaves a duplicate, never a loss; the retry's 412 shows the copy is already there, so it finishes the DELETE."@en ;
    solid-memo:distractor <#q-read-an-app-10b-d1> ,
                          <#q-read-an-app-10b-d2> ,
                          <#q-read-an-app-10b-d3> .

<#q-read-an-app-10b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "No copy at all, because the PUT is rolled back"@en ;
    solid-memo:distractorNote "Each HTTP request stands alone; nothing undoes the PUT."@en .

<#q-read-an-app-10b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only the archived copy, because CSS finishes the delete later"@en ;
    solid-memo:distractorNote "The DELETE was never confirmed; on CSS 7.2 the inbox still listed the message."@en .

<#q-read-an-app-10b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A stuck message: the next attempt gets 412 and stops"@en ;
    solid-memo:distractorNote "The 412 means the copy is there; the app checks its bytes and goes on to the DELETE."@en .

<#q-read-an-app-10c>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid inbox message says alice shared her public profile document with bob. Bob's app checks that the document lies in alice's storage and that bob's own fetch gets it with a 2xx. If both checks pass, what does that show?"@en ;
    solid-memo:back "The document is in alice's storage and bob may read it"@en ;
    solid-memo:backNote "The check rules out a private note never shared and a page in someone else's pod, but not who wrote the message; on CSS 7.2 a forged message about alice's public profile passed it."@en ;
    solid-memo:distractor <#q-read-an-app-10c-d1> ,
                          <#q-read-an-app-10c-d2> ,
                          <#q-read-an-app-10c-d3> .

<#q-read-an-app-10c-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Alice sent the message, and the document is in her storage"@en ;
    solid-memo:distractorNote "Anyone with Append can put alice's WebID in `actor`."@en .

<#q-read-an-app-10c-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Alice gave bob access to the document, and he may read it"@en ;
    solid-memo:distractorNote "Her profile is public; bob could read it before any message."@en .

<#q-read-an-app-10c-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Bob's app may show it as \"alice shared this with you\""@en ;
    solid-memo:distractorNote "The check can't tell a share from a page that was readable anyway."@en .

<#ch-read-an-app-11>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-an-app> ;
    schema:position 10 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Subscribing to changes

To keep the screen current, the app subscribes with **WebSocketChannel2023** (Steps 10.2-10.5 and 10.7). It follows the topic's `storageDescription` link, finds the subscription service whose `notify:channelType` is WebSocketChannel2023, POSTs a subscription, and opens a WebSocket to `receiveFrom`. A message says *that* something changed, not what: on `Update` the app refetches (the message's `state` is the new ETag), on `Delete` it drops the note. If the server offers no such service, `subscribe` returns `null` and the app says "reload to see changes". If the socket closes later, for example because the server restarted, `onClose` lets the app say live updates are off; Step 10.9 covers reconnecting.

```js
// src/live.js
  const { receiveFrom } = await res.json();
  const socket = new WebSocket(receiveFrom);
  socket.onmessage = (event) => {
    const message = JSON.parse(event.data);
    if (/Delete$/.test(message.type)) onDelete(message);
    else onUpdate(message); // Update (state = the new ETag); a container also sends Add, Remove
  };
  await new Promise((resolve, reject) => { socket.onopen = resolve; socket.onerror = reject; });
  socket.onclose = () => onClose();
```

---

On CSS 7.2, a subscription to one note, which was then edited and deleted, received:

```text
{…,"type":"Update","object":"http://localhost:3000/alice40742/notes/first","state":"\\"1791409742758-text/turtle\\"","published":"2026-10-07T21:49:02.761Z"}
{…,"type":"Delete","object":"http://localhost:3000/alice40742/notes/first","published":"2026-10-07T21:49:02.782Z"}
```

The `state` equalled the ETag a HEAD returned after the edit; the Delete message has no `state`."""@en ;
    solid-memo:checkedBy <#q-read-an-app-11a> .

<#q-read-an-app-11a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app subscribed with WebSocketChannel2023 receives an `Update` message for a note. How does it learn the note's new text?"@en ;
    solid-memo:back "It GETs the note again; the message carries no content"@en ;
    solid-memo:backNote "Notifications say that a resource changed (`state` is its new ETag); to see what changed, the app refetches it."@en ;
    solid-memo:distractor <#q-read-an-app-11a-d1> ,
                          <#q-read-an-app-11a-d2> ,
                          <#q-read-an-app-11a-d3> .

<#q-read-an-app-11a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It reads the new text from the message's `object` field"@en ;
    solid-memo:distractorNote "object is the note's URL, not its content."@en .

<#q-read-an-app-11a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It applies the N3 Patch that comes inside the message"@en ;
    solid-memo:distractorNote "Messages carry no patch; they only announce the change."@en .

<#q-read-an-app-11a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It waits for a second message listing the changed triples"@en ;
    solid-memo:distractorNote "There is no second message; the client must refetch."@en .

<#ch-read-an-app-12>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-an-app> ;
    schema:position 11 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Sharing on an ACP server

The same code was run against a second CSS 7.2, configured with Access Control Policy (Step 9.4) instead of WAC.

There `rel="acl"` points to `first.acr`, and a HEAD on it, even a 404, carries `Link: <…acp#AccessControlResource>; rel="type"`. That type, not the URL's suffix, tells `shareNote` to take its ACP branch. ACP only adds (Step 9.4): the pod root's `acp:memberAccessControl` keeps applying, so alice needs no restating. One insert-only N3 Patch creates the ACR (201) or adds to it (205), with fragment IRIs for the access control, policy and matcher, because blank nodes are refused in inserts.

---

The library route did worse. Step 9.5 introduced `universalAccess.setAgentAccess` as one call for both WAC and ACP. On CSS 7.2 with WAC it worked. With ACP, a new resource has no ACR yet, and the call returned `null` without sharing: bob stayed at 403. Always check its return value.

```js
// src/share.js (ACP branch)
  const id = `${acr}#friend-${crypto.randomUUID()}`;
  await patch(acr, n3Patch({
    inserts: `<${acr}> a acp:AccessControlResource; acp:resource <${url}>; acp:accessControl <${id}>.
<${id}> a acp:AccessControl; acp:apply <${id}-policy>.
<${id}-policy> a acp:Policy; acp:allow acl:Read; acp:anyOf <${id}-matcher>.
<${id}-matcher> a acp:Matcher; acp:agent <${friend}>.`,
  }), fetch);
```

On CSS 7.2 with ACP:

```text
shared via acp (http://localhost:3001/alice45887/notes/first.acr); bob GET: 200, WAC-Allow null; alice: 200, WAC-Allow null
setAgentAccess returned null
bob GET: 403 null; alice: 200 null
```

No response carried `WAC-Allow`."""@en ;
    solid-memo:checkedBy <#q-read-an-app-12a> ,
                         <#q-read-an-app-12b> .

<#q-read-an-app-12a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On Community Solid Server 7.2 (2026) configured with ACP, how does the Solid Notes example app's `shareNote` know to write an ACP policy instead of a WAC rule?"@en ;
    solid-memo:back "Its `rel=\"acl\"` target is typed `acp:AccessControlResource`"@en ;
    solid-memo:backNote "CSS links an ACR with `rel=\"acl\"` too; a HEAD on it (even a 404) carries `Link` `rel=\"type\"` `acp:AccessControlResource`, which is how the app tells ACP from WAC."@en ;
    solid-memo:distractor <#q-read-an-app-12a-d1> ,
                          <#q-read-an-app-12a-d2> ,
                          <#q-read-an-app-12a-d3> .

<#q-read-an-app-12a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Its `WAC-Allow` header lists `acp` as one of the modes"@en ;
    solid-memo:distractorNote "CSS 7.2 with ACP sent no WAC-Allow at all, and WAC-Allow has no ACP mode anyway."@en .

<#q-read-an-app-12a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The access resource's URL ends in `.acr`, not `.acl`"@en ;
    solid-memo:distractorNote "URL suffixes are a server convention; clients must not rely on them."@en .

<#q-read-an-app-12a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The storage description says which access language it uses"@en ;
    solid-memo:distractorNote "It declares no access language; the app checks the access resource's own type link."@en .

<#q-read-an-app-12b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In a Solid app, Inrupt's `universalAccess.setAgentAccess` returns `null` when the app shares a note. What should the app do?"@en ;
    solid-memo:back "Treat it as not shared: tell the user, or write the rules itself"@en ;
    solid-memo:backNote "A null result means the access could not be read or set; on a fresh CSS 7.2 ACP resource (2026) the library gave up, while a hand-written N3 Patch to the ACR worked."@en ;
    solid-memo:distractor <#q-read-an-app-12b-d1> ,
                          <#q-read-an-app-12b-d2> ,
                          <#q-read-an-app-12b-d3> .

<#q-read-an-app-12b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Carry on: `null` means the access was set and nothing came back"@en ;
    solid-memo:distractorNote "On CSS 7.2 with ACP bob stayed at 403; null means the library could not set the access."@en .

<#q-read-an-app-12b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Retry the same call until it returns an access object"@en ;
    solid-memo:distractorNote "The ACR is still missing, so the same call fails the same way."@en .

<#q-read-an-app-12b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Grant the friend Read on the pod root instead, which always works"@en ;
    solid-memo:distractorNote "That shares everything in the pod, not one note."@en .

<#ch-read-an-app-13>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-an-app> ;
    schema:position 12 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## What differs between servers

Code that passes on one server may fail on another (Step 12.13). The table adds node-solid-server (NSS) 6.0.0, recorded by the course authors in 2026. NSS 6 can't log a script in, so those runs used its open root anonymously.

| Behaviour | CSS 7.2 (WAC) | NSS 6.0.0 | CSS 7.2 (ACP) |
|---|---|---|---|
| ETag on GET | yes | **none** | yes |
| Wrong `If-Match` on PATCH | 412 | **200 (ignored)** | 412 |
| Blank node in `solid:inserts` | 422 | **200** | 422 |
| POST `Slug: first` | `first` | **`first.ttl`** | `first` |
| WebSocketChannel2023 | yes | **no** | yes |
| `rel="acl"` points to | ACL | ACL | **ACR** |
| `setAgentAccess` | worked | not tested | **returned null** |

---

The app uses **feature detection**, never the server's name:

- **No ETag:** send no `If-Match`; stale deletes still fail with 409, and `editNote` retries.
- **No notification service:** `subscribe` returns `null`; the app asks for a reload.
- **An ACR behind `rel="acl"`:** write an ACP policy, not a WAC rule.

On NSS 6.0.0 the same code recorded:

```text
Location: http://localhost:3902/alice40639/notes/first.ttl
edit that lost a race, then retried: {"status":200,"attempt":2,"retriedAfter":409,"conditional":false}
no WebSocketChannel2023 service: the app falls back to reloading by hand
```"""@en ;
    solid-memo:checkedBy <#q-read-an-app-13a> .

<#q-read-an-app-13a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On node-solid-server 6.0.0 (2026), which sends no ETag, the Solid Notes example app's N3 Patch edit lost a race, yet the other user's change survived. What stopped the lost update?"@en ;
    solid-memo:back "The stale `solid:deletes` no longer matched, so NSS sent 409"@en ;
    solid-memo:backNote "An N3 Patch whose deletes aren't all in the document fails with 409, so deleting the old text acts as a check even without ETags; `editNote` then rereads and retries."@en ;
    solid-memo:distractor <#q-read-an-app-13a-d1> ,
                          <#q-read-an-app-13a-d2> ,
                          <#q-read-an-app-13a-d3> .

<#q-read-an-app-13a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "NSS honoured the `If-Match` header and answered 412"@en ;
    solid-memo:distractorNote "NSS 6 sends no ETag on GET, so there was no If-Match, and it ignores a wrong one."@en .

<#q-read-an-app-13a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "NSS locks a document while a client has it open"@en ;
    solid-memo:distractorNote "HTTP servers keep no such locks between requests."@en .

<#q-read-an-app-13a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A WebSocket notification warned the app before it patched"@en ;
    solid-memo:distractorNote "NSS 6 offered no WebSocketChannel2023."@en .

<#ch-read-an-app-14>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-an-app> ;
    schema:position 13 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## When a session ends: expiry and one silent restore

The library (authn-browser 5.0.1) renews the access token 5 s before it ends (CSS 7.2 gave 3600 s tokens). If a refresh is refused, the library fires `sessionExpired` and logs out locally (Step 12.7).

Solid Notes then tries one **silent restore**: a new login at the same provider with `prompt: 'none'` ("show no page"). If the provider still has her session (a cookie), the browser comes back with an authorization code (Step 7.6); if not, with `login_required`. Before leaving, the app sets a mark in `sessionStorage`, next to the saved route and draft (Step 12.8). Back with the mark but no session, or failing before leaving, it shows "Log in again". Every page load reads and removes the mark.

⚠ `restorePreviousSession` can't do this: the session is already forgotten. `login()` passes `prompt` on, though its typings omit it.

---

```js
// src/login.js
export function onExpiry(storage, { restore, prompt }) {
  const ask = () => { storage.removeItem(KEY.restoring); return prompt(); };
  return () => {
    if (storage.getItem(KEY.restoring) !== null) return ask(); // the attempt came back without a session
    storage.setItem(KEY.restoring, new Date().toISOString()); // KEY.restoring is 'solid-notes:restoring'
    return new Promise((resolve) => { resolve(restore()); }).catch(ask); // it failed before leaving
  };
}
```

On CSS 7.2, in a browser test that cut the first token to 20 s and refused the refresh itself: with the provider session alive, the app came back with no password or consent page; with its cookies cleared, one silent attempt, then "Your session has ended. Log in again; your draft is kept." Draft and route survived."""@en ;
    solid-memo:checkedBy <#q-read-an-app-14a> ,
                         <#q-read-an-app-14b> ,
                         <#q-read-an-app-14c> .

<#q-read-an-app-14a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In a browser Solid app using `@inrupt/solid-client-authn-browser` 5.0.1, a token refresh is refused and `sessionExpired` fires, but the provider still knows the user. How does the Solid Notes example app bring her session back?"@en ;
    solid-memo:back "One `login()` at the same provider with `prompt: 'none'`"@en ;
    solid-memo:backNote "The library logs out locally when it gives up, so the app starts a new login that asks the provider not to show a page; if her provider session is alive, she comes back with an authorization code and is logged in again."@en ;
    solid-memo:distractor <#q-read-an-app-14a-d1> ,
                          <#q-read-an-app-14a-d2> ,
                          <#q-read-an-app-14a-d3> .

<#q-read-an-app-14a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`handleIncomingRedirect({ restorePreviousSession: true })`"@en ;
    solid-memo:distractorNote "By then authn-browser 5.0.1 has forgotten the session, so there is nothing to restore."@en .

<#q-read-an-app-14a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It retries the failed request until the pod accepts it"@en ;
    solid-memo:distractorNote "session.fetch is anonymous now, so every retry gets 401."@en .

<#q-read-an-app-14a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It reloads the page so the library logs her in again"@en ;
    solid-memo:distractorNote "A reload loses the draft, and the library has no session left to restore."@en .

<#q-read-an-app-14b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In the Solid Notes example app, a silent `prompt=none` restore after session expiry comes back without a session. Why doesn't the app try it again?"@en ;
    solid-memo:back "A mark in `sessionStorage` says it already tried once"@en ;
    solid-memo:backNote "The app sets a mark before it leaves for the provider; back with the mark and no session, it shows \"Log in again\". On CSS 7.2 exactly one silent attempt was made."@en ;
    solid-memo:distractor <#q-read-an-app-14b-d1> ,
                          <#q-read-an-app-14b-d2> ,
                          <#q-read-an-app-14b-d3> .

<#q-read-an-app-14b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The provider refuses a second `prompt=none` request"@en ;
    solid-memo:distractorNote "The provider would answer again; the app decides not to ask."@en .

<#q-read-an-app-14b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The library allows only one login per page load"@en ;
    solid-memo:distractorNote "login() can be called at any time; \"Log in again\" calls it."@en .

<#q-read-an-app-14b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The failed redirect clears `sessionStorage`"@en ;
    solid-memo:distractorNote "sessionStorage survives redirects in the same tab; that's how the draft survives."@en .

<#q-read-an-app-14c>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front """A Solid app sets the `sessionStorage` key `solid-notes:restoring` before a silent login after session expiry, and its expiry handler asks the user to log in at once if the key is already set. On every page load it runs the function below. What goes wrong if the `removeItem` line is deleted?

```js
export function afterRestore(storage, loggedIn) {
  const attempted = storage.getItem('solid-notes:restoring') !== null;
  storage.removeItem('solid-notes:restoring');
  if (!attempted) return 'none';
  return loggedIn ? 'restored' : 'failed';
}
```"""@en ;
    solid-memo:back "A later expiry finds the old mark and skips the silent restore"@en ;
    solid-memo:backNote "Removing the mark on every load lets each expiry get its own single attempt; left in place, it makes the next expiry go straight to \"Log in again\"."@en ;
    solid-memo:distractor <#q-read-an-app-14c-d1> ,
                          <#q-read-an-app-14c-d2> ,
                          <#q-read-an-app-14c-d3> .

<#q-read-an-app-14c-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The silent restore then repeats in a loop on every page load"@en ;
    solid-memo:distractorNote "Only onExpiry starts a restore, and it does so once per expiry."@en .

<#q-read-an-app-14c-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing, because each login redirect clears `sessionStorage`"@en ;
    solid-memo:distractorNote "sessionStorage survives redirects in the same tab."@en .

<#q-read-an-app-14c-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The draft and route saved before the redirect are lost"@en ;
    solid-memo:distractorNote "They live under other keys, which this function doesn't touch."@en .

<#ch-read-an-app-15>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-an-app> ;
    schema:position 14 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Logging out: the app, or the provider too

Step 12.8 gave two levels of logout; Solid Notes has a button for each.

**Log out** (`logoutType: 'app'`) forgets the session in this tab, but the provider still knows the user. On CSS 7.2, a silent login (`prompt=none`) right afterwards still got an authorization code: the provider would have let her straight back in.

**Log out of the provider too** (`'idp'`) also ends the provider's session. The library sends the browser to the provider's `end_session_endpoint`, listed in its `/.well-known/openid-configuration` (Step 7.6), with `id_token_hint`, her ID token (Step 7.5), so the provider knows whose session to end, and `post_logout_redirect_uri`, where to send her afterwards. The provider accepts only a URL the app registered for this (Step 14.16). CSS 7.2 asked to confirm; afterwards a silent login got `login_required`.

⚠ CSS 7.2 still skipped the password at the next login: it keeps a separate `css-account` cookie for its account pages until you log out there.

---

```js
// src/login.js
export const logOut = () => logout({ logoutType: 'app' });

export function logOutEverywhere(appUrl, storage = sessionStorage) {
  const issuer = storage.getItem(KEY.issuer);
  const registered = issuer && 'clientId' in clientOptions(appUrl, issuer, { dev: dev() });
  storage.removeItem(KEY.issuer);
  return logout({ logoutType: 'idp', ...(registered ? { postLogoutUrl: redirectUrl(appUrl) } : {}) });
}
```

On CSS 7.2:

```text
after app logout, a prompt=none request gets a code
provider logout went to http://localhost:3000/.oidc/session/end with id_token_hint, post_logout_redirect_uri
after provider logout, a prompt=none request gets login_required
but logging in again shows the consent page: CSS still has its own account cookie, css-account
after logging out on CSS's account pages, logging in shows the password page
```"""@en ;
    solid-memo:checkedBy <#q-read-an-app-15a> .

<#q-read-an-app-15a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In a Solid app, alice clicks a **Log out** button that does only an app logout (`logoutType: 'app'`), then logs in again without typing her password. Why?"@en ;
    solid-memo:back "The provider's session is still alive, so it knows her"@en ;
    solid-memo:backNote "App logout forgets the session in the app; the provider still has its own, which provider logout ends too. ⚠ On CSS 7.2 (2026) even provider logout left its `css-account` cookie, so the password was asked only after logging out on CSS's account page as well."@en ;
    solid-memo:distractor <#q-read-an-app-15a-d1> ,
                          <#q-read-an-app-15a-d2> ,
                          <#q-read-an-app-15a-d3> .

<#q-read-an-app-15a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The library kept her refresh token in `localStorage`"@en ;
    solid-memo:distractorNote "The library keeps tokens in memory, and logout cleared them."@en .

<#q-read-an-app-15a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The Client ID Document lists her as a returning user"@en ;
    solid-memo:distractorNote "A Client ID Document describes the app, not its users."@en .

<#q-read-an-app-15a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "App logout only hides the app; her session in the tab lives on"@en ;
    solid-memo:distractorNote "App logout ends the session in the app; only the provider's session is left."@en .

<#ch-read-an-app-16>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-an-app> ;
    schema:position 15 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Going live: a Client ID Document and one redirect page

Served the way it would go live (Step 13.9), the app provides two things.

**A Client ID Document** at `/id.jsonld`, built from the origin (scheme, host, port) it is served at, so `client_id` equals its own URL. The app logs in with it when it is on https, or when app and provider are both on `http://localhost`; the development server keeps `clientName` (Step 12.9). The provider fetches the document itself.

**One fixed redirect page**, `/`, listed in `redirect_uris` for logins and in `post_logout_redirect_uris` for provider logout (Step 14.15). The route travels in `sessionStorage` (Step 14.14).

Vite's preview server builds the document on each request; for a static host, the build must write `id.jsonld` for the app's real origin, or the file is missing.

---

```js
// src/client-id.js
export function clientIdDocument(origin) {
  const start = new URL('/', origin).href; // the one fixed redirect page
  return {
    '@context': ['https://www.w3.org/ns/solid/oidc-context.jsonld'],
    client_id: clientIdUrl(origin),
    client_name: CLIENT_NAME,
    redirect_uris: [start],
    post_logout_redirect_uris: [start],
    scope: 'openid profile offline_access webid',
    // …
  };
}
```

On CSS 7.2 (2026), with the app at `http://localhost:5173`:

```text
GET http://localhost:5173/id.jsonld: 200 application/ld+json; client_id http://localhost:5173/id.jsonld
authorize with client_id http://localhost:5173/id.jsonld: 303 -> http://localhost:3000/.account/
the same, redirect_uri http://localhost:5173/callback (not listed): 400 … "error":"invalid_redirect_uri" …
client_id http://127.0.0.1:5173/id.jsonld: 500 … "SSL is required for client_id authentication unless working locally." …
token_type DPoP, expires_in 3600 s, refresh_token yes
```"""@en ;
    solid-memo:checkedBy <#q-read-an-app-16a> ,
                         <#q-read-an-app-16b> ,
                         <#q-read-an-app-16c> .

<#q-read-an-app-16a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid-OIDC, why must the identity provider fetch an app's Client ID Document itself, from the app's own URL?"@en ;
    solid-memo:back "The URL is the client ID, and only the app's owner controls it"@en ;
    solid-memo:backNote "Whoever controls the URL controls the `redirect_uris` it lists, so the provider must fetch the document itself, over https so nobody can change it on the way."@en ;
    solid-memo:distractor <#q-read-an-app-16a-d1> ,
                          <#q-read-an-app-16a-d2> ,
                          <#q-read-an-app-16a-d3> .

<#q-read-an-app-16a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "To show the app's own look and pages on the consent page"@en ;
    solid-memo:distractorNote "The consent page shows the client's name and ID, not the app's pages."@en .

<#q-read-an-app-16a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "To read the app's CSP header and check it before the login"@en ;
    solid-memo:distractorNote "The browser enforces the CSP; the provider never reads it."@en .

<#q-read-an-app-16a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "To register the app dynamically under that URL as its name"@en ;
    solid-memo:distractorNote "A Client ID Document replaces dynamic registration."@en .

<#q-read-an-app-16b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app logs in with `<origin>/id.jsonld` as its client ID whenever it runs on https. You deploy a build that has no `id.jsonld` file to an https static host. What happens when someone logs in?"@en ;
    solid-memo:back "The provider can't fetch `/id.jsonld` there, so the login fails"@en ;
    solid-memo:backNote "The provider checks every login's redirect URI against the document, so without that file it has nothing to check the login against."@en ;
    solid-memo:distractor <#q-read-an-app-16b-d1> ,
                          <#q-read-an-app-16b-d2> ,
                          <#q-read-an-app-16b-d3> .

<#q-read-an-app-16b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The app falls back to dynamic registration by itself"@en ;
    solid-memo:distractorNote "The app picks the client ID for any https origin; it doesn't check that the document exists."@en .

<#q-read-an-app-16b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The static host builds `id.jsonld` from `index.html`"@en ;
    solid-memo:distractorNote "A static host only serves the files it was given."@en .

<#q-read-an-app-16b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The login works; the document is only needed for logout"@en ;
    solid-memo:distractorNote "The provider checks every login's `redirect_uri` against the document."@en .

<#q-read-an-app-16c>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On Community Solid Server 7.2 (2026), an app's Client ID Document is accepted at `http://localhost:5173/id.jsonld`. What does the identity provider do with the same document at `http://127.0.0.1:5173/id.jsonld`, and why?"@en ;
    solid-memo:back "Refused: plain http counts as local only on `localhost`"@en ;
    solid-memo:backNote "CSS 7.2 accepts plain http only on `localhost`; the same document on `127.0.0.1` was refused with `SSL is required for client_id authentication unless working locally`, and anywhere else it needs https."@en ;
    solid-memo:distractor <#q-read-an-app-16c-d1> ,
                          <#q-read-an-app-16c-d2> ,
                          <#q-read-an-app-16c-d3> ,
                          <#q-read-an-app-16c-d4> ,
                          <#q-read-an-app-16c-d5> ,
                          <#q-read-an-app-16c-d6> .

<#q-read-an-app-16c-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "`http://localhost:5173/id.jsonld`" ;
    solid-memo:distractorNote "CSS 7.2 accepted it: plain http is allowed on localhost."@en .

<#q-read-an-app-16c-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "`http://localhost:5174/id.jsonld`" ;
    solid-memo:distractorNote "CSS 7.2's check allows `http://localhost` on any port."@en .

<#q-read-an-app-16c-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "`https://notes.example/id.jsonld`" ;
    solid-memo:distractorNote "https passes this check; that error is only for plain http outside localhost."@en .

<#q-read-an-app-16c-d4>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Accepted: `127.0.0.1` counts as local, like `localhost`"@en ;
    solid-memo:distractorNote "CSS 7.2 refused it with `SSL is required for client_id authentication unless working locally`: only `localhost` counts as local for plain http."@en .

<#q-read-an-app-16c-d5>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Refused: its `redirect_uris` don't match the login's origin"@en ;
    solid-memo:distractorNote "The document is built from the origin it is served at, so `client_id` and `redirect_uris` match; CSS 7.2 refused it with `SSL is required for client_id authentication unless working locally`, because plain http counts as local only on `localhost`."@en .

<#q-read-an-app-16c-d6>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Refused: the provider can't fetch from `127.0.0.1`"@en ;
    solid-memo:distractorNote "The provider refused it with `SSL is required for client_id authentication unless working locally`: the issue is plain http outside `localhost`, not fetching."@en .

<#ch-read-an-app-17>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-an-app> ;
    schema:position 16 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Serving it with a CSP

Vite's preview server also sends a **Content-Security-Policy header**: Step 13.2's policy, with the http pods' origins added to `img-src`, and their `http:` and `ws:` origins to `connect-src`. Step 13.2's `https:` and `wss:` don't match a pod on plain http; an https pod needs nothing extra.

Styles live in `src/style.css`, not in an inline `<style>`, because `default-src 'self'` also covers styles and blocks inline ones. The development server sends no CSP: it injects inline styles.

A browser test watched six browser sessions, live updates over WebSocket included, and saw no CSP violations. A real host sends the header from its own configuration.

---

```js
// vite.config.js
// pods: the pods' plain-http origins, read from VITE_SOLID_BASE when the preview starts
export const csp = [
  "default-src 'self'",
  "script-src 'self'",
  "object-src 'none'",
  "base-uri 'none'",
  `img-src 'self' https: data: ${pods.join(' ')}`,
  `connect-src 'self' https: wss: ${pods.map((o) => `${o} ${o.replace(/^http/, 'ws')}`).join(' ')}`,
].join('; ');
```

With pods at `http://localhost:3000` and `http://localhost:3001` the header read:

```text
default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'none'; img-src 'self' https: data: http://localhost:3000 http://localhost:3001; connect-src 'self' https: wss: http://localhost:3000 ws://localhost:3000 http://localhost:3001 ws://localhost:3001
```"""@en ;
    solid-memo:checkedBy <#q-read-an-app-17a> ,
                         <#q-read-an-app-17b> ,
                         <#q-read-an-app-17c> .

<#q-read-an-app-17a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Why does a Solid app served with the CSP `default-src 'self'` (and no `style-src`) keep its styles in a `.css` file instead of an inline `<style>` element?"@en ;
    solid-memo:back "`default-src 'self'` also covers styles, and inline ones aren't `'self'`"@en ;
    solid-memo:backNote "Without a `style-src` directive the browser uses `default-src`, and `'self'` allows files from the app's origin but no inline styles."@en ;
    solid-memo:distractor <#q-read-an-app-17a-d1> ,
                          <#q-read-an-app-17a-d2> ,
                          <#q-read-an-app-17a-d3> .

<#q-read-an-app-17a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`script-src 'self'` forbids every `<style>` element in the page"@en ;
    solid-memo:distractorNote "script-src covers scripts; styles fall back to default-src."@en .

<#q-read-an-app-17a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Vite can't bundle a page that has an inline `<style>` element"@en ;
    solid-memo:distractorNote "Vite builds inline styles fine; the CSP is what blocks them."@en .

<#q-read-an-app-17a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The Client ID Document must list every style file the app loads"@en ;
    solid-memo:distractorNote "It lists redirect URIs and the app's name, not its files."@en .

<#q-read-an-app-17b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app talks to a pod at `http://localhost:3000`. Why does its CSP list `ws://localhost:3000` in `connect-src`, when it already allows `wss:`?"@en ;
    solid-memo:back "Its notifications use plain `ws:`, which `wss:` doesn't match"@en ;
    solid-memo:backNote "A pod on plain http gives WebSocketChannel2023 URLs that start with `ws:`; `https:` and `wss:` only match encrypted origins, so without it live updates would be blocked."@en ;
    solid-memo:distractor <#q-read-an-app-17b-d1> ,
                          <#q-read-an-app-17b-d2> ,
                          <#q-read-an-app-17b-d3> .

<#q-read-an-app-17b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`wss:` covers only remote hosts, never `localhost` itself"@en ;
    solid-memo:distractorNote "A scheme source matches any host with that scheme."@en .

<#q-read-an-app-17b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "WebSockets need their own `ws-src` directive, apart from fetches"@en ;
    solid-memo:distractorNote "There is none; WebSockets fall under connect-src."@en .

<#q-read-an-app-17b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It allows the provider's login page to open in the app"@en ;
    solid-memo:distractorNote "Navigation to the provider isn't a connection; connect-src doesn't govern it."@en .

<#q-read-an-app-17c>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front """A Solid app builds its CSP's `connect-src` from its pods' origins as below. What does it give for the pods `http://localhost:3000` and `https://pod.example`?

```js
const plain = origins.filter((o) => o.startsWith('http:'));
['connect-src', "'self'", 'https:', 'wss:',
  ...plain.flatMap((o) => [o, o.replace(/^http/, 'ws')])].join(' ')
```"""@en ;
    solid-memo:back "`connect-src 'self' https: wss: http://localhost:3000 ws://localhost:3000`" ;
    solid-memo:backNote "Only plain-http pods need extra sources; `https:` and `wss:` already match `https://pod.example` and its WebSocket."@en ;
    solid-memo:distractor <#q-read-an-app-17c-d1> ,
                          <#q-read-an-app-17c-d2> ,
                          <#q-read-an-app-17c-d3> .

<#q-read-an-app-17c-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`connect-src 'self' https: wss: http://localhost:3000 https://pod.example`" ;
    solid-memo:distractorNote "The filter keeps only `http:` origins; `https:` already covers the second pod."@en .

<#q-read-an-app-17c-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`connect-src 'self' https: wss: http://localhost:3000 wss://pod.example`" ;
    solid-memo:distractorNote "The https pod is filtered out, so no `wss:` origin is added for it."@en .

<#q-read-an-app-17c-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`connect-src 'self' https: wss: ws://localhost:3000`" ;
    solid-memo:distractorNote "`flatMap` keeps the http origin as well as its `ws:` twin."@en .

<#ch-read-an-app-18>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-read-an-app> ;
    schema:position 17 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Who logged in: checking the issuer

A login at a provider the profile doesn't list can succeed, but pods won't accept the token as that WebID (Step 7.9). The course authors produced one with two CSS 7.2 servers. CSS lets an account link a WebID from another server once that WebID's profile holds a one-time verification triple (`solid:oidcIssuerRegistrationToken`). So an account on the ACP server linked frank's WebID from the WAC server, and logging in there brought "frank" back from an issuer his profile doesn't list.

So after each login the app compares that issuer with the profile's `solid:oidcIssuer` values, as exact strings. The library doesn't expose the issuer, so `startLogin` saves the provider's own `issuer` string, from its `/.well-known/openid-configuration`, in `sessionStorage`. On a mismatch the app logs out and explains.

---

```js
// src/login.js
export async function checkIssuer(webId, storage, fetchFn = fetch) {
  const issuer = storage.getItem(KEY.issuer);
  if (!issuer) return { checked: false };
  const listed = await issuersOf(webId, fetchFn);
  return { checked: true, issuer, listed, ok: listed.includes(issuer) }; // exact strings
}
// src/main.js, after every login
  if (issuer.checked && !issuer.ok) {
    await logOut();
```

On CSS 7.2 the app showed:

```text
You logged in at http://localhost:3001/, but the profile of http://localhost:3000/frank54192/profile/card#me lists http://localhost:3000/. Pods won't accept this login as that WebID, so you have been logged out. Log in at a provider your profile lists.
```

That fetch of `/.well-known/openid-configuration` is a connection, so the CSP's `connect-src` must allow every http provider the app may use."""@en ;
    solid-memo:checkedBy <#q-read-an-app-18a> ,
                         <#q-read-an-app-18b> ,
                         <#q-read-an-app-18c> .

<#q-read-an-app-18a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In the Solid Notes example app, frank logs in at a provider his WebID profile doesn't list as `solid:oidcIssuer`, and the login succeeds. What does the app do next?"@en ;
    solid-memo:back "Logs him out and names the providers his profile lists"@en ;
    solid-memo:backNote "After login the app compares the issuer it logged in at with the profile's `solid:oidcIssuer` values; on a mismatch it logs out and explains, instead of leaving him with unexplained 401s."@en ;
    solid-memo:distractor <#q-read-an-app-18a-d1> ,
                          <#q-read-an-app-18a-d2> ,
                          <#q-read-an-app-18a-d3> .

<#q-read-an-app-18a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Keeps him logged in, since the provider vouched for his WebID"@en ;
    solid-memo:distractorNote "Pods accept the token only if his profile lists its issuer."@en .

<#q-read-an-app-18a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Adds that provider to his profile's `solid:oidcIssuer`"@en ;
    solid-memo:distractorNote "That changes who may log in as him, which only he should decide."@en .

<#q-read-an-app-18a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Logs in again at the same provider until the pod accepts it"@en ;
    solid-memo:distractorNote "Every token from it fails the same check at the pod."@en .

<#q-read-an-app-18b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app is served with `connect-src 'self' https: wss: http://localhost:3000 ws://localhost:3000`. A user types the provider `http://localhost:3001/`. Why can't the login even start?"@en ;
    solid-memo:back "The CSP blocks the app's fetch of that provider's configuration"@en ;
    solid-memo:backNote "Login starts by fetching the provider's `/.well-known/openid-configuration`; `connect-src` lists no `http://localhost:3001`, so the browser blocks it."@en ;
    solid-memo:distractor <#q-read-an-app-18b-d1> ,
                          <#q-read-an-app-18b-d2> ,
                          <#q-read-an-app-18b-d3> .

<#q-read-an-app-18b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "CSS on port 3001 refuses apps built for port 3000"@en ;
    solid-memo:distractorNote "CSS doesn't know how the app was built."@en .

<#q-read-an-app-18b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The Client ID Document lists only port 3000 as a provider"@en ;
    solid-memo:distractorNote "It lists the app's own redirect URLs, not providers."@en .

<#q-read-an-app-18b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The login library accepts only providers from a built-in list"@en ;
    solid-memo:distractorNote "Any provider URL can be passed to login()."@en .

<#q-read-an-app-18c>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front """After a login at `https://idp.example`, a Solid app's issuer check fails because the WebID profile lists `https://other.example/` and `https://idp.example/` (exact strings differ). Which provider does this function suggest?

```js
const bare = (url) => url.replace(/\\/+$/, '');
const suggest = result.listed.find((i) => bare(i) === bare(result.issuer))
  ?? result.listed[0] ?? null;
```"""@en ;
    solid-memo:back "`https://idp.example/`" ;
    solid-memo:backNote "The same provider spelt with a trailing slash comes first; only without one does it fall back to the first listed issuer, or `null`."@en ;
    solid-memo:distractor <#q-read-an-app-18c-d1> ,
                          <#q-read-an-app-18c-d2> ,
                          <#q-read-an-app-18c-d3> .

<#q-read-an-app-18c-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`https://other.example/`" ;
    solid-memo:distractorNote "That is the fallback, used only when no listed issuer matches without its slash."@en .

<#q-read-an-app-18c-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`https://idp.example`" ;
    solid-memo:distractorNote "It suggests a listed issuer, and the profile lists the one with a slash."@en .

<#q-read-an-app-18c-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`null`" ;
    solid-memo:distractorNote "null is returned only when the profile lists no issuer at all."@en .

<#q-read-an-app-r01>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "In the Solid Notes example app, in what order does the app find where to put a new note?"@en ;
    solid-memo:back "WebID profile, then storage, then type index, then container"@en ;
    solid-memo:backNote "The profile leads to the storage and to the type indexes, whose registration names the notes container."@en ;
    solid-memo:distractor <#q-read-an-app-r01-d1> ,
                          <#q-read-an-app-r01-d2> ,
                          <#q-read-an-app-r01-d3> .

<#q-read-an-app-r01-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Storage description, then profile, then container, then type index"@en ;
    solid-memo:distractorNote "The storage description can be server-wide (as on CSS 7.2's default configuration), and the app starts from the profile."@en .

<#q-read-an-app-r01-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Identity provider, then pod root ACL, then the container"@en ;
    solid-memo:distractorNote "The identity provider and ACLs say nothing about where notes live."@en .

<#q-read-an-app-r01-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Type index, then WebID profile, then storage, then container"@en ;
    solid-memo:distractorNote "The type index is only found through the profile."@en .

<#q-read-an-app-r02>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A developer's Solid app treats only 200 and 204 as a successful PATCH. What happens on Community Solid Server 7.2 (2026)?"@en ;
    solid-memo:back "Every successful edit is reported as a failure: CSS sends 205"@en ;
    solid-memo:backNote "Treat any 2xx as success (`response.ok`); CSS 7.2 answers PUT on an existing resource, PATCH and DELETE with 205."@en ;
    solid-memo:distractor <#q-read-an-app-r02-d1> ,
                          <#q-read-an-app-r02-d2> ,
                          <#q-read-an-app-r02-d3> .

<#q-read-an-app-r02-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing changes, because CSS answers every PATCH with 204"@en ;
    solid-memo:distractorNote "CSS 7.2 answered every successful PATCH with 205 Reset Content."@en .

<#q-read-an-app-r02-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The edits are rejected, because the client must accept 205"@en ;
    solid-memo:distractorNote "The edit is applied; only the app's reading of the answer is wrong."@en .

<#q-read-an-app-r02-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only edits sent with `If-Match` fail, because they answer 412"@en ;
    solid-memo:distractorNote "Conditional edits with a current ETag also answer 205."@en .

<#q-read-an-app-r03>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "The Solid Notes example app runs against a Solid server that offers no WebSocketChannel2023 service. What does it do?"@en ;
    solid-memo:back "It keeps working and tells the user to reload to see changes"@en ;
    solid-memo:backNote "Feature detection: `subscribe` returns `null` when no WebSocketChannel2023 service is found, and the app says \"reload to see changes\"."@en ;
    solid-memo:distractor <#q-read-an-app-r03-d1> ,
                          <#q-read-an-app-r03-d2> ,
                          <#q-read-an-app-r03-d3> .

<#q-read-an-app-r03-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It refuses to log in, because live updates are required"@en ;
    solid-memo:distractorNote "Notifications are optional; subscribe returns null and the app carries on."@en .

<#q-read-an-app-r03-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It polls the container with GET every few seconds by itself"@en ;
    solid-memo:distractorNote "Solid Notes has no polling; it asks the user to reload."@en .

<#q-read-an-app-r03-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It subscribes to the user's inbox as a change feed instead"@en ;
    solid-memo:distractorNote "An LDN inbox is not a change feed for the notes."@en .

<#q-read-an-app-r04>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In the Solid Notes example app, every pod function takes a `fetch` argument. Alice's access token expires in the middle of a session. Which part of the app has to handle it?"@en ;
    solid-memo:back "The login side, which supplies the `fetch`"@en ;
    solid-memo:backNote "Because the pod logic only receives a fetch, tokens live with the login: `session.fetch` in the browser, a client-credentials session in the tests."@en ;
    solid-memo:distractor <#q-read-an-app-r04-d1> ,
                          <#q-read-an-app-r04-d2> ,
                          <#q-read-an-app-r04-d3> .

<#q-read-an-app-r04-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`notes.js`, since every function there sends requests"@en ;
    solid-memo:distractorNote "They use whatever fetch they are given; keeping its token valid is that fetch's job."@en .

<#q-read-an-app-r04-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`share.js`, because sharing needs a fresh token per call"@en ;
    solid-memo:distractorNote "Sharing uses the same fetch as everything else."@en .

<#q-read-an-app-r04-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Every module: each must check the token before a request"@en ;
    solid-memo:distractorNote "Passing fetch in keeps tokens out of the pod logic."@en .

<#q-read-an-app-r05>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Two mechanisms guard the Solid Notes example app's N3 Patch edits against a lost update. Which are they, and which still worked on node-solid-server 6.0.0 (2026)?"@en ;
    solid-memo:back "`If-Match` and the patch's deletes; on NSS 6 only the deletes"@en ;
    solid-memo:backNote "CSS 7.2 rejected a stale ETag with 412; NSS 6 sent no ETag, but the stale delete failed with 409, and `editNote` retried either way."@en ;
    solid-memo:distractor <#q-read-an-app-r05-d1> ,
                          <#q-read-an-app-r05-d2> ,
                          <#q-read-an-app-r05-d3> .

<#q-read-an-app-r05-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`If-Match` and WebSocket messages; on NSS 6 only `If-Match`"@en ;
    solid-memo:distractorNote "NSS 6 ignored If-Match and offered no WebSocket channel."@en .

<#q-read-an-app-r05-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "ETag checks and the Slug header; on NSS 6 only the Slug"@en ;
    solid-memo:distractorNote "A slug names a new resource; it guards no edit."@en .

<#q-read-an-app-r05-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`If-Match` and `If-None-Match: *`; both worked on NSS 6"@en ;
    solid-memo:distractorNote "`If-None-Match: *` guards creation only, and NSS 6 ignored If-Match."@en .

<#q-read-an-app-r06>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Before a browser Solid app (the Solid Notes example) leaves for the identity provider to log in, what does it save in `sessionStorage`?"@en ;
    solid-memo:back "The route, the unsaved draft and the provider's issuer"@en ;
    solid-memo:backNote "The login redirect unloads the page, so the app keeps what the user would miss (route and draft) and what it needs for the issuer check; tokens stay with the library."@en ;
    solid-memo:distractor <#q-read-an-app-r06-d1> ,
                          <#q-read-an-app-r06-d2> ,
                          <#q-read-an-app-r06-d3> .

<#q-read-an-app-r06-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The route and the draft; the issuer comes from the token later"@en ;
    solid-memo:distractorNote "The library doesn't expose the issuer, so the app saves the provider's own string first."@en .

<#q-read-an-app-r06-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The route, the draft and the ID token, for the issuer check"@en ;
    solid-memo:distractorNote "Tokens stay in the library's memory: injected scripts can read storage."@en .

<#q-read-an-app-r06-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The draft only; the route travels in the redirect URL"@en ;
    solid-memo:distractorNote "The redirect page is fixed at `/`, so the route has to be saved."@en .

<#q-read-an-app-r07>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A token refresh fails in the Solid Notes example app, a browser Solid app. In what order do things happen?"@en ;
    solid-memo:back "`sessionExpired`, one `prompt=none` login, then \"Log in again\""@en ;
    solid-memo:backNote "The library fires `sessionExpired` once it gives up; the app marks one silent attempt and, if that comes back without a session, asks the user."@en ;
    solid-memo:distractor <#q-read-an-app-r07-d1> ,
                          <#q-read-an-app-r07-d2> ,
                          <#q-read-an-app-r07-d3> .

<#q-read-an-app-r07-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "\"Log in again\" first, then a `prompt=none` login if she ignores it"@en ;
    solid-memo:distractorNote "The silent attempt comes first: it needs no click if the provider knows her."@en .

<#q-read-an-app-r07-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A `prompt=none` login after every 401, until one succeeds"@en ;
    solid-memo:distractorNote "Retrying on 401 can loop; the app makes one attempt per expiry."@en .

<#q-read-an-app-r07-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A reload, then `restorePreviousSession`, then \"Log in again\""@en ;
    solid-memo:distractorNote "After sessionExpired, authn-browser 5.0.1 has no session left to restore."@en .

<#q-read-an-app-r08>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app at `http://localhost:5173` logs in with a Client ID Document at a Community Solid Server 7.2 (2026) provider. What does the provider fetch from the app during the login?"@en ;
    solid-memo:back "`/id.jsonld`, the Client ID Document"@en ;
    solid-memo:backNote "With a client ID URL, CSS fetches the Client ID Document at login and checks the redirect URL against its `redirect_uris`, so the provider must be able to reach the app's origin."@en ;
    solid-memo:distractor <#q-read-an-app-r08-d1> ,
                          <#q-read-an-app-r08-d2> ,
                          <#q-read-an-app-r08-d3> .

<#q-read-an-app-r08-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The CSP header, to check the app's `connect-src`"@en ;
    solid-memo:distractorNote "The browser enforces the CSP; the provider never sees it."@en .

<#q-read-an-app-r08-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The redirect page `/`, to check that it calls `handleIncomingRedirect`"@en ;
    solid-memo:distractorNote "The provider only compares the redirect URL with the document."@en .

<#q-read-an-app-r08-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "`src/style.css`, to show the app's look on the consent page"@en ;
    solid-memo:distractorNote "The consent page shows the client's name and ID, not its styles."@en .

<#q-read-an-app-r09>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In WAC, bob and carol have Read and Append on alice's list document. At the same moment, each adds an item with an insert-only N3 Patch that uses a fresh fragment IRI. What happens?"@en ;
    solid-memo:back "Both items are kept: the inserts don't overwrite each other"@en ;
    solid-memo:backNote "An insert-only N3 Patch adds triples and removes none, so it needs only Append and can't undo anyone else's change; on CSS 7.2 two adds at the same moment were both kept."@en ;
    solid-memo:distractor <#q-read-an-app-r09-d1> ,
                          <#q-read-an-app-r09-d2> ,
                          <#q-read-an-app-r09-d3> .

<#q-read-an-app-r09-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Carol gets 412: the server makes concurrent patches send `If-Match`"@en ;
    solid-memo:distractorNote "The patches send no If-Match, so there is no precondition to fail."@en .

<#q-read-an-app-r09-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The later patch replaces the list, so one item is lost"@en ;
    solid-memo:distractorNote "A patch changes only the triples it names, and each item has its own IRI."@en .

<#q-read-an-app-r09-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Both get 403, because changing a document needs Write"@en ;
    solid-memo:distractorNote "Insert-only patches need only Append; on CSS 7.2 bob's add got 205."@en .

# Chapter 15: Worked example: walking through a real Solid app.
<#ch-app-walkthrough>
    a solid-memo:Chapter ,
      schema:Syllabus ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <> ;
    schema:position 14 ;
    dcterms:title "Worked example: walking through a real Solid app"@en ;
    dcterms:description "See how a production app, Solid Memo, turns the course's rules into code: login, discovery, conditional writes, its vocabulary contract, migrations and testing across servers."@en ;
    solid-memo:reviewQuestion <#q-app-walkthrough-r01> ,
                              <#q-app-walkthrough-r02> ,
                              <#q-app-walkthrough-r03> ,
                              <#q-app-walkthrough-r04> ,
                              <#q-app-walkthrough-r05> .

<#ch-app-walkthrough-1>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-app-walkthrough> ;
    schema:position 0 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## What the app does and how it is built

Solid Memo is a flashcard app: you study decks of cards, and a spaced-repetition
algorithm decides when each card comes back. This chapter describes its code as
of October 2026. All its data lives in the user's pod, in one container called
an *instance*. The browser app is built with Preact, `@inrupt/solid-client` and
the Inrupt browser authn library; it validates with `rdf-validate-shacl`, and
uses N3.js only in build tooling and tests.

---

The code is hexagonal ("ports and adapters"), in npm packages with their own
import rules. The main layers:

- **domain**: pure types and functions (scheduling, migrations), no network calls;
- **application**: one *use case* per user action, and the *ports* it needs,
  as narrow interfaces;
- **solid**: adapters that implement the ports with the Inrupt libraries;
- **vocab**: the data contract, TypeScript *generated* from the Turtle
  vocabulary and SHACL shapes, which the website also publishes for other
  apps, so code and published contract cannot drift apart.

```ts
export interface DeckRepository {      // a port, in the application package
  listDecks(instanceUrl: string): Promise<Deck[]>;
  createDeck(instanceUrl: string, title: LangText): Promise<Deck>;
  // …
}
```

A check fails the build when a package imports across these lines, so only
the adapters know the data lives in a pod. The rest of this chapter shows
where each rule from Chapters 6-12 ends up."""@en ;
    solid-memo:checkedBy <#q-app-walkthrough-1a> ,
                         <#q-app-walkthrough-1b> .

<#q-app-walkthrough-1a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Why does Solid Memo, a Solid flashcard app, generate its TypeScript types from its Turtle vocabulary and SHACL shapes, rather than writing the types by hand?"@en ;
    solid-memo:back "Other apps read the published RDF, so it must be the single source of truth."@en ;
    solid-memo:backNote "Other apps see only the RDF and shapes in the pod and on the website, so the app derives its code from them; then the code can never quietly disagree with the published contract."@en ;
    solid-memo:distractor <#q-app-walkthrough-1a-d1> ,
                          <#q-app-walkthrough-1a-d2> ,
                          <#q-app-walkthrough-1a-d3> .

<#q-app-walkthrough-1a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "TypeScript cannot describe RDF data unless a generator writes its types."@en ;
    solid-memo:distractorNote "Hand-written types work fine; the reason is keeping code and published contract from drifting apart."@en .

<#q-app-walkthrough-1a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Solid servers check each write against the app's types, so they must match."@en ;
    solid-memo:distractorNote "Servers never see the app's types; they store whatever RDF they are sent."@en .

<#q-app-walkthrough-1a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Generated code is smaller, so the app loads faster in the browser."@en ;
    solid-memo:distractorNote "Size and speed have nothing to do with it; the point is one source of truth for the contract."@en .

<#q-app-walkthrough-1b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid Memo's hexagonal (\"ports and adapters\") design, where does the code that calls `@inrupt/solid-client` belong?"@en ;
    solid-memo:back "In the Solid adapters that implement the application's ports."@en ;
    solid-memo:backNote "Adapters implement the ports the application defines, so the pod library sits at the edge and can be swapped or mocked without touching the domain."@en ;
    solid-memo:distractor <#q-app-walkthrough-1b-d1> ,
                          <#q-app-walkthrough-1b-d2> ,
                          <#q-app-walkthrough-1b-d3> .

<#q-app-walkthrough-1b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In the domain package, next to the scheduling algorithm."@en ;
    solid-memo:distractorNote "The domain is kept pure, free of any library or network call, so it can be tested on its own."@en .

<#q-app-walkthrough-1b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In the vocab package, next to the generated constants."@en ;
    solid-memo:distractorNote "The vocab package is the data contract, not the code that talks to pods."@en .

<#q-app-walkthrough-1b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In the UI components, because they show the decks and cards."@en ;
    solid-memo:distractorNote "The UI calls only use cases, one per user action; it never calls a pod library directly."@en .

<#ch-app-walkthrough-2>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-app-walkthrough> ;
    schema:position 1 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Login

Solid Memo is **WebID-first**. The user types a WebID, and
`SolidSessionGateway`, the adapter behind the `SessionGateway` port, fetches
the profile without logging in and follows `solid:oidcIssuer` (Step 7.9),
never the WebID's origin:

```ts
const issuers = getIriAll(profile, SOLID_OIDC_ISSUER);
const issuer = issuers.find(isSecureUrl);  // https only: the browser goes there next
```

The profile is outside the app's control, so the issuer is checked first:
`isSecureUrl` accepts only an `https:` URL with no user name or password. A
profile that lists only a plain-http issuer gets an error, not a redirect.

---

Step 12.6's other way in, **issuer-first**, is offered too: a user who does
not want to type a WebID picks a suggested provider, the same flow starts at
that issuer, and the WebID arrives with the session. Both are safe for one
reason: a pod accepts a token only from an issuer that the WebID's own
profile lists.

The Inrupt library then runs the authorization code flow with PKCE. The app
passes only a `clientName`, no `clientId`, so the library registers the client
dynamically. That needs nothing hosted, but gives up what a Client ID Document
(Steps 7.11 and 12.9) guarantees: a published list of the only redirect URIs
that may receive the app's tokens."""@en ;
    solid-memo:checkedBy <#q-app-walkthrough-2a> ,
                         <#q-app-walkthrough-2b> .

<#q-app-walkthrough-2a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "When a user logs in with a WebID, Solid Memo (2026) filters the issuers in the WebID profile with `isSecureUrl` before redirecting. What does that prevent?"@en ;
    solid-memo:back "Redirecting the login to a plain-http issuer."@en ;
    solid-memo:backNote "Over plain http the login could be read or altered on the network, so the app follows only an `https:` issuer URL without embedded credentials and reports an error otherwise."@en ;
    solid-memo:distractor <#q-app-walkthrough-2a-d1> ,
                          <#q-app-walkthrough-2a-d2> ,
                          <#q-app-walkthrough-2a-d3> .

<#q-app-walkthrough-2a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Logging in with a WebID whose profile lists more than one issuer."@en ;
    solid-memo:distractorNote "Several issuers are allowed; the app takes the first `https:` one."@en .

<#q-app-walkthrough-2a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Logging in through an issuer that the WebID's profile does not list."@en ;
    solid-memo:distractorNote "The issuers come from the profile in the first place; the filter only drops insecure ones."@en .

<#q-app-walkthrough-2a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Getting a token that the pod will later refuse to accept."@en ;
    solid-memo:distractorNote "Whether a pod accepts a token depends on the profile's issuers, not on this check."@en .

<#q-app-walkthrough-2b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A user skips Solid Memo's WebID field and picks a Solid identity provider from its suggested list. Why can't a rogue provider on that path log in as someone else's WebID?"@en ;
    solid-memo:back "Pods accept its tokens only if that WebID's profile lists it."@en ;
    solid-memo:backNote "Whichever way login starts, the token names a WebID and an issuer, and the pod checks that the WebID's profile lists that issuer as its `solid:oidcIssuer`."@en ;
    solid-memo:distractor <#q-app-walkthrough-2b-d1> ,
                          <#q-app-walkthrough-2b-d2> ,
                          <#q-app-walkthrough-2b-d3> .

<#q-app-walkthrough-2b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Solid Memo checks every provider against a central Solid registry."@en ;
    solid-memo:distractorNote "There is no central registry; trust comes from the user's own profile."@en .

<#q-app-walkthrough-2b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The app rejects any issuer on a different host from the WebID."@en ;
    solid-memo:distractorNote "Issuers often sit on other hosts; the app never compares origins."@en .

<#q-app-walkthrough-2b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The provider must also host the pod that the user's data is in."@en ;
    solid-memo:distractorNote "Identity and storage are separate; any issuer the profile lists may log the user in."@en .

<#ch-app-walkthrough-3>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-app-walkthrough> ;
    schema:position 2 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## The discovery chain

Finding the data is the chain from Steps 11.3-11.4, in two adapter files:

1. **Storage** (`solidStorageGateway.ts`): `pim:storage` from the profile;
   else `candidateStorageUrls` walks up from the WebID document and
   `hasStorageLink` looks for `Link: <…pim/space#Storage>; rel="type"`; else
   the user types the URL.
2. **Type indexes** (`typeIndex.ts`): links are read from the WebID document,
   from every extended profile (`rdfs:seeAlso`, `foaf:isPrimaryTopicOf`) and,
   for the private index, from `pim:preferencesFile`. The first link found
   for each index is used. Inrupt PodSpaces, for one, keeps a read-only WebID
   document and a writable profile in the pod.
3. **Registration**: `solid:forClass sm:Instance`, accepting both
   `solid:instanceContainer` and `solid:instance`.

Every one of these reads, the WebID document's too, goes through the app's
authenticated `fetch`: a plain `fetch` would get a 401 on a private extended
profile or preferences file, and the link in it would look missing."""@en ;
    solid-memo:checkedBy <#q-app-walkthrough-3a> .

<#q-app-walkthrough-3a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Why does Solid Memo (2026) look for type-index links in the WebID document, the extended profiles and the preferences file, instead of only one of them?"@en ;
    solid-memo:back "Real profiles put these links in different documents, so one place could miss them."@en ;
    solid-memo:backNote "In practice the links appear in the WebID document, an extended profile or the preferences file, so a link counts as missing only after all of them are read."@en ;
    solid-memo:distractor <#q-app-walkthrough-3a-d1> ,
                          <#q-app-walkthrough-3a-d2> ,
                          <#q-app-walkthrough-3a-d3> .

<#q-app-walkthrough-3a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The three documents each hold a copy of the index, so the copies must be merged."@en ;
    solid-memo:distractorNote "They hold links to the index documents, not copies of the index."@en .

<#q-app-walkthrough-3a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Each document may name a different index, so the app must check that they agree."@en ;
    solid-memo:distractorNote "The app takes the first link it finds for each index; the search is about finding a link at all."@en .

<#q-app-walkthrough-3a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Reading three documents lets the app avoid asking for any permissions."@en ;
    solid-memo:distractorNote "Where a link is found has nothing to do with what the app may read."@en .

<#ch-app-walkthrough-4>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-app-walkthrough> ;
    schema:position 3 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## When the type index is missing

On Community Solid Server pods a missing type index is **normal**, so Step
11.5's advice (offer to create one) runs on most first logins. Solid Memo asks
the user and defaults to a **private** index under `<storage>settings/`, for
the privacy reason Step 11.5 gives; registering publicly is the other choice.

Real pods force two more choices:

- **Where the link goes.** Solid Memo writes `solid:privateTypeIndex` (or
  `solid:publicTypeIndex`) straight onto the WebID: into the WebID document
  if it accepts the write, else into the first extended profile that does. On
  PodSpaces the WebID document is read-only. It never creates a preferences
  file. That differs from the pattern of Steps 11.4-11.5: it is simpler and
  works on pods with no preferences file, but profile documents are normally
  public, so the private index's *location* becomes public. The index and the
  data stay private.
- **No fallback.** If registration fails, creating the instance fails loudly.
  A registration kept in browser storage would "work" on this device, but
  another device or app could never find the data."""@en ;
    solid-memo:checkedBy <#q-app-walkthrough-4a> .

<#q-app-walkthrough-4a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A user logs in to Solid Memo (2026) with a fresh Community Solid Server pod that has no type index. What does Solid Memo do?"@en ;
    solid-memo:back "Asks the user, then creates and links a private index by default."@en ;
    solid-memo:backNote "Discovery only works if the registration is in the pod, so the app creates the missing index with the user's consent (private unless they choose public) and links it from a writable profile document."@en ;
    solid-memo:distractor <#q-app-walkthrough-4a-d1> ,
                          <#q-app-walkthrough-4a-d2> ,
                          <#q-app-walkthrough-4a-d3> .

<#q-app-walkthrough-4a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Keeps its registration in the browser's local storage until an index exists."@en ;
    solid-memo:distractorNote "There is no local fallback; another device would never find the data."@en .

<#q-app-walkthrough-4a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Reports the pod as broken, because every Solid pod must have an index."@en ;
    solid-memo:distractorNote "A missing index is normal on these pods, not an error."@en .

<#q-app-walkthrough-4a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Stores the data at a fixed path, since a registration is optional."@en ;
    solid-memo:distractorNote "Without a registration, other apps and devices cannot discover the data."@en .

<#ch-app-walkthrough-5>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-app-walkthrough> ;
    schema:position 4 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## A deliberate interop bridge

Solid Memo itself reads only its `sm:Instance` registrations. Inside the
instance it finds the catalogue at a fixed name, `catalog.ttl`, part of its
own layout. But an app that has never heard of Solid Memo would not look for
`sm:Instance`. So each instance also registers a standard class: its
catalogue is a `dcat:Catalog`, and that registration's `solid:instance` names
the catalogue itself. Solid Memo adds, switches and removes this registration
but never reads it: it is there for other apps.

```turtle
<#sm-inst-9f3c1a> a solid:TypeRegistration ;
    solid:forClass sm:Instance ;
    solid:instanceContainer <https://pod.example/solid-memo/main/> .

<#sm-cat-4b7d2e> a solid:TypeRegistration ;
    solid:forClass dcat:Catalog ;
    solid:instance <https://pod.example/solid-memo/main/catalog.ttl#catalog> .
```

---

DCAT is a W3C Recommendation for describing catalogues of datasets. In the
catalogue each deck is both an `sm:Deck` and a `dcat:Dataset`, and its cards
document is linked twice: by `sm:cardsDocument`, which Solid Memo follows, and
by `dcat:distribution` to a node whose `dcat:accessURL` DCAT apps follow. Any
DCAT-aware app can list the user's decks, with titles, descriptions and
licences, knowing nothing about spaced repetition."""@en ;
    solid-memo:checkedBy <#q-app-walkthrough-5a> .

<#q-app-walkthrough-5a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Why does Solid Memo (2026) register `dcat:Catalog` in the user's type index next to its own `sm:Instance`?"@en ;
    solid-memo:back "So apps that know DCAT but not Solid Memo can find the decks."@en ;
    solid-memo:backNote "A shared, standard class is a meeting point: apps that will never know `sm:` can still discover and read the decks as DCAT datasets."@en ;
    solid-memo:distractor <#q-app-walkthrough-5a-d1> ,
                          <#q-app-walkthrough-5a-d2> ,
                          <#q-app-walkthrough-5a-d3> .

<#q-app-walkthrough-5a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "So the catalogue gets its own class, since a class allows one registration."@en ;
    solid-memo:distractorNote "A class may have many registrations; the second class is about which apps recognise it."@en .

<#q-app-walkthrough-5a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "So the catalogue becomes readable by everyone who finds it."@en ;
    solid-memo:distractorNote "A type registration says where data is; it grants no access."@en .

<#q-app-walkthrough-5a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "So the app meets the Solid Protocol's rule that apps publish a catalogue."@en ;
    solid-memo:distractorNote "The Protocol prescribes no app data at all; this is Solid Memo's own choice."@en .

<#ch-app-walkthrough-6>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-app-walkthrough> ;
    schema:position 5 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## The pod layout and the digest

The instance applies the layout rules of Steps 11.9-11.10:

```text
<storage>solid-memo/<name>/
├── meta.ttl               sm:Instance: describes the container itself
├── preferences.ttl        sm:Preferences
├── catalog.ttl            dcat:Catalog + one sm:Deck/dcat:Dataset per deck
├── decks/<id>.ttl         cards
├── reviews/<id>.ttl       review state
├── history/<YYYY-MM>.ttl  answer log
└── digest.ttl             derived cache, keyed by ETags
```

---

What is new is the **digest**: facts per document (such as how many cards are
due), each stamped with the ETag it was learned from. The ports return a
`Since<T>`, for example `readCardsSince(deck, version)`:

```ts
type Since<T> = { unchanged: true }
              | { unchanged: false; value: T; version: string | null };
```

The adapter asks with `If-None-Match: <stamp>`. A `304` becomes
`unchanged: true`, and the fact still holds; a `200` brings the document, and
the fact is recomputed from it and the digest repaired. So a stale digest is
never wrong, only slow. `version` is `null` when the pod sends no ETag: then
nothing can be stamped, and the next visit reads the document again (Step
15.13)."""@en ;
    solid-memo:checkedBy <#q-app-walkthrough-6a> .

<#q-app-walkthrough-6a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Solid Memo's digest cache says a deck's cards document was valid at ETag `\"a1\"`. Since then the user edited the deck on another device. What happens on the next visit?"@en ;
    solid-memo:back "The pod answers 200, not 304, so the app rereads the deck and repairs the digest."@en ;
    solid-memo:backNote "The app asks for the document with `If-None-Match: \"a1\"`; a 200 instead of a 304 means it changed, so it is read and checked in full."@en ;
    solid-memo:distractor <#q-app-walkthrough-6a-d1> ,
                          <#q-app-walkthrough-6a-d2> ,
                          <#q-app-walkthrough-6a-d3> .

<#q-app-walkthrough-6a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The app trusts the digest and shows outdated counts until the digest expires."@en ;
    solid-memo:distractorNote "Every fact is used only after the pod confirms the stamped version is still current."@en .

<#q-app-walkthrough-6a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The pod server updates `digest.ttl` itself, because it saw that the deck changed."@en ;
    solid-memo:distractorNote "The server knows nothing of the digest; the app repairs it."@en .

<#q-app-walkthrough-6a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The app deletes the deck, because its digest entry no longer matches the pod."@en ;
    solid-memo:distractorNote "A stale digest only means more reading; the data itself is never touched."@en .

<#ch-app-walkthrough-7>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-app-walkthrough> ;
    schema:position 6 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Conditional delta writes

Every write goes through `saveDataset` in `datasets.ts`, which applies Step
6.11's read, modify, save:

- an **edit** of a document read earlier is a PATCH of the delta, with
  `If-Match: <the ETag it was read with>`;
- a **creation** sends `If-None-Match: *`;
- a **412** becomes a `PreconditionFailedError` naming the document.

```http
PATCH /solid-memo/main/decks/d1.ttl HTTP/1.1
Content-Type: application/sparql-update
If-Match: "v7"

DELETE DATA { <#card-1> sm:back "Hund" . };
INSERT DATA { <#card-1> sm:back "der Hund" . };
```

(The real body spells every IRI out in full.) The notes app of Step 14.7 sends
the same kind of delta as **N3 Patch**, the one format servers MUST accept (Step
6.7). Solid Memo sends **SPARQL Update** (Step 6.9), which most servers accept
but none must.

---

The type index of Step 15.4 is saved the same way. Other apps' registrations
are not in the delta, so they are kept; and if the index changed since it was
read, the save gets a 412 instead of an edit based on a stale read. That is
stricter than Step 11.5 requires of an insert-only patch."""@en ;
    solid-memo:checkedBy <#q-app-walkthrough-7a> .

<#q-app-walkthrough-7a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Why does Solid Memo save an edit to a pod document as a PATCH of the delta rather than a PUT of the document rebuilt from its own deck model?"@en ;
    solid-memo:back "Triples added by other apps are not in the delta, so they stay."@en ;
    solid-memo:backNote "Rebuilding a document from the app's own model would silently delete what other apps wrote, while sending only the change keeps their data. Solid Memo's PUT for very large edits is different: it starts from the document as read."@en ;
    solid-memo:distractor <#q-app-walkthrough-7a-d1> ,
                          <#q-app-walkthrough-7a-d2> ,
                          <#q-app-walkthrough-7a-d3> .

<#q-app-walkthrough-7a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Solid servers do not allow PUT on documents that already exist."@en ;
    solid-memo:distractorNote "PUT may replace an existing document; it would just drop foreign triples."@en .

<#q-app-walkthrough-7a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A PATCH needs no access rights, while a PUT needs Write access."@en ;
    solid-memo:distractorNote "Both need rights: an insert-only patch needs Append; one that deletes needs Read and Write."@en .

<#q-app-walkthrough-7a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A PATCH is atomic across documents, so a failed save leaves nothing half-written."@en ;
    solid-memo:distractorNote "A PATCH is atomic for one document only; there are no multi-document transactions."@en .

<#ch-app-walkthrough-8>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-app-walkthrough> ;
    schema:position 7 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## What to do on a 412

A 412 means nothing was written. What happens next depends on the data:

- **A user's edit** is not retried. Reapplied to the new version, it could
  undo a change the user never saw, so the app says the data changed
  elsewhere and the user reloads.
- **Data the app can merge mechanically** (the digest, deck groups) is
  reread, changed again and saved, up to a few attempts.

The notes app of Step 14.7 does retry a user's edit, but only through a check:
it refetches and hands the fresh text to the edit's change function, which
reapplies the edit if the text is still what the user saw and otherwise asks
her. A note is one string, so that comparison is easy. Solid Memo cannot know
whether a card edit clashes with an unseen change, so it shows the user the
new version first.

One write needs no precondition at all. Each answer is added to
`history/<YYYY-MM>.ttl` with an insert-only PATCH, without reading the
document and without `If-Match`: each answer is a new subject, so no read is
needed."""@en ;
    solid-memo:checkedBy <#q-app-walkthrough-8a> .

<#q-app-walkthrough-8a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In one Solid Memo session (2026), a write to the digest cache and a user's card edit both get `412 Precondition Failed`. What does Solid Memo do with each?"@en ;
    solid-memo:back "Rereads and retries the digest; asks the user to reload for the edit."@en ;
    solid-memo:backNote "The app retries only what it can merge without judgement, derived or structural data such as the digest and deck groups; a user's edit on top of an unseen change needs the user."@en ;
    solid-memo:distractor <#q-app-walkthrough-8a-d1> ,
                          <#q-app-walkthrough-8a-d2> ,
                          <#q-app-walkthrough-8a-d3> .

<#q-app-walkthrough-8a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Rereads and retries both, since a 412 means nothing was written."@en ;
    solid-memo:distractorNote "Reapplying a user's edit could overwrite a change the user has never seen."@en .

<#q-app-walkthrough-8a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Resends both without `If-Match`, so that the writes go through."@en ;
    solid-memo:distractorNote "That overwrites the other change: the lost update the header exists to prevent."@en .

<#q-app-walkthrough-8a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Asks the user to reload for both, since a 412 always needs a person."@en ;
    solid-memo:distractorNote "The digest is derived data, so the app can merge it mechanically and retry."@en .

<#ch-app-walkthrough-9>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-app-walkthrough> ;
    schema:position 8 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## The vocabulary contract in code

Solid Memo mints its terms under `https://solid-memo.com/ns/vocab/v1.ttl#`,
reuses DCAT, Dublin Core, FOAF, PROV and SKOS where they fit, and evolves the
vocabulary by the rules of Steps 4.12 and 11.11. What matters here is how
those rules reach the code.

`npm run generate` turns `ns/vocab/v1.ttl` into `vocab.generated.ts`, and the
check fails if that file differs from what the Turtle would generate. Each
term's `rdfs:comment` becomes its doc comment, and `owl:deprecated` becomes a
`@deprecated` tag, so the editor strikes through old terms:

```ts
/** How the deck is studied: "front-to-back", … @deprecated Use studyDirection. */
direction: `${SM_NS}direction`,
/** How the deck is studied: a concept of solid-memo:StudyDirections. … */
studyDirection: `${SM_NS}studyDirection`,
```

The new property's values are SKOS concepts such as `sm:frontToBack`, not
strings, and the generated record type allows only the three concept IRIs. A
typo becomes a compile error instead of bad data in someone's pod."""@en ;
    solid-memo:checkedBy <#q-app-walkthrough-9a> .

<#q-app-walkthrough-9a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Solid Memo's Turtle vocabulary marks `sm:direction` as `owl:deprecated`. How does a Solid Memo developer find out before using it in new code?"@en ;
    solid-memo:back "The generated constant carries a `@deprecated` tag the editor flags."@en ;
    solid-memo:backNote "The generator copies `owl:deprecated` into a `@deprecated` doc tag, so the vocabulary's own deprecation shows up as a warning in the editor."@en ;
    solid-memo:distractor <#q-app-walkthrough-9a-d1> ,
                          <#q-app-walkthrough-9a-d2> ,
                          <#q-app-walkthrough-9a-d3> .

<#q-app-walkthrough-9a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The pod server refuses writes that use the deprecated term."@en ;
    solid-memo:distractorNote "Servers know nothing about the app's vocabulary; the warning comes from the generated code."@en .

<#q-app-walkthrough-9a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The SHACL shapes reject every subject that has the old property."@en ;
    solid-memo:distractorNote "Old data still uses it and must stay readable; the warning is for new code."@en .

<#q-app-walkthrough-9a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The constant is removed from the generated file once deprecated."@en ;
    solid-memo:distractorNote "Deprecated terms are kept, because old data in pods still uses them."@en .

<#ch-app-walkthrough-10>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-app-walkthrough> ;
    schema:position 9 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Shapes and migrations in code

Step 11.12 gives the rules; here is where they live:

- **Shapes**: one SHACL file per class and version, open, and without
  `sh:targetClass`, since every version of a class would target the same
  subjects. The validator, in the `shacl` package, picks the shape by
  `rdf:type` plus `sm:formatVersion` (absent means 1).
- **Migrations**: pure modules in the domain package, one per step, typed by
  the generated per-version records, so a step that forgets a required field
  does not compile:

```ts
export const DECK_2_TO_3: MigrationStep<"deck", 2, 3> = {
  shape: "deck", from: 2, to: 3,
  up: ({ direction, ...data }, { subject }) => ({ ...data,
    studyDirection: conceptOfDirection(direction), /* … */ }),
};
```"""@en ;
    solid-memo:checkedBy <#q-app-walkthrough-10a> .

<#q-app-walkthrough-10a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Solid Memo keeps one SHACL shape per class and format version. Why do those shapes leave out `sh:targetClass`?"@en ;
    solid-memo:back "Each version's shape would target the same subjects, so all but one would fail."@en ;
    solid-memo:backNote "With several versions per class, the app picks the shape from the subject's type and `sm:formatVersion` instead of letting every shape target every subject."@en ;
    solid-memo:distractor <#q-app-walkthrough-10a-d1> ,
                          <#q-app-walkthrough-10a-d2> ,
                          <#q-app-walkthrough-10a-d3> .

<#q-app-walkthrough-10a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "SHACL has no `sh:targetClass`, so shapes can only be picked by code."@en ;
    solid-memo:distractorNote "SHACL does define `sh:targetClass`; Solid Memo chooses not to use it."@en .

<#q-app-walkthrough-10a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A shape without a target is closed, which keeps foreign triples out."@en ;
    solid-memo:distractorNote "Closing is `sh:closed`, and Solid Memo's shapes are deliberately open."@en .

<#q-app-walkthrough-10a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Solid servers would otherwise reject writes that do not fit the shape."@en ;
    solid-memo:distractorNote "Servers do not run app shapes; validation happens in the app."@en .

<#ch-app-walkthrough-11>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-app-walkthrough> ;
    schema:position 10 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## The bulk upgrade in code

When an instance's documents need a new format, `solidInstanceCopier.ts`
copies the whole instance to `<name>-<uuid>/`, upgrading as it goes, and only
then switches the type index registrations to the copy:

1. **A write fence.** While the copy runs, the tab's own writes under the
   original are refused before any request leaves the browser.
2. **A check that nothing changed.** The fence cannot stop other tabs or
   apps. So each original document is asked about again with
   `If-None-Match: <the ETag it was copied at>`. A `304` means it is still
   that version; anything else means someone wrote to it, and the run stops
   before the switch. (Without an ETag, `Last-Modified` or a hash of the
   body stands in.)
3. **One commit point.** The switch of the registrations is the moment the
   copy becomes the instance. The original stays as a backup, so a stored
   instance URL can go stale."""@en ;
    solid-memo:checkedBy <#q-app-walkthrough-11a> .

<#q-app-walkthrough-11a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "While Solid Memo's bulk upgrade (2026) copies Alice's instance to a new container, code in the same browser tab tries to save a review under the original container. What happens?"@en ;
    solid-memo:back "The write fence refuses it before the request leaves the browser."@en ;
    solid-memo:backNote "A write to the original after it was copied would be lost at the switch; the fence blocks this tab's writes, and the `If-None-Match` check before the switch catches writes from anywhere else."@en ;
    solid-memo:distractor <#q-app-walkthrough-11a-d1> ,
                          <#q-app-walkthrough-11a-d2> ,
                          <#q-app-walkthrough-11a-d3> .

<#q-app-walkthrough-11a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The pod refuses it, because the copier has locked the original container."@en ;
    solid-memo:distractorNote "Solid has no locks; the fence is in the app and covers this tab only."@en .

<#q-app-walkthrough-11a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It is saved, and the copier merges it into the copy afterwards."@en ;
    solid-memo:distractorNote "Nothing is merged; a review saved from another tab meanwhile is caught by the check and stops the run."@en .

<#q-app-walkthrough-11a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It is sent to the copy instead, since the copy becomes the instance."@en ;
    solid-memo:distractorNote "The fence refuses writes; it does not reroute them."@en .

<#ch-app-walkthrough-12>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-app-walkthrough> ;
    schema:position 11 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Testing across servers

Step 12.13 said to test on several servers. Solid Memo's end-to-end suite runs
its use cases and Solid adapters against servers it starts in Docker, and
separate user journeys drive the built app in a browser against CSS 7:

| Tier | Servers |
|---|---|
| Blocking (gates CI and deploys) | Community Solid Server 6 and 7, node-solid-server 5 and 6 |
| Advisory (reported) | CSS 8 alpha, Pivot (solidcommunity.net's server), Solid-Nextcloud (Nextcloud 32), JavaScript Solid Server (JSS) |

An advisory server keeps an `expected-failures.json`; a job fails only on a
failure it does not list. Tests ask each server instead of assuming: its
`Accept-Patch`, its `Link rel="acl"`.

---

Some deviations found this way, as of October 2026:

- **Community Solid Server 6** ETags change at most once per second.
- **JSS** drops a language tag on a SPARQL Update insert.
- **Solid-Nextcloud**'s `DELETE DATA` deletes every value of the subject and
  predicate.

Step 16.3 weighs what such deviations mean. Step 15.13 shows how the write code copes
with node-solid-server."""@en ;
    solid-memo:checkedBy <#q-app-walkthrough-12a> .

<#q-app-walkthrough-12a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In 2026, Solid Memo tests against several Solid servers, and each advisory server keeps an `expected-failures.json`. What does an entry in it record?"@en ;
    solid-memo:back "A known failure of that server, so only new failures break the job."@en ;
    solid-memo:backNote "Listing known server deviations turns \"red\" into \"something changed\", and the job's summary shows a listed test that now passes, so it can come off the list."@en ;
    solid-memo:distractor <#q-app-walkthrough-12a-d1> ,
                          <#q-app-walkthrough-12a-d2> ,
                          <#q-app-walkthrough-12a-d3> .

<#q-app-walkthrough-12a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A test the developers have not finished writing, so it is skipped for now."@en ;
    solid-memo:distractorNote "Unfinished tests are not the point; each entry names a real failure on that server."@en .

<#q-app-walkthrough-12a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A test that is switched off on every server in the matrix."@en ;
    solid-memo:distractorNote "The list is per server; the same test still runs everywhere else."@en .

<#q-app-walkthrough-12a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A bug in the app, which the app is expected to fix in a later release."@en ;
    solid-memo:distractorNote "Entries record how the server behaves, not defects in the app."@en .

<#ch-app-walkthrough-13>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-app-walkthrough> ;
    schema:position 12 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Writing to node-solid-server

node-solid-server is a blocking server, so every write of Step 15.7 must work
there too. It differs in its ETags, recorded below, and in its PATCH parsing
and size limit, which Solid Memo's code records.

On node-solid-server 6.0.0 (October 2026), an existing Turtle document
answered:

```text
GET    Accept: text/turtle           200, no ETag
HEAD   Accept: text/turtle           200, ETag: W/"2-nOO9…" (of the empty body)
GET    Accept: application/ld+json   200, ETag: W/"a0-XxGgUYFG…"
PATCH  If-Match: "not-the-etag"      200, patch applied
PUT    If-Match: "not-the-etag"      204, document replaced
PUT    If-None-Match: *              412 Precondition Failed
```

---

- **ETags.** A GET of the document as stored carries no ETag. The weak ones
  on HEAD, on writes and on a converted GET are hashes of that response's
  body, not of the resource. `If-Match` is ignored; `If-None-Match: *` is
  honoured by node-solid-server 5.8.8 and 6.0.0, not by 5.7.4. `saveDataset`
  never puts a weak ETag in `If-Match`, so there it writes without the
  header, and the digest (Step 15.6) has nothing to stamp.
- **PATCH bodies.** It fails to parse the body `@inrupt/solid-client` writes,
  so Solid Memo writes its own, one triple per line.
- **PATCH size.** It reads at most 100 kB of a PATCH, so on every server
  Solid Memo sends an edit over 64 KiB as one PUT of the document *as read*
  plus the change, which keeps other apps' triples. With a strong ETag that
  PUT carries `If-Match`; here it cannot, so a change saved elsewhere since
  the read is lost."""@en ;
    solid-memo:checkedBy <#q-app-walkthrough-13a> ,
                         <#q-app-walkthrough-13b> .

<#q-app-walkthrough-13a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On node-solid-server 6.0.0 (2026), a plain Turtle GET returns no ETag and `If-Match` is ignored. What follows for Solid Memo, which caches facts by ETag, on that server?"@en ;
    solid-memo:back "Its edits there cannot be conditional, and the digest cache saves nothing."@en ;
    solid-memo:backNote "Without an ETag there is nothing to put in `If-Match` and nothing to stamp digest facts with, so every visit reads everything; creations stay safe because `If-None-Match: *` is honoured."@en ;
    solid-memo:distractor <#q-app-walkthrough-13a-d1> ,
                          <#q-app-walkthrough-13a-d2> ,
                          <#q-app-walkthrough-13a-d3> .

<#q-app-walkthrough-13a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It refuses to run on node-solid-server, so the user needs another pod."@en ;
    solid-memo:distractorNote "node-solid-server is a blocking server in Solid Memo's test matrix; the app supports it."@en .

<#q-app-walkthrough-13a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It sends `If-Match: *` there to make every edit conditional."@en ;
    solid-memo:distractorNote "`If-Match: *` only checks that the document exists; it cannot detect a change."@en .

<#q-app-walkthrough-13a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server rejects every PATCH, so the app writes with PUT only."@en ;
    solid-memo:distractorNote "PATCH works there for normal-sized edits, and a delta still leaves other apps' triples in place."@en .

<#q-app-walkthrough-13b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On node-solid-server 6.0.0 (2026), which sends no strong ETag, Solid Memo saves a 70 KiB edit of a large deck as one PUT of the document as read plus the change. What does that PUT keep, and what can it lose?"@en ;
    solid-memo:back "It keeps other apps' triples, but loses a change saved elsewhere since the read."@en ;
    solid-memo:backNote "The PUT is built from the document as read, so other apps' triples stay; without `If-Match` it cannot detect a concurrent change, which a PATCH of the delta would simply have kept."@en ;
    solid-memo:distractor <#q-app-walkthrough-13b-d1> ,
                          <#q-app-walkthrough-13b-d2> ,
                          <#q-app-walkthrough-13b-d3> .

<#q-app-walkthrough-13b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It keeps everything, because it carries the `If-Match` of the read."@en ;
    solid-memo:distractorNote "The server sent no strong ETag, so there is no `If-Match` to send, and the server ignores one anyway."@en .

<#q-app-walkthrough-13b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It loses other apps' triples, because a PUT replaces the whole document."@en ;
    solid-memo:distractorNote "It replaces the document with the one it read plus the change, so their triples are in it."@en .

<#q-app-walkthrough-13b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It keeps everything: if the deck changed since the read, the server answers 412."@en ;
    solid-memo:distractorNote "Nothing is checked: the PUT has no `If-Match`, and the server ignores one anyway."@en .

<#q-app-walkthrough-r01>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Which path matches how Solid Memo, a Solid flashcard app, in 2026 gets from a user's WebID to a deck's cards?"@en ;
    solid-memo:back "WebID profile → type index (`sm:Instance`) → instance container → `catalog.ttl` → cards document."@en ;
    solid-memo:backNote "The profile links the type index, whose `sm:Instance` registration names the instance container, where `catalog.ttl` sits at a fixed name and names each deck's cards document. A DCAT-only app takes the `dcat:Catalog` registration and `dcat:accessURL` instead."@en ;
    solid-memo:distractor <#q-app-walkthrough-r01-d1> ,
                          <#q-app-walkthrough-r01-d2> ,
                          <#q-app-walkthrough-r01-d3> .

<#q-app-walkthrough-r01-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "WebID profile → storage root → fixed folder `solid-memo/main/` → `decks/` → the deck's file."@en ;
    solid-memo:distractorNote "The instance is found through the type index, never by guessing its folder; only inside it does the app rely on its own layout."@en .

<#q-app-walkthrough-r01-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "WebID profile → identity provider (`solid:oidcIssuer`) → the provider's list of the user's decks."@en ;
    solid-memo:distractorNote "The identity provider only logs the user in; it knows nothing about the pod's data."@en .

<#q-app-walkthrough-r01-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "WebID profile → storage root → `.acl` → the root's access rules → the cards they name."@en ;
    solid-memo:distractorNote "ACLs say who may access what; they are not used to find data."@en .

<#q-app-walkthrough-r02>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In 2026, Solid Memo adds each answer to a monthly history log in the pod with an insert-only PATCH, without reading the log first and without `If-Match`. Why is that safe when its other edits need `If-Match`?"@en ;
    solid-memo:back "Each answer adds a new subject, so it overwrites nothing."@en ;
    solid-memo:backNote "A lost update happens when a write replaces or deletes something someone else changed; an insert of a new subject touches nothing existing."@en ;
    solid-memo:distractor <#q-app-walkthrough-r02-d1> ,
                          <#q-app-walkthrough-r02-d2> ,
                          <#q-app-walkthrough-r02-d3> .

<#q-app-walkthrough-r02-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "History documents are private, so no other app can write to them."@en ;
    solid-memo:distractorNote "Privacy is not the reason; the safety comes from only adding a fresh subject."@en .

<#q-app-walkthrough-r02-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server locks the log document while the PATCH is applied."@en ;
    solid-memo:distractorNote "Solid has no locks; the insert is safe because it removes nothing."@en .

<#q-app-walkthrough-r02-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The app rewrites the whole month each time, so nothing is lost."@en ;
    solid-memo:distractorNote "The opposite: it sends only the new answer, never the whole document."@en .

<#q-app-walkthrough-r03>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "After a 412 on a user's edit, a Solid notes app whose notes are one string refetches the note and retries instead of asking the user to reload. What condition makes that retry safe?"@en ;
    solid-memo:back "It reapplies the edit only if the fresh text is what the user saw, else asks her."@en ;
    solid-memo:backNote "A reapply is safe only when the edit cannot clash with what changed; a note is one string, so that is easy to check, while Solid Memo cannot tell whether a card edit clashes with an unseen change."@en ;
    solid-memo:distractor <#q-app-walkthrough-r03-d1> ,
                          <#q-app-walkthrough-r03-d2> ,
                          <#q-app-walkthrough-r03-d3> .

<#q-app-walkthrough-r03-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It sends an N3 Patch, which can safely be retried, unlike a SPARQL Update."@en ;
    solid-memo:distractorNote "Both are deltas; the body format says nothing about whether reapplying is safe."@en .

<#q-app-walkthrough-r03-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It runs on CSS, which allows a retry, unlike node-solid-server."@en ;
    solid-memo:distractorNote "A 412 means the same on every server, and node-solid-server ignores `If-Match` anyway."@en .

<#q-app-walkthrough-r03-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Its notes are smaller than 64 KiB, and only small documents may be retried."@en ;
    solid-memo:distractorNote "In Solid Memo the 64 KiB limit decides between PATCH and PUT, not whether to retry."@en .

<#q-app-walkthrough-r04>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A DCAT-only app wants to list Alice's Solid Memo deck titles. Solid Memo created her private type index and linked it from her WebID profile. What does the app read, and what must Alice have granted it?"@en ;
    solid-memo:back "Profile, type index, then `catalog.ttl`, with Read on the private ones."@en ;
    solid-memo:backNote "The `dcat:Catalog` registration in the index leads to the catalogue, where each deck is a `dcat:Dataset` with its title; had the index link been in a preferences file, the app would need Read on that too."@en ;
    solid-memo:distractor <#q-app-walkthrough-r04-d1> ,
                          <#q-app-walkthrough-r04-d2> ,
                          <#q-app-walkthrough-r04-d3> .

<#q-app-walkthrough-r04-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Her profile, then every deck's cards document, with Write on each one."@en ;
    solid-memo:distractorNote "Titles live only in the catalogue, and listing needs only Read."@en .

<#q-app-walkthrough-r04-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only the instance's `meta.ttl`, because it is public by default."@en ;
    solid-memo:distractorNote "`meta.ttl` describes the instance, not the decks, and nothing is public by default."@en .

<#q-app-walkthrough-r04-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Solid Memo's `sm:` vocabulary, then the decks, with no grants needed."@en ;
    solid-memo:distractorNote "Titles are `dcterms:title` on `dcat:Dataset`s, so no `sm:` knowledge is needed, and private data needs Read."@en .

<#q-app-walkthrough-r05>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Another app saved the URL of Alice's Solid Memo instance container last month. Since then she ran Solid Memo's bulk upgrade, which copies the instance to a new container. How should that app find the instance now?"@en ;
    solid-memo:back "Look it up again through the type index registration."@en ;
    solid-memo:backNote "The type index is the one place that says where the current instance lives, so a stored URL is only a cache to re-check."@en ;
    solid-memo:distractor <#q-app-walkthrough-r05-d1> ,
                          <#q-app-walkthrough-r05-d2> ,
                          <#q-app-walkthrough-r05-d3> .

<#q-app-walkthrough-r05-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Follow the HTTP redirect from the old container to the new one."@en ;
    solid-memo:distractorNote "No redirect is set up; the old container stays in place as a backup."@en .

<#q-app-walkthrough-r05-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "List the storage root and pick the newest `solid-memo` container."@en ;
    solid-memo:distractorNote "That guesses from names and dates; only the registration says which copy is current."@en .

<#q-app-walkthrough-r05-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Keep using the saved URL, because container URLs never change."@en ;
    solid-memo:distractorNote "The upgrade moves the instance to a new container and keeps the old one as a backup."@en .

# Chapter 16: Difficulties and open problems.
<#ch-difficulties>
    a solid-memo:Chapter ,
      schema:Syllabus ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <> ;
    schema:position 15 ;
    dcterms:title "Difficulties and open problems"@en ;
    dcterms:description "Judge Solid honestly: which problems come from its design, which from immaturity, and how app builders cope."@en ;
    solid-memo:reviewQuestion <#q-difficulties-r01> ,
                              <#q-difficulties-r02> ,
                              <#q-difficulties-r03> ,
                              <#q-difficulties-r04> ,
                              <#q-difficulties-r05> .

<#ch-difficulties-1>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-difficulties> ;
    schema:position 0 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Spec maturity

The Solid specs are published by the W3C Solid Community Group (CG). A Community Group can publish reports without review by W3C members, and those reports carry no W3C endorsement. Only a Working Group, such as the Linked Web Storage (LWS) Working Group, produces Recommendations, with wide review and two interoperable implementations per feature.

---

As of October 2026, no Solid spec is a Recommendation:

| Spec | Latest published version | Newer draft |
|---|---|---|
| Solid Protocol | 0.11.0 (May 2024), CG report | Editor's draft 0.12.0 (September 2026) |
| Solid-OIDC | 0.1.0 (March 2022) | 2026 draft: adds RFC 9207 `iss` check, client credentials |
| Access Control Policy | 0.9.0 (May 2022), Editor's Draft | Editor's draft (September 2022) |
| SAI | 0.1.0, still in the CG's index | v0.2 (September 2026) |
| Type Indexes | Editor's Draft 1.0.0 (March 2023) | — |

Versions and drafts drift apart; servers may implement either. Before relying on a rule, check which version your target servers implement. A draft's date is usually just when it was last built, not when its rules changed.

**Design or immaturity?** Immaturity: drafts can still change and become Recommendations."""@en ;
    solid-memo:checkedBy <#q-difficulties-1a> ,
                         <#q-difficulties-1b> .

<#q-difficulties-1a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "What does it mean that the Solid Protocol (version 0.11, 2024) is a W3C Community Group report?"@en ;
    solid-memo:back "It was published without W3C member review and carries no W3C endorsement"@en ;
    solid-memo:backNote "Community Groups can publish freely, but only a Working Group produces Recommendations with wide review and an implementation requirement."@en ;
    solid-memo:distractor <#q-difficulties-1a-d1> ,
                          <#q-difficulties-1a-d2> ,
                          <#q-difficulties-1a-d3> .

<#q-difficulties-1a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It is a W3C Recommendation that is waiting for its final version number"@en ;
    solid-memo:distractorNote "Recommendations come only from Working Groups; a CG report is not on that track at all."@en .

<#q-difficulties-1a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It is an IETF RFC that the W3C has adopted as one of its standards"@en ;
    solid-memo:distractorNote "The Solid specs are W3C Community Group documents, not IETF RFCs."@en .

<#q-difficulties-1a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It is a stable standard that only Inrupt's servers are required to follow"@en ;
    solid-memo:distractorNote "It is neither stable nor tied to one vendor; any server may implement it."@en .

<#q-difficulties-1b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A rule appears in the 2026 Solid-OIDC draft but not in the published version 0.1.0 (2022). What should you check before your Solid app depends on it?"@en ;
    solid-memo:back "Whether your target servers implement that draft or 0.1.0"@en ;
    solid-memo:backNote "Drafts move ahead of the published versions, and servers may implement either. A draft's date is usually just when it was last built."@en ;
    solid-memo:distractor <#q-difficulties-1b-d1> ,
                          <#q-difficulties-1b-d2> ,
                          <#q-difficulties-1b-d3> .

<#q-difficulties-1b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Whether the W3C has approved the draft as a Recommendation"@en ;
    solid-memo:distractorNote "No Solid spec is on the Recommendation track, so this check tells you nothing."@en .

<#q-difficulties-1b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Whether the draft's GitHub repository is still active"@en ;
    solid-memo:distractorNote "An active repository says nothing about which version servers implement."@en .

<#q-difficulties-1b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Whether the rule also appears in the WAC specification"@en ;
    solid-memo:distractorNote "WAC covers authorization, not login, so it would not repeat Solid-OIDC rules."@en .

<#ch-difficulties-2>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-difficulties> ;
    schema:position 1 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Fragmentation: two of everything

Several areas have two competing answers:

| Problem | Option A | Option B |
|---|---|---|
| Authorization | WAC | ACP |
| Data discovery | Type Indexes | SAI + Shape Trees |
| Patch format | N3 Patch (required by Protocol 0.11) | SPARQL Update (not in Protocol 0.11) |
| Live updates | Solid Notifications channels | older `solid-0.1` / `solid-0.2` WebSockets |

---

Solid Protocol 0.11 says "Servers MUST conform to either or both" WAC and ACP, so a portable client handles both. ESS (Inrupt's Enterprise Solid Server) uses ACP, and Inrupt does not support running it with WAC in production. SAI lacks server support, so developers use Type Indexes. Protocol 0.11 omits SPARQL Update, yet most servers still accept it. Node Solid Server 6.0.0 (2026) still offers `solid-0.1` WebSockets; ESS 3.0 dropped `solid-0.2` in May 2026.

Detect the option from server headers: the `Accept-Patch` header for the patch format; for ACP, a `rel="type"` link to `acp:AccessControlResource` on the resource that `rel="acl"` points to.

Vendor extensions add more: Inrupt's Access Grants need ESS's Access Grant Service.

**Design or immaturity?** Mostly immaturity: competing drafts and old servers. The WAC-or-ACP choice is in the Protocol itself."""@en ;
    solid-memo:checkedBy <#q-difficulties-2a> ,
                         <#q-difficulties-2b> .

<#q-difficulties-2a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Under the Solid Protocol (0.11, 2024), why must a portable Solid client understand both WAC and ACP?"@en ;
    solid-memo:back "A conforming server may implement only one of them"@en ;
    solid-memo:backNote "Because servers may choose either language, a client that speaks only one cannot manage sharing on some conforming servers."@en ;
    solid-memo:distractor <#q-difficulties-2a-d1> ,
                          <#q-difficulties-2a-d2> ,
                          <#q-difficulties-2a-d3> .

<#q-difficulties-2a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Every server uses WAC for containers and ACP for documents"@en ;
    solid-memo:distractorNote "No such split exists; a server picks WAC, ACP or both for everything."@en .

<#q-difficulties-2a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "ACP is just a newer syntax for writing the same WAC files"@en ;
    solid-memo:distractorNote "ACP is a different model, with matchers and deny rules, in a different document."@en .

<#q-difficulties-2a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The Solid Protocol forbids a server from implementing both"@en ;
    solid-memo:distractorNote "The Protocol says \"either or both\", so a server may support both."@en .

<#q-difficulties-2b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A Solid app shares data using Inrupt's Access Grants. Where will that sharing feature work?"@en ;
    solid-memo:back "Only on servers that run an Access Grant Service, such as ESS"@en ;
    solid-memo:backNote "Vendor extensions need the vendor's service; a feature that relies on them is not portable Solid."@en ;
    solid-memo:distractor <#q-difficulties-2b-d1> ,
                          <#q-difficulties-2b-d2> ,
                          <#q-difficulties-2b-d3> .

<#q-difficulties-2b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "On every server, because Access Grants are part of the Solid Protocol"@en ;
    solid-memo:distractorNote "Access Grants are an Inrupt extension, not a requirement of the Protocol."@en .

<#q-difficulties-2b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "On every server that supports WAC, which grants are built on"@en ;
    solid-memo:distractorNote "Grants are verifiable credentials checked by ESS's own services, not WAC rules."@en .

<#q-difficulties-2b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only on servers that support SAI's Authorization Agent"@en ;
    solid-memo:distractorNote "SAI is a separate draft with its own grant model, not Inrupt's service."@en .

<#ch-difficulties-3>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-difficulties> ;
    schema:position 2 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Servers disagree

Optional rules and servers of different ages give one request different results. Tests in October 2026 recorded:

- JSS 0.0.220: a SPARQL Update insert drops a literal's language tag, leaving a document that no longer parses; `DELETE DATA` deletes nothing yet answers `204`; Turtle ACLs get `415`; concurrent PATCHes get `409`.
- Solid-Nextcloud 0.11 (Nextcloud 32): `DELETE DATA` removes all values of that subject's predicate, not just the named triple; every document's `rel="acl"` link names the folder's ACL; `HEAD` answers `204` for a missing resource; a PATCH gets through a Read-only ACL; concurrent PATCHes get `500`.

So "works on my pod" is not "works on Solid": test on several servers and read results back.

---

Hosts add limits. solidcommunity.net has run Pivot, built on CSS, since January 2025, using CSS's pod quota: 70 MB per pod by default. On CSS 7.2 (2026), a PUT or PATCH past the quota got `413` "Quota exceeded" and kept nothing. Pivot reuses this code, so expect the same. The LWS Working Draft (October 2026) uses `507 Insufficient Storage` instead. Treat any non-2xx write as failed and tell the user.

**Design or immaturity?** Immaturity: optional rules and uneven implementations, not a limit of the model."""@en ;
    solid-memo:checkedBy <#q-difficulties-3a> ,
                         <#q-difficulties-3b> ,
                         <#q-difficulties-3c> .

<#q-difficulties-3a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A Solid app passes every test against Community Solid Server (CSS). What can its developer conclude?"@en ;
    solid-memo:back "It works on that server version, and other servers may still break it"@en ;
    solid-memo:backNote "Servers differ in real, recorded ways, so only testing on several of them tells you how portable an app is."@en ;
    solid-memo:distractor <#q-difficulties-3a-d1> ,
                          <#q-difficulties-3a-d2> ,
                          <#q-difficulties-3a-d3> .

<#q-difficulties-3a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It works on every Solid server, because CSS is the reference implementation"@en ;
    solid-memo:distractorNote "Recorded deviations show other servers answer the same requests differently."@en .

<#q-difficulties-3a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It conforms to the Solid Protocol, because CSS rejects any invalid request"@en ;
    solid-memo:distractorNote "Passing on one server shows nothing about requests other servers handle differently."@en .

<#q-difficulties-3a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It works everywhere, because Solid servers must pass a conformance test suite"@en ;
    solid-memo:distractorNote "No such requirement exists, and recorded servers fail requests that CSS accepts."@en .

<#q-difficulties-3b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid server answers `204` to an app's SPARQL Update `DELETE DATA` request. What is the safest assumption?"@en ;
    solid-memo:back "The request was accepted, so re-read the document if you must be sure"@en ;
    solid-memo:backNote "A success code tells you what the server claims; on servers with known deviations, reading the result back is the only proof."@en ;
    solid-memo:distractor <#q-difficulties-3b-d1> ,
                          <#q-difficulties-3b-d2> ,
                          <#q-difficulties-3b-d3> .

<#q-difficulties-3b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The triples are certainly gone, because `204` means the change was applied"@en ;
    solid-memo:distractorNote "One recorded server (JSS 0.0.220, 2026) answers `204` while deleting nothing."@en .

<#q-difficulties-3b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server rejected the patch, because a delete should return `200`"@en ;
    solid-memo:distractorNote "`204 No Content` is a normal success code for a write."@en .

<#q-difficulties-3b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server deleted the whole document, because `204` means no content is left"@en ;
    solid-memo:distractorNote "`204` only means the response has no body, not that the resource is empty."@en .

<#q-difficulties-3c>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "On solidcommunity.net (Pivot, built on CSS 7.2, 2026), a Solid app's PUT gets `413` because the pod's quota is exceeded. What should the app do?"@en ;
    solid-memo:back "Treat the save as failed and tell the user the pod is full"@en ;
    solid-memo:backNote "On CSS-based hosts such as Pivot, a `413` whose body says \"Quota exceeded\" means nothing was stored; the user must free space first. A `413` can also mean one request was too large, so read the body."@en ;
    solid-memo:distractor <#q-difficulties-3c-d1> ,
                          <#q-difficulties-3c-d2> ,
                          <#q-difficulties-3c-d3> .

<#q-difficulties-3c-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Retry the same PUT until the server accepts it"@en ;
    solid-memo:distractorNote "A refused write keeps nothing, and it fails again until the user frees some space."@en .

<#q-difficulties-3c-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Assume part of the file was saved and write only the rest"@en ;
    solid-memo:distractorNote "On CSS 7.2, none of a write refused for quota is kept."@en .

<#q-difficulties-3c-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Switch to a PATCH request to get around the size limit"@en ;
    solid-memo:distractorNote "On CSS 7.2 the quota counts the whole pod, so a PATCH past it also gets `413`."@en .

<#ch-difficulties-4>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-difficulties> ;
    schema:position 3 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Querying and performance

The Solid Protocol defines reading, writing, containers, auth and notifications. It defines no query. A container listing tells you where resources are, not what is in them, so reading N items costs one listing plus N reads. This is called the **N+1** pattern:

```http
GET /notes/            -> ldp:contains <n1.ttl>, <n2.ttl>, …
GET /notes/n1.ttl
GET /notes/n2.ttl
```

Solid Protocol 0.11 defines no paging either, so a client cannot ask for a page; expect the whole listing in one response. The LWS drafts add paging.

App builders cope with design patterns, not spec features: put many items in one document, keep a summary document, and cache with ETags (send `If-None-Match`; a `304` means your copy is current). Bigger documents mean more write conflicts. Research such as link traversal querying answers simple queries "in the order of seconds" and is not shipped server behaviour.

**Design or immaturity?** Design: the protocol serves documents and has no query or paging."""@en ;
    solid-memo:checkedBy <#q-difficulties-4a> ,
                         <#q-difficulties-4b> .

<#q-difficulties-4a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app lists a container of 200 notes and needs the title of each. Why is this slow?"@en ;
    solid-memo:back "The listing gives only URLs, so the app makes 200 more requests"@en ;
    solid-memo:backNote "Containment says where resources are, not what they hold, which creates the N+1 fetch pattern."@en ;
    solid-memo:distractor <#q-difficulties-4a-d1> ,
                          <#q-difficulties-4a-d2> ,
                          <#q-difficulties-4a-d3> .

<#q-difficulties-4a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The server runs a SPARQL query for each note before replying"@en ;
    solid-memo:distractorNote "Solid servers have no query in the protocol; they simply serve documents."@en .

<#q-difficulties-4a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The listing includes every note's full content, which is large"@en ;
    solid-memo:distractorNote "`ldp:contains` lists members, not their contents."@en .

<#q-difficulties-4a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Each note must be validated against a SHACL shape on the server"@en ;
    solid-memo:distractorNote "Servers do not validate shapes; validation, if any, is the app's job."@en .

<#q-difficulties-4b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Besides putting many items into one document, what design pattern lets a Solid app show many items without one request per item?"@en ;
    solid-memo:back "Keep a summary document that the app updates itself"@en ;
    solid-memo:backNote "Summary documents and larger documents cut the number of requests; ETag caching cuts what each request downloads."@en ;
    solid-memo:distractor <#q-difficulties-4b-d1> ,
                          <#q-difficulties-4b-d2> ,
                          <#q-difficulties-4b-d3> .

<#q-difficulties-4b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Send a SPARQL query to the pod's built-in query endpoint"@en ;
    solid-memo:distractorNote "The Solid Protocol defines no query endpoint for pods."@en .

<#q-difficulties-4b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Ask the server to inline document contents into container listings"@en ;
    solid-memo:distractorNote "Solid listings carry membership and some metadata, never full contents."@en .

<#q-difficulties-4b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Use link traversal querying, which answers in milliseconds"@en ;
    solid-memo:distractorNote "Research reports seconds even for simple queries, and it still fetches documents."@en .

<#ch-difficulties-5>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-difficulties> ;
    schema:position 4 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Consistency

The Solid Protocol defines no cross-document transactions or locks, so two apps, or two tabs, can edit the same document at once.

Protection is opt-in on both sides. Servers only MAY send a strong `ETag` "to encourage clients to opt-in to using the `If-Match` header". A client that never sends `If-Match` can silently overwrite someone else's change. NSS 6.0.0 (tested 2026) sends no ETag for a document returned as stored, and ignores `If-Match`.

---

A PATCH is atomic per document: HTTP requires the server to "apply the entire set of changes atomically". Anything spanning documents is not. On CSS 7.2 (October 2026), an app tagged one item in two documents. The second PATCH sent `If-Match: "stale"`, standing in for an ETag read before another app changed `first.ttl`:

```text
PATCH /alice/notes/deck-b.ttl                    -> 205 Reset Content
PATCH /alice/notes/first.ttl  If-Match: "stale"  -> 412 Precondition Failed
GET   /alice/notes/deck-b.ttl                    -> 200 OK
```

```turtle
<#it> <http://schema.org/text> "Deck B";
    <http://schema.org/keywords> "archived".
```

Nothing rolled back the first write: `deck-b.ttl` is tagged and `first.ttl` is not. A move (insert here, delete there) fails the same way, leaving the item in both places. The app must notice and repair it: retry, undo the first write, or order writes so a half-done state is harmless (data first, index last).

**Design or immaturity?** Design: no cross-document transactions. The optional ETags are a softer, spec-level choice."""@en ;
    solid-memo:checkedBy <#q-difficulties-5a> ,
                         <#q-difficulties-5b> .

<#q-difficulties-5a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A Solid app writes to two documents in a pod, and the second write fails. What does the pod do about the first write?"@en ;
    solid-memo:back "Nothing; the first write stays and the app must repair the state"@en ;
    solid-memo:backNote "PATCH is atomic only per document, so a multi-document operation can be left half done and the app must handle it."@en ;
    solid-memo:distractor <#q-difficulties-5a-d1> ,
                          <#q-difficulties-5a-d2> ,
                          <#q-difficulties-5a-d3> .

<#q-difficulties-5a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It rolls back the first write, because PATCHes run in a transaction"@en ;
    solid-memo:distractorNote "Solid has no transactions across documents; each PATCH stands alone."@en .

<#q-difficulties-5a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It retries the second write until that one succeeds"@en ;
    solid-memo:distractorNote "Servers do not retry client writes; that is the client's decision."@en .

<#q-difficulties-5a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It locks both documents until the app sends a commit request"@en ;
    solid-memo:distractorNote "Solid defines no locks and no commit operation."@en .

<#q-difficulties-5b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Why can't a Solid app count on lost-update protection on every Solid server?"@en ;
    solid-memo:back "Servers needn't send ETags, and clients needn't send `If-Match`"@en ;
    solid-memo:backNote "Conditional writes need the server to send ETags (optional in Solid Protocol 0.11) and the client to send `If-Match`. Not all servers enforce it: NSS 6.0.0 (tested 2026) ignores `If-Match`."@en ;
    solid-memo:distractor <#q-difficulties-5b-d1> ,
                          <#q-difficulties-5b-d2> ,
                          <#q-difficulties-5b-d3> .

<#q-difficulties-5b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "HTTP has no way to make a write depend on the current version"@en ;
    solid-memo:distractorNote "`If-Match` and `412` do exactly that, when both sides use them."@en .

<#q-difficulties-5b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "PATCH bodies cannot carry an `If-Match` header with them"@en ;
    solid-memo:distractorNote "`If-Match` is a request header, not part of the body, and works with PATCH."@en .

<#q-difficulties-5b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "ETags are only defined for containers, not for documents"@en ;
    solid-memo:distractorNote "ETags apply to any resource a server chooses to version."@en .

<#ch-difficulties-6>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-difficulties> ;
    schema:position 5 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Identity and onboarding UX

A Solid app must never guess the user's issuer: it reads `solid:oidcIssuer` from the profile or lets the user pick a provider. The cost: before login, the user must know, and often type, a WebID or a provider. Most people have never needed to.

Issuers carry a lot of trust. The 2026 Solid-OIDC draft adds an "Issuer Trust" section: an identity provider can impersonate you, an outage at it locks you out, and a big shared provider is a single point that many users depend on. Listing several issuers adds redundancy, but each provider you trust is one more place an attacker can break in.

---

People struggle too. A 2024 study by Theys et al. (10 participants, a job application scenario) found the problems came from users' mental models, from fears and doubts eased by brand trust, and from "a challenge of explainability rather than usability". The lesson for app builders: explain what a pod is and what the app will do with it, not only where to click.

**Design or immaturity?** Mostly design: users choose their own provider, so someone has to explain the choice."""@en ;
    solid-memo:checkedBy <#q-difficulties-6a> ,
                         <#q-difficulties-6b> .

<#q-difficulties-6a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Testers move through a Solid app's login screen easily but drop out at \"Enter your WebID\". What does Theys et al.'s 2024 study of Solid users suggest changing?"@en ;
    solid-memo:back "Explain what a pod is and what the app will do with it"@en ;
    solid-memo:backNote "Theys et al. found \"a challenge of explainability rather than usability\", so the fix is explaining pods, not polishing screens."@en ;
    solid-memo:distractor <#q-difficulties-6a-d1> ,
                          <#q-difficulties-6a-d2> ,
                          <#q-difficulties-6a-d3> .

<#q-difficulties-6a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Add a faster issuer lookup so the step takes less time"@en ;
    solid-memo:distractorNote "The testers were not slowed down; the study found understanding, not speed, was the problem."@en .

<#q-difficulties-6a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Remove the WebID field and guess the provider from the email"@en ;
    solid-memo:distractorNote "An email domain says nothing about the identity provider; offer a provider list or ask for the WebID."@en .

<#q-difficulties-6a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Hide the consent screen so there are fewer clicks to make"@en ;
    solid-memo:distractorNote "Fewer clicks do not help people who do not understand what they are agreeing to."@en .

<#q-difficulties-6b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Why is a large shared identity provider a risk in Solid?"@en ;
    solid-memo:back "It can impersonate its users, and its outage locks them all out"@en ;
    solid-memo:backNote "The 2026 Solid-OIDC draft's Issuer Trust section names impersonation, outages and concentration as the risks of shared providers."@en ;
    solid-memo:distractor <#q-difficulties-6b-d1> ,
                          <#q-difficulties-6b-d2> ,
                          <#q-difficulties-6b-d3> .

<#q-difficulties-6b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It can read every pod's data without any access rule allowing it"@en ;
    solid-memo:distractorNote "It can act only as its own users, with their access; other people's data stays closed to it."@en .

<#q-difficulties-6b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It forces users to store their pods with the same company"@en ;
    solid-memo:distractorNote "The issuer, the WebID host and the storage can all be different."@en .

<#q-difficulties-6b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It makes DPoP proofs invalid for servers on other domains"@en ;
    solid-memo:distractorNote "DPoP proofs are bound to the request URL and key, not the provider's domain."@en .

<#ch-difficulties-7>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-difficulties> ;
    schema:position 6 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Privacy pitfalls

Privacy in a pod depends on more than its access rules.

- **The public type index leaks categories.** The Type Indexes draft flags "the visibility of different data types in the Public Type Index". The data may be private, but the registration is not:

  ```turtle
  @prefix solid: <http://www.w3.org/ns/solid/terms#> .

  # In a PUBLIC type index
  <#reg1> a solid:TypeRegistration ;
    solid:forClass <https://example.org/health#MedicationLog> ;
    solid:instanceContainer </private/meds/> .
  ```

  Register in the private index unless others must find the data.
- **Paths and metadata leak.** A path like `/private/divorce-2026/` tells a story, and listings can carry each member's `stat:size` and `dcterms:modified`.
- **Access is per whole resource.** You cannot share one triple, and Leigh Dodds warns of users "accidentally sharing sensitive information because they don't realise the extent of what they're sharing". Split documents along sharing lines.
- **Apps usually inherit the user's access.** WAC's only app limit, `acl:origin`, relies on the browser's `Origin` header, is easy to forge outside a browser and is often unused. So an app usually acts with all of the user's access.

**Design or immaturity?** Design: public indexes, readable paths and whole-document access follow from how pods are built. Weak app limits are partly immaturity: ACP client matchers exist, but not everywhere."""@en ;
    solid-memo:checkedBy <#q-difficulties-7a> ,
                         <#q-difficulties-7b> .

<#q-difficulties-7a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid user's medication log is in a private container, but registered in the public type index. What can a stranger learn?"@en ;
    solid-memo:back "That the user keeps that kind of data, and where"@en ;
    solid-memo:backNote "The public type index reveals which kinds of data exist and where, even when the data itself is private."@en ;
    solid-memo:distractor <#q-difficulties-7a-d1> ,
                          <#q-difficulties-7a-d2> ,
                          <#q-difficulties-7a-d3> .

<#q-difficulties-7a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing, because the container's ACL hides its registration"@en ;
    solid-memo:distractorNote "The registration lives in the public index, which the container's ACL does not protect."@en .

<#q-difficulties-7a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The full contents of the log, because the index copies them"@en ;
    solid-memo:distractorNote "A type index holds registrations only, never the data itself."@en .

<#q-difficulties-7a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only the user's WebID, because indexes hold no class names"@en ;
    solid-memo:distractorNote "Each registration names a class with `solid:forClass`."@en .

<#q-difficulties-7b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In a Solid pod, Bob may read the container `/alice/shared/` but none of the documents in it. What can its listing still tell him?"@en ;
    solid-memo:back "Each member's name, and often its size and last change"@en ;
    solid-memo:backNote "Read on a container shows its members' URLs and, where the server adds them, their `stat:size` and `dcterms:modified`, so names and activity leak even when the contents stay closed."@en ;
    solid-memo:distractor <#q-difficulties-7b-d1> ,
                          <#q-difficulties-7b-d2> ,
                          <#q-difficulties-7b-d3> .

<#q-difficulties-7b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Nothing, because he may not read any of the members"@en ;
    solid-memo:distractorNote "The listing is a resource of its own; Read on the container is enough to see it."@en .

<#q-difficulties-7b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The full contents of every member, inlined into it"@en ;
    solid-memo:distractorNote "A listing carries membership and some metadata, never the contents."@en .

<#q-difficulties-7b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Only how many members there are, without their names"@en ;
    solid-memo:distractorNote "Each `ldp:contains` triple names a member's URL."@en .

<#ch-difficulties-8>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-difficulties> ;
    schema:position 7 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Law and governance

Under the GDPR, a controller decides the purposes and means of processing personal data; a processor only acts on its behalf. Solid splits the classic single company into a pod provider, app developers and the user. So who is the controller?

Pandit (2023), a GDPR researcher, concludes that users who run their own pod server are controllers for storing their data; on a hosted pod they do not control, the provider is. For apps, choosing and revoking access "cannot be sufficient" to make users the controllers, because "the determination of purpose would typically be performed by the apps". The specs also give apps no way to declare who legally operates them. So Solid does not make an app GDPR-compliant; the Flanders deployment reached compliance through governance bodies, not technology alone.

---

Solid's own governance is young: the Open Data Institute (ODI) has been its steward only since October 2024, before which the community had no legal body. Inrupt, co-founded by Tim Berners-Lee, is an influential vendor.

**Design or immaturity?** Both: the split of roles is by design, while the missing legal metadata and young governance are immaturity."""@en ;
    solid-memo:checkedBy <#q-difficulties-8a> ,
                         <#q-difficulties-8b> .

<#q-difficulties-8a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "An app stores users' fitness data in their Solid pods and decides what that data is used for. What is its GDPR role, according to Pandit (2023)?"@en ;
    solid-memo:back "It is still likely a controller, because it decides the purposes"@en ;
    solid-memo:backNote "Pandit argues purpose is usually decided by the app, so the app likely remains a controller; Solid does not make it compliant by itself."@en ;
    solid-memo:distractor <#q-difficulties-8a-d1> ,
                          <#q-difficulties-8a-d2> ,
                          <#q-difficulties-8a-d3> .

<#q-difficulties-8a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It has no role, because the data never leaves the user's pod"@en ;
    solid-memo:distractorNote "The app still processes personal data, and deciding purposes is what makes a controller."@en .

<#q-difficulties-8a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It is only a processor, because the user granted it access"@en ;
    solid-memo:distractorNote "Pandit says granting and revoking access is not enough to make the user the controller."@en .

<#q-difficulties-8a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It is the data subject, because it acts on the user's behalf"@en ;
    solid-memo:distractorNote "The data subject is the person the data is about, never the app."@en .

<#q-difficulties-8b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Inrupt, an influential vendor, adds its own features on top of Solid. Before a Solid app relies on such a feature, what should its builder check?"@en ;
    solid-memo:back "Whether the feature is in a CG spec or only in Inrupt's products"@en ;
    solid-memo:backNote "The ODI stewards Solid and the W3C Solid Community Group publishes the specs; Inrupt is one influential vendor, so features like Access Grants are not portable Solid."@en ;
    solid-memo:distractor <#q-difficulties-8b-d1> ,
                          <#q-difficulties-8b-d2> ,
                          <#q-difficulties-8b-d3> ,
                          <#q-difficulties-8b-d4> .

<#q-difficulties-8b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Whether Inrupt has approved the feature as standard Solid or not yet"@en ;
    solid-memo:distractorNote "The specs belong to the W3C Solid Community Group; Inrupt is one participant."@en .

<#q-difficulties-8b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "Avoid Inrupt's libraries, since they only work with Inrupt's servers"@en ;
    solid-memo:distractorNote "Many of its libraries work with any server; only its extensions need ESS."@en .

<#q-difficulties-8b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Whether the ODI has certified the feature or left it uncertified"@en ;
    solid-memo:distractorNote "The ODI is Solid's steward, not a certifier of vendor features."@en .

<#q-difficulties-8b-d4>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Whether the feature is in Inrupt's server or only in its SDK"@en ;
    solid-memo:distractorNote "Inrupt's server and its SDK are both its own products; what decides portability is whether a CG spec defines the feature."@en .

<#ch-difficulties-9>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-difficulties> ;
    schema:position 8 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Portability and adoption

Solid promises you can take your data elsewhere. In practice, the PDS (personal data store) Migrator project found that downloading data "is a far cry from actually moving it to somewhere else and have everything continue to work as before". Moving breaks things because documents contain absolute URLs, ACLs name the old URIs, and the WebID often lives on the same pod, so moving the pod moves your identity.

App builders can help. Prefer relative IRIs inside a pod's documents, so a document still makes sense at a new address. Never assume the WebID's host is the storage host.

---

Adoption raises harder questions. Platforms earn money by holding data, and pods remove that, so who pays for pods and why would large platforms adopt them? This is widely argued but has no authoritative answer. The deployments that exist are top-down: governments and enterprises such as Flanders' Athumi, with governance bodies.

**Design or immaturity?** Portability breaks partly by design (absolute URLs, WebID on the pod). Adoption is an open question about business models, not about the specs."""@en ;
    solid-memo:checkedBy <#q-difficulties-9a> ,
                         <#q-difficulties-9b> .

<#q-difficulties-9a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A user copies every file from Solid pod A to pod B. Why might their apps break?"@en ;
    solid-memo:back "Absolute URLs and ACL rules still point at pod A"@en ;
    solid-memo:backNote "Data, ACLs and often the WebID reference the old location, so a copy does not \"continue to work as before\"."@en ;
    solid-memo:distractor <#q-difficulties-9a-d1> ,
                          <#q-difficulties-9a-d2> ,
                          <#q-difficulties-9a-d3> .

<#q-difficulties-9a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Pod B cannot store RDF that another server created"@en ;
    solid-memo:distractorNote "RDF documents are portable; the problem is the URLs inside them."@en .

<#q-difficulties-9a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Copying files deletes their type registrations on pod A"@en ;
    solid-memo:distractorNote "Copying does not change the source pod at all."@en .

<#q-difficulties-9a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Pod B stores the copies as non-RDF, so apps cannot parse them"@en ;
    solid-memo:distractorNote "A proper copy keeps each file's content type; the URLs are the issue."@en .

<#q-difficulties-9b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "As of 2026, who drives the Solid deployments that exist, and do they come from the top down or from the bottom up?"@en ;
    solid-memo:back "Governments and enterprises, from the top down"@en ;
    solid-memo:backNote "Real deployments such as Flanders' Athumi run with governance bodies behind them. Wider adoption is still an open question about business models."@en ;
    solid-memo:distractor <#q-difficulties-9b-d1> ,
                          <#q-difficulties-9b-d2> ,
                          <#q-difficulties-9b-d3> ,
                          <#q-difficulties-9b-d4> .

<#q-difficulties-9b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Consumers choosing their own pod providers, from the bottom up"@en ;
    solid-memo:distractorNote "Consumer adoption is still an open question. The deployments that exist come from governments and enterprises, from the top down."@en .

<#q-difficulties-9b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Large social platforms moving user data into pods, from the top down"@en ;
    solid-memo:distractorNote "Platforms earn money by holding data, so why they would adopt pods is an open question. The deployments that exist come from governments and enterprises."@en .

<#q-difficulties-9b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "Research projects only, with no live deployments"@en ;
    solid-memo:distractorNote "Flanders' Athumi, for example, is a live government deployment."@en .

<#q-difficulties-9b-d4>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Governments and enterprises, from the bottom up"@en ;
    solid-memo:distractorNote "The deployments are run by governments and enterprises, but they are top-down, with governance bodies behind them."@en .

<#q-difficulties-r01>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "An app shows 200 notes, each stored as its own document in a pod. What performance cost comes from Solid's design, not from its draft specs?"@en ;
    solid-memo:back "Reading many small documents takes one request each"@en ;
    solid-memo:backNote "The N+1 fetch pattern, one listing plus one read per note, comes from the document-centric design with no query, not from the specs' draft status."@en ;
    solid-memo:distractor <#q-difficulties-r01-d1> ,
                          <#q-difficulties-r01-d2> ,
                          <#q-difficulties-r01-d3> ,
                          <#q-difficulties-r01-d4> ,
                          <#q-difficulties-r01-d5> ,
                          <#q-difficulties-r01-d6> .

<#q-difficulties-r01-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "Solid-OIDC 0.1.0 lacks the RFC 9207 `iss` check"@en ;
    solid-memo:distractorNote "A 2026 draft already adds it; that is draft status, not design."@en .

<#q-difficulties-r01-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "The Solid specs carry no W3C endorsement"@en ;
    solid-memo:distractorNote "Endorsement is exactly what a Recommendation would add."@en .

<#q-difficulties-r01-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "Servers answer the same PATCH in different ways"@en ;
    solid-memo:distractorNote "Those are uneven implementations of optional rules, not a limit of the model."@en .

<#q-difficulties-r01-d4>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The container listing comes back one page at a time"@en ;
    solid-memo:distractorNote "Solid Protocol 0.11 defines no paging; expect the whole listing in one response."@en .

<#q-difficulties-r01-d5>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "One query reads them all, but servers run it slowly"@en ;
    solid-memo:distractorNote "The Solid Protocol defines no query at all; that gap is why each note needs its own read."@en .

<#q-difficulties-r01-d6>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Every note is re-read on each visit, since pods send no ETags"@en ;
    solid-memo:distractorNote "Servers may send ETags, and caching with `If-None-Match` and `304` is how app builders cope."@en .

<#q-difficulties-r02>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A Solid app keeps a summary document in the pod to avoid N+1 fetches. Which new risk does that add?"@en ;
    solid-memo:back "The summary and the data can disagree if one write fails"@en ;
    solid-memo:backNote "Writes that span documents are not atomic, so a summary can fall out of step with the data and the app must repair it."@en ;
    solid-memo:distractor <#q-difficulties-r02-d1> ,
                          <#q-difficulties-r02-d2> ,
                          <#q-difficulties-r02-d3> .

<#q-difficulties-r02-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "None, because the server keeps the summary in sync automatically"@en ;
    solid-memo:distractorNote "Servers do not know your summary vocabulary; only your app updates it."@en .

<#q-difficulties-r02-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Reading the summary still costs N requests, as the server expands it"@en ;
    solid-memo:distractorNote "It is one ordinary document, fetched with one request."@en .

<#q-difficulties-r02-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "None, because PATCHes to the summary and an item are atomic together"@en ;
    solid-memo:distractorNote "PATCH is atomic only per document, not across two."@en .

<#q-difficulties-r03>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A Solid app must run on CSS, ESS and Solid-Nextcloud. Which approach copes best with Solid's fragmentation and server differences?"@en ;
    solid-memo:back "Detect features from headers and test on each server"@en ;
    solid-memo:backNote "Portable apps discover capabilities from headers, handle WAC and ACP, and test on every target server."@en ;
    solid-memo:distractor <#q-difficulties-r03-d1> ,
                          <#q-difficulties-r03-d2> ,
                          <#q-difficulties-r03-d3> .

<#q-difficulties-r03-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Target the newest editor's drafts, which every server follows"@en ;
    solid-memo:distractorNote "Servers implement different versions; drafts run ahead of most of them."@en .

<#q-difficulties-r03-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Use one vendor's extensions everywhere to hide the differences"@en ;
    solid-memo:distractorNote "Extensions such as Access Grants only work where the vendor's service runs."@en .

<#q-difficulties-r03-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Rely on status codes alone, since all servers return the same"@en ;
    solid-memo:distractorNote "Recorded deviations include servers giving success codes for failed or wrong writes."@en .

<#q-difficulties-r04>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid health app registers its data in the public type index and stores it under `/health/hiv-clinic/`. Which risk does Solid's access control not prevent?"@en ;
    solid-memo:back "Strangers learning what data exists from the index entry and path"@en ;
    solid-memo:backNote "Access rules protect contents, but public index entries and descriptive paths reveal data categories on their own."@en ;
    solid-memo:distractor <#q-difficulties-r04-d1> ,
                          <#q-difficulties-r04-d2> ,
                          <#q-difficulties-r04-d3> .

<#q-difficulties-r04-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Strangers reading the records inside the private container"@en ;
    solid-memo:distractorNote "The ACL still protects the documents' contents."@en .

<#q-difficulties-r04-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The app being unable to find its own data on the next login"@en ;
    solid-memo:distractorNote "A public registration is easy to find; that is the problem."@en .

<#q-difficulties-r04-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The pod refusing to store health data without a GDPR consent record"@en ;
    solid-memo:distractorNote "Pods do not check legal grounds; that is the app's and controller's job."@en .

<#q-difficulties-r05>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid app lists a container with 50,000 members on a server that follows Solid Protocol 0.11 (2024). What does it get back?"@en ;
    solid-memo:back "The whole listing in one response, with no paging"@en ;
    solid-memo:backNote "Solid 0.11 has no query and no paging, so a client cannot ask for part of a big container, and each member still needs its own GET."@en ;
    solid-memo:distractor <#q-difficulties-r05-d1> ,
                          <#q-difficulties-r05-d2> ,
                          <#q-difficulties-r05-d3> .

<#q-difficulties-r05-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The first page, with a `next` link to fetch the rest of the members"@en ;
    solid-memo:distractorNote "Paging links come from the LWS drafts, not Solid 0.11."@en .

<#q-difficulties-r05-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An error, until the app asks for a smaller range of members"@en ;
    solid-memo:distractorNote "Solid 0.11 defines no range or limit for container listings."@en .

<#q-difficulties-r05-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Each member's full contents, inlined into the container listing"@en ;
    solid-memo:distractorNote "A listing carries membership and some metadata, never the contents."@en .

# Chapter 17: The road ahead: Linked Web Storage.
<#ch-lws>
    a solid-memo:Chapter ,
      schema:Syllabus ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <> ;
    schema:position 16 ;
    dcterms:title "The road ahead: Linked Web Storage"@en ;
    dcterms:description "Where Solid is heading: the W3C **Linked Web Storage** (LWS) Working Drafts as of October 2026, what they change, and how to write Solid code today that will carry over."@en ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:reviewQuestion <#q-lws-r01> ,
                              <#q-lws-r02> ,
                              <#q-lws-r03> ,
                              <#q-lws-r04> ,
                              <#q-lws-r05> .

<#ch-lws-1>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-lws> ;
    schema:position 0 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## The LWS Working Group

No Solid specification is a W3C standard. In September 2024 the W3C membership approved a charter for a **Working Group** to put Solid's ideas on the standards track. It is called **Linked Web Storage (LWS)**, not "Solid". Its mission is to "enable the development of web applications where data storage, entity authentication, access control, and application provider are all loosely coupled".

The group does not start from scratch: the **Solid Protocol v0.11.0** is one of its two input documents, next to the Fedora API 1.0, and the draft "draws heavily" from it, though LWS changes terms and mechanisms. It must produce the **Linked Web Storage Protocol 1.0**, plus a test suite, an implementation report and a threat model.

---

Two charter rules matter to app builders:

- **Two implementations per feature.** A spec can only leave Candidate Recommendation with "at least two independent interoperable implementations of every feature". That targets the "works on my pod" problem.
- **Scope limits.** New identity mechanisms and new data formats are out of scope. LWS reuses existing web standards rather than inventing a new stack.

This chapter describes Working Drafts as of October 2026. Names, media types and rules may change in any later draft."""@en ;
    solid-memo:checkedBy <#q-lws-1a> ,
                         <#q-lws-1b> .

<#q-lws-1a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "You know the Solid Protocol 0.11 well. How much of it will help you read the W3C Linked Web Storage (LWS) drafts?"@en ;
    solid-memo:back "Most of it: LWS starts from Solid 0.11 and reworks parts."@en ;
    solid-memo:backNote "LWS takes Solid Protocol v0.11.0 as an input document, draws heavily from it, and turns its ideas into a standards-track protocol, with its own design changes."@en ;
    solid-memo:distractor <#q-lws-1a-d1> ,
                          <#q-lws-1a-d2> ,
                          <#q-lws-1a-d3> .

<#q-lws-1a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "None of it: LWS is a rival project with separate roots."@en ;
    solid-memo:distractorNote "The charter names Solid Protocol v0.11.0 as an input document, and the draft \"draws heavily\" from it."@en .

<#q-lws-1a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "All of it: LWS republishes Solid 0.11 unchanged as a standard."@en ;
    solid-memo:distractorNote "LWS changes terms and mechanisms; it is not a renamed copy of Solid 0.11."@en .

<#q-lws-1a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Little of it: LWS swaps RDF for a brand-new data format."@en ;
    solid-memo:distractorNote "New data formats are explicitly out of the group's scope."@en .

<#q-lws-1b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "The W3C Linked Web Storage (LWS) charter requires \"two independent interoperable implementations of every feature\". Why should that matter to a Solid app developer?"@en ;
    solid-memo:back "Features must work alike on separate servers."@en ;
    solid-memo:backNote "Requiring two independent, interoperable implementations, checked by test suites, is aimed directly at the server inconsistency that troubles Solid today."@en ;
    solid-memo:distractor <#q-lws-1b-d1> ,
                          <#q-lws-1b-d2> ,
                          <#q-lws-1b-d3> .

<#q-lws-1b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It forces every user to keep two pods as a backup."@en ;
    solid-memo:distractorNote "The rule is about server implementations of the spec, not about how many pods a user has."@en .

<#q-lws-1b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It lets each vendor define a feature in its own way."@en ;
    solid-memo:distractorNote "The opposite: the implementations must be interoperable, verified by open test suites."@en .

<#q-lws-1b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "It means apps must ship two versions of client code."@en ;
    solid-memo:distractorNote "The rule applies to servers passing the spec's tests, so one client should work against both."@en .

<#ch-lws-2>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-lws> ;
    schema:position 1 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Timeline and status

Standards take time, and LWS has slipped. The charter planned a First Public Working Draft (FPWD) for March 2025 and a Recommendation for September 2026. The real FPWD of LWS Protocol 1.0 came on **31 March 2026**. Working Drafts have followed every few weeks; as of October 2026 the latest is dated **5 October 2026**, the 14th Working Draft since the FPWD.

The charter, first set to end on 8 September 2026, was extended to **8 January 2027** while a new charter is prepared. W3C members had not yet voted on it in October 2026.

Every LWS document is a **Working Draft**. Its status section even says "This is an unofficial proposal", and a draft may be "updated, replaced, or obsoleted". So:

- Servers and libraries you use today implement the Solid Protocol 0.11 stack.
- LWS tells you the *direction*, not the exact syntax you will ship against."""@en ;
    solid-memo:checkedBy <#q-lws-2a> ,
                         <#q-lws-2b> .

<#q-lws-2a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "It is October 2026. A colleague wants to rewrite your Solid app to use only the W3C Linked Web Storage (LWS) Protocol. What is the best advice?"@en ;
    solid-memo:back "Keep building on Solid 0.11 and track the LWS drafts."@en ;
    solid-memo:backNote "LWS is a moving Working Draft, while today's servers and libraries implement the Solid Protocol 0.11 stack, so you build on that and watch LWS."@en ;
    solid-memo:distractor <#q-lws-2a-d1> ,
                          <#q-lws-2a-d2> ,
                          <#q-lws-2a-d3> .

<#q-lws-2a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Switch now, because LWS is a W3C Recommendation."@en ;
    solid-memo:distractorNote "LWS Protocol 1.0 is still a Working Draft, not a Recommendation."@en .

<#q-lws-2a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Wait, because LWS will be a Recommendation by late 2026."@en ;
    solid-memo:distractorNote "The September 2026 target has slipped: LWS is still a Working Draft and its charter was extended."@en .

<#q-lws-2a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Switch now, because drafts are frozen once published."@en ;
    solid-memo:distractorNote "A Working Draft can be updated, replaced or obsoleted, and LWS has changed many times."@en .

<#q-lws-2b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "In 2026 the W3C Linked Web Storage (LWS) Working Group's charter, which had planned a Recommendation for September 2026, was extended while a new one is prepared. What does that tell you when you plan a Solid app?"@en ;
    solid-memo:back "The schedule slipped, so expect more draft changes before a standard."@en ;
    solid-memo:backNote "The extension shows the work needs more time, so the drafts will keep changing while you build on the Solid Protocol 0.11 stack."@en ;
    solid-memo:distractor <#q-lws-2b-d1> ,
                          <#q-lws-2b-d2> ,
                          <#q-lws-2b-d3> .

<#q-lws-2b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "LWS is final, because a charter is only extended once the spec is done."@en ;
    solid-memo:distractorNote "An extension gives the group more time; LWS Protocol 1.0 is still a Working Draft."@en .

<#q-lws-2b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "LWS is being abandoned, because the group is about to close."@en ;
    solid-memo:distractorNote "The group was extended, not closed, and still publishes Working Drafts."@en .

<#q-lws-2b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Write no Solid code until the members vote on the new charter."@en ;
    solid-memo:distractorNote "Today's servers and libraries implement Solid 0.11, whatever the vote decides."@en .

<#ch-lws-3>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-lws> ;
    schema:position 2 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Storage and containers in LWS

LWS says **storage** where Solid says pod: a **storage root** holding **containers** and **data resources**. Its terms live under `https://www.w3.org/ns/lws#`.

The biggest change: **URL structure is not containment**. "Clients SHOULD NOT assume that URI structure reflects containment". A resource names its parent with a `rel="up"` Link header, and every GET and HEAD response also points to its storage:

```http
Link: </alice/notes/>; rel="up"
Link: <https://storage.example/>; rel="https://www.w3.org/ns/lws#storage"
```

---

A container lists its children in `items`, as JSON-LD (`application/lws+json`); abridged from the draft:

```json
{ "@context": "https://www.w3.org/ns/lws/v1",
  "id": "/alice/notes/", "type": "Container", "totalItems": 1,
  "items": [{ "type": "DataResource", "id": "/alice/notes/todo.json",
    "format": "application/json", "size": 2048,
    "modified": "2025-11-24T13:00:00Z" }] }
```

Each item MUST have an `id` and a `type`, a data resource MUST have a `format`, and `size` and `modified` are SHOULD. Solid 0.11 listings SHOULD carry similar metadata as RDF (`stat:size`, `dcterms:modified`); LWS gives it a fixed JSON shape. What is new is **paging**: servers SHOULD split a large listing with `first`/`next`/`prev`/`last` links.

---

The Solid **storage description** becomes a W3C **Controlled Identifier (CID)** document (`application/lws+cid`) listing a `StorageRoot` service. A CID document describes an identifier: the keys that may sign for it and the services it uses, like a generalised WebID profile."""@en ;
    solid-memo:checkedBy <#q-lws-3a> ,
                         <#q-lws-3b> .

<#q-lws-3a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In the W3C Linked Web Storage (LWS) drafts (October 2026), how should a client find the parent container of `https://storage.example/a/b/c`?"@en ;
    solid-memo:back "Read the response's `rel=\"up\"` Link header."@en ;
    solid-memo:backNote "Containment in LWS is expressed by links, `rel=\"up\"` on the child and `items` in the container, not by the shape of the URL."@en ;
    solid-memo:distractor <#q-lws-3a-d1> ,
                          <#q-lws-3a-d2> ,
                          <#q-lws-3a-d3> .

<#q-lws-3a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Strip the last path segment from the URL."@en ;
    solid-memo:distractorNote "LWS says clients should not assume URI structure reflects containment."@en .

<#q-lws-3a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Look up the URL in the storage description."@en ;
    solid-memo:distractorNote "The storage description advertises the storage root and services, not each resource's parent."@en .

<#q-lws-3a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Read the `ldp:contains` triples of `/a/b/`."@en ;
    solid-memo:distractorNote "LWS listings use `items` in `application/lws+json`, and guessing `/a/b/` is itself the URL-structure assumption."@en .

<#q-lws-3b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "What does a container listing in the W3C Linked Web Storage (LWS) drafts (October 2026) add that a Solid Protocol 0.11 listing lacks?"@en ;
    solid-memo:back "Paging links (`first`, `next`) for large containers."@en ;
    solid-memo:backNote "Solid listings already SHOULD carry per-item metadata as RDF; LWS gives it a fixed JSON shape and adds paging. It is still not query: each item needs its own GET."@en ;
    solid-memo:distractor <#q-lws-3b-d1> ,
                          <#q-lws-3b-d2> ,
                          <#q-lws-3b-d3> .

<#q-lws-3b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The full contents of every contained resource."@en ;
    solid-memo:distractorNote "A listing still only describes the items; you GET each one to read it."@en .

<#q-lws-3b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A query endpoint for searching inside the listed items."@en ;
    solid-memo:distractorNote "LWS defines no query mechanism; the metadata only helps you choose what to fetch."@en .

<#q-lws-3b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The access rules that apply to each listed item."@en ;
    solid-memo:distractorNote "A listing carries no access rules; access goes through tokens and grants."@en .

<#ch-lws-4>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-lws> ;
    schema:position 3 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Metadata as linksets

In the Solid Protocol 0.11 you find a resource's **description resource** through `rel="describedby"` and edit it as RDF. LWS replaces it with a **linkset** (RFC 9264): a JSON document that lists typed links about one resource, served as `application/linkset+json`. A response points to it with a Link header:

```http
Link: </alice/notes/shoppinglist.txt.meta>; rel="linkset"; type="application/linkset+json"
```

The linkset itself looks like this (from the draft's example):

```json
{ "linkset": [ { "anchor": "/alice/personalinfo.json",
    "describedby": [ { "href": "/schemas/personal-info.json" } ] } ] }
```

The draft's examples put linksets at `.meta` URLs, but nothing guarantees that shape: the only promise is the `rel="linkset"` link. Writing to a linkset (a "metadata update") changes the links, not the resource itself. Servers MUST accept JSON Patch for that and advertise it in `Accept-Patch` (Step 17.5 explains JSON Patch)."""@en ;
    solid-memo:checkedBy <#q-lws-4a> ,
                         <#q-lws-4b> .

<#q-lws-4a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "One W3C Linked Web Storage (LWS) server (drafts, October 2026) answers with `Link: <…/todo.json.meta>; rel=\"linkset\"`. How should your app find a resource's linkset on a different LWS server?"@en ;
    solid-memo:back "Read the `rel=\"linkset\"` Link header that server sends."@en ;
    solid-memo:backNote "A linkset URL is discovered, not built: follow `rel=\"linkset\"` on each response, whatever shape the URL has."@en ;
    solid-memo:distractor <#q-lws-4a-d1> ,
                          <#q-lws-4a-d2> ,
                          <#q-lws-4a-d3> .

<#q-lws-4a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Append `.meta`, since every LWS server uses that suffix."@en ;
    solid-memo:distractorNote "The draft's examples use `.meta`, but LWS only guarantees the link relation, not the URL shape."@en .

<#q-lws-4a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Follow `rel=\"describedby\"` and parse the Turtle it returns."@en ;
    solid-memo:distractorNote "That is Solid 0.11's description resource; LWS metadata is a JSON linkset."@en .

<#q-lws-4a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Look up each resource's linkset in the storage description."@en ;
    solid-memo:distractorNote "The storage description lists the storage root and services, not per-resource metadata."@en .

<#q-lws-4b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "What is a linkset in the W3C Linked Web Storage (LWS) drafts (October 2026)?"@en ;
    solid-memo:back "A JSON document of typed links about one resource."@en ;
    solid-memo:backNote "A linkset (RFC 9264) collects the links about a resource, such as `describedby`, in one JSON document found through `rel=\"linkset\"`."@en ;
    solid-memo:distractor <#q-lws-4b-d1> ,
                          <#q-lws-4b-d2> ,
                          <#q-lws-4b-d3> .

<#q-lws-4b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A Turtle document of triples that describes the resource."@en ;
    solid-memo:distractorNote "That is Solid 0.11's description resource; a linkset is `application/linkset+json`."@en .

<#q-lws-4b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A list of every resource stored inside one container."@en ;
    solid-memo:distractorNote "That is the container listing and its `items`."@en .

<#q-lws-4b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An access policy saying who may read the resource."@en ;
    solid-memo:distractorNote "LWS defines no ACL files; access goes through tokens and grants."@en .

<#ch-lws-5>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-lws> ;
    schema:position 4 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Patch formats

Solid 0.11 requires N3 Patch. An LWS server "MUST minimally support JSON Patch (`application/json-patch+json`)" (RFC 6902). A JSON Patch is a list of operations (`add`, `remove`, `replace` and others) on a JSON document. Each `path` is a JSON Pointer into it: `/done` means the `done` key at the top level. So it fits JSON resources and linksets, not Turtle:

```http
PATCH /alice/notes/todo.json HTTP/1.1
Content-Type: application/json-patch+json
If-Match: "v7"

[{ "op": "replace", "path": "/done", "value": true }]
```

Other formats are optional. The draft's example storage description lists SPARQL Update as a patch capability for Turtle, and clients SHOULD NOT assume a patch format the server does not advertise. Where no advertised format fits, a PUT of the whole new content still works; the draft's own PUT example sends `If-Match`, and clients SHOULD use conditional requests."""@en ;
    solid-memo:checkedBy <#q-lws-5a> ,
                         <#q-lws-5b> .

<#q-lws-5a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "You want to update `/alice/notes/todo.json` on a W3C Linked Web Storage (LWS) server (drafts, October 2026). Its `Accept-Patch` lists only `application/json-patch+json`, and your code supports N3 Patch and JSON Patch. What should it send?"@en ;
    solid-memo:back "A JSON Patch, the format the server advertises."@en ;
    solid-memo:backNote "Pick the patch format from what the server advertises; under LWS, JSON Patch is the one every server must support, and it fits a JSON resource."@en ;
    solid-memo:distractor <#q-lws-5a-d1> ,
                          <#q-lws-5a-d2> ,
                          <#q-lws-5a-d3> .

<#q-lws-5a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "An N3 Patch, since every server must accept it."@en ;
    solid-memo:distractorNote "N3 Patch is a Solid 0.11 requirement; LWS only requires JSON Patch."@en .

<#q-lws-5a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A SPARQL Update, since most Solid servers accept it."@en ;
    solid-memo:distractorNote "LWS servers need not accept it, and this one does not advertise it."@en .

<#q-lws-5a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "A DELETE, then a POST of the new version."@en ;
    solid-memo:distractorNote "That loses the resource's URL; a supported PATCH, or a conditional PUT, is the right tool."@en .

<#q-lws-5b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "For the Turtle document `/alice/notes/list.ttl`, a W3C Linked Web Storage (LWS) server (drafts, October 2026) advertises only JSON Patch. How should your app change one triple in it?"@en ;
    solid-memo:back "PUT the whole edited document with `If-Match`."@en ;
    solid-memo:backNote "JSON Patch fits JSON, not Turtle. A conditional PUT of the document as read plus the edit keeps other apps' triples and cannot overwrite a change you have not seen."@en ;
    solid-memo:distractor <#q-lws-5b-d1> ,
                          <#q-lws-5b-d2> ,
                          <#q-lws-5b-d3> .

<#q-lws-5b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Send a JSON Patch whose `path` names the triple."@en ;
    solid-memo:distractorNote "A JSON Pointer addresses keys in a JSON document; Turtle has none."@en .

<#q-lws-5b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Send an N3 Patch, which every LWS server accepts."@en ;
    solid-memo:distractorNote "LWS requires only JSON Patch; N3 Patch works only where advertised."@en .

<#q-lws-5b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Convert it to JSON-LD, then send a JSON Patch."@en ;
    solid-memo:distractorNote "That changes the format every other app reads; a conditional PUT keeps the document Turtle."@en .

<#ch-lws-6>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-lws> ;
    schema:position 5 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## ETags, recursive delete and quotas

**ETags.** Solid 0.11 says servers MAY send an `ETag`. LWS says servers MUST send one on GET and HEAD responses. Clients SHOULD use conditional requests such as `If-Match` for writes, and a request whose precondition fails gets `412 Precondition Failed`. Rules still move: from the FPWD (March 2026) to 21 August 2026 the drafts answered `428 Precondition Required` to an unconditional PUT on a resource with ETags and to linkset writes without `If-Match`; the September 2026 drafts dropped both rules.

---

**Recursive delete.** Solid answers `409` when you delete a non-empty container, so you delete children first. LWS keeps that `409` by default, but a server MAY support recursive delete, which a client requests with the `Depth: infinity` header from WebDAV (RFC 4918):

```http
DELETE /alice/notes/ HTTP/1.1
Depth: infinity
```

**Quotas.** On CSS 7.2 a write past a pod quota gets `413` and stores nothing; the LWS draft's operations overview names `507 Insufficient Storage` for quota exceeded. Treat both alike."""@en ;
    solid-memo:checkedBy <#q-lws-6a> ,
                         <#q-lws-6b> .

<#q-lws-6a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your Solid app always sends `If-Match` with the last `ETag` it saw. Why does this habit fit the W3C Linked Web Storage (LWS) drafts (October 2026) better than the Solid Protocol 0.11?"@en ;
    solid-memo:back "LWS servers must send an `ETag` on every read."@en ;
    solid-memo:backNote "In Solid 0.11 an `ETag` is a MAY, so `If-Match` only helps on servers that send one; LWS makes the `ETag` mandatory, so `If-Match` protects against lost updates on every LWS server."@en ;
    solid-memo:distractor <#q-lws-6a-d1> ,
                          <#q-lws-6a-d2> ,
                          <#q-lws-6a-d3> .

<#q-lws-6a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "LWS rejects any write sent without `If-Match`."@en ;
    solid-memo:distractorNote "Sending `If-Match` is a SHOULD; the earlier drafts' 428 rule for unconditional PUTs was dropped in September 2026."@en .

<#q-lws-6a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Solid 0.11 servers reject `If-Match` headers."@en ;
    solid-memo:distractorNote "Solid encourages conditional requests; it just doesn't require servers to send ETags."@en .

<#q-lws-6a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "LWS uses ETags to carry the access token."@en ;
    solid-memo:distractorNote "ETags identify a version of a resource; they have nothing to do with authorization."@en .

<#q-lws-6b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Your app must delete `/alice/old-project/`, a container that still holds files, on a W3C Linked Web Storage (LWS) server (drafts, October 2026). What should the client do?"@en ;
    solid-memo:back "Try `Depth: infinity`; if refused, delete children first."@en ;
    solid-memo:backNote "LWS keeps Solid's `409` for non-empty containers unless the client asks for recursion with `Depth: infinity`, which servers MAY support; a portable client falls back to deleting the children first."@en ;
    solid-memo:distractor <#q-lws-6b-d1> ,
                          <#q-lws-6b-d2> ,
                          <#q-lws-6b-d3> .

<#q-lws-6b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Send a plain `DELETE`; LWS then removes the contents too."@en ;
    solid-memo:distractorNote "Without `Depth: infinity` the server must refuse a non-empty container with `409`."@en .

<#q-lws-6b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Send `Depth: infinity`; every LWS server must support it."@en ;
    solid-memo:distractorNote "Recursive delete is a MAY, so a client must cope with a server that refuses."@en .

<#q-lws-6b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Send `Depth: 1`; repeat it to delete one level at a time."@en ;
    solid-memo:distractorNote "LWS defines recursive delete only through `Depth: infinity`."@en .

<#ch-lws-7>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-lws> ;
    schema:position 6 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Authentication suites

Solid 0.11 has one login method: Solid-OIDC with a WebID. LWS builds identity on the **CID document**: your identifier dereferences to a document that lists your keys and the services you trust. Authentication is split into **suites**, each its own draft:

- **OpenID Connect.** The user's identifier goes in the standard **`sub`** claim, not a `webid` claim. It must resolve to a CID document, and the issuer is trusted when that document has a `service` of type `https://www.w3.org/ns/lws#OpenIdProvider` whose endpoint equals the token's `iss`. This replaces `solid:oidcIssuer`, but the idea is the same: dereference the identifier to learn whom to trust.
- **SAML 2.0**, the XML-based single sign-on standard common in enterprises. Like OpenID Connect, it needs an identity provider.
- **Self-signed identity** with a CID. A bot or server signs its own JWT with `sub` = `iss` = `client_id` = its own URI, and its CID document publishes the key. **No identity provider is needed**.

---

The suites move too: they were first published as drafts on 23 April 2026, a `did:key` suite among them, which was discontinued on 29 September 2026. Whatever the suite, the credential is not sent to the storage directly; it is exchanged for an access token (Step 17.8)."""@en ;
    solid-memo:checkedBy <#q-lws-7a> ,
                         <#q-lws-7b> .

<#q-lws-7a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In the OpenID Connect suite of the W3C Linked Web Storage (LWS) drafts (October 2026), where does the user's identifier appear in the ID token?"@en ;
    solid-memo:back "In the `sub` claim."@en ;
    solid-memo:backNote "LWS puts the subject identifier in `sub` and verifies the issuer through a `service` entry in the identifier's CID document."@en ;
    solid-memo:distractor <#q-lws-7a-d1> ,
                          <#q-lws-7a-d2> ,
                          <#q-lws-7a-d3> .

<#q-lws-7a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In a custom `webid` claim."@en ;
    solid-memo:distractorNote "That is Solid-OIDC; the LWS suite says the ID token must use `sub`."@en .

<#q-lws-7a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In the `aud` claim."@en ;
    solid-memo:distractorNote "`aud` names the intended audiences, such as the client, not the user."@en .

<#q-lws-7a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In the `iss` claim."@en ;
    solid-memo:distractorNote "`iss` identifies the OpenID provider that issued the token."@en .

<#q-lws-7b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "A nightly backup bot has its own identifier and no account at any identity provider. Which authentication suite of the W3C Linked Web Storage (LWS) drafts (October 2026) lets it authenticate?"@en ;
    solid-memo:back "The self-signed suite with its own CID."@en ;
    solid-memo:backNote "With self-signed identity, the agent signs its own JWT and publishes its key in its CID document, so no identity provider is involved."@en ;
    solid-memo:distractor <#q-lws-7b-d1> ,
                          <#q-lws-7b-d2> ,
                          <#q-lws-7b-d3> .

<#q-lws-7b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The OpenID Connect suite via the owner's provider."@en ;
    solid-memo:distractorNote "This suite needs an identity provider to issue the ID token, and the bot has none."@en .

<#q-lws-7b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The SAML 2.0 suite via a company login."@en ;
    solid-memo:distractorNote "SAML also needs an identity provider, and the bot has none."@en .

<#q-lws-7b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "No suite, because bots need no authentication."@en ;
    solid-memo:distractorNote "The storage still needs to know who is asking before granting access."@en .

<#ch-lws-8>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-lws> ;
    schema:position 7 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Access tokens

How does an app get to read a protected resource? Through an **authorization server**, a service that hands out access tokens for the storage:

1. The app requests the resource. The storage answers `401`, and its `WWW-Authenticate` header names the authorization server (`as_uri`). That server's metadata lives at `/.well-known/lws-configuration`.
2. The app sends its credential (an ID token or a self-signed JWT) to the authorization server using **OAuth 2.0 Token Exchange** (RFC 8693).
3. The authorization server returns an **access token**: a short-lived JWT (300 seconds or less is recommended) with a single `aud`, that storage.
4. The app retries the request with the access token.

The token carries `sub`, `iss`, `aud`, `exp` and `client_id`. Solid-OIDC already passes the client ID to the pod, but Web Access Control (WAC) cannot use it and only Access Control Policy (ACP) can. LWS makes `client_id` a **required** claim in every storage token, so whatever enforcement layer a server uses can rely on it."""@en ;
    solid-memo:checkedBy <#q-lws-8a> ,
                         <#q-lws-8b> .

<#q-lws-8a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid 0.11, Solid-OIDC already passes the client ID to the pod. What do the W3C Linked Web Storage (LWS) drafts (October 2026) add by making `client_id` a required access-token claim?"@en ;
    solid-memo:back "Any enforcement layer can count on knowing the app."@en ;
    solid-memo:backNote "In Solid 0.11 the client ID reaches the pod but only ACP can match on it; LWS requires it in every access token, so any enforcement layer, not just ACP, can restrict by app."@en ;
    solid-memo:distractor <#q-lws-8a-d1> ,
                          <#q-lws-8a-d2> ,
                          <#q-lws-8a-d3> .

<#q-lws-8a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The user can log in without any identity provider."@en ;
    solid-memo:distractorNote "That is the self-signed identity suite; `client_id` identifies the app."@en .

<#q-lws-8a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The token becomes valid on every storage the user has."@en ;
    solid-memo:distractorNote "The token has a single audience, one storage."@en .

<#q-lws-8a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The app's identity replaces the user's identity in it."@en ;
    solid-memo:distractorNote "The token still carries the user in `sub`; `client_id` adds the app."@en .

<#q-lws-8b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A W3C Linked Web Storage (LWS) access token (drafts, October 2026) was issued for `https://storage-a.example/`. What happens if the app sends it to `https://storage-b.example/`?"@en ;
    solid-memo:back "Storage B rejects it, since it names another audience."@en ;
    solid-memo:backNote "Each LWS access token has a single audience, so an app needs a separate token exchange for every storage it talks to."@en ;
    solid-memo:distractor <#q-lws-8b-d1> ,
                          <#q-lws-8b-d2> ,
                          <#q-lws-8b-d3> .

<#q-lws-8b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Storage B accepts it, since the same user signed in."@en ;
    solid-memo:distractorNote "The `aud` claim limits the token to storage A, whoever the user is."@en .

<#q-lws-8b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Storage B accepts it until its 300 seconds run out."@en ;
    solid-memo:distractorNote "The lifetime limits when a token works, the audience limits where."@en .

<#q-lws-8b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Storage B forwards it to storage A to have it checked."@en ;
    solid-memo:distractorNote "Each storage validates the tokens it receives; nothing is forwarded."@en .

<#ch-lws-9>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-lws> ;
    schema:position 8 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## Access requests and grants

An app that lacks access can ask for it. An **AccessRequest** is "a request by an agent for access to resources"; an **AccessGrant** is "an authorization by a storage controller granting access to resources". The storage description names the endpoints for both (`AccessRequestService`, `AccessGrantService`). So the app asks, and the storage's controller, not the app, issues the grant.

---

Their contents follow an **ODRL-based profile**. ODRL is a W3C vocabulary for permissions with conditions: who may do what, for which purpose, until when. An access entry has a type (`AccessPolicy`), actions (`read`, `modify`, `create`, `delete`), an `assignee`, a `target` and constraints. A constraint compares a `leftOperand` (such as `purpose`, `client` or `dateTime`) to a `rightOperand` (the allowed value). A grant, abridged from the draft's example:

```json
{ "@context": ["https://www.w3.org/ns/lws/v1"],
  "type": ["AccessGrant"], "storage": "https://storage.example/",
  "access": [{ "type": ["AccessPolicy"], "action": ["read"],
    "assignee": "https://id.example/agent",
    "target": { "type": "StorageResource",
                "value": ["https://storage.example/root/projects/"] },
    "constraint": [{ "leftOperand": "purpose", "operator": "eq",
      "rightOperand": "https://purpose.example/collaboration" }] }] }
```

LWS does **not** mandate WAC or ACP; how grants map onto an enforcement layer is out of scope."""@en ;
    solid-memo:checkedBy <#q-lws-9a> ,
                         <#q-lws-9b> .

<#q-lws-9a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Your Solid server implements Web Access Control (WAC). Do the W3C Linked Web Storage (LWS) drafts (October 2026) require you to replace it with Access Control Policy (ACP)?"@en ;
    solid-memo:back "No, LWS mandates neither WAC nor ACP."@en ;
    solid-memo:backNote "LWS standardises tokens and access requests and grants, but leaves how a server enforces them (WAC, ACP or something else) to the implementation."@en ;
    solid-memo:distractor <#q-lws-9a-d1> ,
                          <#q-lws-9a-d2> ,
                          <#q-lws-9a-d3> .

<#q-lws-9a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Yes, LWS standardises ACP as the only model."@en ;
    solid-memo:distractorNote "The draft deliberately leaves the enforcement layer out of scope."@en .

<#q-lws-9a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Yes, WAC is forbidden because it lacks deny rules."@en ;
    solid-memo:distractorNote "LWS doesn't forbid any access control language."@en .

<#q-lws-9a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "No, LWS requires WAC on every server."@en ;
    solid-memo:distractorNote "LWS doesn't mandate WAC either; the charter only lists WAC and ACP as candidate inputs."@en .

<#q-lws-9b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front """In this W3C Linked Web Storage (LWS) access grant (draft, October 2026), what does the `purpose` constraint express?

```json
{ "type": ["AccessGrant"],
  "access": [{ "type": ["AccessPolicy"], "action": ["read"],
    "assignee": "https://id.example/agent",
    "target": { "value": ["https://storage.example/root/projects/"] },
    "constraint": [{ "leftOperand": "purpose", "operator": "eq",
      "rightOperand": "https://purpose.example/collaboration" }] }] }
```"""@en ;
    solid-memo:back "Read access holds only for collaboration use."@en ;
    solid-memo:backNote "A constraint compares a `leftOperand` (`purpose`) to a `rightOperand` (the collaboration purpose), narrowing the `read` grant to that use."@en ;
    solid-memo:distractor <#q-lws-9b-d1> ,
                          <#q-lws-9b-d2> ,
                          <#q-lws-9b-d3> .

<#q-lws-9b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The agent may also modify the shared projects."@en ;
    solid-memo:distractorNote "The only action granted is `read`; a constraint narrows access, it never adds actions."@en .

<#q-lws-9b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Every app may read the projects for any reason."@en ;
    solid-memo:distractorNote "The grant names one `assignee`, and the constraint limits the purpose."@en .

<#q-lws-9b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The grant expires once the collaboration ends."@en ;
    solid-memo:distractorNote "An end date would be a `dateTime` constraint; `purpose` says what use is allowed."@en .

<#ch-lws-10>
    a solid-memo:Step ,
      schema:LearningResource ;
    solid-memo:formatVersion 1 ;
    schema:isPartOf <#ch-lws> ;
    schema:position 9 ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:theory """## What carries over and what doesn't

LWS renames and reworks a lot, but the core ideas of Solid stay:

- **Decoupling.** Storage, identity, access control and apps can each come from a different provider.
- **URI identity.** You are a URI that dereferences to a document listing whom to trust (WebID profile today, CID document in LWS).
- **Permissioned access.** Data stays private unless access is granted.
- **Following links.** Clients discover storage, parents, metadata and capabilities through Link headers and descriptions.

---

Some of Solid's open problems stay open: LWS defines **no query**; **shapes and schema drift** are untouched because data formats are out of scope; **business models** and **GDPR roles** are not protocol questions.

The habit that transfers best: **never hard-code URL patterns**. Find the storage from a Link header, the metadata from `describedby` (later `linkset`), the patch format from `Accept-Patch`, and the parent from links rather than path cutting. Code written that way needs fewer changes when LWS lands."""@en ;
    solid-memo:checkedBy <#q-lws-10a> ,
                         <#q-lws-10b> .

<#q-lws-10a>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Which coding habit in a Solid 0.11 app will carry over best to the W3C Linked Web Storage (LWS) protocol (drafts, October 2026)?"@en ;
    solid-memo:back "Read URLs and formats from links and headers."@en ;
    solid-memo:backNote "Code that follows links and reads what a server announces keeps working when the details change, and those details are exactly what differs between Solid 0.11 and LWS."@en ;
    solid-memo:distractor <#q-lws-10a-d1> ,
                          <#q-lws-10a-d2> ,
                          <#q-lws-10a-d3> .

<#q-lws-10a-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Build `.acl` and `.meta` URLs by adding suffixes."@en ;
    solid-memo:distractorNote "Those suffixes are only a server convention even today; LWS moves metadata to linksets and defines no ACL files."@en .

<#q-lws-10a-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Treat each URL path segment as a container."@en ;
    solid-memo:distractorNote "LWS says URI structure should not be assumed to reflect containment."@en .

<#q-lws-10a-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Require N3 Patch for every update the app makes."@en ;
    solid-memo:distractorNote "LWS only guarantees JSON Patch, so the format should come from what the server advertises."@en .

<#q-lws-10b>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A manager hopes the W3C Linked Web Storage (LWS) protocol (drafts, October 2026) will make your Solid app GDPR-compliant once it is a standard. What is the accurate reply?"@en ;
    solid-memo:back "No, GDPR roles lie outside a storage protocol."@en ;
    solid-memo:backNote "LWS standardises storage, authentication and authorization; GDPR roles, like business models, remain outside it."@en ;
    solid-memo:distractor <#q-lws-10b-d1> ,
                          <#q-lws-10b-d2> ,
                          <#q-lws-10b-d3> .

<#q-lws-10b-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "No, because LWS grants cannot state a purpose."@en ;
    solid-memo:distractorNote "Grants can carry a `purpose` constraint, but that still doesn't settle GDPR roles."@en .

<#q-lws-10b-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Yes, LWS access grants make the app a processor only."@en ;
    solid-memo:distractorNote "Apps that decide purposes are still likely controllers, and a protocol can't change that."@en .

<#q-lws-10b-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Yes, because data never leaves the user's storage."@en ;
    solid-memo:distractorNote "Apps still read and process the data, and GDPR roles follow who decides the purposes."@en .

<#q-lws-r01>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "A Solid 0.11 app finds a resource's parent by cutting the last path segment, and its metadata by appending `.meta`. Which two changes in the W3C Linked Web Storage (LWS) drafts (October 2026) make these tricks unsafe?"@en ;
    solid-memo:back "Containment via `rel=\"up\"`, and linksets found by link."@en ;
    solid-memo:backNote "Both tricks were only conventions even in Solid 0.11. LWS says clients SHOULD NOT assume URL containment and gives the linkset URL only through `rel=\"linkset\"`."@en ;
    solid-memo:distractor <#q-lws-r01-d1> ,
                          <#q-lws-r01-d2> ,
                          <#q-lws-r01-d3> .

<#q-lws-r01-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "JSON Patch for writes, and ETags required on every read."@en ;
    solid-memo:distractorNote "These affect how the app writes, not how it finds parents or metadata."@en .

<#q-lws-r01-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The `sub` claim, and OAuth 2.0 Token Exchange."@en ;
    solid-memo:distractorNote "These are authentication changes; they don't touch URL discovery."@en .

<#q-lws-r01-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Access grants, and the two-implementation rule."@en ;
    solid-memo:distractorNote "Neither changes how resource URLs relate to each other."@en .

<#q-lws-r02>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "In Solid 0.11 the WebID profile names the trusted issuer with `solid:oidcIssuer`. In the W3C Linked Web Storage (LWS) drafts (October 2026), where is the trusted issuer listed instead?"@en ;
    solid-memo:back "As a service entry in the user's CID document"@en ;
    solid-memo:backNote "The idea stays and the mechanism changes: you still dereference the user's identifier (the `sub` claim) to learn whom to trust. The issuer is trusted when that CID document has a `service` of type `lws:OpenIdProvider` whose endpoint equals the token's `iss`."@en ;
    solid-memo:distractor <#q-lws-r02-d1> ,
                          <#q-lws-r02-d2> ,
                          <#q-lws-r02-d3> ,
                          <#q-lws-r02-d4> ,
                          <#q-lws-r02-d5> ,
                          <#q-lws-r02-d6> .

<#q-lws-r02-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "`ldp:contains` becomes `items`, still derived from paths."@en ;
    solid-memo:distractorNote "LWS decouples containment from URL paths, so the idea changes too, not only the name."@en .

<#q-lws-r02-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "N3 Patch becomes SPARQL Update as the required format."@en ;
    solid-memo:distractorNote "LWS requires JSON Patch, not SPARQL Update."@en .

<#q-lws-r02-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    owl:deprecated true ;
    solid-memo:distractorText "Access control moves from the server into each app."@en ;
    solid-memo:distractorNote "The storage still enforces access, using tokens and grants."@en .

<#q-lws-r02-d4>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In a `webid` claim inside the ID token"@en ;
    solid-memo:distractorNote "LWS puts the user's identifier in the standard `sub` claim, not a `webid` claim, and a token cannot vouch for its own issuer: trust comes from the document the identifier dereferences to."@en .

<#q-lws-r02-d5>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "As a service entry in the storage description"@en ;
    solid-memo:distractorNote "The storage description lists the storage's own services, such as `StorageRoot` and the access request and grant endpoints. The trusted issuer is found by dereferencing the user's identifier, not the storage."@en .

<#q-lws-r02-d6>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "In the access grant from the storage's controller"@en ;
    solid-memo:distractorNote "An access grant says who may do what with which resources; it does not name the identity provider to trust."@en .

<#q-lws-r03>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:front "Before an LWS spec can leave Candidate Recommendation, the charter asks for two independent interoperable implementations, and the group must ship a test suite. Which known Solid 0.11 problem does that target?"@en ;
    solid-memo:back "Servers behaving differently for one feature."@en ;
    solid-memo:backNote "The two-interoperable-implementations rule and the test suite target server divergence, the \"works on my pod\" problem; query, shapes and business models remain open."@en ;
    solid-memo:distractor <#q-lws-r03-d1> ,
                          <#q-lws-r03-d2> ,
                          <#q-lws-r03-d3> .

<#q-lws-r03-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "The lack of any query mechanism in the protocol."@en ;
    solid-memo:distractorNote "LWS defines no query; listings only add metadata and paging, so no implementation rule touches this."@en .

<#q-lws-r03-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Schema drift between different apps' data shapes."@en ;
    solid-memo:distractorNote "Data formats are out of the charter's scope."@en .

<#q-lws-r03-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Unclear business models for storage providers."@en ;
    solid-memo:distractorNote "That is an economic question no protocol settles."@en .

<#q-lws-r04>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Which sequence matches the W3C Linked Web Storage (LWS) drafts (October 2026) for an app reading a protected resource?"@en ;
    solid-memo:back "401, token exchange at the authorization server, retry."@en ;
    solid-memo:backNote "The storage's `401` names the authorization server; the client trades its credential via Token Exchange for a short-lived, storage-specific access token and retries."@en ;
    solid-memo:distractor <#q-lws-r04-d1> ,
                          <#q-lws-r04-d2> ,
                          <#q-lws-r04-d3> .

<#q-lws-r04-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Send the ID token straight to the storage on every request."@en ;
    solid-memo:distractorNote "LWS exchanges credentials at an authorization server for an access token first."@en .

<#q-lws-r04-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Read the resource's ACL, then fetch with the user's password."@en ;
    solid-memo:distractorNote "LWS doesn't use passwords at the storage or mandate ACL files."@en .

<#q-lws-r04-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Get one access token, then reuse it on every storage you use."@en ;
    solid-memo:distractorNote "Access tokens have a single audience, one storage."@en .

<#q-lws-r05>
    a solid-memo:Card ;
    solid-memo:formatVersion 5 ;
    dcterms:created "2026-10-08T00:00:00.000Z"^^xsd:dateTime ;
    solid-memo:textFormat solid-memo:markdown ;
    solid-memo:front "Solid Memo, a Solid flashcard app, follows the type index to its decks, never guesses a deck's path, and saves edits to Turtle documents as SPARQL Update deltas sent with `If-Match`. Which part would need the most change under the W3C Linked Web Storage (LWS) drafts (October 2026)?"@en ;
    solid-memo:back "Saving edits as SPARQL Update deltas to Turtle documents."@en ;
    solid-memo:backNote "LWS guarantees only JSON Patch, so SPARQL Update works only where the server advertises it; the app would need to check and fall back, for example to a conditional PUT of the document as read plus the edit. Its link-following and conditional writes carry over."@en ;
    solid-memo:distractor <#q-lws-r05-d1> ,
                          <#q-lws-r05-d2> ,
                          <#q-lws-r05-d3> .

<#q-lws-r05-d1>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Following the type index to find its decks."@en ;
    solid-memo:distractorNote "Following links instead of guessing paths is the habit that carries over best."@en .

<#q-lws-r05-d2>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Sending `If-Match` with the ETag each edit was read with."@en ;
    solid-memo:distractorNote "LWS makes ETags mandatory, so conditional writes work better, not worse."@en .

<#q-lws-r05-d3>
    a solid-memo:Distractor ,
      schema:Answer ;
    solid-memo:formatVersion 1 ;
    solid-memo:distractorText "Refusing to guess a deck's path from its name or date."@en ;
    solid-memo:distractorNote "Not hard-coding URL patterns is exactly what LWS rewards."@en .

<#turtle>
    a dcat:Distribution ;
    dcat:accessURL <> ;
    dcat:downloadURL <> ;
    dcat:mediaType <https://www.iana.org/assignments/media-types/text/turtle> ;
    dcterms:format <http://publications.europa.eu/resource/authority/file-type/RDF_TURTLE> .
