feed-examples - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:22:38Z

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

← Older revision		Revision as of 16:22, 18 July 2020
Line 1:		Line 1:
	{{stub}}		{{stub}}

	~~<entry-title>~~feed examples~~</entry-title>~~		{{DISPLAYTITLE:feed examples}}

	Part of the [[feed]] microformat development effort per the [[process]].		Part of the [[feed]] microformat development effort per the [[process]].

Tantek: /* real world examples */ note: add examples with hAtom to that examples in wild page

2012-11-06T00:13:43Z

real world examples: note: add examples with hAtom to that examples in wild page

← Older revision		Revision as of 00:13, 6 November 2012
Line 22:		Line 22:
	== real world examples ==		== real world examples ==
	''Links to public web pages, either popular or insightful'' that provide real world examples of the type of publishing that can be improved with a feed microformat.		''Links to public web pages, either popular or insightful'' that provide real world examples of the type of publishing that can be improved with a feed microformat.

			Note: if the example already has [[hAtom]], please add it to [[hatom-examples-in-wild]] instead of here.

	Flat list of examples:		Flat list of examples:
	* http://blog.cuboxlabs.com (blog feed + tweets feed on the same page)		* http://blog.cuboxlabs.com (blog feed + tweets feed on the same page)
	* http://ossguy.com/?cat=8 (blog filtered by category + tweets feed on the same page)

	Grouped examples:		Grouped examples:

Tantek: /* real world examples */ Matt is included in the hAtom examples

2012-11-06T00:09:18Z

real world examples: Matt is included in the hAtom examples

← Older revision		Revision as of 00:09, 6 November 2012
Line 24:		Line 24:

	Flat list of examples:		Flat list of examples:
	* http://ma.tt (blog feed + tweets feed on the same page)
	* http://blog.cuboxlabs.com (blog feed + tweets feed on the same page)		* http://blog.cuboxlabs.com (blog feed + tweets feed on the same page)
	* http://ossguy.com/?cat=8 (blog filtered by category + tweets feed on the same page)		* http://ossguy.com/?cat=8 (blog filtered by category + tweets feed on the same page)

Singpolyma: /* real world examples */ add ossguy.com category example

2012-11-06T00:09:12Z

real world examples: add ossguy.com category example

← Older revision		Revision as of 00:09, 6 November 2012
Line 26:		Line 26:
	* http://ma.tt (blog feed + tweets feed on the same page)		* http://ma.tt (blog feed + tweets feed on the same page)
	* http://blog.cuboxlabs.com (blog feed + tweets feed on the same page)		* http://blog.cuboxlabs.com (blog feed + tweets feed on the same page)
			* http://ossguy.com/?cat=8 (blog filtered by category + tweets feed on the same page)

	Grouped examples:		Grouped examples:

Tantek: add The Problem section, rewrite purpose section into a couple of use cases based on today's discussion

2012-11-05T23:54:22Z

add The Problem section, rewrite purpose section into a couple of use cases based on today's discussion

← Older revision		Revision as of 23:54, 5 November 2012
Line 7:		Line 7:
	This page is for documenting [[examples]] of real world web pages with one or more feeds that would benefit from additional explicit structural markup.		This page is for documenting [[examples]] of real world web pages with one or more feeds that would benefit from additional explicit structural markup.

	== ~~purpose~~ ==		== The Problem ==
			If a site has items from more than one feed, a [[feed-reader]] has no idea how to aggregate items from only one feed. Feed readers need a way to discover and choose which feed on a page they are aggregating.

			== Use Cases ==
			=== Read one feed of many ===
			It '''might''' be useful to have a way of specifying a wrapper for a a collection of entries in the case where there are multiple feeds on one page, and one wanted to read the entries of just one feed (e.g., the main blog feed, but not the sidebar tweets feed).

			=== Search and indexing ===
	Many HTML pages contain periodic/episodic content. It may be helpful to explicitly group similar/related/sequential episodes for the purposes of re-using this data in other contexts (restyling, search, indexing).		Many HTML pages contain periodic/episodic content. It may be helpful to explicitly group similar/related/sequential episodes for the purposes of re-using this data in other contexts (restyling, search, indexing).

	It '''might''' be useful to have a way of specifying a wrapper for a a collection of entries. Especially in the case where there are multiple feeds on one page, but one wanted to target the entries of just one feed (e.g., the main blog feed, but not the sidebar tweets feed).

	== previous effort ==		== previous effort ==
Line 25:		Line 30:

	=== hAtom ===		=== hAtom ===
	~~See~~: [[hatom-examples-in-wild]]		Most examples these days use hAtom already and thus check here for specific modern examples:
			* [[hatom-examples-in-wild]]

	== analysis of publishing practices ==		== analysis of publishing practices ==

Tantek: see hatom examples in wild

2012-11-05T23:39:43Z

see hatom examples in wild

← Older revision		Revision as of 23:39, 5 November 2012
Line 21:		Line 21:
	* http://ma.tt (blog feed + tweets feed on the same page)		* http://ma.tt (blog feed + tweets feed on the same page)
	* http://blog.cuboxlabs.com (blog feed + tweets feed on the same page)		* http://blog.cuboxlabs.com (blog feed + tweets feed on the same page)

			Grouped examples:

			=== hAtom ===
			See: [[hatom-examples-in-wild]]

	== analysis of publishing practices ==		== analysis of publishing practices ==

Tantek at 21:25, 3 October 2012

2012-10-03T21:25:18Z

← Older revision		Revision as of 21:25, 3 October 2012
Line 9:		Line 9:
	== purpose ==		== purpose ==
	Many HTML pages contain periodic/episodic content. It may be helpful to explicitly group similar/related/sequential episodes for the purposes of re-using this data in other contexts (restyling, search, indexing).		Many HTML pages contain periodic/episodic content. It may be helpful to explicitly group similar/related/sequential episodes for the purposes of re-using this data in other contexts (restyling, search, indexing).


	It '''might''' be useful to have a way of specifying a wrapper for a a collection of entries. Especially in the case where there are multiple feeds on one page, but one wanted to target the entries of just one feed (e.g., the main blog feed, but not the sidebar tweets feed).		It '''might''' be useful to have a way of specifying a wrapper for a a collection of entries. Especially in the case where there are multiple feeds on one page, but one wanted to target the entries of just one feed (e.g., the main blog feed, but not the sidebar tweets feed).

Tantek: previous effort

2012-10-03T21:13:33Z

previous effort

← Older revision		Revision as of 21:13, 3 October 2012
Line 12:		Line 12:

	It '''might''' be useful to have a way of specifying a wrapper for a a collection of entries. Especially in the case where there are multiple feeds on one page, but one wanted to target the entries of just one feed (e.g., the main blog feed, but not the sidebar tweets feed).		It '''might''' be useful to have a way of specifying a wrapper for a a collection of entries. Especially in the case where there are multiple feeds on one page, but one wanted to target the entries of just one feed (e.g., the main blog feed, but not the sidebar tweets feed).

			== previous effort ==
			* [[blog-description-examples]] may have examples that could be incorporated here

	== real world examples ==		== real world examples ==

Veganstraightedge: /* purpose */ brain dump on why a container element might be useful

2012-10-03T20:50:10Z

purpose: brain dump on why a container element might be useful

← Older revision		Revision as of 20:50, 3 October 2012
Line 9:		Line 9:
	== purpose ==		== purpose ==
	Many HTML pages contain periodic/episodic content. It may be helpful to explicitly group similar/related/sequential episodes for the purposes of re-using this data in other contexts (restyling, search, indexing).		Many HTML pages contain periodic/episodic content. It may be helpful to explicitly group similar/related/sequential episodes for the purposes of re-using this data in other contexts (restyling, search, indexing).


			It '''might''' be useful to have a way of specifying a wrapper for a a collection of entries. Especially in the case where there are multiple feeds on one page, but one wanted to target the entries of just one feed (e.g., the main blog feed, but not the sidebar tweets feed).

	== real world examples ==		== real world examples ==

Veganstraightedge: /* real world examples */ added a couple links to sites that have both a blog feed and tweets feed on the same page.

2012-10-03T20:41:23Z

real world examples: added a couple links to sites that have both a blog feed and tweets feed on the same page.

← Older revision		Revision as of 20:41, 3 October 2012
Line 14:		Line 14:

	Flat list of examples:		Flat list of examples:
	* ...		* http://ma.tt (blog feed + tweets feed on the same page)
			* http://blog.cuboxlabs.com (blog feed + tweets feed on the same page)

	== analysis of publishing practices ==		== analysis of publishing practices ==