Microformats Wiki - User contributions [en]

microformateers

2009-10-27T14:33:27Z

EmilyLewis: Added self to interested list

<entry-title>Microformateers</entry-title>

[http://twitter.com/microformateers Microformateers] is a Twitter account providing quick answers to people's questions about microformats. Twitter is full of people with short queries about syntax, or remarking upon things they've read about microformats. Microformats.org already runs the [http://twitter.com/microformats @microformats] account for pushing news and announcements, but the microformateers effort is about responding.

==What is this?==

Microformateers is a single Twitter account, shared between a number of individual contributors. They monitor Twitter searches for mentions of microformats and related terms, and respond directly and publicly to people's lazy-web questions, ideally within 140 characters. Where longer code examples are required, code snippets areposted to [http://gist.github.com gist].

==Who are the microformateers?==

<div class="vcard">
Because of the mechanics of Twitter (a single account, shared with a single password) it is not possible for the Microformateers account to be open to all. '''The following agents are currently ‘on duty’''':

<div class="agent vcard">
===Frances Berriman (^FB)===

https://s3.amazonaws.com/twitter_production/profile_images/58225171/17464024_N00_normal_bigger.jpg

* http://twitter.com/phae
* [[User:Phae]]
</div>

<div class="agent vcard">
===Tantek Çelik (^T)===

http://a1.twimg.com/profile_images/76685310/ca-sci-t_bigger.jpg

* http://twitter.com/t
* [[User:Tantek]]
</div>

<div class="agent vcard">
===Jeremy Keith (^??)===

https://s3.amazonaws.com/twitter_production/profile_images/65971001/avatar_bigger.jpg

* http://twitter.com/adactio
* [[User:Adactio]]
</div>

<div class="agent vcard">
===Kevin Marks (^KM)===

http://a1.twimg.com/profile_images/130885696/kevin300am-1_bigger.jpg
* http://twitter.com/kevinmarks
* [[User:Kevin Marks]]
</div>

<div class="agent vcard">
===Drew McLellan (^??)===

https://s3.amazonaws.com/twitter_production/profile_images/124177936/peek_bigger.jpg

* http://twitter.com/drewm
* [[User:DrewMcLellan]]
</div>

<div class="agent vcard">
===Matthias Pfefferle (^MP)===

http://a1.twimg.com/profile_images/481055128/b36983a5651df2c413e264ad4d5cc1a1.jpeg_bigger.jpg

* http://twitter.com/pfefferle
* [[User:Pfefferle]]
</div>

<div class="agent vcard">
===Ben Ward (^BW)===

https://s3.amazonaws.com/twitter_production/profile_images/150824912/2009-200_bigger.jpg

* http://twitter.com/benward
* [[User:BenWard]]
</div>

</div>


==Response Process==

* Microformateers is a single Twitter identity shared between an appropriate number of trusted individuals
* When you have a free moment or the mood takes you, monitor searches for microformats terms (there's one saved in the account already)
* When you find a question to be answered, respond using the [http://twitter.com/microformateers @microformateers account]
* If you need to provide code, stick it on [http://gist.github.com gist.github.com] (or similar pastebin service) and link to it. Gist is good though, as it ties into the Github community as well.
* When you answer someone's question, add the tweet to the [http://twitter.com/microformateers/favorites @microformateers’ favorites], that we avoid inundating questioners with duplicate answers. (Most quality Twitter clients, as well as the Twitter website itself, indicate which tweets you have ‘faved’ inline.)
* Where possible, save 3 characters to sign the tweet with a <kbd>^XX</kbd>, using your initials, so people can reference you personally as well. (e.g. ^BW, ^T, ^JK, ^FB… something identifiabley.) People can refer to this wiki page to look-up the individual. <code>^AB</code> is an existing convention on Twitter for this purpose, used by software such as Co-Tweet.

==Interested List==

If you're interested in becoming an agent for the microformateers, please add your name to the list below. There are a couple of constraints on this system: First is trust and security, simply because Twitter's account model requires sharing the same master password for the @microformateers account between all participants; we have to be conservative with proliferation. The second issue is meeting volume of demand. At present, we think that 4/5 agents is about the right number to be involved given the volume of questions and content that come through Twitter. But, as agents come and go, or as question demand increases we'll refer to this list. Thanks. (Technical solutions to make sharing Twitter accounts safer and accountable are also up for future consideration.) —[[User:BenWard|BenWard]] 21:31, 26 September 2009 (UTC)

* [[User:Pfefferle]] - http://twitter.com/pfefferle & http://twitter.com/mikroformate
** +1 [[User:Tantek|Tantek]] 22:16, 28 September 2009 (UTC)
* [[User:EdwardOConnor|Ted]]
** +1 [[User:Tantek|Tantek]] 21:18, 15 October 2009 (UTC)
* [[User:EmilyLewis|Emily Lewis]]

events/2009-10-07-intro-to

2009-10-21T18:51:54Z

EmilyLewis: Added link to recap blog post

<entry-title>Introduction to Microformats</entry-title>
__TOC__
One of several microformats [[events]].

<div class="event-page vevent">
== Details ==
;When
:2009-10-07 from 18:30 to 19:30
;Where
:Uptown Sports Bar & Grill, 6601 Uptown Blvd NE, Albuquerque, New Mexico 87110 USA
;What
:Introduction to Microformats by [[User:EmilyLewis|Emily Lewis]]
;Web
:http://upcoming.yahoo.com/event/4226407/

'''[http://suda.co.uk/projects/microformats/hcalendar/get-cal.php?uri=http%3A//microformats.org/wiki/events/2009-10-07-weekly-dinner-sf Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Tags ==
Use the following tags on related content (blog posts, photos, [http://twitter.com tweets]):

tags:
<kbd class="tags" style="display:block">
'''microformats-2009-10-07'''
microformats-meetup
microformats
microformats-session
microformats-presentation
albuquerque
webuquerque
''upcoming:event=4226407''
</kbd>

If you use Twitter, mention ''@microformats''' in tweets about the event, and track them on [http://search.twitter.com/search?q=microformats Twitter Search].

== Attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended this event.

* Brian Arnold
* Lisa Arnold
* Chandra Bales
* Mike Bales
* Caroline Blaker
* Pete Brown
* Mark Casias
* Daniel Clark
* Virginia DeBolt
* Miranda Evjen
* Reid Givens
* Greg Gomez
* Chris Kenworthy
* [[User:EmilyLewis|Emily Lewis]]
* Patti March
* Sara McCollum
* Peter Mezensky
* Maria Moreno
* Jason Nakai
* Will Reichard
* Parry Silcox
* Brooks Walch
* Zerek Welz

== Notes ==

Topics Discussed:

* Semantics
* POSH
* rel-tag
* hCard
* hCalendar
* Benefits of microformats
* Google's Rich Snippets
* Oomph Microformats Toolkit
* Operator add-on for Firefox
* Tails Export add-on for Firefox
* Huffduffer
* Ident Engine

== Photographs ==

* Search for photographs from this event on Flickr: [http://flickr.com/photos/tags/microformats-2009-10-07 Photographs tagged microformats-2009-10-07] or for [http://flickr.com/photos/tags/microformats-meetup all photographs from microformats meetups].

''Add a photograph from this event here''.

== Articles and Blog Posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below:

* [http://webuquerque.com/Events/Introduction-Microformats.php Introduction to Microformats]
* [http://www.ablognotlimited.com/articles/webuquerque-introduction-to-microformats/ Introduction to Microformats Recap]

Also, find posts on this meetup on [http://blogsearch.google.com/blogsearch?q=microformats-2009-10-07 Google Blog Search] or [http://technorati.com/search/microformats-2009-10-07 Technorati].

</div> 

== Related Pages==
{{events-related-pages}}

events/2009-10-07-intro-to

2009-10-20T19:29:53Z

EmilyLewis: Reorganized attendee list alphabetically by family name

<entry-title>Introduction to Microformats</entry-title>
__TOC__
One of several microformats [[events]].

<div class="event-page vevent">
== Details ==
;When
:2009-10-07 from 18:30 to 19:30
;Where
:Uptown Sports Bar & Grill, 6601 Uptown Blvd NE, Albuquerque, New Mexico 87110 USA
;What
:Introduction to Microformats by [[User:EmilyLewis|Emily Lewis]]
;Web
:http://upcoming.yahoo.com/event/4226407/

'''[http://suda.co.uk/projects/microformats/hcalendar/get-cal.php?uri=http%3A//microformats.org/wiki/events/2009-10-07-weekly-dinner-sf Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Tags ==
Use the following tags on related content (blog posts, photos, [http://twitter.com tweets]):

tags:
<kbd class="tags" style="display:block">
'''microformats-2009-10-07'''
microformats-meetup
microformats
microformats-session
microformats-presentation
albuquerque
webuquerque
''upcoming:event=4226407''
</kbd>

If you use Twitter, mention ''@microformats''' in tweets about the event, and track them on [http://search.twitter.com/search?q=microformats Twitter Search].

== Attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended this event.

* Brian Arnold
* Lisa Arnold
* Chandra Bales
* Mike Bales
* Caroline Blaker
* Pete Brown
* Mark Casias
* Daniel Clark
* Virginia DeBolt
* Miranda Evjen
* Reid Givens
* Greg Gomez
* Chris Kenworthy
* [[User:EmilyLewis|Emily Lewis]]
* Patti March
* Sara McCollum
* Peter Mezensky
* Maria Moreno
* Jason Nakai
* Will Reichard
* Parry Silcox
* Brooks Walch
* Zerek Welz

== Notes ==

Topics Discussed:

* Semantics
* POSH
* rel-tag
* hCard
* hCalendar
* Benefits of microformats
* Google's Rich Snippets
* Oomph Microformats Toolkit
* Operator add-on for Firefox
* Tails Export add-on for Firefox
* Huffduffer
* Ident Engine

== Photographs ==

* Search for photographs from this event on Flickr: [http://flickr.com/photos/tags/microformats-2009-10-07 Photographs tagged microformats-2009-10-07] or for [http://flickr.com/photos/tags/microformats-meetup all photographs from microformats meetups].

''Add a photograph from this event here''.

== Articles and Blog Posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below:

* [http://webuquerque.com/Events/Introduction-Microformats.php Webuquerque: Introduction to Microformats]

Also, find posts on this meetup on [http://blogsearch.google.com/blogsearch?q=microformats-2009-10-07 Google Blog Search] or [http://technorati.com/search/microformats-2009-10-07 Technorati].

</div> 

== Related Pages==
{{events-related-pages}}

events/2009-10-07-intro-to

2009-10-20T19:25:22Z

EmilyLewis: Added attendees

<entry-title>Introduction to Microformats</entry-title>
__TOC__
One of several microformats [[events]].

<div class="event-page vevent">
== Details ==
;When
:2009-10-07 from 18:30 to 19:30
;Where
:Uptown Sports Bar & Grill, 6601 Uptown Blvd NE, Albuquerque, New Mexico 87110 USA
;What
:Introduction to Microformats by [[User:EmilyLewis|Emily Lewis]]
;Web
:http://upcoming.yahoo.com/event/4226407/

'''[http://suda.co.uk/projects/microformats/hcalendar/get-cal.php?uri=http%3A//microformats.org/wiki/events/2009-10-07-weekly-dinner-sf Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Tags ==
Use the following tags on related content (blog posts, photos, [http://twitter.com tweets]):

tags:
<kbd class="tags" style="display:block">
'''microformats-2009-10-07'''
microformats-meetup
microformats
microformats-session
microformats-presentation
albuquerque
webuquerque
''upcoming:event=4226407''
</kbd>

If you use Twitter, mention ''@microformats''' in tweets about the event, and track them on [http://search.twitter.com/search?q=microformats Twitter Search].

== Attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended this event.

* [[User:EmilyLewis|Emily Lewis]]
* Jason Nakai
* Virginia DeBolt
* Brian Arnold
* Mark Casias
* Chris Kenworthy
* Miranda Evjen
* Pete Brown
* Brooks Walch
* Reid Givens
* Peter Mezensky
* Zerek Welz
* Daniel Clark
* Lisa Arnold
* Will Reichard
* Caroline Blaker
* Sara McCollum
* Chandra Bales
* Mike Bales
* Patti March
* Greg Gomez
* Maria Moreno
* Parry Silcox

== Notes ==

Topics Discussed:

* Semantics
* POSH
* rel-tag
* hCard
* hCalendar
* Benefits of microformats
* Google's Rich Snippets
* Oomph Microformats Toolkit
* Operator add-on for Firefox
* Tails Export add-on for Firefox
* Huffduffer
* Ident Engine

== Photographs ==

* Search for photographs from this event on Flickr: [http://flickr.com/photos/tags/microformats-2009-10-07 Photographs tagged microformats-2009-10-07] or for [http://flickr.com/photos/tags/microformats-meetup all photographs from microformats meetups].

''Add a photograph from this event here''.

== Articles and Blog Posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below:

* [http://webuquerque.com/Events/Introduction-Microformats.php Webuquerque: Introduction to Microformats]

Also, find posts on this meetup on [http://blogsearch.google.com/blogsearch?q=microformats-2009-10-07 Google Blog Search] or [http://technorati.com/search/microformats-2009-10-07 Technorati].

</div> 

== Related Pages==
{{events-related-pages}}

events/2009-10-07-intro-to

2009-10-20T18:21:03Z

EmilyLewis: Added article

<entry-title>Introduction to Microformats</entry-title>
__TOC__
One of several microformats [[events]].

<div class="event-page vevent">
== Details ==
;When
:2009-10-07 from 18:30 to 19:30
;Where
:Uptown Sports Bar & Grill, 6601 Uptown Blvd NE, Albuquerque, New Mexico 87110 USA
;What
:Introduction to Microformats by [[User:EmilyLewis|Emily Lewis]]
;Web
:http://upcoming.yahoo.com/event/4226407/

'''[http://suda.co.uk/projects/microformats/hcalendar/get-cal.php?uri=http%3A//microformats.org/wiki/events/2009-10-07-weekly-dinner-sf Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Tags ==
Use the following tags on related content (blog posts, photos, [http://twitter.com tweets]):

tags:
<kbd class="tags" style="display:block">
'''microformats-2009-10-07'''
microformats-meetup
microformats
microformats-session
microformats-presentation
albuquerque
webuquerque
''upcoming:event=4226407''
</kbd>

If you use Twitter, mention ''@microformats''' in tweets about the event, and track them on [http://search.twitter.com/search?q=microformats Twitter Search].

== Attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended this event.

* [[User:EmilyLewis|Emily Lewis]]
* Jason Nakai
* Virginia DeBolt
* Brian Arnold
* Mark Casias
* Chris Kenworthy
* Miranda Evjen
* Pete Brown
* Brooks Walch
* Reid Givens
* Peter Mezensky
* Zerek Welz
* Daniel Clark
* Lisa Arnold
* Will Reichard
* Caroline Blaker
* Sara McCollum
* Chandra Bales
* Mike Bales
* Patti March

== Notes ==

Topics Discussed:

* Semantics
* POSH
* rel-tag
* hCard
* hCalendar
* Benefits of microformats
* Google's Rich Snippets
* Oomph Microformats Toolkit
* Operator add-on for Firefox
* Tails Export add-on for Firefox
* Huffduffer
* Ident Engine

== Photographs ==

* Search for photographs from this event on Flickr: [http://flickr.com/photos/tags/microformats-2009-10-07 Photographs tagged microformats-2009-10-07] or for [http://flickr.com/photos/tags/microformats-meetup all photographs from microformats meetups].

''Add a photograph from this event here''.

== Articles and Blog Posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below:

* [http://webuquerque.com/Events/Introduction-Microformats.php Webuquerque: Introduction to Microformats]

Also, find posts on this meetup on [http://blogsearch.google.com/blogsearch?q=microformats-2009-10-07 Google Blog Search] or [http://technorati.com/search/microformats-2009-10-07 Technorati].

</div> 

== Related Pages==
{{events-related-pages}}

events/2009-10-07-intro-to

2009-10-20T18:10:56Z

EmilyLewis: /* Notes */

<entry-title>Introduction to Microformats</entry-title>
__TOC__
One of several microformats [[events]].

<div class="event-page vevent">
== Details ==
;When
:2009-10-07 from 18:30 to 19:30
;Where
:Uptown Sports Bar & Grill, 6601 Uptown Blvd NE, Albuquerque, New Mexico 87110 USA
;What
:Introduction to Microformats by [[User:EmilyLewis|Emily Lewis]]
;Web
:http://upcoming.yahoo.com/event/4226407/

'''[http://suda.co.uk/projects/microformats/hcalendar/get-cal.php?uri=http%3A//microformats.org/wiki/events/2009-10-07-weekly-dinner-sf Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Tags ==
Use the following tags on related content (blog posts, photos, [http://twitter.com tweets]):

tags:
<kbd class="tags" style="display:block">
'''microformats-2009-10-07'''
microformats-meetup
microformats
microformats-session
microformats-presentation
albuquerque
webuquerque
''upcoming:event=4226407''
</kbd>

If you use Twitter, mention ''@microformats''' in tweets about the event, and track them on [http://search.twitter.com/search?q=microformats Twitter Search].

== Attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended this event.

* [[User:EmilyLewis|Emily Lewis]]
* Jason Nakai
* Virginia DeBolt
* Brian Arnold
* Mark Casias
* Chris Kenworthy
* Miranda Evjen
* Pete Brown
* Brooks Walch
* Reid Givens
* Peter Mezensky
* Zerek Welz
* Daniel Clark
* Lisa Arnold
* Will Reichard
* Caroline Blaker
* Sara McCollum
* Chandra Bales
* Mike Bales
* Patti March

== Notes ==

Topics Discussed:

* Semantics
* POSH
* rel-tag
* hCard
* hCalendar
* Benefits of microformats
* Google's Rich Snippets
* Oomph Microformats Toolkit
* Operator add-on for Firefox
* Tails Export add-on for Firefox
* Huffduffer
* Ident Engine

== Photographs ==

* Search for photographs from this event on Flickr: [http://flickr.com/photos/tags/microformats-2009-10-07 Photographs tagged microformats-2009-10-07] or for [http://flickr.com/photos/tags/microformats-meetup all photographs from microformats meetups].

''Add a photograph from this event here''.

== Articles and Blog Posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below:

* ...

Also, find posts on this meetup on [http://blogsearch.google.com/blogsearch?q=microformats-2009-10-07 Google Blog Search] or [http://technorati.com/search/microformats-2009-10-07 Technorati].

</div> 

== Related Pages==
{{events-related-pages}}

events/2009-10-07-intro-to

2009-10-20T18:08:51Z

EmilyLewis: /* Attendees */

<entry-title>Introduction to Microformats</entry-title>
__TOC__
One of several microformats [[events]].

<div class="event-page vevent">
== Details ==
;When
:2009-10-07 from 18:30 to 19:30
;Where
:Uptown Sports Bar & Grill, 6601 Uptown Blvd NE, Albuquerque, New Mexico 87110 USA
;What
:Introduction to Microformats by [[User:EmilyLewis|Emily Lewis]]
;Web
:http://upcoming.yahoo.com/event/4226407/

'''[http://suda.co.uk/projects/microformats/hcalendar/get-cal.php?uri=http%3A//microformats.org/wiki/events/2009-10-07-weekly-dinner-sf Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Tags ==
Use the following tags on related content (blog posts, photos, [http://twitter.com tweets]):

tags:
<kbd class="tags" style="display:block">
'''microformats-2009-10-07'''
microformats-meetup
microformats
microformats-session
microformats-presentation
albuquerque
webuquerque
''upcoming:event=4226407''
</kbd>

If you use Twitter, mention ''@microformats''' in tweets about the event, and track them on [http://search.twitter.com/search?q=microformats Twitter Search].

== Attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended this event.

* [[User:EmilyLewis|Emily Lewis]]
* Jason Nakai
* Virginia DeBolt
* Brian Arnold
* Mark Casias
* Chris Kenworthy
* Miranda Evjen
* Pete Brown
* Brooks Walch
* Reid Givens
* Peter Mezensky
* Zerek Welz
* Daniel Clark
* Lisa Arnold
* Will Reichard
* Caroline Blaker
* Sara McCollum
* Chandra Bales
* Mike Bales
* Patti March

== Notes ==

Topics Discussed:

* ...

== Photographs ==

* Search for photographs from this event on Flickr: [http://flickr.com/photos/tags/microformats-2009-10-07 Photographs tagged microformats-2009-10-07] or for [http://flickr.com/photos/tags/microformats-meetup all photographs from microformats meetups].

''Add a photograph from this event here''.

== Articles and Blog Posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below:

* ...

Also, find posts on this meetup on [http://blogsearch.google.com/blogsearch?q=microformats-2009-10-07 Google Blog Search] or [http://technorati.com/search/microformats-2009-10-07 Technorati].

</div> 

== Related Pages==
{{events-related-pages}}

events/2009-10-07-intro-to

2009-10-20T18:04:33Z

EmilyLewis: /* Details */

<entry-title>Introduction to Microformats</entry-title>
__TOC__
One of several microformats [[events]].

<div class="event-page vevent">
== Details ==
;When
:2009-10-07 from 18:30 to 19:30
;Where
:Uptown Sports Bar & Grill, 6601 Uptown Blvd NE, Albuquerque, New Mexico 87110 USA
;What
:Introduction to Microformats by [[User:EmilyLewis|Emily Lewis]]
;Web
:http://upcoming.yahoo.com/event/4226407/

'''[http://suda.co.uk/projects/microformats/hcalendar/get-cal.php?uri=http%3A//microformats.org/wiki/events/2009-10-07-weekly-dinner-sf Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Tags ==
Use the following tags on related content (blog posts, photos, [http://twitter.com tweets]):

tags:
<kbd class="tags" style="display:block">
'''microformats-2009-10-07'''
microformats-meetup
microformats
microformats-session
microformats-presentation
albuquerque
webuquerque
''upcoming:event=4226407''
</kbd>

If you use Twitter, mention ''@microformats''' in tweets about the event, and track them on [http://search.twitter.com/search?q=microformats Twitter Search].

== Attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended this event.

* [[User:EmilyLewis|Emily Lewis]]
* ...

== Notes ==

Topics Discussed:

* ...

== Photographs ==

* Search for photographs from this event on Flickr: [http://flickr.com/photos/tags/microformats-2009-10-07 Photographs tagged microformats-2009-10-07] or for [http://flickr.com/photos/tags/microformats-meetup all photographs from microformats meetups].

''Add a photograph from this event here''.

== Articles and Blog Posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below:

* ...

Also, find posts on this meetup on [http://blogsearch.google.com/blogsearch?q=microformats-2009-10-07 Google Blog Search] or [http://technorati.com/search/microformats-2009-10-07 Technorati].

</div> 

== Related Pages==
{{events-related-pages}}

events/2009-10-07-intro-to

2009-10-20T18:03:51Z

EmilyLewis: /* Details */

<entry-title>Introduction to Microformats</entry-title>
__TOC__
One of several microformats [[events]].

<div class="event-page vevent">
== Details ==
;When
:2009-10-07 from 18:30 to 19:30
;Where
:Uptown Sports Bar & Grill, 6601 Uptown Blvd NE, Albuquerque, New Mexico 87110 USA
;What
:Introduction to Microformats by [[User:EmilyLewis]]
;Web
:http://upcoming.yahoo.com/event/4226407/

'''[http://suda.co.uk/projects/microformats/hcalendar/get-cal.php?uri=http%3A//microformats.org/wiki/events/2009-10-07-weekly-dinner-sf Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Tags ==
Use the following tags on related content (blog posts, photos, [http://twitter.com tweets]):

tags:
<kbd class="tags" style="display:block">
'''microformats-2009-10-07'''
microformats-meetup
microformats
microformats-session
microformats-presentation
albuquerque
webuquerque
''upcoming:event=4226407''
</kbd>

If you use Twitter, mention ''@microformats''' in tweets about the event, and track them on [http://search.twitter.com/search?q=microformats Twitter Search].

== Attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended this event.

* [[User:EmilyLewis|Emily Lewis]]
* ...

== Notes ==

Topics Discussed:

* ...

== Photographs ==

* Search for photographs from this event on Flickr: [http://flickr.com/photos/tags/microformats-2009-10-07 Photographs tagged microformats-2009-10-07] or for [http://flickr.com/photos/tags/microformats-meetup all photographs from microformats meetups].

''Add a photograph from this event here''.

== Articles and Blog Posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below:

* ...

Also, find posts on this meetup on [http://blogsearch.google.com/blogsearch?q=microformats-2009-10-07 Google Blog Search] or [http://technorati.com/search/microformats-2009-10-07 Technorati].

</div> 

== Related Pages==
{{events-related-pages}}

value-excerption-value-title-test

2009-01-23T23:44:02Z

EmilyLewis: /* Successful Tests */

<entry-title>Value Excerption Pattern: Parsing 'value' from an empty element</entry-title>
'''This page is targetted at those already experienced with microformats.'''

''Please carefully note, this page is about a pre-draft, experimental and unfinished microformats proposal. You '''cannot''' use this pattern on your live pages, it is '''not supported''' by any stable parser and you should not assume that this pattern will be finalized as-is! We're just asking for help in testing this thoroughly. '''Thank you'''.''
__TOC__
This is a special page to introduce and gather results to widespread testing of a '''proposed''' extension to the value-excerption pattern. See [[value-excerption-pattern-brainstorming#.E2.80.98value-title.E2.80.99|value excerption pattern brainstorming: value-title]] for the specific proposal.

This pattern can be used to resolve some long standing issues with including [[machine-data|machine-data in microformats]]; it's imperative we test thoroughly before adding it to any pattern specification. Following are a number of example tests. ''Please try them out''.

The pattern we're testing looks a little something like this. Those experienced with microformats should immediately see what we're trying to do:

<source lang=html4strict>



mobile

+44 7773 000 000

</source>

<source lang=html4strict>


January 6th, in the evening

</source>

It allows you to include machine-form data alongside the human form, without polluting visible formatted content with undesired machine form data.

This covers cases where a microformat uses a fixed format of data that is either inappropriate for visible inclusion in a page (such as a full date-time and timezone string), or where an American-English keyword is needed — such as <code>cell</code> instead of ‘mobile’ in a British English page, or any number of non-English translations.

This pattern is based on rendering behavior in browsers whereby an empty element — that is one containing no text-nodes or other child elements — remains in the DOM tree (for parsing) but is not rendered visibly to a page. This allows an element to be included in the document with a <code>title</code> attribute (as in the example), but ''without'' a tooltip being exposed to users, and without the data being read out by screen readers.

You can use <code>value-title</code> on non-empty elements as well; whatever makes most sense to your publishing scenario. This page is dedicated to the empty-element version though, since that offers up the consumption unknowns.

Based on everything we know up to this point, we believe this pattern will work. But, it's wide ranging and the web is broad, and we want to be sure. Please, help us out testing this pattern proposal. Examples tests are below, please push them or your own variants into publishing systems, content management systems, editor applications and tools. Check that it comes out the other side with the data intact, and exposed (or hidden) as expected: Render it in desktop browsers, mobile browers, screen readers, in braille… ''anything you can test, we want to know about''! We need to see any quirks, oddities and so on.

Also, by all means provide thoughts on the publishing flow for this. An empty element is an uncommon structure outside of forms and scripts, but the reasoning is as follows: ''‘Machine formatted data’ is not metadata, it is content. Therefore, it's structurally appropriate to have it as a sibling to the human-formatted content.''

'''Note that valid HTML is a cornerstone of microformats'''. ''Inventing new attributes, depending on unstable drafts of HTML5, using non-standard DOCTYPEs or XML extensions is not an applicable option''. We're trying to achieve something as gracefully as we can within the limitations of HTML4, and without harming user experience.

==The proposed parsing rules==

The current, likely incomplete, parsing rules and restrictions for this pattern are as follows:

* Only one <code>value-title</code> element may be included as a child of a property. No splitting or concatenation, no combining with other value-excerption elements.
* An empty <code>value-title</code> element '''must''' be the ''first''-child of the property (not including any preceding whitespace). To alleviate the [[value-excerption-pattern-brainstorming#issues_2|negative impact of non-visible data]], the value should be as near as possible to declaring the property.
* The machine-data value ''must'' represent the same data as the visible text; the parent property ''must not'' contain arbitrary data. Validator tools will be encouraged to verify this where possible (for example, some programming languages have access to powerful date parsing algorithms that can compare human dates to the ISO form).
* The empty element can be ''any element'', but a generic <code>span</code> is most appropriate. You could use <code>b</code> if you want to save bytes, or an <code>input type=hidden</code> if it makes sense to you. That choice will not matter to parsers. You are in complete control of that publishing decision. As per usual µf documentation, <code>span</code> will be used for generic examples.
* The <code>value-title</code> property does not have to be empty. If you ''do'' want a tool-tip to expose a useful data-form, you can. e.g. <code>last year</code> is valid too.

==Example Tests==

The following snippets are example tests for the new pattern. You can use them as is, or use them as a base for your own tests with your own content. If you write your own tests, please document them under ‘additional test cases’ so that any failing tests can be checked for validity.

===hAtom#1: An hAtom <code>published</code>/<code>updated</code> Property===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hAtom#1</title>
</head>
<body>
<div class="hentry">
<h1 class="entry-title">An introduction to Microformats</h1>

Published on 

January 9th, around lunchtime
by 
<a class="url fn" href="http://example.com">
Joe Blogger</a>.

Wow, microformats are really useful! You can
learn loads about them on the
<a href="http://microformats.org/wiki">microformats wiki</a>.

</div>
</body>
</html>
</source>

===hCal#1: An hCalendar <code>dtstart</code>===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hCal#1</title>
</head>
<body>
<div class="vevent">
<h1 class="summary">Value Exception Test Day!</h1>
Come help 
<a class="fn url org" href="http://microformats.org">microformats.org</a>
 test a new value-excerption pattern for sanity and
robustness!

Help out by running some tests at


midday on Monday January 12th.

See <a class="url" href="http://microformats.org/wiki/value-excerption-pattern-issues/empty-value-element-test">the
wiki</a> for more details!

</div>
</body>
</html>
</source>

===hCard#1: An hCard <abbr title="birthday"><code>bday</code></abbr>===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hCard#1</title>
</head>
<body>

<div class="vcard">
<h1 class="fn">Ben Ward</h1>
Ben Ward's birthday is


February 9th
.
You should throw him a party! Or call his 
mobile
on 415.123.123 to wish him well!

</div>

</body>
</html>
</source>

===hAudio#1: An hAudio <code>duration</code>===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hAudio#1</title>
</head>
<body>
<h1>Song of the year?</h1>

Did you hear ‘Heavy Water’ on
Foals
‘Antidodes’ record


last year
? It's


4 and a half minutes long
, you should make time to hear it!
</div>

</body>
</html>
</source>

''If you believe there is an error in any of these tests, or in any others that people contribute, please post on the {{MicroformatsMailingList}}.''

==Evil Tests==

If you want to give existing microformat parsers a good run out, construct ‘evil’ tests using nesting, combination and interpolation of different microformats.

===hAtom + hCalendar===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hAtomhCalEvil#1</title>
</head>
<body>
<div class="hentry vevent">
<h1 class="entry-title summary">An introduction to Microformats</h1>

Published on 

January 11th, late afternoon
by 
<a class="url fn" href="http://example.com">
Joe Blogger</a>.




this coming Wednesday at 7
 is not the date of a completely fictional microformats
event. If it existed, it would promise to be informative and get
you up to speed on microformats.org for 2009! Now you've
learned to work with microformats a little, why not attend and
get involved! Why not? Because this event is a test case, not
for real.

</div>
</body>
</html>
</source>

==Response==

* Don't like the empty element? Don't like the use of the title attribute? '''Please file general issues concerning the proposed pattern on the main [[value-excerption-pattern-brainstorming#enabling_more_use_of_title_attributes|value excerption brainstorming page]]''', or discuss them on the {{MicroformatsMailingList}}.
* Add results of tests and responses to these tests themselves on ''this page''.

Misplaced responses will be moved, and having to do so will make [[User:BenWard|Ben]] growly, so, y'know, please try to keep the wiki tidy.

===Successful Tests===

List successfully tested environments here. Add new environments as new list items, and expand existing list items with your name and platform variants to indicate verified successes.

{|
|+ Results of tests across various publishing/rendering environments
|-
! Product
! <abbr title="Publishing or Consuming?">P/C?</abbr>
! Platforms
! Test By
! Notes
|-
| MediaWiki/Linux
| Publishing
| Safari 3.2.1 (Mac OSX 10.5)
| [[User:BenWard]]
| The empty <code>span</code> elements are maintained in <abbr title="MediaWiki">MW</abbr> output. Note that <code>a</code> elements in the tests get escaped by this MediaWiki install.
|-
| Safari 2.0.4
| Consuming
| Mac OSX 10.5
| [[User:GeorgeBrock]]
| No tooltip.
|-
| Safari 3.2.1
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| Empty-span remains in DOM. Web Inspector reports the element has width and height of ‘0px’. No tooltip due to zero-dimensions.
|-
| Firefox 2.0
| Consuming
| Mac OSX 10.5
| [[User:GeorgeBrock]]
| Empty-span remains in DOM. Firebug reports the element has width of '0px' and height of ‘16px’. No tooltip due to zero-width.
|-
| Firefox 3.0
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| Empty-span remains in DOM. Firebug reports the element has width of '0px' and height of ‘16px’. No tooltip due to zero-width.
|-
| Firefox 3.1ß1
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| Empty-span remains in DOM. No tooltip.
|-
| Opera 9.62
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| Empty-span remains in DOM. Dragonfly reports the element has width of '0px' and height of ‘0px’. No tooltip due to zero-dimensions.
|-
| Internet Explorer 5.2
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| No tooltip.
|-
| Internet Explorer 6.0
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:GeorgeBrock]]
| Empty-span remains in DOM (visible to Web Developer Toolbar, accessible from Javascript). No tooltip.
|-
| Internet Explorer 7.0
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:GeorgeBrock]]
| Empty-span remains in DOM (visible to Web Developer Toolbar, accessible from Javascript). No tooltip.
|-
| Internet Explorer 8.0 beta 2
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:GeorgeBrock]]
| Empty-span remains in DOM. Developer Tools (built in to <abbr title="Internet Explorer 8 beta 2">IE8b2</abbr>) report the element has width of '0px' and height of '19px'. No tooltip due to zero-width.
|-
| Firefox 3.0.5
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No tooltip
|-
| Safari 3.2.1
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No tooltip
|-
| Opera 9.6
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No tooltip
|-
| Camino 1.6.5
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No tooltip
|-
| Flock 2.0.2
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No tooltip
|-
| Firefox 3.0.5
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Safari 3.0.3
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Opera 9.6.2
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Flock 2.0.2
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Chrome 1.0.154.43
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Internet Explorer 6
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Internet Explorer 7
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Native BlackBerry browser (BlackBerry mode)
| Consuming
| BlackBerry Storm OS 4.0.7.85 (leaked, non-official OS build from Verizon)
| [[User:EmilyLewis]]
| No tooltip
|-
| MobileSafari 3.2
| Consuming
| iPhone OS 2.2
| [[User:EmilyLewis]]
| No tooltip
|-
| IE Mobile 7.11
| Consuming
| Sprint HTC Mogul, OS: Windows Mobile 6.1
| [[User:EmilyLewis]]
| No tooltip
|-
| JAWS 10.0.512 (demo mode)
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No voice
|-
| Fire Vox (Firefox 3.0.5)
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No voice
|-
| WebbIE (Thunder 1.43)
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No voice
|-
| VoiceOver (Safari 3.2.1)
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No voice
|-
|}

===Failed Tests===

For failures, please provide as much information as you can. The precise impact of the error, whether the behavior could be regarded as a bug in the software you're testing, whether it works in subsequent releases, whether you changed any settings in the software to produce the result, and if so, whether enabling/disabling that setting should be regarded a showstopper if this pattern were certified.

Since we want more detail, please expand failures into headed sections rather than cramming into a table.

For example, take this entirely plausible scenario as a template:

====Example: Fake Publisher 3.1ß====
; Platform
: Windows Vista
; Test By
: [[User:BenWard]]
; Description
: When trying to enter an empty span in my <abbr title="Hypertext Markup Language">HTML</abbr> editor, which I wrote myself whilst I was high, the application immediately crashes, performs <code>rm -rf /</code> on all UNIX boxes connected to my local network (which also appears to cause Android phones within Bluetooth range to do the same…), and then causes all attached peripherals to combust. I was not able to reproduce, as my house was now on fire. I think using a self closing XHTML tag instead might work-around the problem because as we know, it's been proved by Real Scienticians that XML is always better than HTML. Alternatively, it may be a bug in the beta software.
; Notes
: This is a beta release, and a bug has been filed.
: This product has a known history of flammability bugs.
: The user must explicitly enable the ‘Endanger My Life’ checkbox under the ‘Advanced Mislabelled Checkboxes’ tab of the ‘Complicated Preferences’ preferences pane.
: You get the idea.

====Browser <abbr title="What you see is what you get">WYSIWYG</abbr> editor: [http://tinymce.moxiecode.com/ TinyMCE 3.2.1.1]====
; Platform
: Firefox 3.0 on Mac OSX 10.5
; Test By
: [[User:GeorgeBrock]]
; Description
: Empty spans entered using TinyMCE's source editor are removed when switching back to the default WYSIWYG view.
: This is not a bug with TinyMCE, the editor is designed to remove empty instances of most elements by default. The handling of empty elements can be changed by modifying the [http://wiki.moxiecode.com/index.php/TinyMCE:Configuration/valid_elements valid-elements setting] (e.g. change <code>-span</code> to <code>span</code> and empty spans will no longer be removed), however settings can only be changed by modifying the source code of the page that contains the TinyMCE instance, so it is likely that some users will not be able to apply this fix.
; Notes
: This behaviour can be easily reproduced using the online [http://tinymce.moxiecode.com/examples/full.php TinyMCE examples].
: TinyMCE is the default WYSIWYG editor in WordPress[http://codex.wordpress.org/TinyMCE].
: With a single whitespace character (‘space’), the <code>span</code> is preserved, but yet still seems to collapse in Safari. Will write a follow-up test.--[[User:BenWard|BenWard]] 23:11, 20 January 2009 (UTC)
: You ''can'' publish this pattern using the <code>input type='hidden' class='value-title' title='2009-01-20'</code> hinted above. Semantically odd, although it's been suggested on µf lists before. Publishing workaround exists through element agnosticism. --[[User:BenWard|BenWard]] 23:11, 20 January 2009 (UTC)

====Browser <abbr title="What you see is what you get">WYSIWYG</abbr> editor: [http://www.fckeditor.net/ FCKEditor 2.6.4 Beta]====
; Platform
: Firefox 3.0 on Mac OSX 10.5
; Test By
: [[User:GeorgeBrock]]
; Description
: Empty spans entered using FCKEditor's source editor are removed when switching back to the default WYSIWYG view or submitting the form that contains the FCKEditor instance.
; Notes
: This behaviour can be easily reproduced using the online [http://www.fckeditor.net/demo FCKEditor demo].
: FCKEditor is used by various content management systems, frameworks and applications[http://www.fckeditor.net/whosusing].
: With a single whitespace character (‘space’), the <code>span</code> is preserved, but yet still seems to collapse in Safari. Will write a follow-up test.--[[User:BenWard|BenWard]] 23:12, 20 January 2009 (UTC)
: You ''can'' publish this pattern using the <code>input type='hidden' class='value-title' title='2009-01-20'</code> mentioned above. --[[User:BenWard|BenWard]] 23:12, 20 January 2009 (UTC)
: This issue does not effect FCKEditor instances that use the Placeholders plugin (this plugin comes with FCKEditor, enable it using <code>FCKConfig.Plugins.Add('placeholder')</code>). Examining the Placeholders plugin code may yield an easier work-around than including the plugin (I had a quick look but didn't see anything that was obviously responsible for allowing empty spans) -[[User:GeorgeBrock|GeorgeBrock]] 23:20, 20 January 2009 (UTC)



===General Test Feedback===
<div class='discussion'>
* Any general feedback you have on this test is most welcome. However, if you have issues with the pattern or alternate suggestions, please file them on the main [[value-excerption-pattern-issues]] page. Also, please remember to sign your comments with <nowiki>—~~~~</nowiki> —[[User:BenWard|BenWard]] 00:12, 9 January 2009 (UTC)
* … 
** … 
</div>

==Related Pages==
* [[value-excerption-pattern]]
* [[value-excerption-pattern-issues]]
* [[value-excerption-pattern-brainstorming]]
* [[value-excerption-dt-separation-test]]

value-excerption-value-title-test

2009-01-23T19:50:12Z

EmilyLewis: /* Successful Tests */

<entry-title>Value Excerption Pattern: Parsing 'value' from an empty element</entry-title>
'''This page is targetted at those already experienced with microformats.'''

''Please carefully note, this page is about a pre-draft, experimental and unfinished microformats proposal. You '''cannot''' use this pattern on your live pages, it is '''not supported''' by any stable parser and you should not assume that this pattern will be finalized as-is! We're just asking for help in testing this thoroughly. '''Thank you'''.''
__TOC__
This is a special page to introduce and gather results to widespread testing of a '''proposed''' extension to the value-excerption pattern. See [[value-excerption-pattern-brainstorming#.E2.80.98value-title.E2.80.99|value excerption pattern brainstorming: value-title]] for the specific proposal.

This pattern can be used to resolve some long standing issues with including [[machine-data|machine-data in microformats]]; it's imperative we test thoroughly before adding it to any pattern specification. Following are a number of example tests. ''Please try them out''.

The pattern we're testing looks a little something like this. Those experienced with microformats should immediately see what we're trying to do:

<source lang=html4strict>



mobile

+44 7773 000 000

</source>

<source lang=html4strict>


January 6th, in the evening

</source>

It allows you to include machine-form data alongside the human form, without polluting visible formatted content with undesired machine form data.

This covers cases where a microformat uses a fixed format of data that is either inappropriate for visible inclusion in a page (such as a full date-time and timezone string), or where an American-English keyword is needed — such as <code>cell</code> instead of ‘mobile’ in a British English page, or any number of non-English translations.

This pattern is based on rendering behavior in browsers whereby an empty element — that is one containing no text-nodes or other child elements — remains in the DOM tree (for parsing) but is not rendered visibly to a page. This allows an element to be included in the document with a <code>title</code> attribute (as in the example), but ''without'' a tooltip being exposed to users, and without the data being read out by screen readers.

You can use <code>value-title</code> on non-empty elements as well; whatever makes most sense to your publishing scenario. This page is dedicated to the empty-element version though, since that offers up the consumption unknowns.

Based on everything we know up to this point, we believe this pattern will work. But, it's wide ranging and the web is broad, and we want to be sure. Please, help us out testing this pattern proposal. Examples tests are below, please push them or your own variants into publishing systems, content management systems, editor applications and tools. Check that it comes out the other side with the data intact, and exposed (or hidden) as expected: Render it in desktop browsers, mobile browers, screen readers, in braille… ''anything you can test, we want to know about''! We need to see any quirks, oddities and so on.

Also, by all means provide thoughts on the publishing flow for this. An empty element is an uncommon structure outside of forms and scripts, but the reasoning is as follows: ''‘Machine formatted data’ is not metadata, it is content. Therefore, it's structurally appropriate to have it as a sibling to the human-formatted content.''

'''Note that valid HTML is a cornerstone of microformats'''. ''Inventing new attributes, depending on unstable drafts of HTML5, using non-standard DOCTYPEs or XML extensions is not an applicable option''. We're trying to achieve something as gracefully as we can within the limitations of HTML4, and without harming user experience.

==The proposed parsing rules==

The current, likely incomplete, parsing rules and restrictions for this pattern are as follows:

* Only one <code>value-title</code> element may be included as a child of a property. No splitting or concatenation, no combining with other value-excerption elements.
* An empty <code>value-title</code> element '''must''' be the ''first''-child of the property (not including any preceding whitespace). To alleviate the [[value-excerption-pattern-brainstorming#issues_2|negative impact of non-visible data]], the value should be as near as possible to declaring the property.
* The machine-data value ''must'' represent the same data as the visible text; the parent property ''must not'' contain arbitrary data. Validator tools will be encouraged to verify this where possible (for example, some programming languages have access to powerful date parsing algorithms that can compare human dates to the ISO form).
* The empty element can be ''any element'', but a generic <code>span</code> is most appropriate. You could use <code>b</code> if you want to save bytes, or an <code>input type=hidden</code> if it makes sense to you. That choice will not matter to parsers. You are in complete control of that publishing decision. As per usual µf documentation, <code>span</code> will be used for generic examples.
* The <code>value-title</code> property does not have to be empty. If you ''do'' want a tool-tip to expose a useful data-form, you can. e.g. <code>last year</code> is valid too.

==Example Tests==

The following snippets are example tests for the new pattern. You can use them as is, or use them as a base for your own tests with your own content. If you write your own tests, please document them under ‘additional test cases’ so that any failing tests can be checked for validity.

===hAtom#1: An hAtom <code>published</code>/<code>updated</code> Property===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hAtom#1</title>
</head>
<body>
<div class="hentry">
<h1 class="entry-title">An introduction to Microformats</h1>

Published on 

January 9th, around lunchtime
by 
<a class="url fn" href="http://example.com">
Joe Blogger</a>.

Wow, microformats are really useful! You can
learn loads about them on the
<a href="http://microformats.org/wiki">microformats wiki</a>.

</div>
</body>
</html>
</source>

===hCal#1: An hCalendar <code>dtstart</code>===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hCal#1</title>
</head>
<body>
<div class="vevent">
<h1 class="summary">Value Exception Test Day!</h1>
Come help 
<a class="fn url org" href="http://microformats.org">microformats.org</a>
 test a new value-excerption pattern for sanity and
robustness!

Help out by running some tests at


midday on Monday January 12th.

See <a class="url" href="http://microformats.org/wiki/value-excerption-pattern-issues/empty-value-element-test">the
wiki</a> for more details!

</div>
</body>
</html>
</source>

===hCard#1: An hCard <abbr title="birthday"><code>bday</code></abbr>===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hCard#1</title>
</head>
<body>

<div class="vcard">
<h1 class="fn">Ben Ward</h1>
Ben Ward's birthday is


February 9th
.
You should throw him a party! Or call his 
mobile
on 415.123.123 to wish him well!

</div>

</body>
</html>
</source>

===hAudio#1: An hAudio <code>duration</code>===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hAudio#1</title>
</head>
<body>
<h1>Song of the year?</h1>

Did you hear ‘Heavy Water’ on
Foals
‘Antidodes’ record


last year
? It's


4 and a half minutes long
, you should make time to hear it!
</div>

</body>
</html>
</source>

''If you believe there is an error in any of these tests, or in any others that people contribute, please post on the {{MicroformatsMailingList}}.''

==Evil Tests==

If you want to give existing microformat parsers a good run out, construct ‘evil’ tests using nesting, combination and interpolation of different microformats.

===hAtom + hCalendar===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hAtomhCalEvil#1</title>
</head>
<body>
<div class="hentry vevent">
<h1 class="entry-title summary">An introduction to Microformats</h1>

Published on 

January 11th, late afternoon
by 
<a class="url fn" href="http://example.com">
Joe Blogger</a>.




this coming Wednesday at 7
 is not the date of a completely fictional microformats
event. If it existed, it would promise to be informative and get
you up to speed on microformats.org for 2009! Now you've
learned to work with microformats a little, why not attend and
get involved! Why not? Because this event is a test case, not
for real.

</div>
</body>
</html>
</source>

==Response==

* Don't like the empty element? Don't like the use of the title attribute? '''Please file general issues concerning the proposed pattern on the main [[value-excerption-pattern-brainstorming#enabling_more_use_of_title_attributes|value excerption brainstorming page]]''', or discuss them on the {{MicroformatsMailingList}}.
* Add results of tests and responses to these tests themselves on ''this page''.

Misplaced responses will be moved, and having to do so will make [[User:BenWard|Ben]] growly, so, y'know, please try to keep the wiki tidy.

===Successful Tests===

List successfully tested environments here. Add new environments as new list items, and expand existing list items with your name and platform variants to indicate verified successes.

{|
|+ Results of tests across various publishing/rendering environments
|-
! Product
! <abbr title="Publishing or Consuming?">P/C?</abbr>
! Platforms
! Test By
! Notes
|-
| MediaWiki/Linux
| Publishing
| Safari 3.2.1 (Mac OSX 10.5)
| [[User:BenWard]]
| The empty <code>span</code> elements are maintained in <abbr title="MediaWiki">MW</abbr> output. Note that <code>a</code> elements in the tests get escaped by this MediaWiki install.
|-
| Safari 2.0.4
| Consuming
| Mac OSX 10.5
| [[User:GeorgeBrock]]
| No tooltip.
|-
| Safari 3.2.1
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| Empty-span remains in DOM. Web Inspector reports the element has width and height of ‘0px’. No tooltip due to zero-dimensions.
|-
| Firefox 2.0
| Consuming
| Mac OSX 10.5
| [[User:GeorgeBrock]]
| Empty-span remains in DOM. Firebug reports the element has width of '0px' and height of ‘16px’. No tooltip due to zero-width.
|-
| Firefox 3.0
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| Empty-span remains in DOM. Firebug reports the element has width of '0px' and height of ‘16px’. No tooltip due to zero-width.
|-
| Firefox 3.1ß1
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| Empty-span remains in DOM. No tooltip.
|-
| Opera 9.62
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| Empty-span remains in DOM. Dragonfly reports the element has width of '0px' and height of ‘0px’. No tooltip due to zero-dimensions.
|-
| Internet Explorer 5.2
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| No tooltip.
|-
| Internet Explorer 6.0
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:GeorgeBrock]]
| Empty-span remains in DOM (visible to Web Developer Toolbar, accessible from Javascript). No tooltip.
|-
| Internet Explorer 7.0
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:GeorgeBrock]]
| Empty-span remains in DOM (visible to Web Developer Toolbar, accessible from Javascript). No tooltip.
|-
| Internet Explorer 8.0 beta 2
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:GeorgeBrock]]
| Empty-span remains in DOM. Developer Tools (built in to <abbr title="Internet Explorer 8 beta 2">IE8b2</abbr>) report the element has width of '0px' and height of '19px'. No tooltip due to zero-width.
|-
| Firefox 3.0.5
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No tooltip
|-
| Safari 3.2.1
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No tooltip
|-
| Opera 9.6
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No tooltip
|-
| Camino 1.6.5
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No tooltip
|-
| Flock 2.0.2
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No tooltip
|-
| Firefox 3.0.5
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Safari 3.0.3
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Opera 9.6.2
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Flock 2.0.2
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Chrome 1.0.154.43
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Internet Explorer 6
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Internet Explorer 7
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Native BlackBerry browser (BlackBerry mode)
| Consuming
| BlackBerry Storm OS 4.0.7.85 (leaked, non-official OS build from Verizon)
| [[User:EmilyLewis]]
| No tooltip
|-
| MobileSafari 3.2
| Consuming
| iPhone OS 2.2
| [[User:EmilyLewis]]
| No tooltip
|-
| JAWS 10.0.512 (demo mode)
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No voice
|-
| Fire Vox (Firefox 3.0.5)
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No voice
|-
| WebbIE (Thunder 1.43)
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No voice
|-
| VoiceOver (Safari 3.2.1)
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No voice
|-
|}

===Failed Tests===

For failures, please provide as much information as you can. The precise impact of the error, whether the behavior could be regarded as a bug in the software you're testing, whether it works in subsequent releases, whether you changed any settings in the software to produce the result, and if so, whether enabling/disabling that setting should be regarded a showstopper if this pattern were certified.

Since we want more detail, please expand failures into headed sections rather than cramming into a table.

For example, take this entirely plausible scenario as a template:

====Example: Fake Publisher 3.1ß====
; Platform
: Windows Vista
; Test By
: [[User:BenWard]]
; Description
: When trying to enter an empty span in my <abbr title="Hypertext Markup Language">HTML</abbr> editor, which I wrote myself whilst I was high, the application immediately crashes, performs <code>rm -rf /</code> on all UNIX boxes connected to my local network (which also appears to cause Android phones within Bluetooth range to do the same…), and then causes all attached peripherals to combust. I was not able to reproduce, as my house was now on fire. I think using a self closing XHTML tag instead might work-around the problem because as we know, it's been proved by Real Scienticians that XML is always better than HTML. Alternatively, it may be a bug in the beta software.
; Notes
: This is a beta release, and a bug has been filed.
: This product has a known history of flammability bugs.
: The user must explicitly enable the ‘Endanger My Life’ checkbox under the ‘Advanced Mislabelled Checkboxes’ tab of the ‘Complicated Preferences’ preferences pane.
: You get the idea.

====Browser <abbr title="What you see is what you get">WYSIWYG</abbr> editor: [http://tinymce.moxiecode.com/ TinyMCE 3.2.1.1]====
; Platform
: Firefox 3.0 on Mac OSX 10.5
; Test By
: [[User:GeorgeBrock]]
; Description
: Empty spans entered using TinyMCE's source editor are removed when switching back to the default WYSIWYG view.
: This is not a bug with TinyMCE, the editor is designed to remove empty instances of most elements by default. The handling of empty elements can be changed by modifying the [http://wiki.moxiecode.com/index.php/TinyMCE:Configuration/valid_elements valid-elements setting] (e.g. change <code>-span</code> to <code>span</code> and empty spans will no longer be removed), however settings can only be changed by modifying the source code of the page that contains the TinyMCE instance, so it is likely that some users will not be able to apply this fix.
; Notes
: This behaviour can be easily reproduced using the online [http://tinymce.moxiecode.com/examples/full.php TinyMCE examples].
: TinyMCE is the default WYSIWYG editor in WordPress[http://codex.wordpress.org/TinyMCE].
: With a single whitespace character (‘space’), the <code>span</code> is preserved, but yet still seems to collapse in Safari. Will write a follow-up test.--[[User:BenWard|BenWard]] 23:11, 20 January 2009 (UTC)
: You ''can'' publish this pattern using the <code>input type='hidden' class='value-title' title='2009-01-20'</code> hinted above. Semantically odd, although it's been suggested on µf lists before. Publishing workaround exists through element agnosticism. --[[User:BenWard|BenWard]] 23:11, 20 January 2009 (UTC)

====Browser <abbr title="What you see is what you get">WYSIWYG</abbr> editor: [http://www.fckeditor.net/ FCKEditor 2.6.4 Beta]====
; Platform
: Firefox 3.0 on Mac OSX 10.5
; Test By
: [[User:GeorgeBrock]]
; Description
: Empty spans entered using FCKEditor's source editor are removed when switching back to the default WYSIWYG view or submitting the form that contains the FCKEditor instance.
; Notes
: This behaviour can be easily reproduced using the online [http://www.fckeditor.net/demo FCKEditor demo].
: FCKEditor is used by various content management systems, frameworks and applications[http://www.fckeditor.net/whosusing].
: With a single whitespace character (‘space’), the <code>span</code> is preserved, but yet still seems to collapse in Safari. Will write a follow-up test.--[[User:BenWard|BenWard]] 23:12, 20 January 2009 (UTC)
: You ''can'' publish this pattern using the <code>input type='hidden' class='value-title' title='2009-01-20'</code> mentioned above. --[[User:BenWard|BenWard]] 23:12, 20 January 2009 (UTC)
: This issue does not effect FCKEditor instances that use the Placeholders plugin (this plugin comes with FCKEditor, enable it using <code>FCKConfig.Plugins.Add('placeholder')</code>). Examining the Placeholders plugin code may yield an easier work-around than including the plugin (I had a quick look but didn't see anything that was obviously responsible for allowing empty spans) -[[User:GeorgeBrock|GeorgeBrock]] 23:20, 20 January 2009 (UTC)



===General Test Feedback===
<div class='discussion'>
* Any general feedback you have on this test is most welcome. However, if you have issues with the pattern or alternate suggestions, please file them on the main [[value-excerption-pattern-issues]] page. Also, please remember to sign your comments with <nowiki>—~~~~</nowiki> —[[User:BenWard|BenWard]] 00:12, 9 January 2009 (UTC)
* … 
** … 
</div>

==Related Pages==
* [[value-excerption-pattern]]
* [[value-excerption-pattern-issues]]
* [[value-excerption-pattern-brainstorming]]
* [[value-excerption-dt-separation-test]]

value-excerption-value-title-test

2009-01-23T15:27:24Z

EmilyLewis: /* Successful Tests */

<entry-title>Value Excerption Pattern: Parsing 'value' from an empty element</entry-title>
'''This page is targetted at those already experienced with microformats.'''

''Please carefully note, this page is about a pre-draft, experimental and unfinished microformats proposal. You '''cannot''' use this pattern on your live pages, it is '''not supported''' by any stable parser and you should not assume that this pattern will be finalized as-is! We're just asking for help in testing this thoroughly. '''Thank you'''.''
__TOC__
This is a special page to introduce and gather results to widespread testing of a '''proposed''' extension to the value-excerption pattern. See [[value-excerption-pattern-brainstorming#.E2.80.98value-title.E2.80.99|value excerption pattern brainstorming: value-title]] for the specific proposal.

This pattern can be used to resolve some long standing issues with including [[machine-data|machine-data in microformats]]; it's imperative we test thoroughly before adding it to any pattern specification. Following are a number of example tests. ''Please try them out''.

The pattern we're testing looks a little something like this. Those experienced with microformats should immediately see what we're trying to do:

<source lang=html4strict>



mobile

+44 7773 000 000

</source>

<source lang=html4strict>


January 6th, in the evening

</source>

It allows you to include machine-form data alongside the human form, without polluting visible formatted content with undesired machine form data.

This covers cases where a microformat uses a fixed format of data that is either inappropriate for visible inclusion in a page (such as a full date-time and timezone string), or where an American-English keyword is needed — such as <code>cell</code> instead of ‘mobile’ in a British English page, or any number of non-English translations.

This pattern is based on rendering behavior in browsers whereby an empty element — that is one containing no text-nodes or other child elements — remains in the DOM tree (for parsing) but is not rendered visibly to a page. This allows an element to be included in the document with a <code>title</code> attribute (as in the example), but ''without'' a tooltip being exposed to users, and without the data being read out by screen readers.

You can use <code>value-title</code> on non-empty elements as well; whatever makes most sense to your publishing scenario. This page is dedicated to the empty-element version though, since that offers up the consumption unknowns.

Based on everything we know up to this point, we believe this pattern will work. But, it's wide ranging and the web is broad, and we want to be sure. Please, help us out testing this pattern proposal. Examples tests are below, please push them or your own variants into publishing systems, content management systems, editor applications and tools. Check that it comes out the other side with the data intact, and exposed (or hidden) as expected: Render it in desktop browsers, mobile browers, screen readers, in braille… ''anything you can test, we want to know about''! We need to see any quirks, oddities and so on.

Also, by all means provide thoughts on the publishing flow for this. An empty element is an uncommon structure outside of forms and scripts, but the reasoning is as follows: ''‘Machine formatted data’ is not metadata, it is content. Therefore, it's structurally appropriate to have it as a sibling to the human-formatted content.''

'''Note that valid HTML is a cornerstone of microformats'''. ''Inventing new attributes, depending on unstable drafts of HTML5, using non-standard DOCTYPEs or XML extensions is not an applicable option''. We're trying to achieve something as gracefully as we can within the limitations of HTML4, and without harming user experience.

==The proposed parsing rules==

The current, likely incomplete, parsing rules and restrictions for this pattern are as follows:

* Only one <code>value-title</code> element may be included as a child of a property. No splitting or concatenation, no combining with other value-excerption elements.
* An empty <code>value-title</code> element '''must''' be the ''first''-child of the property (not including any preceding whitespace). To alleviate the [[value-excerption-pattern-brainstorming#issues_2|negative impact of non-visible data]], the value should be as near as possible to declaring the property.
* The machine-data value ''must'' represent the same data as the visible text; the parent property ''must not'' contain arbitrary data. Validator tools will be encouraged to verify this where possible (for example, some programming languages have access to powerful date parsing algorithms that can compare human dates to the ISO form).
* The empty element can be ''any element'', but a generic <code>span</code> is most appropriate. You could use <code>b</code> if you want to save bytes, or an <code>input type=hidden</code> if it makes sense to you. That choice will not matter to parsers. You are in complete control of that publishing decision. As per usual µf documentation, <code>span</code> will be used for generic examples.
* The <code>value-title</code> property does not have to be empty. If you ''do'' want a tool-tip to expose a useful data-form, you can. e.g. <code>last year</code> is valid too.

==Example Tests==

The following snippets are example tests for the new pattern. You can use them as is, or use them as a base for your own tests with your own content. If you write your own tests, please document them under ‘additional test cases’ so that any failing tests can be checked for validity.

===hAtom#1: An hAtom <code>published</code>/<code>updated</code> Property===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hAtom#1</title>
</head>
<body>
<div class="hentry">
<h1 class="entry-title">An introduction to Microformats</h1>

Published on 

January 9th, around lunchtime
by 
<a class="url fn" href="http://example.com">
Joe Blogger</a>.

Wow, microformats are really useful! You can
learn loads about them on the
<a href="http://microformats.org/wiki">microformats wiki</a>.

</div>
</body>
</html>
</source>

===hCal#1: An hCalendar <code>dtstart</code>===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hCal#1</title>
</head>
<body>
<div class="vevent">
<h1 class="summary">Value Exception Test Day!</h1>
Come help 
<a class="fn url org" href="http://microformats.org">microformats.org</a>
 test a new value-excerption pattern for sanity and
robustness!

Help out by running some tests at


midday on Monday January 12th.

See <a class="url" href="http://microformats.org/wiki/value-excerption-pattern-issues/empty-value-element-test">the
wiki</a> for more details!

</div>
</body>
</html>
</source>

===hCard#1: An hCard <abbr title="birthday"><code>bday</code></abbr>===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hCard#1</title>
</head>
<body>

<div class="vcard">
<h1 class="fn">Ben Ward</h1>
Ben Ward's birthday is


February 9th
.
You should throw him a party! Or call his 
mobile
on 415.123.123 to wish him well!

</div>

</body>
</html>
</source>

===hAudio#1: An hAudio <code>duration</code>===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hAudio#1</title>
</head>
<body>
<h1>Song of the year?</h1>

Did you hear ‘Heavy Water’ on
Foals
‘Antidodes’ record


last year
? It's


4 and a half minutes long
, you should make time to hear it!
</div>

</body>
</html>
</source>

''If you believe there is an error in any of these tests, or in any others that people contribute, please post on the {{MicroformatsMailingList}}.''

==Evil Tests==

If you want to give existing microformat parsers a good run out, construct ‘evil’ tests using nesting, combination and interpolation of different microformats.

===hAtom + hCalendar===

<source lang=html4strict>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<title>Value Excerption Pattern Test hAtomhCalEvil#1</title>
</head>
<body>
<div class="hentry vevent">
<h1 class="entry-title summary">An introduction to Microformats</h1>

Published on 

January 11th, late afternoon
by 
<a class="url fn" href="http://example.com">
Joe Blogger</a>.




this coming Wednesday at 7
 is not the date of a completely fictional microformats
event. If it existed, it would promise to be informative and get
you up to speed on microformats.org for 2009! Now you've
learned to work with microformats a little, why not attend and
get involved! Why not? Because this event is a test case, not
for real.

</div>
</body>
</html>
</source>

==Response==

* Don't like the empty element? Don't like the use of the title attribute? '''Please file general issues concerning the proposed pattern on the main [[value-excerption-pattern-brainstorming#enabling_more_use_of_title_attributes|value excerption brainstorming page]]''', or discuss them on the {{MicroformatsMailingList}}.
* Add results of tests and responses to these tests themselves on ''this page''.

Misplaced responses will be moved, and having to do so will make [[User:BenWard|Ben]] growly, so, y'know, please try to keep the wiki tidy.

===Successful Tests===

List successfully tested environments here. Add new environments as new list items, and expand existing list items with your name and platform variants to indicate verified successes.

{|
|+ Results of tests across various publishing/rendering environments
|-
! Product
! <abbr title="Publishing or Consuming?">P/C?</abbr>
! Platforms
! Test By
! Notes
|-
| MediaWiki/Linux
| Publishing
| Safari 3.2.1 (Mac OSX 10.5)
| [[User:BenWard]]
| The empty <code>span</code> elements are maintained in <abbr title="MediaWiki">MW</abbr> output. Note that <code>a</code> elements in the tests get escaped by this MediaWiki install.
|-
| Safari 2.0.4
| Consuming
| Mac OSX 10.5
| [[User:GeorgeBrock]]
| No tooltip.
|-
| Safari 3.2.1
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| Empty-span remains in DOM. Web Inspector reports the element has width and height of ‘0px’. No tooltip due to zero-dimensions.
|-
| Firefox 2.0
| Consuming
| Mac OSX 10.5
| [[User:GeorgeBrock]]
| Empty-span remains in DOM. Firebug reports the element has width of '0px' and height of ‘16px’. No tooltip due to zero-width.
|-
| Firefox 3.0
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| Empty-span remains in DOM. Firebug reports the element has width of '0px' and height of ‘16px’. No tooltip due to zero-width.
|-
| Firefox 3.1ß1
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| Empty-span remains in DOM. No tooltip.
|-
| Opera 9.62
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| Empty-span remains in DOM. Dragonfly reports the element has width of '0px' and height of ‘0px’. No tooltip due to zero-dimensions.
|-
| Internet Explorer 5.2
| Consuming
| Mac OSX 10.5,
| [[User:BenWard]]
| No tooltip.
|-
| Internet Explorer 6.0
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:GeorgeBrock]]
| Empty-span remains in DOM (visible to Web Developer Toolbar, accessible from Javascript). No tooltip.
|-
| Internet Explorer 7.0
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:GeorgeBrock]]
| Empty-span remains in DOM (visible to Web Developer Toolbar, accessible from Javascript). No tooltip.
|-
| Internet Explorer 8.0 beta 2
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:GeorgeBrock]]
| Empty-span remains in DOM. Developer Tools (built in to <abbr title="Internet Explorer 8 beta 2">IE8b2</abbr>) report the element has width of '0px' and height of '19px'. No tooltip due to zero-width.
|-
| Firefox 3.0.5
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No tooltip
|-
| Safari 3.2.1
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No tooltip
|-
| Opera 9.6
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No tooltip
|-
| Camino 1.6.5
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No tooltip
|-
| Flock 2.0.2
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No tooltip
|-
| Firefox 3.0.5
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Safari 3.0.3
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Opera 9.6.2
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Flock 2.0.2
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Chrome 1.0.154.43
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Internet Explorer 6
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Internet Explorer 7
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No tooltip
|-
| Native BlackBerry browser (BlackBerry mode)
| Consuming
| BlackBerry Storm OS 4.0.7.85 (leaked, non-official OS build from Verizon)
| [[User:EmilyLewis]]
| No tooltip
|-
| JAWS 10.0.512 (demo mode)
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No voice
|-
| Fire Vox (Firefox 3.0.5)
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No voice
|-
| WebbIE (Thunder 1.43)
| Consuming
| Windows XP (<abbr title="Service Pack 3">SP3</abbr>)
| [[User:EmilyLewis]]
| No voice
|-
| VoiceOver (Safari 3.2.1)
| Consuming
| Mac OSX 10.5.6
| [[User:EmilyLewis]]
| No voice
|-
|}

===Failed Tests===

For failures, please provide as much information as you can. The precise impact of the error, whether the behavior could be regarded as a bug in the software you're testing, whether it works in subsequent releases, whether you changed any settings in the software to produce the result, and if so, whether enabling/disabling that setting should be regarded a showstopper if this pattern were certified.

Since we want more detail, please expand failures into headed sections rather than cramming into a table.

For example, take this entirely plausible scenario as a template:

====Example: Fake Publisher 3.1ß====
; Platform
: Windows Vista
; Test By
: [[User:BenWard]]
; Description
: When trying to enter an empty span in my <abbr title="Hypertext Markup Language">HTML</abbr> editor, which I wrote myself whilst I was high, the application immediately crashes, performs <code>rm -rf /</code> on all UNIX boxes connected to my local network (which also appears to cause Android phones within Bluetooth range to do the same…), and then causes all attached peripherals to combust. I was not able to reproduce, as my house was now on fire. I think using a self closing XHTML tag instead might work-around the problem because as we know, it's been proved by Real Scienticians that XML is always better than HTML. Alternatively, it may be a bug in the beta software.
; Notes
: This is a beta release, and a bug has been filed.
: This product has a known history of flammability bugs.
: The user must explicitly enable the ‘Endanger My Life’ checkbox under the ‘Advanced Mislabelled Checkboxes’ tab of the ‘Complicated Preferences’ preferences pane.
: You get the idea.

====Browser <abbr title="What you see is what you get">WYSIWYG</abbr> editor: [http://tinymce.moxiecode.com/ TinyMCE 3.2.1.1]====
; Platform
: Firefox 3.0 on Mac OSX 10.5
; Test By
: [[User:GeorgeBrock]]
; Description
: Empty spans entered using TinyMCE's source editor are removed when switching back to the default WYSIWYG view.
: This is not a bug with TinyMCE, the editor is designed to remove empty instances of most elements by default. The handling of empty elements can be changed by modifying the [http://wiki.moxiecode.com/index.php/TinyMCE:Configuration/valid_elements valid-elements setting] (e.g. change <code>-span</code> to <code>span</code> and empty spans will no longer be removed), however settings can only be changed by modifying the source code of the page that contains the TinyMCE instance, so it is likely that some users will not be able to apply this fix.
; Notes
: This behaviour can be easily reproduced using the online [http://tinymce.moxiecode.com/examples/full.php TinyMCE examples].
: TinyMCE is the default WYSIWYG editor in WordPress[http://codex.wordpress.org/TinyMCE].
: With a single whitespace character (‘space’), the <code>span</code> is preserved, but yet still seems to collapse in Safari. Will write a follow-up test.--[[User:BenWard|BenWard]] 23:11, 20 January 2009 (UTC)
: You ''can'' publish this pattern using the <code>input type='hidden' class='value-title' title='2009-01-20'</code> hinted above. Semantically odd, although it's been suggested on µf lists before. Publishing workaround exists through element agnosticism. --[[User:BenWard|BenWard]] 23:11, 20 January 2009 (UTC)

====Browser <abbr title="What you see is what you get">WYSIWYG</abbr> editor: [http://www.fckeditor.net/ FCKEditor 2.6.4 Beta]====
; Platform
: Firefox 3.0 on Mac OSX 10.5
; Test By
: [[User:GeorgeBrock]]
; Description
: Empty spans entered using FCKEditor's source editor are removed when switching back to the default WYSIWYG view or submitting the form that contains the FCKEditor instance.
; Notes
: This behaviour can be easily reproduced using the online [http://www.fckeditor.net/demo FCKEditor demo].
: FCKEditor is used by various content management systems, frameworks and applications[http://www.fckeditor.net/whosusing].
: With a single whitespace character (‘space’), the <code>span</code> is preserved, but yet still seems to collapse in Safari. Will write a follow-up test.--[[User:BenWard|BenWard]] 23:12, 20 January 2009 (UTC)
: You ''can'' publish this pattern using the <code>input type='hidden' class='value-title' title='2009-01-20'</code> mentioned above. --[[User:BenWard|BenWard]] 23:12, 20 January 2009 (UTC)
: This issue does not effect FCKEditor instances that use the Placeholders plugin (this plugin comes with FCKEditor, enable it using <code>FCKConfig.Plugins.Add('placeholder')</code>). Examining the Placeholders plugin code may yield an easier work-around than including the plugin (I had a quick look but didn't see anything that was obviously responsible for allowing empty spans) -[[User:GeorgeBrock|GeorgeBrock]] 23:20, 20 January 2009 (UTC)



===General Test Feedback===
<div class='discussion'>
* Any general feedback you have on this test is most welcome. However, if you have issues with the pattern or alternate suggestions, please file them on the main [[value-excerption-pattern-issues]] page. Also, please remember to sign your comments with <nowiki>—~~~~</nowiki> —[[User:BenWard|BenWard]] 00:12, 9 January 2009 (UTC)
* … 
** … 
</div>

==Related Pages==
* [[value-excerption-pattern]]
* [[value-excerption-pattern-issues]]
* [[value-excerption-pattern-brainstorming]]
* [[value-excerption-dt-separation-test]]

User:EmilyLewis

2009-01-23T15:26:32Z

EmilyLewis: New page: I am a front-end developer living in Albuquerque, New Mexico. ==Contact== * Blog: http://www.ablognotlimited.com/ * Email: emily at ablognotlimited dot com * Twitter: [http://twitter.co...

I am a front-end developer living in Albuquerque, New Mexico.

==Contact==

* Blog: http://www.ablognotlimited.com/
* Email: emily at ablognotlimited dot com
* Twitter: [http://twitter.com/emilylewis @emilylewis]

articles

2008-11-20T17:05:56Z

EmilyLewis: /* 2008 */

<h1>Articles</h1>
{{TOC-right}}



== 2008 ==
*2008-11-20: <cite class="entry-title">Getting Semantic With Microformats, Part 7: Themes & Issues</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-7-themes-and-issues/

*2008-11-10: <cite class="entry-title">Getting Semantic With Microformats, Part 6: hResume</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-6-hresume/

*2008-10-15: <cite class="entry-title">Getting Semantic With Microformats, Part 5: hAtom</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-5-hatom/

*2008-10-01: <cite class="entry-title">Getting Semantic With Microformats, Part 4: hCalendar</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-4-hcalendar/

*2008-09-22: <cite class="entry-title">Getting Semantic With Microformats, Part 3: hCard</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-3-hcard/

*2008-09-17: <cite class="entry-title">Getting Semantic With Microformats, Part 2: XFN</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-2-xfn/

*2008-09-09: <cite class="entry-title">Getting Semantic With Microformats, Part 1: rel</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-1-rel/

*2008-09-05: <cite class="entry-title">Getting Semantic With Microformats, Introduction</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-introduction/

*2008-02-21: ''<cite class="entry-title">XFN encoding, extraction, and visualizations</cite>'' by Brian Suda: http://dev.opera.com/articles/view/xfn-encoding-extraction-and-visualizat/

*2008-02-21: ''Microformats : comment microformater du contenu déjà existant ?'' by Thomas Parisot: http://www.clever-age.com/veille/blog/microformats-comment-microformater-du-contenu-deja-existant.html

*2008-01-24: ''Microformats introduction to content and user experience'' by Sarven Capadisli: http://www.csarven.ca/microformats-introduction

*2008-01-11: ''Microformats : republier et donner du sens aux contenus'' by Thomas Parisot: http://www.clever-age.com/veille/blog/microformats-republier-et-donner-du-sens-aux-contenus.html

== 2007 ==

*2007-12-05: ''The Magical Minimalism of Microformats'' by Jacob Harris in The New York Times blog: http://open.blogs.nytimes.com/2007/12/05/the-magical-minimalism-of-microformats/

*2007-11-21: ''Portable Social Networks: Take Your Friends with You'' by Brian Suda: http://www.sitepoint.com/article/social-networks-take-friends/

*2007-07-24: ''Microformats: More Meaning from Your Markup'' by Brian Suda: http://www.sitepoint.com/article/microformats-meaning-markup

==2006==

*2006-04-02: ''Blog Business Summit: Microformats in Plain English: the Promise of Simple Business to Business Data Exchange'' by Steve Broback: http://blogbusinesssummit.com/2006/04/microformats_in.htm

*2006-01-29: ''How Microformats Affect Seearch Engine Optimization'' by Shaun Shull: http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo

*2006-01-27: ''Introduction to hCard'' by Jesse Skinner: http://www.thefutureoftheweb.com/blog/2006/1/hcard

==2005==

*2005-12-06: ''Practical Microformats with hCard'' by Drew McLellan: http://24ways.org/advent/practical-microformats-with-hcard

*2005-11-17: ''An Extra SIDE to Web Standards Based Design - How Semantic Information Design Ethics (SIDE) and a few readily available techniques can help heal the Web'' by Jon Tan: http://www.gr0w.com/articles/design/an_extra_side_to_web_standards_based_design/
**See also his [http://www.csszengarden.com/?cssfile=/193/193.css&page=0 CSS Zen Garden "Leggo my ego" entry].

*2005-11-14: ''Microformats Primer'' by Garrett Dimon in Digital Web Magazine: http://www.digital-web.com/articles/microformats_primer/

*2005-07-24: ''Usable Microformats'' by Andrew D. Hume: http://usabletype.com/weblog/usable-microformats/

*2005-06-03: ''Introducing microformats'' by Andrew D. Hume: http://thedredge.org/2005/07/introducing-microformats/

== Miscellaneous Reference ==

These are various intro-related links/articles which we haven't figured out yet how to incorporate. You may find them of interest.

* [http://www.betaversion.org/~stefano/linotype/news/93/ Data First vs. Structure First]
** [http://tantek.com/log/ Tantek] says: In many ways it is actually *far* worse than that post conveys. The "typical" programmer literally loves spending far more time worrying about and designing the structure for structure's sake, than data, and even less so, "real world" data (current behaviors etc.). Hence we have taken the directly opposite tack with microformats when looking to solve a problem.
*** Zeroeth, define the real-world problem. If you can't do this, then stop.
*** First, look at real-world usage (data).
*** Second, what previous standards are people actually using today? If there is more than one, then lean towards those with the better adoption.
***And only after those first two do we bother to pay attention to theoretical standards, those that have been invented (whether by individuals, committees), but haven't seen much if any actual adoption.
* [http://lists.w3.org/Archives/Public/www-rdf-interest/2000Mar/0103 2000-03-21 Dan Connolly on human-consumable information]: ('''strong emphasis''' added)
** I believe that one of the best ways to transition into RDF, if not a long-term deployment strategy for RDF, is to '''manage the information in human-consumable form (XHTML) annotated with just enough info to extract''' the RDF statements that the human info is intended to convey. In other words: using a relational database or some sort of native RDF data store, and spitting out HTML dynamically, is a lot of infrastructure to operate and probably not worth it for lots of interesting cases. '''We all know that we have to produce a human-readable version of the thing... why not use that as the primary source?'''

== See Also ==
* [[press]]

hatom

2008-11-17T15:19:17Z

EmilyLewis: Added Further Reading section with link to hResume blog post

<entry-title>hAtom 0.1</entry-title>
{{Template:DraftSpecification}}

hAtom is a microformat for content that can be syndicated, primarily but not exclusively weblog postings. hAtom is based on a subset of the [http://www.atomenabled.org/ Atom] syndication format. hAtom will be one of several [[microformats]] open standards.
__TOC__
== Draft Specification ==

;Editor/Author
:[http://blogmatrix.blogmatrix.com/ David Janes] ([http://www.blogmatrix.com BlogMatrix, Inc.])

;Contributors
:[http://members.optusnet.com.au/benjamincarlyle/benjamin/blog/ Benjamin Carlyle]
:[http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc.])

=== Copyright ===
{{MicroFormatCopyrightStatement2005}}
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.
** When all authors/editors have done so, we can remove the MicroFormatCopyrightStatement template reference and replace it with the MicroFormatPublicDomainContributionStatement.

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

== Introduction ==

hAtom is a [[microformat]] for identifying semantic information in weblog posts and practically any other place [http://www.atomenabled.org/ Atom] may be used, such as news articles. hAtom content is easily added to most blogs by simple modifications to the blog's template definitions.

{{rfc-2119-intro}}

== Semantic XHTML Design Principles ==
{{semantic-xhtml-design-principles}}

== Format ==
=== In General ===
The [http://atomenabled.org/developers/syndication/#person Atom Syndication Format] provides the conceptual basis for this microformat, with the following caveats:

* Atom provides a lot more functionality than we need for a "blog post" microformat, so we've taken the minimal number of elements needed.
* the "logical" model of hAtom is that of Atom. If there is a conflict, Atom should be taken as correct.
* the "physical" model of hAtom -- the actual writing of elements -- is a lot more varied than Atom provides for, due to the variety of ways weblogs are actually produced in the wild. The hAtom microformat provides a number of rules for "bridging the gap"

=== Schema ===
Schema elements are based on the Atom nomenclature and follow the microformat pattern of prefixing a unique identifier (in this case, '<code>h</code>') on the outermost container elements -- the Feed or Entry. The parts of this microformat are based on analysis of many weblog, bulletin board and media posts and can be read [[blog-post-brainstorming#Discovered_Elements]].

The hAtom schema consists of the following:

* hfeed ('''<code>hfeed</code>'''). optional.
** '''<code>feed category</code>'''. optional. keywords or phrases, using '''[[rel-tag]]'''.
** hentry ('''<code>hentry</code>''').
*** '''<code>entry-title</code>'''. required. text.
*** '''<code>entry-content</code>'''. optional (see field description). text. [*]
*** '''<code>entry-summary</code>'''. optional. text.
*** '''<code>updated</code>'''. required using [[datetime-design-pattern]]. [*]
*** '''<code>published</code>'''. optional using [[datetime-design-pattern]].
*** '''<code>author</code>'''. required using '''[[hcard|hCard]]'''. [*]
*** '''<code>bookmark</code>''' (permalink). optional, using '''[[rel-bookmark]]'''.
*** tags. optional. keywords or phrases, using '''[[rel-tag]]'''.

[*] Some required elements have defaults if missing, see below.

=== Field and Element Details ===

===== Feed =====
* a Feed element is identified by the class name <code>hfeed</code>
* a Feed element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.1.1 Atom feed]
* the Feed element is optional and, if missing, is assumed to be the page
* hAtom documents {{may}} have multiple Feed elements

===== Feed Category =====
* a Feed Category element is identified by [[rel-tag]]
* a Feed {{may}} have a Feed Category
* a Feed Category element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.2 Atom category] inside a [http://www.atomenabled.org/developers/syndication/#optionalFeedElements feed]
* Feed Category elements {{must}} appear inside a Feed element but not inside an Entry element
* the [[rel-tag]] <code>href</code> encodes the atom <code>category:term</code>; the link text defines the atom <code>category:label</code>

===== Entry =====
* an Entry element is identified by class name <code>hentry</code>
* an Entry element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.1.2 Atom entry]
* any microformat content inside a <code><blockquote></code> or <code><q></code> element within the Entry should not be considered part of the Entry.
: ''This allows quoting other microformated data without worry of corrupting the model''

===== Entry Category =====
* an Entry Category element is identified by [[rel-tag]]
* an Entry {{may}} have an Entry Category
* an Entry Category element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.2 Atom category] inside an [http://www.atomenabled.org/developers/syndication/#optionalEntryElements entry]
* the [[rel-tag]] <code>href</code> encodes the atom <code>category:term</code>; the link text defines the atom <code>category:label</code>

===== Entry Title =====
* an Entry Title element is identified by the class name <code>entry-title</code>
* an Entry {{should}} have an Entry Title
* an Entry Title element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.14 Atom entry title]
* if the Entry Title is missing, use
** the first <code><h#></code> element in the Entry, or
** the <code><title></code> of the page, if there is no enclosing Feed element, or
** assume it is the empty string

===== Entry Content =====
* an Entry Content element is identified by class name <code>entry-content</code>
* an Entry {{should}} have Entry Content
* an Entry Content element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#atomContent Atom content]
* an Entry {{may}} have 0 or more Entry Content elements. The "logical Entry Content" of an Entry is the concatenation, in order of appearance, of all the Entry Contents within the Entry
: ''Many web logs split content into multiple sections with a "Read More" link and JavaScript tricks. This is also needed in cases where Entry Titles are coded in-line and are considered part of the content.''
* if the Entry Content is missing, assume it is the empty string

===== Entry Summary =====
* an Entry Summary element is identified by class name <code>entry-summary</code>
* an Entry Summary element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.13 Atom summary]
* an Entry {{may}} have 0 or more Entry Summary elements. The "logical Entry Summary" of an Entry is the concatenation, in order of appearance, of all the Entry Summarys within the Entry

===== Entry Permalink =====
* an Entry Permalink element is identified by [[rel-bookmark]]
* an Entry {{should}} have an Entry Permalink
* an Entry Permalink element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.7 Atom link in an entry]
* if the Entry Permalink is missing, use the URI of the page; if the Entry has an "id" attribute, add that as a fragment to the page URI to distinguish individual entries

===== Entry Updated =====
* an Entry Updated element is identified by class name <code>updated</code>
* an Entry Updated element represents the concept of [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.15 Atom updated]
* an Entry {{should}} have an Entry Updated element
* use the [[datetime-design-pattern]] to encode the updated datetime
* if there is no Entry Updated element,
** use the Entry Published element, if present
** otherwise the page is invalid hAtom

===== Entry Published =====
* an Entry Published element is identified by the class name <code>published</code>
* an Entry Published element represents the concept of [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.9 Atom published]
* use the [[datetime-design-pattern]] to encode the published datetime

===== Entry Author =====
* an Entry Author element is represented by class name <code>author</code>
* an Entry Author element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.1 Atom author]
* an Entry Author element {{must}} be encoded in an [[hcard|hCard]]
* an Entry Author element {{should}} be encoded in an <code><address></code> element
* an Entry {{should}} have at least one Entry Author element
* an Entry {{may}} have more than one Entry Author elements
* if the Entry Author is missing
** find the [[algorithm-nearest-in-parent|Nearest In Parent]] <code><address></code> element(s) with class name <code>author</code> and that is/are a valid [[hcard|hCard]]
** otherwise the entry is invalid hAtom

=== XMDP Profile ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hfeed</dt>
<dd>
The concept of atom:feed from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>hentry</dt>
<dd>
The concept of atom:entry from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>entry-title</dt>
<dd>
The concept of atom:title inside of an atom:entry from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>entry-content</dt>
<dd>
The concept of atom:content from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>entry-summary</dt>
<dd>
The concept of atom:summary from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>bookmark</dt>
<dd>
The concept of atom:link (without any "rel") with an atom:entry from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>published</dt>
<dd>
The concept of atom:published from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>updated</dt>
<dd>
The concept of atom:updated from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>author</dt>
<dd>
The concept of atom:author from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
</dl>
</dd>
</dl>
</pre>

== Examples ==

See [[hatom-examples]].

=== Examples in the wild ===

See [[hatom-examples-in-wild]].

== Implementations ==

This section is '''informative'''.

The following implementations have been developed which either generate or parse hAtom links. If you have an hAtom 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.

* [http://spinn3r.com/opensource.php Spinn3r Open Source] - implemented in [http://spinn3r.com Spinn3r] and part of [http://code.tailrank.com/feedparser FeedParser] and our announcement of [http://blog.spinn3r.com/2008/01/announcing-spin.html hAtom in Spinn3r 2.1]
* the [http://tools.blogmatrix.com/extract/ Almost Universal Microformat Parser] can extract hAtom content from webpages ([http://tools.blogmatrix.com/extract/?uri=http%3A%2F%2Fblog.davidjanes.com&microformat=hatom&submit=Submit example])
* [http://rbach.priv.at/hAtom2Atom/ hAtom2Atom.xsl] transforms hAtom to Atom (as the name suggests.)
* There is now an [http://www.lukearno.com/projects/hatom2atom/ hatom2atom proxy] that uses hAtom2Atom.xsl.
* [http://placenamehere.com/article/185/SubscribingTohAtomFeedsWithNetNewsWire Subscribe To hAtom] is a script that provides [http://ranchero.com/netnewswire/ NetNewsWire 2.x] users with the ability to subscribe to hAtom documents as they would any other feed. by [[User:ChrisCasciano|Chris Casciano]].
* [http://boxtheweb.mihopa.net/code/apis/#outlineclasses Outline Classes] - has GPL'ed PHP code for reading hAtom
* [http://boxtheweb.4x2.net/ BoxtheWeb] - supports subscribing to hAtom as a feed format
* There is a [http://code.google.com/p/transformr/downloads/list hAtom toolkit] that extracts hAtom, there is also a [http://transformr.co.uk/ demo here]


== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.ietf.org/rfc/rfc4287 RFC4287: The Atom Syndication Format]
* [[hcard-parsing]]
* [[rfc-2119|RFC 2119]]
* [[iso-8601|ISO8601]]

=== Informative References ===
* [http://www.atomenabled.org/ atomenabled.org]

== Further Reading ==
* [http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-5-hatom/ Getting Semantic With Microformats, Part 5: hAtom] by [http://www.ablognotlimited.com/ Emily Lewis]

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. There is a separate document where we are keeping our brainstorms and other explorations relating to hAtom:

* [[blog-post-brainstorming|blog-post Brainstorming]]

=== Version 0.1 ===

Version 0.1 was released 28 February 2006.

== Discussions ==

* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

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

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

==See Also==
{{hatom-related-pages}}
* [[rel-enclosure]] - how to semantically reference enclosures (e.g. podcasts) in hAtom
* [[blog-post-brainstorming]]
* [[blog-post-formats]]
* [[blog-post-examples]]
* [[blog-post-feed-equivalence]]
* [[blog-description-format]] - how to describe a blog (as opposed to the individual entries, which is what we're doing here)
* [[xhtml-syndication]]

[[Category:Draft Specifications]]
[[Category:hAtom]]

hresume

2008-11-17T15:16:46Z

EmilyLewis: /* Further Reading */

<entry-title>hResume</entry-title>
{{DraftSpecification}}
__TOC__
hResume is a microformat for publishing resumes and CVs. hResume is one of several open microformat standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.

Want to get started with writing an hResume? Use the [http://hresume.weblogswork.com/hresumecreator/ hResume Creator] to create your hResume and publish it, or follow the hResume authoring tips to add hResume markup to your web page or blog.

==Microformats Draft Specification==

; 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.

{{rfc-2119-intro}}

== 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. {{must}} use [[hcard|hCard]]; {{should}} use <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 in an [[hCard]]; {{should}} use <code class="element"><address></code> with [[hCard]] when possible.
* '''<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="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.

=== XMDP Profile ===
* [[hresume-profile]] (@TODO)

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

*...

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

<pre><nowiki>

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...

</nowiki></pre>

=== Contact ===
<pre><nowiki>
<address class="vcard">
Pedro Sanchez

123 Fake St.
Preston, Idaho 83263

Email: <a class="email" href="mailto:joe@example.com">pedro@vote-for-pedro.com</a>
Homepage: <a class="url" href="http://vote-for-pedro.com/">vote-for-pedro.com</a>
Phone: +01.208.555.4567
</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">
President,
Preston High School,
<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 one or more [[hcard|hCard]]s. hCard requires the <code class="class-name">fn</code> ("formatted name") field, but it isn't customary 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.

Currently, the recommended way to reference includes within microformats is to use a hyperlink with class="include". See [[include-pattern|include-pattern]] for details.

For example, this hCard refers to another hCard:

Using <code><a></code>:
<pre>

<a href="#pedro-name" class="include" title="Pedro Sanchez"></a>
Preston High School
Class President

</pre>

Using <code><object></code>:
<pre>

<object data="#pedro-name" class="include"></object>
Preston High School
Class President

</pre>

Where "<code class="attr-value">pedro-name</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">

Pedro
Sanchez

</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 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>
National Honor Society
</nowiki></pre>

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

== Examples in the wild ==
See [[hresume-examples-in-wild]]

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

The following implementations have been developed which either generate or parse hResumes. If you have an hResume 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.

* [[Resume.app]]

* [http://linkedin.com LinkedIn] generates hResume for all Public Profiles. [http://www.linkedin.com/in/steveganz LinkedIn Public Profile Example].

* [http://www.antix.co.uk Anthony Johnston] has implemented hResume (Creation and Import) in the [http://cv.antix.co.uk Antix CV Builder], an example resume using this site can be found [http://cv.antix.co.uk/ant here]
** The example resume is ''invalid''; job titles are marked with an hCard that is missing a "fn" (either directly or via object). --[[User:Gazza|Gazza]] 04:23, 1 May 2007 (PDT)
*** This is fixed now --[[User:Antix|Ant]] 00:38, 8 Dec 2007 (GMT)

* The [http://spurinc.com Spur] team has created an hResume WordPress plugin located at [http://hresume.weblogswork.com/?page_id=3 hResume Plugin]. See an example of the hResume markup [http://hresume.weblogswork.com/?page_id=6 here]. Neat feature of the hResume plugin is that it automatically creates a new page for the resume - no cutting and pasting...

* The [http://www.ssdesigninteractive.com/ssdesign Sajid Saiyed] has created an hResume WordPress plugin located at [http://www.ssdesigninteractive.com/ssdesign/?p=96 Microformat Resume Plugin]. See an example of the hResume markup [http://www.ssdesigninteractive.com/ssdesign/?page_id=95 here].

* Spur also created a standalone hResume Creator located at [http://hresume.weblogswork.com/hresumecreator/ hResume Creator]. The creator will generate hResume markup ready to cut and paste into your webpage.

== Copyright ==
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.
* [[RyanKing]]: I release all of my contributions to the public domain.

Per the above, and the public domain release on the author, [[User:RyanKing|RyanKing]]'s, user page this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

== References ==
=== Normative References ===
* [[hcard|hCard]]
* [[hcalendar|hCalendar]]
* [[include-pattern|include pattern]]
* [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]]
* [[rfc-2119]]
* @TODO

=== Informative References ===
* @TODO

== 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])

== Related Pages ==
{{hresume-related-pages}}

== Further Reading ==
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].
* [http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-6-hresume/ Getting Semantic With Microformats, Part 6: hResume] by [http://www.ablognotlimited.com/ Emily Lewis]

[[Category:Draft Specifications]]
[[Category:hResume]]

hcalendar

2008-11-17T15:14:04Z

EmilyLewis: /* Further Reading */

<entry-title>hCalendar</entry-title>

hCalendar is a simple, open, distributed calendaring and events format, based on the iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]), suitable for embedding in HTML or XHTML, Atom, RSS, and arbitrary XML. hCalendar is one of several open [[microformats|microformat]] standards.

Want to get started with writing an [[hcalendar|hCalendar]] event? Use the [http://microformats.org/code/hcalendar/creator hCalendar creator] to write up an event and publish it, or follow the [[hcalendar-authoring|hCalendar authoring tips]] to add hCalendar markup to your page of upcoming events or events you mention in blog posts, wikis, etc.

__TOC__

== Specification ==

; Editor : [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc])
; Authors : [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc])
: [http://suda.co.uk/ Brian Suda]

=== Copyright ===
Per the public domain release on the authors' user pages ([[User:Tantek|Tantek Çelik]], [[User:Brian|Brian Suda]]) this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

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

=== Inspiration and Acknowledgments ===
Thanks to:
* Adam Bosworth for leading the [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation] which brought together a critical mass of interested parties.

== Introduction ==
The iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]), has been broadly interoperably implemented (e.g. Apple's "iCal" application built into MacOSX).

In addition, bloggers often discuss events on their blogs -- upcoming events, writeups of past events, etc. With just a tad bit of structure, bloggers can discuss events in their blog(s) in such a way that spiders and other aggregators can retrieve such events, automatically convert them to iCalendar, and use them in any iCalendar application or service.

This specification introduces the '''hCalendar''' format, which is a 1:1 representation of the aforementioned iCalendar standard, in semantic HTML. Bloggers can both embed hCalendar events directly in their web pages, and style them with CSS to make them appear as desired. In addition, hCalendar enables applications to retrieve information about such events directly from web pages without having to reference a separate file.

{{rfc-2119-intro}}

== Semantic XHTML Design Principles ==

{{semantic-xhtml-design-principles}}

For practical implementations, it should be noted that Internet Explorer's support for styling <code><nowiki><abbr></nowiki></code> elements is poor, and may require wrapper elements.

== Format ==
=== In General ===
The iCalendar standard ([http://www.ietf.org/rfc/rfc2445.txt RFC2445]) forms the basis of hCalendar.

Note: the editor and authors of this specification are tracking the [http://lists.osafoundation.org/pipermail/ietf-calsify/ "iCal-Basic" effort] and intend to base the core hCalendar profile on iCal-Basic. See references for a link to the current draft.

The basic format of hCalendar is to use iCalendar object/property names in lower-case for class names, and to map the nesting of iCalendar objects directly into nested XHTML elements.

=== Root Class Name ===
The root class name for hCalendar is "vcalendar". An element with a class name of "vcalendar" is itself called an ''hCalendar''.

The root class name for events is "vevent". An element with a class name of "vevent" is itself called an ''hCalendar event''.

For authoring convenience, both "vevent" and "vcalendar" are treated as root class names for parsing purposes. If a document contains elements with class name "vevent" but not "vcalendar", the entire document has an implied "vcalendar" context.

'''vevent''' should be considered required for each event listing.

=== Properties and Sub-properties ===
The properties of an hCalendar are represented by elements inside the hCalendar. Elements with class names of the listed properties represent the values of those properties. Some properties have sub-properties, and those are represented by elements inside the elements for properties.

=== Property List ===
hCalendar properties (sub-properties in parentheses like this)

'''Required:'''
* '''dtstart''' ([[iso-8601|ISO date]])
* '''summary'''
Optional:
* location
* url
* dtend (ISO date), duration (ISO date duration)
* rdate, rrule
* category, description
* uid
* geo (latitude, longitude)
* ... editor's note: this list is incomplete (an incomplete list is better than no list) and is being currently edited from RFC2445 to here. The above list of properties are those that are most commonly used for hCalendar.

=== More Semantic Equivalents ===
For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:
* <code>URL</code> in iCalendar becomes <code><a class="url" href="...">...</a></code> inside the element with <code>class="vevent"</code> in hCalendar.
* <code>ATTENDEE</code>, <code>CONTACT</code>, and <code>ORGANIZER</code> in iCalendar {{may}} be represented by an [[hcard|hCard]] in hCalendar .
* A named <code>LOCATION</code> (potentially with an address and/or geo) in iCalendar {{may}} be represented by a nested [[hcard|hCard]] in hCalendar. Similarly, an address <code>LOCATION</code> {{may}} be represented by an [[adr]], and a geo (latitude and longitude) <code>LOCATION</code> may be represented by a [[geo]].
* <code>UID</code> in iCalendar simply becomes another semantic applied to a specific URL for an hCalendar event.

=== Singular vs. Plural Properties ===

For properties which are singular (e.g. "N" and "FN" from vCard), the first descendant element with that class {{should}} take effect, any others being ignored.

For properties which can be plural (e.g. "TEL" from vCard), each class instance {{should}} create a instance of that property. Plural properties with subtypes (e.g. TEL with WORK, HOME, CELL from vCard) can be optimized to share a common element for the property itself, with each instance of subtype being an appropriately classed descendant of the property element.

==== Plural Properties Singularized ====

Since plural property names become their singular equivalents, even if the original plural property permitted only a single value with multiple components, those multiple components are represented each with their own singularly named property and the the property is effectively multivalued and subject to the above treatment of multivalued properties.

=== Human vs. Machine readable ===
If an <code><nowiki><abbr></nowiki></code> element is used for a property, then the '<code>title</code>' attribute of the <code><nowiki><abbr></nowiki></code> element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value. This specification recommends that such <code><nowiki><abbr></nowiki></code> elements be used for the following iCalendar properties:
* DTSTART, DTEND, DURATION, RDATE, RRULE

== Example ==

Here is a sample event in an iCalendar:
<pre>
<nowiki>
BEGIN:VCALENDAR
PRODID:-//XYZproduct//EN
VERSION:2.0
BEGIN:VEVENT
URL:http://www.web2con.com/
DTSTART:20071005
DTEND:20071020
SUMMARY:Web 2.0 Conference
LOCATION:Argent Hotel\, San Francisco\, CA
END:VEVENT
END:VCALENDAR
</nowiki>
</pre>

and an equivalent event in hCalendar format with various elements optimized appropriately. See [[hcalendar-example1-steps]] for the derivation.

<pre><nowiki>
<div class="vevent">
<a class="url" href="http://www.web2con.com/">http://www.web2con.com/</a>
Web 2.0 Conference:
<abbr class="dtstart" title="2007-10-05">October 5</abbr>-
<abbr class="dtend" title="2007-10-20">19</abbr>,
at the Argent Hotel, San Francisco, CA
</div>
</nowiki></pre>

which could be displayed as:

<div class="vevent">
http://www.web2con.com/ 
Web 2.0 Conference:
<abbr class="dtstart" title="2007-10-05">October 5</abbr>-
<abbr class="dtend" title="2007-10-20">19</abbr>,
at the Argent Hotel, San Francisco, CA
</div>

Note that this is a '''live''' hCalendar microformat, which will be found on this page by parsers.

=== Example 2 ===

The following example specifies a scheduled meeting that begins
at 8:30 AM EST on March 12, 1998 and ends at 9:30 AM EST on March 12,
1998.

<pre><nowiki>
BEGIN:VCALENDAR
BEGIN:VEVENT
UID:guid-1.host1.com
DTSTAMP:19980309T231000Z
DESCRIPTION:Project XYZ Review Meeting
SUMMARY:XYZ Project Review
DTSTART:19980312T133000Z
DTEND:19980312T143000Z
LOCATION:1CP Conference Room 4350
END:VEVENT
END:VCALENDAR
</nowiki></pre>

The equivalent in hCalendar:

<pre><nowiki>
<div class="vevent">
<h3 class="summary">XYZ Project Review</h3>
Project XYZ Review Meeting
To be held on <abbr class="dtstart" title="1998-03-12T08:30:00-05:00">12 March 1998 from 8:30am EST</abbr>
until <abbr class="dtend" title="1998-03-12T09:30:00-05:00">9:30am EST</abbr>
Location: 1CP Conference Room 4350
Booked by: guid-1.host1.com on
<abbr class="dtstamp" title="19980309T231000Z">9 Mar 1998 6:00pm</abbr>
</div>
</nowiki></pre>

This could be displayed as:

----

<div class="vevent">

<h3 class="summary">XYZ Project Review</h3>
Project XYZ Review Meeting
To be held on <abbr class="dtstart" title="1998-03-12T08:30:00-05:00">12 March 1998 from 8:30am EST</abbr>
until <abbr class="dtend" title="1998-03-12T09:30:00-05:00">9:30am EST</abbr>
Location: 1CP Conference Room 4350
Booked by: guid-1.host1.com on <abbr class="dtstamp" title="19980309T231000Z">9 Mar 1998 6:00pm</abbr></div>

----

Note 1: The product information is not necessary since hCalendar is an interchange format. When transforming hCalendar back into iCalendar, the transforming engine should add its own product ID.

Note 2: A surrounding <code><nowiki></nowiki></code> element is optional, and is left out as such. It is optional since the context of a vcalendar is implied when a vevent is encountered. The implied context/scope is that of the document. Authors may explicitly use elements with class="vcalendar" to wrap sets of vevents that all belong to the same calendar, e.g. when publishing multiple calendars on the same page.

Note 3: The version information is unnecessary in hCalendar markup directly since the version will be defined by the profile of hCalendar that is used/referred to in the 'profile' attribute of the <head> element.

Note 4: [[iso-8601|ISO8601]] dates (required by iCalendar) are not very human friendly. In addition, the year is often understood implicitly by humans from the context. Thus <code><nowiki><abbr></nowiki></code> elements are used to simultaneously provide a human friendly date and/or time in the visible contents of the element, while placing the respective machine parsable comprehensive ISO8601 datetime in the 'title' attribute.
The notation <code>YYYY-MM-DDThh:mm:ss</code> should be used for better readability, following the format of RFC 3339.

Note 5: The difference between the DTEND ISO8601 date (2005-10-08) and the human readable date (7) is NOT a mistake. [http://lists.osafoundation.org/pipermail/ietf-calsify/2005-September/000769.html DTEND is exclusive], meaning, that the event ends just before the DTEND. Thus for events which start on one day and end on another day, the DTEND date must be specified as the day after the day that a human would say is the last day of the event.

Note 6: The location in this example contains implicit structure (venue name, city, state) which could be marked up explicitly as an [[hcard|hCard]]. See [http://microformats.org/wiki/hcalendar-brainstorming#hCard_locations hCalendar brainstorming: hCard locations] for a informative explanation of how to do this.

==Buttons==
Don't forget that you can add one of our [[buttons#hCalendar|buttons]] to the page, to indicate the presence of hCalendar microformats. For example: http://www.boogdesign.com/images/buttons/microformat_hcalendar.png. If you can link it back to this page (or even page on your website, about your use of the microformat), so much the better!

=== More Examples ===
See [[hcalendar-examples|hCalendar examples]] for more examples, including examples from iCalendar RFC 2445 converted into hCalendar.

== Examples in the wild ==
This section is '''informative'''. The number of hCalendar examples in the wild has expanded far beyond the capacity of being kept inline in this specification. They have been moved to a [[hcalendar-examples-in-wild|separate page]].

See [[hcalendar-examples-in-wild|hCalendar Examples in the wild]].

== Implementations ==
This section is '''informative'''. The number of hCalendar implementations has also expanded beyond the capacity of keeping them inline. They have been moved to a [[hcalendar-implementations|separate page]].

See [[hcalendar-implementations|hCalendar Implementations]].

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [[hcard|hCard]]
* [http://www.ietf.org/rfc/rfc2445.txt iCalendar RFC2445]
* [[rfc-2119| RFC 2119]]
* [[iso-8601|ISO8601]]

=== Informative References ===
* [http://w3.org/TR/REC-CSS1 CSS1]
* [http://tantek.com/log/2004/09.html#hcalendar hCalendar term introduced and defined on the Web, 20040930]
* [http://wiki.oreillynet.com/foocamp04/index.cgi?HTMLForCalendars FOO Camp 2004 HTML For Calendars presentation, 20040911]
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]
* [http://ietfreport.isoc.org/idref/draft-royer-ical-basic/ iCal-Basic (latest)] [http://www.faqs.org/ftp/pub/pub/internet-drafts/draft-royer-ical-basic-04.txt (draft 04)]
* [http://www.w3.org/TR/NOTE-datetime W3C Note on Date and Time Formats]
* [http://www.imc.org/pdi/ Internet Mail Consortium Personal Data Interchange vCard and vCalendar]
* Contributed from http://developers.technorati.com/wiki/hCalendar

==== Specifications That Use hCalendar ====
* [[hreview|hReview]]

==== Related Work ====
* [http://lists.osafoundation.org/pipermail/ietf-calsify/ IETF-calsify archives]
* [http://www.softwarestudio.org/iCal/2445Issues.html RFC2445 Issues List]
* [http://ietf.webdav.org/calsify/ CALSIFY WG Links And Resources]

== Further Reading ==
* [http://www.livejournal.com/users/jwz/444651.html jwz - Hula] (required reading)
* [http://www.jwz.org/doc/groupware.html Groupware Bad by Jamie Zawinski] crystalizes the reason for hCalendar ('''emphasis''' added):
<blockquote>Right now people can do that by publishing .ics files, but it's not trivial to do so, and it's work on the part of other people to look at them. '''If it's not HTML hanging off our friend's home page that can be viewed in any browser on a public terminal in a library, the bar to entry is too high and it's useless.'''</blockquote>

* [http://muddybranch.thejkgroup.com/ Jason Klemow's blog]
* [http://weblog.infoworld.com/udell/2006/01/11.html#a1368 Moving forward with microformats] by [http://weblog.infoworld.com/udell Jon Udell] provides an hCalendar example and some discussion.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page] and the [http://technorati.com/tags/hcalendar hCalendar tag]
* [http://en.wikipedia.org/wiki/HCalendar Wikipedia article on hCalendar] (requires expansion)
* [http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-4-hcalendar/ Getting Semantic With Microformats, Part 4: hCalendar] by [http://www.ablognotlimited.com/ Emily Lewis]

== Related Pages ==
{{hcalendar-related-pages}}

[[Category:Specifications]]
[[Category:hCalendar]]

xfn

2008-11-17T15:11:59Z

EmilyLewis:

<entry-title>XFN - The XHTML Friends Network</entry-title>
<abbr title="XHTML Friends Network">XFN</abbr> is a simple way to represent human relationships using hyperlinks.

The XFN specification and more information can be found at [http://www.gmpg.org/xfn/ GMPG.org].

* [http://gmpg.org/xfn/ XFN home page]
* [http://gmpg.org/xfn/intro introduction to XFN]
* [http://gmpg.org/xfn/and/#idconsolidation XFN and identity consolidation with rel="me"]

Some pages discussing XFN can be found on this wiki:

{{xfn-related-pages}}

Lengthy article(s) on XFN:
* [http://www.centralityjournal.com/archives/xfn_bottomup_social_networks.html XFN:bottom-up Social Networks by Stowe Boyd]
* [http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-2-xfn/ Getting Semantic With Microformats, Part 2: XFN] by [http://www.ablognotlimited.com/ Emily Lewis]

[[Category:Specifications]]
[[Category:XFN]]

hcard

2008-11-17T15:10:03Z

EmilyLewis: /* Further Reading */

<entry-title>hCard</entry-title>
__TOC__
hCard is a simple, open, distributed format for representing people, companies, organizations, and places, using a 1:1 representation of vCard ([[rfc-2426|RFC2426]]) properties and values in [[semantic-xhtml|semantic HTML or XHTML]]. hCard is one of several open [[microformats|microformat]] standards suitable for embedding in HTML, XHTML, Atom, RSS, and arbitrary XML.

Want to get started with writing an [[hcard|hCard]]? Use the [http://microformats.org/code/hcard/creator hCard creator] to write up some contact information and publish it, or follow the [[hcard-authoring|hCard authoring tips]] to add hCard markup to your current contact page.

== Specification ==

<div class="vcard">
; Editor
: [[User:Tantek|Tantek Çelik]] (http://tantek.com/, and before at [http://technorati.com Technorati, Inc.], and at [http://microsoft.com/ Microsoft Corporation])
</div>
; Authors: [http://tantek.com/ Tantek Çelik] (affiliations above)
: [[User:Brian|Brian Suda]] (http://suda.co.uk/)

; Acknowledgments: See [[hcard#Inspiration_and_Acknowledgements|acknowledgments]].

[[hcard#Copyright|copyright]] and [[hcard#Patents|patents]] statements apply.

== Introduction ==
The vCard standard ([[rfc-2426|RFC2426]]), has been broadly interoperably implemented (e.g. Apple's "Address Book" application built into MacOSX).

In addition, many bloggers identify themselves by name and discuss their friends and family. With just a tad bit of structure, bloggers can discuss people in their blog(s) in such a way that spiders and other aggregators can retrieve this information, automatically convert them to vCards, and use them in any vCard application or service.

This specification introduces the '''hCard''' format, which uses a 1:1 representation of the properties and values of the aforementioned vCard standard, in semantic HTML. Bloggers can both embed hCards directly in their web pages, and style them with CSS to make them appear as desired. In addition, hCard enables applications to retrieve information directly from web pages without having to reference a separate file.

Use the [http://microformats.org/code/hcard/creator hCard creator] and copy the HTML code it generates to your blog or website to publish your contact info.

{{rfc-2119-intro}}

== Format ==
=== In General ===
The vCard standard ([[rfc-2426|RFC2426]]) forms the basis of hCard.

The basic format of hCard is to use vCard object/property names in lower-case for class names, and to map the nesting of vCard objects directly into nested HTML elements.

=== Root Class Name ===
The root class name for an hCard is "vcard". An element with a class name of "vcard" is itself called an ''hCard''.

=== Properties and Sub-properties ===
The properties of an hCard are represented by elements inside the hCard. Elements with class names of the listed properties represent the values of those properties. Some properties have sub-properties, and those are represented by elements inside the elements for properties.

=== Property List ===
hCard properties (sub-properties in parentheses like this)

'''Required:'''
* '''fn'''
* '''n'''[[#note1|1]] (family-name, given-name, additional-name, honorific-prefix, honorific-suffix)
Optional:
* nickname, sort-string
* url, email (type, value), tel[[#note2|2]] (type, value)
* adr (post-office-box, extended-address, street-address, locality, region, postal-code, country-name, type, value), label
* geo (latitude, longitude), tz
* photo, logo, sound, bday
* title, role, org (organization-name, organization-unit)
* category, note
* class, key, mailer, uid, rev

=== Property Notes ===
[[#property-list-n|1. ^]]: The 'n' property is {{optional}} if any [[hcard#Implied_.22n.22_Optimization|implied 'n' optimization rules]] are in effect. 
[[#property-list-tel|2. ^]]: tel - Authors {{may}} follow the [http://en.wikipedia.org/wiki/E.123 E.123] standard for writing values of telephone numbers. Letter values (e.g. +1-555-FORMATS) {{must}} be converted to numbers. Use an <code>abbr</code> to display letters and provide a numerical value simultaneously, e.g. <code><nowiki><abbr title="+15553676287">+1-555-FORMATS</abbr></nowiki></code>.

=== Singular vs. Plural Properties ===
Singular properties: 'fn', 'n', 'bday', 'tz', 'geo', 'sort-string', 'uid', 'class'. For properties which are singular, the first descendant element with that class {{should}} take effect, any others being ignored.

All other properties {{may}} be plural. Each class instance of such properties creates a new instance of that property.

=== Human vs. Machine readable ===
The human visible text contents of an element for a property represents the value of that property, with a few exceptions:

If an <code><abbr></code> element is used for a property, then the '<code>title</code>' attribute (if present) of the <code><abbr></code> element is the value of the property, instead of the contents of the element, which instead provide a more human presentable version of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>src="..."</code> attribute provides the property value.
# For other properties, the <code><img></code> element's '<code>alt</code>' attribute is the value of the property.

If an <code><object></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>data="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

=== Value excerpting ===
Sometimes only part of an element which is the equivalent for a property is used for the value of the property. This typically occurs when a property has a subtype, like 'tel'. For this purpose, the special class name "<code>value</code>" is used to excerpt out the subset of the element that is the value of the property. E.g. here is an hCard fragment for marking up a home phone number: 

vCard:
<pre><nowiki>
TEL;TYPE=HOME:+1.415.555.1212
</nowiki></pre>

hCard:
<pre><nowiki>

home:
+1.415.555.1212

</nowiki></pre>

This hCard fragment could be displayed as:

<div style="border: thin dashed black; width: 95%; padding: .5em 1em;">

home:
+1.415.555.1212

</div>



=== Property Exceptions ===
vCard has several properties which either do not make sense on, or are already implied within the context of a web page. This section explains what to (not) do with them.

# vCard's '''NAME''', '''PROFILE''', '''SOURCE''', '''PRODID''', '''VERSION''' properties are defined in Sections 2.1.2, 2.1.3, 2.1.4, 3.6.3, 3.6.9 of [[rfc-2426|RFC2426]]. Content publishers {{must-not}} use these properties in their hCards, and as such, hCard consumers/parsers {{must}} IGNORE these properties if they are found within an hCard. Instead. hCard to vCard converters {{should}} use the title of the page where the hCard is found (e.g. the <code><title></code> element in HTML documents) to construct the NAME property, {{may}} output a PROFILE value of "<code>VCARD</code>" per [[rfc-2426|RFC2426]], {{should}} use the URL of the page where the hCard is found to construct the SOURCE property (e.g. perhaps as a parameter to a URL/service that converts hCards to vCards), for an output vCard stream (e.g. a .vcf file). Only services/applications that output actual vCards should write the PRODID property, with the product identifier for said service/application. Similarly, only such services/applications should write the VERSION property, with the value "3.0" (without quotes) per [[rfc-2426|RFC2426]] Section 3.6.9.

=== Organization Contact Info ===
If the "FN" and "ORG" properties have the exact same value (typically because they are set on the same element, e.g. class="fn org"), then the hCard represents contact information for a company, organization or place and {{should}} be treated as such. In this case the author also {{must-not}} set the "N" property, or set it (and any sub-properties) explicitly to the empty string "". Thus parsers {{should}} handle the missing "N" property, in this case by implying empty values for all the "N" sub-properties.

=== Implied "n" Optimization ===
Although vCard requires that the "N" property be present, the authors of the vCard specification ([[rfc-2426|RFC2426]]) themselves do not include "N" properties in their vCards near the end of the spec (p.38). This apparent contradiction can be resolved by simply allowing the "FN" property to imply "N" property values in typical cases provided in the spec. We do so explicitly in hCard.

If "FN" and "ORG" are not the same (see previous section), and the value of the "FN" property is exactly two words (separated by whitespace), and there is no explicit "N" property, then the "N" property is inferred from the "FN" property. For "FN"s with either one word see below, and for three or more, the author {{must}} explicitly markup the "N", except for the organization contact info case, [http://microformats.org/wiki/hcard#Organization_Contact_Info see above] for that.

# The content of "FN" is broken into two "words" separated by whitespace.
# The ''first'' word of the "FN" is interpreted as the "given-name" for the "N" property.
# The ''second/last'' word of the "FN" is interpreted as the "family-name" for the "N" property.
# Exception: If the first word ends in a "," comma OR if the second word is a single character (optionally followed by a period "."), then the first word (minus the comma at the end if any) is interpreted as the "family-name" and the second word is interpreted as the "given-name".

This allows simplification in the typical case of people stating:
* given-name (space) family-name
* family-name (comma) given-name
* family-name (comma) given-name-first-initial
* family-name (space) given-name-first-initial (optional period)

=== Implied "nickname" Optimization ===
Due to the prevalence of the use of nicknames/handles/usernames in actual content published on the Web (e.g. authors of [[hReview|reviews]]), hCard also has an implied "nickname" optimization to handle this.

Similar to the implied "n" optimization, if "FN" and "ORG" are not the same, and the value of the "FN" property is exactly one word, and there is no explicit "N" property, then:

# The content of the "FN" {{must}} be treated as a "nickname" property value.
# Parsers {{should}} handle the missing "N" property by implying empty values for all the "N" sub-properties.

Though parsers {{must}} follow the implied nickname optimization, publishers {{should}} explicitly indicate the "nickname" even in this case, e.g.:

<pre><nowiki>

daveman692

</nowiki></pre>

The hCard {{may}} have additional explicit "nickname" property values in addition to the implied nickname.

=== Implied "organization-name" Optimization ===
The "ORG" property has two subproperties, organization-name and organization-unit. Very often authors only publish the organization-name. Thus if an "ORG" property has no "organization-name" inside it, then its entire contents {{must}} be treated as the "organization-name".

=== Tags as Categories ===
Categories in hCard {{may}} be represented by tags with [[rel-tag]]. When a category property is a rel-tag, the tag (as defined by rel-tag) is used for that category.

=== type subproperty values ===
The 'type' subproperty in particular takes different values depending on which property it is a subproperty of. These 'type' subproperty values are case-INSENSITIVE, meaning "Home" is the same as "home", as well as multivalued, e.g. a tel can be home and preferred:

vCard:
<pre><nowiki>
TEL;TYPE=HOME,PREF:+1.415.555.1212
</nowiki></pre>

hCard:
<pre><nowiki>
Home (preferred):
+1.415.555.1212

</nowiki></pre>

This could be displayed as:

<div style="border: thin dashed black; width: 95%; padding: .5em 1em; ">
Home (preferred):
+1.415.555.1212

</div>

==== type with unspecified value ====
When the type of a property is specified, and there is no explicit value specified, then everything in the property except for the type is considered the value of the property. E.g.

<pre><nowiki>
Home +1.415.555.1212
</nowiki></pre>

is equivalent to:

<pre><nowiki>
Home +1.415.555.1212
</nowiki></pre>

And thus the type is "home" and the value is "+1.415.555.1212".

==== adr tel email types ====
The following lists are ''informative''. See [[rfc-2426|RFC2426]] sections 3.2.1 ADR, 3.3.1 TEL, and 3.3.2 EMAIL respectively for normative type values. They are repeated here for convenience. Default type subproperty value(s) is(are) first in each list and indicated in ALL CAPS. types may be multivalued.

* adr type: INTL, POSTAL, PARCEL, WORK, dom, home, pref
* tel type: VOICE, home, msg, work, pref, fax, cell, video, pager, bbs, modem, [http://flickr.com/photos/tags/carcellphone/ car], isdn, pcs
* email type: INTERNET, x400, pref, "other IANA registered address types"

=== XMDP Profile ===

See [[hcard-profile]] for the [http://gmpg.org/xmdp XMDP] profile of hCard which contains the above complete list of properties, with references to their [[rfc-2426|RFC2426]] definitions.

=== Parsing Details ===

See [[hcard-parsing|hCard parsing]].

== Examples ==

This section is informative.

=== Sample vCard ===

Here is a sample vCard:

<pre><nowiki>
BEGIN:VCARD
VERSION:3.0
N:Çelik;Tantek
FN:Tantek Çelik
URL:http://tantek.com/
END:VCARD
</nowiki></pre>

and an equivalent in hCard with various elements optimized appropriately. See [[hcard-example1-steps| hCard Example 1]] for the derivation.

<pre><nowiki>
<div class="vcard">
<a class="url fn" href="http://tantek.com/">Tantek Çelik</a>
</div>
</nowiki></pre>

This hCard might be displayed as:
<div style="border: thin dashed black; width: 95%; padding: .5em 1em;">
[http://tantek.com/ Tantek Çelik]
</div>

Note: The version information is unnecessary in hCard markup directly since the version will be defined by the profile of hCard that is used/referred to in the 'profile' attribute of the <head> element.

===Live example===

Here is [http://www.commerce.net/ Commercenet]'s contact details, as a live hCard which will be detected, on this page, by microformat parsing tools:

<div class="vcard">
<div class="fn org">'''CommerceNet'''</div>
<div class="url">'''<nowiki>http://www.commerce.net/</nowiki>'''</div>
<div class="adr">'''Work:'''
<div class="street-address">'''169 University Avenue'''</div>
'''Palo Alto''', '''CA'''  '''94301'''
<div class="country-name">'''USA'''</div>
</div>
<div class="tel">'''Work +1-650-289-4040'''</div>
<div class="tel">'''Fax +1-650-289-4041'''</div>
<div>'''Email <nowiki>info@commerce.net</nowiki>'''</div>
</div>

The mark-up, emboldening omitted for clarity, with the following semantic improvements:
* <code>abbr</code> to expand abbreviations
* hyperlinking the org name with the url

<pre><nowiki>
<div class="vcard">
<a class="fn org url" href="http://www.commerce.net/">CommerceNet</a>
<div class="adr">
Work:
<div class="street-address">169 University Avenue</div>
Palo Alto,
<abbr class="region" title="California">CA</abbr>  
94301
<div class="country-name">USA</div>
</div>
<div class="tel">
Work +1-650-289-4040
</div>
<div class="tel">
Fax +1-650-289-4041
</div>
<div>Email:
info@commerce.net
</div>
</div>
</nowiki></pre>

=== More Examples ===
See [[hcard-examples|hCard examples]] for more examples, including all examples from vCard [[rfc-2426|RFC2426]] converted into hCard.

==Buttons==
You can use these buttons on pages with hCards. See [[buttons#hCard]] for any recent additions.

* http://www.crowley.nl/images/hcard.png (mirror: http://www.davidjanes.com/images/mf_hcard.png)
* http://rbach.priv.at/2006/buttons/hcard.png
* http://www.boogdesign.com/images/buttons/microformat_hcard.png
* CSS-powered button, as evidenced at [http://re-run.com/about/microformat-badges microformat badges @ re-run]

== Examples in the wild ==
This section is '''informative'''. The number of hCard examples in the wild has expanded far beyond the capacity of being kept inline in this specification. They have been moved to a [[hcard-examples-in-wild|separate page]].

See [[hcard-examples-in-wild|hCard Examples in the wild]].

== Implementations ==
This section is '''informative'''. The number of hCard implementations has also expanded beyond the capacity of keeping them inline. They have been moved to a [[hcard-implementations|separate page]].

See [[hcard-implementations|hCard Implementations]].

== Copyright ==
Per the public domain release on the authors' user pages ([[User:Tantek|Tantek Çelik]], [[User:Brian|Brian Suda]]) this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426]
* [http://www.itu.int/rec/T-REC-E.123-200102-I/en ITU recommendation E.123] format of telephone numbers (chargeable document)
* [[rfc-2119|RFC 2119]]

=== Informative References ===
* [[hcard-history|hCard history]]
** [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 2004-09-10]
** [http://tantek.com/log/2004/09.html#hcard hCard term introduced and defined on the Web, 2004-09-30]
** Contributed from http://developers.technorati.com/wiki/hCard 2005-06-20
* [http://www.dante.net/np/ds/osi/9594-6-X.520.A4.ps X.520 in Postscript] ([http://72.14.253.104/search?q=cache:FjqzsFu4h20J:www.dante.net/np/ds/osi/9594-6-X.520.A4.ps HTMLization courtesy of Google Cache]) - vCard refers to ROLE as being "based on the X.520 Business Category explanatory attribute".
* [http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426]
* [http://w3.org/TR/REC-CSS1 CSS1]
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]
* [http://en.wikipedia.org/wiki/E.123 Wikipedia summary of ITU-T Recommendation E.123] - for "TEL" values.
* [http://www.imc.org/pdi/ Internet Mail Consortium Personal Data Interchange vCard and vCalendar]
* [[iso-8601|ISO8601]]

==== Specifications That Use hCard ====
* [[adr]]
* [[geo]]
* [[hcalendar|hCalendar]]
* [[hreview|hReview]]

==== Similar Work ====
* [http://www.intertwingly.net/wiki/pie/PaceBetterPersonElement Atom PaceBetterPersonElement]
* [http://www.jabber.org/jeps/jep-0054.html JEP-0054: vcard-temp]

== Inspiration and Acknowledgments ==
Thanks to: my good friend [http://vadim.com/ Vadim] who introduced me to vCard ''many'' years ago, and if I'd only paid more attention then, perhaps I could have helped a lot of people avoid wasting a lot of time reinventing various standards wheels.

== Notes on derivation from vCard ==
This section is ''informative''.

<div id="Semantic_XHTML_Design_Principles">See: [[hcard-design-methodology]].</div>

=== More Semantic Equivalents ===
For some properties there are HTML elements which better match and convey their semantics. The following properties SHOULD be encoded with the following HTML:
* <code>URL</code> in vCard becomes <code><a class="url" href="...">...</a></code> inside the element with <code>class="vcard"</code> in hCard.
* Similarly, <code>EMAIL</code> in vCard becomes <code><nowiki><a class="email" href="mailto:...">...</a></nowiki></code>
* <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.

=== Singular and Plural derivations ===
The [[hcard#Singular_vs._Plural_Properties|lists of singular and plural properties]] have been derived by analyzing the semantics of the individual properties in vCard RFC2426 and determining logically that they MUST be singular per their semantics. See [[hcard-singular-properties]] for explanations.

==== Plural Properties Singularized ====
Since plural property names become their singular equivalents, even if the original plural property permitted only a single value with multiple components, those multiple components are represented each with their own singularly named property and the the property is effectively multivalued and subject to the above treatment of multivalued properties.

== Further Reading ==
* [http://www.digital-web.com/articles/microformats_primer/ Digital Web Magazine: Microformats Primer] by Garrett Dimon has a good intro to hCard
* [http://24ways.org/advent/practical-microformats-with-hcard Practical Microformats with hCard] by Drew McLellan
* [http://www.naturalsearchblog.com/archives/2006/09/28/tips-for-local-search-engine-optimization-for-your-site/ Local Search Engine Optimization using Microformats] by Chris Silver Smith
* [http://thedredge.org/ Andrew D. Hume] has written a blog post on [http://usabletype.com/articles/2005/usable-microformats/ usable microformats] which discusses hCard
* [http://www.thefutureoftheweb.com/blog/2006/1/hcard Jesse Skinner's introduction to hCard]
* [http://blog.usweb.com/ Shaun Shull's] great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], including his [[hcard|hCard]] as an example.
* [http://24ways.org/2006/styling-hcards-with-css 24 Ways: Styling hCards with CSS] A 24 Ways article - John Allsopp on styling hCard using CSS
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page] and the [http://technorati.com/tags/hcard hCard tag]
* [http://www.rfc-editor.org/rfc/rfc4770.txt <nowiki>RFC 4770</nowiki> Extensions for Instant Messaging]
* [http://ungeekdapo.wordpress.com/2008/04/30/a-real-life-use-case-of-microformat-hcard-in-action/ A real life use case of Microformat hCard in action] by Bob Ngu
* [http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-3-hcard/ Getting Semantic With Microformats, Part 3: hCard] by [http://www.ablognotlimited.com/ Emily Lewis]

== Related Pages ==
{{hcard-related-pages}}

[[Category:Specifications]]
[[Category:hCard]]

articles

2008-11-10T14:58:04Z

EmilyLewis: /* 2008 */

<h1>Articles</h1>
{{TOC-right}}



== 2008 ==
*2008-11-10: <cite class="entry-title">Getting Semantic With Microformats, Part 6: hResume</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-6-hresume/

*2008-10-15: <cite class="entry-title">Getting Semantic With Microformats, Part 5: hAtom</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-5-hatom/

*2008-10-01: <cite class="entry-title">Getting Semantic With Microformats, Part 4: hCalendar</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-4-hcalendar/

*2008-09-22: <cite class="entry-title">Getting Semantic With Microformats, Part 3: hCard</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-3-hcard/

*2008-09-17: <cite class="entry-title">Getting Semantic With Microformats, Part 2: XFN</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-2-xfn/

*2008-09-09: <cite class="entry-title">Getting Semantic With Microformats, Part 1: rel</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-1-rel/

*2008-09-05: <cite class="entry-title">Getting Semantic With Microformats, Introduction</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-introduction/

*2008-02-21: ''<cite class="entry-title">XFN encoding, extraction, and visualizations</cite>'' by Brian Suda: http://dev.opera.com/articles/view/xfn-encoding-extraction-and-visualizat/

*2008-02-21: ''Microformats : comment microformater du contenu déjà existant ?'' by Thomas Parisot: http://www.clever-age.com/veille/blog/microformats-comment-microformater-du-contenu-deja-existant.html

*2008-01-24: ''Microformats introduction to content and user experience'' by Sarven Capadisli: http://www.csarven.ca/microformats-introduction

*2008-01-11: ''Microformats : republier et donner du sens aux contenus'' by Thomas Parisot: http://www.clever-age.com/veille/blog/microformats-republier-et-donner-du-sens-aux-contenus.html

== 2007 ==

*2007-12-05: ''The Magical Minimalism of Microformats'' by Jacob Harris in The New York Times blog: http://open.blogs.nytimes.com/2007/12/05/the-magical-minimalism-of-microformats/

*2007-11-21: ''Portable Social Networks: Take Your Friends with You'' by Brian Suda: http://www.sitepoint.com/article/social-networks-take-friends/

*2007-07-24: ''Microformats: More Meaning from Your Markup'' by Brian Suda: http://www.sitepoint.com/article/microformats-meaning-markup

==2006==

*2006-04-02: ''Blog Business Summit: Microformats in Plain English: the Promise of Simple Business to Business Data Exchange'' by Steve Broback: http://blogbusinesssummit.com/2006/04/microformats_in.htm

*2006-01-29: ''How Microformats Affect Seearch Engine Optimization'' by Shaun Shull: http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo

*2006-01-27: ''Introduction to hCard'' by Jesse Skinner: http://www.thefutureoftheweb.com/blog/2006/1/hcard

==2005==

*2005-12-06: ''Practical Microformats with hCard'' by Drew McLellan: http://24ways.org/advent/practical-microformats-with-hcard

*2005-11-17: ''An Extra SIDE to Web Standards Based Design - How Semantic Information Design Ethics (SIDE) and a few readily available techniques can help heal the Web'' by Jon Tan: http://www.gr0w.com/articles/design/an_extra_side_to_web_standards_based_design/
**See also his [http://www.csszengarden.com/?cssfile=/193/193.css&page=0 CSS Zen Garden "Leggo my ego" entry].

*2005-11-14: ''Microformats Primer'' by Garrett Dimon in Digital Web Magazine: http://www.digital-web.com/articles/microformats_primer/

*2005-07-24: ''Usable Microformats'' by Andrew D. Hume: http://usabletype.com/weblog/usable-microformats/

*2005-06-03: ''Introducing microformats'' by Andrew D. Hume: http://thedredge.org/2005/07/introducing-microformats/

== Miscellaneous Reference ==

These are various intro-related links/articles which we haven't figured out yet how to incorporate. You may find them of interest.

* [http://www.betaversion.org/~stefano/linotype/news/93/ Data First vs. Structure First]
** [http://tantek.com/log/ Tantek] says: In many ways it is actually *far* worse than that post conveys. The "typical" programmer literally loves spending far more time worrying about and designing the structure for structure's sake, than data, and even less so, "real world" data (current behaviors etc.). Hence we have taken the directly opposite tack with microformats when looking to solve a problem.
*** Zeroeth, define the real-world problem. If you can't do this, then stop.
*** First, look at real-world usage (data).
*** Second, what previous standards are people actually using today? If there is more than one, then lean towards those with the better adoption.
***And only after those first two do we bother to pay attention to theoretical standards, those that have been invented (whether by individuals, committees), but haven't seen much if any actual adoption.
* [http://lists.w3.org/Archives/Public/www-rdf-interest/2000Mar/0103 2000-03-21 Dan Connolly on human-consumable information]: ('''strong emphasis''' added)
** I believe that one of the best ways to transition into RDF, if not a long-term deployment strategy for RDF, is to '''manage the information in human-consumable form (XHTML) annotated with just enough info to extract''' the RDF statements that the human info is intended to convey. In other words: using a relational database or some sort of native RDF data store, and spitting out HTML dynamically, is a lot of infrastructure to operate and probably not worth it for lots of interesting cases. '''We all know that we have to produce a human-readable version of the thing... why not use that as the primary source?'''

== See Also ==
* [[press]]

articles

2008-10-15T15:08:28Z

EmilyLewis: /* 2008 */

<h1>Articles</h1>
{{TOC-right}}



== 2008 ==
*2008-10-15: <cite class="entry-title">Getting Semantic With Microformats, Part 5: hAtom</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-5-hatom/

*2008-10-01: <cite class="entry-title">Getting Semantic With Microformats, Part 4: hCalendar</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-4-hcalendar/

*2008-09-22: <cite class="entry-title">Getting Semantic With Microformats, Part 3: hCard</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-3-hcard/

*2008-09-17: <cite class="entry-title">Getting Semantic With Microformats, Part 2: XFN</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-2-xfn/

*2008-09-09: <cite class="entry-title">Getting Semantic With Microformats, Part 1: rel</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-1-rel/

*2008-09-05: <cite class="entry-title">Getting Semantic With Microformats, Introduction</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-introduction/

*2008-02-21: ''<cite class="entry-title">XFN encoding, extraction, and visualizations</cite>'' by Brian Suda: http://dev.opera.com/articles/view/xfn-encoding-extraction-and-visualizat/

*2008-02-21: ''Microformats : comment microformater du contenu déjà existant ?'' by Thomas Parisot: http://www.clever-age.com/veille/blog/microformats-comment-microformater-du-contenu-deja-existant.html

*2008-01-24: ''Microformats introduction to content and user experience'' by Sarven Capadisli: http://www.csarven.ca/microformats-introduction

*2008-01-11: ''Microformats : republier et donner du sens aux contenus'' by Thomas Parisot: http://www.clever-age.com/veille/blog/microformats-republier-et-donner-du-sens-aux-contenus.html

== 2007 ==

*2007-12-05: ''The Magical Minimalism of Microformats'' by Jacob Harris in The New York Times blog: http://open.blogs.nytimes.com/2007/12/05/the-magical-minimalism-of-microformats/

*2007-11-21: ''Portable Social Networks: Take Your Friends with You'' by Brian Suda: http://www.sitepoint.com/article/social-networks-take-friends/

*2007-07-24: ''Microformats: More Meaning from Your Markup'' by Brian Suda: http://www.sitepoint.com/article/microformats-meaning-markup

==2006==

*2006-04-02: ''Blog Business Summit: Microformats in Plain English: the Promise of Simple Business to Business Data Exchange'' by Steve Broback: http://blogbusinesssummit.com/2006/04/microformats_in.htm

*2006-01-29: ''How Microformats Affect Seearch Engine Optimization'' by Shaun Shull: http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo

*2006-01-27: ''Introduction to hCard'' by Jesse Skinner: http://www.thefutureoftheweb.com/blog/2006/1/hcard

==2005==

*2005-12-06: ''Practical Microformats with hCard'' by Drew McLellan: http://24ways.org/advent/practical-microformats-with-hcard

*2005-11-17: ''An Extra SIDE to Web Standards Based Design - How Semantic Information Design Ethics (SIDE) and a few readily available techniques can help heal the Web'' by Jon Tan: http://www.gr0w.com/articles/design/an_extra_side_to_web_standards_based_design/
**See also his [http://www.csszengarden.com/?cssfile=/193/193.css&page=0 CSS Zen Garden "Leggo my ego" entry].

*2005-11-14: ''Microformats Primer'' by Garrett Dimon in Digital Web Magazine: http://www.digital-web.com/articles/microformats_primer/

*2005-07-24: ''Usable Microformats'' by Andrew D. Hume: http://usabletype.com/weblog/usable-microformats/

*2005-06-03: ''Introducing microformats'' by Andrew D. Hume: http://thedredge.org/2005/07/introducing-microformats/

== Miscellaneous Reference ==

These are various intro-related links/articles which we haven't figured out yet how to incorporate. You may find them of interest.

* [http://www.betaversion.org/~stefano/linotype/news/93/ Data First vs. Structure First]
** [http://tantek.com/log/ Tantek] says: In many ways it is actually *far* worse than that post conveys. The "typical" programmer literally loves spending far more time worrying about and designing the structure for structure's sake, than data, and even less so, "real world" data (current behaviors etc.). Hence we have taken the directly opposite tack with microformats when looking to solve a problem.
*** Zeroeth, define the real-world problem. If you can't do this, then stop.
*** First, look at real-world usage (data).
*** Second, what previous standards are people actually using today? If there is more than one, then lean towards those with the better adoption.
***And only after those first two do we bother to pay attention to theoretical standards, those that have been invented (whether by individuals, committees), but haven't seen much if any actual adoption.
* [http://lists.w3.org/Archives/Public/www-rdf-interest/2000Mar/0103 2000-03-21 Dan Connolly on human-consumable information]: ('''strong emphasis''' added)
** I believe that one of the best ways to transition into RDF, if not a long-term deployment strategy for RDF, is to '''manage the information in human-consumable form (XHTML) annotated with just enough info to extract''' the RDF statements that the human info is intended to convey. In other words: using a relational database or some sort of native RDF data store, and spitting out HTML dynamically, is a lot of infrastructure to operate and probably not worth it for lots of interesting cases. '''We all know that we have to produce a human-readable version of the thing... why not use that as the primary source?'''

== See Also ==
* [[press]]

articles

2008-10-02T14:50:42Z

EmilyLewis: /* 2008 */

<h1>Articles</h1>
{{TOC-right}}



== 2008 ==
*2008-10-01: <cite class="entry-title">Getting Semantic With Microformats, Part 4: hCalendar</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-4-hcalendar/

*2008-09-22: <cite class="entry-title">Getting Semantic With Microformats, Part 3: hCard</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-3-hcard/

*2008-09-17: <cite class="entry-title">Getting Semantic With Microformats, Part 2: XFN</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-2-xfn/

*2008-09-09: <cite class="entry-title">Getting Semantic With Microformats, Part 1: rel</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-1-rel/

*2008-09-05: <cite class="entry-title">Getting Semantic With Microformats, Introduction</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-introduction/

*2008-02-21: ''<cite class="entry-title">XFN encoding, extraction, and visualizations</cite>'' by Brian Suda: http://dev.opera.com/articles/view/xfn-encoding-extraction-and-visualizat/

*2008-02-21: ''Microformats : comment microformater du contenu déjà existant ?'' by Thomas Parisot: http://www.clever-age.com/veille/blog/microformats-comment-microformater-du-contenu-deja-existant.html

*2008-01-24: ''Microformats introduction to content and user experience'' by Sarven Capadisli: http://www.csarven.ca/microformats-introduction

*2008-01-11: ''Microformats : republier et donner du sens aux contenus'' by Thomas Parisot: http://www.clever-age.com/veille/blog/microformats-republier-et-donner-du-sens-aux-contenus.html

== 2007 ==

*2007-12-05: ''The Magical Minimalism of Microformats'' by Jacob Harris in The New York Times blog: http://open.blogs.nytimes.com/2007/12/05/the-magical-minimalism-of-microformats/

*2007-11-21: ''Portable Social Networks: Take Your Friends with You'' by Brian Suda: http://www.sitepoint.com/article/social-networks-take-friends/

*2007-07-24: ''Microformats: More Meaning from Your Markup'' by Brian Suda: http://www.sitepoint.com/article/microformats-meaning-markup

==2006==

*2006-04-02: ''Blog Business Summit: Microformats in Plain English: the Promise of Simple Business to Business Data Exchange'' by Steve Broback: http://blogbusinesssummit.com/2006/04/microformats_in.htm

*2006-01-29: ''How Microformats Affect Seearch Engine Optimization'' by Shaun Shull: http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo

*2006-01-27: ''Introduction to hCard'' by Jesse Skinner: http://www.thefutureoftheweb.com/blog/2006/1/hcard

==2005==

*2005-12-06: ''Practical Microformats with hCard'' by Drew McLellan: http://24ways.org/advent/practical-microformats-with-hcard

*2005-11-17: ''An Extra SIDE to Web Standards Based Design - How Semantic Information Design Ethics (SIDE) and a few readily available techniques can help heal the Web'' by Jon Tan: http://www.gr0w.com/articles/design/an_extra_side_to_web_standards_based_design/
**See also his [http://www.csszengarden.com/?cssfile=/193/193.css&page=0 CSS Zen Garden "Leggo my ego" entry].

*2005-11-14: ''Microformats Primer'' by Garrett Dimon in Digital Web Magazine: http://www.digital-web.com/articles/microformats_primer/

*2005-07-24: ''Usable Microformats'' by Andrew D. Hume: http://usabletype.com/weblog/usable-microformats/

*2005-06-03: ''Introducing microformats'' by Andrew D. Hume: http://thedredge.org/2005/07/introducing-microformats/

== Miscellaneous Reference ==

These are various intro-related links/articles which we haven't figured out yet how to incorporate. You may find them of interest.

* [http://www.betaversion.org/~stefano/linotype/news/93/ Data First vs. Structure First]
** [http://tantek.com/log/ Tantek] says: In many ways it is actually *far* worse than that post conveys. The "typical" programmer literally loves spending far more time worrying about and designing the structure for structure's sake, than data, and even less so, "real world" data (current behaviors etc.). Hence we have taken the directly opposite tack with microformats when looking to solve a problem.
*** Zeroeth, define the real-world problem. If you can't do this, then stop.
*** First, look at real-world usage (data).
*** Second, what previous standards are people actually using today? If there is more than one, then lean towards those with the better adoption.
***And only after those first two do we bother to pay attention to theoretical standards, those that have been invented (whether by individuals, committees), but haven't seen much if any actual adoption.
* [http://lists.w3.org/Archives/Public/www-rdf-interest/2000Mar/0103 2000-03-21 Dan Connolly on human-consumable information]: ('''strong emphasis''' added)
** I believe that one of the best ways to transition into RDF, if not a long-term deployment strategy for RDF, is to '''manage the information in human-consumable form (XHTML) annotated with just enough info to extract''' the RDF statements that the human info is intended to convey. In other words: using a relational database or some sort of native RDF data store, and spitting out HTML dynamically, is a lot of infrastructure to operate and probably not worth it for lots of interesting cases. '''We all know that we have to produce a human-readable version of the thing... why not use that as the primary source?'''

== See Also ==
* [[press]]

articles

2008-09-23T01:58:28Z

EmilyLewis: /* 2008 */

<h1>Articles</h1>
{{TOC-right}}



== 2008 ==
*2008-09-22: <cite class="entry-title">Getting Semantic With Microformats, Part 3: hCard</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-3-hcard

*2008-09-17: <cite class="entry-title">Getting Semantic With Microformats, Part 2: XFN</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-2-xfn

*2008-09-09: <cite class="entry-title">Getting Semantic With Microformats, Part 1: rel</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-1-rel

*2008-09-05: <cite class="entry-title">Getting Semantic With Microformats, Introduction</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-introduction/

*2008-02-21: ''<cite class="entry-title">XFN encoding, extraction, and visualizations</cite>'' by Brian Suda: http://dev.opera.com/articles/view/xfn-encoding-extraction-and-visualizat/

*2008-02-21: ''Microformats : comment microformater du contenu déjà existant ?'' by Thomas Parisot: http://www.clever-age.com/veille/blog/microformats-comment-microformater-du-contenu-deja-existant.html

*2008-01-24: ''Microformats introduction to content and user experience'' by Sarven Capadisli: http://www.csarven.ca/microformats-introduction

*2008-01-11: ''Microformats : republier et donner du sens aux contenus'' by Thomas Parisot: http://www.clever-age.com/veille/blog/microformats-republier-et-donner-du-sens-aux-contenus.html

== 2007 ==

*2007-12-05: ''The Magical Minimalism of Microformats'' by Jacob Harris in The New York Times blog: http://open.blogs.nytimes.com/2007/12/05/the-magical-minimalism-of-microformats/

*2007-11-21: ''Portable Social Networks: Take Your Friends with You'' by Brian Suda: http://www.sitepoint.com/article/social-networks-take-friends/

*2007-07-24: ''Microformats: More Meaning from Your Markup'' by Brian Suda: http://www.sitepoint.com/article/microformats-meaning-markup

==2006==

*2006-04-02: ''Blog Business Summit: Microformats in Plain English: the Promise of Simple Business to Business Data Exchange'' by Steve Broback: http://blogbusinesssummit.com/2006/04/microformats_in.htm

*2006-01-29: ''How Microformats Affect Seearch Engine Optimization'' by Shaun Shull: http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo

*2006-01-27: ''Introduction to hCard'' by Jesse Skinner: http://www.thefutureoftheweb.com/blog/2006/1/hcard

==2005==

*2005-12-06: ''Practical Microformats with hCard'' by Drew McLellan: http://24ways.org/advent/practical-microformats-with-hcard

*2005-11-17: ''An Extra SIDE to Web Standards Based Design - How Semantic Information Design Ethics (SIDE) and a few readily available techniques can help heal the Web'' by Jon Tan: http://www.gr0w.com/articles/design/an_extra_side_to_web_standards_based_design/
**See also his [http://www.csszengarden.com/?cssfile=/193/193.css&page=0 CSS Zen Garden "Leggo my ego" entry].

*2005-11-14: ''Microformats Primer'' by Garrett Dimon in Digital Web Magazine: http://www.digital-web.com/articles/microformats_primer/

*2005-07-24: ''Usable Microformats'' by Andrew D. Hume: http://usabletype.com/weblog/usable-microformats/

*2005-06-03: ''Introducing microformats'' by Andrew D. Hume: http://thedredge.org/2005/07/introducing-microformats/

== Miscellaneous Reference ==

These are various intro-related links/articles which we haven't figured out yet how to incorporate. You may find them of interest.

* [http://www.betaversion.org/~stefano/linotype/news/93/ Data First vs. Structure First]
** [http://tantek.com/log/ Tantek] says: In many ways it is actually *far* worse than that post conveys. The "typical" programmer literally loves spending far more time worrying about and designing the structure for structure's sake, than data, and even less so, "real world" data (current behaviors etc.). Hence we have taken the directly opposite tack with microformats when looking to solve a problem.
*** Zeroeth, define the real-world problem. If you can't do this, then stop.
*** First, look at real-world usage (data).
*** Second, what previous standards are people actually using today? If there is more than one, then lean towards those with the better adoption.
***And only after those first two do we bother to pay attention to theoretical standards, those that have been invented (whether by individuals, committees), but haven't seen much if any actual adoption.
* [http://lists.w3.org/Archives/Public/www-rdf-interest/2000Mar/0103 2000-03-21 Dan Connolly on human-consumable information]: ('''strong emphasis''' added)
** I believe that one of the best ways to transition into RDF, if not a long-term deployment strategy for RDF, is to '''manage the information in human-consumable form (XHTML) annotated with just enough info to extract''' the RDF statements that the human info is intended to convey. In other words: using a relational database or some sort of native RDF data store, and spitting out HTML dynamically, is a lot of infrastructure to operate and probably not worth it for lots of interesting cases. '''We all know that we have to produce a human-readable version of the thing... why not use that as the primary source?'''

== See Also ==
* [[press]]

articles

2008-09-17T16:59:21Z

EmilyLewis: /* 2008 */

<h1>Articles</h1>
{{TOC-right}}



== 2008 ==
*2008-09-17: <cite class="entry-title">Getting Semantic With Microformats, Part 2: XFN</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-2-xfn

*2008-09-09: <cite class="entry-title">Getting Semantic With Microformats, Part 1: rel</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-1-rel

*2008-09-05: <cite class="entry-title">Getting Semantic With Microformats, Introduction</cite> by Emily <abbr class="additional-name">P.</abbr> Lewis (http://www.ablognotlimited.com/): http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-introduction/

*2008-02-21: ''<cite class="entry-title">XFN encoding, extraction, and visualizations</cite>'' by Brian Suda: http://dev.opera.com/articles/view/xfn-encoding-extraction-and-visualizat/

*2008-02-21: ''Microformats : comment microformater du contenu déjà existant ?'' by Thomas Parisot: http://www.clever-age.com/veille/blog/microformats-comment-microformater-du-contenu-deja-existant.html

*2008-01-24: ''Microformats introduction to content and user experience'' by Sarven Capadisli: http://www.csarven.ca/microformats-introduction

*2008-01-11: ''Microformats : republier et donner du sens aux contenus'' by Thomas Parisot: http://www.clever-age.com/veille/blog/microformats-republier-et-donner-du-sens-aux-contenus.html

== 2007 ==

*2007-12-05: ''The Magical Minimalism of Microformats'' by Jacob Harris in The New York Times blog: http://open.blogs.nytimes.com/2007/12/05/the-magical-minimalism-of-microformats/

*2007-11-21: ''Portable Social Networks: Take Your Friends with You'' by Brian Suda: http://www.sitepoint.com/article/social-networks-take-friends/

*2007-07-24: ''Microformats: More Meaning from Your Markup'' by Brian Suda: http://www.sitepoint.com/article/microformats-meaning-markup

==2006==

*2006-04-02: ''Blog Business Summit: Microformats in Plain English: the Promise of Simple Business to Business Data Exchange'' by Steve Broback: http://blogbusinesssummit.com/2006/04/microformats_in.htm

*2006-01-29: ''How Microformats Affect Seearch Engine Optimization'' by Shaun Shull: http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo

*2006-01-27: ''Introduction to hCard'' by Jesse Skinner: http://www.thefutureoftheweb.com/blog/2006/1/hcard

==2005==

*2005-12-06: ''Practical Microformats with hCard'' by Drew McLellan: http://24ways.org/advent/practical-microformats-with-hcard

*2005-11-17: ''An Extra SIDE to Web Standards Based Design - How Semantic Information Design Ethics (SIDE) and a few readily available techniques can help heal the Web'' by Jon Tan: http://www.gr0w.com/articles/design/an_extra_side_to_web_standards_based_design/
**See also his [http://www.csszengarden.com/?cssfile=/193/193.css&page=0 CSS Zen Garden "Leggo my ego" entry].

*2005-11-14: ''Microformats Primer'' by Garrett Dimon in Digital Web Magazine: http://www.digital-web.com/articles/microformats_primer/

*2005-07-24: ''Usable Microformats'' by Andrew D. Hume: http://usabletype.com/weblog/usable-microformats/

*2005-06-03: ''Introducing microformats'' by Andrew D. Hume: http://thedredge.org/2005/07/introducing-microformats/

== Miscellaneous Reference ==

These are various intro-related links/articles which we haven't figured out yet how to incorporate. You may find them of interest.

* [http://www.betaversion.org/~stefano/linotype/news/93/ Data First vs. Structure First]
** [http://tantek.com/log/ Tantek] says: In many ways it is actually *far* worse than that post conveys. The "typical" programmer literally loves spending far more time worrying about and designing the structure for structure's sake, than data, and even less so, "real world" data (current behaviors etc.). Hence we have taken the directly opposite tack with microformats when looking to solve a problem.
*** Zeroeth, define the real-world problem. If you can't do this, then stop.
*** First, look at real-world usage (data).
*** Second, what previous standards are people actually using today? If there is more than one, then lean towards those with the better adoption.
***And only after those first two do we bother to pay attention to theoretical standards, those that have been invented (whether by individuals, committees), but haven't seen much if any actual adoption.
* [http://lists.w3.org/Archives/Public/www-rdf-interest/2000Mar/0103 2000-03-21 Dan Connolly on human-consumable information]: ('''strong emphasis''' added)
** I believe that one of the best ways to transition into RDF, if not a long-term deployment strategy for RDF, is to '''manage the information in human-consumable form (XHTML) annotated with just enough info to extract''' the RDF statements that the human info is intended to convey. In other words: using a relational database or some sort of native RDF data store, and spitting out HTML dynamically, is a lot of infrastructure to operate and probably not worth it for lots of interesting cases. '''We all know that we have to produce a human-readable version of the thing... why not use that as the primary source?'''

== See Also ==
* [[press]]