+1 to the idea of using blocks to express Semantic Web data.
Blocks are powerful for that they can hold both human-friendly text and computer-friendly props,
allowing both humans and computers to reason on them.
And we want that computer assistance.
Semantic Web is a great idea and fits perfectly with the design of blocks, as they resemble a direct labeled graph by referencing other blocks, just like Semantic Web’s model.
I like the metaphor of distributed wiki.
I believe one important trait of such wiki is immutability,
as we scale to the size of the Web we better to not have link rot in the design.
Likily, it’s possible to have an immutable Semantic Web graph by using content-hashes to identify blocks. That way we have an immutable direct acyclic graph, and it’s possible to host it on top of content-addressable storages, such as IPFS, GNUnet, or use a CDN, Matrix, Solid, or all at once - the more the merrier.
Due to blocks being content-addressed we can get ‘trust’ ouf of equation - we care little where data for a content-hash is coming from, because we can verify that it’s exactly what we asked by comparing hashes.
Same applies for ways to distribute data, we can use any number of protocols we like - it can be p2p, via ActivityPub, RSS, Solid, IPFS, OrbitDB, Matrix - you name it.=)