Dmitri Zagidulin

What's the use case (necessity) for this? :)

@jeff-zucker > I would like to put in a word for mime-type support. +1, I think that mime-type would be incredibly useful. (So, specifically, containment + mime-type being the minimum...

+1 to not tackling this yet. Nowhere near ready to standardize.

Interoperability is for a different issue. (In general, interop is a much broader issue, and is an overall aim of our project.) Portability specifically means that "the user can take...

Saying it's optional recognizes the fact that maintaining 301 redirects by the old server, when the user is no longer a paying customer and has moved on, is a _policy...

> If you want to guarantee portability, dont use the web. From what I understand, one of the _core goals_ of both Solid and the Crosscloud Project is to _enable_...

Related issues: * [solid/70 - notifications api](https://github.com/solid/solid/issues/70) * [solid-spec/11 - PubSub](https://github.com/solid/solid-spec/issues/11) * [solid-spec/53 - semantic pingback/webmention](https://github.com/solid/solid-spec/issues/53) * [solid-spec/46 - Live Updates and Push](https://github.com/solid/solid-spec/issues/46)

We'd need to spec several pre-requisites to make this happen. (And I'm happy to break these out into individual issues, where appropriate, if people agree on the general list.) Most,...

Just to be clear, though, that while I agree with @RubenVerborgh that we may not have time to address all dependencies 1-6, in time for the a 1.0 spec, I...

Great point. (I would add the `/proxy` endpoint to that list.)