rel-in-reply-to: Difference between revisions
(stub) |
GRegorLove (talk | contribs) (note superseded by u-in-reply-to) |
||
| (13 intermediate revisions by 2 users not shown) | |||
| 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. | ||
== 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>. | |||
=== Limitations === | |||
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. | |||
== Consumers == | |||
=== WebMention === | |||
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 == | |||
=== 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? | |||
=== 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 == | ||
=== 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>http://gdata.youtube.com/schemas/2007#in-reply-to"</code> | * <code><nowiki>rel="http://gdata.youtube.com/schemas/2007#in-reply-to"</nowiki></code> | ||
in their Atom API, e.g.: | in their Atom API, e.g.: | ||
<source lang=xml> | <source lang=xml> | ||
| Line 14: | Line 50: | ||
== 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: | |||
* <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) | |||
** archive pages 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. | |||
== 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 == | ||
| Line 22: | Line 69: | ||
* [[hAtom]] | * [[hAtom]] | ||
* [[h-entry]] | * [[h-entry]] | ||
* http://indiewebcamp.com/comments | |||
* http://indiewebcamp.com/webmention | |||
Latest revision as of 23:21, 18 July 2018
This article is a stub. You can help the microformats.org wiki by expanding it.
Note: this proposal is superseded by the u-in-reply-to property of h-entry.
rel=in-reply-to is proposed method for linking from a comment to the original post that the comment is a reply to.
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 rel value in-reply-to.
Limitations
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 rel=in-reply-to
Posts that are aggregated in other pages, e.g. an archive page, or home/updates page, must not use rel=in-reply-to on links because those aggregate pages (e.g. archive, home, updates) are not replies themselves, even though they may contain replies.
Consumers
WebMention
If your site implements receiving webmentions, implement the WebMention ping verification using rel="in-reply-to" as documented in the 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: 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
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 rel="in-reply-to" on the hyperlinks to all of the other original posts? Or should the reply only use rel="in-reply-to" 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
Atom in-reply-to extension
Atom Threading Extensions (RFC4685) has an 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:
rel="http://gdata.youtube.com/schemas/2007#in-reply-to"
in their Atom API, e.g.:
<link rel="http://gdata.youtube.com/schemas/2007#in-reply-to"
type="application/atom+xml"
href="https://gdata.youtube.com/feeds/api/videos/2cd.../comments/978..."/>
Alternatives
u-in-reply-to
Alternatively, or in addition, there is the suggestion to use:
class=u-in-reply-to
on hyperlinks from comment posts marked up with h-entry to original posts.
Advantage:
class=u-in-reply-tocan be used anywhere a post may occur:- 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
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
rel=in-reply-to(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