Standards Committee Teleconference 2008 07 02 - Revision history

Joe.andrieu: /* Notes */

2008-07-02T18:25:52Z

Notes

← Older revision		Revision as of 18:25, 2 July 2008
Line 67:		Line 67:

	Users need some sort of agent, acting only on user impulse, on their behalf. That impulse may be provided at policy provision, but was also need to be aware of blanket policies that actually presume an impulse.		Users need some sort of agent, acting only on user impulse, on their behalf. That impulse may be provided at policy provision, but was also need to be aware of blanket policies that actually presume an impulse.

			===Workshop Planning===
			#PAM intro
			#PAM working session on One Night Stands
			#RelButton standards track work
			#Policy stuff (building on Asa's PAM policy work) [optional]
			##User-driven verses vendor-specified
			##Technical
			##Legal

	===Future Agenda Topics===		===Future Agenda Topics===

Joe.andrieu: /* One Night Stands */

2008-07-02T18:14:08Z

One Night Stands

← Older revision		Revision as of 18:14, 2 July 2008
Line 38:		Line 38:

	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.		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.

			Perception: because users have login-lockin, they'll come back more often.

			Eve: In the world of paper catalogs, I get sent offers. I can look at them if I want, and typcially will order by phone, instead of online. I tell them what I want... and they ask for the number from the catalog, which is then used to pull up my record in their system. That is easier than going online where you have username/password issues.

			Joe: but that's not really a one-night-stand. They've been courting you for a while. They have your address, which you probably gave to them or gave to another catalog company. And once you order, they have long term retention.

			But from a user perception, it almost feels like it. Simple, unobtrusive. In the mail order catalog system, where the buyer calls, they have made it as easy as possible to provision the data record to give the buyer what they want.

			We should be able to show up at Staples.com, and in one step, have them automatically get the data they need to make a perfect transaction (my address, billing preferences, etc.). And have that be data-protected, privacy-safe, etc.

			Goal: enable a first-time transaction to be just as efficient as a long term relationships.
			Side effect: The vendor doesn't have to keep the data.

			Requirement: ease of high-level provisioning.

			Non-repudiation?

			Especially in the one-night-stand case, where people would like prove about data persistence, propagation, etc. Receipts of that sort is a hard problem. It should be possible to assert a policy requesting an explicit statement/assertion/representation by the vendor that they adhere to my data retention policies.

			MySpace is doing this, of a sort, with their Data Availability initiative. That is a blanket TOS for all vendors, across all users.

			Formal assertion of de-provisioning of the data.

			Perhaps the real challenge is getting the policy agreement in place before users give away all their data. Because once the data release is normal, it will be hard to change vendor and user behavior.

			User selected policy. If we had the PAM in place, we still couldn't use it. It wouldn't matter what policy we assert, because we /still/ have to give Amazon our address.

			Users need some sort of agent, acting only on user impulse, on their behalf. That impulse may be provided at policy provision, but was also need to be aware of blanket policies that actually presume an impulse.

	===Future Agenda Topics===		===Future Agenda Topics===

Joe.andrieu: /* Notes */

2008-07-02T17:38:28Z

Notes

@@ Line 27: / Line 27: @@
 ==Notes==
 ===Future Agenda Topics===
 #Discuss the distinctions between a Service Endpoint and a Service Manager.

Joe.andrieu: /* Notes */

2008-07-02T17:19:30Z

Notes

← Older revision		Revision as of 17:19, 2 July 2008
Line 27:		Line 27:

	==Notes==		==Notes==
			===Future Agenda Topics===
			#Discuss the distinctions between a Service Endpoint and a Service Manager.

	==Action Items==		==Action Items==

Joe.andrieu: /* Agenda */

2008-07-02T17:19:11Z

Agenda

← Older revision		Revision as of 17:19, 2 July 2008
Line 23:		Line 23:
	#Gnip anyone?		#Gnip anyone?
	#Discuss the differences between one-night-stands and long term relationships with service providers and vendors.		#Discuss the differences between one-night-stands and long term relationships with service providers and vendors.
	~~#Discuss the distinctions between a Service Endpoint and a Service Manager.~~
	#Planning for VRM Workshop		#Planning for VRM Workshop
	#Review Action Items		#Review Action Items

Joe.andrieu: /* Attendees */

2008-07-02T17:17:51Z

Attendees

← Older revision		Revision as of 17:17, 2 July 2008
Line 8:		Line 8:
	==Attendees==		==Attendees==
	* Joe Andrieu		* Joe Andrieu
			* Eve Maler
			* Drummond Reed

	==Previous Action Items==		==Previous Action Items==

Joe.andrieu: /* Agenda */

2008-07-02T16:51:39Z

Agenda

← Older revision		Revision as of 16:51, 2 July 2008
Line 19:		Line 19:
	#Set Agenda		#Set Agenda
	#Review previous Action Items		#Review previous Action Items
			#Gnip anyone?
	#Discuss the differences between one-night-stands and long term relationships with service providers and vendors.		#Discuss the differences between one-night-stands and long term relationships with service providers and vendors.
	#Discuss the distinctions between a Service Endpoint and a Service Manager.		#Discuss the distinctions between a Service Endpoint and a Service Manager.

Joe.andrieu: pre-meeting draft

2008-07-02T16:49:18Z

pre-meeting draft

New page

==Standards Committee Teleconference Call Notes==
Drafted by Joe Andrieu, July 2, 2008

==Other Calls==
[[Category:Standards Committee Teleconferences]]
[[:Category:Standards Committee Teleconferences]]

==Attendees==
* Joe Andrieu

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

==Agenda==
#Set Agenda
#Review previous Action Items
#Discuss the differences between one-night-stands and long term relationships with service providers and vendors.
#Discuss the distinctions between a Service Endpoint and a Service Manager.
#Planning for VRM Workshop
#Review Action Items

==Notes==
==Action Items==

==Next Meeting==
Face to face at the VRM 2008 Workshop
[[Standards Committee Teleconference 2008 07 30]]