rsvp-brainstorming - Revision history

Sebsel: added 'went' and 'did not go' semantics

2016-11-28T14:34:01Z

added 'went' and 'did not go' semantics

← Older revision		Revision as of 14:34, 28 November 2016
Line 57:		Line 57:
	* '''Maybe''' / might be going, there's some intent to attend		* '''Maybe''' / might be going, there's some intent to attend
	* '''Interested''' / interested - this appears to be distinct from Maybe. It's used by [http://plancast.com Plancast] and [http://lanyrd.com Lanyrd], which don't have explicit "Maybe" options, and yet people use it differently than "Maybe". It's used almost to collect or recommend events - like bookmarking/linkblogging. [http://facebook.com Facebook] allows you to similarly "Save" an event, e.g. http://aaronparecki.com/uploads/facebook-saved-event-20150209-225455.png		* '''Interested''' / interested - this appears to be distinct from Maybe. It's used by [http://plancast.com Plancast] and [http://lanyrd.com Lanyrd], which don't have explicit "Maybe" options, and yet people use it differently than "Maybe". It's used almost to collect or recommend events - like bookmarking/linkblogging. [http://facebook.com Facebook] allows you to similarly "Save" an event, e.g. http://aaronparecki.com/uploads/facebook-saved-event-20150209-225455.png

			Some other options may include past-tense forms of the above, more describing the action after the event took place.
			* '''Went'''
			* '''Did not go'''

	== proposals ==		== proposals ==

Tantek: Status: p-rsvp is now a draft property

2015-03-20T16:06:09Z

Status: p-rsvp is now a draft property

← Older revision		Revision as of 16:06, 20 March 2015
Line 60:		Line 60:
	== proposals ==		== proposals ==
	=== h-entry plus additions ===		=== h-entry plus additions ===
			Status: this proposal is now a [[h-entry#Draft_Properties\|draft property]] in h-entry.

	Just use [[h-entry]] with a few extra properties		Just use [[h-entry]] with a few extra properties

Tantek: link h-entry, rename tracking to interested, since "tracking" already means something different in web specs (e.g. tracking protection)

2015-03-20T15:47:03Z

link h-entry, rename tracking to interested, since "tracking" already means something different in web specs (e.g. tracking protection)

← Older revision		Revision as of 15:47, 20 March 2015
Line 56:		Line 56:
	* '''No''' / explicitly not going		* '''No''' / explicitly not going
	* '''Maybe''' / might be going, there's some intent to attend		* '''Maybe''' / might be going, there's some intent to attend
	* '''~~Tracking~~''' / interested - this appears to be distinct from Maybe. It's used by [http://plancast.com Plancast] and [http://lanyrd.com Lanyrd], which don't have explicit "Maybe" options, and yet people use it differently than "Maybe". It's used almost to collect or recommend events - like bookmarking/linkblogging. [http://facebook.com Facebook] allows you to similarly "Save" an event, e.g. http://aaronparecki.com/uploads/facebook-saved-event-20150209-225455.png		* '''Interested''' / interested - this appears to be distinct from Maybe. It's used by [http://plancast.com Plancast] and [http://lanyrd.com Lanyrd], which don't have explicit "Maybe" options, and yet people use it differently than "Maybe". It's used almost to collect or recommend events - like bookmarking/linkblogging. [http://facebook.com Facebook] allows you to similarly "Save" an event, e.g. http://aaronparecki.com/uploads/facebook-saved-event-20150209-225455.png

	== proposals ==		== proposals ==
	=== h-entry plus additions ===		=== h-entry plus additions ===
	Just use h-entry with a few extra properties		Just use [[h-entry]] with a few extra properties

	* h-entry		* h-entry
Line 69:		Line 69:
	** u-in-reply-to ([[rel-in-reply-to]]) link to the event post		** u-in-reply-to ([[rel-in-reply-to]]) link to the event post
	** '''p-rsvp''' (new, enum, use <data> element or [[value-class-pattern]])		** '''p-rsvp''' (new, enum, use <data> element or [[value-class-pattern]])
	*** "invited", "yes", "no", "maybe", "~~tracking~~", e.g. from the news feed example:		*** "invited", "yes", "no", "maybe", "interested", e.g. from the news feed example:
	*** <code><nowiki>... <data class="p-rsvp" value="yes">is going</data> to ...</nowiki></code>, or		*** <code><nowiki>... <data class="p-rsvp" value="yes">is going</data> to ...</nowiki></code>, or
	*** <code><nowiki>... <data class="p-rsvp" value="maybe">might go</data> to ...</nowiki></code>		*** <code><nowiki>... <data class="p-rsvp" value="maybe">might go</data> to ...</nowiki></code>
	*** <code><nowiki>... <data class="p-rsvp" value="no">unable to go</data> to ...</nowiki></code>		*** <code><nowiki>... <data class="p-rsvp" value="no">unable to go</data> to ...</nowiki></code>
	*** <code><nowiki>... <data class="p-rsvp" value="~~tracking~~">am tracking</data> ...</nowiki></code>		*** <code><nowiki>... <data class="p-rsvp" value="interested">am interested/tracking/watching</data> ...</nowiki></code>

Tantek: note FB lets you save the event with screenshot

2015-02-10T07:19:43Z

note FB lets you save the event with screenshot

← Older revision		Revision as of 07:19, 10 February 2015
Line 56:		Line 56:
	* '''No''' / explicitly not going		* '''No''' / explicitly not going
	* '''Maybe''' / might be going, there's some intent to attend		* '''Maybe''' / might be going, there's some intent to attend
	* '''Tracking''' / interested - this appears to be distinct from Maybe. It's used by [http://plancast.com Plancast] and [http://lanyrd.com Lanyrd], which don't have explicit "Maybe" options, and yet people use it differently than "Maybe". It's used almost to collect or recommend events - like bookmarking/linkblogging.		* '''Tracking''' / interested - this appears to be distinct from Maybe. It's used by [http://plancast.com Plancast] and [http://lanyrd.com Lanyrd], which don't have explicit "Maybe" options, and yet people use it differently than "Maybe". It's used almost to collect or recommend events - like bookmarking/linkblogging. [http://facebook.com Facebook] allows you to similarly "Save" an event, e.g. http://aaronparecki.com/uploads/facebook-saved-event-20150209-225455.png

	== proposals ==		== proposals ==

Tantek: /* h-entry plus additions */ provide explicit no and tracking examples instead of etc.

2013-09-21T14:44:04Z

h-entry plus additions: provide explicit no and tracking examples instead of etc.

← Older revision		Revision as of 14:44, 21 September 2013
Line 72:		Line 72:
	*** <code><nowiki>... <data class="p-rsvp" value="yes">is going</data> to ...</nowiki></code>, or		*** <code><nowiki>... <data class="p-rsvp" value="yes">is going</data> to ...</nowiki></code>, or
	*** <code><nowiki>... <data class="p-rsvp" value="maybe">might go</data> to ...</nowiki></code>		*** <code><nowiki>... <data class="p-rsvp" value="maybe">might go</data> to ...</nowiki></code>
	*** ~~etc~~.		*** <code><nowiki>... <data class="p-rsvp" value="no">unable to go</data> to ...</nowiki></code>
			*** <code><nowiki>... <data class="p-rsvp" value="tracking">am tracking</data> ...</nowiki></code>

Tantek: subhead discussion

2013-05-09T18:11:48Z

subhead discussion

← Older revision		Revision as of 18:11, 9 May 2013
Line 83:		Line 83:
	Which leaves the only really new property '''p-rsvp'''.		Which leaves the only really new property '''p-rsvp'''.

			==== h-entry plus additions discussion ====
	<div class="discussion">		<div class="discussion">
	* Is it worth introducing a separate/new '''h-rsvp''' top level microformat just for RSVPs for one new property?		* Is it worth introducing a separate/new '''h-rsvp''' top level microformat just for RSVPs for one new property?

Tantek: reformat questions as discussion, note perhaps it's ok to annotate with h-as-rsvp

2013-05-09T15:15:39Z

reformat questions as discussion, note perhaps it's ok to annotate with h-as-rsvp

← Older revision		Revision as of 15:15, 9 May 2013
Line 83:		Line 83:
	Which leaves the only really new property '''p-rsvp'''.		Which leaves the only really new property '''p-rsvp'''.

	Is it worth introducing a separate/new '''h-rsvp''' top level microformat just for RSVPs for one new property?		<div class="discussion">
			* Is it worth introducing a separate/new '''h-rsvp''' top level microformat just for RSVPs for one new property?
	Or should we simply add '''p-rsvp''' as an optional property to h-entry?		** I'm not sure it is worth introducing h-rsvp just for one new property. If further brainstorming shows RSVPs to need more than just one new property, we can reconsider. - [[User:Tantek\|Tantek]]
			* Or should we simply add '''p-rsvp''' as an optional property to h-entry?
	I'm leaning towards the latter, since that is fewer additions, and seems simpler. ~~I'm not sure it~~ is ~~worth introducing~~ h-~~rsvp just~~ for ~~one new property.~~		** I'm leaning towards the latter, since that is fewer additions, and seems simpler. - [[User:Tantek\|Tantek]]
			* Consider <code>h-as-rsvp</code>
	~~If further brainstorming shows RSVPs~~ to ~~need more than just one new property, we can reconsider~~.		** Since RSVP is also a concept in [[activity-streams]], and there has been some practice in the wild of annotating h-entries along with their activity stream object types (e.g. <code>h-as-note</code>, <code>h-as-article</code>, using -as- like a vendor prefix for activity streams concepts), it might be reasonable to annotate RSVP <code>h-entry</code> elements with <code>h-as-rsvp</code> as well. - [[User:Tantek\|Tantek]]
			</div>
	[[User:Tantek\|Tantek]] ~~16:05, 8 May 2013 (UTC)~~

Tantek: /* analysis */ -]

2013-05-08T16:08:23Z

analysis: -]

← Older revision		Revision as of 16:08, 8 May 2013
Line 40:		Line 40:
	*** p-attendee h-card (for icons of other attendees, with alt text for names, and linked to their profiles)		*** p-attendee h-card (for icons of other attendees, with alt text for names, and linked to their profiles)

	The "action links" would be better represented as [http://indiewebcamp.com/webactions web actions]]:		The "action links" would be better represented as [http://indiewebcamp.com/webactions web actions]:
	* "Join"		* "Join"
	* "Like" (favorite, bookmark)		* "Like" (favorite, bookmark)

Tantek: lc

2013-05-08T16:06:58Z

← Older revision		Revision as of 16:06, 8 May 2013
Line 7:		Line 7:
	* [[rsvp-brainstorming]]		* [[rsvp-brainstorming]]

	== ~~Analysis~~ ==		== analysis ==
	From the [[rsvp-examples#News_feed_RSVP\|news feed RSVP post example]] we know that event RSVP posts contain the following:		From the [[rsvp-examples#News_feed_RSVP\|news feed RSVP post example]] we know that event RSVP posts contain the following:

Line 58:		Line 58:
	* '''Tracking''' / interested - this appears to be distinct from Maybe. It's used by [http://plancast.com Plancast] and [http://lanyrd.com Lanyrd], which don't have explicit "Maybe" options, and yet people use it differently than "Maybe". It's used almost to collect or recommend events - like bookmarking/linkblogging.		* '''Tracking''' / interested - this appears to be distinct from Maybe. It's used by [http://plancast.com Plancast] and [http://lanyrd.com Lanyrd], which don't have explicit "Maybe" options, and yet people use it differently than "Maybe". It's used almost to collect or recommend events - like bookmarking/linkblogging.

	== ~~Proposals~~ ==		== proposals ==
	=== h-entry plus additions ===		=== h-entry plus additions ===
	Just use h-entry with a few extra properties		Just use h-entry with a few extra properties

Tantek: analysis and proposal

2013-05-08T16:05:51Z

analysis and proposal

New page

{{stub}}

This is part of an effort to define an [[rsvp]] microformat for marking up rsvp [[notes]] posted on independent sites about or [[in-reply-to]] an [[event]] [[post]]. Per the microformats [[process]]:

* [[rsvp-examples]]
* [[rsvp-formats]]
* [[rsvp-brainstorming]]

== Analysis ==
From the [[rsvp-examples#News_feed_RSVP|news feed RSVP post example]] we know that event RSVP posts contain the following:

* attendee (photo, name, both linked to profile)
* RSVP status ("is going to")
* link to event post
* nested event post with:
** photo
** name (also linked)
** start date and time
** location (including venue, city/locality, state/region)
** icons of other attendees (seven, likely most recent other RSVPs)
** number of attendees
** "Join" link (posts an RSVP to the event)
* web actions: "like", "comment", "share"
* time of RSVP
** hyperlinked to permalink of RSVP post
* location when RSVP posted (little globe icon)

Much of this can be built from [[h-entry]] (for the RSVP), and [[h-event]] (for the nested event).

* h-entry
** p-author h-card (for attendee photo, name, hyperlink)
** dt-published (time of RSVP)
** u-url (permalink to RSVP post)
** p-location (re-use from h-event or p-geo h-geo, for pure latlong of where posted)
** h-event (should this be on a specific property?)
*** u-photo (re-use from h-card)
*** p-name
*** dt-start (presumably optional dt-end)
*** p-location h-card (for venue, locality, region)
*** p-attendee h-card (for icons of other attendees, with alt text for names, and linked to their profiles)

The "action links" would be better represented as [http://indiewebcamp.com/webactions web actions]]:
* "Join"
* "Like" (favorite, bookmark)
* "Comment" (post a comment, reply)
* "Share" (post)

The only new things that an RSVP seems to need are:
* RSVP status ("is going to" from the example), which has been previously brainstormed here: [[hcalendar-brainstorming#participation_status|hCalendar brainstorming: participation status]]
* and which event is this regarding - which seems very much akin to [[in-reply-to]]
** an RSVP is just a reply to an event post, similar to a comment on a post

For the RSVP options it seem there are five distinct semantics
* '''Invited''' / has been invited, has not responded explicitly. You wouldn't post this yourself would you? Or do people post "I've been invited to ..." posts? Possibly. Examples?
* '''Yes''' / going
* '''No''' / explicitly not going
* '''Maybe''' / might be going, there's some intent to attend
* '''Tracking''' / interested - this appears to be distinct from Maybe. It's used by [http://plancast.com Plancast] and [http://lanyrd.com Lanyrd], which don't have explicit "Maybe" options, and yet people use it differently than "Maybe". It's used almost to collect or recommend events - like bookmarking/linkblogging.

== Proposals ==
=== h-entry plus additions ===
Just use h-entry with a few extra properties

* h-entry
** p-author h-card (for attendee photo, name, hyperlink)
** dt-published (time of RSVP)
** u-url (permalink to RSVP post)
** ''p-location'' (re-use from h-event, substructure with h-card/h-adr/h-geo as needed)
** u-in-reply-to ([[rel-in-reply-to]]) link to the event post
** '''p-rsvp''' (new, enum, use <data> element or [[value-class-pattern]])
*** "invited", "yes", "no", "maybe", "tracking", e.g. from the news feed example:
*** <code><nowiki>... <data class="p-rsvp" value="yes">is going</data> to ...</nowiki></code>, or
*** <code><nowiki>... <data class="p-rsvp" value="maybe">might go</data> to ...</nowiki></code>
*** etc.

To keep it simple, we don't need need to markup the nested event - since it can be discovered at the in-reply-to link.

The re-use of p-location from h-event is probably something we should add to h-entry anyway - it certainly has use beyond RSVP posts.

Similarly, we should formally add u-in-reply-to to h-entry as it has shown usefulness for comment posts, now RSVPs, and will likely be useful for any other kind of post which is in regard to some other post.

Which leaves the only really new property '''p-rsvp'''.

Is it worth introducing a separate/new '''h-rsvp''' top level microformat just for RSVPs for one new property?

Or should we simply add '''p-rsvp''' as an optional property to h-entry?

I'm leaning towards the latter, since that is fewer additions, and seems simpler. I'm not sure it is worth introducing h-rsvp just for one new property.

If further brainstorming shows RSVPs to need more than just one new property, we can reconsider.

[[User:Tantek|Tantek]] 16:05, 8 May 2013 (UTC)