Sarven Capadisli

Re #server-options-asterisk-accept-headers : >Servers MAY include the HTTP Accept-Patch, Accept-Post and Accept-Put headers in the response of a OPTIONS * request. As noted, not all servers would be configured to...

There is "When responding to authorized requests:" before the requirement on `OPTIONS *` and that was intended to exclude the CORS pre-flight case. Is that alright? Can we then put...

We've been through this material and discussion several times. I've been content to assume that Ted is sharing knowledge of LDP in good faith for some time now. Unless the...

I'd suspect the WG captured some of the background in the mailing list, meeting minutes or the W3C issue tracker. I suppose we weren't compelled enough to dig into that...

IANAL. The intention with this license document (`mit-license`) is so that there is a human/machine-readable version that can potentially be reused/attached to TRs. The copyright year makes things a bit...

Good discussion. We can introduce CG's WebID once it exists. Possibly a new group under https://solidproject.solidcommunity.net/Solid%20Project%20Contacts/Group/ or somewhere else (more?) persistent. At the moment, we have this URL: https://www.w3.org/groups/cg/solid -...

Some thoughts: I like the 404 here. Would it be useful to make sure that the 404 response MUST be accompanied with an expiration time for caches? If so, related...

@dmitrizagidulin Isn't a given that the requesting agent can come forward with credentials on any resource? If I'm interpreting correctly, I think signalling allowRequestPermission along with a 404 works contrary...

I would only ask how much would the 404 approach will cause the applications lose out on considering the option to authenticate (if not already) and re-request. So, re 404,...

Punting the responsibility/decision making to the "outermost layer of the architecture" certainly sounds reasonable, *if and only if*, there is an "outermost layer" to speak of. Certainly we expect a...