Microformats

Umbrella Profile March 2008

The following is an XMDP profile which acts as a profile for all non-draft Microformats as of March 2008. It should be considered an umbrella for the individual Microformat profiles.

hCard/1.0: http://purl.org/uF/hCard/1.0/
hCalendar/1.0: http://purl.org/uF/hCalendar/1.0/
rel-tag/1.0: http://purl.org/uF/rel-tag/1.0/
rel-license/1.0: http://purl.org/uF/rel-license/1.0/
rel-nofollow/1.0: http://purl.org/uF/rel-nofollow/1.0/
VoteLinks/1.0: http://purl.org/uF/VoteLinks/1.0/
XFN/1.1: http://gmpg.org/xfn/11
XOXO/1.0: (no individual profile URI)

Authors making use of Microformats should include this profile in their document head. The permanent, canonical URI for this document is: http://purl.org/uF/2008/03/. Other URIs for this document may not be permanent so must not be used.

An example of linking to this profile in HTML 4.0:

<html>
	<head profile="http://purl.org/uF/2008/03/">
	...

This profile does not include any draft or experimental microformats. Authors wishing to combine use of this profile with other profiles may list multiple profile URIs in their document. Note that when two profiles contradict, the profile listed first is treated as the definitive definition of a term. If an author wishes to use this profile in conjunction with a newer version of one of the Microformats covered by this profile, they should list the newer version first. An example of a page using hAtom 0.1, and a newer version of hCard:

<html>
	<head profile="http://purl.org/uF/hCard/2.1/
		http://purl.org/uF/2008/03/ 
		http://purl.org/uF/hAtom/0.1/">
	...

class

HTML4 definition of the 'class' attribute. This meta data profile defines some 'class' attribute values (class names) and their meanings as suggested by a draft of "Hypertext Links in HTML".

vcard: A container for hCard class names. See RFC 2426.
fn: See section 3.1.1 of RFC 2426.
n: See section 3.1.2 of RFC 2426. May be inferred per Implied "N" Optimization.
family-name: See "Family Name" in section 3.1.2 of RFC 2426.
given-name: See "Given Name" in section 3.1.2 of RFC 2426.
additional-name: See "Additional Names" in section 3.1.2 of RFC 2426.
honorific-prefix: See "Honorific Prefixes" in section 3.1.2 of RFC 2426.
honorific-suffix: See "Honorific Suffixes" in section 3.1.2 of RFC 2426.
nickname: See section 3.1.3 of RFC 2426.
photo: See section 3.1.4 of RFC 2426. Typically used with an <img> tag. Use the 'src' attribute for URI values. Use the 'data:' URI scheme for binary values.
bday: See section 3.1.5 of RFC 2426. Typically used with an <abbr> tag with the 'title' attribute for the date value, and a human readable date inside the element.
adr: See section 3.2.1 of RFC 2426.
post-office-box: See "post office box" in section 3.2.1 of RFC 2426.
extended-address: See "extended address" in section 3.2.1 of RFC 2426.
street-address: See "street address" in section 3.2.1 of RFC 2426.
locality: See "locality" in section 3.2.1 of RFC 2426.
region: See "region" in section 3.2.1 of RFC 2426.
postal-code: See "postal code" in section 3.2.1 of RFC 2426.
country-name: See "country name" in section 3.2.1 of RFC 2426.
type: See "type" in the various sections of RFC 2426.
value: This class name is used to distinguish the actual value of a property from any other cruft that may be in the element representing the property.
label: See section 3.2.2 of RFC 2426.
tel: See section 3.3.1 of RFC 2426.
email: See section 3.3.2 of RFC 2426.
mailer: See section 3.3.3 of RFC 2426.
tz: See section 3.4.1 of RFC 2426. Typically used with an <abbr> tag with the 'title' attribute for the tz value, and a human readable time zone inside the element.
geo: See section 3.4.2 of RFC 2426.
latitude: See "latitude" in section 3.4.2 of RFC 2426.
longitude: See "longitude" in section 3.4.2 of RFC 2426.
title: See section 3.5.1 of RFC 2426.
role: See section 3.5.2 of RFC 2426.
logo: See section 3.5.3 of RFC 2426. Typically used with an <img> tag. Use the 'src' attribute for URI values. Use the 'data:' URI scheme for binary values.
agent: See section 3.5.4 of RFC 2426. If the value is a vCard, then use a nest hCard. For simplicity in that case, the same element that has the class name of "agent" should use the class name of "vcard".
org: See section 3.5.5 of RFC 2426.
organization-name: See "Organization Name" in section 3.5.5 of RFC 2426. May be inferred per Implied "organization-name" Optimization.
organization-unit: See "Organization Unit" in section 3.5.5 of RFC 2426.
category: See section 3.6.1 of RFC 2426.; Category of the event object. Note: this property may be repeated (an event may belong in several categories). Common values are: MEETING, APPOINTMENT, CONFERENCE, EXPO. See section 4.8.1.2 of RFC 2445.
note: See section 3.6.2 of RFC 2426.
rev: See section 3.6.4 of RFC 2426. Typically used with an <abbr> tag with the 'title' attribute for the date value, and a human readable date inside the element.
sort-string: See section 3.6.5 of RFC 2426.
sound: See section 3.6.6 of RFC 2426. Typically used with either an <a> or <object> tag. Use the 'data:' URI scheme for binary values.
uid: See section 3.6.7 of RFC 2426.; A globally unique identifier for the event; typically a URL is used. See section 4.8.4.7 of RFC 2445.
url: See section 3.6.8 of RFC 2426. Typically used with an <a> tag.; A URL to a page that contains the definitive/preferred information about an event; UID and URL are typically the same. See section 4.8.4.6 of RFC 2445.
class: See section 3.7.1 of RFC 2426.; Access classification of the event information; Values are: PUBLIC, PRIVATE, CONFIDENTIAL. See section 4.8.1.3 of RFC 2445.
key: See section 3.7.2 of RFC 2426. Typically used with an <abbr> tag with the 'title' attribute for the key value, and a human readable key equivalent inside the element.
vcalendar: A container for one or more events (vevent). This property is optional; if there is only one event then omit it. See section 1. of RFC 2445.
vevent: A container for one event. See section 4.6.1 of RFC 2445.
dtstart: Date/time of the start of the event. See section 4.8.2.4 of RFC 2445.
dtend: Date/time of the end of the event. See section 4.8.2.2 of RFC 2445.
duration: Length of the event. See section 4.8.2.5 of RFC 2445.
summary: Short synopsis, title, or name of the event. See section 4.8.1.12 of RFC 2445.
dtstamp: Date/time of when the document containing information about the event was created. See section 4.8.7.2 of RFC 2445.
method: Function of the event object. Values for this property are: PUBLISH, REQUEST, REPLY, ADD, CANCEL, REFRESH, COUNTER, or DECLINECOUNTER. For example, a value of REQUEST indicates that a request is being made for the event to occur. See section 4.7.2 of RFC 2445.
location: Tells where the event is to be held. May be represented by nested hCard record, adr record, geo record, or combination thereof. See sections 4.8.1.7 and 4.8.1.6 of RFC 2445.
description: A more detailed synopsis of the event than that provided by summary. See section 4.8.1.5 of RFC 2445.
last-modified: Date/time the information about the event was updated. See section 4.8.7.3 of RFC 2445.
status: Status of the calendar event. Values are: TENTATIVE, CONFIRMED, CANCELLED. See section 4.8.1.11 of RFC 2445.
attendee: An individual invited to attend the event; An event container may contain more than one attendee record; May be represented by nested hCard record. See section 4.8.4.1 of RFC 2445.
contact: Contact information associated with the event; May be represented by nested hCard record. See section 4.8.4.2 of RFC 2445.
organizer: The organizer associated with the event; May be represented by nested hCard record. See section 4.8.4.3 of RFC 2445.
xoxo: A XOXO outline as defined by the XOXO specification. Typically an ordered list <ol> or unordered list <ul> element.
blogroll: When used with the aforementioned 'xoxo' value, this value means a particular instance of a XOXO outline which has the additional semantic of being a blogroll.

rel

HTML4 definition of the 'rel' attribute. Here are some additional values.

tag: Indicates that the referred resource serves as a "tag", or keyword/subject, for the referring page.
license: Indicates that the referred resource is a license for the referring page.
nofollow: Indicates that the referred resource was not necessarily linked to by the author of the page, and thus said reference should not afford the referred resource any additional weight or ranking by user agents.
contact: Someone you know how to get in touch with. Often symmetric.
acquaintance: Someone who you have exchanged greetings and not much (if any) more — maybe a short conversation or two. Often symmetric.
friend: Someone you are a friend to. A compatriot, buddy, home(boy|girl) that you know. Often symmetric.
met: Someone who you have actually met in person. Symmetric.
co-worker: Someone a person works with, or works at the same organization as. Symmetric. Usually transitive.
colleague: Someone in the same field of study/activity. Symmetric. Often transitive.
co-resident: Someone you share a street address with. Symmetric and transitive.
neighbor: Someone who lives nearby, perhaps only at an adjacent street address or doorway. Symmetric. Often transitive.
child: A person's genetic offspring, or someone that a person has adopted and takes care of. Inverse is parent.
parent: Inverse of child.
sibling: Someone a person shares a parent with. Symmetric. Usually transitive.
spouse: Someone you are married to. Symmetric. Not transitive.
kin: A relative, someone you consider part of your extended family. Symmetric and typically transitive.
muse: Someone who brings you inspiration. No inverse.
crush: Someone you have a crush on. No inverse.
date: Someone you are dating. Symmetric. Not transitive.
sweetheart: Someone with whom you are intimate and at least somewhat committed, typically exclusively. Symmetric. Not transitive.
me: A link to yourself at a different URL. Exclusive of all other XFN values. Required symmetric. There is an implicit "me" relation from a subdirectory to all of its contents.

rev

HTML4 definition of the 'rev' attribute. Here are some additional values.

vote-for: Indicates agreement with or recommendation for the referred resource.
vote-abstain: Indicates abstention or indifference for the referred resource.
vote-against: Indicates disagreement with or recommendation against the referred resource.

Changes

Although this document is intended to represent microformats as of March 2008, changes have been and will be made to it afterwards. The intention is that changes will only be made which are consistent with the usage of microformats as of March 2008. Although new terms may be added, existing terms will not be removed or significantly changed in meaning. For major changes that involve removing terms or changing their meanings, a new URI will be used.

2008-03-20: Initial version of this page.
2008-05-13: Included XOXO in the profile; corrected VoteLinks information.