Looking forward to unpacking this at IIW. For those not yet registered, here’s a link: <
https://iiw24.eventbrite.com/>. It runs from Tuesday to Thursday of this week at the Computer History Museum in Silicon Valley.
I also trust you’ll share it at VRM Day as well. That’s tomorrow, at the same location. Our focus in the morning will be on self-sovereign terms: ones each of us can proffer as first parties in our dealings with sites and services over the Net. Those terms will live, as sources code can point to, at Customer Commons, much as personal copyrights do the same at Creative Commons: <
http://customercommons.org/terms/>.
The first two terms we’re nailing down are #NoStalking and #Intentcasting. The former will reduce or eliminate the need for ad blockers and tracking protection on the user’s side, while saving the asses of publishers and advertisers by killing the surveillance-based advertising business (aka adtech) with which they made the Faustian bargain that has given us, among other things, fake news. We already have at least one very large publisher open to saying yes, automatically, as a second party, to #NoStalking terms. The latter will reform retailing from the customers’ side. It will be easy for CRM systems to listen to and obey customer terms, and a demo is ready using Salesforce.
I describe both in two similar posts:
Others here will know better than I how UMA might help with either or both, but I’m sure it can, and hope we can talk about it and work on it at VRM Day and IIW.
Thanks,
Doc
The trick to getting rid of intermediaries is not to avoid intermediary agents but to own the agent as an individual. This is self-sovereign technology where any of the first three parties of the transaction (pastor, payee, intermediary) can be self-sovereign tech. The major trick to doing this at scale is to avoid federations, including IDPs, as much as possible. It's especially important to avoid asssuming there are federations when designing the standards that support self-sovereign technology.
The alternative to trust based on federations is trust based on distributed ledger technology as in bliockchains. This is what we're demonstrating with HIE of One using UMA as the authorization standard and self-sovereign blockchain ID as the authentication standard. Instead of a payment, our demo shows writing a prescription. See it at IIW.
Adrian
Kevin, thanks.
If I've understood your concern, it is that hosting of the data stores should be independent of financial institutions. My thought is that the data model should work for both (all) situations - the data store can be hosted by a financial institution or by someone else, including by individuals themselves. This, I believe, is how email works - there is a common standard and you can set up your own server for yourself or a group, or have someone else do it. The email interchange standards and open source software keeps this cheap and portable. You can take your email history when you change hosts, so hosts have little leverage.
The critical thing seems to be the data model and interchange protocols.
Jim
--
_______________________________________________WG-UMA mailing listWG-UMA@kantarainitiative.orghttp://kantarainitiative.org/mailman/listinfo/wg-uma