Discussions on Life Management Platforms and Technology-Enabled Relationship Management#
Phil Windley Said#"User control is central tenant of any online world that most of us will want to live in. You don't have to consider things like surveillance-based marketing or devices that spy on us long to realize that a future that's an extrapolation of what we have now is a very real threat to personal autonomy and freedom."
A key part of the answer is developing protocols that make it easy to give control to users.The Seven Laws Of Identity", I wanted to provide the starting point for the community to build a similar set of design constraints and considerations for relationships and Relationship Management Technologies. Our current IAM methods will be insufficient in a near future in which we are dealing with an unreasonable number of people and things and the relationships between them. At the IRM Summit, I’ll be presenting a strawman set of laws for relationships to help us think about this coming future. To that end, here is a preview of the laws (and axioms and attributes) of relationships.
Traditional IAM techniques are not optimized for the world our industry faces—a world populated by innumerable things and the complicated interactions between people and those things. Such a world runs on relationships. As we enhance IAM to be vitally relevant in such a world, the question remains as to how we should guide it. (from his talk on The Laws of Relationships).Kelly Flanagan on "Domains, Personal APIs, and Portfolios" touches on some good ideas they are working on. Some of their objectives include
- Encourage members of our community to not simply consume, but contribute to the body of knowledge through the use of blogs and social media.
- Support individuals in publishing a Personal API (i.e. api.example.com) that allows the owner to authorize others to interact with their personal information and revoke access privileges as desired.
Some more content from the site:
Personal API and Portfolios#Imagine a world where other sites on the web don’t hold your personal data, but instead request access to the data they need through your Personal API. Perhaps you grant them access to only the portions they actually need and restrict them from others. They use the resources they’ve been authorized to access, perform the business functions you desire, return results, and their access is revoked.
For example, imagine you work for weLovePrivacy.com and it’s payday. The payroll system springs to life and determines how much you should be paid this month. However, it needs to know how much should be withheld for taxes, how much pretax contributions to make, where these should be made, where you want your money deposited, etc. In a traditional system all of this information is centrally held. This centrally held information compels the institution to create systems to enable you to manipulate it, and makes the company liable for any loss of this data. On the other hand, you are depending on the institution safeguarding your personal information and not using it for nefarious purposes, a dangerous assumption.
However, there is a better way. Imagine the payroll system interacts with your Personal API to obtain your social security number, the number of exemptions you are declaring, the name of your 401k vendor, 401k account number, your checking account provider and account number, etc. The institutional system does the computation and disbursements, and your Personal API revokes access to these resources until the next time they are needed. While the institution could store the collected information it may not be in their best interest to do so and could even be released to them with the understanding it is to be used for the sole purpose disclosed to the user.
While it may be a while before ERP administrators are comfortable getting employee data from their personal API, there are plenty of other scenarios where a personal API is useful. Portfolios is an example of such a scenario. An instructor at an institution requests authorization to place assignments into your Personal Portfolio, their request is granted, and the assignments are deposited. You perform learning activities that generate solutions to the assignment, and deposit these in your portfolio. You have authorized the instructor to see them and place their critiques back into your portfolio. Since this is your portfolio it moves with you from one part of your life to another, from one institution to another, etc. It is yours to use and share as you choose.
Summary#It is time for learners to take control of their content, artifacts of education, and personal information. Our desire and intent is to teach these principles to our community and give them the necessary tools. We hope to do so in a way that others can easily use and benefit from.
Some of the concepts expressed in Domains, Personal APIs, and Portfolios are the same as we have heard form others. Phil Windley talks about similar ideas using Persistent Compute Objects.
I use the application PlaceUS that performes some Life Management Platform functions in an efortless way. I like the simplicity of the concept and believe that if this were applied to a broader set of items within our life it could be something that would be used more broadly.
More Information#There might be more information for this subject on one of the following: ...nobody
- [#1] - Regaining Control of Our Data with User-Managed Access
- [#2] - The Laws of Relationships (A Work In Progress) - based on information obtained 2014-05-29
- [#3] - The Law of Relationship: A Work in Progress, Ian Glazer, salesforce.com - based on information obtained 2014-06-19
- [#4] - TERM - based on information obtained 2015-09-02
- [#5] - Domains, Personal APIs, and Portfolios - based on information obtained 2015-11-07