a16z-contracts
a16z-contracts copied to clipboard
a16z
ProseObject versions of the License PDFs
Suggest that a plain text version of the License PDFs would permit much better use of this great work. Those could be in normal markdown, but suggest advantage in using a "source" format that allows composability - ProseObjects.
These licenses can be seen at http://www.commonaccord.org/i.php?v=l&f=G/a16z-contracts/licenses/pr0b/ That site is driven by Heroku from a repo at https://github.com/CommonAccord/Cmacc-Org/tree/master/Doc/G/a16z-contracts.
(Updated the URL, shortening it.)
This is extremely practical and we may look to use something like this for our use case/ dApp
Hey @HazardJ - we'd love to include this. Can you move the SEC and pr0b folders into the new licenses folder in the github? Additionally, please resolve any merge conflicts.
After that, would be more than happy to merge. Thank you!
Superb! Yes, I'll move the ProseObjects into /licenses/PrOb/ (or /licenses/prob/ if you prefer), will test and then update the pull-request.
@fmhall - I picked up on your suggestion and put the ProseObject versions into /licenses/pr0b/. (Used your suggestion of the folder name, too. With zero instead of oh. Compact and searchable.)
I think this should be ready to go, no conflicts.
Presented here http://www.commonaccord.org/index.php?action=list&file=G/a16z-contracts/licenses/pr0b/
(using Heroku drawing from www.GitHub.com/Cmacc-Org/)
@HazardJ If you prefer to use "o" instead of 0, that works too! Not sure why I said 0 in the first place tbh. I'll merge later either way!
@fmhall I'm intrigued by the zero. It makes search easy. Happy to stay with the zero.
O and 0 aside, have you considered any opportunities the work done by W3C ODRL might offer? https://www.w3.org/TR/odrl-vocab/
As Web3 gateways are emerging, standardized vocabulary/terminology may save a great deal of time.
I fully understand the urgent need to get NFTs up with TOS and acceptance mechanisms, and your breakthrough efforts are important first steps. But, as you have pointed out, it's hard to upgrade/downgrade going forward.
@flatout - https://www.w3.org/TR/odrl-vocab/ is a very good thought. Yes, in a standards and object-oriented approach (even ProseObjects), we can leverage standard ontologies. And the odrl-vocab for content is tightly connected to licensing (CBE-* etc.). I've played with some other ontologies that also make sense to connect to at commonaccord.org.
Re the @w3c - ProseObjects can be a pathway to making all contracts smart: https://www.w3.org/2016/04/blockchain-workshop/interest/hazard-hardjono.html (with the estimable @findthomas).