This document defines formatting and style rules for HTML and CSS. It aims at improving collaboration, code quality, and enabling supporting infrastructure. It applies to raw, working files that use HTML and CSS, including GSS files. Tools are free to obfuscate, minify, and compile as long as the general code quality is maintained.

All about Googlebot

hDOAP is a microformat-like convention (i.e. a dialect of XHTML containing embedded data) used to express Description of a Project (DOAP) data in XHTML. This document describes and defines the hDOAP profile. GRDDL may be used to extract machine-readable data from the document.
Status

* 2008-08-09 - unchanged apart from rewording intro to make clear this is not an official microformat (because it wasn't produced by the microformats.org process. For some reason the XSLT is no longer working with W3C service, though is ok with xsltproc - @@TODO fix.
* 2005-05-29 - almost finished, some less common elements need adding to the stylesheets, minor bug (empty release is added)

@@TODO add references to relevant docs
Creating hDOAP Documents

There are (at least) two ways of creating a hDOAP document. The first is to use an HTML editor and include the attributes for CSS as structured in this sample : redland-doap.html (describes the Redland RDF Toolkit).

The second is to create a standard DOAP file and run it through the XSLT transformation described below. The DOAP-a-matic provides a very easy way of creating the DOAP.

Those that use Firefox with the Tails extension, read no further. This is not for you. You have it given to you on a plate, you don’t know how lucky you are. This is for those of us using Camino, Safari or Omniweb.

After I mocked up an image of how Microformats detection might work in Safari, I started looking at the tools there were available. While there wasn’t anything that handled detection, Tantek did release his bookmarklets to allow hCard and hCalendar information to be exported from a page. Nothing in the region of Tails where you could view a list and choose which contacts/events you wanted, but it worked. This just left some way of handling detection, until I came across Chris Casciano’s script for NetNewsWire to Extract Microformats. It was a simple solution too – use css to style .vcard and .vevent classes differently.

So I’ve knocked up one of my own as a starting point. Here it is in action on Adactio, a rich harvest of microformats to be highlighted:

Example of the highlight microformats css in action

Here’s the file to download: expose-mf.css

It may work better with some designs than others. So far, I’ve not come

Microformats Wiki

* Blog
* Wiki
* Discuss

Search
cheat-sheet

(Redirected from cheatsheets)
Jump to: navigation, search

Brian Suda has made a PDF microformats "cheat-sheet" which you can download, free. An alternative cheat sheet is also available.

These cover:

* Address
o see adr-cheatsheet
* Geolocation
o see geo-cheatsheet
* hAtom
o see hatom-cheatsheet
* hCalendar
o see hcalendar-cheatsheet
* hCard
o see hcard-cheatsheet
* hResume
* hReview
* rel-directory
* rel-license
* rel-nofollow
* rel-tag
* VoteLinks
* XFN
* xFolk

and the datetime and include patterns.
Folding cheatsheet

Erin Caton has designed a pocket cheat sheet. Download the PDF, print double-sided and borderless, then fold it up.

Erin's cheatsheet covers hCard, hCalendar, hResume, hReview, hAtom, rel-license, rel-tag and XFN.

Here are some pictures of the folded cheatsheet.

Note issues, feedback, and suggestions on the pocket cheat sheet feedback page.

microformats resources

* buttons
* cheatsheets are handy if you need a quick reminder about a particular microformat.
* css - some handy CSS code for improving your published microformats.
* demo - a page with links for quickly demonstrating microformats working in practice.
* events
* existing-classes
* existing-rel-values
* icons
* jobs
* RFCs used by microformats
* 2D Barcodes
* shortcuts to wiki pages with long names
* spell-check dictionary
* spread-microformats
* and finally, humor!

Retrieved from "http://microformats.org/wiki/resources"

Xhtml Friends Network

XFN™ (XHTML Friends Network) is a simple way to represent human relationships using hyperlinks. In recent years, blogs and blogrolls have become the fastest growing area of the Web. XFN enables web authors to indicate their relationship(s) to the people in their blogrolls simply by adding a 'rel' attribute to their <a href> tags, e.g.:

<a href="http://jeff.example.org" rel="friend met">...

To find out how to write and use XFN, or to write a program to generate or spider it, read the following sections:

Introduction and Examples
Introduction to XFN, examples, styling suggestions, and future potential.
Getting Started
Join the XHTML Friends Network in just four easy steps!
Profile
Version 1.1 of the XFN meta data profile: the list of the values used in XFN with their significance. See the XMDP home page for more information on XHTML Meta Data Profiles.
Background
The thinking that went into the design of XFN, why particular values were chosen, and why other values were left out.
FAQ
Frequently asked questions about XFN.
XFN Tools
A collection of tools, templates, editors, communities, and other resources that let you edit XFN information. Includes the XFN Creator, among many others.
XFN and ...
How to use XFN with numerous social network services and other technologies.
What's out there?
Pointers to pages and sites which use XFN, tools, ...
How can I help?
If you would like to support XFN...
Press
Articles about or that reference XFN...
Thanks
Thanks to all those who have helped XFN with their feedback, constructive criticisms, suggestions, and inspirational uses.
Feedback
Let us know what you think about XFN.

Microformats Wiki

* Blog
* Wiki
* Discuss

Search
existing-classes

Jump to: navigation, search
Class Names Across All Microformats

Microsummaries are regularly-updated short summaries of web pages. They are compact enough to fit in the space available to a bookmark label, they provide more useful information about pages than static page titles, and they get regularly updated as new information becomes available.

Here are examples of possible microsummaries for some common types of pages:
Type of Page Possible Microsummary
auction item Honda Accord - $5000 - 1 minute left
(item name, current highest bid, and time remaining)
product for sale Linksys WRT54G - $60 - in stock
(product name, current price, and availability)
news site BBC: Chirac to sign France's job law
(latest headline)
word of the day flat-hat
(today's word)
stock quote TWX: 16.94 + 0.30
(stock price and movement)
weather report SF: showers likely
(current forecast)
tinderbox 3 burning
(status of the tree)
forum thread my first thread - 37 comments - last by Aaron
(thread name, number of comments, and last commenter)
support ticket tn79217 - in progress - J.Doe - eta: 3hrs
(ticket number, status, owner, and ETA)

Microformats Wiki

* Blog
* Wiki
* Discuss

Search
existing rel values

Jump to: navigation, search


This page contains tables of known HTML rel values from specifications, formats, proposals, brainstorms, and non-trivial POSH usage in the wild. In addition, dropped and rejected values are listed at the end for comprehensiveness.

usage: see how is 'rel' used. Regarding rev, see: should 'rev' even be used.
Contents
[hide]

* 1 formats
o 1.1 notes
* 2 proposals
* 3 brainstorming
o 3.1 more brainstorming
* 4 POSH usage
o 4.1 WCLR
* 5 non HTML rel values
* 6 dropped
* 7 rejected
* 8 unspecified
* 9 tools
* 10 related

formats

These rel values are defined formats from specifications (HTML 4, microformats) are thus are recommended for general use. Alphabetically ordered by value.

Note:

rel and rev attribute values, with counts of number of pages on which they occur, out of 127249 random text/html pages from dmoz.org downloaded on 2008-02-26: (UPDATE: Actually it looks like it's not just text/html pages, it includes others too. Oh well.)

alternate, appendix, bookmark, chapter, contents, copyright, current, describedby, edit, edit-media, enclosure, first, glossary, help, hub, index, last, latest-version, license, monitor, monitor-group, next, next-archive, payment, predecessor-version, prev, previous, prev-archive, related, replies, section, self, service, start, stylesheet, subsection, successor-version, up, version-history, via, working-copy, working-copy-of

The Resource Description Framework RDF allows users to describe both Web documents and concepts from the real world—people, organisations, topics, things—in a computer-processable way. Publishing such descriptions on the Web creates the Semantic Web. URIs (Uniform Resource Identifiers) are very important, providing both the core of the framework itself and the link between RDF and the Web. This document presents guidelines for their effective use. It discusses two strategies, called 303 URIs and hash URIs. It gives pointers to several Web sites that use these solutions, and briefly discusses why several other proposals have problems.

Rich snippets testing tool
Share

* Twitter
* Gmail
* Blogger
* Buzz
* Orkut
* Google Reader
* Bookmarks
* » More

Comment Print

The rich snippets testing tool lets you check your markup and make sure that Google can extract the structured data from your page. This tool will display the markup found on a specific web page, as well as a preview of how that page might appear in Google search results.

This tool is still a work in progress, so there are a few points to note:

* The tool doesn't currently display a preview of breadcrumbs content. We're working on it!
* The tool interface is currently available in English only. The tool will correctly test markup in other languages; however, the results will not look like they will look in an actual non-English search results page.
* The tool will only display extracted information that is officially supported for rich snippets. Supported RDFa attributes are xmlns, typeof, property, rel, and content.

"Insufficient data to generate preview"

In general, the goal of rich snippets is to display the most relevant content on the page to users. If you see an "insufficient data to generate preview" message, it is generally for one of two reasons:

* The marked-up content doesn't appear to be the main subject of the page. This can happen if the marked-up content is very low down on the page, is found in boilerplate elements such as headers, footers, and navigation, or is included in a hidden HTML element.
* The marked-up content is missing important tags. For example, a Person item must include organization, location, or role, as well as name.

This is an early release of the testing tool, and feedback is welcome. Please submit feedback or bugs on the Webmaster Tools forum. For tips and tricks, check out the Rich snippets knol (English only).

Rich snippets (microdata, microformats, RDFa)

o Rich snippets (microdata, microformats, and RDFa)
o Breadcrumbs
o About microdata
o About microformats
o About RDFa
o Nested items
o Recipes
o Reviews
o Review ratings
o People
o Events
o Businesses and organizations
o Products
o Videos: Facebook Share and RDFa
o Rich snippets testing tool

<div itemscope itemtype="http://data-vocabulary.org/Breadcrumb"> <a href="http://www.example.com/dresses" itemprop="url"> <span itemprop="title">Dresses</span> </a> › </div> <div itemscope itemtype="http://data-vocabulary.org/Breadcrumb"> <a href="http://www.example.com/dresses/real" itemprop="url"> <span itemprop="title">Real Dresses</span> </a> › </div> <div itemscope itemtype="http://data-vocabulary.org/Breadcrumb"> <a href="http://www.example.com/clothes/dresses/real/green" itemprop="url"> <span itemprop="title">Real Green Dresses</span> </a> </div>

I don’t think it is hyperbole to say that HTML5 will change the way that you think about web development. I welcome many of the changes as they make development easier, and the user experience richer. With any change, though, there is certain to be a bit of trepidation and controversy. One addition that certainly is not without its controversy is the Microdata specification, but I believe the benefits of this very simple specification are going to change how you look at your mark-up in the very near future.

Your First WordPress Plugin: Simple Optimization
Tutorial Details
Step 0 Before we Begin
Step 1. What our Plugin Does
Remove useless meta tags:
Remove unnecessary filters:
SEO:
Step 2. Laying the Groundwork
Step 3. Adding Features
Step 4. SEO
Step 5. Optimizing the Database
Step 6. Filling out the ReadMe
By Jonathan Wolfe

The collapsible content area widget is fairly simple — a couple of HTML elements controlled with minimal CSS and JavaScript — but when we were researching our book, Designing with Progressive Enhancement, we discovered that many common approaches to creating collapsible content fail to incorporate accessibility features. Happily, there is a way to build collapsible content with progressive enhancement so it delivers an optimal accessible experience for sighted and screen reader users alike.

The code example described in this article is one of the 12 fully-accessible, project-ready, progressive enhancement-driven widgets that accompanies our new book, Designing with Progressive Enhancement.

The single best way to make Google aware of all your videos on your website is to create and maintain a Video Sitemap. Video Sitemaps provide Google with essential information about your videos, including the URLs for the pages where the videos can be found, the titles of the videos, keywords, thumbnail images, durations, and other information. The Sitemap also allows you to define the period of time for which each video will be available. This is particularly useful for content that has explicit viewing windows, so that we can remove the content from our index when it expires.

We all work hard at the SEO process - analyzing sites, gathering data, researching potential problems and identifying the solutions. Today's post is on how to work smarter and faster using bookmarklets for SEO. No matter your browser, these plug-and-play links will let you get your job done faster and easier, and look like a pro in front of bosses and clients.
The list isn't 100% compre...