Re: [DG-BSC] Legal/technical smart contract WG -- RE: Notes from BSC telecon Thursday, April 27

Thomas; Almost every contract I've seen has a phrase like, "This contract/agreement/memorandum will be governed by the laws of [jurisdiction]". Given the variation between and the specific requirements of multiple jurisdictions, a specification might be too big of a first step. That being said, Common Accord would be seem to be a natural ally and good starting point. JW John Wunderlich, BA, MBA IAPP Fellow of Information Privacy CISA, CIPM, CIPP/C, PbD Ambassador @PrivacyCDN https://twitter.com/PrivacyCDN & Privacist On 28 April 2017 at 08:14, Thomas Hardjono wrote:

...

...

...

Eve: We've talked from time to time about the UMA Legal subgroup possibly spinning up as its own group. Maybe there's something to think about here – combining forces, or two separate WGs? Maybe a "Legal WG" with Kantara-wide scope would make sense; John repeats himself in Legal, CIS, a lot. It would need to be able to produce technical specs as well (that is, have the right IPR policy for that).

One thing that I'd like to see is a specification (actual spec, not best practices or guidelines) on a "smart-contract", something that has a hope of being accepted in the legal mindset/industry:

(a) Technical: What is a technical definition of a smart contract: define the fields (syntax), allowable values and allowable interpretations (e.g. semantics). Digital signatures.

(b) Legal: What information needs to be captured in a smart-contract, for example, to make it admissible in court.

Some progress is being made (see bill HB2417 in Arizona and the one in Vermont by Oliver Goodfellow), but I believe more work needs to be done. For example, is the legal acceptance of HB2417 based on the digital signatures only or also on additional features.

So, a new Kantara WG (a) with the right mix of legal/technical and (b) very well defined deliverables, would be groundbreaking.

/thomas/

________________________________________ From: dg-bsc-bounces@kantarainitiative.org [dg-bsc-bounces@ kantarainitiative.org] on behalf of Colin Wallis [ colin@kantarainitiative.org] Sent: Thursday, April 27, 2017 11:11 PM To: Eve Maler Cc: dg-bsc@kantarainitiative.org Subject: Re: [DG-BSC] Notes from BSC telecon Thursday, April 27

Folks

Great work there. Thanks!

The Report is shaping up well, but as Eve implies, it needs your best strategic thought bubbles being applied to those recommendations.

If this helps at all, I am aware that the Leadership Council is seriously considering re-starting Kantara's P3 WG (Privacy and Public Policy). Who was around and remembers those ground-breaking, thought provoking calls on P3?:-).

I bring this to your attention because if you do recommend a Legal WG, combining the efforts from UMA Legal and BSC, then there will be great cross-walk potential with P3.

Thanks again,

Colin

Executive Director Cell: +44 (0)7490 266 778 Kantara Initiative Inc.https://kantarainitiative.org/

[https://drive.google.com/uc?id=0B7y8c3lrgRtUUjRFMHFMQm1BR3M& export=download]

On Thu, Apr 27, 2017 at 8:52 PM, Eve Maler > wrote: http://kantarainitiative.org/confluence/display/BSC/2017- 04+%28April+2017%29+Meetings#id-2017-04(April2017)Meetings- Thursday,April27

Agenda:

* Report<https://docs.google.com/document/d/ 1HOVJ3lKqOIjwCqPt5jFxfLr7wEoJ0ZVNbMGsdsWzCKQ/edit?usp=sharing> work

Attending: Eve, Matisse, Marco, Thomas, Susan, Jeff, Maryann, Kathleen, JohnW

The candidate recommendations are, so far, not captured in the report – . Let's confirm today which ones we "believe in", and add any others, and then put them in the report.

Kathleen notes that ONC is beginning work on a trust framework/contract. Hopefully

Our WG recommendation: How about: Spin up a WG to develop on blockchains and smart contract good practice on use and handling of data related to individuals so as to facilitate individual autonomy [and enable equitable and efficient participation in transaction ecosystems?].

John talks about knowledge, choice, and control as the three axes of autonomy. Ecosystems typically constrain autonomy.

Add to potential liaison relationships: ONC and HL7.

The recommendation we want to make has a pretty sharp audience, set of outputs, set of activities, and set of directions for next steps.

We've talked from time to time about the UMA Legal subgroup possibly spinning up as its own group. Maybe there's something to think about here – combining forces, or two separate WGs? Maybe a "Legal WG" with Kantara-wide scope would make sense; John repeats himself in Legal, CIS, a lot. It would need to be able to produce technical specs as well (that is, have the right IPR policy for that).

Kickstarting the good practice work: We want to recommend to all the "legal capacity to contract" (parties/counterparties) people that they should be using identity standards and, as much as possible, standard claim catalogs so that they can get the benefit of standard flows and standard claim/attribute semantics. (Point to "Analysis of Integrating Legal Contracts and Smart Contracts" section.)

Eve made up an editing task list for herself and Thomas. Keep an eye on report changes.

AI: All: Please review the Report and comment in it or on the list! Keep in mind we're at the very end.

AI: Eve: Ask for one more meeting next Thursday. It's the LAST ONE.

Eve Maler ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756tel:(425)%20345-6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

_______________________________________________ DG-BSC mailing list DG-BSC@kantarainitiative.orgmailto:DG-BSC@kantarainitiative.org http://kantarainitiative.org/mailman/listinfo/dg-bsc _______________________________________________ DG-BSC mailing list DG-BSC@kantarainitiative.org http://kantarainitiative.org/mailman/listinfo/dg-bsc

-- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.