Solid compliance

PATCH /alice HTTP/1.1
Host: mypod.store
Content-Type: application/sparql-update

PREFIX as: <https://www.w3.org/ns/activitystreams#>
INSERT DATA { <https://mypod.store/alice> as:preferredUsername "Alice" . };
DELETE DATA { <https://mypod.store/alice> as:preferredUsername "ALICE" . };

PATCH /alice/data/events HTTP/1.1
Host: mypod.store
Content-Type: application/sparql-update

PREFIX ldp: <http://www.w3.org/ns/ldp#>
INSERT DATA { <http://mypod.store/alice/data/events> ldp:contains <http://url/of/resource/to/attach>. };
DELETE DATA { <http://mypod.store/alice/data/events> ldp:contains <http://url/of/resource/to/detach>. };

{
	"@context": "https://activitypods.org/context.json",
	"id": "https://mypod.store/alice",
	"type": ["foaf:Person", "Person"],
	"dc:created": "2023-01-13T11:42:45.636Z",
	"dc:modified": "2023-01-13T11:42:48.389Z",
	"foaf:nick": "alice",
	"preferredUsername": "alice",
	"inbox": "https://mypod.store/alice/inbox",
	"outbox": "https://mypod.store/alice/outbox",
	"followers": "https://mypod.store/alice/followers",
	"following": "https://mypod.store/alice/following",
	"liked": "https://mypod.store/alice/liked",
	"publicKey": {
		"owner": "https://mypod.store/alice",
		"publicKeyPem": "-----BEGIN PUBLIC KEY-----\nMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAzlq6avqA4nwxGDqXMijZ\nixRIllyIDkF4rc9KxUHizysOJEBx9+WSfom0wlS1hPr+Qn90eb8h/8wjbvfXdjYm\npdusaTOrRMFEEMX4lquAPcgLxZKzQNAy8zUw/oBpnrep52Hmx7VfYFfCpAP7OxAL\nsA4mdKq1tx2e0g9so+5WeAa3yiKCvqkE6QJQXgk+WQ998aQg133HOUOqa1JKaU0k\nJK6fVYnJ74L7b6OWQDbehu0SBlAAypOJzkO4WysKOGiUCrrcgol2LmTImzCoTZS3\nPUUV0Rh2iI3v5t07vUfr5o415Em5YFwoPRhq3WH6hmP7wd9ducaFNl9Q/XyYQmPK\nG1F3RQNwtSy6aeAUajw6HTWd+FlFA6oA9LLaVxCoTxlejLB8IrYo3y2PGxPAXNl3\nqodsXWk/I/Jm/nus+RLVGCoJLl+i+zzEF0WG20+rfb0cNPjzuzgWuYY2PTBu78Ib\nizaXLv23fPLmxxUwHQgcCc4RgbmBAwhLWTsGETRLbDSWwBZnkv6PnMVlyrzs47jf\nr+vFYIxdiz8VvJe+sQ7hSrkzVjCluKIXhWT3bPtOkq4fepTnZmGi3qXRCg5cacd8\ni+KLaGtsHIsNyGOGfi55S5ZiSMo7kbeUxfM6xFjfhWuj3jDmMYfYQgBSmP2CNcEU\nTWmx7zJiaO3Me1q3sFG8Ti0CAwEAAQ==\n-----END PUBLIC KEY-----\n"
	},
	"endpoints": {
		"void:sparqlEndpoint": "https://mypod.store/alice/sparql",
		"proxyUrl": "https://mypod.store/alice/proxy"
	},
	"url": "https://mypod.store/alice/data/profiles/63c143b75ea9720d1b484a39"
}

• Applications declare their needs through AccessNeedGroups and AccessNeeds, which are displayed on an authorization screen.

• Before registration, AccessGrants and DataGrants are created on the user’s Pod.

• The ApplicationRegistration resource is created on the user’s Pod and sent to the application through a Create activity.

• If the ApplicationRegistration is correct, it is saved on the application instance, as well as the corresponding grants. It returns an Accept activity.

• Whenever the user connects again to the application, we check that the AccessNeeds haven’t changed. If needed, we show an authorization screen again and ApplicationRegistration is updated (with a Update activity).

• If the user wants to uninstall the application, we delete the ApplicationRegistration (and corresponding grants) and send a Delete activity to the application.

• Authorization flow is handled using ActivityPub. The application is an ActivityPub actor.

• We only handle registration with Applications, not with other SocialAgents (we continue to use WAC permissions for the latter)

• Pods don’t declare an AuthorizationAgent. It is handled internally.

• Pods don’t declare a DataRegistry. This registry is only used to list ShapeTrees. TypeIndex can be used instead.

• Applications don’t declare AccessDescription for the time being (we can deduce the accesses requested, and later it may be used to justify access to certain resources).

• Pods only create AccessGrants and DataGrants, not AccessAuthorizations and DataAuthorizations. Grants can be shared with the registered application, while Authorizations cannot. The only difference between them is a grantedWith predicate in AccessAuthorizations that indicates which app was used to manage authorizations (but we manage that internally anyway).

• Pods don’t declare RegistrySet, ApplicationRegistry, AuthorizationRegistry as they are not visible from the outside. We just read ApplicationRegistrations, AccessGrants and DataGrants in their dedicated containers.

To subscribe to the http://localhost:3000/foo resource using WebSockets, you use an authenticated POST request to send the following JSON-LD document to the server, at http://localhost:3000/.notifications/WebhookChannel2023/:

{
  "@context": [ "https://www.w3.org/ns/solid/notification/v1" ],
  "type": "http://www.w3.org/ns/solid/notifications#WebhookChannel2023",
  "topic": "http://localhost:3000/foo",
  "sendTo": "https://example.com/webhook"
}

The sendTo predicate is the Webhook URL of your server, the URL to which you want the notifications to be sent.

Just like the Community Solid Server, we support five different notification types that the client can receive. The format of the notification can slightly change depending on the type.

• Create: When the resource is created.
• Update: When the existing resource is changed.
• Delete: When the resource is deleted. Does not have a state field.

Additionally, when listening to a LDP container or an ActivityStreams collection, there are two extra notifications that are sent out when the contents of the container or collection change. For these notifications, the object field references the resource that was added or removed, while the new target field references the container or collection itself.

• Add: When a new resource is added to the container or collection.
• Remove: When a resource is removed from the container or collection.