Sarven Capadisli

I think the constructor (what it used to be) is not working as it used to. Suspicious of commit https://github.com/linkeddata/rdflib.js/commit/236d6db6a71482d51368a23766eaf1a17d96f287 . At the moment, removeHash needs to use options.base (instead...

I can't comment on the fetcher just yet. The issue was introduced as part of a set of conversion change to use require(). @dmitrizagidulin As requested, sample RDFa: https://dokie.li/ ,...

Just to add more fun to the mix - this brings back old nightmares: There is an issue with base URI setting in Green Turtle when there is a request...

If it is about brute merging, then don't, because we don't entirely know what it will break further or fix - maybe not even an issue anymore? There may be...

I'd say that the https://solidproject.org/ED/protocol#server-accept-headers requirement (intended to) covers 404 responses. "Authorized" typically entailing something other than 403.

>So it seems to be spec conformal to omit the Allow header and in consequence the Accept-* headers in unsuccessful responses. I don't think that's correct or accurate. >How can...

>Are you refering to the spec or to my statement? :) Your statement but I may have misinterpreted. I think 404 is most interesting here (e.g., in response to HEAD...

Sharing this comment from @emmettownsend : >I suspect most of the auxiliary resources will need to be cached as they will be used at runtime by the server to make...

Moving this to WAC repo. There are some related considerations about Groups in https://github.com/solid/web-access-control-spec/blob/main/README-v0.5.0.md#group-listings---authentication-of-external-requests that can be taken up at the same time.

Noting that the current WAC Editor's Draft allows servers to associate resources and ACL resources, and they can be on different origins. See #web-origin-authorization #uri-origin .