h-entry

(Difference between revisions)

Jump to: navigation, search
m (Reverted edits by Saymosir (Talk) to last version by ChristopheDucamp)
Line 1: Line 1:
-
'''Essentially the most Lively Singer Taylor Swift is breaking all Records'''
+
<entry-title>h-entry</entry-title>
 +
<span class="h-card vcard"><span class="p-name fn">[[User:Tantek|Tantek Çelik]]</span> (<span class="p-role role">Editor</span>)</span>
 +
----
 +
<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]] draft standards suitable for embedding data in HTML/HTML5.
 +
h-entry is the [[microformats2]] update to [[hAtom]]'s "hentry". For an update to "hfeed" see [[h-feed]].
 +
{{cc0-owfa-license}}
-
One of the most charming and peppy region singer Taylor Swift is great performer. She just mesmerizes every person along with her singing. She tasted the accomplishment at extremely younger age and has stolen hearts of thousands and thousands along with her amazing talent of singing and tune writing. Probably she is the youngest pop singer to generate much of identify and fame in very short time. Taylor Swift songs are very catchy and quickly grab the eye on the listeners. Taylor Swift was born in December 13, 1989 in Looking through, Pennsylvania. At very younger age of nine, she started out executing at neighborhood exhibits and when she turned twelve, she discovered to enjoy guitar and composed her very first track. Taylor Swift received a great opportunity to deal with RCA Documents. After that in addition to her mothers and fathers she moved to Nashville. In 2005, she remaining RCA and joined with Big Equipment Records and started concentrating on her 1st album.
+
== Example ==
 +
Here is a simple blog post example:
 +
<source lang=html4strict>
 +
<article class="h-entry">
 +
  <h1 class="p-name">Microformats are amazing</h1>
 +
  <p>Published by <a class="p-author h-card">W. Developer</a>
 +
    on <time class="dt-published" datetime="2013-06-13 12:00:00">13<sup>th</sup> June 2013</time>
 +
 
 +
  <p class="p-summary">In which I extoll the virtues of using microformats.</p>
 +
 
 +
  <div class="e-content">
 +
    <p>Blah blah blah</p>
 +
  </div>
 +
</article>
 +
</source>
 +
=== Get started ===
 +
The class '''<code>h-entry</code>''' is a ''root class name'' that indicates the presence of an h-entry.
-
Taylor Swift began her advantageous job with her track Tim McGraw from her debut album and was remarkably tremendous accomplishment and assisted her in creating in this particular subject and turned a renowned identify while in the list of effective singers and songwriters in place audio. Taylor Swift has numerous accomplishments in her sleeves like Grammy Awards, CMA Awards, ACM Awards, and American Tunes Awards and so on. Taylor Swift Movies are most seen and her fans are insane about her songs and movies. Taylor Swift Videos are most sought and her fans basically feast to find out her doing so confidently.
+
'''p-name''', '''p-author''', '''dt-published''' and the other h-entry property classnames listed below define properties of the h-entry.
 +
See [[microformats2-parsing]] to learn more about property classnames.
 +
== Properties ==
 +
h-entry properties, inside an element with class '''h-entry''':
 +
* '''<code>p-name</code>''' - entry name/title
 +
* '''<code>p-summary</code>''' - short entry summary
 +
* '''<code>e-content</code>''' - full content of the entry
 +
* '''<code>dt-published</code>''' - when the entry was published
 +
* '''<code>dt-updated</code>''' - when the entry was updated
 +
* '''<code>p-author</code>''' - who wrote the entry, optionally embedded [[h-card]](s)
 +
* '''<code>p-category</code>''' - entry categories/tags
 +
* '''<code>u-url</code>''' - entry permalink URL
 +
* '''<code>u-uid</code>''' - unique entry ID
 +
* '''<code>p-location</code>''' - location the entry was posted from, optionally embed [[h-card]], [[h-adr]], or [[h-geo]]
-
‘Our Song’ her third one tune brought her as rising youngest author and singer within the checklist in the country chart. This song led her to’ Very best New Artist’ nomination at the 2008 Grammy Awards. Taylor Swift 2nd album was unleashed in 2008, “Fearless”. She obtained the huge recognition together with her singles “Love Story” and “You Belong with Me”. “Fearless” turned up to be most strike album in 2009 and was incredibly renowned in her concert tour. This introduced her 4 Grammy Awards and younger diva was presented the title of ‘Album of the Year’ winner. Furthermore, her good results reached at zenith in 2010 and her 3rd album “Speak Now” was unveiled and file breaking offered one particular million copies. The album’s 3rd solitary tune “Mean” bagged her two Grammy Awards. Her rise to success went at peak together with her fourth album “Red”. This album was large hit and broke all information she was introduced together with the tag of very first feminine artist to possess two million furthermore opening weeks. Swift’s singles “We Are Never At any time Obtaining Back again Together” and “I Understood You Have been Trouble” was strike through the globe. In 2013 and 2014, a big live performance tour is scheduled around the world as “Red Tour”.
+
The following experimental properties are in use in the wild but are not yet part of the spec:
 +
* '''<code>u-in-reply-to</code>''' - the URL which the h-entry is considered a reply to or comment on.
 +
** Potentially optionally an embedded (or nested?) h-entry (for reply contexts) but I’m the only one doing that right now so not considered a recommendation --[[User:Barnabywalters|bw]] 16:44, 13 June 2013 (UTC)
 +
* '''<code>p-comment</code>''' - optionally embedded (or nested?) h-entry(ies), each of which is a comment on/reply to the parent h-entry. See [[comment-brainstorming]].
 +
The following properties are proposed additions based on various existing link preview markup conventions which are ''not'' yet used in the wild (Related: [[link-preview-brainstorming]])
 +
* '''<code>u-photo</code>'''
 +
* '''<code>u-audio</code>''' - consider special u- parsing rules for <code>&lt;audio></code>
 +
* '''<code>u-video</code>''' - consider special u- parsing rules for <code>&lt;video></code>
-
Taylor Swift songs are narrative in character and are basically very soulful. Her songs symbolize her ordeals and her lifestyle journey. Her musical journey has thus far been very wonderful. She has acquired seven Grammy Awards, twelve Billboard Tunes Awards, eleven Region Songs Awards, six Academy of Country Songs Award and fifteen American Music Awards. So far all around 26 million albums and 75 million electronic solitary downloads are already approximated that is positive a commendable work. The young tinsel city singer has acted within a light-weight comedy movie in “Valentine’s Day” and has accomplished an animated film “The Lorax”. Taylor Swift is really a philanthropist and supports several human triggers like children literacy, charities for sick children, normal disaster aid and so on. to understand more about your favorite singer and to hear and watch her videos and songs, enthusiasts can simply pay a visit to her official site http://www.taylorswiftsongs.org/
+
All properties are optional.
 +
 
 +
== Status ==
 +
'''h-entry''' is a microformats.org draft specification. Public discussion on h-entry takes place on [[h-entry-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-new/ microformats-new mailing list].
 +
 
 +
h-entry is ready to use and implemented in the wild, but for backwards compatibility you should also mark h-entries up as classic [[hAtom]] entries.
 +
 
 +
== Property Details ==
 +
This section is a stub.
 +
=== p-location ===
 +
'''<code>p-location</code>''' has been re-used from [[h-event]].
 +
 
 +
== FAQ ==
 +
=== p-name of a note ===
 +
<div class="discussion">
 +
* '''What is the <code>p-name</code> of a [http://indiewebcamp.com/note note]?'''
 +
** A few options, from simplest to most detailed.
 +
*** '''same as the p-content/e-content''' property.
 +
*** '''same as the <code>title</code> element''' on the note permalink post page. When publishing a note on its own permalink post page, the contents of the note are likely abbreviated for the title of the page. The same abbreviation can be used for the p-name.
 +
*** '''first sentence of the p-content/e-content''' property. It may be better for [http://indiewebcamp.com/syndication syndication] and [[link-preview]] purposes to provide just the first sentence of the note as the <code>p-name</code>. Similarly if only a portion of the content is syndicated to other sites, that portion can be marked up as the <code>p-summary</code>.
 +
</div>
 +
 
 +
=== venue an entry was posted from ===
 +
<div class="discussion">
 +
* '''How do you indicate a named venue where an entry was posted from? Like a restaurant or park.'''
 +
** Use an embedded [[h-card]] microformat on a <code>p-location</code> property value.
 +
</div>
 +
=== address an entry was posted from ===
 +
<div class="discussion">
 +
* '''How do you indicate the address where an entry was posted from? Like a restaurant or park.'''
 +
** If the address is just part of a named venue, see above, use an [[h-card]]
 +
** Otherwise use an embedded [[h-adr]] microformat on a <code>p-location</code> property value.
 +
</div>
 +
=== lat long an entry was posted from ===
 +
<div class="discussion">
 +
* '''How do you indicate the latitude and longitude of where an entry was posted from?'''
 +
** If the location has a name in addition to latitude and longitude, see above, use an [[h-card]]
 +
** Otherwise if there is an address in addition to latitude and longitude, see above, use an [[h-adr]]
 +
** Otherwise use an embedded [[h-geo]] microformat on a <code>p-location</code> property value.
 +
</div>
 +
 
 +
== Examples in the wild ==
 +
Real world in the wild examples:
 +
 
 +
* ... add uses of h-entry you see in the wild here.
 +
* App.net marks up profile pages and permalink pages with h-entry as of 2013-08-06 ([https://alpha.app.net/voidfiles example])
 +
* The Twitter archive browser UI uses h-entry and h-card internally, unfortunately it’s not exposed as HTML in static files anywhere
 +
* Brett Comnes marks up his posts with h-entry and h-card ([http://bret.io/2013/06/29/getting-started-with-bower/ example])
 +
* Ben Werdmuller marks up his posts with h-card and h-entry, u-in-reply-to and u-like ([http://werd.io/view/51d5097fbed7ded0633a5956 example])
 +
* Sandeep Shetty marks his posts up with h-card and h-entry, as well as draft u-in-reply-to and experimental u-like properties ([http://sandeep.io/101 example])
 +
* spreadly marks up share permalink pages with h-entry, as well as minimal h-cards and experimental p-like properties ([http://my.spread.ly/share/51d570bc09e9486562000002 example])
 +
* Laurent Eschenauer marks up his posts with h-entry ([http://eschnou.com/entry/first-autonomous-flight-of-my-nodecopter-62-24992.html example])
 +
* Tom Morris marks up his posts using h-entry ([http://tommorris.org/posts/8417 example])
 +
* Numerous newer W3C specs, e.g.
 +
** [http://www.w3.org/TR/2013/CR-css3-values-20130404/ CSS Values and Units Module Level 3 - 2013-04-04]
 +
** [http://www.w3.org/TR/2013/CR-css3-conditional-20130404/ CSS Conditional Rules Module Level 3 - 2013-04-04]
 +
** [http://www.w3.org/TR/2013/WD-css3-page-20130314/ CSS Paged Media Module Level 3 - 2013-03-14]
 +
** [http://www.w3.org/TR/2013/WD-css-counter-styles-3-20130221/ CSS Counter Styles Level 3 - 2013-02-21]
 +
* [http://wordpress.org/extend/themes/sempress SemPress] is a WordPress theme that supports h-card, h-feed/h-entry.
 +
* [http://the-pastry-box-project.net/ The Pastry Box Project] use h-card and h-entry markup on their homepage and individual thoughts pages
 +
* Aaron Parecki uses h-entry to mark up notes, e.g. [http://aaronparecki.com/2012/230/reply/1 2012/230/reply/1].
 +
* [http://tantek.com/ Tantek Çelik] uses h-entry on his home page, as well as h-entry on all post permalinks, e.g. [http://tantek.com/2012/243/t1/name-beats-title-modern-use-dubline-core-wrong-uf2 2012-243 post], with [[rel-prev]]/[[rel-next]] (if applicable) to indicate prev/next posts
 +
* [http://waterpigs.co.uk/ Barnaby Walters] uses h-entry on all notes and articles, as well as nested within notes as reply contexts [http://waterpigs.co.uk/notes/1468/ example] and comments [http://waterpigs.co.uk/notes/1482/ example].
 +
 
 +
== Validating ==
 +
* '''[http://indiewebify.waterpigs.co.uk/validate-h-entry/ indiewebify.me h-entry validator]''' parses [[h-entry]] markup, finds common errors and makes suggestions for things to add, with code samples
 +
{{h-spec-section-validating}}
 +
 
 +
== Backward Compatibility ==
 +
=== Publisher Compatibility ===
 +
For backward compatibility, you may wish to use classic [[hAtom]] classnames in addition to the more future-proof h-entry properties, for example:
 +
 
 +
<source lang=html4strict>
 +
<div class="h-entry hentry">
 +
  <h1 class="p-name entry-title">My great blog post</h1>
 +
</div>
 +
</source>
 +
 
 +
=== Parser Compatibility ===
 +
Microformats parsers {{should}} detect classic properties only if a classic root class name is found and parse them as microformats2 properties.
 +
 
 +
If an "h-entry" is found, don't look for an "hentry" on the same element.
 +
 
 +
Compat root class name: <code id="hentry">hentry</code><br/>
 +
Properties: (parsed as '''p-''' plain text unless otherwise specified):
 +
 
 +
* <code>entry-title</code> - parse as '''<code>p-name</code>'''
 +
* <code>entry-summary</code> - parse as '''<code>p-summary</code>'''
 +
* <code>entry-content</code> - parse as '''<code>e-content</code>'''
 +
* <code>published</code> - parse as '''dt-'''
 +
* <code>updated</code> - parse as '''dt-'''
 +
* <code>author</code> - including compat root <code>vcard</code> in the absence of <code>h-card</code>
 +
* <code>category</code>
 +
 
 +
=== Compat FAQ ===
 +
==== What about rel bookmark ====
 +
Also asked as: ''Why use an h-entry u-url u-uid for permalinks when I have [[rel-bookmark|rel=bookmark]]?''
 +
 
 +
A: tl;dr: use <code>class="u-url u-uid"</code> instead of <code>rel=bookmark</code> for post permalinks because it's simpler (fewer attributes), and works better across contexts (permalink page, recent posts on home page, collection of posts on archive pages).
 +
 
 +
rel=bookmark was the old [[hAtom]] way of marking up permalinks. Since then two factors have contributed to reducing use of rel inside microformats:
 +
* rel by typically* document scoped in [[HTML5]] - thus making it inappropriate for use in microformats that are aggregated, e.g. a collection of posts on a home page or in monthly archives.
 +
* it is easier to always use class names for properties. When formats use two (or more!) attributes in HTML to specify properties, confusion results in lower data quality (of the markup and thus the stuff that is marked up). Thus per the microformats [[principle]] of [[simplicity]], in [[microformats2]] we only use class names for properties.
 +
 
 +
<nowiki>*</nowiki> even though rel=bookmark in particular is article-element / sectioning scoped in HTML5[http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#link-type-bookmark], it's a detail that typical authors are not going to remember, and thus it's not good to depend on it for any kind of format.
 +
 
 +
== Background ==
 +
This work is based on the existing [[hAtom]] microformat, and extensive selfdogfooding in the [http://indiewebcamp.com indie web camp] community.
 +
 
 +
== Design Principles ==
 +
 
 +
(stub, expand)
 +
 
 +
== See Also ==
 +
* [[h-feed]]
 +
* [[microformats2]]
 +
* [[microformats2-parsing]]
 +
* [[h-geo]]
 +
* [[hCard]]
 +
 
 +
[[Category:Draft Specifications]]

Revision as of 14:26, 1 January 2014

Tantek Çelik (Editor)


h-entry 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 microformat draft standards suitable for embedding data in HTML/HTML5.

h-entry is the microformats2 update to hAtom's "hentry". For an update to "hfeed" see h-feed.

Per CC0, to the extent possible under law, the editors have waived all copyright and related or neighboring rights to this work. In addition, as of 2019-08-18, the editors have made this specification available under the Open Web Foundation Agreement Version 1.0.

Contents

Example

Here is a simple blog post example:

<article class="h-entry">
  <h1 class="p-name">Microformats are amazing</h1>
  <p>Published by <a class="p-author h-card">W. Developer</a>
     on <time class="dt-published" datetime="2013-06-13 12:00:00">13<sup>th</sup> June 2013</time>
 
  <p class="p-summary">In which I extoll the virtues of using microformats.</p>
 
  <div class="e-content">
    <p>Blah blah blah</p>
  </div>
</article>

Get started

The class h-entry is a root class name that indicates the presence of an h-entry.

p-name, p-author, dt-published and the other h-entry property classnames listed below define properties of the h-entry.

See microformats2-parsing to learn more about property classnames.

Properties

h-entry properties, inside an element with class h-entry:

The following experimental properties are in use in the wild but are not yet part of the spec:

The following properties are proposed additions based on various existing link preview markup conventions which are not yet used in the wild (Related: link-preview-brainstorming)

All properties are optional.

Status

h-entry is a microformats.org draft specification. Public discussion on h-entry takes place on h-entry-feedback, the #microformats irc channel on irc.freenode.net, and microformats-new mailing list.

h-entry is ready to use and implemented in the wild, but for backwards compatibility you should also mark h-entries up as classic hAtom entries.

Property Details

This section is a stub.

p-location

p-location has been re-used from h-event.

FAQ

p-name of a note

  • What is the p-name of a note?
    • A few options, from simplest to most detailed.
      • same as the p-content/e-content property.
      • same as the title element on the note permalink post page. When publishing a note on its own permalink post page, the contents of the note are likely abbreviated for the title of the page. The same abbreviation can be used for the p-name.
      • first sentence of the p-content/e-content property. It may be better for syndication and link-preview purposes to provide just the first sentence of the note as the p-name. Similarly if only a portion of the content is syndicated to other sites, that portion can be marked up as the p-summary.

venue an entry was posted from

  • How do you indicate a named venue where an entry was posted from? Like a restaurant or park.
    • Use an embedded h-card microformat on a p-location property value.

address an entry was posted from

  • How do you indicate the address where an entry was posted from? Like a restaurant or park.
    • If the address is just part of a named venue, see above, use an h-card
    • Otherwise use an embedded h-adr microformat on a p-location property value.

lat long an entry was posted from

  • How do you indicate the latitude and longitude of where an entry was posted from?
    • If the location has a name in addition to latitude and longitude, see above, use an h-card
    • Otherwise if there is an address in addition to latitude and longitude, see above, use an h-adr
    • Otherwise use an embedded h-geo microformat on a p-location property value.

Examples in the wild

Real world in the wild examples:

Validating

Main article: validators

Test and validate microformats2 markup in general with:

Backward Compatibility

Publisher Compatibility

For backward compatibility, you may wish to use classic hAtom classnames in addition to the more future-proof h-entry properties, for example:

<div class="h-entry hentry">
  <h1 class="p-name entry-title">My great blog post</h1>
</div>

Parser Compatibility

Microformats parsers SHOULD detect classic properties only if a classic root class name is found and parse them as microformats2 properties.

If an "h-entry" is found, don't look for an "hentry" on the same element.

Compat root class name: hentry
Properties: (parsed as p- plain text unless otherwise specified):

Compat FAQ

What about rel bookmark

Also asked as: Why use an h-entry u-url u-uid for permalinks when I have rel=bookmark?

A: tl;dr: use class="u-url u-uid" instead of rel=bookmark for post permalinks because it's simpler (fewer attributes), and works better across contexts (permalink page, recent posts on home page, collection of posts on archive pages).

rel=bookmark was the old hAtom way of marking up permalinks. Since then two factors have contributed to reducing use of rel inside microformats:

* even though rel=bookmark in particular is article-element / sectioning scoped in HTML5[1], it's a detail that typical authors are not going to remember, and thus it's not good to depend on it for any kind of format.

Background

This work is based on the existing hAtom microformat, and extensive selfdogfooding in the indie web camp community.

Design Principles

(stub, expand)

See Also

Categories

h-entry was last modified: Wednesday, December 31st, 1969

Views