Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Higgins white paper outline"
| Line 12: | Line 12: | ||
*Outline | *Outline | ||
| − | + | # Clarify the Audience (Why does he reader care) | |
**Target Audience - Persons who have no previous background in Higgins, who need something between the home pages and the technical details. | **Target Audience - Persons who have no previous background in Higgins, who need something between the home pages and the technical details. | ||
*** Decision makers - business managers (CIO, CTO's and privacy/policy people). | *** Decision makers - business managers (CIO, CTO's and privacy/policy people). | ||
| Line 21: | Line 21: | ||
** Enterprise point of view (may come in front door and or back door) | ** Enterprise point of view (may come in front door and or back door) | ||
| − | + | # What are the problems we are trying to solve? | |
| + | * Use a consistently themed story (as per advice of that book.) through out the paper | ||
| + | **Paul with consumer perspective problems | ||
| + | **Mary with enterprise perspective problems | ||
* History of the technology of related efforts, what are their limitations, and what is there current status. (What are the things out there that need to be considered to provide context. Venn of Identity Diagram (Eve M.) | * History of the technology of related efforts, what are their limitations, and what is there current status. (What are the things out there that need to be considered to provide context. Venn of Identity Diagram (Eve M.) | ||
| Line 29: | Line 32: | ||
**OpenID (high level) (Phishing issue...) | **OpenID (high level) (Phishing issue...) | ||
| − | + | # Higgins Technology deeper dive (issue two doors (Higgins client and Higgins Server - yes or 3 doors?) | |
** Positioning | ** Positioning | ||
*** Higgins problem statement. | *** Higgins problem statement. | ||
| Line 47: | Line 50: | ||
**** CP's | **** CP's | ||
** Implementation | ** Implementation | ||
| − | ** Deployment use case(s) to make this concrete Using a consistent story. | + | ** Deployment use case(s) to make this concrete Using a consistent story. |
| − | + | # So what does this mean? (Did it solve the problems?) Where do we see things going. | |
| − | + | # Conclusions /next Steps | |
>>>>>>>>>>>>>>>>>>>> | >>>>>>>>>>>>>>>>>>>> | ||
Revision as of 12:27, 29 October 2008
- Draft
- Editor - Hank
- A Higgins paper, published under the EPL, with copyright by individual contributors.
- 1 long complete paper - ~30 pages
- Will have follow-on effort of shorter documents
- A Higgins paper, published under the EPL, with copyright by individual contributors.
- Goal
- Make Higgins More digestable. To educate people to a solution
- Outline
- Clarify the Audience (Why does he reader care)
- Target Audience - Persons who have no previous background in Higgins, who need something between the home pages and the technical details.
- Decision makers - business managers (CIO, CTO's and privacy/policy people).
- Not for Joe the plumber.
- Audience orientation There are perspectives - both consumer and enterprise space. (There is tension between user-centric and Enterprise....)
- See Paul blog on user-centric. Also Blakley's relationship stuff and Dave Kearns' blog.
- From the consumer point of view
- Enterprise point of view (may come in front door and or back door)
- Target Audience - Persons who have no previous background in Higgins, who need something between the home pages and the technical details.
- What are the problems we are trying to solve?
- Use a consistently themed story (as per advice of that book.) through out the paper
- Paul with consumer perspective problems
- Mary with enterprise perspective problems
- History of the technology of related efforts, what are their limitations, and what is there current status. (What are the things out there that need to be considered to provide context. Venn of Identity Diagram (Eve M.)
- Passport, why it "failed"
- Liberty
- Lid..
- OpenID (high level) (Phishing issue...)
- Higgins Technology deeper dive (issue two doors (Higgins client and Higgins Server - yes or 3 doors?)
- Positioning
- Higgins problem statement.
- World will stay heterogeneous or (not plausible or possible to have one thing.)
- Need to avoid single vendor lock-in
- Positioning
- Higgins point of view - Higgins "answer" - design center - What is Higgins?
- Works with open source and closed source
- Provides a set of abstractions for identity and data that are plugable
- Higgins point of view - Higgins "answer" - design center - What is Higgins?
- Architecture (Extensible, pluggable (Eclipse values), yet multi-platform....)
- Selectors
- Web Services
- IdAS - very special service
- CP's
- Implementation
- Deployment use case(s) to make this concrete Using a consistent story.
- Architecture (Extensible, pluggable (Eclipse values), yet multi-platform....)
- So what does this mean? (Did it solve the problems?) Where do we see things going.
- Conclusions /next Steps
>>>>>>>>>>>>>>>>>>>>
- Obvious questions that need to be answered somewhere...
- CardSpace and Higgins interoperability
- It is not able