- Review the first draft deliverable http://www.commonaccord.org/index.php?action=doc&file=GHx/KantaraInitiative/UMA/2013/2.md and its model clauses and definitions - How to take our work forward? Continue our subgroup meetings? - AOB Attending: Eve, Andrew H, Steve, Adrian, John W, Mark, Ann, Jon N, Jim, Scott, Dazza *How to take our work forward? Continue our subgroup meetings?* What is the interest in continuing the subgroup meeting series into 2016? Andrew is interested in a capped-length subgroup meeting series, e.g. six months tied to outcomes, but is wary of scope drift. Adrian would like to see an implementation group continue, but he's wondering where the academic focus went. Eve described the 2015 mission http://www.commonaccord.org/index.php?action=doc&file=GHx/KantaraInitiative/UMA/2013/2.md as relentlessly practical. Mark noted that with the consent receipt work pushing forward, the direction of this work and further collaboration seem very important. Eve will propose a fresh, limited draft charter for the subgroup. Eve will schedule a meeting on Friday January 8 for us to review where we are for the first half of 2016. *Review the first draft deliverable and its model clauses and definitions* *Intro first para:* We suggest Jim and Scott follow up to switch to "represent" language vs. declaration and conformance (only "operators" can conform, vs. "users"). *Does the color marking system work?* Andrew suggests that color coding doesn't help for tokens. But for defined terms and abbreviations, it does, and probably for the persons/parties. *Idea for the UX:* It would be cool if clicking on a term/abbreviation would take the reader to the definition. *What to do about Individual/NPE/Subject?* In the era of IoT, we have to get this very right. The alternative that would be both legal- and technical-friendly would be *Individual *(?)*/Legal Person/* Device/Application/etc.*/Person*. Note that Subject in a legal sense is much more than "subject" in a technical sense; the former is the "subject of someone's gaze" (think data subject) and the latter, at least in security and identity is the subject of authentication. Also, we'll need conversion tables into other natural languages. Can we define the terms as bounded by US law until we can vet that it works cross-jurisdictionally, or provide sets of terms that are compatible with different jurisdictions? If we're targeting Canada as a first "customer", how should we handle this? Maybe we can put a note into the relevant definitions, we can put in notes about these being derived from US law. Can we borrow/steal from some existing federation language to support our UMA-specific needs? The UETA may have everything we need to support both "bags of protoplasm" and "organizations" running "server-side services" and "client-side apps". Jim will propose a change to this set of terms, with Legal Person (without an abbreviation). We may someday use NPE for equipment. *Two-party or three-party relationships?* We can see three-party relationships we clustering of two-party relationships, where a condition precedent to one two-party relationship is the formation of a prior two-party relationship. We can state any condition precedent and/or condition subsequent in terms of UMA roles (and leave holes for non-UMA conditions). AI: Jim/Eve: We'll have to be sure to do that in our clause reusability structuring. Scott notes that there's an RNA analogy. And Dazza notes that the Carat Guidelines from the '90s (here http://civics.typepad.com/files/carat_final_011400-1.pdf) said that there should be a limited number of roles, functions are allocated to roles, and when there are permutations and functions are allocated to more than one legal party, it should be clear what rights and obligations are delegated to them and which are delegable and non-delegable. Maybe we can include some of that language! *Adrian's earlier comments:* In email, Adrian sent comments that pointed out a typo we will fix. *Analyzing the very first clause:* "When the Client successfully gains access from a Resource Server to a protected resource by wielding a valid "bearer" RPT associated with at least one currently valid permission for the type of access sought, the Requesting Party using that Client gains an obligation to the Authorizing Party to adhere to any terms it agreed to in order to gain the permission." We drilled down into the specific Adhere-to-Terms clause source http://www.commonaccord.org/index.php?action=source&file=GHx/KantaraInitiative/UMA/2013/2_2_1.md, which has "comments" and "issues" that don't show up in the main document rendering. Eve observes that: - A LOT of conditions precedent seem to be buried in that one condition! - We probably need to get into the weeds of the Client Operator in a way we haven't previously. - We haven't said that the Requesting Party actually supplied claims, and maybe this Duty should only depend on a Condition of having supplied claims; the Issue mentions that the Condition perhaps be at the juncture of supplying the claim. - And oh, by the way, this clause is just stating the "blinding flash of the obvious" about what the protocol messages *exist to mean*. SAML the protocol never ever stated this: An IdP never promises to mean that it authenticated somebody at time *x* using method *y*. Scott observes that: - Right. Sit down in the chair -- get a haircut -- you have to pay for it. :-) Dazza observes that: - We have to get into "all applicable laws need to be followed". - We can start to have everyone propose clauses for our "clause bank", now that we are hammering out the canonical form. Jim observes that: - We can actually have a series of "Duty" phrases that can appear as alternatives and/or can aggregate. This would be a different reusability logic vs. the Adhere-to-Terms unique naming of each Duty, and would depend on whether the Condition is unique per set of Duty phrases. Jim and Eve: Propose a fresh clause skeleton http://www.commonaccord.org/index.php?action=source&file=GHx/KantaraInitiative/UMA/Z/Clause.md . *Thanks to all, with especial thanks to Jim and Mark! See you on the other side!* *Eve Maler*Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl