Microformats Wiki - User contributions [en]

hcalendar-authoring

2006-07-09T18:11:39Z

Jonathan Arkell: /* Adding hCalendar markup to existing content */

<h1>hCalendar authoring</h1>

This page contains useful tips and guidelines for how to author [[hcalendar|hCalendar]] events, either from scratch, or by adding markup to existing content.

'''Goal:''' The goal of this document is to provide some good intuitive guidelines that should make it as easy and as quick as possible for any web author to create hCalendar events or add hCalendar markup to existing content.

'''Audience:''' Web authors and designers. This document is written for easy consumption and understanding by any web designer who knows at least enough (X)HTML and CSS to use HTML class names on elements and write CSS selectors that apply styles to those class names. Please help with clarifying/simplifying this document accordingly.

'''Author(s):''' Tantek Çelik

__TOC__

== Creating new hCalendar events ==

Start with the [http://microformats.org/code/hcalendar/creator hCalendar creator], and for additional fields and properties (e.g. contact, attendees, etc.), see the [[hcalendar-examples|hCalendar examples]] page as well as the rest of this page.

== Adding hCalendar markup to existing content ==

=== Minimal Markup Changes ===

The important thing to keep in mind when adding microformats to existing content, is the fact that microformats are designed so that they can be added with minimal (almost always no) changes to the existing presentation of the page. Thus keep this in mind: change as little markup as possible. If you want to fix various pages to be valid XHTML as well, that's fine goal and highly encouraged.

In all cases below, where it says to add an element with class name of "xyz", if you can find an existing element that precisely surrounds the necessary content, then re-use that element and simply add the class name "xyz" to it (by adding it to the class attribute on the existing element, or by adding a new class attribute <code>class="xyz"</code> to elements without a class attribute).

For instance, assuming you have the following markup:

<pre><nowiki>
<div class="someFoo">
<p> This is my wonderful markup, it contains some event information inside of it</p>
<h6>Some Wonderful Event</h6>
<p> From the people who brought you Great Times and Fun Lovin,
comes the Some Wonderful Event at the Local Sports Stadium.
Come at <b>A Specified Time</b>, and enjoy yourself! </p>
</div>
</nowiki></pre>

If you need to add an element with the class of "vevent" around your event content, you could re-use the existing div element, and add the class "vevent" to it like so:
<pre><nowiki>
<div class="someFoo vevent">
</nowiki></pre>
Similarly, if you decide not to re-purpose an existing container, you can just wrap the content around a new block:
<pre><nowiki>
<div class="someFoo">
<div class="vevent">
<p> This is my wond...
...
... and enjoy yourself! </p>
</div>
</div>
</nowiki></pre>

=== Find Events ===

Start with looking for all mentions of events on a page, such as an "Upcoming Events" or "Recent Events" listing. Those are all potential hCalendar events. Even more so if they are linked to their respective URLs (e.g. per event pages with more details).

If an event is mentioned several times on a page, consider marking up the mention which is the most persistent, detailed, definitive, or otherwise thorough as an hCalendar event. Ideally you might want to mark up ''all'' instances of a events with hCalendar, but for now, just keep it simple and markup the most representative instance. (Perhaps the most "definitive" instance, which could also then be marked up with a <code><nowiki><dfn></nowiki></code> element around the summary/title of the event for additional semantic XHTML goodness.)

=== Determine The Surrounding Element for Each ===

For each event that you want to add hCalendar, find the smallest element that contains all the info about that event, without overlapping with any other event on the page.

Add the class name "<code>vevent</code>" to that element.

If there is no such element (perhaps the nearest enclosing element contains more than one event), then add a <code><nowiki><span class="vevent">...</span></nowiki></code> or <code><nowiki><div class="vevent">...</div></nowiki></code> that wraps the info about about that event and just that event.

The rest of the markup for this hCalendar event MUST go ''inside'' that element with the class name "vevent".

=== The Importance of Time and Topic ===

Several properties are required in hCalendar. At a minimum, an event needs a "summary" (AKA title) and "dtstart" (starting date time), as well as either a "dtend" (ending date time) or "duration". Thus be sure to mark up the name/summary/title of the event with the class name "summary". E.g.

<pre><nowiki>
<div class="vevent">
<span class="summary">An Event Apart, New York City, NY</span>,
<abbr class="dtstart" title="20060710">July 10</abbr>-<abbr class="dtend" title="20060712">11th, 2006</abbr>
</div></nowiki></pre>

This event might be presented like:

An Event Apart, New York City, NY, <abbr class="dtstart" title="20060710">July 10</abbr>-<abbr class="dtend" title="20060712">11th, 2006</abbr>

Note: the use of the abbr element's title attribute to markup a machine readable absolute datetime in addition to the human readable text. Note also that the machine readable ending date is the day *after* the date specified in the human readable content. The reason for this is that hCalendar still interprets an ending date without a time as an instant in time, that is midnight, the absolute beginning of that day, thus ending the event the day before. See [[hcalendar|hCalendar]] and [[hcalendar-example1-steps]] for more details on the use of the abbr element in this fashion.

=== Eliminating Default Dotted Underline ===

Some browsers (Camino, Firefox, Mozilla) put a <span style="border-bottom:dotted 1px">dotted underline or border</span> on each <abbr title="abbreviation">abbr</abbr>. This is typically an ugly effect and distracting in most clean modern web designs. Thus be sure to use the following rule in your style sheet to eliminate this default presentation.

<pre><nowiki>
abbr{border:0}
</nowiki></pre>

In the above example, this would have the following effect (which may not look any different for some readers):

An Event Apart, New York City, NY, <abbr style="border:0" class="dtstart" title="20060710">July 10</abbr>-<abbr style="border:0" class="dtend" title="20060712">11th, 2006</abbr>

=== Representative URLs ===

One of the most common patterns for events in web content is to link them to their definitive/preferred web site.

"Event Rolls" are a good example of this (see also [[xoxo|XOXO]] for proper semantic list and outline markup).

Since the class attribute takes a space separated set of class names, one can often markup the URL on the same element as the name, e.g. by replacing the first <code><nowiki><span></nowiki></code> in the above example with an <code><nowiki><a href></nowiki></code> hyperlink:

<pre><nowiki>
<div class="vevent">
<a href="http://aneventapart.com/events/2006/nyc/" class="summary url">An Event Apart, New York City, NY</a>,
<abbr class="dtstart" title="20060710">July 10</abbr>-<abbr class="dtend" title="20060712">11th, 2006</abbr>
</div></nowiki></pre>

This event might be presented like:

[http://aneventapart.com/events/2006/nyc/ An Event Apart, New York City, NY], <abbr style="border:0" class="dtstart" title="20060710">July 10</abbr>-<abbr style="border:0" class="dtend" title="20060712">11th, 2006</abbr>

=== Location Location Location ===

As with real estate, the location of an event is quite relevant, and important to markup properly. At a minimum, identify the location related information in the event and mark it up with the class name of "locatioin", e.g. continuing with the above example:

<pre><nowiki>
<div class="vevent">
<a href="http://aneventapart.com/events/2006/nyc/" class="summary url">An Event Apart,
<span class="location">New York City, NY</span></a>,
<abbr class="dtstart" title="20060710">July 10</abbr>-<abbr class="dtend" title="20060712">11th, 2006</abbr>
</div></nowiki></pre>

This is good, but can be made even better with the addition of the [[adr]] microformat to explicitly identify the city and state:

<pre><nowiki>
<div class="vevent">
<a href="http://aneventapart.com/events/2006/nyc/" class="summary url">An Event Apart,
<span class="location adr"><span class="locality">New York City</span>, <span class="region">NY</span></span></a>,
<abbr class="dtstart" title="20060710">July 10</abbr>-<abbr class="dtend" title="20060712">11th, 2006</abbr>
</div></nowiki></pre>

Even better, if the location has a name, such as a business or organization, make the location into complete [[hcard|hCard]] rather than just an [[adr]]:

<pre><nowiki>
<div class="vevent">
<a href="http://aneventapart.com/events/2006/nyc/" class="summary url">An Event Apart,
<span class="location vcard">
<span class="fn org">Scandinavia House</span>,
<span class="adr"><span class="locality">New York City</span>, <span class="region">NY</span></span>
</span></a>,
<abbr class="dtstart" title="20060710">July 10</abbr>-<abbr class="dtend" title="20060712">11th, 2006</abbr>
</div></nowiki></pre>

=== More tips and guidelines ===

Feel free to add more tips that experience has taught you while marking up events with hCalendar, even if all you add is a brief catch phrase that reminds you.

* How to mark up the contact and organizer
* How to mark up attendees (including speakers)
* ...

=== See Also ===

* [[hcalendar|hCalendar]]
* [[hcalendar-profile|hCalendar profile]]
* [[hcalendar-examples|hCalendar examples]]
* [[hcalendar-brainstorming]]
* [[hcard-authoring]]
* [[hcard|hCard]]

User:DavidJanes

2006-04-14T00:12:27Z

Jonathan Arkell:

= David Janes =

* [http://www.davidjanes.com Home Page]
* [http://blog.davidjanes.com Weblog] (Home)
* [http://www.blogmatrix.com Work]
* [http://blogmatrix.blogmatrix.com Weblog] (Work)

== Microformats I'm working on ==

=== Primo ===
* [[hatom|hAtom]]
* [[blog-post-examples]], [[blog-post-formats]], [[blog-post-brainstorming]]
* [[abbr-design-pattern]]
* [[class-design-pattern]]
* [[rel-design-pattern]]

=== Secundo ===
* [[datetime-design-pattern]]

== Mailbox ==

Thanks for letting me know the root element of my hResume was broken. --[[User:Jonathan Arkell]]

User:Jonathan Arkell

2006-04-14T00:12:06Z

Jonathan Arkell:

== Jonathan Arkell ==
email: jonnay@jonnay.net
website: http://www.jonnay.net
blog: http://blog.jonnay.net
wiki: http://wiki.jonnay.net

Programmer, Graphic Designer, Musician.

I am currently just playing around with microformats. I have made a REST <-> SQL interface called MyRestSql that outputs XHTML fragments, in microformats where applicable, and I am also working on a PHP template/widget thing that will spit out microformats.

MyRestSql is at http://bunny.jonnay.net/projects/Meditation/examples/MyRestSql/table.php and uses xoxo, plus a potential microformat that is tentatively named hSql. I'll be expanding on this at some point in the undetermined future, one I can find more examples in the wild.

My Portfolio website uses hCard and hResume: http://portfolio.jonnay.net

== Wiki Mailbox ==

Empty

hresume

2006-04-14T00:07:09Z

Jonathan Arkell: /* Examples in the wild */ Fixed root element on my portfolio

<h1> hResume </h1>

hResume is a microformat for publishing resumes and CVs.

This paragraph is where we write some thing that makes everyone in the world want to use hResume. Because, you know, hResume's the future and people like the future. And so on... [[hresume-use|Wanna get started on hResume right now?]]

<h2> Microformats Draft Specification </h2>

; Editor/Author: [http://theryanking.com Ryan King]
; Acknowledgments: See [http://microformats.org/wiki/hresume#Acknowledgements acknowledgments].

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

__TOC__

== Status ==
Draft, version 0.1.

== Introduction ==
=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

== Format ==
=== In General ===
The hResume format is based on a set of fields common to numerous resumes published today on the web. Where possible field names have been chosen and reused from preexisting microformats.

=== Schema ===
The hResume schema consists of the following:

* hResume
** summary. optional. text.
** contact info. required. <code class="element"><address></code> + [[hcard|hCard]].
** experience. optional. One or more [[hcalendar]] events with the class name '<code class="class-name">experience</code>', with an embedded [[hcard|hCard]] indicating the job title, name of company, address of company etc.
** education. optional One or more [[hcalendar]] events with the class name '<code class="class-name">education</code>', with an embedded [[hcard|hCard]] indicating the name of school, address of school etc.
** skills. optional. phrases or keywords using the [[rel-tag]] microformat with the class name '<code class="class-name">skill</code>'.
** affiliations. optional. the class name <code class="class-name">affiliation</code> along with an [[hcard]] of the organization
** publications. optional. One or more citations. Use cite tag.

=== Field details ===
The fields of the hResume schema represent the following:

* '''<code class="class-name">hresume</code>''':: root class name
* '''<code class="class-name">summary</code>''':: The class name <code class="class-name">summary</code> is used to mark up an overview of qualifications and objectives.
* '''contact''':: Current contact info. The <code class="element"><address></code> with [[hCard]].
* '''<code class="class-name">education</code>''':: the class name '<code class="class-name">education</code>' is applied to an [[hcalendar]] event.
* '''<code class="class-name">experience</code>''':: the class name '<code class="class-name">experience</code>' is applied to an [[hcalendar]] event. Job titles/positions should use an [[hCard]].
* '''<code class="class-name">skill</code>''':: An hResume may be tagged using the [[rel-tag]] microformat and the '<code class="class-name">skill</code>' class name.
* '''<code class="class-name">affiliation</code>''':: The class name <code="class-name">affiliation</code> is used along with an [[hcard]] of the organization
* '''publications''':: just use <code class="element"><cite></code>. When there is a [[citation]] microformat, then that can be used in combination with the cite element to further markup the components of the citation.

=== Notes ===
This section is informative.

*...

== Examples ==
=== Summary ===
An example summary:

<pre><nowiki>
<p class="summary">
I have 10 years experience with all Web 2.0 technologies– I've been working with Ajax since 1996,
designing with pastels while others will still using tiled background images and frames...
</p>
</nowiki></pre>

=== Contact ===
<pre><nowiki>
<address class="vcard">
<span class="fn">Pedro Sanchez</span>
<span class="adr">
<span class="street-address">123 Fake St.</span>
<span class="locality">Preston</span>, <span class="region">Idaho</span> <span class="postal-code">83263</span>
</span>
<span>Email: <a class="email" href="mailto:joe@example.com">pedro@vote-for-pedro.com</a></span>
<span>Homepage: <a class="url" href="http://vote-for-pedro.com/">vote-for-pedro.com</a></span>
<span>Phone: <span class="tel">+01.208.555.4567</span></span>
</address>
</nowiki></pre>

=== Education ===
<pre><nowiki>
<ol class="vcalendar">
<li class="education vevent">
<a class="url summary" href="http://example.edu/">Preston High School</a>
(<abbr class="dtstart" title="2001-01-24">2001</abbr> - <abbr class="dtend" title="2005-05-25">2005</abbr>)
</li>
...
</nowiki></pre>

=== Experience ===
==== Basic ====
A basic experience event:

<pre><nowiki>
<ol class="vcalendar">
<li class="experience vevent">
<span class="summary">President</span>,
<span class="location">Preston High School</span>,
<abbr class="dtstart" title="2004-09-01">May 2004</abbr> - <abbr title="2005-05-25">present</abbr>
</li>
...
</nowiki></pre>

==== Job Titles ====
To express one or more job titles/positions in the same experience event you should use [[hCard]]s. [[hcard]] requires the <code class="class-name">fn</code> ("formatted name") field, but it isn't reasonable to repeat your name for every job title you mark up in [[hResume|hresume]]. So, you may use an <code class="element"><object></code> and the class name '<code class="class-name">include</code>' with a reference to the <code class="class-name">fn</code> somewhere else on the page.

For example, this [[hCard]] refers to another [[hCard]]

<pre>
<span class="vcard">
<object data="#j" class="include"></object>
<span class="org">Preston High School</span>
<span class="title">Class President</span>
</span>
</pre>

Where "<code class="attr-value">j</code>" is the id attribute value of the "<code class="mf-prop">fn n</code>" element of the contact [[hCard]] at the top of the page, e.g. (shown here as a verbose [[hCard]] for purposes of illustration that the reference may be to a subtree, not just a text node):

<pre><nowiki>
<address class="vcard">
<span class="fn n" id="j">
<span class="given-name">Pedro</span>
<span class="family-name">Sanchez</span>
</span>
</address>
</nowiki></pre>

This method of hCard property indirection via an object element [[include-pattern|has been generalized]] to apply to any/all string/text properties in hCard.
Note: the object data attribute MUST be a local ID reference. External references (which would require a consuming application to load an external resource) are currently not supported by this method.

=== Skills ===
Some sample skills tags:
<pre><nowiki>
I have skills in <a class="skill" rel="tag" href="http://en.wikipedia.org/wiki/Bow_%28weapon%29">bow hunting</a>
and <a class="skill" rel="tag" href="http://en.wikipedia.org/wiki/Nunchucks">nunchucks</a>.
</nowiki></pre>

=== Affiliations ===
<pre><nowiki>
<span class="affiliation vcard"><span class="fn org">National Honor Society</span></span>
</nowiki></pre>

=== Publications ===
<pre><nowiki>
<cite>Breeding Ligers for Fun and Magic</cite>, Idaho Press, 2004.
</nowiki></pre>

== Examples in the wild ==
This section is '''informative'''.

The following sites have published hResumes, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If you have an hResume on your own page, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

* [[User:Wim Le Page|Wim Le Page]] has also marked up [http://adrem.ua.ac.be/~wlepage/curriculum-vitae/ his curriculum vitae] as an hResume.
* [[user:Jonathan Arkell|Jonathan Arkell]] has posted an [http://portfolio.jonnay.net/cv/ hResume] on his portfolio website.
* [http://steve.ganz.name/hresume/ Steve Ganz - hResume 0.1]
* [[User:Dave Cardwell|Dave Cardwell]] has marked up [http://davecardwell.co.uk/cv/ his curriculum vitae] as an hResume. ''When this is downloaded outside of a browser, WTF it doesn't appear to be HTML? The root element is "htmllang"? -- [[DavidJanes]]''
* [[user:Izo|Mathieu Drouet]] has posted an [http://izo.aucuneid.com/hresume.html hResume]. ''Incorrect root class name hResume? -- [[DavidJanes]]''

== Profile ==
@TODO

== Implementations ==
@TODO

== References ==
=== Normative References ===
* [http://www.w3.org/TR/REC-html40/ HTML 4]
* [http://www.w3.org/TR/xhtml1/ XHTML]
* [http://gmpg.org/xmdp/ XMDP]
* [[rel-tag| Rel-Tag]]
* @TODO

=== Informative References ===
@TODO

== Copyright ==
{{MicroFormatCopyrightStatement2006}}

== Patents ==
{{MicroFormatPatentStatement}}

== Acknowledgements ==

=== Concept ===
* [http://theryanking.com/ Ryan King], [http://technorati.com Technorati]
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati]
* James Levine [http://simplyhired.com Simply Hired]
* [http://epeus.blogspot.com/ Kevin Marks], [http://technorati.com Technorati]

== See also ==
* [[resume-examples]]
* [[resume-formats]]
* [[resume-brainstorming]]

== Discussions ==

* Feedback is encouraged on the [[hresume-feedback]] page.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

=== Q&A ===
* If you have any questions about hResume, check the [[hresume-faq|hResume FAQ]], and if you don't find answers, add your questions to the end!

=== Issues ===
* Please add any issues with the specification to the separate [[hresume-issues|hResume issues]] document.

Main Page

2006-03-28T21:25:41Z

Jonathan Arkell: Removed Spam.

__NOTOC__
__NOTOC__
= Microformats Wiki =

'''Please read [[how-to-play]] before making any edits.'''

'''Please read [[process]] before proposing any new microformats.'''

== Introduction ==

What are microformats? See the [http://microformats.org/about/ about page] for an overview, and the [[introduction]] page for more info. Recent [[press]] and [[presentations]] are also a good place for some background reading as well. Frequently asked questions are answered in the [[faq]]. Want something or want to contribute? Help with things [[to-do]].

One popular definition from our [http://microformats.org/discuss/ mailing list] is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:
:simple conventions
:for embedding semantic markup
::for a specific problem domain
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML
::that normalize existing content usage patterns
::using brief, descriptive class names
::often based on existing interoperable standards
:to enable decentralized development
::of resources, tools, and services

"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]

== Specifications ==
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])
* [[hcalendar|hCalendar]]
* [[hcard|hCard]]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo|XOXO]]

== Drafts ==
* [[adr|adr]]
* [[geo|geo]]
* [[hatom|hAtom]] {{NewMarker}}
* [[hresume|hResume]] {{NewMarker}}
* [[hreview|hReview]]
* [[rel-directory]]
* [[rel-enclosure]]
* [[relpayment-research | rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]
* [[rel-home]] {{NewMarker}}

== Design Patterns ==

Design patterns give microformat authors a vocabulary for expressing their ideas consistently with what has already been done. ''If you're tempted to try your hand at writing a microformat '''[[process|read this first]]'''!''

* [[abbr-design-pattern]]
* [[class-design-pattern]]
* [[datetime-design-pattern]]
* [[existing-classes|class names defined across all microformats]]
* [[include-pattern]] {{NewMarker}}
* [[rel-design-pattern]]

== Exploratory discussions ==
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat.
*[[attention]]
*[[blog-description-examples]]
*[[blog-info-examples]]
*[[blog-post-examples]], [[blog-post-formats]], [[blog-post-brainstorming]] (yields [[hatom|hAtom]])
*[[book-examples]], [[book-formats]], [[book-brainstorming]]
*[[chat-examples]], [[chat-formats]]
*[[citation|citation microformat overview]], [[citation-examples]], [[citation-formats]], [[citation-brainstorming]]
*[[comment-problem]], [[comment-examples]], (need to extract from [[comments-formats]])
*[[directory-inclusion-examples]], [[directory-inclusion-formats]]. (see also [[rel-directory]])
*[[distributed-conversation]], [[distributed-conversation-brainstorming]], [[distributed-conversation-examples]], [[distributed-conversation-formats]]
*[[forms-examples]]
*[[genealogy-formats]]
*[[hash-examples]]
*[[last-modified-examples]], [[last-modified-formats]], [[last-modified-brainstorming]]
*[[hlisting-proposal]], [[hlisting-feedback]] {{NewMarker}}
**[[listing-examples]], [[listing-formats]], [[listing-brainstorming]]
*[[location-formats]]. (see also [[adr]] and [[geo]])
*[[media-info-examples]]
*[[mfo-examples]]
*[[music-examples]]
*[[other-formats]]
*[[photo-note-examples]]
*[[recipe-examples]]
*[[requirements-testing]], [[requirements-testing-examples]]
*[[rest-examples]]
*[[resume-brainstorming]], [[resume-formats]]
*[[review-examples]], [[review-formats]] (yielded the [[hreview|hReview]] draft)
*[[search-results-example]]
*[[show-brainstorming]]
*[[showroll-brainstorming]]
*[[table-examples]]
*[[tagspeak-examples]]
*[[transit-table-examples]]
*[[widget-examples]], [[widget-brainstorming]]
*[[wiki-formats]]
*[[work-of-art]] {{NewMarker}}
*[[xmdp-brainstorming]] (see also [[xmdp-faq]])

== Examples ==
* [[examples]]
* [[zen-garden]] {{NewMarker}}

== 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 and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.

*[[parsing-microformats]]
*[[selected-test-cases-from-the-web]]
*[[vcard-implementations]], [[vcard-errata]]
*[[icalendar-implementations]]
*[[faqs-for-rdf]]
*[[why-are-content-standards-hard]]

== shared work areas ==
* [[buttons]] {{NewMarker}}
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.
* [[events]] {{NewMarker}}
* [[to-do]]
* [[marked-for-deletion]]

== microformats wiki in other languages ==

You may read and edit microformats articles in <del>many different</del> other languages

=== microformats wiki languages with over 2 articles ===

* [[Main_Page-fr|Français (French)]]
* [[Main_Page-jp|日本語 (Japanese)]] {{NewMarker}}

=== Start a microformats wiki in another language ===

Don't see the language you want? Help translate the microformats wiki into another language!

We're still figuring this out.

For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.

You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).

Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].

==== more languages folks want to see ====

* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])

rest

2006-03-23T20:44:08Z

Jonathan Arkell: Added Meditation to list of tools

= Microformats in REST Web Services =
This the home page for discussion, research, and standards regarding how to optimally use Microformats as the encoding for [http://en.wikipedia.org/wiki/Representational_State_Transfer REST] web services. The goal is for all REST-related information in the microformats world to live under this URL.

== Discussion Forums ==
* [http://microformats.org/discuss/mail/microformats-rest/ uf-rest] discussion list on microformats.org
* [http://groups.yahoo.com/group/rest-discuss/ rest-discuss] @ Yahoo Groups

== Topics ==
=== URLs ===
;[[rest/opacity]]
:Properly Interpreting the "Axiom of URI Opacity"
;[[rest/urls]]
:How should URLs be structured for maximum clarity & discoverability?
=== HTML ===
;[[rest/ahah]]
:Asychronous HTML vs. AJAX
;[[rest/datatypes]]
:How to encode type information in HTML
;[[rest/description]]
:What, if anything, is the analogue of WSDL for REST services?
;[[rest/webforms]]
:Upgrading browsers to support PUT and DELETE properly

=== Implementations ===
;[[rest/cgi]]
:CGI is slow, and FastCGI is designed for C parsers. Is there a third option?
;[[rest/rails]]
:Ways to make Ruby on Rails more REST-friendly out of the box.
=== Standards ===
* [http://www.ietf.org/rfc/rfc3205.txt HTTP as a Substrate] - Best Current Practice
* [http://www.faqs.org/rfcs/rfc2483.html text/uri-list] (Section 5, URI Resolution Services)

== Background Research ==
=== Examples ===
* [[rest/examples]]
* [[rest/forms-examples]]

=== Brainstorming ===

* [[rest/brainstorming]]
* [[rest/forms-brainstorming]]

== Proposals ==
Note that these are all preliminary.

* [http://www.opendarwin.org/~drernie/talk/rest-enabled-xhtml-20051019.html REST-Enabled XHTML]] by Dr. Ernie
** original at [[rest/rex-proposal]]
* [http://restylab.php5.cz/dreams/webutopia.html WebUtopia] by Toydi
** more details in rest-discuss thread: [http://groups.yahoo.com/group/rest-discuss/message/5290 "Dreams about ReSTifying web apps"]

== Implementations ==

=== Tools ===
* [[xoxo-sample-code| XOXO parser (python)]]
** also [http://www.opendarwin.org/~drernie/xoxo-plist.py xoxo-plist.py], a pyobjc variant support Mac OS X plists]
* [http://www.opendarwin.org/~drernie/src/ahah.js ahah.js] Asynchronous HTML over HTTP
** was [http://epeus.blogspot.com/2005_05_01_epeus_archive.html#111588374981985824 JAH], an [http://technorati.com/tag/AJAX AJAX] alternative)
* Ruby RESTifarian plugin
$ script/plugin install restifarian # need beta gems/edge rails for this to work
** See also prototype [http://www.onautopilot.com/oss/rails/rest_controller.rb controller]
* [http://wiki.jonnay.net/bunny/meditation/meditation Meditation] a PHP REST API Framework.

=== Examples ===
* [http://www.opendarwin.org/~drernie/C499496031/E20051019100520/index.html DARC]: Darwin-Apache-Rails-CoreData
* [http://www.opendarwin.org/~drernie/C499496031/E20051026153908/index.html TurboGear] AddressBook (Mac OS X-only)
=== Sites ===
* [http://www.larrystaton.com Larry Staton Jr.] AHAH-enabled homepage (a first!)

== Participants ==
* [http://www.opendarwin.org/~drernie/C395201355/index.html Dr. Ernie Prabhakar]
* [http://restylab.php5.cz/ Teo HuiMing (toydi)]
* [mailto:dimitri.glazkov@gmail.com Dimitri Glazkov]
* [http://www.xrest.org Max Voelkel (xamde)]
* [http://www.loudthinking.com/ David Heinemeier Hansson]

rel-tag

2006-03-15T23:10:40Z

Jonathan Arkell: Added s9y

<h1> rel-tag </h1>

__TOC__

== Draft Specification 2005-01-10 ==
=== Editor/Author ===
[http://tantek.com/ Tantek Çelik]

=== Concept ===
[http://powazek.com/ Derek Powazek]
[http://epeus.blogspot.com/ Kevin Marks]

=== Copyright ===
{{MicroFormatCopyrightStatement2004}}

=== Patents ===
{{MicroFormatPatentStatement}}

== Abstract ==
[[Rel-Tag]] is one of several [[MicroFormats]]. By adding <code>rel="tag"</code> to a hyperlink, a page indicates that the destination of that hyperlink is an author-designated "tag" (or keyword/subject) of 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,

<pre><nowiki><a href="http://technorati.com/tag/tech" rel="tag">tech</a></nowiki></pre>

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

<pre><nowiki><a href="http://technorati.com/tag/tech" rel="tag">fish</a></nowiki></pre>

would indicate the tag "tech" rather than "fish".

== Scope ==
rel="tag" is specifically designed for "tagging" content, typically web pages (or portions thereof, like blog posts).

rel="tag" is NOT designed for "tagging" arbitrary URLs or external content. There is demand for a general decentralized syntax for tagging URLs, and that is certainly something to think about, but this is not meant for that. See [[xfolk|xFolk]] and [[hreview|hReview]] for ways to tag arbitrary URLs.

== XMDP profile ==
<pre><nowiki>
<dl class="profile">
<dt id="rel">rel</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel">
HTML4 definition of the 'rel' attribute.</a>
Here is an additional value.</p>
<dl>
<dt id="tag">tag</dt>
<dd>Indicates that the referred resource serves as a "tag",
or keyword/subject, for the referring page.</dd>
</dl>
</dd>
</dl>
</nowiki></pre>

== Tag Spaces ==

Tags are embedded in HTTP URIs in a well-defined manner so that the tag embedded in an HTTP URI can be mechanically extracted from that URI. Specifically, the last segment of the path portion of the URI (after the final "/" character) contains the tag value. For example, the URI <pre><nowiki>http://www.example.com/tags/foo</nowiki></pre> contains the tag "foo".

Thus, for the purposes of comparing two HTTP URIs as tags, the last segment of the path portion should be extracted and only that value (that value of the tag) should be compared.

''Need more formal language about comparison and extraction process.''

The destination of a rel="tag" hyperlink is required to be a tag space (a place that collates or defines tags), where the last segment of the path of the URL is the tag, e.g.

<pre><nowiki>http://technorati.com/tag/tech </nowiki></pre>

is a URL for the tag "tech".

Tags may only be placed in the URL path, and only in the last segment of the path. Tags may not be placed in query parameters or fragment identifiers. e.g.

<pre><nowiki>http://technorati.com/tag/tech?tag=fish#emu </nowiki></pre>

is still a URL for the tag "tech", not "fish" or "emu".

Since the only part of a tag space URL of which any structure is required is the last path segment, a tag space URL can be hosted at any domain. Authors may choose to link to a tag at a particular tag space in order to provide a specific meaning. E.g. a tag for technology could link to:

<pre><nowiki> http://en.wikipedia.org/wiki/Technology </nowiki></pre>

Trailing slashes in tag URLs are ignored, that is:

<pre><nowiki> http://technorati.com/tag/Technology/ </nowiki></pre>
as a rel-tag URL is treated as:
<pre><nowiki> http://technorati.com/tag/Technology </nowiki></pre>

== Encoding issues ==
Spaces can be encoded either as <code>+</code> or <code>%20</code>. Unicode characters are encoded as specified in [http://www.ietf.org/rfc/rfc3986.txt RFC 3986]. For example:

<pre><nowiki><a href="http://technorati.com/tag/Sant%C3%A9+et+bien-%C3%AAtre" rel="tag">Santé et bien-être</a> </nowiki></pre>

== Tags Are Visible Metadata ==
<code>rel="tag"</code> hyperlinks are intended to be visible links on pages and posts. This is in stark contrast to meta keywords (which were invisible and typically never revealed to readers), and thus is at least somewhat more resilient to the problems which plagued meta keywords.

Making tag hyperlinks visible has the additional benefit of making it more obvious to readers if a page is abusing tag links, and thus providing more peer pressure for better behavior. It also makes it more obvious to authors, who may not always be aware what invisible metadata is being generated on their behalf.

As a result the invisible tag link syntax variant: <code><link rel="tag" href="..." /></code> SHOULD NOT be supported by implementations.

== Implementations ==
This section is '''informative'''.

The following implementations have been developed which either generate or parse rel-tag links. If you have a rel-tag implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

* The Freetag plugin for the [http://www.s9y.org Serendipity] blog software supports rel-tags on a per-entry basis, as well as inside of its tag clouds. (The Freetag plugin is available inside of SPARTACUS)
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding rel-tags and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* [http://news.livejournal.com/86492.html?thread=24881884 LiveJournal] - see also [http://www.livejournal.com/support/faq.bml?cat=tags their FAQ regarding their tags support]
* [http://trac.labnotes.org/cgi-bin/trac.cgi/wiki/TagsLinks TagsLinks] Turn each tag into links that let you find related content on tagging services.
* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] rel-tags for user entered tags.
* [http://evdb.com EVDB] publishes rel-tags for user entered tags.
* [http://dev.wp-plugins.org/wiki/BunnysTechnoratiTags "Tag plugin for wordpress"]
* Technorati first implemented rel-tag in its [http://technorati.com/tag/ Technorati Tags] service. Technorati indexes rel-tag tags.
* [http://consumingexperience.blogspot.com/2005/12/updated-multiple-word-technorati-tag.html Greasemonkey script for Firefox that generates tags for Blogger]

== References ==
=== Normative References ===
* [http://www.w3.org/TR/REC-html40/ HTML 4]
* [http://www.w3.org/TR/xhtml1/ XHTML 1]
* [http://gmpg.org/xmdp/ XMDP]
* RFC 3986 specifies URL syntax. Section 3.3 specifies URL paths and path segments.

=== Informative References ===
* [[hreview|hReview]] uses rel-tag for tags and scalar tags
* [[xfolk|xFolk]] uses rel-tag to build a distributed remote resource tagging construct
* [http://developers.technorati.com/wiki/attentionxml Attention.XML] uses rel-tag for reader tagging of pages, posts, feeds
* [[hcard|hCard]] can use rel-tag for categories
* [[hcalendar|hCalendar]] can use rel-tag for categories
* [http://technorati.com/help/tags.html Using Technorati Tags]

== Discussions ==
* Feedback is encouraged on the [[rel-tag-feedback]] page.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].
* History: [http://www.powazek.com/2005/07/000532.html How Tags Happened at Technorati] by [http://www.powazek.com/ Derek Powazek]

=== Q&A ===
* If you have any questions about rel-tag, check the [[rel-faq|rel FAQ]] first for general rel attribute questions, then check the [[rel-tag-faq|rel-tag FAQ]], and then if you don't find answers, ask your question on the [http://microformats.org/discuss microformats-discuss] mailing list.

=== Issues ===
* Please add any issues with the specification to the separate [[rel-tag-issues|rel-tag issues]] document.

User:Jonathan Arkell

2006-03-12T22:14:03Z

Jonathan Arkell: /* Jonathan Arkell */

irc

2006-03-12T22:09:11Z

Jonathan Arkell: Added myself to the list

__NOTOC__
= Microformats IRC =

We have an IRC channel, [irc://irc.freenode.net#microformats #microformats on the freenode network].

There's typically someone there at any point during the day, though there isn't always active discussion. Sometimes, though this is the best place to discuss issues that need lots of back and forth discussion.

== People on irc ==
A list of IRC regulars and their normal timezones.

* [[User:Amette|amette]] (+1000)
* [[User:BenjaminCarlyle|BenjaminCarlyle]] (+1000)
* [[User:B.K._DeLong|bkdelong]] (-0500)
* [[User:Cgriego|cgriego]] (-0600)
* [[User:ChrisCasciano|pnhChris]] (-0500)
* [[User:DimitriGlazkov|dglazkov]] (-0600)
* [[User:ChrisMessina|factoryjoe]] (-0800)
* [[User:EdwardOConnor|hober]] (-0800)
* [[User:Enric|enric]] (-0800)
* [[User:Fil|Fil]] (+0200)
* [[User:IanHickson|Hixie]] (-0800)
* [[User:Izo|IZO]]
* [[User:JoeGregorio|jcgregorio]]
* [[User:Jonathan_Arkell|jonnay]] (-0700/0600)
* [http://epeus.blogspot.com/ KevinMarks] (-0800)
* [[User:neuro|neuro`]]
* [[User:RyanKing|kingryan]] (-0800)
* [[User:RobertBachmann|RobertBachmann]] (+0100)
* [[User:Tantek|Tantek]] (-0800)
* [[User:ChristopherStJohn|cks]] (-0600)
* [[User:Mark Mansour|Mark Mansour]] (+1100)
* [[User:Dave Cardwell|davecardwell]] (+0000)
* [[User:Boneill|boneill]] (+0000)
* [[User:Steve Ganz|SteveGanz]] (-0800)
* [[User:Hlb|hlb]] (+0800)
* [[User:Ben Ward|BenWard]] (+0000)

=== bots ===

* [[mfbot]]
* [[mflogbot]]
* [http://joi.ito.com/joiwiki/JiBot jibot]

== Logs ==

Available here: http://rbach.priv.at/Microformats-IRC/

== IRC meetups ==

The idea of having IRC meetups (that is, a set time for meeting on IRC) has been suggested by [[User:RyanKing|Ryan King]], as it appears to work well for the WordPress community and may help us from time-to-time. As of yet, there are no plans to have meetups, though.

qa-examples

2006-03-09T02:29:57Z

Jonathan Arkell: Added another example

This page is a place holder for examples of how people currently collect questions and answers

== Examples ==

DocBook has a <qandaset> element http://www.docbook.org/tdg/en/html/qandaset.html
which is used with <question> and <answer> elements, and optionally
<qandadiv> elements.

The Firefox faq is marked up with <dl> http://www.mozilla.org/support/firefox/faq
as is the old Mozilla 1.5 FAQ: http://www.mozilla.org/start/1.5/faq/profile.html#newprofile
Both of them are separated into sections and have tables of contents.

For the [http://www.w3.org/MarkUp/2004/xhtml-faq W3C XHTML faq], the table of contents is in an ordered list, and contains urls that point to the question/answer fragments below. The question answer fragments are an h3 element paired with one or more p elements.

For the Brainstorms and Raves article on [http://brainstormsandraves.com/articles/semantics/structure/#faqSemantics, HTML, XHTML, and Structure], the faq is definition list enclosed in a div element of the class faq. Questions are inside of dt elements, and answers inside of dd elements. If a question has multiple answers, there would be a seperate dd element for each answer.

Main Page

2006-03-09T01:59:08Z

Jonathan Arkell: Removed (automated?) spam

__NOTOC__
__NOTOC__
= Microformats Wiki =

'''Please read [[how-to-play]] before making any edits.'''

'''Please read [[process]] before proposing any new microformats.'''

== Introduction ==

What are microformats? See the [http://microformats.org/about/ about page] for an overview, and the [[introduction]] page for more info. Recent [[press]] and [[presentations]] are also a good place for some background reading as well. Frequently asked questions are answered in the [[faq]].

One popular definition from our [http://microformats.org/discuss/ mailing list] is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:
:simple conventions
:for embedding semantic markup
::for a specific problem domain
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML
::that normalize existing content usage patterns
::using brief, descriptive class names
::often based on existing interoperable standards
:to enable decentralized development
::of resources, tools, and services

"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]

== Specifications ==
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])
* [[hcalendar|hCalendar]]
* [[hcard|hCard]]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo|XOXO]]

== Drafts ==
* [[adr|adr]]
* [[geo|geo]]
* [[hatom|hAtom]] {{NewMarker}}
* [[hresume|hResume]] {{NewMarker}}
* [[hreview|hReview]]
* [[rel-directory]]
* [[rel-enclosure]]
* [[relpayment-research | rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]
* [[rel-home]] {{NewMarker}}

== Design Patterns ==

Design patterns give microformat authors a vocabulary for expressing their ideas consistently with what has already been done. ''If you're tempted to try your hand at writing a microformat '''[[process|read this first]]'''!''

* [[abbr-design-pattern]]
* [[class-design-pattern]]
* [[datetime-design-pattern]]
* [[existing-classes|class names defined across all microformats]]
* [[include-pattern]] {{NewMarker}}
* [[rel-design-pattern]]

== Exploratory discussions ==
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat.
*[[attention]]
*[[blog-description-examples]]
*[[blog-info-examples]]
*[[blog-post-examples]], [[blog-post-formats]], [[blog-post-brainstorming]] (yields [[hatom|hAtom]])
*[[book-examples]], [[book-formats]], [[book-brainstorming]]
*[[chat-examples]], [[chat-formats]]
*[[citation|citation microformat overview]], [[citation-examples]], [[citation-formats]], [[citation-brainstorming]]
*[[comment-problem]], [[comment-examples]], (need to extract from [[comments-formats]])
*[[directory-inclusion-examples]], [[directory-inclusion-formats]]. (see also [[rel-directory]])
*[[distributed-conversation]], [[distributed-conversation-brainstorming]], [[distributed-conversation-examples]], [[distributed-conversation-formats]]
*[[forms-examples]]
*[[genealogy-formats]]
*[[hash-examples]]
*[[last-modified-examples]], [[last-modified-formats]], [[last-modified-brainstorming]]
*[[hlisting-proposal]], [[hlisting-feedback]] {{NewMarker}}
**[[listing-examples]], [[listing-formats]], [[listing-brainstorming]]
*[[location-formats]]. (see also [[adr]] and [[geo]])
*[[media-info-examples]]
*[[mfo-examples]]
*[[other-formats]]
*[[photo-note-examples]]
*[[recipe-examples]]
*[[requirements-testing]], [[requirements-testing-examples]]
*[[rest-examples]]
*[[resume-brainstorming]], [[resume-formats]]
*[[review-examples]], [[review-formats]] (yielded the [[hreview|hReview]] draft)
*[[search-results-example]]
*[[show-brainstorming]]
*[[showroll-brainstorming]]
*[[table-examples]]
*[[tagspeak-examples]]
*[[transit-table-examples]]
*[[widget-examples]], [[widget-brainstorming]]
*[[wiki-formats]]
*[[xmdp-brainstorming]] (see also [[xmdp-faq]])

== Examples ==
* [[examples]]
* [[zen-garden]] {{NewMarker}}

== 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 and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.

*[[parsing-microformats]]
*[[selected-test-cases-from-the-web]]
*[[vcard-implementations]], [[vcard-errata]]
*[[icalendar-implementations]]
*[[faqs-for-rdf]]
*[[why-are-content-standards-hard]]

== shared work areas ==
* [[buttons]] {{NewMarker}}
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.
* [[events]] {{NewMarker}}
* [[to-do]]
* [[marked-for-deletion]]

== microformats wiki in other languages ==

You may read and edit microformats articles in <del>many different</del> other languages

=== microformats wiki languages with over 2 articles ===

* [[Main_Page-fr|Français (French)]]
* [[Main_Page-jp|日本語 (Japanese)]] {{NewMarker}}

=== Start a microformats wiki in another language ===

Don't see the language you want? Help translate the microformats wiki into another language!

We're still figuring this out.

For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.

You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).

Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].

==== more languages folks want to see ====

* Chinese: 微支付 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])

qa-examples

2006-03-09T01:52:09Z

Jonathan Arkell:

User:Jonathan Arkell

2006-03-08T21:06:43Z

Jonathan Arkell:

hresume

2006-03-08T21:03:31Z

Jonathan Arkell: Fixed link to my user page

<h1> hResume </h1>

hResume is a microformat for publishing resumes and CVs.

This paragraph is where we write some thing that makes everyone in the world want to use hResume. Because, you know, hResume's the future and people like the future. And so on... [[hresume-use|Wanna get started on hResume right now?]]

<h2> Microformats Draft Specification </h2>

; Editor/Author: [http://theryanking.com Ryan King]
; Acknowledgments: See [http://microformats.org/wiki/hresume#Acknowledgements acknowledgments].

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

__TOC__

== Status ==
Draft, version 0.1.

== Introduction ==
=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

== Format ==
=== In General ===
The hResume format is based on a set of fields common to numerous resumes published today on the web. Where possible field names have been chosen and reused from preexisting microformats.

=== Schema ===
The hResume schema consists of the following:

* hResume
** summary. optional. text.
** contact info. required. <code class="element"><address></code> + [[hcard|hCard]].
** experience. optional. One or more [[hcalendar]] events with the class name '<code class="class-name">experience</code>', with an embedded [[hcard|hCard]] indicating the job title, name of company, address of company etc.
** education. optional One or more [[hcalendar]] events with the class name '<code class="class-name">education</code>', with an embedded [[hcard|hCard]] indicating the name of school, address of school etc.
** skills. optional. phrases or keywords using the [[rel-tag]] microformat with the class name '<code class="class-name">skill</code>'.
** affiliations. optional. the class name <code class="class-name">affiliation</code> along with an [[hcard]] of the organization
** publications. optional. One or more citations. Use cite tag.

=== Field details ===
The fields of the hReview schema represent the following:

* '''<code class="class-name">hresume</code>''':: root class name
* '''<code class="class-name">summary</code>''':: The class name <code class="class-name">summary</code> is used to mark up an overview of qualifications and objectives.
* '''contact''':: Current contact info. The <code class="element"><address></code> with [[hCard]].
* '''<code class="class-name">education</code>''':: the class name '<code class="class-name">education</code>' is applied to an [[hcalendar]] event.
* '''<code class="class-name">experience</code>''':: the class name '<code class="class-name">experience</code>' is applied to an [[hcalendar]] event. Job titles/positions should use an [[hCard]].
* '''<code class="class-name">skill</code>''':: An hResume may be tagged using the [[rel-tag]] microformat and the '<code class="class-name">skill</code>' class name.
* '''<code class="class-name">affiliation</code>''':: The class name <code="class-name">affiliation</code> is used along with an [[hcard]] of the organization
* '''publications''':: just use <code class="element"><cite></code>. When there is a [[citation]] microformat, then that can be used in combination with the cite element to further markup the components of the citation.

=== Notes ===
This section is informative.

*...

== Examples ==
=== Summary ===
An example summary:

<pre><nowiki>
<p class="summary">
I have 10 years experience with all Web 2.0 technologies– I've been working with Ajax since 1996,
designing with pastels while others will still using tiled background images and frames...
</p>
</nowiki></pre>

=== Contact ===
<pre><nowiki>
<address class="vcard">
<span class="fn">Pedro Sanchez</span>
<span class="adr">
<span class="street-address">123 Fake St.</span>
<span class="locality">Preston</span>, <span class="region">Idaho</span> <span class="postal-code">83263</span>
</span>
<span>Email: <a class="email" href="mailto:joe@example.com">pedro@vote-for-pedro.com</a></span>
<span>Homepage: <a class="url" href="http://vote-for-pedro.com/">vote-for-pedro.com</a></span>
<span>Phone: <span class="tel">+01.208.555.4567</span></span>
</address>
</nowiki></pre>

=== Education ===
<pre><nowiki>
<ol class="vcalendar">
<li class="education vevent">
<a class="url summary" href="http://example.edu/">Preston High School</a>
(<abbr class="dtstart" title="2001-01-24">2001</abbr> - <abbr class="dtend" title="2005-05-25">2005</abbr>)
</li>
...
</nowiki></pre>

=== Experience ===
==== Basic ====
A basic experience event:

<pre><nowiki>
<ol class="vcalendar">
<li class="experience vevent">
<span class="summary">President</span>,
<span class="location">Preston High School</span>,
<abbr class="dtstart" title="2004-09-01">May 2004</abbr> - <abbr title="2005-05-25">present</abbr>
</li>
...
</nowiki></pre>

==== Job Titles ====
To express one or more job titles/positions in the same experience event you should use [[hCard]]s. [[hcard]] requires the <code class="class-name">fn</code> ("formatted name") field, but it isn't reasonable to repeat your name for every job title you mark up in [[hResume|hresume]]. So, you may use an <code class="element"><object></code> and the class name '<code class="class-name">include</code>' with a reference to the <code class="class-name">fn</code> somewhere else on the page.

For example, this [[hCard]] refers to another [[hCard]]

<pre>
<span class="vcard">
<object data="#j" class="include"></object>
<span class="org">Preston High School</span>
<span class="title">Class President</span>
</span>
</pre>

Where "<code class="attr-value">j</code>" is the id attribute value of the "<code class="mf-prop">fn n</code>" element of the contact [[hCard]] at the top of the page, e.g. (shown here as a verbose [[hCard]] for purposes of illustration that the reference may be to a subtree, not just a text node):

<pre><nowiki>
<address class="vcard">
<span class="fn n" id="j">
<span class="given-name">Pedro</span>
<span class="family-name">Sanchez</span>
</span>
</address>
</nowiki></pre>

This method of hCard property indirection via an object element [[include-pattern|has been generalized]] to apply to any/all string/text properties in hCard.
Note: the object data attribute MUST be a local ID reference. External references (which would require a consuming application to load an external resource) are currently not supported by this method.

=== Skills ===
Some sample skills tags:
<pre><nowiki>
I have skills in <a class="skill" rel="tag" href="http://en.wikipedia.org/wiki/Bow_%28weapon%29">bow hunting</a>
and <a class="skill" rel="tag" href="http://en.wikipedia.org/wiki/Nunchucks">nunchucks</a>.
</nowiki></pre>

=== Affiliations ===
<pre><nowiki>
<span class="affiliation vcard"><span class="fn org">National Honor Society</span></span>
</nowiki></pre>

=== Publications ===
<pre><nowiki>
<cite>Breeding Ligers for Fun and Magic</cite>, Idaho Press, 2004.
</nowiki></pre>

== Examples in the wild ==
This section is '''informative'''.

The following sites have published hResumes, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If you have an hResume on your own page, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

* [[user:Jonathan Arkell|Jonathan Arkell]] has posted an [http://portfolio.jonnay.net/cv/ hResume] on his (work in progress) portfolio website.
* [http://steve.ganz.name/hresume/ Steve Ganz - hResume 0.1]
* [[User:Dave Cardwell|Dave Cardwell]] has marked up [http://davecardwell.co.uk/cv/ his curriculum vitae] as an hResume.
** If you are working on hResume, please take a look and point out any glaring problems to davecardwell on #microformats on irc.

== Profile ==
@TODO

== Implementations ==
@TODO

== References ==
=== Normative References ===
* [http://www.w3.org/TR/REC-html40/ HTML 4]
* [http://www.w3.org/TR/xhtml1/ XHTML]
* [http://gmpg.org/xmdp/ XMDP]
* [[rel-tag| Rel-Tag]]
* @TODO

=== Informative References ===
@TODO

== Copyright ==
{{MicroFormatCopyrightStatement2006}}

== Patents ==
{{MicroFormatPatentStatement}}

== Acknowledgements ==

=== Concept ===
* [http://theryanking.com/ Ryan King], [http://technorati.com Technorati]
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati]
* SimplyHired guys... @TODO
* [http://epeus.blogspot.com/ Kevin Marks], [http://technorati.com Technorati]

== See also ==
* [[resume-examples]]
* [[resume-formats]]
* [[resume-brainstorming]]

== Discussions ==

* Feedback is encouraged on the [[hresume-feedback]] page.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

=== Q&A ===
* If you have any questions about hResume, check the [[hresume-faq|hResume FAQ]], and if you don't find answers, add your questions to the end!

=== Issues ===
* Please add any issues with the specification to the separate [[hresume-issues|hResume issues]] document.

hresume

2006-03-08T21:01:32Z

Jonathan Arkell: /* Examples in the wild */

<h1> hResume </h1>

hResume is a microformat for publishing resumes and CVs.

This paragraph is where we write some thing that makes everyone in the world want to use hResume. Because, you know, hResume's the future and people like the future. And so on... [[hresume-use|Wanna get started on hResume right now?]]

<h2> Microformats Draft Specification </h2>

; Editor/Author: [http://theryanking.com Ryan King]
; Acknowledgments: See [http://microformats.org/wiki/hresume#Acknowledgements acknowledgments].

Microformats [http://microformats.org/wiki/hresume#Copyright copyright] and [http://microformats.org/wiki/hresume#Patents patents] statements apply.

__TOC__

== Status ==
Draft, version 0.1.

== Introduction ==
=== Semantic XHTML Design Principles ===
{{SemanticXHTMLDesignPrinciples}}

== Format ==
=== In General ===
The hResume format is based on a set of fields common to numerous resumes published today on the web. Where possible field names have been chosen and reused from preexisting microformats.

=== Schema ===
The hResume schema consists of the following:

* hResume
** summary. optional. text.
** contact info. required. <code class="element"><address></code> + [[hcard|hCard]].
** experience. optional. One or more [[hcalendar]] events with the class name '<code class="class-name">experience</code>', with an embedded [[hcard|hCard]] indicating the job title, name of company, address of company etc.
** education. optional One or more [[hcalendar]] events with the class name '<code class="class-name">education</code>', with an embedded [[hcard|hCard]] indicating the name of school, address of school etc.
** skills. optional. phrases or keywords using the [[rel-tag]] microformat with the class name '<code class="class-name">skill</code>'.
** affiliations. optional. the class name <code class="class-name">affiliation</code> along with an [[hcard]] of the organization
** publications. optional. One or more citations. Use cite tag.

=== Field details ===
The fields of the hReview schema represent the following:

* '''<code class="class-name">hresume</code>''':: root class name
* '''<code class="class-name">summary</code>''':: The class name <code class="class-name">summary</code> is used to mark up an overview of qualifications and objectives.
* '''contact''':: Current contact info. The <code class="element"><address></code> with [[hCard]].
* '''<code class="class-name">education</code>''':: the class name '<code class="class-name">education</code>' is applied to an [[hcalendar]] event.
* '''<code class="class-name">experience</code>''':: the class name '<code class="class-name">experience</code>' is applied to an [[hcalendar]] event. Job titles/positions should use an [[hCard]].
* '''<code class="class-name">skill</code>''':: An hResume may be tagged using the [[rel-tag]] microformat and the '<code class="class-name">skill</code>' class name.
* '''<code class="class-name">affiliation</code>''':: The class name <code="class-name">affiliation</code> is used along with an [[hcard]] of the organization
* '''publications''':: just use <code class="element"><cite></code>. When there is a [[citation]] microformat, then that can be used in combination with the cite element to further markup the components of the citation.

=== Notes ===
This section is informative.

*...

== Examples ==
=== Summary ===
An example summary:

<pre><nowiki>
<p class="summary">
I have 10 years experience with all Web 2.0 technologies– I've been working with Ajax since 1996,
designing with pastels while others will still using tiled background images and frames...
</p>
</nowiki></pre>

=== Contact ===
<pre><nowiki>
<address class="vcard">
<span class="fn">Pedro Sanchez</span>
<span class="adr">
<span class="street-address">123 Fake St.</span>
<span class="locality">Preston</span>, <span class="region">Idaho</span> <span class="postal-code">83263</span>
</span>
<span>Email: <a class="email" href="mailto:joe@example.com">pedro@vote-for-pedro.com</a></span>
<span>Homepage: <a class="url" href="http://vote-for-pedro.com/">vote-for-pedro.com</a></span>
<span>Phone: <span class="tel">+01.208.555.4567</span></span>
</address>
</nowiki></pre>

=== Education ===
<pre><nowiki>
<ol class="vcalendar">
<li class="education vevent">
<a class="url summary" href="http://example.edu/">Preston High School</a>
(<abbr class="dtstart" title="2001-01-24">2001</abbr> - <abbr class="dtend" title="2005-05-25">2005</abbr>)
</li>
...
</nowiki></pre>

=== Experience ===
==== Basic ====
A basic experience event:

<pre><nowiki>
<ol class="vcalendar">
<li class="experience vevent">
<span class="summary">President</span>,
<span class="location">Preston High School</span>,
<abbr class="dtstart" title="2004-09-01">May 2004</abbr> - <abbr title="2005-05-25">present</abbr>
</li>
...
</nowiki></pre>

==== Job Titles ====
To express one or more job titles/positions in the same experience event you should use [[hCard]]s. [[hcard]] requires the <code class="class-name">fn</code> ("formatted name") field, but it isn't reasonable to repeat your name for every job title you mark up in [[hResume|hresume]]. So, you may use an <code class="element"><object></code> and the class name '<code class="class-name">include</code>' with a reference to the <code class="class-name">fn</code> somewhere else on the page.

For example, this [[hCard]] refers to another [[hCard]]

<pre>
<span class="vcard">
<object data="#j" class="include"></object>
<span class="org">Preston High School</span>
<span class="title">Class President</span>
</span>
</pre>

Where "<code class="attr-value">j</code>" is the id attribute value of the "<code class="mf-prop">fn n</code>" element of the contact [[hCard]] at the top of the page, e.g. (shown here as a verbose [[hCard]] for purposes of illustration that the reference may be to a subtree, not just a text node):

<pre><nowiki>
<address class="vcard">
<span class="fn n" id="j">
<span class="given-name">Pedro</span>
<span class="family-name">Sanchez</span>
</span>
</address>
</nowiki></pre>

This method of hCard property indirection via an object element [[include-pattern|has been generalized]] to apply to any/all string/text properties in hCard.
Note: the object data attribute MUST be a local ID reference. External references (which would require a consuming application to load an external resource) are currently not supported by this method.

=== Skills ===
Some sample skills tags:
<pre><nowiki>
I have skills in <a class="skill" rel="tag" href="http://en.wikipedia.org/wiki/Bow_%28weapon%29">bow hunting</a>
and <a class="skill" rel="tag" href="http://en.wikipedia.org/wiki/Nunchucks">nunchucks</a>.
</nowiki></pre>

=== Affiliations ===
<pre><nowiki>
<span class="affiliation vcard"><span class="fn org">National Honor Society</span></span>
</nowiki></pre>

=== Publications ===
<pre><nowiki>
<cite>Breeding Ligers for Fun and Magic</cite>, Idaho Press, 2004.
</nowiki></pre>

== Examples in the wild ==
This section is '''informative'''.

The following sites have published hResumes, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If you have an hResume on your own page, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

* [http://portfolio.jonnay.net/cv/ Jonathan Arkell]] has posted an hResume on his (work in progress) portfolio website.
* [http://steve.ganz.name/hresume/ Steve Ganz - hResume 0.1]
* [[User:Dave Cardwell|Dave Cardwell]] has marked up [http://davecardwell.co.uk/cv/ his curriculum vitae] as an hResume.
** If you are working on hResume, please take a look and point out any glaring problems to davecardwell on #microformats on irc.

== Profile ==
@TODO

== Implementations ==
@TODO

== References ==
=== Normative References ===
* [http://www.w3.org/TR/REC-html40/ HTML 4]
* [http://www.w3.org/TR/xhtml1/ XHTML]
* [http://gmpg.org/xmdp/ XMDP]
* [[rel-tag| Rel-Tag]]
* @TODO

=== Informative References ===
@TODO

== Copyright ==
{{MicroFormatCopyrightStatement2006}}

== Patents ==
{{MicroFormatPatentStatement}}

== Acknowledgements ==

=== Concept ===
* [http://theryanking.com/ Ryan King], [http://technorati.com Technorati]
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati]
* SimplyHired guys... @TODO
* [http://epeus.blogspot.com/ Kevin Marks], [http://technorati.com Technorati]

== See also ==
* [[resume-examples]]
* [[resume-formats]]
* [[resume-brainstorming]]

== Discussions ==

* Feedback is encouraged on the [[hresume-feedback]] page.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

=== Q&A ===
* If you have any questions about hResume, check the [[hresume-faq|hResume FAQ]], and if you don't find answers, add your questions to the end!

=== Issues ===
* Please add any issues with the specification to the separate [[hresume-issues|hResume issues]] document.