Standards Committee Teleconference 2008 06 04: Difference between revisions
Joe.andrieu (talk | contribs) (first draft, with proposed agenda) |
Joe.andrieu (talk | contribs) (→R-Card) |
||
(5 intermediate revisions by the same user not shown) | |||
Line 8: | Line 8: | ||
==Attendees== | ==Attendees== | ||
* Joe Andrieu | * Joe Andrieu | ||
* Iain Henderson | |||
* Asa Hardcastle | |||
* Eva Maler | |||
==Previous Action Items== | ==Previous Action Items== | ||
Line 21: | Line 24: | ||
#PAM Next Steps (especially re: July) | #PAM Next Steps (especially re: July) | ||
#Action Items | #Action Items | ||
==Notes== | |||
===Action Items=== | |||
Asa got his done real quick. Joe's was a bit late (late last night). Iain hopes to get his done this week. Will be an action item this week. | |||
===Asa's Diagrams=== | |||
Asa set out to map out the roles fit together and reduced and simplified to clarify the core architecture. | |||
The UPS delivery use case is enabled by a /different/ delivery service. So that a vendor requesting "an address" may be really asking "how do I deliver to you?", which is really discovery of the delivery service. | |||
===R-Card=== | |||
Identity mash up with r-card creation as permission provisioning within selector? | |||
Multiple end-points at the claim level is a design goal. | |||
Also need to provide an explicit interface for managing permissions and data at times other than login. Login is conceptually an easy point for a service provider to ask for claims, but it isn't really the ideal place to manage claims. You don't want to have to log in to all of your vendors to manage their permissions. Note that the Liberty People Service is exactly that: an interface for managing permissions at the individual /and/ group level. | |||
==Action Items== | ==Action Items== | ||
# Customer journey for PAM on wiki -- Iain -- by next Friday | |||
# Queue up email post on r-card blog -- Joe -- by Friday | |||
# Blog post follow on -- Eve -- by Monday | |||
# PAM review & diagram integration meeting -- Asa -- by next Friday | |||
==Next Meeting== | ==Next Meeting== | ||
[[Standards Committee Teleconference 2008 06 18]] | [[Standards Committee Teleconference 2008 06 18]] |
Latest revision as of 13:34, 4 June 2008
Standards Committee Teleconference Call Notes
Drafted by Joe Andrieu, June 4, 2008
Other Calls
Category:Standards Committee Teleconferences
Attendees
- Joe Andrieu
- Iain Henderson
- Asa Hardcastle
- Eva Maler
Previous Action Items
- AddressOwner change on PAM Site â Joe by Monday 5/26
- Customer Journey on Wiki â Iain by Monday 5/26
- F irst draft diagram â Asa by Monday 5/26
Agenda
- Set Agenda
- Review Action Items
- Asa's diagrams
- R-card
- PAM Next Steps (especially re: July)
- Action Items
Notes
Action Items
Asa got his done real quick. Joe's was a bit late (late last night). Iain hopes to get his done this week. Will be an action item this week.
Asa's Diagrams
Asa set out to map out the roles fit together and reduced and simplified to clarify the core architecture.
The UPS delivery use case is enabled by a /different/ delivery service. So that a vendor requesting "an address" may be really asking "how do I deliver to you?", which is really discovery of the delivery service.
R-Card
Identity mash up with r-card creation as permission provisioning within selector?
Multiple end-points at the claim level is a design goal.
Also need to provide an explicit interface for managing permissions and data at times other than login. Login is conceptually an easy point for a service provider to ask for claims, but it isn't really the ideal place to manage claims. You don't want to have to log in to all of your vendors to manage their permissions. Note that the Liberty People Service is exactly that: an interface for managing permissions at the individual /and/ group level.
Action Items
- Customer journey for PAM on wiki -- Iain -- by next Friday
- Queue up email post on r-card blog -- Joe -- by Friday
- Blog post follow on -- Eve -- by Monday
- PAM review & diagram integration meeting -- Asa -- by next Friday