Henry Story

> These semantics are not incompatible; it is perfectly possible to have a 'ClientWebID': "a HTTP URI that is globally unique, that is bound to one Entity, which refers to...

> With regards to the logical notation, I don't think that you can put it that way, at least not in RDF: the identifier () stands for the Entity it...

> I think it's important that Solid enables (parts of) pods to be hosted on static file servers, which usually don't have the ability to perform content negotiation, Solid is...

It would be interesting to know how things look on different operating systems. Some support attributes on files. Is there an OS which supports attributes where Apps consistently consult those?...

I think @timbl's answer here is a helpful one, especially as it helps avoid problems with `.exe` attacks on Windows. URI on the web Content type Filename on the system...

@leobard I think one may be able to avoid 3 namespaces and have just one ```https://myserver.com/bob/documents/projects/bar/foo.html``` First note that a Solid server should just be a normal HTTP server. So...

Solid already provides a way of viewing and editing one resource using one URL, since it is using LDP. That simplifies a lot of state-management all over the place. The...

One problem I see reading @RubenVerborgh's [resource-mapper.js](https://github.com/solid/node-solid-server/blob/1afe2f45104a87606007fe97ac443462065cc953/lib/resource-mapper.js#L137) is that it does not deal with content negotiation. This is well explained by @leobard's [Cool URIs for the Semantic Web](https://www.w3.org/TR/cooluris/). If I...

This thread started with an emphasis on authorization of software agents that may run on the user's POD, fetching data on his behalf or posting notification messages. Those agents may...

I find your scenario difficult to understand, as I don't know what perform chart, yoyodyne or acme do. Does the following attempt at a more realistic scenario that everyone can...