Andrei
Andrei
It will be the client's responsibility -- i.e. whichever app the user goes through to browse and manage their social graph.
1. Sure, if we ever find the time to implement it, or if someone wants to submit a PR to our servers. But I don't think we'll mandate it for...
1) I agree, SSE looks pretty sweet. 2) I doubt it will ever serialize to JSON-LD.
Globbing is just a pattern matching feature of Unix-like systems. It does not return a tar.gz file, or any type of archive. I've added a couple of examples to show...
Globbing only applies to RDF resources (now properly reflected in the spec text).
@sandhawke it is actually called _glob_: https://en.wikipedia.org/wiki/Glob_(programming)
@bblfish multipart results is a reasonable improvement over the current way of doing globbing. I'll try to implement it to see how well (easy) it is to work with.
Yes, it would be the client's job to handle these operations.
Yes, this is a non-standard improvement to PUT that we could propose as an extension to LDP. It is currently described (specced) in this doc so that people writing apps...
I see your point. I think we can address it in LDP Next, where we plan to have a way for servers to advertise what they support.