This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links
Law of Consistent Experience Across Contexts
Law of Consistent Experience Across Contexts

Version management

Difference between version and

At line 1 added 30 lines
!!! Overview
The unifying identity metasystem must guarantee its users a simple, consistent experience while enabling separation of [contexts] through multiple operators and technologies.
[{$pagename}] is a [Law] defined in the [The Seven Laws Of Identity].
Let's project ourselves into a future where we have a number of contextual [Digital Identity] choices. For [example]:
* Browsing: a self-asserted [Digital Identity] for exploring the Web (giving away no real data)
* Personal: a self-asserted [Digital Identity] for sites with which I want an ongoing but private relationship (including my name and a long-term e-mail address)
* [Community]: a public [Digital Identity] for collaborating with others
* Professional: a public [Digital Identity] for collaborating issued by an [Organizational Entity]
* [Credit card|Payment Card]: a [Digital Identity] issued by my [Financial Institution]
* [Citizen]: an [Digital Identity] issued by my a [government Entity]
We can expect that different individuals will have different combinations of these [digital identities|Digital Identity], as well as others.
To make this possible, we must "thingify" digital identities—make them into "[things|Entity]" the user can see on the desktop, add and delete, select and share. (We have chosen to "localize" the more venerable word "reify".) How usable would today's computers be had we not invented icons and lists that consistently represent folders and documents? We must do the same with digital identities|Digital Identity].
What type of digital identities|Digital Identity] is acceptable in a given [context]? The properties of potential candidates will be specified by the Web service from which a user wants to obtain a service. Matching thingified digital identities can then be displayed to the user, who can select between them and use them to understand what information is being requested. This allows the user to control what is released.
Different [relying parties|Relying Party] will require different kinds of digital identities|Digital Identity]. And two things are clear:
* A single [relying parties|Relying Party] will often want to accept more than one kind of [identity|Digital Identity], and
* A user will want to understand his or her options and select the best [identity|Digital Identity] for the [context]
Putting all the laws together, we can see that the request, selection, and proffering of [Digital Identity] information must be done such that the channel between the parties is safe. The user experience must also prevent ambiguity in the user's [consent], and understanding of the parties involved and their proposed uses. These options need to be consistent and clear. [{$pagename}] is required for this to be done in a way that communicates unambiguously with the human system components.
As users, we need to see our various identities as part of an integrated world that nonetheless respects our need for independent [contexts].
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthorTop