event-consolidation - Revision history

Tantek: /* see also */ unified rsvp

2009-07-27T01:55:44Z

Tantek: revise problem statement to include user-centric/chosen design for reflection per recently noted challenge (good point), add privacy section

2008-01-11T21:43:36Z

revise problem statement to include user-centric/chosen design for reflection per recently noted challenge (good point), add privacy section

← Older revision		Revision as of 21:43, 11 January 2008
Line 6:		Line 6:
	Why do I have to RSVP on three sites for the same event?		Why do I have to RSVP on three sites for the same event?

	Why can't I just RSVP once and have that ~~RSVP~~ reflected in all the other systems?		Why can't I just RSVP once and have that action automatically reflected on all the other event systems that I want to RSVP to?

	== examples ==		== examples ==
Line 96:		Line 96:

	== challenges ==		== challenges ==
			=== privacy ===
	* '''private events'''. How do you consolidate fully private events? Even assuming multiple event representations, each having URLs which each point to each other, what type of protocols are needed both by the sites themselves to consolidate with the other site(s)? What additional (if any) protocols are needed for a third party site (or a desktop application) to consolidate events across event sites?		* '''private events'''. How do you consolidate fully private events? Even assuming multiple event representations, each having URLs which each point to each other, what type of protocols are needed both by the sites themselves to consolidate with the other site(s)? What additional (if any) protocols are needed for a third party site (or a desktop application) to consolidate events across event sites?
	* How do you have the RSVP show on some, but not all, of the included sites (for privacy purposes, say)?		* How do you have the RSVP show on some, but not all, of the included sites (for privacy purposes, say)?

AndyMabbett: rv self and add as challenge

2008-01-11T10:49:26Z

rv self and add as challenge

← Older revision		Revision as of 10:49, 11 January 2008
Line 4:		Line 4:

	== problem statement ==		== problem statement ==

	Why do I have to RSVP on three sites for the same event?		Why do I have to RSVP on three sites for the same event?

	Why can't I just RSVP once and have that RSVP ~~(optionally)~~ reflected in all the other systems?		Why can't I just RSVP once and have that RSVP reflected in all the other systems?

	== examples ==		== examples ==
Line 98:		Line 97:
	== challenges ==		== challenges ==
	* '''private events'''. How do you consolidate fully private events? Even assuming multiple event representations, each having URLs which each point to each other, what type of protocols are needed both by the sites themselves to consolidate with the other site(s)? What additional (if any) protocols are needed for a third party site (or a desktop application) to consolidate events across event sites?		* '''private events'''. How do you consolidate fully private events? Even assuming multiple event representations, each having URLs which each point to each other, what type of protocols are needed both by the sites themselves to consolidate with the other site(s)? What additional (if any) protocols are needed for a third party site (or a desktop application) to consolidate events across event sites?
			* How do you have the RSVP show on some, but not all, of the included sites (for privacy purposes, say)?

	== see also ==		== see also ==

AndyMabbett: /* problem statement */ "optionally" (for privacy purposes)

2008-01-11T10:46:28Z

problem statement: "optionally" (for privacy purposes)

← Older revision		Revision as of 10:46, 11 January 2008
Line 4:		Line 4:

	== problem statement ==		== problem statement ==

	Why do I have to RSVP on three sites for the same event?		Why do I have to RSVP on three sites for the same event?

	Why can't I just RSVP once and have that RSVP reflected in all the other systems?		Why can't I just RSVP once and have that RSVP (optionally) reflected in all the other systems?

	== examples ==		== examples ==

Tantek: add an event postings cross-linking example

2008-01-11T09:45:51Z

add an event postings cross-linking example

← Older revision		Revision as of 09:45, 11 January 2008
Line 10:		Line 10:
	== examples ==		== examples ==
	These are real world examples of existing events with multiple representations that could benefit from event consolidation.		These are real world examples of existing events with multiple representations that could benefit from event consolidation.

			=== photomatt bday party 2008 ===
			Example of event posted to multiple sites, with some cross-linkage.
			* [http://upcoming.yahoo.com/event/404112/ Upcoming]
			** viewable without login
			** marked up with [[hCalendar]]
			** links to Facebook version of same event
			* [http://pownce.com/agendacide/notes/1171601/ Pownce]
			** viewable without login
			** marked up with [[hCalendar]]
			** links to Upcoming and Facebook versions of same event
			* [http://www.facebook.com/event.php?eid=7081976551 Facebook]
			** requires login to view

	=== laughing squid pre nye party 2007 ===		=== laughing squid pre nye party 2007 ===
			Example of an event posted to multiple sites, with star-network linkage from event sites to a blog post, and from that blog post to each of the event sites.
	* [http://laughingsquid.com/laughing-squids-last-minute-unholiday-party/ Scott's blog post]		* [http://laughingsquid.com/laughing-squids-last-minute-unholiday-party/ Scott's blog post]
	** viewable without login		** viewable without login
Line 27:		Line 41:

	=== satsifactory cupcakes and cocktails 2007 ===		=== satsifactory cupcakes and cocktails 2007 ===
			First event where event-consolidation problem was mentioned conceptually.
	"the Satisfactory's first weekly "Cupcakes & Cocktails" happy hour"		"the Satisfactory's first weekly "Cupcakes & Cocktails" happy hour"
	* [http://pownce.com/monstro/notes/261632/ Pownce]		* [http://pownce.com/monstro/notes/261632/ Pownce]

AndyMabbett: /* lazyweb */ grammar

2008-01-01T17:25:32Z

lazyweb: grammar

← Older revision		Revision as of 17:25, 1 January 2008
Line 46:		Line 46:
	This would allow any event site (or perhaps a smart desktop calendar app) to RSVP for you across such sites.		This would allow any event site (or perhaps a smart desktop calendar app) to RSVP for you across such sites.
	== lazyweb ==		== lazyweb ==
	We need a event posting / RSVPing plugins for blogging tools:		We need event posting / RSVPing plugins for blogging tools:
	* Wordpress		* Wordpress
	* MovableType		* MovableType
Line 53:		Line 53:
	An event posting plugin would simply:		An event posting plugin would simply:

	# add just a few more fields (see the differences in how [http://pownce.com Pownce] lets you post a simple note ~~vs.~~ an event note) to let ~~user's~~ easily post info about an event, including URLs to representations of the event on other event posting sites.		# add just a few more fields (see the differences between how [http://pownce.com Pownce] lets you post a simple note and an event note) to let users easily post info about an event, including URLs to representations of the event on other event posting sites.
	# publish the information in a blog post on your blog with hCalendar (and download/subscribe links using the [http://feeds.technorati.com/events/ Technorati Events Feed service]).		# publish the information in a blog post on your blog with hCalendar (and download/subscribe links using the [http://feeds.technorati.com/events/ Technorati Events Feed service]).
	# modify the commenting user-interface on such "event" posts to add an "RSVP" field (again, note how Pownce does comments on event notes in contrast to simple notes).		# modify the commenting user-interface on such "event" posts to add an "RSVP" field (again, note how Pownce does comments on event notes in contrast to simple notes).

Tantek: added challenges section for private events

2007-12-31T22:34:56Z

added challenges section for private events

← Older revision		Revision as of 22:34, 31 December 2007
Line 3:		Line 3:
	Just as [[identity-consolidation]] solves the problem of how do I connect all these profiles that all mean "me", '''event consolidation''' is a solution to the problem of how do I connect all these different representations of the same event, across blogs, event posting systems, and perhaps the site for the event itself.		Just as [[identity-consolidation]] solves the problem of how do I connect all these profiles that all mean "me", '''event consolidation''' is a solution to the problem of how do I connect all these different representations of the same event, across blogs, event posting systems, and perhaps the site for the event itself.

	~~Or to put it another way, why~~ do I have to RSVP on three sites for the same event? Why can't I just RSVP once and have that RSVP reflected in all the other systems?		== problem statement ==
			Why do I have to RSVP on three sites for the same event?

			Why can't I just RSVP once and have that RSVP reflected in all the other systems?

	== examples ==		== examples ==
Line 76:		Line 79:
	* (c) publish the "primary" URL as a "uid" in the [[hCalendar]] for the event		* (c) publish the "primary" URL as a "uid" in the [[hCalendar]] for the event
	* (d) support [[OAuth]] access to the RSVP to events on your behalf		* (d) support [[OAuth]] access to the RSVP to events on your behalf

			== challenges ==
			* '''private events'''. How do you consolidate fully private events? Even assuming multiple event representations, each having URLs which each point to each other, what type of protocols are needed both by the sites themselves to consolidate with the other site(s)? What additional (if any) protocols are needed for a third party site (or a desktop application) to consolidate events across event sites?

	== see also ==		== see also ==

Tantek: added second example, and quotes noting need for event consolidation

2007-12-29T16:45:27Z

added second example, and quotes noting need for event consolidation

← Older revision		Revision as of 16:45, 29 December 2007
Line 17:		Line 17:
	** viewable without login		** viewable without login
	** marked up with [[hCalendar]]		** marked up with [[hCalendar]]
			** note Tara's comment: "LOL. Replied in 3 places! I think we need an OpenID solution to these puppies!"
	* [http://www.facebook.com/event.php?eid=19966532768 Facebook]		* [http://www.facebook.com/event.php?eid=19966532768 Facebook]
	** requires login to view		** requires login to view
Line 22:		Line 23:
	In this case, note that Scott links from each event posting to his blog post, which then links to all three event postings. If Scott were markup the event in his blog post using hCalendar (including all three event posting URLs), it would be theoretically possible to RSVP to his blog post (assuming his blogging software supported RSVPing to event posts), and have that same code route you to the other event systems and auto-RSVP for your there.		In this case, note that Scott links from each event posting to his blog post, which then links to all three event postings. If Scott were markup the event in his blog post using hCalendar (including all three event posting URLs), it would be theoretically possible to RSVP to his blog post (assuming his blogging software supported RSVPing to event posts), and have that same code route you to the other event systems and auto-RSVP for your there.

	== brainstorm ==		=== satsifactory cupcakes and cocktails 2007 ===
			"the Satisfactory's first weekly "Cupcakes & Cocktails" happy hour"
			* [http://pownce.com/monstro/notes/261632/ Pownce]
			** requires login to view
			** marked up with [[hCalendar]]
			** note Lane's comment: "there are far too many places to post events these days. need some sort of application to bundle up all of the rsvps in one place."
			* Facebook (URL unknown)
			* Upcoming (event implied by commentary in Pownce event, URL unknown)

			This was perhaps the first instance where I (Tantek) saw a call for event consolidation by concept (" too many places to post events ... need ... to bundle up all of the rsvps in one place ").

			== recipes brainstorm ==
	Any site that permits the user to post an event should:		Any site that permits the user to post an event should:
	* (a) let you post one or more URLs for the event,		* (a) let you post one or more URLs for the event,
Line 30:		Line 42:

	This would allow any event site (or perhaps a smart desktop calendar app) to RSVP for you across such sites.		This would allow any event site (or perhaps a smart desktop calendar app) to RSVP for you across such sites.

	== lazyweb ==		== lazyweb ==
	We need a event posting / RSVPing plugins for blogging tools:		We need a event posting / RSVPing plugins for blogging tools:

Tantek: drafted

2007-12-29T16:19:04Z

drafted

New page

<h1>event consolidation</h1>
{{TOC-right}}
Just as [[identity-consolidation]] solves the problem of how do I connect all these profiles that all mean "me", '''event consolidation''' is a solution to the problem of how do I connect all these different representations of the same event, across blogs, event posting systems, and perhaps the site for the event itself.

Or to put it another way, why do I have to RSVP on three sites for the same event? Why can't I just RSVP once and have that RSVP reflected in all the other systems?

== examples ==
These are real world examples of existing events with multiple representations that could benefit from event consolidation.

=== laughing squid pre nye party 2007 ===
* [http://laughingsquid.com/laughing-squids-last-minute-unholiday-party/ Scott's blog post]
** viewable without login
* [http://upcoming.yahoo.com/event/395300/ Upcoming]
** viewable without login
** marked up with [[hCalendar]] including link to Scott's post.
* [http://pownce.com/laughingsquid/notes/1130070/ Pownce]
** viewable without login
** marked up with [[hCalendar]]
* [http://www.facebook.com/event.php?eid=19966532768 Facebook]
** requires login to view

In this case, note that Scott links from each event posting to his blog post, which then links to all three event postings. If Scott were markup the event in his blog post using hCalendar (including all three event posting URLs), it would be theoretically possible to RSVP to his blog post (assuming his blogging software supported RSVPing to event posts), and have that same code route you to the other event systems and auto-RSVP for your there.

== brainstorm ==
Any site that permits the user to post an event should:
* (a) let you post one or more URLs for the event,
* (b) let you pick the "primary" URL for the event,
* (c) published the event info in [[hCalendar]], including the "primary" URL as a <code>uid</code> property value.
* (d) support [[OAuth]] access to RSVP to events on your behalf

This would allow any event site (or perhaps a smart desktop calendar app) to RSVP for you across such sites.

== lazyweb ==
We need a event posting / RSVPing plugins for blogging tools:
* Wordpress
* MovableType
* ... etc.

An event posting plugin would simply:

# add just a few more fields (see the differences in how [http://pownce.com Pownce] lets you post a simple note vs. an event note) to let user's easily post info about an event, including URLs to representations of the event on other event posting sites.
# publish the information in a blog post on your blog with hCalendar (and download/subscribe links using the [http://feeds.technorati.com/events/ Technorati Events Feed service]).
# modify the commenting user-interface on such "event" posts to add an "RSVP" field (again, note how Pownce does comments on event notes in contrast to simple notes).
# since the commenting system knows your URL (either via the form, [[hCard]] subscription/import, and/or [[OpenID]]), it can retrieve your [[identity-consolidation]] from that URL (e.g. your list of "Other Profiles" on your Pownce profile), and go to those systems that are among the set of other event posting sites noted in step 1, obtain access via [[OAuth]], and RSVP for you on your accounts on those other systems.
# if you update your RSVP, the plugin should propagate that update to the other systems as well.

== advocacy ==
What we need current event sites to do.
=== facebook ===
Let's start with please support hCalendar on event postings plus the ability to publish events publicly so that services can do some event consolidation without having to implement additional protocols. Add to that OAuth support for access to private events.

=== pownce ===
Pownce rocks because it already supports [[hCalendar]] and allows public events!
In addition it would be great if they:
* (a) let you post one or more URLs for the event
* (b) let you pick the "primary" URL for the event
* (c) publish the "primary" URL as a "uid" in the [[hCalendar]] for the event
* (d) support [[OAuth]] access to the RSVP to events on your behalf

=== upcoming ===
Upcoming rocks because it already supports [[hCalendar]] and defaults to public events!
In addition it would be great if they:
* (a) let you post more than one URL for an event
* (b) let you pick the "primary" URL for the event
* (c) publish the "primary" URL as a "uid" in the [[hCalendar]] for the event
* (d) support [[OAuth]] access to the RSVP to events on your behalf

== see also ==
* [[hCalendar]]
* [[identity-consolidation]]
* [[OAuth]]

← Older revision		Revision as of 01:55, 27 July 2009
Line 104:		Line 104:
	* [[identity-consolidation]]		* [[identity-consolidation]]
	* [[OAuth]]		* [[OAuth]]
			* [[unified-rsvp]]