profile
viewpoint

albertmeronyo/SemanticCorrelation 7

Playground to provide semantic similarity measures between statistically correlated concepts

csarven/270a.info 6

:fist: 270a.info Linked Dataspaces

csarven/bfs-linked-data 3

BFS (Bundesamt für Statistik - Swiss Federal Statistics Office) Linked Data

csarven/270a.info.interlinks 1

270a.info interlinks

csarven/abs-linked-data 1

ABS (Australian Bureau of Statistics) Linked Data

csarven/bis-linked-data 1

BIS (Bank for International Settlements) Linked Data

csarven/DAT3 1

General Assembly's Data Science course in Washington, DC

csarven/dbpedia-links 1

A repo that contains outgoing links in ntriples format

albertmeronyo/lsd-dsd-similarity 0

Playground for computing similarity between two arbitrary Data Structure Definitions (DSD) in RDF Data Cube

push eventsolid/notifications-panel

Sarven Capadisli

commit sha 27fd20f2346c08c962f34a6d07e40e3f427dddd5

Minor

view details

push time in 2 days

push eventsolid/notifications-panel

Sarven Capadisli

commit sha b14a60799c1eb931c4f05639240e6fd8d92e70c8

Update 2022-01-20 minutes

view details

push time in 2 days

startedaudapolis/audapolis

started time in 2 days

PR opened solid/notifications-panel

Add 2022-01-20 agenda and minutes

Request to merge in 24 hours following meeting.

+106 -0

0 comment

1 changed file

pr created time in 2 days

create barnchsolid/notifications-panel

branch : meeting/2022-01-20

created branch time in 2 days

Pull request review commentsolid/notifications

Define LinkedDataNotificationsSubscription2021 type for Solid Notifications

+<!DOCTYPE html>+<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">+  <head>+    <meta charset="utf-8" />+    <title>Solid Notifications: LinkedDataNotificationsSubscription2021</title>+    <meta content="width=device-width, initial-scale=1" name="viewport" />+    <link href="https://www.w3.org/StyleSheets/TR/2021/W3C-ED" media="all" rel="stylesheet" title="W3C-ED" />+<style>+body {+counter-reset:section;+counter-reset:sub-section;+}+em.rfc2119 { color: #900; }+code, samp { color: #c83500; }+pre code, pre samp { color: #000; }+dfn { font-weight:inherit; }+.do.fragment a { border-bottom:0; }+.do.fragment a:hover { background:none; border-bottom:0; }+section figure pre { margin:1em 0; display:block; }+cite .bibref { font-style: normal; }+.tabs nav ul li { margin:0; }+div.issue, div.note, div.warning {+clear: both;+margin: 1em 0;+padding: 1em 1.2em 0.5em;+position: relative;+}+div.issue h3, div.note h3,+div.issue h4, div.note h4,+div.issue h5, div.note h5 {+margin:0;+font-weight:normal;+font-style:normal;+}+div.issue h3 > span, div.note h3 > span,+div.issue h4 > span, div.note h4 > span,+div.issue h5 > span, div.note h5 > span {+text-transform: uppercase;+}+div.issue h3, div.issue h4, div.issue h5 {+color:#ae1e1e;+}+div.note h3, div.note h4, div.note h5 {+color:#178217;+}+figure .example-h {+margin-top:0;+text-align: left;+color:#827017;+}+figure .example-h > span {+text-transform: uppercase;+}++header address a[href] {+float: right;+margin: 1rem 0 0.2rem 0.4rem;+background: transparent none repeat scroll 0 0;+border: medium none;+text-decoration: none;+}+header address img[src*="logos/W3C"] {+background: #1a5e9a none repeat scroll 0 0;+border-color: #1a5e9a;+border-image: none;+border-radius: 0.4rem;+border-style: solid;+border-width: 0.65rem 0.7rem 0.6rem;+color: white;+display: block;+font-weight: bold;+}+main article > h1 {+font-size: 220%;+font-weight:bold;+}++article section:not([id=abstract]):not([id=sotd]):not([id=references]):not([id=appendix]):not([id=acknowledgements]):not([id=change-log]):not([id=exit-criteria]) {+counter-increment:section;+counter-reset:sub-section;+}+article section:not([id=abstract]):not([id=sotd]):not([id=references]):not([id=appendix]):not([id=acknowledgements]):not([id=change-log]) section:not([id$=references]):not([id=exit-criteria]) {+counter-increment:sub-section;+counter-reset:sub-sub-section;+}+article section:not([id=abstract]):not([id=sotd]):not([id=references]):not([id=appendix]):not([id=acknowledgements]):not([id=change-log]) section:not([id$=references]):not([id=exit-criteria]) section {+counter-increment:sub-sub-section;+counter-reset:sub-sub-sub-section;+}+article section:not([id=abstract]):not([id=sotd]):not([id=references]):not([id=appendix]):not([id=acknowledgements]):not([id=change-log]) section:not([id$=references]):not([id=exit-criteria]) section section {+counter-increment:sub-sub-sub-section;+counter-reset:sub-sub-sub-sub-section;+}+article section:not([id=abstract]):not([id=sotd]):not([id=references]):not([id=appendix]):not([id=acknowledgements]):not([id=change-log]):not([id=exit-criteria]):not([id^=table-of-]) > h2:before {+content:counter(section) ".\00a0";+}+section:not([id$=references]):not([id^=change-log]):not([id=exit-criteria]) > h3:before {+content:counter(section) "." counter(sub-section) "\00a0";+}+section > h4:before {+content:counter(section)"." counter(sub-section) "." counter(sub-sub-section) "\00a0";+}+#acknowledgements ul { padding: 0; margin:0 }+#acknowledgements li { display:inline; }+#acknowledgements li:after { content: ", "; }+#acknowledgements li:last-child:after { content: ""; }++aside.do { overflow:inherit; }+aside.do blockquote {+padding: 0; border: 0; margin: 0;+}+dl[id^="document-"] ul {+padding-left:0;+list-style-type:none;+}+dl [rel~="odrl:action"],+dl [rel~="odrl:action"] li {+display: inline;+}+dl [rel~="odrl:action"] li:after {+content: ",";+}+dl [rel~="odrl:action"] li:last-child:after {+content: "";+}+</style>+    <link href="https://dokie.li/media/css/dokieli.css" media="all" rel="stylesheet" />+    <script src="https://dokie.li/scripts/dokieli.js"></script>+  </head>++  <body about="" prefix="rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns# rdfs: http://www.w3.org/2000/01/rdf-schema# owl: http://www.w3.org/2002/07/owl# xsd: http://www.w3.org/2001/XMLSchema# dcterms: http://purl.org/dc/terms/ skos: http://www.w3.org/2004/02/skos/core# prov: http://www.w3.org/ns/prov# mem: http://mementoweb.org/ns# qb: http://purl.org/linked-data/cube# schema: http://schema.org/ doap: http://usefulinc.com/ns/doap# deo: http://purl.org/spar/deo/ fabio: http://purl.org/spar/fabio/ cito: http://purl.org/spar/cito/ as: https://www.w3.org/ns/activitystreams# ldp: http://www.w3.org/ns/ldp# earl: http://www.w3.org/ns/earl# spec: http://www.w3.org/ns/spec# rel: https://www.w3.org/ns/iana/link-relations/relation# odrl: http://www.w3.org/ns/odrl/2/" typeof="schema:CreativeWork prov:Entity as:Article">+    <header>+      <address>+        <a class="logo" href="https://solidproject.org/"><img height="66" width="72" alt="Solid Project" src="https://solidproject.org/TR/solid.svg"/></a>+      </address>+    </header>++    <main>+      <article about="" typeof="schema:Article doap:Specification">+        <h1 property="schema:name">LinkedDataNotificationsSubscription2021</h1>+        <h2>Editor’s Draft, 2021-12-23</h2>++        <details open="">+          <summary>More details about this document</summary>++          <dl id="document-identifier">+            <dt>This version</dt>+            <dd><a href="https://solid.github.io/notifications/linkeddatanotifications-subscription-2021" rel="owl:sameAs">https://solid.github.io/notifications/linkeddatanotifications-subscription-2021</a></dd>+          </dl>++          <dl id="document-latest-version">+            <dt>Latest version</dt>+            <dd><a href="https://solid.github.io/notifications/linkeddatanotifications-subscription-2021" rel="rel:latest-version">https://solid.github.io/notifications/linkeddatanotifications-subscription-2021</a></dd>+          </dl>++          <div id="authors">+            <dl id="author-name">+              <dt>Editors</dt>+              <dd id="Sarven-Capadisli"><span about="" rel="schema:creator schema:editor"><span about="https://csarven.ca/#i" typeof="schema:Person"><a rel="schema:url" href="https://csarven.ca/"><span about="https://csarven.ca/#i" property="schema:name"><span property="schema:givenName">Sarven</span> <span property="schema:familyName">Capadisli</span></span></a></span></span></dd>+            </dl>+          </div>++          <dl id="document-created">+            <dt>Created</dt>+            <dd><time content="2021-12-23T00:00:00Z" datatype="xsd:dateTime" datetime="2021-12-23T00:00:00Z" property="schema:dateCreated">2021-12-23</time></dd>+          </dl>++          <dl id="document-published">+            <dt>Published</dt>+            <dd><time content="2021-12-23T00:00:00Z" datatype="xsd:dateTime" datetime="2021-12-23T00:00:00Z" property="schema:datePublished">2021-12-23</time></dd>+          </dl>++          <dl id="document-modified">+            <dt>Modified</dt>+            <dd><time content="2021-12-23T00:00:00Z" datatype="xsd:dateTime" datetime="2021-12-23T00:00:00Z" property="schema:dateModified">2021-12-23</time></dd>+          </dl>++          <dl id="document-repository">+            <dt>Repository</dt>+            <dd><a href="https://github.com/solid/notifications" rel="doap:repository">GitHub</a></dd>+            <dd><a href="https://github.com/solid/notifications/issues" rel="doap:bug-database">Issues</a></dd>+          </dl>++          <dl id="document-language">+            <dt>Language</dt>+            <dd><span content="en" lang="" property="dcterms:language" xml:lang="">English</span></dd>+          </dl>++          <dl id="document-license">+            <dt>License</dt>+            <dd><a href="http://purl.org/NET/rdflicense/MIT1.0" rel="schema:license">MIT License</a></dd>+          </dl>++          <dl id="document-status">+            <dt>Document Status</dt>+            <dd prefix="pso: http://purl.org/spar/pso/" rel="pso:holdsStatusInTime" resource="#a23256bd-feda-4af2-a3fb-dfbb2194c377"><span rel="pso:withStatus" resource="http://purl.org/spar/pso/draft" typeof="pso:PublicationStatus">Editor’s Draft</span></dd>+          </dl>++          <dl id="document-in-reply-to">+            <dt>In Reply To</dt>+            <dd><a href="https://solidproject.org/origin" rel="as:inReplyTo">Solid Origin</a></dd>+            <dd><a href="https://solid.github.io/notifications/protocol" rel="as:inReplyTo">Solid Notifications Protocol</a></dd>+            <dd><a href="https://github.com/solid/process/blob/main/notifications-panel-charter.md" rel="as:inReplyTo">Notifications Panel Charter</a></dd>+          </dl>++          <dl id="document-policy">+            <dt>Policy</dt>+            <dd>+              <dl id="document-policy-offer" rel="odrl:hasPolicy" resource="#document-policy-offer" typeof="odrl:Policy">+                <dt>Rule</dt>+                <dd><a about="#document-policy-offer" href="https://www.w3.org/TR/odrl-vocab/#term-Offer" typeof="odrl:Offer">Offer</a></dd>+                <dt>Unique Identifier</dt>+                <dd><a href="https://solid.github.io/notifications/linkeddatanotifications-subscription-2021#document-policy-offer" rel="odrl:uid">https://solid.github.io/notifications/linkeddatanotifications-subscription-2021#document-policy-offer</a></dd>+                <dt>Target</dt>+                <dd><a href="https://solid.github.io/notifications/linkeddatanotifications-subscription-2021" rel="odrl:target">https://solid.github.io/notifications/linkeddatanotifications-subscription-2021</a></dd>+                <dt>Permission</dt>+                <dd>+                  <dl id="document-permission" rel="odrl:permission" resource="#document-permission" typeof="odrl:Permission">+                    <dt>Assigner</dt>+                    <dd><a rel="odrl:assigner" href="https://www.w3.org/community/solid/">W3C Solid Community Group</a></dd>+                    <dt>Action</dt>+                    <dd>+                      <ul rel="odrl:action">+                        <li><a href="https://www.w3.org/TR/odrl-vocab/#term-aggregate" resource="odrl:aggregate">Aggregate</a></li>+                        <li><a href="https://www.w3.org/TR/odrl-vocab/#term-archive" resource="odrl:archive">Archive</a></li>+                        <li><a href="https://www.w3.org/TR/odrl-vocab/#term-concurrentUse" resource="odrl:concurrentUse">Concurrent Use</a></li>+                        <li><a href="https://www.w3.org/TR/odrl-vocab/#term-DerivativeWorks" resource="http://creativecommons.org/ns#DerivativeWorks">Derivative Works</a></li>+                        <li><a href="https://www.w3.org/TR/odrl-vocab/#term-derive" resource="odrl:derive">Derive</a></li>+                        <li><a href="https://www.w3.org/TR/odrl-vocab/#term-digitize" resource="odrl:digitize">Digitize</a></li>+                        <li><a href="https://www.w3.org/TR/odrl-vocab/#term-display" resource="odrl:display">Display</a></li>+                        <li><a href="https://www.w3.org/TR/odrl-vocab/#term-Distribution" resource="http://creativecommons.org/ns#Distribution">Distribution</a></li>+                        <li><a href="https://www.w3.org/TR/odrl-vocab/#term-index" resource="odrl:index">Index</a></li>+                        <li><a href="https://www.w3.org/TR/odrl-vocab/#term-inform" resource="odrl:inform">Inform</a></li>+                        <li><a href="https://www.w3.org/TR/odrl-vocab/#term-install" resource="odrl:install">Install</a></li>+                        <li><a href="https://www.w3.org/TR/odrl-vocab/#term-Notice" resource="http://creativecommons.org/ns#Notice">Notice</a></li>+                        <li><a href="https://www.w3.org/TR/odrl-vocab/#term-present" resource="odrl:present">Present</a></li>+                        <li><a href="https://www.w3.org/TR/odrl-vocab/#term-print" resource="odrl:print">Print</a></li>+                        <li><a href="https://www.w3.org/TR/odrl-vocab/#term-read" resource="odrl:read">Read</a></li>+                        <li><a href="https://www.w3.org/TR/odrl-vocab/#term-reproduce" resource="odrl:reproduce">Reproduce</a></li>+                        <li><a href="https://www.w3.org/TR/odrl-vocab/#term-Reproduction" resource="http://creativecommons.org/ns#Reproduction">Reproduction</a></li>+                        <li><a href="https://www.w3.org/TR/odrl-vocab/#term-stream" resource="odrl:stream">Stream</a></li>+                        <li><a href="https://www.w3.org/TR/odrl-vocab/#term-synchronize" resource="odrl:synchronize">Synchronize</a></li>+                        <li><a href="https://www.w3.org/TR/odrl-vocab/#term-textToSpeech" resource="odrl:textToSpeech">Text-to-speech</a></li>+                        <li><a href="https://www.w3.org/TR/odrl-vocab/#term-transform" resource="odrl:transform">Transform</a></li>+                        <li><a href="https://www.w3.org/TR/odrl-vocab/#term-translate" resource="odrl:translate">Translate</a></li>+                      </ul>+                    </dd>+                  </dl>+                </dd>+              </dl>+            </dd>+          </dl>+        </details>++        <p class="copyright">Copyright © 2021 <a href="http://www.w3.org/community/solid/">W3C Solid Community Group</a>.</p>++        <div datatype="rdf:HTML" id="content" property="schema:description">+          <section id="abstract">+            <h2>Abstract</h2>+            <div datatype="rdf:HTML" property="schema:abstract">+              <p>The <cite><a href="https://solid.github.io/notifications/protocol" rel="cito:discusses">Solid Notifications Protocol</a></cite> defines a set of interaction patterns for agents to establish subscriptions to resources in a <cite><a href="https://solidproject.org/TR/2021/protocol-20211217#storage" rel="cito:discusses">Solid Storage</a></cite>. This specification defines a <em>subscription type</em> to enable the delivery of change notifications about a resource to an <cite><a href="https://www.w3.org/TR/ldn/" rel="cito:discusses">Linked Data Notifications</a></cite> inbox.</p>+            </div>+          </section>++          <section id="sotd" inlist="" rel="schema:hasPart" resource="#sotd">+            <h2 property="schema:name">Status of This Document</h2>+            <div property="schema:description" datatype="rdf:HTML">+              <p>This section describes the status of this document at the time of its publication.</p>++              <p>This document was published by the <a href="https://www.w3.org/community/solid/">Solid Community Group</a> as an <em>Editor’s Draft</em>. The sections that have been incorporated have been reviewed following the <a href="https://github.com/solid/process">Solid process</a>. However, the information in this document is still subject to change. You are invited to <a href="https://github.com/solid/specification/issues">contribute</a> any feedback, comments, or questions you might have.</p>++              <p>Publication as an <em>Editor’s Draft</em> does not imply endorsement by the <abbr title="World Wide Web Consortium">W3C</abbr> Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p>++              <p>This document was produced by a group operating under the <a href="https://www.w3.org/community/about/agreements/cla/">W3C Community Contributor License Agreement (CLA)</a>. A human-readable <a href="https://www.w3.org/community/about/agreements/cla-deed/">summary</a> is available.</p>+            </div>+          </section>++          <nav id="toc">+            <h2 id="table-of-contents">Table of Contents</h2>+            <div>+              <ol class="toc">+                <li class="tocline">+                  <a class="tocxref" href="#abstract">Abstract</a>+                </li>+                <li class="tocline">+                  <a class="tocxref" href="#sotd">Status of This Document</a>+                </li>+                <li class="tocline">+                  <a class="tocxref" href="#introduction"><span class="secno">1</span> <span class="content">Introduction</span></a>+                  <ol>+                    <li><a href="#terminology"><span class="secno">1.2</span> <span class="content">Terminology</span></a></li>+                    <li><a href="#overview"><span class="secno">1.3</span> <span class="content">Overview</span></a></li>+                    <li><a href="#conformance"><span class="secno">1.4</span> <span class="content">Conformance</span></a></li>+                  </ol>+                </li>+                <li class="tocline">+                  <a class="tocxref" href="#subscription-type"><span class="secno">2</span> <span class="content">LinkedDataNotificationsSubscription2021 Type</span></a>+                  <ol>+                    <li class="tocline">+                      <a class="tocxref" href="#linkeddatanotifications-subscription"><span class="secno">2.1</span> Subscription Example</a>+                    </li>+                  </ol>+                </li>+                <li class="tocline">+                  <a class="tocxref" href="#authentication-authorization"><span class="secno">3</span> <span class="content">Authentication and Authorization</span></a>+                </li>+                <li class="tocline">+                  <a class="tocxref" href="#references"><span class="secno"></span> <span class="content">References</span></a>+                  <ol>+                    <li><a href="#normative-references"><span class="secno"></span> <span class="content">Normative References</span></a></li>+                  </ol>+                </li>+              </ol>+            </div>+          </nav>++          <section id="introduction" inlist="" rel="schema:hasPart" resource="#introduction">+            <h2 about="#introduction" property="schema:name" typeof="deo:Introduction">Introduction</h2>+            <div datatype="rdf:HTML" property="schema:description">+              <p><em>This section is non-normative.</em></p>++              <p id="motivation" rel="schema:hasPart" resource="#motivation" typeof="deo:Motivation"><span datatype="rdf:HTML" property="schema:description">The <cite><a href="https://solid.github.io/notifications/protocol">Solid Notifications Protocol</a></cite> describes a general pattern by which agents can be notified when a Solid Resource changes. This specification defines a <em>subscription type</em> to enable the delivery of change notifications about a resource to <cite><a href="https://www.w3.org/TR/ldn/" rel="cito:discusses">Linked Data Notifications</a></cite> inbox.</span></p>++              <p>This specification is for:</p>++              <ul rel="schema:audience">+                <li><a href="http://data.europa.eu/esco/occupation/a7c1d23d-aeca-4bee-9a08-5993ed98b135">Resource server developers</a> who wish to enable clients to listen for updates to particular resources.</li>+                <li><a href="http://data.europa.eu/esco/occupation/c40a2919-48a9-40ea-b506-1f34f693496d">Application developers</a> who wish to implement a client to listen for updates to particular resources.</li>+              </ul>++              <!-- TODO define terminology -->+              <section class="todo" id="terminology" inlist="" rel="schema:hasPart" resource="#terminology" typeof="skos:ConceptScheme">+                <h3 property="schema:name skos:prefLabel">Terminology</h3>+                <div datatype="rdf:HTML" property="schema:description">+                  <p><em>This section is non-normative.</em></p>++                  <p>This document uses terminology from the <cite><a href="https://solid.github.io/notifications/protocol">Solid Notification Protocol</a></cite>, including <q cite="https://solid.github.io/notifications/protocol#notification-subscription-api">subscription API</q>. This document also uses terms from <cite><a href="https://datatracker.ietf.org/doc/html/rfc6749">The OAuth 2.0 Authorization Framework</a></cite> specification, including <q>resource server</q>, <q>authorization server</q>, <q>access token</q>, and <q>client</q>, as well as terms from the <cite><a href="https://www.w3.org/TR/websub/">WebSub</a></cite> specification, including <q cite="https://www.w3.org/TR/websub/#dfn-topic">topic</q>.</p>+                </div>+              </section>++              <section class="todo" id="overview" inlist="" rel="schema:hasPart" resource="#overview">+                <h3 property="schema:name">Overview</h3>+                <div datatype="rdf:HTML" property="schema:description">+                  <p><em>This section is non-normative.</em></p>++                  <p>The following diagram shows the high-level interactions involved in this flow. How a client retrieves an access token for step 5 is outside the scope of this document.</p>++                  <figure id="solid-linkeddatanotifications-flow" rel="schema:hasPart" resource="#solid-linkeddatanotifications-flow">+                    <img src="linkeddatanotifications-subscription-2021-flow.png" height="318" rel="schema:image" width="640" />++                    <figcaption property="schema:name">Solid LinkedDataNotificationsSubscription2021 Flow</figcaption>+                  </figure>+                </div>+              </section>++              <section id="conformance" inlist="" rel="schema:hasPart" resource="#conformance">+                <h3 property="schema:name">Conformance</h3>+                <div datatype="rdf:HTML" property="schema:description">+                  <p>All assertions, diagrams, examples, and notes are non-normative, as are all sections explicitly marked non-normative. Everything else is normative.</p>++                  <p>The key words “MUST” and “SHOULD” are to be interpreted as described in <cite><a href="https://tools.ietf.org/html/bcp14" rel="rdfs:seeAlso">BCP 14</a></cite> [<cite><a class="bibref" href="#bib-rfc2119">RFC2119</a></cite>] [<cite><a class="bibref" href="#bib-rfc8174">RFC8174</a></cite>] when, and only when, they appear in all capitals, as shown here.</p>+                </div>+              </section>+            </div>+          </section>++          <section id="subscription-type" inlist="" rel="schema:hasPart" resource="#subscription-type">+            <h2 property="schema:name">LinkedDataNotificationsSubscription2021 Type</h2>+            <div datatype="rdf:HTML" property="schema:description">+              <p>This specification defines the <code>LinkedDataNotificationsSubscription2021</code> type for use with Solid Notifications subscriptions. The URI of the subscription type is <code>http://www.w3.org/ns/solid/notification#LinkedDataNotificationsSubscription2021</code>.</p>++              <p class="issue">The URI and definition of the subscription type is pending the approval of JSON-LD Context and the Notification vocabulary: <a href="https://github.com/solid/vocab/pull/62/">https://github.com/solid/vocab/pull/62/</a>.</p>++              <p>An <code>LinkedDataNotificationsSubscription2021</code> API MUST conform to the <cite><a href="https://solid.github.io/notifications/protocol#discovery">Solid Notifications Protocol</a></cite> [<cite><a class="bibref" href="#bib-solid-notifications">SOLID-NOTIFICATIONS</a></cite>].</p>++              <p>An <code>LinkedDataNotificationsSubscription2021</code> API SHOULD support the <cite><a href="https://solid.github.io/notifications/protocol#notification-features">Solid Notifications Features</a></cite>.</p>++              <p property="skos:definition">The <code>LinkedDataNotificationsSubscription2021</code> type defines the following properties:</p>++              <span rel="skos:hasTopConcept"><span resource="#linkeddatanotificationssubscription2021-inbox"></span><span resource="#linkeddatanotificationssubscription2021-webid"></span></span>++              <dl>+                <dt about="#linkeddatanotificationssubscription2021-inbox" property="skos:prefLabel" typeof="skos:Concept"><dfn id="linkeddatanotificationssubscription2021-inbox">inbox</dfn></dt>

Just to be aware, and in case it matters, in LDN terms, "target" is the resource that's advertising the inbox, not the inbox itself.

csarven

comment created time in 2 days

PullRequestReviewEvent

PR opened solid/notifications

Add LDN Subscription Type
+485 -0

0 comment

1 changed file

pr created time in 2 days

create barnchsolid/notifications

branch : ldn-document

created branch time in 2 days

issue openedsolid/specification

Include "Success Criteria" (or "Exit Criteria")

Example "Success Criteria": https://github.com/solid/process/blob/main/notifications-panel-charter.md#success-criteria

Or an "Exit Criteria" when typically transitioning from a ~CR to ~PR as per W3C Process, e.g, https://www.w3.org/TR/ldn/#exit-criteria

created time in 3 days

pull request commentsolid/specification

Add server-auxiliary-resources-management server-link-auxiliary-type

I'm not okay to merge both PRs. The "both" that I, and I believe, Ruben is referring to is about mentioning the specific support in each ("both") section.

I'm okay to modify this PR to do that, but if we do that, I suggest mentioning the rel value in each of those requirements i.e., the upcoming #server-web-access-control-management and #server-description-resource-management .

However, if we stick to the current PR, hitting merge right now would be sufficient.

csarven

comment created time in 4 days

push eventsolid/specification

Sarven Capadisli

commit sha 610b60f2564b0940c76d49635cbfdd43a2987ffe

Apply suggestions from code review Co-authored-by: Ruben Verborgh <ruben@verborgh.org>

view details

push time in 4 days

push eventsolid/specification

Sarven Capadisli

commit sha ee780a9c862eb716a4f754748f5c96365411c4cd

Add missing subsections

view details

push time in 4 days

push eventsolid/specification

Sarven Capadisli

commit sha 5814c8e6f54b0762564a611bc6cfde1ebb5a8aef

Minor

view details

push time in 4 days

delete branch solid/notifications-panel

delete branch : notifications-ucr

delete time in 5 days

delete branch solid/notifications-panel

delete branch : meeting-schedule

delete time in 5 days

delete branch solid/notifications-panel

delete branch : meetings/2021-11-11

delete time in 5 days

delete branch solid/notifications-panel

delete branch : meetings/2021-12-16

delete time in 5 days

delete branch solid/notifications-panel

delete branch : meetings/2022-01-13

delete time in 5 days

push eventsolid/notifications-panel

Sarven Capadisli

commit sha 406128828b08655e59c0074bf23ddccbfa9b01c8

Add 2022-01-13 agenda and minutes

view details

Sarven Capadisli

commit sha 42b6dca94a12ff5a8b297bf9b280bb71f49dcdd8

Add CRUD Notifications to agenda

view details

Sarven Capadisli

commit sha 8793f95d66df3bdbe4fed90c9adacabc83552b67

Apply suggestions from code review Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>

view details

Sarven Capadisli

commit sha 8cb76745b7252bc1f23b41dfa6743e5227a8eb9a

Update 2022-01-13 minutes

view details

Sarven Capadisli

commit sha 63b327b3395baf8f3010826a6db45285c47d696c

Merge pull request #42 from solid/meetings/2022-01-13 Add 2022-01-13 agenda and minutes

view details

push time in 5 days

PR merged solid/notifications-panel

Add 2022-01-13 agenda and minutes

Request to merge in 24 hours following meeting.

+188 -0

0 comment

1 changed file

csarven

pr closed time in 5 days

push eventsolid/notifications-panel

Aaron Coburn

commit sha 0a02f344077416d0b012265a5cb0df299fb6e4cb

Adjust meeting schedule to weekly

view details

Sarven Capadisli

commit sha 016d79a5cc3cf8b92ab042ba0b649c202e4ac45f

Merge pull request #43 from solid/meeting-schedule Adjust meeting schedule to weekly

view details

push time in 8 days

PR merged solid/notifications-panel

Adjust meeting schedule to weekly

As discussed in the 2022-01-13 meeting, the Notification Panel will meet weekly.

+1 -1

0 comment

1 changed file

acoburn

pr closed time in 8 days

issue commentsolid/conformance-test-harness

Failed to send authorized request / header parser received no bytes

I don't have a strong opinion on whether to include a test for DAHU or not. Or perhaps more broadly, whether to test RFC 7231 conformance or not. The thing is, if only the requirements listed in the Solid Protocol are tested, it is possible to pass it with flying colours but not necessarily be a conforming HTTP server. The Solid Protocol calls for the RFC requirements, so I think the question is more about whether the respective tests are imported or not.

RubenVerborgh

comment created time in 8 days

issue commentsolid/conformance-test-harness

Failed to send authorized request / header parser received no bytes

As mentioned in Gitter and RFC, for an unrecognised method, 501 would be most appropriate. A server may recognise DAHU, but a Solid server is not expected to recognise it, hence 501 is appropriate. Just because Solid Protocol doesn't call out 501, it doesn't rule out appropriate responses as per RFC.

Even still, a server could respond to DAHU with 405 irrespective to genuinely recognising it or not - there is no sure way to tell. The Solid Protocol grants that possibility. Both 501 and 405 are clear about the issue with respect to the HTTP method.

If devs want to ignore available 501, 405.. and make an argument for 400 / equate with 4xx - all purpose code - then at least make the effort to provide a message in the response body explaining what went wrong.

From the point of testing, 501, 405, and with some cringing, 400 is okay. From the point of a server, I think they should aim for 501, 405, 400 (in that order) - Solid server or not.

RubenVerborgh

comment created time in 8 days

push eventtheRealImy/solidproject.org

Sarven Capadisli

commit sha 2b97700a242bc3b8bfc3efb183d12493cd61b806

Update pages/solid-events.md

view details

push time in 8 days

Pull request review commentsolid/solidproject.org

Solid World aftermath

 Solid Events provide an opportunity to meet others who are working on Solid or a | Date | Event | Organiser | Recordings, Slides and Notes | |----|-------|-------------|------------------------------| |2022-02-10| [Solid World](https://www.eventbrite.co.uk/e/solid-world-2022-tickets-223005725127) | [Solid Team](https://solidproject.org/team) | Register for the event over on [Eventbrite](https://www.eventbrite.co.uk/e/solid-world-2022-tickets-223005725127). Agenda will be announced shortly on Eventbrite. |-|2022-01-13| [Solid World](https://www.eventbrite.co.uk/e/solid-world-2022-tickets-223005725127) | [Solid Team](https://solidproject.org/team) | Presentations: <br/> Sarven Capadisli, W3C Solid Community Group Chair and Solid Editor, presented the recent milestone release of [Solid Protocol Version 0.9](https://solidproject.org/TR/protocol). <br/> Ruben Verborgh, Professor of decentralized Web technology at Ghent University, presented [a vision on access, query and search across the decentralized Web, and the role that Web APIs play therein](https://rubenverborgh.github.io/Web-APIs-for-decentralized-knowledge-graphs/#). <br/> All links from the meetup are shared on [SolidWorld Gitter Chat](https://gitter.im/solid/SolidWorld?at=61e056ca9b470f3897656603) |+|2022-01-13| [Solid World](https://www.eventbrite.co.uk/e/solid-world-2022-tickets-223005725127) | [Solid Team](https://solidproject.org/team) | Presentations: <br/> [Sarven Capadisli](https:/csarven.ca/#i), [W3C Solid Community Group](https://www.w3.org/community/solid/) Chair and Solid Editor, presented the recent milestone release of [Solid Protocol Version 0.9](https://solidproject.org/TR/protocol). <br/> Ruben Verborgh, Professor of decentralized Web technology at Ghent University, presented [a vision on access, query and search across the decentralized Web, and the role that Web APIs play therein](https://rubenverborgh.github.io/Web-APIs-for-decentralized-knowledge-graphs/#). <br/> All links from the meetup are shared on [SolidWorld Gitter Chat](https://gitter.im/solid/SolidWorld?at=61e056ca9b470f3897656603) |
|2022-01-13| [Solid World](https://www.eventbrite.co.uk/e/solid-world-2022-tickets-223005725127) | [Solid Team](https://solidproject.org/team) | Presentations: <br/> [Sarven Capadisli](https://csarven.ca/#i), [W3C Solid Community Group](https://www.w3.org/community/solid/) Chair and Solid Editor, presented the recent milestone release of [Solid Protocol Version 0.9](https://solidproject.org/TR/protocol). <br/> Ruben Verborgh, Professor of decentralized Web technology at Ghent University, presented [a vision on access, query and search across the decentralized Web, and the role that Web APIs play therein](https://rubenverborgh.github.io/Web-APIs-for-decentralized-knowledge-graphs/#). <br/> All links from the meetup are shared on [SolidWorld Gitter Chat](https://gitter.im/solid/SolidWorld?at=61e056ca9b470f3897656603) |
theRealImy

comment created time in 8 days

PullRequestReviewEvent
PullRequestReviewEvent

Pull request review commentsolid/solidproject.org

Solid World aftermath

 Solid Events provide an opportunity to meet others who are working on Solid or a  | Date | Event | Organiser | Recordings, Slides and Notes | |----|-------|-------------|------------------------------|-|2022-01-13| Solid World |[Solid Team](https://solidproject.org/team)| Solid World will be back on 13th January 2022. Stay tuned for the agenda at [Eventbrite](https://www.eventbrite.co.uk/e/solid-world-2022-tickets-223005725127). |+|2022-02-10| [Solid World](https://www.eventbrite.co.uk/e/solid-world-2022-tickets-223005725127) | [Solid Team](https://solidproject.org/team) | Register for the event over on [Eventbrite](https://www.eventbrite.co.uk/e/solid-world-2022-tickets-223005725127). Agenda will be announced shortly on Eventbrite. |+|2022-01-13| [Solid World](https://www.eventbrite.co.uk/e/solid-world-2022-tickets-223005725127) | [Solid Team](https://solidproject.org/team) | Presentations: <br/> Sarven Capadisli, W3C Solid Community Group Chair and Solid Editor, presented the recent milestone release of [Solid Protocol Version 0.9](https://solidproject.org/TR/protocol). <br/> Ruben Verborgh, Professor of decentralized Web technology at Ghent University, presented [a vision on access, query and search across the decentralized Web, and the role that Web APIs play therein](https://rubenverborgh.github.io/Web-APIs-for-decentralized-knowledge-graphs/#). <br/> All links from the meetup are shared on [SolidWorld Gitter Chat](https://gitter.im/solid/SolidWorld?at=61e056ca9b470f3897656603) |
|2022-01-13| [Solid World](https://www.eventbrite.co.uk/e/solid-world-2022-tickets-223005725127) | [Solid Team](https://solidproject.org/team) | Presentations: <br/> [Sarven Capadisli](https:/csarven.ca/#i), [W3C Solid Community Group](https://www.w3.org/community/solid/) Chair and Solid Editor, presented the recent milestone release of [Solid Protocol Version 0.9](https://solidproject.org/TR/protocol). <br/> Ruben Verborgh, Professor of decentralized Web technology at Ghent University, presented [a vision on access, query and search across the decentralized Web, and the role that Web APIs play therein](https://rubenverborgh.github.io/Web-APIs-for-decentralized-knowledge-graphs/#). <br/> All links from the meetup are shared on [SolidWorld Gitter Chat](https://gitter.im/solid/SolidWorld?at=61e056ca9b470f3897656603) |
theRealImy

comment created time in 8 days

more