Beaker browser community ask questions about how independent developers can introduce changes to data structures without breaking each other's things. The discussion touches on issues that will be familiar, and overly complicated, to wiki developers. github 
_(@neuroplastic diverts from the specific proposals into interesting territory. see this comment )_
@yoshuawuyts, @pfrazee and @taravancil are making a push right now against the UX barrier that has kept the original vision of the ReadWriteWeb (and the semantic web) from succeeding. In your, @dominictarr's, et alia's work, we see a modular approach to handling HTML from within node.js javascript. As e.g. @jondashkyle demonstrates, this can be a simpler UX than direct HTML wrangling.
_(re: @dominictar, et alia's work: see hyperscript github )_
@pfrazee is identifying JSON-LD as a blocker for usability of the p2p RWW. But JSON-LD is a critical piece of the puzzle to enable scientific and general data integration in an open web. This issue is an argument that can potentially make or break JSON-LD, and hence, SOLID. We can't let LD go, not when @timbl is this close with SOLID. (If it helps, young hurried devs, think of the LD as JSON-Leibniz&Diderot).
The elements in JSON-LD @pfrazee is calling attention to - @context and type - are so epistemically freighted, no wonder there's been no usable solution, hence the tenson in this issue's thread. The web needs a breakthrough here, and it needs it now.
@msporny, @kevinmarks, @timbl, @csarven, @RubenVerborgh: are you ready to agree there is no declarative solution to the usability problem of RDF formats?
If so, then the solution must be that an application is already a set of contexts and types. The same JSON must be ingestible by different apps able to apply different LD contexts and types. This is where i see @pfrazee leading, but, critically, IndieWeb and SOLID are stuck in the old app paradigm. For SOLID and the RWW to work, JSON-LD needs new imperative/functional tooling, and the radical simplection happening in choo, dat, and e.g. hyperscript is the place.
@yoshuawuyts, can we rebuild SOLID using choo, Dat, and Beaker?