Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 

true
Table of Contents
outlinetrue
absoluteUrl

Introduction

tbs - brief history of group formation and launch - audience for this report (primary: Kantara leadership; secondary: others)

...

tbs - both internal and external - IRM, IDoT, UMA, CIS, other

Purpose

tbs - (from July 19 discussion) We want to focus on use cases that are about "contracting and transacting" in the context of empowering individuals, smaller companies, smaller countries, and communities in a "peer to peer" way with larger companies and countries etc. (not meaning P2P technologies necessarily, though it might do so). "Legal" means a formal statement of relationships, and it could include contracts, permits, consents, and so on. All legal documents increment relationships between some "Persons" (including both human and non-human). (from email followup to July 21 minutes) We briefly discussed how the connection of identity taxonomies to our work effort is that transactions/contracts involve parties (as Jim's emailed taxonomy demonstrates). I don't imagine we want to take on a meta-taxonomy effort, nor a whole new comprehensive taxonomy effort, but this connection is definitely important, and probably something to touch on (or cover at more length?) in our briefing note(new crystallization of the purpose, derived from a BSC DG blog post directed to the Kantara LC) The BSC Discussion Group is offering these recommendations and observations to Kantara Initiative regarding solving use cases for empowering traditionally disempowered parties (such as individuals) to "contract and transact", e.g. with parties that traditionally hold greater power (such as companies and large countries), given the new landscape of "decentralization and distributed" technologies and techniques (such as blockchain and smart contracts) and their mixture with identity.

(from July 26 discussion) 

...

tbs - identify and analyze issues uncovered through the use cases - do this in a separate top-level section?