Sarven Capadisli

I ran into that as well. My take on it was that including ETag in the response of a PUT ensures that the ETag value corresponds to the representation data...

There is `https://dokie.li/ a doap:Project`. (Aside: It should probably be `https://dokie.li/#project a doap:Project` instead.) I'm approaching this with an interest to use `prov:wasGeneratedBy`/`as:generator` where it points at either the "project"...

I think this issue should be rephrased to potential relationships between the concepts, and not necessarily a *particular* "mapping". Understanding and clarifying the intentions and boundaries of what's here is...

I suggest that there is a consideration to reusing the [Solid CoC](https://github.com/solid/process/blob/main/code-of-conduct.md) but with its own Committee, thereby overriding the Enforcement section of the Solid CoC. In case it matters,...

@domenic re https://github.com/bryanmcquade/scroll-to-css-selector/issues/5#issuecomment-391489271 , I'm genuinely curious: when you say browsers, are you referring to a specific / identifiable list or any? What constitutes a significant browser implementation? Can it...

To be clear, the Solid Notifications Protocol is not claiming the entirety of Description Resource. It is merely describing the data model that's used as part of a Description Resource...

https://solidproject.org/TR/2022/protocol-20221231#server-storage-description Aside: Interesting that CSS is still using the unregistered scheme `.well-known/solid`. Moreover, it is supposed to be used at the beginning of the URI path, so `/joachimvh/.well-known/solid` is a...

Right. I've realised that storage description resource and the description resource of the storage resource could be different but practically can be the same resource when I implemented 1) the...

I should add that the intention of storageDescription was/is to refer to "storage description of a storage in which this resource is in" (as mentioned in the comments). Practically speaking...

Related: as an interim solution, should the NSS repo state that it reflects solid-spec (as opposed to solid/specification) .. and that the current solid/test-suite may give different results?