July 2016 - DG-BSC - mailman.kantarainitiative.org

Wiki home page has been updated with our goal statement of last week about our deliverable
by Eve Maler 14 Jul '16

14 Jul '16

Namely, a briefing note at the end of six months that answers these questions: - What is blockchain - What is CommonAccord - What are the kinds of contracts that have "smarts" - Use cases for the above - Issue identification and analysis for the above Some of our recent list discussion could, I suspect, contribute... *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits and UnSummits* are coming to <http://summits.forgerock.com/> *Sydney, London, and Paris!*

1 0

Notes from BSC telecon Julyl 14
by Eve Maler 14 Jul '16

14 Jul '16

(Apologies for any confusion; I put incorrect Thursday times in the meeting notes page! All correct now. Sigh. We finally have a process in place, and correct data...) http://kantarainitiative.org/confluence/display/BSC/2016-07+%28July+2016%29… Thursday July 14 Attending: Eve, Jim, Scott, Thomas, Thorsten, Colin Thanks to Scott we have a new Use Cases <http://kantarainitiative.org/confluence/display/BSC/Use+Cases> page! Eve speaks in favor of having champions and recording stakeholders, where possible. Scott will add. Here's the template <http://kantarainitiative.org/confluence/display/BSC/Use+Case+Template>. Adding web sequence diagrams <https://www.websequencediagrams.com/> is a very nice touch. Thorsten's email about IRM liaison opportunities probably doesn't contain use cases as such, but their work on "IRM in the wild" may bubble up use cases, which we can capture here. Okay, returning to discussing our current use case: Jeff S stated in email the concern that getting proofs that something happened *out of* a blockchain is not going to be as scalable or performant as we might be assuming. For example, we're talking about consent receipts. If an individual argues they didn't consent, and the service operator argues they did, and it's two years later, and it's hard to find that needle in the haystack, what good is a blockchain? Does IPFS help? Certificate transparency (see the RFC and the Chrome implementation) is a model where the CAs publicly attest to the certificate so that you don't have to "trust the CA". Does this help the problem we're discussing, where it's hard to get "recorded truth" out of the ledger? J-LINC Labs uses Stellar <https://www.stellar.org/papers/stellar-consensus-protocol.pdf> as a lightweight consensus protocol. Interledger was also mentioned; Jim has looked at it and likes it. Jim's take is that blockchain is really a notarization service – just validating a record. He believes Bitcoin doesn't need all that strength; you could use a (central) trust provider instead. In most social transacting, you probably don't need all the blockchain infrastructure. On the other hand, it's the best solution for the worst case: It's for the wide ecosystem. It's for the Internet (or disconnected) use cases where there's a lot of loose coupling. Given that blockchain is therefore a social mechanism, and consensus is social, and blockchain seems best suited for "lack of centralized trust" use cases, Eve shares her concern about relying on lightweight consensus mechanisms if they open the way to vulnerabilities of a social/sociological/business sort (vs. a purely technical sort). Let's look at our current candidate use case, and others, with an eye towards the wide ecosystem implications. *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits and UnSummits* are coming to <http://summits.forgerock.com/> *Sydney, London, and Paris!*

1 0

Notes from BSC DG telecon on July 12
by Eve Maler 14 Jul '16

14 Jul '16

http://kantarainitiative.org/confluence/display/BSC/2016-07+%28July+2016%29… Attending: Thomas, Eve, Jim, Scott S, Don, Marc, Philippe, Thorsten, Ann, John W The May 23-24 event at MIT, variously called *Digital Contracts, Identities, and Blockchain* and *Digital Identities, Contracts, and Blockchain*, had some notes as output. Here are relevant links: - Technical and Future Infrastructure track notes <https://docs.google.com/a/forgerock.com/document/d/14KD-KA-XPKKvuSfNx4E5B2Z…> - Business track notes <https://docs.google.com/document/d/1fNjd25h_Ne4HUedn-vKkfNP73TKZAG-PM_K7Qf6…> - Healthcare use cases track notes <https://docs.google.com/document/d/1nGTZHq7Q_51tu46jcivLLlS-1vTKXr9z_JcyntB…> - IBM Open Blockchain white paper <https://github.com/openblockchain/obc-docs/blob/master/whitepaper.md> - Article <https://medium.com/enspiral-tales/bootstrapping-a-bossless-organisation-in-…> on bootstrapping a bosses organization - Screenshot <https://slack-files.com/T02DW4GQE-F1BEJRL2G-7421d194f1> from Bart's presentation comparing "smart" and "legal" contracts (did his whole presentation get posted?) - CommonAccord intro presentation <https://docs.google.com/presentation/d/1LqdDjo41PlXBUj3l84gUVQI4H8GH04mvavH…> - CommonAccord site <http://www.commonaccord.org/> - CommonAccord Slack team invitation <https://cmacc-slack-add.herokuapp.com/> For a candidate use case, Jim proposes: Patient consent, in a context of 3-4 countries – e.g., including France, Germany. Leverage the GA4GH (Global Alliance for Genomics and Health) and genetic research. Jim has been discussing this use case with Bart Suiches of Philips Blockchain Lab. Would this be about storing consents? The GA4GH folks have a committee that created a model data sharing consent form <http://www.commonaccord.org/index.php?action=doc&file=Wx/org/genomicsandhea…> in CommonAccord. There's capacity for it to be signed. Would the Consent Receipts work be able to handle a machine-readable representation? It might need to be extended. This would be a good use case for extensibility for that spec. Culture might be the biggest barrier around consent – IRBs and equivalents would have trouble conceiving of consent as anything but a one-way door. John notes that there are six different ways to get approval to process data, and only one of them is consent. John recommends narrowing down this as a use case a bit, since it involves research and IRBs and such and takes it out of the full health regulatory environment (at least in the Canadian system). This is really a "health research" use case more than a "healthcare" use case, as it stands. *AI:* John to share research consent templates with Jim/the group. On Thursday, Scott will present a sample use case template into which we can fill use case content. Everybody should take the opportunity to get familiar with the linked material above, and start to think about their own use cases they'd like to collect. *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits and UnSummits* are coming to <http://summits.forgerock.com/> *Sydney, London, and Paris!*

6 8

Proposed agenda for BSC-DG Call (July 14th, 2016)
by Thomas Hardjono 13 Jul '16

13 Jul '16

Folks, Just a quick reminder of our BSC-DG Call: - Tuesdays: 10:30AM-EST (7:30AM-PST & 16:30PM-CET) - 30 minutes - Thursdays: 2:00PM-EST (11AM-PST & 20:00PM-CET) -- 30 minutes - Call-in info: Use join.me/findthomas for both Voice and Screen-share. Agenda for July 14th: (a) Continue use-cases discussion. (b) Scott to present a sample use-case template into which we can fill use case content. Here are the notes from the previous call: http://kantarainitiative.org/confluence/display/BSC/2016-07+%28July+2016%29… Best. Thomas/Eve/Jim

1 0

Using Join.me voice --- RE: Bridge details -- RE: BSC-DG Call Tuesday July/12/2016 at 10:30AM-EST (7:30AM-PST & 16:30PM-CET)
by Thomas Hardjono 12 Jul '16

12 Jul '16

Folks, We may not be able to use the bridge from last week. If so, let us try using the voice feature on Join.me. URL is just www.join.me/FindThomas /thomas/ ________________________________________ From: Thomas Hardjono [hardjono(a)mit.edu] Sent: Tuesday, July 12, 2016 9:48 AM To: dg-bsc(a)kantarainitiative.org Cc: eve.maler(a)forgerock.com; james.g.hazard(a)gmail.com; hardjono(a)media.mit.edu Subject: Bridge details -- RE: BSC-DG Call Tuesday July/12/2016 at 10:30AM-EST (7:30AM-PST & 16:30PM-CET) Folks, While we await the permanent number/code we can trying using last week's bridge. I've also attached a backup number. (a) Bridge number: Dial-in: Skype:+99051000000481 * US Dial-In: +1-805-309-2350 | Room Code: 613-2898 * For more dial-in information, see: http://kantarainitiative.org/confluence/display/GI/Telco+Bridge+Info Local & International Phone Numbers (Toll) Local, Skype & SIP Access United States Toll +1 (805) 309-2350 Alternate Toll +1 (714) 551-9842 Skype [+99051000000481] Skype Name: Turbo Bridge TurboPhone (beta): https://www.turbobridge.com/join.html Works with Internet Explorer on Windows only SIP Access (using IP phone or soft phone) sip:bridge@turbobridge.com SIP URL details: https://www.turbobridge.com/help/Index.html?context=180 (b) Backup number: Conference Dial-in Number: (605) 475-4700 Participant Access Code: 176720# Screen sharing using Join.Me: join.me/findthomas /thomas/ ________________________________________ From: Thomas Hardjono [hardjono(a)mit.edu] Sent: Monday, July 11, 2016 10:31 PM To: dg-bsc(a)kantarainitiative.org Cc: eve.maler(a)forgerock.com; james.g.hazard(a)gmail.com; hardjono(a)media.mit.edu Subject: BSC-DG Call Tuesday July/12/2016 at 10:30AM-EST (7:30AM-PST & 16:30PM-CET) Folks, Just a quick reminder of this week's BSC-DG call. - Tuesdays: 10:30AM-EST (7:30AM-PST & 16:30PM-CET) - 30 minutes - Thursdays: 2:00PM-EST (11AM-PST & 20:00PM-CET) -- 30 minutes Best. Thomas/Eve/Jim

1 0

Bridge details -- RE: BSC-DG Call Tuesday July/12/2016 at 10:30AM-EST (7:30AM-PST & 16:30PM-CET)
by Thomas Hardjono 12 Jul '16

12 Jul '16

Folks, While we await the permanent number/code we can trying using last week's bridge. I've also attached a backup number. (a) Bridge number: Dial-in: Skype:+99051000000481 * US Dial-In: +1-805-309-2350 | Room Code: 613-2898 * For more dial-in information, see: http://kantarainitiative.org/confluence/display/GI/Telco+Bridge+Info Local & International Phone Numbers (Toll) Local, Skype & SIP Access United States Toll +1 (805) 309-2350 Alternate Toll +1 (714) 551-9842 Skype [+99051000000481] Skype Name: Turbo Bridge TurboPhone (beta): https://www.turbobridge.com/join.html Works with Internet Explorer on Windows only SIP Access (using IP phone or soft phone) sip:bridge@turbobridge.com SIP URL details: https://www.turbobridge.com/help/Index.html?context=180 (b) Backup number: Conference Dial-in Number: (605) 475-4700 Participant Access Code: 176720# Screen sharing using Join.Me: join.me/findthomas /thomas/ ________________________________________ From: Thomas Hardjono [hardjono(a)mit.edu] Sent: Monday, July 11, 2016 10:31 PM To: dg-bsc(a)kantarainitiative.org Cc: eve.maler(a)forgerock.com; james.g.hazard(a)gmail.com; hardjono(a)media.mit.edu Subject: BSC-DG Call Tuesday July/12/2016 at 10:30AM-EST (7:30AM-PST & 16:30PM-CET) Folks, Just a quick reminder of this week's BSC-DG call. - Tuesdays: 10:30AM-EST (7:30AM-PST & 16:30PM-CET) - 30 minutes - Thursdays: 2:00PM-EST (11AM-PST & 20:00PM-CET) -- 30 minutes Best. Thomas/Eve/Jim

1 0

BSC-DG Call Tuesday July/12/2016 at 10:30AM-EST (7:30AM-PST & 16:30PM-CET)
by Thomas Hardjono 11 Jul '16

11 Jul '16

Folks, Just a quick reminder of this week's BSC-DG call. - Tuesdays: 10:30AM-EST (7:30AM-PST & 16:30PM-CET) - 30 minutes - Thursdays: 2:00PM-EST (11AM-PST & 20:00PM-CET) -- 30 minutes Best. Thomas/Eve/Jim

1 0

Reminder: Our two-calls-a-week schedule doesn't start until next week
by Eve Maler 07 Jul '16

07 Jul '16

(end of message) *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits and UnSummits* are coming to <http://summits.forgerock.com/> *Sydney, London, and Paris!*

1 0

Notes from BSC DG telecon on July 5
by Eve Maler 05 Jul '16

05 Jul '16

Since we'll be meeting so frequently, I've gone for a hybrid approach to collecting meeting notes: Put all notes from each month into a single wiki page. The TOC for each of these pages will hopefully be self-explanatory and not too terribly overwhelming. If you'd prefer for me to collect *all* notes into a single page across our lifespan, I can change to that. http://kantarainitiative.org/confluence/display/BSC/2016-07+%28July+2016%29… Eve is taking notes and is happy to take notes in future. *Attendees and introductions* Please send introductions to the list if Eve got anything wrong! - Jim Hazard - Lawyer frustrated with word processing - Eve Maler - ForgeRock - interesting UMA/smart contract connections - Thomas Hardjono - interest in getting a high-level language specified for contracts - Andrew Hughes - runs the Leadership Council - Jeff Stallman - blockchain developer - Scott Shorter - Kimble & Associates - doing some ONC work, auditing, and governance - Don Quigley - director of services leader for GE - Mark Aronson - Penn council of notaries - Kathleen Connor - consultant involved in UMA, UMA legal, and ONC - Ann Vroom - private individual interested in blockchain - Clare Nelson - AllClearID - Thorsten Niebuhr - John Wunderlich - Javier Moreno - Colin Wallis *What is a DG about?* A DG has more informal deliverables. It might, for example, recommend formation of a WG. There are several Kantara WGs and efforts that have a legal flavor to them: - UMA, with its UMA legal subgroup - Consent and Information Sharing - The Identity Assurance effort, with its trust framework components Smart contracts, broadly defined as executable code to represent legal agreements, are one way to approach agreements. *Participant goals* Jim briefly described his work on digitizing legal agreements. Eve briefly described some discussion from the Digital Contracts event/workshop of six weeks ago. The worlds of smart contracts and digital contracts that use natural language are distinct. There’s a gap between them. It seems to be narrowing, but there seems to be urgency about closing the gap and connecting them. Mark says that notary had been used previously as a synonym for timestamping. Now blockchain is coming to the fore in the same way. John would like to clarify what goes, and what should go, on a blockchain. Jim believes that smart contracts would be good to focus on independently of how they themselves are recorded. Blockchain is often the wrong way to store information. Jeff concurs with that. Blockchain is a suite of technologies, and you don’t always need all of them. Kathleen is working for the DHA security architect. The overhead for establishing trust frameworks is incredible. Adding agility would be great. Also, helping privacy, security, and administrative parts of healthcare to scale — HL7 V2, V3, and FHIR — is important. Clare is a fan of Steve Wilson of Constellation. UBS is spending a lot of money in financial services. She’s interested in pursuing a conversation along that path. John also notes that “contracts of adhesion” that often force individuals to accept terms and conditions are another use case where scalability of forming agreements would help — in this case, help individuals directly. Scott brings up a long-ago goal of technically verifiable agreements that have been parameterized. It now seems a lot more possible. *Logistics and deliverables* How often to meet? Andrew recommends five months of intensive meeting and discussion, one month of intensive writing, and the reporting out. Several people speak up in favor of frequent short/intensive meetings. Deliverables? Thomas suggests a use case document, ranked by priority. John summarizes the discussion by suggesting a final deliverable that would be a briefing note that contains “what is a BC, what is CmA, what are the kinds of contracts that have ‘smarts’, use cases, issue identification and analysis”, etc. We could take a look at some of the outputs of the Digital Contracts event held May 23-24, which Kantara helped to sponsor as part of our work. Jim met with Bart Suiches of the Philips Blockchain Lab subsequently to the Digital Contracts event and discussed patient consents as a use case. John cautions about using health as our first or primary use case for discussion. Jim agrees that it’s the hardest case, which makes it attractive to him. But we can start simple. Bart told him they’re absorbed figuring out the GDPR. Don’t forget that we can use our mailing list for discussion. *Next steps* *AI:* Eve: Share out links to notes and artifacts from the Digital Contracts event. Let’s meet twice a week for 30 minutes each, at different times to spread out for US and Europe, and to avoid the UMA call. They will be (we think) at Tue 11am ET and Thu 2pm ET. The group reached consensus on having Thomas and Eve as co-chairs. Scott kindly agreed to serve as use case collector on the DG wiki. John created a use case template <http://kantarainitiative.org/confluence/display/infosharing/Use+Case%3A+Tem…> for CIS WG usage we might consider using. *AI:* Thomas: Send out a note confirming the call times and set up the call dial-ins with Shannon. We’ll start the repeating call series next week. *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits and UnSummits* are coming to <http://summits.forgerock.com/> *Sydney, London, and Paris!*

1 0

Correction - RE: Twice-weekly BSC-DG telecon calls
by Thomas Hardjono 05 Jul '16

05 Jul '16

Correction: - Tuesdays: 10:30AM-EST (7:30AM-PST & 16:30PM-CET) - 30 minutes - Thursdays: 2:00PM-EST (11AM-PST & 20:00PM-CET) -- 30 minutes (Thanks Marc) /thomas/ ------------------------------------------ >>> -----Original Message----- >>> From: Thomas Hardjono >>> Sent: Tuesday, July 05, 2016 3:42 PM >>> To: dg-bsc(a)kantarainitiative.org >>> Cc: Thomas Hardjono; eve.maler(a)forgerock.com; Jim Hazard >>> (james.g.hazard(a)gmail.com) Shannon Taylor (staylor(a)virtualmgmt.com) >>> Subject: Twice-weekly BSC-DG telecon calls >>> >>> >>> Folks, >>> >>> Thank you for attending the first DG Telecon call today. >>> >>> In order to avoid a time-clash with the Kantara CIS weekly call, we will >>> swap the times on Tuesdays and Thursdays for our telecons. >>> >>> Note that our twice-weekly calls is only scheduled for 30 minutes each. >>> >>> Here are the times: >>> >>> - Tuesdays: 10:30AM-EST (7:30AM-PST & 16:30PM-CET) - 30 minutes >>> >>> - Thursdays: 2:00AM-EST (11AM-PST & 20:00PM-CET) -- 30 minutes >>> >>> >>> I will follow-up with the bridge numbers. >>> >>> In the meantime, please begin to think about use-cases. >>> >>> >>> Best. >>> >>> >>> Thomas/Eve/Jim >>> >>> >>> >>> ------------------------------------------ >>>

1 0