This omtology is only informative. The normative version is always that on the site <http://microformats.org>.
microformats are a way to encode semantic information into (x)html. they define formats that share one common namespace. this piece of work defines a mapping from microformats into RDF-land by mirroring the elements of microformats - as straight as possible - into an RDF vocabulary and then mapping this mf-specific voacbulary into established RDF-vocabularies.
Address of the object. <http://microformats.org/wiki/existing-classes>
This specification introduces the adr microformat, which is a 1:1 representation of the aforementioned adr property from the vCard standard, by simply reusing the adr property and sub-properties as-is from the hCard microformat. <http://microformats.org/wiki/adr>
hAtom is a microformat for content that can be syndicated, primarily but not exclusively weblog postings. hAtom is based on a subset of the Atom syndication format. <http://microformats.org/wiki/hAtom>
The HTML4 spec describes a bookmark as 'a link to a key entry point within an extended document'. By convention, this entry point also captures the notion of a 'permalink'. <http://microformats.org/wiki/rel-design-pattern#rel.3D.22bookmark.22>
I am aware of the existence of hcalendar-brainstorming and htask. This is intended to be more of a formal-style document, representing a draft replacement for the current hcalendar spec, mostly aimed at filling in areas where the current spec is incomplete or ambiguous, rather than adding newly requested functionality. <http://microformats.org/wiki/User:TobyInk/hcalendar-1.1>
hCalendar is a simple, open, distributed calendaring and events format, based on the iCalendar standard (RFC2445 <http://www.ietf.org/rfc/rfc2445.txt>), suitable for embedding in HTML or XHTML, Atom, RSS, and arbitrary XML. hCalendar is one of several open microformat standards. <http://microformats.org/wiki/hCalendar>
All values are defined according to the semantics defined in the hCard specification and thus in RFC 2426. <http://microformats.org/wiki/hcard-profile>
geo (pronounced 'gee-oh') is a simple format for marking up WGS84 geographic coordinates (latitude; longitude), suitable for embedding in HTML or XHTML, Atom, RSS, and arbitrary XML. geo is a 1:1 representation of the 'geo' property in the vCard standard (RFC2426) in HTML, one of several open microformat standards. <http://microformats.org/wiki/geo>
The problem: Measures (e.g. weights, sizes, temperatures) occur frequently on the Web, they are constituted of a value a unit-measure and, in scientific and technical contexts, an experimental uncertainty. These 3 elements should be marked-up consistently across websites so that they can be easily identified and acted upon (export, compute, convert) in collaborative distributed applications. Unit-measures differ from locale to locale (e.g. Fahrenheit vs. Celsius, pound versus Kilogram), making comparison and matching of offerings difficult. The Measurement microformat will enable unambiguous description of physical quantities and thus provide a solid ground for data sharing and automation in many areas. <http://microformats.org/wiki/measure>
The subclasses of AMicroformat are RDF-ifications of microformats defined on the site <http://microformats.org>. They merely reference the fields from the aMicroformat ontology (of which they are part of themselves), that are defined or referenced by the original microformat. More thorough descriptions of those elements, together with mappings to well established RDF-vocabularies and terms are contained in this aMicroformat ontology.
The hRecipe microformat is designed for the mark-up of instructions for creating meals, drinks or food-based items. <http://microformats.org/wiki/recipe#Introduction>
Rel-License is a simple, open, format for indicating content licenses which is embedable in HTML or XHTML, Atom, RSS, and arbitrary XML. [...] By adding rel='license' to a hyperlink, a page indicates that the destination of that hyperlink is a license for the current page. <http://microformats.org/wiki/rel-license>
Rel-Tag is one of several MicroFormats. By adding rel='tag' to a hyperlink, a page indicates that the destination of that hyperlink is an author-designated 'tag' (or keyword/subject) for the current page. Note that a tag may just refer to a major portion of the current page (i.e. a blog post). e.g. by placing this link on a page, tech the author indicates that the page (or some portion of the page) has the tag 'tech'. The linked page SHOULD exist, and it is the linked page, rather than the link text, that defines the tag. The last path component of the URL is the text of the tag, so fish would indicate the tag 'tech' rather than 'fish'. <http://microformats.org/wiki/rel-tag#Abstract>
hResume is a microformat for publishing resumes and CVs. <http://microformats.org/wiki/hResume>
hReview is a simple, open, distributed format, suitable for embedding reviews (of products, services, businesses, events, etc.) in HTML, XHTML, Atom, RSS, and arbitrary XML. hReview is one of several microformats open standards. <http://microformats.org/wiki/hreview>
XFN (XHTML Friends Network) is a simple way to represent human relationships using hyperlinks. <http://gmpg.org/xfn/>
some microformats implicitly define the equivalent of what's called 'blank nodes' in RDF, e.g. to express hierarchies of subproperties. the property 'hasAbstractClass' is a helper property to model those implicit constructs. the class 'AbstractClass' is a helper class to capture those constructs. individuals of type 'AbstractClass' are not explicit parts of the original microformat being re-modeled.
A container for the rest of the class names defined in this aCard. See section 1. of RFC 2426 <http://www.ietf.org/rfc/rfc2426.txt>.
Indicates that this element and all containing elements are part of the hCard microformat. <http://microformats.org/wiki/existing-classes>
A weblog/microcontent entry <http://microformats.org/wiki/existing-classes>
an Entry element represents the concept of an Atom entry <http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.1.2>
A container for hentrys <http://microformats.org/wiki/existing-classes>
a Feed element represents the concept of an Atom feed <http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.1.1>
A helper class for constructing the RDF-graph
A Recipe is used to identify and describe values und metadata typically associated with a recipe.
Some fields are marked experimental since they exceed the minimum set of elements needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these elements will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec. <http://microformats.org/wiki/hrecipe#In_General>
Someone you know how to get in touch with. Often symmetric.
See 'Additional Names' in section 3.1.2 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
See section 3.2.1 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
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'. <http://www.ietf.org/rfc/rfc2426.txt>
# an Entry Author element represents the concept of an Atom author <http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.1> # an Entry Author element MUST be encoded in an hCard # an Entry Author element SHOULD be encoded in an element
An Author is the person who authored the recipe.
Author of a weblog/microcontent entry <http://microformats.org/wiki/existing-classes>
The contents of the element MUST include a valid hCard.
See section 3.1.5 of RFC 2426. Typically used with an tag with the 'title' attribute for the date value, and a human readable date inside the element. <http://www.ietf.org/rfc/rfc2426.txt>
The birth date of the object. <http://microformats.org/wiki/existing-classes>
The HTML4 spec describes a bookmark as 'a link to a key entry point within an extended document'. By convention (citation needed), this entry point also captures the notion of a 'permalink'..
an Entry Permalink element represents the concept of an Atom link in an entry <http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.7>
A Feed Category element represents the concept of an Atom category <http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.2> inside a mf2rdf:Feed
Application category of the object. <http://microformats.org/wiki/existing-classes>
See section 3.6.1 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
A person's genetic offspring, or someone that a person has adopted and takes care of. Inverse is parent.
See section 3.7.1 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
The access classification of the object. For example, public or private. <http://microformats.org/wiki/existing-classes>
Someone you share a street address with. Symmetric and transitive.
Someone a person works with, or works at the same organization as. Symmetric. Usually transitive.
Someone in the same field of study/activity. Symmetric. Often transitive.
Current contact info of the object. The with hCard. <http://microformats.org/wiki/existing-classes>
Name of the country for this particular address. <http://microformats.org/wiki/existing-classes>
See 'country name' in section 3.2.1 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
Someone you have a crush on. No inverse.
Someone you are dating. Symmetric. Not transitive.
The time it takes to prepare the meal described by the recipe. Multiple duration fields can be used to denote e.g. time for preparing a dough, time needed for the dough to raise, time to bake the dough, time for decorating the cake etc.
The time it takes to prepare the meal described by the recipe. Multiple preparation-time fields can be used to denote e.g. time for preparing a dough, time needed for the dough to raise, time to bake the dough, time for decorating the cake etc.
See section 3.3.2 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
This object's email address. <http://microformats.org/wiki/existing-classes>
Content of a weblog/microcontent entry <http://microformats.org/wiki/existing-classes>
an Entry Content element represents the concept of an Atom content <http://www.atomenabled.org/developers/syndication/atom-format-spec.php#atomContent>
Summary of a weblog/microcontent entry <http://microformats.org/wiki/existing-classes>
an Entry Summary element represents the concept of an Atom summary <http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.13>
Title of weblog/microcontent entry <http://microformats.org/wiki/existing-classes>
an Entry Title element represents the concept of an Atom entry title <http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.14>
Extended address for this particular address. <http://microformats.org/wiki/existing-classes>
See 'extended address' in section 3.2.1 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
See 'Family Name' in section 3.1.2 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
See section 3.1.1 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
The name of the object. <http://microformats.org/wiki/existing-classes>
The title of a single recipe is a short textual description used to identify the work among interested parties. This can be the name of a meal or a short description regarding it's ingredients. <http://microformats.org/wiki/hrecipe>
Someone you are a friend to. A compatriot, buddy, home(boy|girl) that you know. Often symmetric.
Geographical coordinates of the object. <http://microformats.org/wiki/existing-classes>
See section 3.4.2 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
See 'Given Name' in section 3.1.2 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
some microformats implicitly define the equivalent of what's called 'blank nodes' in RDF, e.g. to express hierarchies of subproperties. the property 'hasAbstractClass' is a helper property to model those implicit constructs.
See 'Honorific Prefixes' in section 3.1.2 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
See 'Honorific Suffixes' in section 3.1.2 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
Describes one or more ingredients used in the recipe.
The element MAY include the fields num, unit and item following the conventions outlined in measure. In this case each ingredient should be marked up with it's own ingredient element. The element MAY include a note which MUST follow the conventions outlined in hCard.
The field MAY include valid HTML markup e.g. paragraphs or a list of steps.
Public key of the object <http://microformats.org/wiki/existing-classes>
See section 3.7.2 of RFC 2426. Typically used with an tag with the 'title' attribute for the key value, and a human readable key equivalent inside the element. <http://www.ietf.org/rfc/rfc2426.txt>
A relative, someone you consider part of your extended family. Symmetric and typically transitive.
Formatting to be used by a delivery address label. <http://microformats.org/wiki/existing-classes>
See section 3.2.2 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
See 'latitude' in section 3.4.2 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
The latitude coordinates of the object. <http://microformats.org/wiki/existing-classes>
Indicates that the referred resource is a license for the referring page..
Locality for this particular address. <http://microformats.org/wiki/existing-classes>
See 'locality' in section 3.2.1 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
Object's logo. <http://microformats.org/wiki/existing-classes>
See section 3.5.3 of RFC 2426. Typically used with an tag. Use the 'src' attribute for URI values. Use the 'data:' URI scheme for binary values. <http://www.ietf.org/rfc/rfc2426.txt>
See 'longitude' in section 3.4.2 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
The longitude coordinates of the object. <http://microformats.org/wiki/existing-classes>
Email software used by the object. <http://microformats.org/wiki/existing-classes>
See section 3.3.3 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
A link to yourself at a different URL. Exclusive of all other XFN values. Required symmetric. There is an implicit 'me' relation from the contents of a directory to the directory itself.
Someone who you have actually met in person. Symmetric.
Someone who brings you inspiration. No inverse.
See section 3.1.2 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
The name of the unit (additional-name, family-name, given-name, honorific-prefix, honorific-suffix, nickname) <http://microformats.org/wiki/existing-classes>
Someone who lives nearby, perhaps only at an adjacent street address or doorway. Symmetric. Often transitive.
See section 3.1.3 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
See section 3.6.2 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
Supplemental information about the object <http://microformats.org/wiki/existing-classes>
Nutritional information like calories, fat, dietary fiber etc.
The element MAY include the fields num, unit and item following measure.
See section 3.5.5 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
The organization or company of the object. <http://microformats.org/wiki/existing-classes>
See 'Organization Name' in section 3.5.5 of RFC 2426. May be inferred per Implied 'organization-name' Optimization. <http://www.ietf.org/rfc/rfc2426.txt>
The name of the organization or company of the object. <http://microformats.org/wiki/existing-classes>
See 'Organization Unit' in section 3.5.5 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
The unit or department of the object. <http://microformats.org/wiki/existing-classes>
A photo of the object. Used in <http://microformats.org/wiki/existing-classes>
See section 3.1.4 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
The element SHOULD use an element. The element MAY use any other element that contains a URL, such as or , but it is not recommended. The contents of the element MUST follow the conventions outlined in hCard.
Typically used with an tag. Use the 'src' attribute for URI values. Use the 'data:' URI scheme for binary values. <http://www.ietf.org/rfc/rfc2426.txt>
Post office box number of this particular address. <http://microformats.org/wiki/existing-classes>
See 'post office box' in section 3.2.1 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
Postal code for this particular address. <http://microformats.org/wiki/existing-classes>
See 'postal code' in section 3.2.1 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
* an Entry Published element is identified by the class name published * an Entry Published element represents the concept of Atom published <http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.9> * use the datetime-design-pattern to encode the published datetime
Publish date of a weblog/microcontent entry <http://microformats.org/wiki/existing-classes>
The datetime-design-pattern SHOULD be used to encode the published datetime.
this microformat re-uses that element from another microformat, but with different constraints on value properties
this microformat re-uses that element from another microformat
Region of this particular address. <http://microformats.org/wiki/existing-classes>
See 'region' in section 3.2.1 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
See section 3.6.4 of RFC 2426. Typically used with an tag with the 'title' attribute for the date value, and a human readable date inside the element. <http://www.ietf.org/rfc/rfc2426.txt>
Specifies revision of the hCard. <http://microformats.org/wiki/existing-classes>
Information regarding the role of the object. <http://microformats.org/wiki/existing-classes>
See section 3.5.2 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
Someone a person shares a parent with. Symmetric. Usually transitive.
See section 3.6.5 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
String used to sort this object in an alphabetical list. <http://microformats.org/wiki/existing-classes>
Audio reading back another element's content. By default, the 'fn'. <http://microformats.org/wiki/existing-classes>
See section 3.6.6 of RFC 2426. Typically used with either an or tag. Use the 'data:' URI scheme for binary values. <http://www.ietf.org/rfc/rfc2426.txt>
Someone you are married to. Symmetric. Not transitive.
See 'street address' in section 3.2.1 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
Street address of this particular address. <http://microformats.org/wiki/existing-classes>
The summary provides a short introduction or an accompanying statement about the recipe.
Someone with whom you are intimate and at least somewhat committed, typically exclusively. Symmetric. Not transitive.
Indicates that the referred resource serves as a 'tag', or keyword/subject, for the referring page.
See section 3.3.1 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
Telephone number of the object <http://microformats.org/wiki/existing-classes>
Job title or functional position of the object. <http://microformats.org/wiki/existing-classes>
See section 3.5.1 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
Defines a type of the parent element. For instance a type of telephone number such as home or work.. Used in conjunction with 'value'. <http://microformats.org/wiki/existing-classes>
See 'type' in the various sections of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
See section 3.4.1 of RFC 2426. Typically used with an tag with the 'title' attribute for the tz value, and a human readable time zone inside the element. <http://www.ietf.org/rfc/rfc2426.txt>
The timezone the object is in. <http://microformats.org/wiki/existing-classes>
Globally unique identifier associated with the object, or one of the object's properties. <http://microformats.org/wiki/existing-classes>
See section 3.6.7 of RFC 2426. <http://www.ietf.org/rfc/rfc2426.txt>
# an Entry Updated element is identified by class name updated # an Entry Updated element represents the concept of Atom updated <http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.15> # an Entry SHOULD have an Entry Updated element # use the datetime-design-pattern to encode the updated datetime
Last updated date of a weblog/microcontent entry <http://microformats.org/wiki/existing-classes>
A link to the this object's home page or extended profile. Used in <http://microformats.org/wiki/existing-classes>
See section 3.6.8 of RFC 2426. Typically used with an tag. <http://www.ietf.org/rfc/rfc2426.txt>
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. <http://www.ietf.org/rfc/rfc2426.txt>
Used in conjunction with 'type'. The actual value of a particular type. For instance a telephone number of type work such as +1.415.555.1212. <http://microformats.org/wiki/existing-classes>
Specifies the quantity produced by the recipe, like how many persons it satisfyies or how many pieces can be made of it.