Matthieu Fesselier

Yes indeed, I think it's OK now

The existing properties are favored only over our default which is defined by ` '@vocab': 'http://happy-dev.fr/owl/#'` For the properties we define explicitely, it works fine

Interested in this too! I'm not sure, but token renewal is here where there is no token on the client and we need to get a new one from the...

What you mean is this is supposed to work: `solid.data.resolve('user.bestfriend.name')` But not this? `solid.data.user.resolve('bestfriend.name')` We built our wrapper around this idea: ``` javascript const resource = solid.data['someURI'] const value =...

When I inspect the network requests, as all the resources are in the 1rst graph, only one request to `https://apiprod.happy-dev.fr/clients/` is made

I don't know if it helps but here are some observations: ```javascript await solid.data.context.extend(base_context) const resource = solid.data["https://apiprod.happy-dev.fr/clients/1/"]; console.time(); await resource.name; console.timeEnd(); // first call, need to request server: ~150-200ms...

I am testing in a browser (Chrome 78). Without extending our context, with this code: ```javascript const container = solid.data["https://apiprod.happy-dev.fr/clients/"]; console.time(container.toString()) for await (const r of container.ldp_contains) { console.time(r.toString()) await...

Great thanks! Any idea on how to reduce URLs on the meantime? Should we use the JSON-LD library?

Thanks! When I get the `type` of this container: `https://api.happy-dev.fr/collectives/` I get the expanded field `http://www.w3.org/ns/ldp#Container`, but I expected `ldp:Container`. Is it the same problem here?

Ok, you mean that the NamedNode URIs are never compacted with the current context?