h-entry - Revision history

Tantek: use internet archive link to rescue one example, move a couple of examples to offline

2025-07-02T23:12:15Z

use internet archive link to rescue one example, move a couple of examples to offline

← Older revision		Revision as of 23:12, 2 July 2025
Line 105:		Line 105:
	* '''<code>u-uid</code>''' - universally unique identifier, typically canonical entry URL		* '''<code>u-uid</code>''' - universally unique identifier, typically canonical entry URL
	* '''<code>p-location</code>''' - location the entry was posted from, optionally embed [[h-card]], [[h-adr]], or [[h-geo]]		* '''<code>p-location</code>''' - location the entry was posted from, optionally embed [[h-card]], [[h-adr]], or [[h-geo]]
	* '''<code id="u-syndication">u-syndication</code>''' - URL(s) of syndicated copies of this post. The property equivalent of [[rel-syndication]] ([http://erinjo.is/2014/checked-into-rockit-colabs-23 example])		* '''<code id="u-syndication">u-syndication</code>''' - URL(s) of syndicated copies of this post. The property equivalent of [[rel-syndication]] ([https://web.archive.org/web/20141027120218/http://erinjo.is:80/2014/checked-into-rockit-colabs-23 archived example])
	* '''<code>u-in-reply-to</code>''' - the URL which the h-entry is considered reply to (i.e. doesn’t make sense without context, could show up in comment thread), optionally an embedded [[h-cite]] ([http://indiewebcamp.com/reply-context reply-context]) ([https://kartikprabhu.com/notes/re-citizen-of-indieweb example])		* '''<code>u-in-reply-to</code>''' - the URL which the h-entry is considered reply to (i.e. doesn’t make sense without context, could show up in comment thread), optionally an embedded [[h-cite]] ([http://indiewebcamp.com/reply-context reply-context]) ([https://kartikprabhu.com/notes/re-citizen-of-indieweb example])
	* '''<code id="p-rsvp">p-rsvp</code>''' (enum, use <data> element or [[value-class-pattern]])		* '''<code id="p-rsvp">p-rsvp</code>''' (enum, use <data> element or [[value-class-pattern]])
Line 236:		Line 236:
	* Michiel de Jong marks up his profile and notes with h-entry and h-card on [https://michielbdejong.com/ michielbdejong.com]		* Michiel de Jong marks up his profile and notes with h-entry and h-card on [https://michielbdejong.com/ michielbdejong.com]
	* Mike Taylor marks up his profile and blog posts with h-card and h-entry on [https://bear.im/bearlog/ bear.im]		* Mike Taylor marks up his profile and blog posts with h-card and h-entry on [https://bear.im/bearlog/ bear.im]
	* Erin Jo Ritchey marks up her profile, posts and comments using h-card, h-entry and h-cite with idno on [http://erinjo.is/ erinjo.is]
	* Jeena Paradies marks up his profile, blog posts, notes and comments using h-card, h-entry and h-cite on [https://jeena.net/ jeena.net]		* Jeena Paradies marks up his profile, blog posts, notes and comments using h-card, h-entry and h-cite on [https://jeena.net/ jeena.net]
	* Andy Sylvester marks up his profile, blog posts and comments using h-card and h-entry on [http://andysylvester.com/2014/03/01/howto-setting-up-the-selfoss-feed-reader-with-microformats-support/ andysylvester.com] (note: as of 2014-03-13 using h-entry for comments instead of correct h-cite --[[User:Barnabywalters\|bw]] 14:44, 13 March 2014 (UTC))		* Andy Sylvester marks up his profile, blog posts and comments using h-card and h-entry on [http://andysylvester.com/2014/03/01/howto-setting-up-the-selfoss-feed-reader-with-microformats-support/ andysylvester.com] (note: as of 2014-03-13 using h-entry for comments instead of correct h-cite --[[User:Barnabywalters\|bw]] 14:44, 13 March 2014 (UTC))
Line 244:		Line 244:
	* Marcus Povey marks up his blog posts and profile with h-entry and h-card on [http://www.marcus-povey.co.uk/ marcus-povey.co.uk]		* Marcus Povey marks up his blog posts and profile with h-entry and h-card on [http://www.marcus-povey.co.uk/ marcus-povey.co.uk]
	* Matthias Pfefferle marks up his blog posts, comments and profile with h-card, h-cite and h-entry on [http://notizblog.org/ notizblog.org]		* Matthias Pfefferle marks up his blog posts, comments and profile with h-card, h-cite and h-entry on [http://notizblog.org/ notizblog.org]
	* Kyle Mahan marks up his profile and notes with h-card and h-entry on [http://kylewm.com/ kylewm.com]
	* Okinawan-lyrics marks up his posts with h-entry and h-card ([http://www.okinawan-lyrics.com/ example])		* Okinawan-lyrics marks up his posts with h-entry and h-card ([http://www.okinawan-lyrics.com/ example])
	* App.net marks up profile pages and permalink pages with h-entry as of 2013-08-06 ([https://alpha.app.net/voidfiles example])		* App.net marks up profile pages and permalink pages with h-entry as of 2013-08-06 ([https://alpha.app.net/voidfiles example])
Line 265:		Line 264:

	=== offline ===		=== offline ===
			* Erin Jo Ritchey marked up her profile, posts and comments using h-card, h-entry and h-cite with idno on <nowiki>http://erinjo.is/</nowiki>
			* Kyle Mahan marked up his profile and notes with h-card and h-entry on <nowiki>http://kylewm.com/</nowiki>
	* spreadly marks up share permalink pages with h-entry, as well as minimal h-cards and experimental p-like properties		* spreadly marks up share permalink pages with h-entry, as well as minimal h-cards and experimental p-like properties

Snarfed: remove "episodic or datestamped" qualifier. it's kinda right in spirit, but not in letter. see https://chat.indieweb.org/microformats/2024-10-17#t1729138929962700

2024-10-17T23:56:16Z

remove "episodic or datestamped" qualifier. it's kinda right in spirit, but not in letter. see https://chat.indieweb.org/microformats/2024-10-17#t1729138929962700

← Older revision		Revision as of 23:56, 17 October 2024
Line 1:		Line 1:
	{{DISPLAYTITLE:h-entry}}		{{DISPLAYTITLE:h-entry}}
	<dfn style="font-style:normal;font-weight:bold">h-entry</dfn> is a simple, open format for ~~episodic or datestamped~~ content on the web. h-entry is often used with content intended to be syndicated, e.g. blog posts. h-entry is one of several open [[microformats\|microformat]] standards suitable for embedding data in HTML.		<dfn style="font-style:normal;font-weight:bold">h-entry</dfn> is a simple, open format for content on the web. h-entry is often used with content intended to be syndicated, e.g. blog posts. h-entry is one of several open [[microformats\|microformat]] standards suitable for embedding data in HTML.

	h-entry is the [[microformats2]] update to [[hAtom]], in particular its "hentry" root class which itself was based on [[Atom]]'s "entry" element. For an update to "hfeed" see [[h-feed]].		h-entry is the [[microformats2]] update to [[hAtom]], in particular its "hentry" root class which itself was based on [[Atom]]'s "entry" element. For an update to "hfeed" see [[h-feed]].

Tantek: /* Properties */ editorial: more explicit clarification of existing functionality that all properties are optional and plural meaning they may have multiple instances, not that each property instance takes multiple values (no one has ever implemented that, fortunately)

2024-05-23T17:47:53Z

Properties: editorial: more explicit clarification of existing functionality that all properties are optional and plural meaning they may have multiple instances, not that each property instance takes multiple values (no one has ever implemented that, fortunately)

← Older revision		Revision as of 17:47, 23 May 2024
Line 90:		Line 90:

	== Properties ==		== Properties ==
	h-entry properties, inside an element with class '''h-entry'''. All properties are optional and may ~~be plural~~.		h-entry properties, inside an element with class '''h-entry'''. All properties are both optional and may have multiple instances, e.g. multiple name, url, photo etc. properties.
	* See [[microformats2-parsing]] to learn more about property classnames.		* See [[microformats2-parsing]] to learn more about property classnames.

Dshanske: /* Properties */

2023-11-24T20:53:03Z

Properties

← Older revision		Revision as of 20:53, 24 November 2023
Line 153:		Line 153:
	* '''<code>u-translation-of</code>''' - indicates this h-entry is a translation of the linked URL into another language. Can be used in the same way as the existing <code>u-like-of</code> and <code>u-repost-of</code> properties, with just the URL to the original h-entry, or (optionally) contain an embedded <code>h-cite</code>. https://github.com/microformats/h-entry/issues/26		* '''<code>u-translation-of</code>''' - indicates this h-entry is a translation of the linked URL into another language. Can be used in the same way as the existing <code>u-like-of</code> and <code>u-repost-of</code> properties, with just the URL to the original h-entry, or (optionally) contain an embedded <code>h-cite</code>. https://github.com/microformats/h-entry/issues/26
	* '''<code>u-checkin</code>''' - the URL of the venue/location h-card which the h-entry is considered a “checkin” of. Optionally an embedded h-card. https://github.com/microformats/h-entry/issues/15		* '''<code>u-checkin</code>''' - the URL of the venue/location h-card which the h-entry is considered a “checkin” of. Optionally an embedded h-card. https://github.com/microformats/h-entry/issues/15
			* '''<code>u-review-of</code>''' - the URL which the h-entry is considered a review of, optionally an embedded h-cite, h-card, h-event, or h-item. This could allow retirement of the h-review as unnecessary, in theory.
			** [https://github.com/microformats/h-entry/issues/32 Issue 32]

	The following interpretation is also proposed addition:		The following interpretation is also proposed addition:

GRegorLove: s///

2023-07-26T21:16:46Z

s/<source>/<syntaxhighlight>/

← Older revision		Revision as of 21:16, 26 July 2023
Line 22:		Line 22:
	Here is a simple blog post example:		Here is a simple blog post example:

	<~~source~~ lang=~~html4strict~~>		<syntaxhighlight lang="html">
	<article class="h-entry">		<article class="h-entry">
	<h1 class="p-name">Microformats are amazing</h1>		<h1 class="p-name">Microformats are amazing</h1>
Line 34:		Line 34:
	</div>		</div>
	</article>		</article>
	</~~source~~>		</syntaxhighlight>

	Parsed JSON:		Parsed JSON:
	<~~source~~ lang=~~javascript~~>		<syntaxhighlight lang="json">
	{		{
	"items": [		"items": [
Line 80:		Line 80:
	]		]
	}		}
	</~~source~~>		</syntaxhighlight>

	== Get started ==		== Get started ==
Line 287:		Line 287:
	For backward compatibility with legacy [[hAtom]] consuming implementations, use [[hAtom]] classnames (or rel values) in addition to the more future-proof h-entry properties, for example:		For backward compatibility with legacy [[hAtom]] consuming implementations, use [[hAtom]] classnames (or rel values) in addition to the more future-proof h-entry properties, for example:

	<~~source~~ lang=~~html4strict~~>		<syntaxhighlight lang="html">
	<article class="h-entry hentry">		<article class="h-entry hentry">
	<h1 class="p-name entry-title">A Tale Of Two Tags</h1>		<h1 class="p-name entry-title">A Tale Of Two Tags</h1>
Line 300:		Line 300:
	<a href="/category/uncategorized/" rel="category tag" class="p-category">General</a>		<a href="/category/uncategorized/" rel="category tag" class="p-category">General</a>
	</article>		</article>
	</~~source~~>		</syntaxhighlight>

	{{note\|Note: you may use any valid HTML5 elements. The <code>article h1 address time</code> elements are used in the example as semantically richer suggestions, however in general <code>div span</code> work fine too. The <code>time</code> element is special though in that its <code>datetime</code> attribute provides a more author/user friendly way of separating a machine readable ISO8601 datetime from a human readable summary.		{{note\|Note: you may use any valid HTML5 elements. The <code>article h1 address time</code> elements are used in the example as semantically richer suggestions, however in general <code>div span</code> work fine too. The <code>time</code> element is special though in that its <code>datetime</code> attribute provides a more author/user friendly way of separating a machine readable ISO8601 datetime from a human readable summary.

Tantek: editorial: float TOC right like h-card

2023-06-30T23:15:26Z

editorial: float TOC right like h-card

← Older revision		Revision as of 23:15, 30 June 2023
Line 17:		Line 17:
	;License		;License
	: {{cc0-owfa-license}}		: {{cc0-owfa-license}}
	__TOC__		<span style="float:right">__TOC__</span>

	== Example ==		== Example ==

Tantek: editorial: note issues that u-photo depends on in order to advance from draft property, add proposal to require alt text on u-photo properties unless described in other text properties

2023-02-05T02:08:19Z

editorial: note issues that u-photo depends on in order to advance from draft property, add proposal to require alt text on u-photo properties unless described in other text properties

← Older revision		Revision as of 02:08, 5 February 2023
Line 123:		Line 123:
	* '''<code id="u-photo">u-photo</code>''' - one or more photos that is/are considered the primary content of the entry, unless there is a <code>p-location h-card</code>, which is still considered a "checkin" (i.e. with a photo). Otherwise the presence of a u-photo means the name of the entry should be interpreted as a caption on the photo, and the summary/content should be interpreted as a description of the photo.		* '''<code id="u-photo">u-photo</code>''' - one or more photos that is/are considered the primary content of the entry, unless there is a <code>p-location h-card</code>, which is still considered a "checkin" (i.e. with a photo). Otherwise the presence of a u-photo means the name of the entry should be interpreted as a caption on the photo, and the summary/content should be interpreted as a description of the photo.
	** [https://github.com/microformats/h-entry/issues/4 Issue 4: u-photo draft->core bc way more than 3+ pub and consuming impls/sites]		** [https://github.com/microformats/h-entry/issues/4 Issue 4: u-photo draft->core bc way more than 3+ pub and consuming impls/sites]
	** [https://github.com/microformats/h-entry/issues/24 Issue 24: Update Definition of Draft Property u-photo]		*** depends on: [https://github.com/microformats/h-entry/issues/24 Issue 24: Update Definition of Draft Property u-photo]
			*** depends on: [https://github.com/microformats/h-entry/issues/23 Issue 23: E-Content Overlaps with u-photo and similar properties]
			** Proposed (issue TBF): A <code>u-photo</code> property MUST be on an element that provides a text description for the image (e.g. <code><img alt=""></code>) UNLESS the image is already described inside the contents a text property such as <code>p-name</code>, <code>p-summary</code>, or <code>e-content</code>
	* '''<code id="u-video">u-video</code>''' - special u- parsing rules for <code><video src> & <source src></code>		* '''<code id="u-video">u-video</code>''' - special u- parsing rules for <code><video src> & <source src></code>
	** [https://github.com/microformats/h-entry/issues/5 Issue 5]		** [https://github.com/microformats/h-entry/issues/5 Issue 5]

JamesGallagher: Add link to new u-like GitHub issue

2022-08-15T16:25:19Z

Add link to new u-like GitHub issue

← Older revision		Revision as of 16:25, 15 August 2022
Line 132:		Line 132:
	** [https://github.com/microformats/h-entry/issues/6 Issue 6]		** [https://github.com/microformats/h-entry/issues/6 Issue 6]
	* '''<code>u-like</code>''' - similar to p-comment, URL to a like post of the current post, e.g. in a responses list or facepile.		* '''<code>u-like</code>''' - similar to p-comment, URL to a like post of the current post, e.g. in a responses list or facepile.
			** [https://github.com/microformats/h-entry/issues/31 Issue 32]
	* '''<code>u-repost</code>''' - similar to u-like, URL to a repost of the current post, e.g. in a responses list or facepile.		* '''<code>u-repost</code>''' - similar to u-like, URL to a repost of the current post, e.g. in a responses list or facepile.
	** [https://github.com/microformats/h-entry/issues/30 Issue 30]		** [https://github.com/microformats/h-entry/issues/30 Issue 30]

JamesGallagher: Add u-repost GitHub issue

2022-08-15T16:20:48Z

Add u-repost GitHub issue

← Older revision		Revision as of 16:20, 15 August 2022
Line 133:		Line 133:
	* '''<code>u-like</code>''' - similar to p-comment, URL to a like post of the current post, e.g. in a responses list or facepile.		* '''<code>u-like</code>''' - similar to p-comment, URL to a like post of the current post, e.g. in a responses list or facepile.
	* '''<code>u-repost</code>''' - similar to u-like, URL to a repost of the current post, e.g. in a responses list or facepile.		* '''<code>u-repost</code>''' - similar to u-like, URL to a repost of the current post, e.g. in a responses list or facepile.
			** [https://github.com/microformats/h-entry/issues/30 Issue 30]
	* '''<code>u-bookmark-of</code>''' - indicates this h-entry is a bookmark of another URL. Optionally an [[h-cite]]. See [https://indieweb.org/bookmark indieweb.org/bookmark] for examples in the wild.		* '''<code>u-bookmark-of</code>''' - indicates this h-entry is a bookmark of another URL. Optionally an [[h-cite]]. See [https://indieweb.org/bookmark indieweb.org/bookmark] for examples in the wild.
	** [https://github.com/microformats/h-entry/issues/12 Issue 12]		** [https://github.com/microformats/h-entry/issues/12 Issue 12]

Dshanske: /* Proposed Additions */

2022-08-13T17:36:36Z

Proposed Additions

← Older revision		Revision as of 17:36, 13 August 2022
Line 137:		Line 137:
	* '''<code>u-featured</code>''' - a representative photo or image for the entry, e.g. primary photo for an article or subject-cropped photo, suitable for use in a [[link-preview]].		* '''<code>u-featured</code>''' - a representative photo or image for the entry, e.g. primary photo for an article or subject-cropped photo, suitable for use in a [[link-preview]].
	** +1 sknebel: https://github.com/microformats/h-entry/issues/14		** +1 sknebel: https://github.com/microformats/h-entry/issues/14
	* '''<code>p-latitude</code>''' - latitude of the location of the entry		* Location Properties - https://github.com/microformats/h-entry/issues/29
	* '''<code>p-longitude</code>''' - longitude of the location of the entry		** '''<code>p-latitude</code>''' - latitude of the location of the entry
			** '''<code>p-longitude</code>''' - longitude of the location of the entry
			** '''<code>p-altitude</code>''' - altitude of the location of the entry
	* '''<code>p-duration</code>''' - duration of an audio or video file in the entry. https://indieweb.org/duration Multiple publishers and consumers in the wild; https://github.com/snarfed/granary/issues/169 more background.		* '''<code>p-duration</code>''' - duration of an audio or video file in the entry. https://indieweb.org/duration Multiple publishers and consumers in the wild; https://github.com/snarfed/granary/issues/169 more background.
	** [https://github.com/microformats/h-entry/issues/21 Issue 21]		** [https://github.com/microformats/h-entry/issues/21 Issue 21]