rel-in-reply-to - Revision history

GRegorLove: note superseded by u-in-reply-to

2018-07-18T23:21:53Z

note superseded by u-in-reply-to

← Older revision		Revision as of 23:21, 18 July 2018
Line 1:		Line 1:
	{{stub}}		{{stub}}

			<span style="font-weight:bold;padding:0.5em;background:yellow">Note: this proposal is superseded by the u-in-reply-to property of [[h-entry]].</span>

	'''<dfn>rel=in-reply-to</dfn>''' is proposed method for linking from a comment to the original post that the comment is a reply to.		'''<dfn>rel=in-reply-to</dfn>''' is proposed method for linking from a comment to the original post that the comment is a reply to.

Tantek: history - note csarven 2008-10-03 proposal on microformats.org to re-use rel=in-reply-to

2015-06-23T11:17:40Z

history - note csarven 2008-10-03 proposal on microformats.org to re-use rel=in-reply-to

← Older revision		Revision as of 11:17, 23 June 2015
Line 59:		Line 59:
	** home page or recent updates that contain the post		** home page or recent updates that contain the post
	Whereas rel=in-reply-to MUST ONLY be used on post permalink page, which is harder to get right.		Whereas rel=in-reply-to MUST ONLY be used on post permalink page, which is harder to get right.

			== History ==
			* 2008-10-03 [[User:Csarven]] proposed <code>rel=in-reply-to</code> (re-use from cited RFC4685 Atom Threading Extensions) as a way to link a comment "hEntry" to a "root hEntry": http://microformats.org/wiki/hatom-brainstorming#User_comment_entries

	== See Also ==		== See Also ==

Tantek: /* u-in-reply-to */ fix sentence frag and flow of wording

2014-04-09T21:30:42Z

u-in-reply-to: fix sentence frag and flow of wording

← Older revision		Revision as of 21:30, 9 April 2014
Line 54:		Line 54:

	Advantage:		Advantage:
	* can be used <em>anywhere</em> a post may occur~~, where-as rel=in-reply-to sh~~		* <code>class=u-in-reply-to</code> can be used <em>anywhere</em> a post may occur:
	** post permalink page (which should also use rel=in-reply-to)		** post permalink page (which should also use rel=in-reply-to)
	** archive pages that contain the post		** archive pages that contain the post
	** home page or recent updates that contain the post		** home page or recent updates that contain the post
			Whereas rel=in-reply-to MUST ONLY be used on post permalink page, which is harder to get right.

	== See Also ==		== See Also ==

Tantek: /* Previous Formats */ Atom in-reply-to extension

2013-08-10T01:31:54Z

Previous Formats: Atom in-reply-to extension

← Older revision		Revision as of 01:31, 10 August 2013
Line 32:		Line 32:

	== Previous Formats ==		== Previous Formats ==
			=== Atom in-reply-to extension ===
			Atom Threading Extensions (RFC4685) has an [http://tools.ietf.org/html/rfc4685#section-3 in-reply-to Extension Element].

			No idea if anyone is consuming it.

			=== Gdata in-reply-to ===
	[[YouTube]] uses a URL-qualified version of in-reply-to:		[[YouTube]] uses a URL-qualified version of in-reply-to:
	* <code><nowiki>rel="http://gdata.youtube.com/schemas/2007#in-reply-to"</nowiki></code>		* <code><nowiki>rel="http://gdata.youtube.com/schemas/2007#in-reply-to"</nowiki></code>

Tantek: /* Limitations */ to

2013-04-10T22:10:43Z

Limitations: to

← Older revision		Revision as of 22:10, 10 April 2013
Line 6:		Line 6:
	In a post that is a reply/response/comment to some other original post on the web, the hyperlink from the reply to the original should be marked up with the <code>rel</code> value <code>in-reply-to</code>.		In a post that is a reply/response/comment to some other original post on the web, the hyperlink from the reply to the original should be marked up with the <code>rel</code> value <code>in-reply-to</code>.
	=== Limitations ===		=== Limitations ===
	Publishers must only use this rel value on a post's permalink page, thereby indicating that the permalink page is a reply the destination of the hyperlink with <code>rel=in-reply-to</code>		Publishers must only use this rel value on a post's permalink page, thereby indicating that the permalink page is a reply to the destination of the hyperlink with <code>rel=in-reply-to</code>

	Posts that are aggregated in other pages, e.g. an archive page, or home/updates page, must not use <code>rel=in-reply-to</code> on links because those aggregate pages (e.g. archive, home, updates) are not replies themselves, even though they may contain replies.		Posts that are aggregated in other pages, e.g. an archive page, or home/updates page, must not use <code>rel=in-reply-to</code> on links because those aggregate pages (e.g. archive, home, updates) are not replies themselves, even though they may contain replies.

Tantek: limitations - only on post permalink pages

2013-04-10T22:07:47Z

limitations - only on post permalink pages

← Older revision		Revision as of 22:07, 10 April 2013
Line 5:		Line 5:
	== Publishers ==		== Publishers ==
	In a post that is a reply/response/comment to some other original post on the web, the hyperlink from the reply to the original should be marked up with the <code>rel</code> value <code>in-reply-to</code>.		In a post that is a reply/response/comment to some other original post on the web, the hyperlink from the reply to the original should be marked up with the <code>rel</code> value <code>in-reply-to</code>.
			=== Limitations ===
			Publishers must only use this rel value on a post's permalink page, thereby indicating that the permalink page is a reply the destination of the hyperlink with <code>rel=in-reply-to</code>

			Posts that are aggregated in other pages, e.g. an archive page, or home/updates page, must not use <code>rel=in-reply-to</code> on links because those aggregate pages (e.g. archive, home, updates) are not replies themselves, even though they may contain replies.

	== Consumers ==		== Consumers ==

Tantek: /* Alternatives */ u-in-reply-to, advantages

2013-04-10T22:04:56Z

Alternatives: u-in-reply-to, advantages

← Older revision		Revision as of 22:04, 10 April 2013
Line 38:		Line 38:

	== Alternatives ==		== Alternatives ==
			=== u-in-reply-to ===
	Alternatively, or in addition, there is the suggestion to use:		Alternatively, or in addition, there is the suggestion to use:
	* <code>class=u-in-reply-to</code>		* <code>class=u-in-reply-to</code>
	on hyperlinks from comment posts marked up with [[h-entry]] to original posts.		on hyperlinks from comment posts marked up with [[h-entry]] to original posts.

			Advantage:
			* can be used <em>anywhere</em> a post may occur, where-as rel=in-reply-to sh
			** post permalink page (which should also use rel=in-reply-to)
			** archive pages that contain the post
			** home page or recent updates that contain the post

	== See Also ==		== See Also ==

Barnabywalters: /* Issues */

2013-04-10T18:46:52Z

Issues

← Older revision		Revision as of 18:46, 10 April 2013
Line 19:		Line 19:
	Should the reply put <code>rel="in-reply-to"</code> on the hyperlinks to all of the other original posts? Or should the reply only use <code>rel="in-reply-to"</code> on the first or most important original post that it's a reply to?		Should the reply put <code>rel="in-reply-to"</code> on the hyperlinks to all of the other original posts? Or should the reply only use <code>rel="in-reply-to"</code> on the first or most important original post that it's a reply to?

			=== Nature of a “reply” ===

			How exactly do we define “reply” so that in-reply-to is used in suitable contexts? What factors differentiate a reply from, say, a comment or mention?

			* If the reply makes sense without the original content as context, is it a reply? If I write a blog post which is in response to another, but makes a point on it’s own, does it qualify to use in-reply-to? Does the content of a reply (and, by extension, multiple replies) have to flow like a conversation?

			For example, a “reply” could cover almost anything from a short, two word comment (F1R5T P0ST) to a long essay, or even a video (e.g. youtube video responses). Handling all of these concurrently (e.g. trying to build a facebook/twitter-like chronological conversation UI) is likely to be a nightmare.

	== Previous Formats ==		== Previous Formats ==

Tantek: /* Consumers */ display

2013-04-10T18:13:54Z

Consumers: display

← Older revision		Revision as of 18:13, 10 April 2013
Line 8:		Line 8:
	== Consumers ==		== Consumers ==
	=== WebMention ===		=== WebMention ===
	If ~~you~~ site implements receiving ~~WebMentions~~, implement the WebMention ping verification using <code>rel="in-reply-to"</code> as documented in the [http://webmention.org/ WebMention specification].		If your site implements receiving webmentions, implement the WebMention ping verification using <code>rel="in-reply-to"</code> as documented in the [http://webmention.org/ WebMention specification].

			When your site receives a verified webmention with an "in-reply-to" link, provide a display of the webmention source on your webmention target page, e.g. as suggested in: [http://indiewebcamp.com/comment-presentation#Display_received_comments_brainstorm IndieWebCamp: comment presentation] (uses the [[h-entry]] at the source page to construct a comment on the target page with author, comment contents, date posted, etc.).

	== Issues ==		== Issues ==

Tantek: add explicit publishers and consumers spec text, add issues section with reply to multiple other posts question

2013-04-10T03:33:35Z

add explicit publishers and consumers spec text, add issues section with reply to multiple other posts question

← Older revision		Revision as of 03:33, 10 April 2013
Line 3:		Line 3:
	'''<dfn>rel=in-reply-to</dfn>''' is proposed method for linking from a comment to the original post that the comment is a reply to.		'''<dfn>rel=in-reply-to</dfn>''' is proposed method for linking from a comment to the original post that the comment is a reply to.

	== WebMention ==		== Publishers ==
	~~Checking for~~ <code>rel="in-reply-to"</code> ~~on a link is one of~~ the ~~methods mentioned in~~ [http://webmention.org/ WebMention] ~~for verifying~~ a ~~WebMention ping.~~		In a post that is a reply/response/comment to some other original post on the web, the hyperlink from the reply to the original should be marked up with the <code>rel</code> value <code>in-reply-to</code>.

			== Consumers ==
			=== WebMention ===
			If you site implements receiving WebMentions, implement the WebMention ping verification using <code>rel="in-reply-to"</code> as documented in the [http://webmention.org/ WebMention specification].

			== Issues ==
			=== Replying To Multiple Original Posts ===
			What if a post is a reply/response/comment to multiple other original posts on the web?
			* Example: (need a real world example of a reply to multiple other posts to better understand this problem and its importance)

			Should the reply put <code>rel="in-reply-to"</code> on the hyperlinks to all of the other original posts? Or should the reply only use <code>rel="in-reply-to"</code> on the first or most important original post that it's a reply to?


	== Previous Formats ==		== Previous Formats ==