The reason for posting is that Slimcoin's RDF backing positions it very well as a host for for Ricardian contracts, assuming that i) they work in practice and ii) there's any interest in using them.)
Cheers
Graham
As far as I understand (probably wrong) the RDF backend is derived from blockchain data. Ricardian contracts (or any smart contracts) can be parseable in RDF, but they must be
enforced first at the blockchain level. OP_RETURN is not suitable for that, IMHO, or it may be only if we follow the same design pattern: store the URL of a certain document, and the document itself in another storage (an RDF instance, in our case) but a smart contract also has parameters. OP_RETURN
seems to be too small for this type of project. I've been diving into various small Turing complete machines (even gotten into one called BrainFuck, which only uses 8 symbols to describe a full Turing complete machine:
>,<,+,-,[,],comma.point
but couldn't find one shorter than 80 bytes (which is the OP_RETURN size (usually it's 40 bytes, if I'm not wrong).
I'd be interested to know more of your thoughts about this...