Sarven Capadisli

>No matter what language(s) we choose, someone will feel alienation or disinclusion, because we can't use every language at once. That's not at all the point. Pick random names from...

https://github.com/w3c/idcg/issues/17#issuecomment-993679054

Noting here that LDN is also used in ActivityPub's server-to-server interactions: https://www.w3.org/TR/activitypub/#server-to-server-interactions . Besides an AP server having some similarities to an LDP server ie. counting as potential implementation experiences,...

I agree that this issue wouldn't quite make it into milestone 1 (~FPWD). I've bumped it down for later. If all dependencies in the earlier milestones are addressed, we can...

@dmitrizagidulin >I personally think that it's crucial that we address items 1 through 3 for the 1.0 spec. If any issue pertaining to items 1-3 are not logged, can you...

There is a bit more comprehensive list of resource types documented here: https://github.com/solid/specification/issues/191 . I suggest using that as basis/input for the categorisation.

The resolution of the dimensions can vary. What I wrote in https://github.com/solid/specification/issues/270#issuecomment-868013522 is fairly flat and I think gives more precision on the characteristics of auxiliary resources. And, then there...

>However, it does not specify what should happen for auxiliary resources, in particular for ACL resources. Auxiliary resources are ... resources. >Should auxiliary resources have a WAC-Allow header? I'd say...

Good issue. >Shall we list that explicitly in the spec though? I agree, it'd be worthwhile. Thinking: If Control is allowed on resource, then ACL resource's WAC-Allow should include `user="read...

I can't recall a prior discussion specifically about associating an inbox to a resource through Link header in a request but do recall wanting it to for any link relation...