Sarven Capadisli

[1] Whether and how the server should process that particular payload is unspecified. Hence, servers are neither required to accept the request; to further create new resources based on the...

I don't think WAC-Allow addresses what I had in mind about immutable resources, but correct me if I have missed. There may exist an agent that's can't alter a resource...

Thanks all! I observe no objections. I suggest that we accept this proposal until there is a general decision to update the parameters of the weekly meeting. The following is...

Closing issue as commenter satisfied - original proposal withdrawn in favour of 0.10: https://github.com/solid/specification/issues/461#issuecomment-1287502961

Aren't the sparql, qpf etc interfaces about the storage and so should instead be part of storage's description?

It may not be appropriate to interpret those interfaces as another (type of a) storage. My understanding was that they are alternative (or additional) endpoints, services, communication options offered by...

Yes, along those lines. Perhaps the property is specialised for the interface so that clients can easily follow-their-nose. I think `pim:Storage` is conceptually not equivalent to `void:Dataset`, `sd:Service`, `dcat:Catalog`, and...

>Solid flavored LDP I don't believe that association is accurate and find it to be potentially misleading. The Solid Protocol and LDP are compatible in some aspects, however neither are...

This issue is a duplicate of https://github.com/nodeSolidServer/node-solid-server/issues/1465 with the main difference being the HTTP method. Servers are expected to support PATCH to create resources (including containers and non-containers). See also...

`LOAD `