Jim - GAGH (Global Alliance for Genetics and Health) - With machine readable consent group. Starting with taxonomy for access. Figure out a way of handling the specification of authorization of use of a genome. With Thomas working on a UMA / Common Accord / Blockchain hack. Scot interested in gene information sharing. Adrian also involved via a Mayo Clinic genomic determinism and data management. Steve with blockchain. Ann wants to help. Will be at FutureCommerce Hackathon. Thomas: CommonAccord for GitHub contract version tracking and specialization. The core contribution from Jim allows modularized pieces of the contract. Transacting parties A and B would each have to set up their own GitHub client and each time a party makes a change a hash is sent along with the diff that's sent to the other party and the hash is also put up on a blockchain. UMA comes in for the privacy aspects of the contract. Access control to contract via UMA to avoid having to ship the contract around.
Consents expressed in CommonAccord format - points to data item - Organize the machine readable consent to drive UMA policies.
CommonAccord + UMA + Blockchain is a general solution. Blockchain is advertising my signature / providing non-repudiation / for the process. Helps with escrow. SHA-1 to find data a la BitTorrent and SHA-256 are combined. May need to also conform to the Digital Signature Act using X509. Stock market analogy - stock certificates, then derivatives. Multi-channel verification of rights.
What can we code to explain this? CommonAccord interacting in a GitHub like server + add the hash drop out - then add UMA and later blockchain. Patient consent or material transfer agreements.
Jim demos NDA between two parties. Called Nameless. Common Accord + code to build something like a Merkle tree + post hash to blockchain as the minimum viable demo.
Separate piece of this - what would be a taxonomy of access - by adding UMA -
Dazza suggests the iAuth project for FutureCommerce that takes the hash of a commit in GitHub and its message digest via GitHub API (blocksign) - then make it so one of the commits are linked to OAuth2 / UMA and tied to a scope.
Let's continue this discussion on 1 2 or 3 projects on the Slack channel for the next week as prep for http://futurecommerce.civics.com/index.html Please email Dazza or Mark to join the Slack channel (I don't seem to have invite power).
Legal call next week will go on as scheduled and FutureCommerce starts an hour after (1PM EST).