Search Engine Advertising Marketing 1-818-501-3646

Get Started microformats FN Getting started with microformats is easy. Here’s a simple guide to help you on your way.
Microformats are simple ways to add information to a web page using mostly the class attribute (although sometimes the id, title, rel or rev attributes too). The class names are semantically rich and describe the data they encapsulate.
Using microformats makes your data easy to consume and publish in a standardized way, so that you can do things like make your data available for indexing, searching or to do tasks like download a contact’s information or add an event to your calendar simply.
Your first microformat in 5 minutes or less!
You can put a microformat on your website in less than five minutes.The following three steps will take you through the process of puttingan hCard – your online business card – on your site.
1. Find your name somewhere on your website
The best place is a part of your site that’s the same on everypage. If you have a blog, the footer template or sidebar is usually agood place to start. However, you can always test microformats out ina regular blog post.
2. Wrap your name in an “fn”
The “fn” class indicates that this is your “formatted name”. If you have a complex name (more than just first and last), see these examples for more information on how to structure your name.
Jamie Jones
This example shows a span element because it will work almost anywhere on the webpage, but you can and should use the most appropriate element for your use-case.
3. Wrap it all in a “vcard”
The “vcard” class declares that everything inside is the hCardmicroformat:
Jamie Jones
Again, we used a “span” element because this is a basic, versatile, element - but if your use-case was for your information on your website that you’ve built and the point of contact, the address element would be more appropriate.

Jamie Jones

The address element indicates that the person in the hCard is the contact for the page (or a major portion thereof).
Or perhaps you’re using your name in a statement about you. You may want something more like this:

Hi, my name is Jamie Jones and I dig microformats!

Congratulations! You now have a basic microformat on your website! Now that you’ve had your first experience with microformats, here are some next steps:
Add more information to your hCard
Link to your friends and contacts with XFN
Add events to your site with hCalendar
Review movies, books, and more with hReview
Still confused? Don’t worry - you can talk to some real people about your problems either on our IRC channel or on our mailing lists.
Marketing Advertising Directory

Latest microformats news
Value Class Pattern
The value-class-pattern solves two of the three most challenging issues that microformats have encountered in their entire history: accessibility and localization.
After many long months of focused iterating (repeatedly researching, brainstorming, testing, documenting) led by Ben Ward, the value-class-pattern alpha draft is ready to use and support.
Publish and implement
Several publishers have already started using the value-class-pattern, including this blog, and some implementations have already started supporting it as well.
Everyone who publishes content marked up with microformats or develops microformats implementations such as parsers and authoring tools should take a close look at supporting the value-class-pattern in the content they are publishing and the tools they are implementing. In particular:
If your implementation parses hCalendar, hReview, or hAtom, please implement the value-class-pattern in your parser, test it with the examples given both in the spec and the growing list of value-class-pattern examples in the wild, and add it to the list of value-class-pattern implementations.
If your site publishes hCalendar, hReview, or hAtom, please use the value-class-pattern for your dates and times, and add your site to the growing list of value-class-pattern examples in the wild.
If your implementation generates hCalendar, hReview, or hAtom, please generate your dates and times marked up with the value-class-pattern, and add your implementation to the list of value-class-pattern implementations.
If and when you encounter any issues or have feedback regarding the value-class-pattern, please add them to the value-class-pattern-issues and value-class-pattern-feedback pages respectively.
Major resolutions and minor revisions
The value-class-pattern has greatly addressed accessibility and authoring issues across several microformats, in particular for typical uses of dates and times. However, there are still a few open issues on specific microformats for which we are still exploring better (more semantic, more accessible) solutions, in particular the geo microformat (and property of hCard) when specified as a single hyperlink or abbreviation, and hCalendar’s dtend property when specifying a whole date (rather than a specific datetime).
With the value-class-pattern providing solutions to two out of the three biggest microformats challenges (the last of the three to be addressed in its own blog post), and resolutions to the remaining substantial open issues (e.g. as mentioned) on hCard, hCalendar, hReview, and hAtom, we will work on 1.0.1 revisions that:
incorporate said resolved substantial issues to date
require support of the value-class-pattern
are edited for broader understandability and usability.
The editors of all drafts, in development, and future compound microformats should also require support of the value-class-pattern in order to encourage better accessibility in content that is marked up with microformats.
Acknowledgments
Thanks to those in the broader accessibility and internationalization communities that have kept up with their constructive criticisms, suggestions, test cases, testing, test results documentation, feedback, and overall participation. Your efforts have contributed to major improvements in microformats, and we could not have done it without you and your expertise. In particular:
The original Web Standards Project article hAccessibility by Bruce Lawson and James Craig which provided both detailed documentation of real world concrete problems that were/are being experienced due to some uses of the abbr element with microformats, as well as several ideas for alternatives to explore. Many of those ideas formed the basis for what the microformats community spent many months investigating in depth, testing, iterating, evolving and eventually narrowing down and refining into what made it into the value-class-pattern (e.g. value-title in particular).
Everyone who has contributed documentation of patterns, issues, brainstorms, opinions regarding the abbr element, dates, datetimes, accessibility, assistive technology, internationalization/localization, etc. to the microformats wiki. All these additions to our broader body of knowledge helped shape and refine the value-class-pattern you see today.
In particular I want to thank James Craig for the many hours he spent extensively testing and documenting of several alternatives with screen readers.
Personally I have very much appreciated Derek Featherstone’s optimism regarding microformats and accessibility, consistent in-person encouragement to me and others to keep working at it, and continued positive reminding to keep in mind the broader community of those that use the Web.
Finally, thanks to all of the authors, designers, and developers supporting microformats, especially those who continued to do so when well aware of accessiblity and other open issues, for their patience and for never giving up.
Related
@microformats announcement of value-class-pattern
Ben Ward’s “value-class-pattern call for implementations” post to microformats-dev.
May 12th, 2009
Tantek
1 Comment
1 blog reaction
Marketing Advertising Directory

Hi, my name is Emil Cohen and I dig microformats!

Social Networking Websites.
Marking up structured dataPrint
About structured data
Structured data makes the web a better place. It also helps Google better understand and present your page in search results.
For example, we can recognize the following kinds of information on pages containing reviews, and may make them available in search results:
The writer of the review
The date the review was written
The rating (for example, 4/5).
For items with multiple user reviews, the number of reviews and average rating.
Google's first use of this data will be in search results snippets for two kinds of objects: Reviews and People. Providing more detail in search results helps users to understand the value of your pages. When users get more information showing how your page is relevant to their search, they're more likely to click through to see the full page. (Including this information will not necessarily affect your search results. As always, Google will use its own algorithms and policies to determine what information to show and when to show information based on user needs.) This structured data can also be used by Custom Search engines on your site, and gives you much more control over the behavior of your Custom Search engine. (Note: We currently support this structured content in English only.)
At Google, we believe in openness, so we are using two open standards to allow you to annotate structured data on your site: microformats and RDFa. Both standards allow markup of information on your pages. To ensure that Google understands your markup, we encourage you to follow the format of our examples. You don't need any prior knowledge of microformats or RDFa to use these standards, just a basic knowledge of XHTML.
How microformats and RDFa work
Imagine that you have a review of a restaurant on your page. In your HTML, you show the name of the restaurant, the address and phone number, the number of users who have provided reviews, and the average rating. People can read and understand this information, but to a computer it is nothing but strings of unstructured text. With microformats or RDFa, you can label each piece of text to make it clear that it represents a certain type of data: for example, a restaurant name, an address, or a rating. This is done by providing additional HTML tags that computers understand. These don't affect the appearance of your pages, but Google and any other services that look at the HTML can use the tags to better understand your information, and display it in useful ways—for example, in search results. You can use either whichever standard you prefer—microformats or RDFa— and you don't need to understand one in order to use the other.
If you are marking up structured data on your web pages, you can let us know. While we won't be able to individually reply to everyone who fills out this form and we can't make guarantees about how we may use data from any particular site, we may be in touch to learn more about your data.
For more information, see the following articles:
About microformats
About RDFa
For specific vocabulary and examples, see:
Reviews
People
Products
Businesses and organizations

Marketing Advertising Directory