Standards Committee Teleconference 2008 07 02: Difference between revisions

From Project VRM
Jump to navigation Jump to search
Line 27: Line 27:


==Notes==
==Notes==
===Gnip===
Interesting. May be useful for personal datastore/data propagation. http://blog.gnipcentral.com
===One Night Stands===
All the power of long term identity-based relationships, but just for NOW, with no strings attached.
Staples.com requires a username/password for purchase, so that return uses are easier.
But that is lame. Why create an identity just so the /return/ is easier?
If we can provision the current fresh data on-the-fly, we'll have /more/ not less relationships, each of which is potentially ephemeral because there's no login-lockin.
===Future Agenda Topics===
===Future Agenda Topics===
#Discuss the distinctions between a Service Endpoint and a Service Manager.
#Discuss the distinctions between a Service Endpoint and a Service Manager.

Revision as of 12:38, 2 July 2008

Standards Committee Teleconference Call Notes

Drafted by Joe Andrieu, July 2, 2008

Other Calls

Category:Standards Committee Teleconferences

Attendees

  • Joe Andrieu
  • Eve Maler
  • Drummond Reed

Previous Action Items

  1. One Night Stand Use Cases - Eve - Before July 2
  2. Flower Power Scenario Diagrams - Asa - Before July 2
  3. Write up notes from call into wiki - Joe - By Monday
  4. Send blog post seeds to Drummond re: r-cards - Joe - Today
  5. Blog about current state of r-cards - Drummond - Next Week

Agenda

  1. Set Agenda
  2. Review previous Action Items
  3. Gnip anyone?
  4. Discuss the differences between one-night-stands and long term relationships with service providers and vendors.
  5. Planning for VRM Workshop
  6. Review Action Items

Notes

Gnip

Interesting. May be useful for personal datastore/data propagation. http://blog.gnipcentral.com

One Night Stands

All the power of long term identity-based relationships, but just for NOW, with no strings attached.

Staples.com requires a username/password for purchase, so that return uses are easier.

But that is lame. Why create an identity just so the /return/ is easier?

If we can provision the current fresh data on-the-fly, we'll have /more/ not less relationships, each of which is potentially ephemeral because there's no login-lockin.

Future Agenda Topics

  1. Discuss the distinctions between a Service Endpoint and a Service Manager.

Action Items

Next Meeting

Face to face at the VRM 2008 Workshop Standards Committee Teleconference 2008 07 30

Retrieved from "http://cyber.harvard.edu/projectvrm/?title=Standards_Committee_Teleconference_2008_07_02&oldid=2816"