Sarven Capadisli

https://www.w3.org/TR/sparql11-update/#updateLanguage >If multiple operations are present in a single request, then a result of failure from any operation MUST abort the sequence of operations, causing the subsequent operations to be...

Naming things is hard. I prefer them short while aiming to be consistent / "automatically" constructable given input. So, the initial proposal is a bit inconsistent in that regard with...

I gave a bit more detail in https://github.com/solid/specification/issues/379#issuecomment-1078876775 that covers some of your questions/feedback. I'll follow up with a PR clarifying further. Thanks for the feedback! >One first takeaway is...

https://tools.ietf.org/html/rfc8941

No, I want to clarify protocol's position and checking to make sure there no oversights or misunderstandings of the specs. As things stand, a successful response to create and update...

The Protocol doesn't (re)define "server" because it builds on HTTP server (as per 7230, 7231).

In the PR thread: >This is really about when a server supports multiple storages with different owners under the same host. >The key word that I used was "host" but...

All, great issue and feedback. * The motivation and applicability of RFC3987 is clear. * The INTERNATIONAL-SPECS includes recommendations for resources identifiers, identifiers in documents, and (potential) visibility of identifiers...

The delegation precondition is analogous to https://solidproject.org/TR/protocol#storage-owner-uri-ownership : >[Solid Protocol] does not describe the relationship between a Solid storage "owner" and Web architecture’s URI ownership. Solid Protocol should not describe...

This issue is intended to remove assumptions about the availability of a Solid server responding to certain requests. Comments in the issue #355 for example considers the possibilities like OPTIONS...