Hi Folks - Some alternatives to murmuration (which is great, by the way).  Deleuze called it "a body without organs," but that is too ghoulish.  "Holon" is too space-aged.  "Lagrangian entropic gradients" is too wacky.  


I didn't realize that "stakeholders" was a term of art, and I have used that too freely in the past


I have returned to using "community of interest," but with the qualifier that it is also time bounded to accommodate the notion of change through time.  


Kind regards, 
Scott
From: wg-uma-bounces@kantarainitiative.org <wg-uma-bounces@kantarainitiative.org> on behalf of John Wunderlich <john@wunderlich.ca>
Sent: Friday, November 6, 2015 12:39 PM
To: Andrew Hughes
Cc: wg-uma@kantarainitiative.org WG
Subject: Re: [WG-UMA] Notes from UMA legal subgroup telecon 2015-11-06
 
+1 Andrew;

I use stakeholders in a very particular sense when I do business process improvement work, and I suspect others will have particular uses for the contexts from whence they came. Hence I agree that stakeholder should be off the table.

We need something that is, to some extent, a self descriptive term for transient and/or permanent groups of entities that are created by their relationships to one another or through the relationships that they have with each other - if I understand what you were describing. I’m reminded more of a flock than a community, since the group can change and move based on the rules by which the particular flock was consituted. Simple flocking rules generate complex coordinated flocking behaviour - which is what I sense you’re trying to get at.

One is tempted to refer to a murmuration, but that might be too cute.
Unbelievable Starlings
A super amazing flock of starlings swoops low over the streets.



Sincerely,
John Wunderlich
(@PrivacyCDN)

On Nov 6, 2015, at 1:14 PM, Andrew Hughes <andrewhughes3000@gmail.com> wrote:

Aiighhh!!!!! Not Stakeholders!!!! 

;-)

I know that they should have a stake in the situation, but it's such an abused term... 
Constituents, Group, MicroSociety, Participants, ...

Andrew Hughes CISM CISSP 
Independent Consultant
In Turn Information Management Consulting

o  +1 650.209.7542
m +1 250.888.9474
1249 Palmer Road,
Victoria, BC V8P 2H8
AndrewHughes3000@gmail.com 
ca.linkedin.com/pub/andrew-hughes/a/58/682/
Identity Management | IT Governance | Information Security 


On Fri, Nov 6, 2015 at 10:02 AM, j stollman <stollman.j@gmail.com> wrote:
Regarding a term for Community of interest, how about "stakeholders"?


---------------------------------
Jeff Stollman
stollman.j@gmail.com
1 202.683.8699

Truth never triumphs — its opponents just die out.
Science advances one funeral at a time.
                                    Max Planck

On Fri, Nov 6, 2015 at 12:09 PM, Eve Maler <eve@xmlgrrl.com> wrote:
  • Goal: start building a general "legal stack" for UMA-specific elements
  • Learn more of Andrew H’s use case details
  • Examine the sociotechnical norms for potentially useful concepts
  • AOB
Attending: Eve, John, Ann, Adrian, Andrew H, Jim, Jon, Mark, Nat, Sal

Andrew has sketched a model for resource set registration services. So far this is very informal, so we won’t be minuting it in detail.

What’s a better word/phrase for “community of interest”/CoI? Policymakers? Constituents?

He’s trying to capture “reliance” relationships, and obligations/commitments.

Adrian has concerns: Can we look at the simplest possible scenario and just map that? On the other hand, providing “legal resources” (akin to “developer resources”) for those who have constraints that require an UMA solution would be very valuable, because this is a real-world situation that we expect to be common.

The “Open Identity Trust Framework Model” white paper may be useful for background on generic trust frameworks. OITF was influenced by the Liberty Alliance work, and Andrew has contributed to TF work heavily over time.

Once you have the abstract model, then you can identify your specific “users” and “operators”.

So can we make progress on our goal, given Andrew’s input? We could work on outputs for his “C” elements, and a lot of the “B”. Jurisdiction clauses are something everyone needs. And if we pick a business environment (university, or health, or DIACC!), we know of typical clauses they’ll need. UMA-specific stuff may affect, all of the business, legal, and technical sections (portions of the stack). Standardizing these clauses is the benefit we’re aiming to supply.

Can we use the sociotechnical norms language? Eve suggests that the five norms are so clear, and clarifying, that they would be helpful for distinguishing the piece-parts of UMA flows that reflect different norms and developing model clauses for each of the B, L, and T layers that can focus on one type of norm at a time. John W thinks that there is relevance for consent receipts. Eve muses: Maybe Authorization could be for true consent receipts, and Commitment, Prohibition, Sanction, and Power could be for other types of transaction receipts? Powers could be conveyed to another party (such as durable medical power of attorney), and then there could be a flow chart after that where prohibitions and sanctions and such come into play.

Next steps:

  • Adrian is kindly running the next call. He will send out an agenda focusing on agency restatements.
  • After her vacation, Eve will work with John and Andrew (and maybe rope in Tim as well?) on recasting whatever old Binding Obligations are still useful into norms language, and try to bucket them into B/L/T clauses for putative sections of a “stack".


Eve Maler | cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl | Calendar: xmlgrrl@gmail.com


_______________________________________________
WG-UMA mailing list
WG-UMA@kantarainitiative.org
http://kantarainitiative.org/mailman/listinfo/wg-uma



_______________________________________________
WG-UMA mailing list
WG-UMA@kantarainitiative.org
http://kantarainitiative.org/mailman/listinfo/wg-uma


_______________________________________________
WG-UMA mailing list
WG-UMA@kantarainitiative.org
http://kantarainitiative.org/mailman/listinfo/wg-uma



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.