It's easy for schemes of this sort to become fragile constructs. Moreover, the primary motivation for such an approach is copyright management - IE, fighting the "information wants to be free" tendency.
In the Objectory tool you could e.g. use it to re-use definitions along a specification. You could add a translucent link and show the text wherever needed without creating redundancy.
I tried in for a little product review I did of a friends app. Once I was done I found out there is no good way to export any of it to anything readable...
My choices where broken markdown or css-hacks for clean screenshots.
Markdown would be ok if it would translate well, it's made to be rendered as HTML after all.
A new line in markdown however is not the same as a new line in roam, but in the export it is treated like it is. If you render the exported markdown as html you will have a lot of paragraphs broken (and maybe lists too, don't quite remember).
edit: look: roam | markdown | html https://i.imgur.com/2WGJGsY.png