Sarven Capadisli

Note https://github.com/solid/specification/issues/44#issuecomment-648048614 proposing how the constraints can be named and defined in the Solid spec.

Putting aside security consideration / discussion here.. there is discussion/PR in solid/specification on this already. Also reminder: https://github.com/solid/vocab --- Note LDP BP: * https://www.w3.org/TR/ldp-bp/#prefer-standard-datatypes * https://www.w3.org/TR/ldp-bp/#re-use-established-linked-data-vocabularies-instead-of-re--inventing-duplicates > . > ....

Related https://github.com/solid/specification/issues/119

I may have previously shared https://ethical.net/resources/?resource-category=web-hosting somewhere.. I use Infomaniak (CH based) for some of my personal sites. See their "actions for sustainable, responsible growth": https://www.infomaniak.com/en/green-hosting . I don't know...

https://github.com/solid/specification/issues/28 goes in the direction of addressing the need generally for Solid, and not coupled with an authorization mechanism.

I ran into the issue of flipping between schemorg's http/https in my application. Sticked with http in the end. It is not something we can address in our specs -...

If the rough rough rough consensus here is that an ACL need not have its ACL, then the proposal at https://github.com/solid/specification/issues/184 would prevent servers from advertising a link relation.

When a contained resource is deleted, the server MUST also delete the associated ACL. Multiple accessTos would mean that an ACL's lifecycle can depend on multiple resources - especially in...

>It has no way other than the published wACLs to know how to authenticate to a given resource. I'm not sure I understand how an ACL (which are only discoverable...

https://github.com/solid/authorization-and-access-control-panel/issues/55