benefits - Revision history

AmeerDawood: /* Easy to add */

2008-11-17T23:50:52Z

Easy to add

← Older revision		Revision as of 23:50, 17 November 2008
Line 20:		Line 20:
	==Easy to add==		==Easy to add==

	The Microformats design process is built around the idea of "paving the cow paths". That means we aim to support common patterns of ~~behaviour~~ so you probably won't have to change that much in your HTML, in most cases it's as easy as adding a few class names to existing elements and a few <span> elements here and there.		The Microformats design process is built around the idea of "paving the cow paths". That means we aim to support common patterns of behavior so you probably won't have to change that much in your HTML, in most cases it's as easy as adding a few class names to existing elements and a few <span> elements here and there.

	Here's a quick example of some contact details in a web page:		Here's a quick example of some contact details in a web page:

GeorgeBrock: added an h1 and a toc

2008-09-10T14:00:35Z

added an h1 and a toc

← Older revision		Revision as of 14:00, 10 September 2008
Line 1:		Line 1:
			<h1> Benefits of using Microformats </h1>
			{{TOC-right}}

	There are many benefits to using Microformats when publishing content on the web. This page provides a summary of some of those benefits.		There are many benefits to using Microformats when publishing content on the web. This page provides a summary of some of those benefits.

GeorgeBrock at 12:30, 10 September 2008

2008-09-10T12:30:29Z

New page

There are many benefits to using Microformats when publishing content on the web. This page provides a summary of some of those benefits.

==Don't repeat yourself==

With Microformats you can publish a single, human readable version of your information in HTML and then make it machine readable with the addition of a few standard class names.

A common example is contact details: If you wanted to publish human- and machine-readable versions without Microformats you would publish an HTML page containing your contact information and a separate machine-readable vCard file that people could automatically import into their address book software. Your information would be stored in two places making it harder to maintain and easier to get out of sync.

Using Microformats you only publish one version of the data, the human-readable HTML version with a few added class names defined by the [[hCard]] Microformat. You could also add a link to an online service to convert your hCard into a vCard file for users to download ([http://technorati.com/contacts/ Technorati] provides a service to do this). When it comes to maintaining your information not only do you only have one copy of it, it's also a copy that you can easily look at in a web browser to see if it's up to date or not.

==You already know HTML==

If you're publishing information online you already know HTML. Microformats allow you to make that your information machine readable without the need to learn a plethora of other languages.

There are Microformats to mark up [[hCard|contact information]], [[hCalendar|event information]] and [[hAtom|episodic web content]]. Without these Microformats you would need to learn three extra languages/vocabularies (vCard, iCalendar and Atom) to get the same benefits.

==Easy to add==

The Microformats design process is built around the idea of "paving the cow paths". That means we aim to support common patterns of behaviour so you probably won't have to change that much in your HTML, in most cases it's as easy as adding a few class names to existing elements and a few elements here and there.

Here's a quick example of some contact details in a web page:

<pre><nowiki>

For more information call John Smith on 0207 123 123
or email <a href="mailto:john.smith@example.org">john.smith@example.org</a>

</nowiki></pre>

Then we add the [[hCard]] Microformat:

<pre><nowiki>

For more information call John Smith on 0207 123 123
or email <a class="email" href="mailto:john.smith@example.org">john.smith@example.org</a>

</nowiki></pre>

It's easy as that. This wiki even provides some helpful [[cheatsheets]] to help you remember the relevant class names.