Thanks Eve, and hello to the list from my new work email address. It was due a rebranding, not a change of affiliation.

 

I’ll aim to update my sections by the end of this week. I can chair the call if there is new content to review.

-

Scott

 

From: <dg-bsc-bounces@kantarainitiative.org> on behalf of Eve Maler <eve.maler@forgerock.com>
Date: Monday, October 10, 2016 at 12:04 PM
To: "dg-bsc@kantarainitiative.org" <dg-bsc@kantarainitiative.org>
Subject: [DG-BSC] Please read and respond ASAP if you're mentioned: Meetings and section assignments this week, and how to fill in sections

 

Both Thomas and I are unable to attend/run the meetings this week. We have a couple of options: a) If there is new section content to review, we could seek a chair pro tem (Scott S?) for that purpose, or b) if there isn't, we probably shouldn't meet.

 

The current assignments are as follows. You can find most of them in the Report itself. Can people please speak up TODAY about when they can complete first drafts, and we'll make a judgment call ASAP about tomorrow's call?

• IPFS: Thomas
• Certificate Transparency: Scott S (already some content there)
• CommonAccord: Jim H
• Protocol-Specific Contract Provisions:

• Kathleen for HL7 piece
• Eve for UMA model text piece

• Legal contracts: Scott D
• Digital Identity: Andrew
• UMA: Eve
• Consent Receipts: John W
• User-Submitted Terms: John W or designee
• Case Study: MedRec: Kathleen
• Case Study: Blood Diamond: Matisse+Scott S
• Case Study: Sovrin: Eve

For case studies, we said we'd use a questionnaire approach something like this:

• Deficits and benefits of how the problem space was/is being solved
• Proposed benefits of the new solution space – crystalize this (e.g., fraud, not "user empowerment"?)
• Different approaches being taken (e.g., whitelist? blacklist? other?) in the new solution space
• Strengths, weaknesses, risks, and open issues being seen in practice
• Cross-references to the appropriate other technology, case study, and use case sections
• Since our Report process is time-boxed, go into only as much depth as you can in a short period of time

For use cases, we already have a template in use; I feel it may benefit from enhancement with points from the above.

 

For technology/technique sections, we said we'd like to see this information:

• A definition
• A short discussion of strengths and weakness of the current way of doing things
• A short comparative discussion of strengths and weakness of the new way of doing things (if the technology/technique is "new")
• Pointers to the other technology and technique sections as appropriate (so that we have cross-references among the sections)

Eve Maler
ForgeRock Office of the CTO | VP Innovation & Emerging Technology
Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl
ForgeRock Summits are coming to London and Paris!