Sarven Capadisli

1. Namespace is not the point. The first paragraph (and even the first sentence) dives into describing providers/issuers. This is a good place to tie the notion to `http://www.w3.org/ns/solid/terms#oidcIssuer` which...

If knowledge of SPARQL is required to understand the Solid-OIDC spec, see https://github.com/solid/solid-oidc/issues/23

I think a part of this issue is covered by specifying/clarifying conformance classes - in issue https://github.com/solid/solid-oidc/issues/20 .

Example blocks have leading text/heading using the text "Example", Notes tend to use "Note". At the very least prepend the text "Issue" before the description so that the context is...

@balessan eg. https://www.w3.org/TR/ldn/#conformance-classes states: >LDN implementations may be senders, receivers or consumers. The conformance criteria for each of these roles are described in their respective sections of this specification. and...

Some differences as I understand it: * There is no registration * Notifications can come from anyone * Notification payload contains all there is needed to know * Notifications are...

What's coded in the validator is the https use of AS2 ns (mentioned in the /cloud document). The payload you used had http. I guess we can relax that condition...

`MUST` include: ```turtle # No need to declare the URI of the notification. a as:Announce ; # A valid xsd:dateTime. as:updated "2017-09-05T21:11:58.611Z"^^xsd:dateTime ; # CC0 license must be declared here....

To take one step back, part of this data shape depends on what should be provided by the sender, and if at all, what should be modified by the receiver....

This is essentially about enabling our tools to help us make informed decisions. Welcome to use a term that's more suitable than "preferred". >Can the DPV express separate policies for...