Tim Berners-Lee

This issue is invalid as it is nonsense as phrased. The Solid spec does not CHANGE the http spec at all. It refers to it and calls out a small...

Specifically the point made at https://github.com/solid/specification/issues/70#issuecomment-547924171 (Thanks @csarven )

It does? It should not.

You don't just switch from one form to another. You always have to have both for a while. Severs in the server-interim must provide both, and clients during the client-interim...

The `updateMany` function in rdflib https://github.com/linkeddata/rdflib.js/blob/main/src/update-manager.ts#L685 is what we suggest developers call when the change updates more than one resource. It currently iterates over the resources needed to be changed,...

See Road map item "Atomic multi-file updates" https://solidproject.solidcommunity.net/Roadmap/state.ttl#Iss1595438497668 The "To Be Done" state means we had decided it was a good thing to do though it is not scheduled.

Every spec needs a version number. So that comparability future versions can be tracked. Whatever the maturity of the document. Yes it could have been a separate Pr. But I...

@RubenVerborgh - I agree. "I think that, if we make such deviations, they should be made explicit". What do you suggest is the best way? We could flag it in...

The publication of the URI of the owner of the pod is needed to prevent a kludge where the current home page code just guesses it! It was felt so...

The architecture of the web is that you read write documents, not people. Typically we use the `#` to separate the URI of the document from the identifier of the...