UMA Legal

Our "elevator pitch":

The User-Managed Access (UMA) technical protocol applies protection policies to "permission tokens". The UMA legal framework maps those permission tokens to licenses as legal devices. This licensing mechanism is valuable to individuals, organizations, legal professionals, and privacy professionals because it allows Alice to license Bob to use her digital resources on her terms.

You can find out more about UMA here:

Part of the UMA WG's work is overtly technical, and part of the work explores other layers of the BLT (business-legal-technical) sandwich. The documents linked from this page, dedicated to the Legal subgroup's work, reflect efforts in these other areas, many produced by our ad hoc "legal subgroup".

The overall goal of this subgroup: Accelerate adoption and reduce inhibitors in a business context.


Notes on mission progress

The subgroup found funding to work with legal expert Tim Reiniger starting in 2017, with a schedule to produce three staged deliverables. The first, Use Cases for Analyzing and Determining a Legal Framework, was delivered in draft on 28 Feb 2017, with the group providing commentary and revisions as input to later stages, resulting in a revised final version delivered 26 Mar 2017. The second, The Legal Value Perspective for UMA Use Cases, was delivered on 31 May 2017, again after extensive group review and commentary. The third, UMA Definitions Annotated, was delivered 25 Aug 2017.

Subgroup meetings

The subgroup's meeting times and notes are here. We meet on Fridays at 8am PT.

If you are just visiting and are interested to join the UMA Work Group and take part in this subgroup's efforts, we invite you to join! Visit our home page and see the Join link there. Note: Since the legal subgroup meetings do not count towards WG quorum, it's advised to join as a "non-voting participant" unless you also intend to join the WG meetings on Thursdays at 9am PT.

Sources of liability tension

These are some key trust relationships we are exploring for the "liability tensions" within them, that is, the misalignment of incentives that leads to a reluctance to deal with each other, mistrust, or added friction in decisions to use or deploy UMA. Here are some of our use cases?

Work to date on model text

The model text work is being encoded in the system. CommonAccord is:

" initiative to create global codes of legal transacting by codifying and automating legal documents, including contracts, permits, organizational documents, and consents. We anticipate that there will be codes for each jurisdiction, in each language. For international dealings and coordination, there will be at least one "global" code."

Here is the draft model text. The definitions are more mature than the clauses, but all of this text predates the analysis being performed and may be radically changed.

Additional artifacts

An UMA in Contractual and Regulatory Contexts primer/manual is in early draft form. This slide deck, presented at Digital Contracts, Identities, and Blockchain at MIT in May 2016, shares some key use cases. A few additional artifacts are available on the WG's GitHub wiki. All of this work predates the analysis being performed. We may produce a completely new primer/manual at the end of this process.