May 2 2007 Meeting notes: Difference between revisions
(→Status) |
Joe.andrieu (talk | contribs) |
||
| Line 40: | Line 40: | ||
|Set up Jabber Host for conference calls||doc||no date||''new'' | |Set up Jabber Host for conference calls||doc||no date||''new'' | ||
|} | |} | ||
Unfortunately Doc won't be able to join us today. | Unfortunately Doc won't be able to join us today. | ||
| Line 61: | Line 59: | ||
Consider a use case where Alice is specifying the RFP, but Dad is paying for it. This is discussed on the [[Technology]] page. | Consider a use case where Alice is specifying the RFP, but Dad is paying for it. This is discussed on the [[Technology]] page. | ||
===Social Use Cases=== | |||
The thought of this term triggered some concerns about a data mining case. | |||
Think of gift registries. I'm a Bride or Groom. Where the good is registered in an identity-capable registry. Liberty's People Service enables this to allow access to the invited people without needing a unique account. The relationship specified by the Bride and confirmed upon login could be used by a VRM system to integrate this information, mapping the desires of the bride against, for example the budget constraints of a particular guest (assuming such constraint is also made available via a People Service for the guest). | |||
In an RFP, there are two different pieces of information: what I want and what I'm willing to pay. In a social application, those might be controlled by separate people. | |||
==Action Items== | ==Action Items== | ||
{| | {| | ||
Revision as of 12:58, 2 May 2007
Conference Call Notes
Drafted by Joe Andrieu, May 2, 2007
Previous Meeting Links
- February 8
- February 22
- Conference MP3
- No notes available
Attendees
(please update with last names & IM if you'd like a backchannel during the call...)
- Paul Madsen
- Keith Hopper on AIM: hopperomatic
- Ben Laurie
- Joe Andrieu on AIM: jpandrieu
- Leif Chastaine
- Dean Landsman On IRC: deanland On AIM: deanlandsman
- Britt Blaser
- Deborah Schulz
Status
| what | who | when | status |
| ---------- | ---------- | ---------- | ---------- |
| open id on wiki | david | no date | |
| static website development | doc, dean, joe, chris | no date | |
| group blog/RSS to wiki (venus) | doc | no date | up, but only one author |
| project VRM definition | doc | 1 week | still working on it |
| brainstorm Initiatives | all | ongoing | |
| Set up Jabber Host for conference calls | doc | no date | new |
Unfortunately Doc won't be able to join us today.
Joe: remind Dean about transcript.
Report from Brussels
Doc led a session at the Open Identity event last week. Britt took a look at how Liberty Alliance's architecture might help.
One foundation of VRM is the personal RFP, a way for individuals to express their buying desires in a way that vendors can respond directly. Britt sees a personal RFP as an aspect of a person's Identity. That would be put on the web so buyers could find them, analyze them, and discover with them a potential match for what they could provide me. At its basic, the WSF (web services framework) is a way to do just that: provide aspects of identity securely over the Internet.
Liberty Alliance is a standards body for federated identity and identity services.
VRM still needs to define and XML syntax for what this RFP looks like. Some sort of product number, useful meta-data, etc. Some way for users to describe what they want to buy, maximum price, timing on purchase, etc.
The web services is really about moving around that type of identity-centric document.
So, we have schemas that specify, for example, a calendar format that allows people to share calendar data through this framework.
Consider a use case where Alice is specifying the RFP, but Dad is paying for it. This is discussed on the Technology page.
Social Use Cases
The thought of this term triggered some concerns about a data mining case.
Think of gift registries. I'm a Bride or Groom. Where the good is registered in an identity-capable registry. Liberty's People Service enables this to allow access to the invited people without needing a unique account. The relationship specified by the Bride and confirmed upon login could be used by a VRM system to integrate this information, mapping the desires of the bride against, for example the budget constraints of a particular guest (assuming such constraint is also made available via a People Service for the guest).
In an RFP, there are two different pieces of information: what I want and what I'm willing to pay. In a social application, those might be controlled by separate people.
Action Items
| what | who | when | status |