Main Page: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
(add see blog / feed at the top since domain home page redirects here now, float TOC to right)
 
(260 intermediate revisions by more than 100 users not shown)
Line 1: Line 1:
<entry-title>Welcome to the microformats wiki!</entry-title>
{{DISPLAYTITLE:Welcome to the microformats wiki!}}
__TOC__
Please start with the [[introduction]] page and read [[how-to-play]] before making any edits.


Why the 5.7 Hemi is One of the Best Dodge Engines Ever Made
'''<dfn>microformats</dfn>''' are HTML for marking up [[h-card|people, organizations]], [[h-event|events]], [[h-adr|locations]], [[h-entry|blog posts]], [[h-product|products]], [[h-review|reviews]], [[h-resume|resumes]], [[h-recipe|recipes]] etc. Sites use microformats to publish a standard API that is consumed and used by [[search engines]], [[browsers]], and other web sites. See [[what-are-microformats]] for more.


When people think of Dodge, they tend to immediately think of the most legendary of Dodge Engines: the Hemi. While the old-school Hemi from nearly a quarter-century ago was renowned around the world for its jaw-dropping brute force that could catapult full-sized cars through the quarter mile faster than you can say “Hemi”, it was not necessarily known as a fuel-efficient motor. The new 5.7L Hemi, released in 2003 is a completely different story, and it has already gone down in history as one of the very best Dodge engines. In fact, it would not be a stretch to say that many performance enthusiasts would agree that the modern Hemi is probably one of the best high-performance engines on the planet.
* See '''[[microformats2]]''' for a technical overview and summary of how to use microformats on public web pages and for APIs.


What makes the 5.7L Hemi one of the best <a href=http://www.lowmileageengines.com/used-engines/dodge/>Dodge engines</a> ever? There are three primary factors: power, reliability, and efficiency. Combined, these three factors make the modern Hemi a world-class engine, and serve as a shining example of what Dodge engines can do when given the chance.
If you are looking for the '''microformats.org blog''', see:
* https://microformats.org/blog ([https://microformats.org/feed RSS feed])
<span style="float:right">__TOC__</span>
==Introduction==
{{main|introduction|Introduction}}
This wiki is the central resource of the microformats community and provides microformats authoring guides, references, specifications, drafts, publishing patterns, research, brainstorming, and issue tracking.


The modern Hemi is powerful enough to actually replace not only the outgoing 5.9L Magnum engines in many Dodge/Chrysler vehicles, but also to replace the legendary 8.0L V10 that powered some of the most impressive Dodge pickup trucks of the 1990s and early 2000s. Depending on how it is tuned, the modern 5.7L Hemi can have over 360 horsepower and nearly 400 lb-ft of torque on tap, most of which at a very wide rpm-range that starts just shy of the 2000-rpm mark. For this reason alone many muscle car enthusiasts have taken a real liking to the 5.7L Hemi, and more than one old-school Challenger has gotten a new lease on life thanks to one of the best Dodge engines ever created.
== Get Started==
{{main|get-started|Getting Started}}
Get started with microformats:


Of course, muscle cars of 60s and 70s were not famous for their reliability. A large part of the problem had to do with the titanic force that their engines were putting to the pavement via oversized tires and transmissions that were struggling to keep up. Nowhere was this more true than with the earliest Dodge engines to bear the Hemi-moniker; the bottom line was that these motors were just too powerful for their own good and all that power caused undue stress on a number of components both inside and outside of the old-school Hemi block.
* Make sure your pages and web apps use proper ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.
* Mark-up your contact info with [[h-card]], link to other profiles with [[rel-me]]
* Mark-up your blog with [[h-entry]]. See https://indieweb.org/ for more
* Questions? Read the [[faq|frequently asked questions]], ask on [[IRC]]
* Want to learn more in person? Check out microformats [[events]]


Oh have times have changed. The new 5.7L Hemi is far more refined than the old Hemi in terms of reliability, and car-making in general has come a long ways in the past few decades. The results are that the latest Dodge engines to proudly carry the Hemi-badge are so reliable that they have been listed on Ward’s 10 Best Engines list for six out of seven years. The Ward’s 10 Best Engines list covers engines produced by all major automobile vendors with a global reach, which includes all of the major Asian and European automakers. With competition like that, it is impressive that not only has a Dodge engine won a slot on that list consistently, but that the list favors reliability above all else.
== How to contribute ==
Want to join in and contribute?


The MDS (Multi-Displacement System) in the modern Hemi also makes it very efficient and easy to drive in day-to-day situations. Who ever thought that anyone would say that about one of the fiercest Dodge engines ever made? The bottom line is that the new Hemi sets the standards not only for Dodge engines in general, but for engines around the world.  
* [[get-started|Get started]] by adding microformats to your website, services, and products
* Join the [[irc|IRC Channel]] to learn and help answer questions.
* Write a [[testimonial]]
* Do something on the [[to-do|to do list]].
* [[Main_Page#microformats_wiki_translations|Translate this microformats wiki into other languages]] to make microformats more accessible to readers of languages around the world.
* Before proposing any new microformats, make sure your website is [[POSH]], [[get-started|uses existing microformats]], and then read the [[process]].


Anyone looking for replacement <a href=http://www.lowmileageengines.com/used-engines/dodge/>Used Dodge engine</a> could do a lot worse than to look at the powerful, reliable, and efficient Hemi.
This wiki has a number of enhancements to assist development and contributions to microformats. Before you start editing, see the [[wiki-2|wiki introduction page]] for instructions.


Why the 5.7 Hemi is One of the Best Dodge Engines Ever Made
== Specifications ==
'''[[microformats2]]''' is stable, has a test suite, publishers, and interoperable implementations. Use it on public web pages and developing more parsers and applications.


When people think of Dodge, they tend to immediately think of the most legendary of Dodge Engines: the Hemi. While the old-school Hemi from nearly a quarter-century ago was renowned around the world for its jaw-dropping brute force that could catapult full-sized cars through the quarter mile faster than you can say “Hemi”, it was not necessarily known as a fuel-efficient motor. The new 5.7L Hemi, released in 2003 is a completely different story, and it has already gone down in history as one of the very best Dodge engines. In fact, it would not be a stretch to say that many performance enthusiasts would agree that the modern Hemi is probably one of the best high-performance engines on the planet.
Current, stable microformats open standard specifications.


What makes the 5.7L Hemi one of the best Dodge engines ever? There are three primary factors: power, reliability, and efficiency. Combined, these three factors make the modern Hemi a world-class engine, and serve as a shining example of what Dodge engines can do when given the chance.
=== Parsing ===
If you are implementing a microformats2 parser, see:
* [[microformats2-parsing]]


The modern Hemi is powerful enough to actually replace not only the outgoing 5.9L Magnum engines in many Dodge/Chrysler vehicles, but also to replace the legendary 8.0L V10 that powered some of the most impressive Dodge pickup trucks of the 1990s and early 2000s. Depending on how it is tuned, the modern 5.7L Hemi can have over 360 horsepower and nearly 400 lb-ft of torque on tap, most of which at a very wide rpm-range that starts just shy of the 2000-rpm mark. For this reason alone many muscle car enthusiasts have taken a real liking to the 5.7L Hemi, and more than one old-school Challenger has gotten a new lease on life thanks to one of the best Dodge engines ever created.
=== Vocabularies ===
microformats2 vocabularies:
* [[h-adr]]
* [[h-card]]
* [[h-entry]]
* [[h-event]]
* [[h-feed]]
* [[h-geo]]
* [[h-item]]
* [[h-listing]]
* [[h-product]]
* [[h-recipe]]
* [[h-resume]]
* [[h-review]]
* [[h-review-aggregate]]


Of course, muscle cars of 60s and 70s were not famous for their reliability. A large part of the problem had to do with the titanic force that their engines were putting to the pavement via oversized tires and transmissions that were struggling to keep up. Nowhere was this more true than with the earliest Dodge engines to bear the Hemi-moniker; the bottom line was that these motors were just too powerful for their own good and all that power caused undue stress on a number of components both inside and outside of the old-school Hemi block.
=== rel microformats ===
Some microformats require only a rel attribute and are widely supported by consuming sites and software.
* [[rel-author]] - link to the author's home page (from an article)
* [[rel-enclosure]] - link to attachments (e.g. files) to download and cache
* [[rel-license]] - licensed content
* [[rel-nofollow]] - links in untrusted 3rd party content
* [[rel-tag]] - tag posts and pages by subject
* [[XFN]] - social relationships and [[rel-me]] links among profiles for the same person


Oh have times have changed. The new 5.7L Hemi is far more refined than the old Hemi in terms of reliability, and car-making in general has come a long ways in the past few decades. The results are that the latest Dodge engines to proudly carry the Hemi-badge are so reliable that they have been listed on Ward’s 10 Best Engines list for six out of seven years. The Ward’s 10 Best Engines list covers engines produced by all major automobile vendors with a global reach, which includes all of the major Asian and European automakers. With competition like that, it is impressive that not only has a Dodge engine won a slot on that list consistently, but that the list favors reliability above all else.  
=== Classic Microformats ===
In addition use well established classic microformats for the primary subject of a page for legacy [[search engines]] support.


The MDS (Multi-Displacement System) in the modern Hemi also makes it very efficient and easy to drive in day-to-day situations. Who ever thought that anyone would say that about one of the fiercest Dodge engines ever made? The bottom line is that the new Hemi sets the standards not only for Dodge engines in general, but for engines around the world.
* [[hatom|hAtom]] - blog posts and other date-stamped content
* [[hcalendar|hCalendar]] - events
* [[hcard|hCard]] - people, organizations, contacts
* [[hlisting|hListing]] - listings for products or services
* [[hmedia|hMedia]] - media info about images, video, audio
* [[hproduct|hProduct]] - products
* [[hrecipe|hRecipe]] - cooking+baking recipes
* [[hresume|hResume]] - individual resumes and CVs
* [[hreview|hReview]] - individual reviews and ratings
* [[hreview-aggregate|hReview-aggregate]] - aggregate reviews and ratings


Anyone looking for replacement Used Dodge engine could do a lot worse than to look at the powerful, reliable, and efficient Hemi.
* [[adr|adr]] - address location information
* [[geo|geo]] - latitude &amp; longitude location ([http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates)


==Definition==
==== Classic Drafts ====
Microformats are small patterns of HTML to represent commonly published things like [[hcard|people]], [[hcalendar|events]], [[hatom|blog posts]], [[hreview|reviews]] and [[rel-tag|tags]] in web pages.
Drafts are classic microformats which have varying degrees of support by consuming applications. They are stable and yet still open to change based on consuming application support, per the [[process]] to become specifications.


Microformats enable the publishing of higher fidelity information on the Web; the fastest and simplest way to provide feeds and APIs for the information in your website.
* [[hnews|hNews]] - news articles, extension of hAtom


* Read more explanations of [[what-are-microformats|what microformats are]], and [[what-can-you-do-with-microformats|what you can do with them]].
* [[rel-home]] - link to the homepage of a site
* [[rel-payment]] - link to a payment mechanism


== How to contribute ==
* [[XMDP]] - define a microformat vocabulary / profile
Do you want to help take microformats to the next level?  You can:
* [[xoxo|XOXO]] - outlines


* [[get-started|Get started]] by adding microformats to your website, services, and products.
''If you're tempted to try your hand at writing a microformat please read '''[[process|the process]]''' page first!'' and then take a look at [[exploratory-discussions]] for details of prior research, analysis of real-world [[examples]], existing formats, and brainstorming of possible new microformats, per the microformats [[process]].
* [[advocacy|Advocate]] the use of microformats on other web sites, especially those you use.
* Write a [[testimonial]].
* Do something on the [[to-do|to do list]].
* Join the [[irc|IRC Channel]] and [[mail|mailing lists]] to learn and help answer questions (read the [[mailing-lists#General_guidelines|general guidelines]] before posting).
* [[Main_Page#microformats_wiki_translations|Translate this microformats wiki into other languages]] to make microformats more accessible to readers of languages around the world.
* Before proposing any new microformats, make sure your website is [[POSH]], [[get-started|uses existing microformats]], and then read the [[process]].


This wiki has a number of enhancements to assist development and contributions to microformats. Before you start editing, see the [[wiki-2|wiki introduction page]] for instructions.
== Design Patterns ==
{{design_patterns}} <!-- this can be edited in /wiki/Template:design_patterns -->


== Specifications ==
== Archived ==
The list of current, stable [[microformats|Microformats]] open standard specifications.
Past specifications, drafts, and exploratory discussions which have either lacked (or lost) wide publishing support, implementation, or have been superceded by newer specs (see also [[process#related_issues_questions_regarding_document_stages|when does it make sense to demote a microformat spec]]). These may eventually be retired, deprecated, or reincorporated into other exploratory discussions.
 
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]
* [[XMDP]]
* [[xoxo|XOXO]]
 
''If you're tempted to try your hand at writing a microformat please read '''[[process|the process]]''' page first!''
 
== Drafts ==
Drafts are newer microformats, for which the specifications haven't been completed yet. Drafts are somewhat mature in the development [[process]] (see [[exploratory-discussions]] for additional efforts that are not as far along in the process). The stability of these documents cannot be guaranteed, and implementers should be prepared to keep abreast of future developments and changes. Please watch the wiki pages for updates.
 
* [[adr|adr]] - for marking up address information
* [[geo|geo]] - for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates (latitude; longitude)
* [[hatom|hAtom]] - syndicating episodic content (e.g. weblog postings)
* [[haudio|hAudio]]
* [[haudio|hAudio]]
* [[hlisting|hListing]] - open, distributed listings
* [[hmedia|hMedia]] - A single media publishing format that relates to Images, Video and Audio.
* [[hnews|hNews]]
* [[hproduct|hProduct]]
* [[hrecipe|hRecipe]] - for cooking+baking recipes
* [[hresume|hResume]] - for publishing resumes and CVs
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page
* [[rel-enclosure]] - for indicating attachments (e.g. files) to download and cache
* [[rel-home]] - indicate a hyperlink to the homepage of the site
* [[rel-payment]] - indicate a payment mechanism
* [[robots-exclusion|robots exclusion]]
* [[robots-exclusion|robots exclusion]]
* [[xfolk|xFolk]] - tagged links


* [[xfolk|xFolk]]
* [[rel-directory]] - link to web directories
 
* [[vote-links|VoteLinks]]
== Design Patterns ==
{{design_patterns}} <!-- this can be edited in /wiki/Template:design_patterns -->
 
== Exploratory Discussions ==
See: [[exploratory-discussions]] for details of research and analysis of real-world [[examples]], existing formats, and brainstorming of possible new microformats, per the microformats [[process]].


== Examples ==
== Examples ==
Line 110: Line 122:
*[[data-portability]]
*[[data-portability]]
*[[social-network-portability]]
*[[social-network-portability]]
*[http://indiewebcamp.com/ indieweb]


== Shared work areas ==
== Shared work areas ==
Line 121: Line 134:
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting [[tools|tools and services]] that need to process more than one microformat. That section is intended for editors, [[parsers]], [[validators]], test cases, and other information relevant across multiple microformats.
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting [[tools|tools and services]] that need to process more than one microformat. That section is intended for editors, [[parsers]], [[validators]], test cases, and other information relevant across multiple microformats.


<span id="microformats_wiki_translations"><span id="microformats_wiki_translations_in_other_languages">&nbsp;</span></span>
== Microformats wiki translations ==
== Microformats wiki translations ==
<span id="microformats_wiki_translations_in_other_languages">You may read and edit microformats articles in many other languages:</span>
You may read and edit microformats articles in many other languages:


* languages with over 100 articles
* languages with over 100 articles
** [[Main_Page-fr|<span lang="fr">Français</span> (French)]] <span lang="fr">{{UpdateMarker-fr}}</span>
** [[Main_Page-fr|<span lang="fr">Français</span> (French)]] <span lang="fr">{{UpdateMarker-fr}}</span>
* languages with over 10 articles
* languages with over 10 articles
** [[Main_Page-ja|<span lang="ja">日本語</span> (Japanese)]]
** [[Main_Page-pt-br|<span lang="pt-br">Português</span> (Brazilian Portuguese)]]
** [[Main_Page-pt-br|<span lang="pt-br">Português</span> (Brazilian Portuguese)]]
** [[Main_Page-ja|<span lang="ja">日本語</span> (Japanese)]]
** [[Main_Page-ru|<span lang="ru">Русский</span> (Russian)]]
** [[Main_Page-ru|<span lang="ru">Русский</span> (Russian)]]
* languages with over 2 articles
* languages with over 2 articles
** [[Main_Page-cs|<span lang="cs">Česky</span> (Czech)]] {{NewMarker}}
** [[Main_Page-cs|<span lang="cs">Česky</span> (Czech)]]
** [[Main_Page-zh|<span lang="zh">汉语</span> (Chinese)]]
** [[Main_Page-de|<span lang="de">Deutsch</span> (German)]]
** [[Main_Page-de|<span lang="de">Deutsch</span> (German)]]
** [[Main_Page-es|<span lang="es">Español</span> (Spanish)]]
** [[Main_Page-es|<span lang="es">Español</span> (Spanish)]]
** [[Main_Page-gl|<span lang="gl">Galego</span> (Galician)]] {{NewMarker}}
** [[Main_Page-gl|<span lang="gl">Galego</span> (Galician)]]  
** [[Main_Page-id|<span lang="id">Indonesia</span> (Bahasa Indonesia)]]
** [[Main_Page-pl|<span lang="pl">Polski</span> (Polish)]]
** [[Main_Page-pl|<span lang="pl">Polski</span> (Polish)]]
** [[Main_Page-ro|<span lang="ro">Română</span> (Romanian)]] {{NewMarker}}
** [[Main_Page-ro|<span lang="ro">Română</span> (Romanian)]]
** [[Main_Page-zh|<span lang="zh">汉语</span> (Chinese)]]
** [[Main_Page-id|<span lang="id">Indonesia</span> (Bahasa Indonesia)]] {{NewMarker}}
* languages just started
* languages just started
** [[Main_Page-fa|<span lang="fa">پارسی</span> (Farsi)]] {{NewMarker}}
** [[Main_Page-ar|<span lang="ar">العربية</span> (Arabic)]]
** [[Main_Page-ar|<span lang="ar">العربية</span> (Arabic)]]
** [[Main_Page-fa|<span lang="fa">پارسی</span> (Farsi)]]
** [[Main_Page-ka|<span lang="ka">ქართული</span> (Georgian)]] {{NewMarker}} <!-- 2013 -->
** [[Main_Page-it|<span lang="it">Italiano</span> (Italian)]]
** [[Main_Page-ko|<span lang="ko">한국어</span> (Korean)]]
** [[Main_Page-th|<span lang="th">ภาษาไทย</span> (Thai)]]
** [[Main_Page-th|<span lang="th">ภาษาไทย</span> (Thai)]]
** [[Main_Page-it|<span lang="it">Italiano</span> (Italian)]] {{NewMarker}}
** [[Main_Page-tr|<span lang="tr">Türkçe</span> (Turkish)]] {{NewMarker}} <!-- 2012-328 -->
** [[Main_Page-ko|<span lang="ko">한국어</span> (Korean)]] {{NewMarker}}
* elsewhere
* elsewhere
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] has been translated into a number of languages.
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] has been translated into a number of languages.


See also [[other-languages]], and [[how-to-start-new-translation|how-to-start-a-new-translation]].
See also [[other-languages]], and [[how-to-start-new-translation|how-to-start-a-new-translation]].
== community ==
<span class="h-card"><strong class="p-name p-org">microformats.org</strong> is <span class="p-note">a community focused on using an empirical (rather than aspirational) [[process]] to research web data & information human publishing behaviors, openly document it on our wiki (<span class="p-url p-uid">http://microformats.org/wiki/</span>), discuss it in [[IRC]] (<span class="p-url">irc://irc.freenode.net/microformats</span>), then brainstorm ideas & proposals based on that research for simple formats based on HTML to interoperably represent that information on the web, incrementally implement, and iterate.</span></span>

Latest revision as of 20:37, 12 September 2024


microformats are HTML for marking up people, organizations, events, locations, blog posts, products, reviews, resumes, recipes etc. Sites use microformats to publish a standard API that is consumed and used by search engines, browsers, and other web sites. See what-are-microformats for more.

  • See microformats2 for a technical overview and summary of how to use microformats on public web pages and for APIs.

If you are looking for the microformats.org blog, see:

Introduction

Main article: introduction

This wiki is the central resource of the microformats community and provides microformats authoring guides, references, specifications, drafts, publishing patterns, research, brainstorming, and issue tracking.

Get Started

Main article: get-started

Get started with microformats:

How to contribute

Want to join in and contribute?

This wiki has a number of enhancements to assist development and contributions to microformats. Before you start editing, see the wiki introduction page for instructions.

Specifications

microformats2 is stable, has a test suite, publishers, and interoperable implementations. Use it on public web pages and developing more parsers and applications.

Current, stable microformats open standard specifications.

Parsing

If you are implementing a microformats2 parser, see:

Vocabularies

microformats2 vocabularies:

rel microformats

Some microformats require only a rel attribute and are widely supported by consuming sites and software.

  • rel-author - link to the author's home page (from an article)
  • rel-enclosure - link to attachments (e.g. files) to download and cache
  • rel-license - licensed content
  • rel-nofollow - links in untrusted 3rd party content
  • rel-tag - tag posts and pages by subject
  • XFN - social relationships and rel-me links among profiles for the same person

Classic Microformats

In addition use well established classic microformats for the primary subject of a page for legacy search engines support.

  • adr - address location information
  • geo - latitude & longitude location (WGS84 geographic coordinates)

Classic Drafts

Drafts are classic microformats which have varying degrees of support by consuming applications. They are stable and yet still open to change based on consuming application support, per the process to become specifications.

  • hNews - news articles, extension of hAtom
  • XMDP - define a microformat vocabulary / profile
  • XOXO - outlines

If you're tempted to try your hand at writing a microformat please read the process page first! and then take a look at exploratory-discussions for details of prior research, analysis of real-world examples, existing formats, and brainstorming of possible new microformats, per the microformats process.

Design Patterns

Design patterns are common uses of markup across microformats.

Archived

Past specifications, drafts, and exploratory discussions which have either lacked (or lost) wide publishing support, implementation, or have been superceded by newer specs (see also when does it make sense to demote a microformat spec). These may eventually be retired, deprecated, or reincorporated into other exploratory discussions.

Examples

Resources

See resources.

User centric development

Shared work areas

Tools, test cases, additional research

The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. That section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.

 

Microformats wiki translations

You may read and edit microformats articles in many other languages:

See also other-languages, and how-to-start-a-new-translation.

community

microformats.org is a community focused on using an empirical (rather than aspirational) process to research web data & information human publishing behaviors, openly document it on our wiki (http://microformats.org/wiki/), discuss it in IRC (irc://irc.freenode.net/microformats), then brainstorm ideas & proposals based on that research for simple formats based on HTML to interoperably represent that information on the web, incrementally implement, and iterate.

Retrieved from "http://microformats.org/wiki/index.php?title=Main_Page&oldid=70705"