Kjetil Kjernsmo

The formal specification for merging RDF graphs are here: https://www.w3.org/TR/rdf-mt/#graphdefs I think that should be the basis of this feature, if it is implemented. E.g. `INSERT DATA` is specified in...

Yeah, I've been trying to ask around for use cases that can distinguish HTTP/2+SSE vs WebSockets, but there hasn't been anything very clear so far.

I admit to like WebID-TLS, and I am hoping it can stay, and I see it as a simpler alternative for IoT devices that need to send data to Pods....

It is pretty implementation specific but, I think it is an issue that more implementers will encounter. The issue is really this: The client asks for e.g. `/foo/` and the...

> For example, /foo/ is the main resource, with /foo/index.html or /foo/index.ttl are representations; ACL should be set on /foo/, but also cover representations. However, in this spec, no assumptions...

We should also keep in mind the general architectural principle of [orthogonal specifications](https://www.w3.org/TR/webarch/#orthogonal-specs). That is to say, there is not _one_ Solid spec, but a group of orthogonal specifications making...

> While it is tempting as engineers to think of a spec as a bunch of interchangeable and modular pieces, this can lead to problems with interoperability in the absence...

> I actually think there is a resolution now: Right. > * There is the v0.8 draft spec (this repo) > > * There is the Solid specification repository with...

Hmmmm, not quite sure about what this would entail in terms of the spec, as we have group listings, and to me, it seems like each of these are group...

> In general IRIs should be considered as opaque identifiers. Certainly! But it is a contribution towards the aesthetics of the system, so I think it is a nice feature...