Ruben Verborgh

+1 for the above as a third option. Regarding security, agreed; this is what we started to convey in https://github.com/solid/specification/pull/13/files#diff-8d72b2ee1631b8eec737030e9b4a3c9cR37-R38 and https://github.com/solid/specification/pull/13/files#diff-8d72b2ee1631b8eec737030e9b4a3c9cR59-R60; we probably want to add more details.

None. Not all conversations are panel-bound.

(Quickly rebased this one to trigger CI.)

@sebilasse Note that it is not "closed closed" as in the sense that we wouldn't want to tackle this. Rather, it is tagged "revisit", which means that it is something...

I think we will not be able to implement that until #661 and #662 are incorporated (which we need for proper conneg) and they are unfortunately a lot of work.

Caveat here is that the current server does not support such a modular design. So without significant work on the server, building this as part of NSS or as an...

Hmm, the assumption is that the library takes a valid RDF Term in the [(old) N3.js representation](https://github.com/rdfjs/N3.js/tree/v0.11.3#triple-representation). No validation is performed, so the behavior of invalid terms is undefined. If...

Interesting work. However, I believe there are still some cases that are not covered. For example: ``` *half*-italic # Title 1 *half-*italic # Title 2 ``` The second title does...

Since the solutions in this thread involved a lot of keypresses, I started the [Vim Markup Assistant](https://github.com/RubenVerborgh/vim-markup-assistant) plugin, which toggles single words in Markdown to italic or bold. Thereby, I...

> i am wondering why you're just mentioning structural constraints? Because structural constraints are not necessarily “additional semantics”. I.e., we could imagine creating a profile that imposes certain structural constraints...