comment-brainstorming - Revision history

Btrem: /* Distinction between Comment and List of Comments */ Grammatical correction.

2022-07-13T22:58:05Z

Distinction between Comment and List of Comments: Grammatical correction.

← Older revision		Revision as of 22:58, 13 July 2022
Line 13:		Line 13:

	== Distinction between Comment and List of Comments ==		== Distinction between Comment and List of Comments ==
	Ideally, each comment/reply should have its own permalink page, but also get copied into the markup of the post ~~its~~ in reply to. Should the markup of the two cases differ? We should be able to solve both problems by extending <code>h-entry</code> a little.		Ideally, each comment/reply should have its own permalink page, but also get copied into the markup of the post it's in reply to. Should the markup of the two cases differ? We should be able to solve both problems by extending <code>h-entry</code> a little.

	* A reply on its own page is just another h-entry. The presence of u-in-reply-to implies its a reply (of a sort, could also be a special reply like an RSVP).		* A reply on its own page is just another h-entry. The presence of u-in-reply-to implies its a reply (of a sort, could also be a special reply like an RSVP).

Btrem: /* Problem */ Minor grammatical corrections.

2022-07-13T20:37:12Z

Problem: Minor grammatical corrections.

← Older revision		Revision as of 20:37, 13 July 2022
Line 8:		Line 8:
	Shortform: How do you publish comments on your own site, and how do you publish comments others have made on your posts?		Shortform: How do you publish comments on your own site, and how do you publish comments others have made on your posts?

	Longform: How do you publish your own comments, others' comments on your stuff, and how do you track comments? How do track the comments you have made on blogs, comments made on blogs ~~your~~ interested in and comments other people have made on your own blog?		Longform: How do you publish your own comments, others' comments on your stuff, and how do you track comments? How do you track the comments you have made on blogs, comments made on blogs you're interested in and comments other people have made on your own blog?

	How can you do this in a pragmatic way, ingested into some kind of data store, searched or aggregated?		How can you do this in a pragmatic way, ingested into some kind of data store, searched or aggregated?

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:21:30Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:21, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~Brainstorming for a Comment Microformat~~</entry-title>~~		{{DISPLAYTITLE:Brainstorming for a Comment Microformat}}

	{{instead\|https://indieweb.org/reply and https://indieweb.org/comments}}		{{instead\|https://indieweb.org/reply and https://indieweb.org/comments}}

Tantek: see instead indieweb.org/reply and comments

2018-06-08T23:01:12Z

see instead indieweb.org/reply and comments

← Older revision		Revision as of 23:01, 8 June 2018
Line 1:		Line 1:
	<entry-title>Brainstorming for a Comment Microformat</entry-title>		<entry-title>Brainstorming for a Comment Microformat</entry-title>

			{{instead\|https://indieweb.org/reply and https://indieweb.org/comments}}

	This is a brainstorm for comment microformat. Examples of a comment can be found here [[comment-examples]]		This is a brainstorm for comment microformat. Examples of a comment can be found here [[comment-examples]]

Tantek: remove reference to "indieweb" from issue / idea - was not relevant to the idea. clarify comment on its own page, vs in a list, vs both.

2015-07-12T21:27:57Z

remove reference to "indieweb" from issue / idea - was not relevant to the idea. clarify comment on its own page, vs in a list, vs both.

← Older revision		Revision as of 21:27, 12 July 2015
Line 9:		Line 9:
	How can you do this in a pragmatic way, ingested into some kind of data store, searched or aggregated?		How can you do this in a pragmatic way, ingested into some kind of data store, searched or aggregated?

	== Distinction between Comment ~~(permalink)~~ and List of Comments ==		== Distinction between Comment and List of Comments ==
			Ideally, each comment/reply should have its own permalink page, but also get copied into the markup of the post its in reply to. Should the markup of the two cases differ? We should be able to solve both problems by extending <code>h-entry</code> a little.

	~~Ideally~~, ~~each indieweb~~ comment~~/reply should~~ have ~~it’s~~ own permalink page~~, but~~ also ~~get~~ copied ~~into the markup~~ of ~~the~~ post ~~it’s~~ in ~~reply~~ to. ~~Should the markup~~ of ~~the two cases differ? We should be able to solve both problems by extending <code>~~h-entry~~</code> a little~~.		* A reply on its own page is just another h-entry. The presence of u-in-reply-to implies its a reply (of a sort, could also be a special reply like an RSVP).
			* If a comment does have its own permalink page and also copied to a list of comments on a post, it should likely be marked up as an [[h-cite]] in the list of comments, and link to its canonical copy on its own page.
	* Note: define "indieweb" and describe its relevancy --[[User:~~Csarven~~\|~~Sarven Capadisli~~]] 21:57, 12 July 2015 (UTC)		* If a comment only exists as part of a list of comments, then using [[h-entry]] for it there seems fine, since that's likely the (only?) canonical copy of the comment. [[User:Tantek\|Tantek]] 21:27, 12 July 2015 (UTC)

	== Discovered Elements ==		== Discovered Elements ==

Csarven: Asked for clarification/relevancy on "indieweb"

2015-07-12T20:58:15Z

Asked for clarification/relevancy on "indieweb"

← Older revision		Revision as of 20:58, 12 July 2015
Line 12:		Line 12:

	Ideally, each indieweb comment/reply should have it’s own permalink page, but also get copied into the markup of the post it’s in reply to. Should the markup of the two cases differ? We should be able to solve both problems by extending <code>h-entry</code> a little.		Ideally, each indieweb comment/reply should have it’s own permalink page, but also get copied into the markup of the post it’s in reply to. Should the markup of the two cases differ? We should be able to solve both problems by extending <code>h-entry</code> a little.

			* Note: define "indieweb" and describe its relevancy --[[User:Csarven\|Sarven Capadisli]] 21:57, 12 July 2015 (UTC)

	== Discovered Elements ==		== Discovered Elements ==

Tantek: /* Use case for same page u-in-reply-to */ note use-case currently theoretical

2015-07-12T20:09:22Z

Use case for same page u-in-reply-to: note use-case currently theoretical

← Older revision		Revision as of 20:09, 12 July 2015
Line 82:		Line 82:

	A: The use-case for the same page u-in-reply-to is applications/sites that may subscribe to the comments as a feed, perhaps mix them in with other comments/entries. Having an explicit u-in-reply-to makes the comment portable. It's not critical, but it is also a simple/good pattern that encourages extracted data to be self-contained in general.		A: The use-case for the same page u-in-reply-to is applications/sites that may subscribe to the comments as a feed, perhaps mix them in with other comments/entries. Having an explicit u-in-reply-to makes the comment portable. It's not critical, but it is also a simple/good pattern that encourages extracted data to be self-contained in general.

			* Note: this use-case is currently theoretical, no one is actually doing or asking to do this yet. [[User:Tantek\|Tantek]] 20:09, 12 July 2015 (UTC)

	=== Notes ===		=== Notes ===

Tantek: re-order with current thinking proposal at the top, cluster pre-microformats2 proposals, update/fix heading levels

2013-05-13T17:24:43Z

re-order with current thinking proposal at the top, cluster pre-microformats2 proposals, update/fix heading levels

Show changes

Barnabywalters: /* microformats2 h-feed p-comments */

2013-05-13T09:54:34Z

microformats2 h-feed p-comments

← Older revision		Revision as of 09:54, 13 May 2013
Line 61:		Line 61:
	</div>		</div>
	</source>		</source>

			* -1 for too much markup compared to .h-entry > .h-entry.p-comment --[[User:Barnabywalters\|bw]] 09:54, 13 May 2013 (UTC)

	== microformats2 p-comment h-entry ==		== microformats2 p-comment h-entry ==

Tantek: =

2013-05-02T22:25:54Z

← Older revision		Revision as of 22:25, 2 May 2013
Line 115:		Line 115:
	* one fewer div / less hierarchy than proposal above		* one fewer div / less hierarchy than proposal above

	== Questions ==		=== Questions ===
	=== Use case for same page u-in-reply-to ===		==== Use case for same page u-in-reply-to ====
	Q: What is the use-case for the same page u-in-reply-to?		Q: What is the use-case for the same page u-in-reply-to?