Microformats Wiki - User contributions [en]

hcard-cheatsheet

2009-12-19T04:46:02Z

AngeloGladding: corrected previous alphabetization's mixup

<h1>hCard cheatsheet</h1>

[[hcard|hCard]] properties and how to use them.

==Profile==
<nowiki><head profile="http://www.w3.org/2006/03/hcard"></nowiki>

==Properties (Class Names)==

*'''vcard''' {1}
**''[[adr]]''*
***type [work|home|pref|postal|dom|intl]?
***post-office-box?
***''street-address''*
***extended-address?
***region?
***locality?
***postal-code?
***country-name?
**''agent''*
**[[hcard-singular-properties#bday|bday]]? ''([[datetime-design-pattern |ISO date]])''
**[[hcard-singular-properties#class|class]]? ''confidentiality/access classification of the ''entire'' hCard''
**''category''*
**''email''*
***type?
***value?
**'''[[hcard-singular-properties#fn|fn]]''' {1}
**[[geo]]?
***latitude?
***longitude?
**''key''*
**''label''*
**''logo''*
**''mailer''*
**[[hcard-singular-properties#n|n]]?
***''honorific-prefix''*
***''given-name''*
***''additional-name''*
***''family-name''*
***''honorific-suffix''*
**''nickname''*
**''note''*
**''org''*
***organization-name?
***''organization-unit''*
**''photo''*
**[[hcard-singular-properties#rev|rev]]? ''datetime of the revision of the ''entire'' hCard''
**''role''*
**[[hcard-singular-properties#sort-string|sort-string]]?
**''sound''*
**''tel''* ''(Note [http://en.wikipedia.org/wiki/E.123 E.123] for formatting info.)''
***type [home|work|pref|fax|cell|pager]?
***value?
**''title''*
**[[hcard-singular-properties#tz|tz]]? ''timezone of the person''
**[[hcard-singular-properties#uid|uid]]? ''applies to the ''entire'' hCard''
**''url''*

{{cheatsheet-key}}
{| border="1" cellpadding="2"
| pref || preferred
|-
| dom || domestic
|-
| intl || international
|-
| cell || mobile
|}

===Notes===
*{{rfc-2119-intro}}
* <code>URL</code> in vCard becomes <code><a class="url" href=...>...</a></code> inside the element with class <code>vcard</code> in hCard.
* Similarly, <code>EMAIL</code> in vCard becomes <code><nowiki><a class="email" href="mailto:...">...</a></nowiki></code>
* <code>FN</code> is an abbreviation of "'''formatted name'''".
* <code>PHOTO</code> in vCard becomes <code><img class="photo" src=... alt="Photo of ..." /></code> or <code><object class="photo" data=... type=...>Photo of ...</object></code>
* <code>UID</code> in vCard simply becomes another semantic applied to a specific URL (or EMAIL) for an hCard.
* Compare <code>TITLE</code> of "Wing Commander" with <code>ROLE</code> of "pilot".

====Adr====
{{adr-note}}

====Geo====
{{geo-note}}

==Related pages==
{{hcard-related-pages}}
*{{cheatsheets}}

hcard-cheatsheet

2009-12-09T03:49:29Z

AngeloGladding: obsessive-collation disorder

<h1>hCard cheatsheet</h1>

[[hcard|hCard]] properties and how to use them.

==Profile==
<nowiki><head profile="http://www.w3.org/2006/03/hcard"></nowiki>

==Properties (Class Names)==

*'''vcard''' {1}
**''[[adr]]''*
***type [work|home|pref|postal|dom|intl]?
***post-office-box?
***''street-address''*
***extended-address?
***region?
***locality?
***postal-code?
***country-name?
**''agent''*
**[[hcard-singular-properties#bday|bday]]? ''([[datetime-design-pattern |ISO date]])''
**[[hcard-singular-properties#class|class]]? ''confidentiality/access classification of the ''entire'' hCard''
**''category''*
**''email''*
***type?
***value?
**'''[[hcard-singular-properties#fn|fn]]''' {1}
**[[geo]]?
***latitude?
***longitude?
**''key''*
**''label''*
**''logo''*
**''mailer''*
**[[hcard-singular-properties#n|n]]?
***''honorific-prefix''*
***''given-name''*
***''additional-name''*
***''family-name''*
***''honorific-suffix''*
**''nickname''*
**''note''*
**''org''*
***organization-name?
***''organization-unit''*
**''photo''*
**[[hcard-singular-properties#rev|rev]]? ''datetime of the revision of the ''entire'' hCard''
**''role''*
**[[hcard-singular-properties#sort-string|sort-string]]?
**''sound''*
**''tel''* ''(Note [http://en.wikipedia.org/wiki/E.123 E.123] for formatting info.)''
**''title''*
***type [home|work|pref|fax|cell|pager]?
***value?
**[[hcard-singular-properties#tz|tz]]? ''timezone of the person''
**[[hcard-singular-properties#uid|uid]]? ''applies to the ''entire'' hCard''
**''url''*

{{cheatsheet-key}}
{| border="1" cellpadding="2"
| pref || preferred
|-
| dom || domestic
|-
| intl || international
|-
| cell || mobile
|}

===Notes===
*{{rfc-2119-intro}}
* <code>URL</code> in vCard becomes <code><a class="url" href=...>...</a></code> inside the element with class <code>vcard</code> in hCard.
* Similarly, <code>EMAIL</code> in vCard becomes <code><nowiki><a class="email" href="mailto:...">...</a></nowiki></code>
* <code>FN</code> is an abbreviation of "'''formatted name'''".
* <code>PHOTO</code> in vCard becomes <code><img class="photo" src=... alt="Photo of ..." /></code> or <code><object class="photo" data=... type=...>Photo of ...</object></code>
* <code>UID</code> in vCard simply becomes another semantic applied to a specific URL (or EMAIL) for an hCard.
* Compare <code>TITLE</code> of "Wing Commander" with <code>ROLE</code> of "pilot".

====Adr====
{{adr-note}}

====Geo====
{{geo-note}}

==Related pages==
{{hcard-related-pages}}
*{{cheatsheets}}

parsing-brainstorming

2009-12-08T22:44:10Z

AngeloGladding: cognition name change

<entry-title>Parsing Algorithm (Brainstorming)</entry-title>

= Introduction =

This document is intended to replace [[parsing]] once it reaches consensus, as it is somewhat more detailed.

This page explains how to parse the properties of a compound microformat once we have located the root element, which we shall call <code>root</code>. It deals with simple properties which have no sub-properties (such as <code>fn</code> in hCard), and with properties which may include an embedded microformat (such as <code>agent</code> in hCard) — 95% of properties do fall into these categories. Most other properties can be parsed by performing a "pivot": treating the property element as a microformat in its own right and finding sub-properties using the techniques on this page.

{{TOC-right}}

= Contributors =

'''Primary Author:''' Toby Inkster ([[User:TobyInk|TobyInk]])

= Licence =

The author of this page releases the algorithms described into the public domain.

Additionally, a working ''implementation'' of these algorithms (in Perl) is available as part of [http://buzzword.org.uk/swignition/ Swignition]. The implementation is ''not'' released into the public domain, but is licensed under the [http://www.gnu.org/licenses/gpl.html GNU General Public License (version 3)].

= General Algorithm =

This algorithm is described in procedural terms, but the same ideas could be used in a functional or declarative programming language. A DOM-like tree of the HTML is preferable, for quick, easy access to parent/child nodes. A [http://developer.mozilla.org/en/docs/DOM:document.getElementsByClassName getElementsByClassName]-like function is needed — if your programming environment does not provide one, then you will need to write one yourself. (Bear in mind that the class attribute is a whitespace delimited list, and classes are case sensitive.)

# Make a ''copy'' of the DOM tree to operate on. All future references to DOM traversal and manipulation refer to this clone.
# Implement [[include-pattern|the include pattern]] by removing any nodes with <code>class="include"</code> and replacing them with the node which they point to. (Unless the node pointed to is an ancestor node of the node with <code>class="include"</code>!!)
# Parse all properties that may contain nested microformats. For example within hCard, the agent property may contain a nested hCard. For each property <code>prop</code> which may contain a nested microformat:
## Create an empty array to store the value(s) of <code>prop</code> in. Call this <code>A</code>.
## Find all elements with <code>class="prop"</code> that are descended from <code>root</code>. Call this list <code>P</code>.
## Create an empty list <code>E</code>.
## For each element <code>p</code> in <code>P</code>:
### Let <code>ok</code> be true.
### Let <code>a</code> by the parent node of <code>p</code>.
### While <code>a</code> is not the root element of this microformat:
#### If <code>a</code> has a class attribute which indicates that it is a nested microformat (e.g. <code>class="vevent"</code>) then set <code>ok</code> to false
#### Set <code>a</code> to the parent of <code>a</code>.
### If <code>ok</code> is true, then push <code>p</code> onto <code>E</code>.
## OUTER: For each element <code>e</code> in <code>E</code>:
### INNER: For each microformat root class name that might be present (e.g. within an hCalendar event's <code>location</code> property you might reasonably expect to find an hCard, and adr or a geo!):
#### Create an empty list <code>F</code>.
#### Search for any elements within <code>e</code> which have the microformat root class name. Bear in mind that perhaps this element might ''be'' <code>e</code> — this is allowed. For each such element, <code>e2</code>:
##### Parse <code>e2</code> as an embedded microformat and place the result in <code>F</code> if it is valid.
##### Run the DESTROY_ELEMENT function on <code>e2</code>
#### If <code>F</code> is not empty:
##### Move the first item in <code>F</code> to <code>A</code>
##### Jump out of the INNER loop.
### If <code>A</code> is not empty:
#### Change the <code>class</code> attribute on <code>e</code>, removing <code>prop</code> from the class list.
#### If property <code>prop</code> is singular, jump out of the OUTER loop.
## If <code>prop</code> is a singular property, let <code>A[0]</code> be its value. If plural, let <code>A</code> be the list of its values.
# Run the DESTROYER function on <code>root</code>.
#* Depending on what microformat you're parsing, you will want to pass a further parameter to DESTROYER indicating a list of microformats to "save" from destruction. This allows for the simple string/url/datetime/etc properties to be included within nested microformats. So far, the only case I've found where this is beneficial is when parsing hCard, it is useful to save adr and geo from destruction. This enables the <code>fn</code> property to be set on address components. [[parsing-brainstorming#hCardFNinADRexample|example]]
# Parse all properties. There are three different categories of property — singular, plural and concatenated. Most properties are either singular or plural, but a handful are concatenated, such as <code>entry-summary</code> in [[hAtom]]. For each property <code>prop</code> within <code>root</code>:
## Create an empty array to store the value(s) of <code>prop</code> in. Call this <code>A</code>.
## Find all elements with <code>class="prop"</code> that are descended from <code>root</code>.
## For each element <code>e</code>, run this:
### [[#Finding_Values|Find the value of <code>e</code>]], using the techniques in the section below.
### If the value of <code>e</code> is not NULL, add it to <code>A</code>
### If the <code>prop</code> is a singular property and <code>A</code> is not empty, jump out of this foreach loop.
## If <code>prop</code> is a singular property, then its value is <code>A[0]</code>.
## If <code>prop</code> is a plural property, then its values are <code>A</code>.
## If <code>prop</code> is a concatenated property, then its values are formed by concatenating the values of <code>A</code> together.

== Finding Values ==

There are at least five different types of property that can be parsed, each of which requires different techniques:

* HTML properties, such as <code>entry-content</code> in hAtom
* URI properties, such as <code>url</code> in [[hCard]]
* ID properties, such as <code>uid</code> in hCard
* Datetime properties, such as <code>dtstart</code> in [[hCalendar]]
* Plain text properties, such as <code>title</code> in hCard

Arguments can be made for duration properties and numeric properties to also have variations in the algorithm, but for now, we'll just treat them as plain text properties.

Generally speaking, the mechanism for going from an element <code>e</code> to a value is to use the first "hit" from the following:

# Look at relevant attributes (e.g. <code>datetime</code> if we're looking for a date, or <code>href</code> if we're looking for a URI).
# Look for any descendants with <code>class="value"</code>.
# Look at the node contents.

This is described in more detail below, for each type of property.

=== HTML Properties ===

These are the easiest to parse. Given an element <code>e</code>, just use the HTML representation of its DOM node. Some DOM implementations make this available as <code>.outerHTML</code>.

=== URI Properties ===

Certain HTML elements are capable of linking to other resources. The most obvious is <code><a></code> though there are many others. The following list of linking elements is derived from Perl's ''HTML::Tagset'' module:

<pre><nowiki>{
'a' => ['href'],
'applet' => ['codebase', 'archive', 'code'],
'area' => ['href'],
# 'base' => ['href'],
'bgsound' => ['src'],
'blockquote' => ['cite'],
# 'body' => ['background'],
'del' => ['cite'],
'embed' => ['src', 'pluginspage'],
'form' => ['action'],
'frame' => ['src', 'longdesc'],
'iframe' => ['src', 'longdesc'],
# 'ilayer' => ['background'],
'img' => ['src', 'lowsrc', 'longdesc', 'usemap'],
'input' => ['src', 'usemap'],
'ins' => ['cite'],
'isindex' => ['action'],
# 'head' => ['profile'],
'layer' => ['src'], # 'background'
'link' => ['href'],
'object' => ['data', 'classid', 'codebase', 'archive', 'usemap'],
'q' => ['cite'],
'script' => ['src', 'for'],
# 'table' => ['background'],
# 'td' => ['background'],
# 'th' => ['background'],
# 'tr' => ['background'],
'xmp' => ['href'],
}</nowiki></pre>

Note that some are commented out as they might be too counter-intuitive to implement!

If we're parsing an element <code>e</code> and looking for a URI, here is the algorithm we use:

# Set variable <code>u</code> to NULL.
# Search <code>e</code> for any descendent elements with <code>class="value"</code>. Call this list <code>V</code>.
# Add the element <code>e</code> itself to the list <code>V</code>, at the ''front'' of the list.
# OUTER: for each element <code>v</code> from list <code>V</code>:
## If <code>v</code> is a linking element from the above list
### INNER: for each attribute <code>a</code> associated that the tag name of <code>v</code> in the above list
#### If <code>a</code> is set
##### Set <code>u</code> to the contents of <code>a</code>
##### Jump out of the OUTER loop.
# If <code>u</code> is not null, and is a relative URI, convert it to an absolute URI.

The URI has hopefully been found in <code>u</code>. If no URI has been found, then fall back to plain text parsing.

=== UID Properties ===

UID properties are parsed similarly to URL properties, but with a slightly modified algorithm, allowing for UIDs to be specified in the <code>id</code> attribute. The following example has a UID of "http://example.com/page#foo".

<pre><nowiki>
<base href="http://example.com/page" />
<div class="uid" id="foo">...</div>
</nowiki></pre>

The modified algorithm used is:

# Set variable <code>u</code> to NULL.
# Search <code>e</code> for any descendent elements with <code>class="value"</code>. Call this list <code>V</code>.
# Add the element <code>e</code> itself to the list <code>V</code>, at the ''front'' of the list.
# OUTER: for each element <code>v</code> from list <code>V</code>:
## If <code>v</code> is a linking element from the above list
### INNER: for each attribute <code>a</code> associated that the tag name of <code>v</code> in the above list
#### If <code>a</code> is set
##### Set <code>u</code> to the contents of <code>a</code>
##### Jump out of the OUTER loop.
## If <code>v</code> has an <code>id</code> attribute set
### Set <code>u</code> to the contents of <code>id</code>, with the character "#" prepended
### Jump out of the OUTER loop.
# If <code>u</code> is not null, and is a relative URI, convert it to an absolute URI.

Again, if no <code>u</code> has been found by the algorithm, then fall back to parsing it as a plain text property.

=== Datetime Properties ===

Parsing property <code>prop</code>, if <code>class="prop"</code> is found on element <code>e</code>.

# If element <code>e</code> has an attribute <code>datetime</code>, then the content of that attribute is the value and the rest of these steps should be skipped.
# Create a list <code>D</code>, which is empty.
# Create a list <code>V</code> of elements with <code>class="value"</code>.
# For each element <code>v</code> in <code>V</code>:
## If <code>v</code> has an attribute <code>datetime</code>, then add the content of that attribute to <code>D</code>
## Otherwise, run the STRINGIFY function on <code>v</code> and add the result to <code>D</code>
# If <code>D</code> is empty, then run the STRINGIFY function on <code>e</code> and let the result be the value, and skip the rest of these steps.
# If <code>D</code> contains only one item, and it looks like an ISO date or ISO datetime, then let that be the value, and skip the rest of these steps.
# If <code>D</code> contains two items, and the first looks like an ISO date, and the second like a time, concatenate them, joining with an upper case 'T', let that be the value, and skip the rest of these steps.
# If <code>D</code> contains three items, and the first looks like an ISO date, the second like a time, and the last like a timezone (may need normalisation), concatenate them, joining the first two with an upper case 'T' and the last one with no intervening character, let that be the value, and skip the rest of these steps.
# Concatenate all the items in <code>D</code> and let that be the value.

The final value should be interpreted as liberally as possible with regards to punctuation as an ISO date or ISO datetime.

==== Normalizing Timezones ====

Where ''S'' is a sign (+ or -) and the letters ''a, b, c, d'' are numerals, then:

* Sa → S0a00
* Sab → Sab00
* Sabc → S0abc
* Sa: → S0a00
* Sab: → Sab00
* Sa:b → S0ab0
* S:ab → S00ab
* Sa:bc → S0abc
* Sab:c → Sabc0
* Sab:cd → Sabcd

=== Plain text Properties ===

To obtain the value of the property, run STRINGIFY on the property node.

== Stringification ==

The STRINGIFY function performs a text serialisation of an HTML node, with a few adjustments to implement the [[abbr-design-pattern|ABBR pattern]]. It uses a helper function, _STRINGIFY.

=== STRINGIFY ===

* First parameter: element to stringify, <code>e</code>.
* Second parameter: whether to perform value excerpting - default yes.
* Third parameter: whether to perform abbr pattern - default yes.

# If <code>e</code> is an <code><abbr></code> or <code><acronym></code> element, and has a <code>title</code> attribute, then return that attribute.
# If you want to implement any proposed alternatives to the ABBR pattern, then here is the place to do so.
# If value excerpting is enabled:
## Create an empty list <code>S</code>
## Search for any descendant elements of <code>e</code> with <code>class="value"</code>. Put these into a list <code>V</code>.
## For each element <code>v</code> in <code>V</code>
### Recursion: call STRINGIFY on <code>v</code>, disabling value excerpting but enabling the ABBR pattern. Add the result to <code>S</code>.
## Concatenate the items in <code>S</code> to form a string. If this string is not empty, then return the string.
# Run _STRINGIFY on <code>e</code>, trim excess white space from the result and return it.

=== _STRINGIFY ===

This is a somewhat simplified version of the real algorithm that I use. You probably want to refine it by adding better whitespace handling rules (e.g. line breaks after block elements, asterisks for list items, etc).

_STRINGIFY is called with one parameter, the element <code>e</code> to be stringified.

# If <code>e</code> is text node (not an element), then return it.
# If <code>e</code> is an <code><img></code> tag, return the <code>alt</code> text.
# If <code>e</code> is an <code><input></code> tag, return the text of the <code>value</code> attribute.
# If <code>e</code> is an <code> </code> tag, return a linebreak character.
# If <code>e</code> is an <code><del></code> tag, return a zero-length string.
# Otherwise, create an empty list <code>S</code>.
# For each direct child node <code>c</code> of <code>e</code>:
## Run _STRINGIFY on <code>c</code> and add the result to <code>S</code>.
# Concatenate the items in list <code>S</code> and return them.

== Destruction ==

In some cases it is necessary to render an element and its children opaque to later microformat processing. The two functions DESTROYER and DESTROY_ELEMENT deal with this.

=== DESTROYER ===

This function aims to find any microformats within an element and make them opaque to later parsing.

* First parameter: element to operate on, <code>e</code>.
* Second parameter: list of microformats to "save" from destruction, <code>S</code>.

# Create a list <code>M</code> of all known compound microformat root classes. This list should include any microformats you know about, even if your parser does not include support for them. A sample list is included below.
# For each item in <code>S</code>: remove from <code>M</code>.
# For each descendent element <code>d</code> of <code>e</code> (not including <code>e</code> as a descendent of itself):
## If the class list of <code>d</code> includes one or more of the class names in <code>M</code>, then:
### Run the DESTROY_ELEMENT function on <code>d</code>.
### Modify the <code>class</code> attribute of <code>d</code>, removing any classes which appear in <code>M</code>.

==== Compound microformat root classes ====

<div style="float:left;width:22%">
* mfo
* vcard
* adr
* geo
* hreview
* xfolkentry
* hresume
* biota
</div>

<div style="float:left;width:22%">
* vcalendar
* vevent
* vtodo
* valarm
* vfreebusy
* hfeed
* hentry
* hslice
</div>

<div style="float:left;width:22%">
* haudio
* hmeasure
* hangle
* hmoney
* hlisting
* figure
* hproduct
* hmedia
</div>

 

Note that XOXO and XMDP are excluded from this list, as they are not ''compound'' microformats.

=== DESTROY_ELEMENT ===

The aim of this function is to make the innards of a particular element opaque to microformat parsing. The algorithm for "destroying" element <code>e</code> is as follows:

# Search for all elements which descend from <code>e</code>. For each such element <code>d</code>:
## Set the <code>class</code> attribute to the empty string.
## Set the <code>rel</code> attribute to the empty string.
## Set the <code>rev</code> attribute to the empty string.

= Hierarchy =

Generally speaking, when looking for a property <code>p</code> and an element with class <code>p</code> is found, we look for the value of <code>p</code> in the following places and use the first value that has been found:

# Appropriate attributes on <code>p</code>
# Appropriate attributes on any descendants of <code>p</code> with <code>class="value"</code> (using first in case of URLs/UIDs, concatenating otherwise)
# Contents of all descendants of <code>p</code> with <code>class="value"</code>, concatenated
# Contents of <code>p</code>

== Example ==

Looking for a URL, these should all be parsed as <nowiki>p="http://example.com/use-this"</nowiki>.

<pre><nowiki><a class="p" href="http://example.com/use-this">...</a></nowiki></pre>

<pre><nowiki>...<a class="value" href="http://example.com/use-this">...</a>...</nowiki></pre>

<pre><nowiki>...http://example.com/use-this...</nowiki></pre>

<pre><nowiki>http://example.com/use-this</nowiki></pre>

= Examples of Parsable HTML =

== Nested Microformats Examples ==

<pre><nowiki><div class="vcard">
Jack Bauer
<div class="agent">
Agent:
<div class="vcard">
Chloe O'Brian
</div>
</div>
</div></nowiki></pre>

<pre><nowiki><div class="vcard">
Jack Bauer
<div class="agent vcard">
Agent: Chloe O'Brian
</div>
</div></nowiki></pre>

OK, this one's getting complicated, but still works:

<pre><nowiki><div class="vcard">
Queen Elizabeth II's

representative in Australia is
Governor General
<a class="fn url" href="http://www.gg.gov.au/">Michael Jeffery</a>.

You can contact him through his secretary,
Malcolm Hazell.


</div></nowiki></pre>

Here's an "fn" inside an address:

<pre id="hCardFNinADRexample"><nowiki><div class="vcard">


Chemistry Library,
Fictional Institute of Science,

123 Example Street,
Testville.

</div></nowiki></pre>

== Plain Text Examples ==

All the following examples parse as "Foobar baz".

<pre><nowiki>Foobar baz</nowiki></pre>

<pre><nowiki><img class="note" alt="Foobar baz" src="foobar-baz.jpeg"></nowiki></pre>

<pre><nowiki>
Foo quux
bar baz xyzzy.
</nowiki></pre>

<pre><nowiki><abbr class="note" title="Foobar baz">FBB</abbr></nowiki></pre>

<pre><nowiki><div class="note">
Foobar
<abbr class="value" title=" baz">FBB</abbr>
</div></nowiki></pre>

<pre><nowiki>Foobar baz</nowiki></pre>

== URL Examples ==

The following are all parsed as the same URL.

<pre><nowiki><a class="url" href="http://example.com/page">Page</a></nowiki></pre>

<pre><nowiki>
<a href="http://example.com/not-this">Not this</a>
<a class="value" href="http://example.com/page">Page</a>
</nowiki></pre>

<pre><nowiki>
<a class="value" href="http://example.com/page">Page</a>
<a class="value" href="http://example.com/not-this">Not this</a>
</nowiki></pre>

<pre><nowiki>
http://example.com/
Not this
page
</nowiki></pre>

<pre><nowiki><img class="url" alt="foo" src="http://example.com/page"
longdesc="http://example.com/not-this"></nowiki></pre>

<pre><nowiki>
<img class="url" longdesc="http://example.com/page"></nowiki></pre>

<pre><nowiki>

<img src="http://example.com/not-this"
alt="http://example.com/page">
</nowiki></pre>

<pre><nowiki>

<img src="http://example.com/page"
alt="http://example.com/not-this" class="value">
</nowiki></pre>

== UID Examples ==

<pre><nowiki><a class="uid" href="http://example.com/page">Page</a></nowiki></pre>

<pre><nowiki>Not this</nowiki></pre>

<pre><nowiki><a class="uid" href="http://example.com/page" id="not-this">Page</a></nowiki></pre>

<pre><nowiki><div class="uid">
Not this
<a href="http://example.com/not-this" class="value">Not this</a>
</div></nowiki></pre>

== Datetime Examples ==

<pre><nowiki><time class="dtstart" datetime="2008-07-21">Monday</time></nowiki></pre>

<pre><nowiki>
<time class="value" datetime="2008-07-21">Monday</time> at
<time class="value" datetime="21:30">9:30pm</time>.
</nowiki></pre>

<pre><nowiki>
<time class="value" datetime="2008-07-21">Monday</time> at
<time class="value" datetime="21:30">9:30pm</time>
<time class="value" datetime="+1">(UK)</time>.
</nowiki></pre>

<pre><nowiki>
<abbr class="value" title="2008-07-21">Monday</time> at
<abbr class="value" title="T21:30">9:30pm</time>
<abbr class="value" title="+0100">(UK)</time>.
</nowiki></pre>

== Combination Examples ==

<pre><nowiki><div class="vcard">
<h1 class="fn">Toby Inkster</h1>
<ins class="rev url" datetime="2008-07-21T21:30:00+0100">
I launched my <a href="http://example.com/" class="value">new
website</a> today with the help of

graphic designer
Joe Bloggs.

</ins>
</div></nowiki></pre>

Parsed as:

'''First hCard:'''
* fn = "Toby Inkster"
* rev = 2008-07-21T21:30:00+0100
* url = http://example.com/

'''Second hCard:'''
* fn = "Joe Bloggs"
* role = "graphic designer"

Main Page

2009-11-04T09:32:55Z

AngeloGladding:

<entry-title>Welcome to the microformats wiki!</entry-title>
__TOC__
Please start with the [[introduction]] page and read [[how-to-play]] before making any edits.

==Introduction==
This wiki is the central resource of the microformats community. You'll find current versions of published microformat specifications, specification drafts and publishing patterns. The wiki also hosts development resources, such as brainstorming pages for new formats and issue tracking pages for all current and in-development microformats.

== Get Started==
To get started with microformats:

* First, be familiar writing your pages and applications with semantically rich, descriptive, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.
* Learn about microformats from the [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations]], [[books]], [[podcasts]], & [[screencasts]] pages.
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.
* Want to learn more in person? Check out microformats [[events]].

==Definition==
Microformats are small patterns of HTML to represent commonly published things like [[hcard|people]], [[hcalendar|events]], [[hatom|blog posts]], [[hreview|reviews]] and [[rel-tag|tags]] in web pages.

Microformats enable the publishing of higher fidelity information on the Web; the fastest and simplest way to provide feeds and APIs for the information in your website.

* Read more explanations of [[what-are-microformats|what microformats are]], and [[what-can-you-do-with-microformats|what you can do with them]].

== How to contribute ==
Do you want to help take microformats to the next level? You can:

* [[get-started|Get started]] by adding microformats to your website, services, and products.
* [[advocacy|Advocate]] the use of microformats on other web sites, especially those you use.
* Write a [[testimonial]].
* Do something on the [[to-do|to do list]].
* Join the [[irc|IRC Channel]] and [[mail|mailing lists]] to learn and help answer questions (read the [[mailing-lists#General_guidelines|general guidelines]] before posting).
* [[Main_Page#microformats_wiki_translations|Translate this microformats wiki into other languages]] to make microformats more accessible to readers of languages around the world.
* Before proposing any new microformats, make sure your website is [[POSH]], [[get-started|uses existing microformats]], and then read the [[process]].

This wiki has a number of enhancements to assist development and contributions to microformats. Before you start editing, see the [[wiki-2|wiki introduction page]] for instructions.

== Specifications ==
The list of current, stable [[microformats|Microformats]] open standard specifications.

* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]
* [[XMDP]]
* [[xoxo|XOXO]]

''If you're tempted to try your hand at writing a microformat please read '''[[process|the process]]''' page first!''

== Drafts ==
Drafts are newer microformats, for which the specifications haven't been completed yet. Drafts are somewhat mature in the development [[process]] (see [[exploratory-discussions]] for additional efforts that are not as far along in the process). The stability of these documents cannot be guaranteed, and implementers should be prepared to keep abreast of future developments and changes. Please watch the wiki pages for updates.

* [[adr|adr]] - for marking up address information
* [[geo|geo]] - for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates (latitude; longitude)
* [[hatom|hAtom]] - syndicating episodic content (e.g. weblog postings)
* [[haudio|hAudio]]
* [[hlisting|hListing]] - open, distributed listings
* [[hmedia|hMedia]] - A single media publishing format that relates to Images, Video and Audio.
* [[hnews|hNews]]
* [[hproduct|hProduct]]
* [[hrecipe|hRecipe]] - for cooking+baking recipes
* [[hresume|hResume]] - for publishing resumes and CVs
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page
* [[rel-enclosure]] - for indicating attachments (e.g. files) to download and cache
* [[rel-home]] - indicate a hyperlink to the homepage of the site
* [[rel-payment]] - indicate a payment mechanism
* [[robots-exclusion|robots exclusion]]
* [[xfolk|xFolk]]

== Design Patterns ==
{{design_patterns}} 

== Exploratory Discussions ==
See: [[exploratory-discussions]] for details of research and analysis of real-world [[examples]], existing formats, and brainstorming of possible new microformats, per the microformats [[process]].

== Examples ==
* [[examples-in-the-wild]]
* [[implementations]]
* [[zen-garden]]

== Resources ==
See [[resources]].

== User centric development ==
*[[user-interface]]
*[[data-portability]]
*[[social-network-portability]]

== Shared work areas ==
* [[to-do]]
* [[templates]]
* [http://microformats.org/wiki/delete pages for deletion] 
* [[Special:Specialpages|"Special" wiki pages]]
* [[year-in-review]]

== Tools, test cases, additional research ==
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting [[tools|tools and services]] that need to process more than one microformat. That section is intended for editors, [[parsers]], [[validators]], test cases, and other information relevant across multiple microformats.

== Microformats wiki translations ==
You may read and edit microformats articles in many other languages:

* languages with over 100 articles
** [[Main_Page-fr|Français (French)]] {{UpdateMarker-fr}}
* languages with over 10 articles
** [[Main_Page-pt-br|Português (Brazilian Portuguese)]]
** [[Main_Page-ja|日本語 (Japanese)]]
** [[Main_Page-ru|Русский (Russian)]]
* languages with over 2 articles
** [[Main_Page-cs|Česky (Czech)]] {{NewMarker}}
** [[Main_Page-de|Deutsch (German)]]
** [[Main_Page-es|Español (Spanish)]]
** [[Main_Page-gl|Galego (Galician)]] {{NewMarker}}
** [[Main_Page-pl|Polski (Polish)]]
** [[Main_Page-ro|Română (Romanian)]] {{NewMarker}}
** [[Main_Page-zh|汉语 (Chinese)]]
** [[Main_Page-id|Indonesia (Bahasa Indonesia)]] {{NewMarker}}
* languages just started
** [[Main_Page-ar|العربية (Arabic)]]
** [[Main_Page-th|ภาษาไทย (Thai)]]
** [[Main_Page-it|Italiano (Italian)]] {{NewMarker}}
** [[Main_Page-ko|한국어 (Korean)]] {{NewMarker}}
* elsewhere
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] has been translated into a number of languages.

See also [[other-languages]], and [[how-to-start-new-translation|how-to-start-a-new-translation]].

Main Page

2009-11-04T09:32:15Z

AngeloGladding:

<entry-title>Welcome to the microformats wiki!</entry-title>
__TOC__
Please start with the [[introduction]] page and read [[how-to-play]] before making any edits.

==Introduction==
This wiki is the central resource of the microformats community. You'll find current versions of published microformat specifications, specification drafts and publishing patterns. The wiki also hosts development resources, such as brainstorming pages for new formats and issue tracking pages for all current and in-development microformats.

== Get Started==
To get started with microformats:

* First, be familiar writing your pages and applications with semantically rich, descriptive, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.
* Learn about microformats from the [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations]], [[books]], [[podcasts]], & [[screencasts]] pages.
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.
* Want to learn more in person? Check out microformats [[events]].

==Definition==
Microformats are small patterns of HTML to represent commonly published things like [[hcard|people]], [[hcalendar|events]], [[hatom|blog posts]], [[hreview|reviews]] and [[rel-tag|tags]] in web pages.

Microformats enable the publishing of higher fidelity information on the Web; the fastest and simplest way to provide feeds and APIs for the information in your website.

* Read more explanations of [[what-are-microformats|what microformats are]], and [[what-can-you-do-with-microformats|what you can do with them]].

== How to contribute ==
Do you want to help take microformats to the next level? You can:

* [[get-started|Get started]] by adding microformats to your website, services, and products.
* [[advocacy|Advocate]] the use of microformats on other web sites, especially those you use.
* Write a [[testimonial]].
* Do something on the [[to-do|to do list]].
* Join the [[irc|IRC Channel]] and [[mail|mailing lists]] to learn and help answer questions (read the [[mailing-lists#General_guidelines|general guidelines]] before posting).
* [[Main_Page#microformats_wiki_translations|Translate this microformats wiki into other languages]] to make microformats more accessible to readers of languages around the world.
* Before proposing any new microformats, make sure your website is [[POSH]], [[get-started|uses existing microformats]], and then read the [[process]].

This wiki has a number of enhancements to assist development and contributions to microformats. Before you start editing, see the [[wiki-2|wiki introduction page]] for instructions.

== Specifications ==
The list of current, stable [[microformats|Microformats]] open standard specifications.

* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]
* [[XMDP]]
* [[xoxo|XOXO]]

''If you're tempted to try your hand at writing a microformat please read '''[[process|the process]]''' page first!''

== Drafts ==
Drafts are newer microformats, for which the specifications haven't been completed yet. Drafts are somewhat mature in the development [[process]] (see [[exploratory-discussions]] for additional efforts that are not as far along in the process). The stability of these documents cannot be guaranteed, and implementers should be prepared to keep abreast of future developments and changes. Please watch the wiki pages for updates.

* [[adr|adr]] - for marking up address information
* [[geo|geo]] - for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates (latitude; longitude)
* [[hatom|hAtom]] - syndicating episodic content (e.g. weblog postings)
* [[haudio|hAudio]]
* [[hlisting|hlisting]] - open, distributed listings
* [[hmedia|hMedia]] - A single media publishing format that relates to Images, Video and Audio.
* [[hnews|hNews]]
* [[hproduct|hProduct]]
* [[hrecipe|hRecipe]] - for cooking+baking recipes
* [[hresume|hResume]] - for publishing resumes and CVs
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page
* [[rel-enclosure]] - for indicating attachments (e.g. files) to download and cache
* [[rel-home]] - indicate a hyperlink to the homepage of the site
* [[rel-payment]] - indicate a payment mechanism
* [[robots-exclusion|robots exclusion]]
* [[xfolk|xFolk]]

== Design Patterns ==
{{design_patterns}} 

== Exploratory Discussions ==
See: [[exploratory-discussions]] for details of research and analysis of real-world [[examples]], existing formats, and brainstorming of possible new microformats, per the microformats [[process]].

== Examples ==
* [[examples-in-the-wild]]
* [[implementations]]
* [[zen-garden]]

== Resources ==
See [[resources]].

== User centric development ==
*[[user-interface]]
*[[data-portability]]
*[[social-network-portability]]

== Shared work areas ==
* [[to-do]]
* [[templates]]
* [http://microformats.org/wiki/delete pages for deletion] 
* [[Special:Specialpages|"Special" wiki pages]]
* [[year-in-review]]

== Tools, test cases, additional research ==
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting [[tools|tools and services]] that need to process more than one microformat. That section is intended for editors, [[parsers]], [[validators]], test cases, and other information relevant across multiple microformats.

== Microformats wiki translations ==
You may read and edit microformats articles in many other languages:

* languages with over 100 articles
** [[Main_Page-fr|Français (French)]] {{UpdateMarker-fr}}
* languages with over 10 articles
** [[Main_Page-pt-br|Português (Brazilian Portuguese)]]
** [[Main_Page-ja|日本語 (Japanese)]]
** [[Main_Page-ru|Русский (Russian)]]
* languages with over 2 articles
** [[Main_Page-cs|Česky (Czech)]] {{NewMarker}}
** [[Main_Page-de|Deutsch (German)]]
** [[Main_Page-es|Español (Spanish)]]
** [[Main_Page-gl|Galego (Galician)]] {{NewMarker}}
** [[Main_Page-pl|Polski (Polish)]]
** [[Main_Page-ro|Română (Romanian)]] {{NewMarker}}
** [[Main_Page-zh|汉语 (Chinese)]]
** [[Main_Page-id|Indonesia (Bahasa Indonesia)]] {{NewMarker}}
* languages just started
** [[Main_Page-ar|العربية (Arabic)]]
** [[Main_Page-th|ภาษาไทย (Thai)]]
** [[Main_Page-it|Italiano (Italian)]] {{NewMarker}}
** [[Main_Page-ko|한국어 (Korean)]] {{NewMarker}}
* elsewhere
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] has been translated into a number of languages.

See also [[other-languages]], and [[how-to-start-new-translation|how-to-start-a-new-translation]].

irc-people

2009-11-03T23:42:05Z

AngeloGladding:

A list of [[irc|IRC]] regulars, sorted by nick, and their normal timezones (winter/summer).

* {{irc user|Amodal1| amodal1|-0500/-0600}}
* {{irc user|Adam Ballai|AdamBallai|-700/-700}}
* {{irc user|Adam Craven|AdamCraven|+0000}}
* {{irc user|Alenonimo|Alenonimo|-0300}}
* {{irc user|Alexander Graf|AlexanderGraf|+0100}}
* {{irc user|Tomasino|aloneone|-0500}}
* {{irc user|AmanuelTewolde|Amanuel|-0500/-0400}}
* {{irc user|Amette|amette|+1000}}
* {{irc user|Amir Guindehi|AmirGuindehi|+1000}}
* {{irc user|Andr3|andr3|+0000}}
* {{irc user|Ajaswa|Andrew Jaswa|-0500}}
* {{irc user|AndrewDisley|AndrewDisley|+0000}}
* {{irc user|Andrii Ponomarov|Andrii|+0300}}
* {{irc user|AngeloGladding|angelogladding|-0800/-0700}}
* {{irc user|AnselHalliburton|anselxyz|-0800/-0700}}
* {{irc user|Ashe Dryden|Ashe|-600}}
* {{irc user|Atamido|Atamido|-0600/-0500}}
* {{irc user|Barce|Barce|-0800/-0700}}
* {{irc user|Azathoth|Florian Beer|+1000}}
* {{irc user|Tyler Roehmholdt|Baristo|-0800/-0700}}
* {{irc user|Belling|Belling|-0800/-0700}}
* {{irc user|BenjaminCarlyle|BenjaminCarlyle|+1000}}
* {{irc user|HenriBergius|bergie|+0200/+0300}}
* {{irc user|Ben Ward|BenWard|-0800/-0700}}
* {{irc user|BenWest|bewest|-0800/-0700}}
* {{irc user|B.K._DeLong|bkdelong|-0500/-0400}}
* {{irc user|Robert|blueace|+0100}}
* {{irc user|Robert|blueace|+0100}}
* {{irc user|BluesMoon|bluesmoon|+0530}}
* {{irc user|BobChao|BobChao|+0800}}
* {{irc user|Bob Jonkman|BobJonkman|-0500/-0400}}
* {{irc user|Boneill|boneill|+0000}}
* {{irc user|Brian|briansuda|+0000}}
* {{irc user|TimT|bringo|-0800/-0700}}
* {{irc user|Briski|Briski|+0000}}
* {{irc user|BryanL|BryanL|-0500/-0400}}
* {{irc user|BryanRieger|Bryan Rieger|+0000}}
* {{irc user|Bug-E|Bug-E|+0200}}
* {{irc user|CarlaHufstedler|carlamagpie|-0500/-0400}}
* {{irc user|Colin_Barrett|cbarrett|-1000}}
* {{irc user|Cognizance|Cognizance|-0800/-0700}}
* {{irc user|ColinDDevroe|cdevroe|-0500/-0600}}
* {{irc user|Cgriego|cgriego|-0600/-0500}}
* {{irc user|Charlvn|Charl|+0200/+0200}}
* {{irc user|CharlesRoper|charles_r|0000/+0100}}
* {{irc user|Chris_Cressman|Chris Cressman|-0500/-0400}}
* {{irc user|ChristopherStJohn|cks|-0600/-0500}}
* {{irc user|JeremyBoggs|clioweb|-5000/-4000}}
* {{irc user|Cloud|Cloud|+0000}}
* {{irc user|Cruster|cruster|+0200}}
* {{irc user|Csarven|csarven|-0500/-0400}}
* {{irc user|ChrisBrentano|ctb|-0800/-0700}}
* {{irc user|DanC|DanC|-0600/-0500}}
* {{irc user|DanielBurka|DanielBurka|-0400}}
* {{irc user|DanielJohnLewis|danieljohnlewis|0000}}
* {{irc user|DannyAyers|danja|+0100/+0200}}
* {{irc user|Dave Cardwell|davecardwell|+0000}}
* {{irc user|DavidMead|DavidMead|-0400}}
* {{irc user|DavidRussell|davidrussell|-0600/-0500}}
* {{irc user|DBounds|Darren Bounds|-0500}}
* {{irc user|Ddonat|David Gratton|-0800/-700}}
* {{irc user|DenisDefreyne|ddfreyne|+0100/+0200}}
* {{irc user|DeanEro|deanero|-0800/-0700}}
* {{irc user|DeepText|Deep Text|-0800/-0700}}
* {{irc user|DerrickPallas|DerrickPallas|-0800/-0700}}
* {{irc user|DimitriGlazkov|dglazkov|-0600/-0500}}
* {{irc user|DiegoBudny|DiegoBudny|-unspecified-}}
* {{irc user|DKerzman|DKerzman|-0600}}
* {{irc user|Dan Kubb|dkubb|-0800/-0700}}
* {{irc user|DrErnie|DrErnie|-0800/-0700}}
* {{irc user|DrewMcLellan|drewinthehead|+0000/+0100}}
* {{irc user|DrewBell|droob|-0600/-0500}}
* {{irc user|DimitriosZachariadis|dzach|+0200/+0300}}
* {{irc user|DydimusTK|dydimustk|-0600}}
* {{irc user|Ed Summers|edsu|-0500/-0400}}
* {{irc user|Enric|Enric|-0800/-0700}} (alt sp "enric")
* {{irc user|Evan|evanpro|-0500}}
* {{irc user|Evan|e_s_p|-0500}}
* {{irc user|Ket Majmudar|ethicaljunction|+0100}}
* {{irc user|EdwardWelker|ewelker|-0500}}
* {{irc user|ChrisMessina|factoryjoe|-0800/-0700}}
* {{irc user|Fil|Fil|+0200}}
* {{irc user|CFinke|Finke|-0700/-0600}}
* {{irc user|MarkoMrdjenovic|friedcell|+0100/+0200}}
* {{irc user|GarethR|garethr|+0000/+0100}}
* {{irc user|GeorgeBrock|georgebrock|+0000/+0100}}
* {{irc user|Grantbow|Grantbow|-0800/-0700}}
* {{irc user|Griffin|Griffin|-0600/-0500}}
* {{irc user|Guillaume Lebleu|glebleu|-0800}}
* {{irc user|Aubergine10|Guy Fraser|+0100/+0000}}
* {{irc user|HenrichPoehls|HenrichP|+0100}}
* {{irc user|IanHickson|Hixie|-0800/-0700}}
* {{irc user|Hlb|hlb|+0800-0700}}
* {{irc user|EdwardOConnor|hober|-0800/-0700}}
* {{irc user|Ichigo|ichigo|+1000}}
* {{irc user|Alper|illustir|+0100}}
* {{irc user|Inkbase|inkbase|-0800/-0700}}
* {{irc user|IwaiMasaharu|iwaim|+0900}}
* {{irc user|Izo|IZO|-unspecified-}}
* {{irc user|Jabz|Jabz|+0000}}
* {{irc user|JamieKnight|JamieKnight|+1000/0000}}
* {{irc user|JayMyers|jaymyers|-0600/-0500}}
* {{irc user|JoeGregorio|jcgregorio|-unspecified-}}
* {{irc user|WizardIsHungry|jcw9|-0500/-0400}}
* {{irc user|Adactio|Jeremy Keith|+0000}}
* {{irc user|jrodgers|JesseRodgers|-0500}}
* {{irc user|JasonK|jkridner|-0600/-0500}}
* {{irc user|JeffMcNeill|jeffmcneill|-1000}}
* {{irc user|JimboJW|jimbojw|-0600/-0500}}
* {{irc user|Jonathan_Arkell|jonnay|-0700/0600}}
* {{irc user|JonathanMalek|JonathanMalek|-0800/-0700}}
* {{irc user|JosephHolsten|josephholsten|-0600/-0500}}
* {{irc user|JulianStahnke|julianstahnke|+0000}}
* {{irc user|Kapowaz|kapowaz|+0000/+0100}}
* {{irc user|Keri Henare|kerihenare|+1200}}
* {{irc user|KevBurnsJr|kevburnsjr|-0800}}
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)
* {{irc user|RyanKing|kingryan|-0800/-0700}}
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC
* {{irc user|Lachlan Hunt|Lachy|+1000/+1100}}
* {{irc user|Levitation|levitation[A]|+0200/+0300}}
* {{irc user|Linmic|linmic|+0800-0700}}
* {{irc user|MarkNg|madness|+0000/+0100}}
* {{irc user|Mark Mansour|Mark Mansour|+1100}}
* {{irc user|MarkNormanFrancis|Mark Norman Francis|+0000/+0100}}
* {{irc user|Maddiin|Martin Czura|+0100}}
* {{irc user|MattBowen|Matt Bowen|-0500/-0400}}
* {{irc user|Groningen|Matthias Kluth|+0100}}
* {{irc user|MattisManzel|Mattis Manzel|+0100/+0200}}
* {{irc user|CiaranMc|McNulty|+0000/+0100}}
* [[mfbot]] - a bot which logs all edits to this wiki. It appends a number with a '+' or '-' sign, to indicate the number of characters added or removed as a result of the edit.
* {{irc user|Mike|Michael McCracken(mmc)|-0800/-0700}}
* {{irc user|MikeKaply|mkaply|-0600/-0500}}
* {{irc user|SteveIvy|monkinetic/redmonk|-0700}}
* {{irc user|MWTE|mwte|+0000/+0100}}
* {{irc user|RobManson|nambor|+1000}}
* {{irc user|Naterkane|Nater Kane|-0500}}
* {{irc user|Nelix|nelix|+1000}}
* {{irc user|neuro|neuro|-unspecified-}}
* {{irc user|Niekie|niekie|+0100/+0200}}
* {{irc user|NTollervey|ntoll|+0000/+0100}}
* {{irc user|Pawlik|pawlik|+0100/+0200}}
* {{irc user|Andy Pemberton|pembertona|-0500/-0400}}
* {{irc user|Phae|Phae|+0000/+0100}}
* {{irc user|pius|Pius Uzamere|+0500}}
* {{irc user|PriitLaes|plaes|+0200/+0300}}
* {{irc user|ChrisCasciano|pnhChris|-0500/-0400}}
* {{irc user|Hugopeixoto|Politoed|+0000/+0100}}
* {{irc user|PetarPopov|popov|-0800/-0700}}
* {{irc user|Pfefferle|pfefferle|+0100/+0200}}
* {{irc user|Lauren Scime|pseudowish|-0800/-700}}
* {{irc user|DavidOsolkowski|qid|-0500}}
* {{irc user|RCanine|RCanine|-0500/-0400}}
* {{irc user|Remi|Remi|-0500/-0400}}
* {{irc user|ZachCarter|riah|-0500/-0400}}
* {{irc user|RobertBachmann|RobertBachmann|+0100/+0200}}
** Office hours: <s>Wednesday, 18:00-20:00 UTC</s> (Currently no office hours}}
* {{irc user|RobLinton|RobLinton|-0800/-0700}}
* {{irc user|Ronnos|Ron Kok|+0000}}
* {{irc user|SamJohnston|samj|+0100/+0200}}
* {{irc user|SarahWorsham|sazbean|-0500/-0400}}
* {{irc user|ScottNelle|snelle|-0500/-0400}}
* {{irc user|ScottRozic|gravitas|-0500/+0100}}
* {{irc user|Dana Benson|Snowden|-0800/-0700}}
* {{irc user|SinDoc|SinDoc|+0100/+0200}}
* {{irc user|Savell Martin|Savell|+0000/+0000}}
* {{irc user|Smackman|Steve Farrell|-0800/-0700}}
* {{irc user|SpikeUK|SpikeUK|+0000/+0100}}
* {{irc user|Steve Ganz|SteveGanz|-0800/-0700}}
* {{irc user|Stii|Stii|+0200 GMT}}
* {{irc user|ReinierZ|surial|+0100 GMT}}
* {{irc user|SuperPhly|SuperPhly|-600/-500}}
* {{irc user|SyedSRahman|syedsrahman|+0530}}
* sym[[User:LynX|lynX]] or (better) [[User:LynX|lynX]] on [http://about.psyc.eu PSYC] (+0100}}
* {{irc user|DavidLehn|taaz|-0500/-0400}}
* {{irc user|Tantek|Tantek|-0800/-0700}}
* {{irc user|tbmartin|tbmartin|-0800/-0700}}
* {{irc user|themattharris|themattharris|-0800/-0700}}
* {{irc user|Wojciech|theanxy|+0100/+0200}}
* {{irc user|TheJbf|thejbf|+0100/+0200}}
* {{irc user|thuddwhirr|thuddwhirr|-0800/-0700}}
* {{irc user|TobyInk|tobyink|+0000/+0100}}
* {{irc user|Trovster|trovster|-0800/-0700}}
* {{irc user|Vadania|vadania|-0600/-0700}}
* {{irc user|Vant|vant|+0900}}
* {{irc user|venkateswaran|vensilver|+5.30 GMT}}
* {{irc user|Victor|victor|+0100/+0200}}
* {{irc user|V-I-P|V-I-P|+0100/+0200}}
* {{irc user|KrissWatt|VoodooChild|+0000/+0100}}
* {{irc user|WebOrganics|weborganics|+0100}}
* {{irc user|JacksonWilkinson|whafro|-0500/-0400}}
* {{irc user|Richard Conyard|WhiskeyM|+0000}}
* {{irc user|Veeliam|William Lawrence|-0800/-0700}}
* {{irc user|StevenWoods|woodss|+0000 GMT}}
* {{irc user|Ianloic|yakk|-0800/-0700}}
* {{irc user|LarsStrojny|mastaYoda|+0100}}
* {{irc user|ZimbaTm|zimbatm|+0100}}
* {{irc user|FoundAtion|Foundation|-0800}}
* {{irc user|PJKix|pjkix|-0800/-700}}
* {{irc user| ChrisBroadfoot|broady|+1000}}
* {{irc user|Natalie Downe|NatBat|+0000}}
* {{irc user|Dotjay|dotjay|+0000}}
* {{irc user|PeterHellberg|zil|+0100}}
* {{irc user|Kiryl Zhybul|zkv|+0400}}
* {{irc user|ScottThorpe|Salve|-0800/-0700}}
* {{irc user|Dane|imdane|-0600/-0500}}
* {{irc user|ThomasLoertsch|tl|+0100/+0200}}
* {{irc user|Francisco Bernardo|frantic0|+0100/+0200}}
* {{irc user|Steven Osborn|steve918|-0700/-0800}}
* {{irc user|Trodrigues|trodrigues|+0000}}

User:AngeloGladding

2009-11-03T23:33:32Z

AngeloGladding:

Angelo Gladding

angelo@gladding.name

http://angelo.gladding.name/

{{public-domain-release}}

user/AngeloGladding

2008-06-24T01:08:19Z

AngeloGladding:

Angelo Gladding

me@angelogladding.com

http://angelogladding.com/

user/AngeloGladding

2008-06-24T01:08:09Z

AngeloGladding:

Angelo Gladding
me@angelogladding.com
http://angelogladding.com/

user/AngeloGladding

2008-06-24T01:07:57Z

AngeloGladding:

Angelo Gladding
me@angelogladding.com
http://angelogladding.com/

food-item-examples

2008-02-19T09:01:21Z

AngeloGladding:

= Food Item Examples =
Restaurant menus can be found scattered

== The Problem ==
''What is the purpose of this exploration?''

== Participants ==
* [[User:AngeloGladding|Angelo Gladding]]

== Real-World Examples ==
''Links to public web pages, either popular or insightful''

=== [http://www.thecrepevine.com/menu.html The Crepe Vine] ===
<pre>
APPETIZERS
IMPORTED CHEESE PLATE & BAGUETTE ..........13 
 
TUNA TARTARE  ..........8
 
fresh tuna with roasted shallot aioli, and lotus chips
 
 
BRUSCHETTA ..........8
 
tomato, garlic, basil, chevre, olive oil and balsamic on crostini
 
 
STEAK TARTARE  .......... 12
 
Horseradish aioli, caramelized shallots, and potato hash
 
 
BABY BEET SALAD  ..........11
 
candy cane baby beets, sherry vinaigrette and herb goat cheese
</pre>

== Existing Practices ==
* ''Summary of common patterns discovered''
* ''Other attempts to solve The Problem''

== Proposal ==
* Early drafts
* ''Link to related pages as they become available''
** -brainstorming
** - proposal
** -microformat

== See Also ==
* ''Other microformats''
* ''Normative references for tags used''

food-item-examples

2008-02-19T08:56:20Z

AngeloGladding: work in progress

= Food Item Examples =
Restaurant menus can be found scattered

== The Problem ==
''What is the purpose of this exploration?''

== Participants ==
* [User:AngeloGladding]

== Real-World Examples ==
''Links to public web pages, either popular or insightful''

=== [http://www.thecrepevine.com/menu.html The Crepe Vine] ===
<pre>
APPETIZERS
IMPORTED CHEESE PLATE & BAGUETTE ..........13 
 
TUNA TARTARE  ..........8
 
fresh tuna with roasted shallot aioli, and lotus chips
 
 
BRUSCHETTA ..........8
 
tomato, garlic, basil, chevre, olive oil and balsamic on crostini
 
 
STEAK TARTARE  .......... 12
 
Horseradish aioli, caramelized shallots, and potato hash
 
 
BABY BEET SALAD  ..........11
 
candy cane baby beets, sherry vinaigrette and herb goat cheese
</pre>

=== [Example #2 (http://google.com)] ===
pre
escaped <tags>

== Existing Practices ==
* ''Summary of common patterns discovered''
* ''Other attempts to solve The Problem''

== Proposal ==
* Early drafts
* ''Link to related pages as they become available''
** -brainstorming
** - proposal
** -microformat

== See Also ==
* ''Other microformats''
* ''Normative references for tags used''

User:AngeloGladding

2008-02-19T08:48:32Z

AngeloGladding:

Angelo Gladding

[http://angelogladding.com http://angelogladding.com]

me@angelogladding.com

{{public-domain-release}}

food-item-examples

2008-02-19T06:33:11Z

AngeloGladding: work in progress

= Food Item Examples =

<pre>
APPETIZERS
IMPORTED CHEESE PLATE & BAGUETTE ..........13 

 
TUNA TARTARE  ..........8 
fresh tuna with roasted shallot aioli, and lotus chips 
BRUSCHETTA ..........8 
tomato, garlic, basil, chevre, olive oil and balsamic on crostini 
 
STEAK TARTARE  .......... 12 

Horseradish aioli, caramelized shallots, and potato hash 
 
BABY BEET SALAD  ..........11 
candy cane baby beets, sherry vinaigrette and herb goat cheese
</pre>