Microformats Wiki - User contributions [en]

picoformats

2009-08-22T19:35:47Z

Cloud: Wanted to include another picoformat, for reference purposes... John Breslin.

<entry-title>picoformats</entry-title>
;short URL
:http://tr.im/picoformats
== Introduction ==
Picoformats represent an effort being undertaken led by Chris Messina to codify various standards and openly pursue a nomenclature and syntax for communicating and executing commands with mobile devices over SMS or via command line interfaces (CLI).

An example application is [http://dodgeball.com Dodgeball's] use of the at symbol (@) to express checking in to a place.

Using the Microformats process and principles of building block design, our goal is to openly develop a complete syntax for interacting with various mobile services using the characters available on most mobile devices.

== Problem Statement ==
* send messages to user mobiles - via SMS, or a small application, that contains information like appointment times, locations,
directions, and contact info. For example, when2where.com reminds users when they need to leave to get to their appointment, so the
message may be like:

leave @ 4:35PM ~Dentist Office -> Detroit, MI

where the text itself is simple and readable, but there *may* be an small utility that would parse the @ symbol to add the event to the calendar, the ~ to allow the person to quickly call that contact, or the -> to pull up a Map/directions to the location

* allow users to write messages to query an application - this is similar to what Mozes has started with notes:

when2where: ?today --- what appointments to I have today
new @ 4PM ~Olive Garden -> Novi --- add an appointment

In addition to the obvious mobile device arena, picoformats may be usable in any context where "markup" is too heavy. For example, an IRC bot, whereisbot, that announces user locations as they sign into a channel, or allows people to do:

.whereami, or .whereis <nick> to geolocate other people in a channel.

The intention is to 'markup' the information, but putting actual XHTML or XML is annoying, since IRC doesn't parse the information at all. So right now the response is:

ajturner: .whereami
whereisbot: ajturner is in Northville, MI, US [42.4365 x -83.4884]

So then someone could write a Picoformat parser for X-Chat/Colloquy/other that would parse the [ #### x #### ] and provide a Map url link.

Using arrows to denote time and place, familiar from video recorders and other devices.
Some thoughts: <past >future ^now (the hat is also mnemonic for Here + At) or >5 (in five days time) >>5 (in 5 weeks time) >>>5 (5 months)

Meeting <Leeds went well. ^Home. See you >london
Sorry, saw them <<2 wanna go see film >3?

<div id="Documented_Syntaxes">

== Syntaxes ==

=== Generic ===

* @-replies
* [http://hashtags.org/ hashtags]
* [http://buzzword.org.uk/2009/microturtle/spec MicroTurtle]
* [http://microsyntax.org/ microsyntax.org]
* [http://twitterdata.org/ twitterdata.org]
* [http://civilities.net/Star_Priority_Notation Star Priority]

=== Service-Specific ===

* [[actiontastic-syntax | Actiontastic]]
* [[brightkite-syntax| BrightKite]]
* [[dodgeball-syntax| Dodgeball]]
* [[dopplr-syntax | Dopplr]]
* [[facebook-syntax | Facebook Mobile]]
* [[igtd-syntax | iGTD]]
* [[kiboze-syntax|Kiboze]]
* [[jaiku-syntax|Jaiku]]
* [[mixd-syntax | Mixd]]
* [[plazes-syntax | Plazes]]
* [[poi66-syntax | POI66]] - [http://www.poi66.com/maps/step1.php]
* [[quickpack-syntax | QuickPack]]
* [[remember-the-milk | Remember the Milk for Twitter]]
* [[stikkit-syntax | Stikkit]] [http://stikkit.com/]
* [[swaggle-syntax | Swaggle]] [http://swaggle.mobi/]
* [[textmarks-syntax|Textmarks]]
* [[tfl-syntax | Transport for London]]
* [[tripit-syntax | TripIt]]
* [[twitter-syntax | Twitter]]

</div>

== References ==
* [http://www.kiboze.com/kiboze/CustWorks.aspx Kiboze How it Works]
* Flagr: [http://www.flagr.com/help/howto#mobile_creating_flag Creating mobile flags]
* [http://www.dodgeball.com/glossary Dodgeball Glossary]
* [http://twttr.com/t/help/lingo twttr lingo]
* Twitter (or Jaiku) [[twitter-nanoformats]] brainstorm [http://twitternanoformats.wikispaces.com/ A proposal for Twitter nanoformats]
* [http://skobee.com/email_howto Skobee's email syntax]
* [https://www.billmonk.com/about/sms BillMonk syntax]

== concept ==
Thanks to [http://factoryjoe.com/blog Chris Messina] for collecting a bunch of common work in this area, and exploring the area of short semi-structured text for potential "formats" of a sort that could be agreed upon, perhaps among multiple providers to make it easier for users to remember a common user interface.

distributed-conversation-formats

2006-10-02T21:53:04Z

Cloud: Microformats and SIOC

= Distributed Conversation Formats =

== Examples of Related Formats ==
===Email/Usenet===
Email and Usenet both keep track of discussion threads in a non-central manner using headers and references to message IDs. Some common headers and their use are highlighted in [http://www.faqs.org/rfcs/rfc2076.html RFC2076 - Common Internet Message Headers] section 3.6:
* In-Reply-To - Reference to message which this message is a reply to.
* References - In e-mail: reference to other related messages, in Usenet News reference to replied-to-articles.
* See-Also - References to other related articles in Usenet News.
* Obsoletes - Reference to previous message being corrected and replaced.
* Supersedes - Commonly used in Usenet News in similar ways to the "Obsoletes" header described above. In Usenet News, however, Supersedes causes a full deletion of the replaced article in the server, while "Supersedes" and "Obsoletes" in e-mail is implemented in the client and often does not remove the old version of the text.
* Article-Updates - Only in Usenet News, similar to "Supersedes:" but does not cause the referenced article to be physically deleted.
* Article-Names - Reference to specially important articles for a particular Usenet Newsgroup.

===Thread Description Language===
Thread Description Language - TDL is an RDF vocabulary for describing threaded discussions, such as Usenet, weblogs, bulletin boards, and e-mail conversations.
* http://www.eyrie.org/~zednenem/2002/web-threads/
* http://www.eyrie.org/~zednenem/2002/wtprofile/
TDL v3 defines the following properties:
* Property tdl:discusses - Relates a Post to a resource it talks about
* Property tdl:follows - Indicates that this resource comes no earlier than the specified resource
* Property tdl:inThread - Relates a post to a thread which includes it
* Property tdl:mentions - Indicates that this resource refers to the specified resource
* Property tdl:respondsTo - Relates a post to its parent(s) in a discussion
* Property tdl:respondsNegativelyTo - Relates a post to a parent post which it dissents from or corrects
* Property tdl:respondsPositivelyTo - Relates a post to a parent post with which it concurs

'''Discussion of TDL'''

# respondsNegativelyTo, respondsPositivelyTo are beyond the scope of this spec. They can both be implemented using vote-links.
# Without those, respondsTo remains the main connector between posts in a thread.
# mentions and discusses seem to be splitting hairs. It appears that both of them can be replaced by using the CITE tag.
# follows seems to be designed for use in a central registry that tracks threads and therefore is useless for a distributed solution.

===IBIS - Issues Based Information Systems===
Kunz's Issue Based Information Systems (IBIS) provide a framework for collaborative understanding of the major issues and implications surrounding what are described as ``wicked problems'' (problems that lack a definitive formulation). Understanding is achieved by using hypertext components to create structured arguments surrounding the issues. (<cite>[http://www.weblogkitchen.com/wiki.cgi?GraphicalIbis Weblog Kitchen]</cite>)
* [http://dannyayers.com/xmlns/ibis/ IBIS vocabulary]
* [http://collab.blueoxen.net/forums/yak/2003-12/threads.html#00191 How to start an IBIS discussion in Email]
* [http://www.weblogkitchen.com/wiki.cgi?GraphicalIbis graphical IBIS (gIBIS)]
The hypertext model of IBIS consists of three node types:
1. issues
2. positions
3. arguments

Eight link types represent the allowable relationships between these nodes:
1. generalises
2. specialises
3. replaces
4. questions
5. is_suggested_by
6. responds_to
7. objects_to
8. supports

'''Discussion of IBIS'''

Similar to TDL, IBIS seems to tackle a bigger problem than the one discussed here.
* The different node types are not necessary for tracking a discussion thread. Tracking the flow of the conversation, the arguments and flow of ideas is a wider more complex issue than just gluing together disparate pieces of an online discussion.
* Link type such as "generalises" and "specialises" might be useful but seem to require a lot from the user. If we allow for inheritance of link type they could be used as optional parts of the format but it appears that we can do well enough without them.

=== SIOC - Semantically-Interlinked Online Communities ===
SIOC (Semantically Interlinked Online Communities) is an ontology for describing discussion forums and posts on topic threads in online community sites. This includes but is not limited to: blogs, bulletin boards, mailing lists, newsgroups, etc.
* http://sioc-project.org/
* http://rdfs.org/sioc/spec/

Relevant properties defined under [http://rdfs.org/sioc/spec/ SIOC]:
* has_reply - This details replies or responses to this Post, which can be used for purposes of display ordering.
* reply_of - Links to a previous Post, which this Post is a reply of (or to).
* next_version - Links to the next revision of this Post.
* previous_version - Links to a previous revision of this Post.
* has_sibling - A Post may have a sibling or a twin that exists in a different Forum, but the siblings may differ in some small way (for example, language, category, etc.). The sibling of this Post only needs to have the changed information.
* sibling_of - This Post differs from its sibling in some small way. The other sibling can be used as a source for any missing data.
* attachment - A URI of the attachment related to a Post.
* related_to - Related Posts for this Post, perhaps determined implicitly from topics or references.
* is_closed - Details if this (and any children) is closed.

'''Discussion of SIOC'''
* We cannot expect the complementary relations (e.g. has_reply) to exist. This would require a more strongly connected system that we do not assume exists. Similarly for is_closed.
* next_version and previous_version might be an interesting alternative to updates in the case where the author of the updated version has control of the previous version as well. This is not always the case but might happen often enough to include this option.
* The concept of siblings is an interesting one, although the difference between that and update or forward might be too particular for most users.
* attachment might be interesting but is it necessary?
* related_to might be useful in an aggregate environment (think delicious related tags) but otherwise I see those posts use as source citations, so this specific relation type might be pointless.

'''Microformats and SIOC'''

* John Breslin has written a blog post about [http://www.johnbreslin.com/blog/2006/10/02/microformats-and-sioc/ potential connections between mf, cite-rel and SIOC].

== Examples of Use ==
From Email we get two basic relations between message:
* Reply - This message is a reply to the referenced message.
* Forward - This message forwards the referenced message to additional recipients.

From various publications (often of standards) we get:
* Updates/Obsoletes - This documents contains updates or even replaces the referenced document.

Citation of resources comes in several flavors:
* Quote
* Citing a reference
* Via link/Hat tip (mainly in blogs)

User:Cloud

2006-10-02T07:26:21Z

Cloud:

'''[http://www.johnbreslin.com/ John Breslin]''' (AKA ''Cloud'') is a researcher and adjunct lecturer at the [http://www.deri.ie/ Digital Enterprise Research Institute], [http://www.nuigalway.ie/ National University of Ireland, Galway]. He is also leader of the [http://sw.deri.ie/soso Social Software Subcluster] there. He is the author of a number of research publications into the areas of social networks and semantically-enabled online communities (see [http://sioc-project.org/ SIOC]). In September 2004, he was an organiser of the 1st Workshop on Friend Of A Friend, Social Networks and the (Semantic) Web ([http://sw.deri.org/~jbreslin/foaf-galway FOAF Galway]).

John is also co-founder of Ireland's largest discussion community [http://www.boards.ie/ boards.ie]. He has built smaller bulletin board sites for other countries such as Japan ([http://www.boards.jp/ boards.jp]), the US ([http://www.boards.us boards.us]) and New Zealand ([http://www.boards.co.nz boards.co.nz]). In 2005, he set up blog aggregators for both [http://planet.journals.ie Ireland] and [http://planet.journals.co.nz New Zealand], and a multi-user blogging site at [http://journals.ie journals.ie].

==External links==

*[http://www.johnbreslin.com/ John Breslin's Personal Page]
*[http://sw.deri.org/~jbreslin/ John Breslin's Work Page]
*[http://www.johnbreslin.com/blog/ John Breslin's Blog: Cloudlands]
*[http://www.boards.ie/ boards.ie]
*[http://sioc-project.org/ Semantically-Interlinked Online Community Project]

User:Cloud

2006-10-02T07:26:01Z

Cloud:

'''[http://www.johnbreslin.com/ John Breslin]''' (AKA ''Cloud'') is a researcher and adjunct lecturer at the [http://www.deri.ie/ Digital Enterprise Research Institute], [http://www.nuigalway.ie/ National University of Ireland, Galway]. He is also leader of the [http://sw.deri.ie/soso Social Software Subcluster]] there. He is the author of a number of research publications into the areas of social networks and semantically-enabled online communities (see [http://sioc-project.org/ SIOC]). In September 2004, he was an organiser of the 1st Workshop on Friend Of A Friend, Social Networks and the (Semantic) Web ([http://sw.deri.org/~jbreslin/foaf-galway FOAF Galway]).

John is also co-founder of Ireland's largest discussion community [http://www.boards.ie/ boards.ie]. He has built smaller bulletin board sites for other countries such as Japan ([http://www.boards.jp/ boards.jp]), the US ([http://www.boards.us boards.us]) and New Zealand ([http://www.boards.co.nz boards.co.nz]). In 2005, he set up blog aggregators for both [http://planet.journals.ie Ireland] and [http://planet.journals.co.nz New Zealand], and a multi-user blogging site at [http://journals.ie journals.ie].

==External links==

*[http://www.johnbreslin.com/ John Breslin's Personal Page]
*[http://sw.deri.org/~jbreslin/ John Breslin's Work Page]
*[http://www.johnbreslin.com/blog/ John Breslin's Blog: Cloudlands]
*[http://www.boards.ie/ boards.ie]
*[http://sioc-project.org/ Semantically-Interlinked Online Community Project]

irc

2006-10-02T07:19:35Z

Cloud: /* People on irc */

__NOTOC__
= Microformats IRC =

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

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

== People on irc ==
A list of IRC regulars and their normal timezones. (winter/summer)

* [[User:BenWest|bewest]] (-0800/-0700)
* [[User:Adam Craven|AdamCraven]] (+0000)
* [[User:Amette|amette]] (+1000)
* [[User:B.K._DeLong|bkdelong]] (-0500/-0400)
* [[User:Ben Ward|BenWard]] (+0000)
* [[User:BenjaminCarlyle|BenjaminCarlyle]] (+1000)
* [[User:Boneill|boneill]] (+0000)
* [[User:Brian|briansuda]] (+0000)
* [[User:ColinDDevroe|cdevroe]] (-0500/-0600)
* [[User:Cgriego|cgriego]] (-0600/-0500)
* [[User:ChrisCasciano|pnhChris]] (-0500/-0400)
* [[User:ChrisMessina|factoryjoe]] (-0800/-0700)
* [[User:ChristopherStJohn|cks]] (-0600/-0500)
* [[User:Cloud|Cloud]] (+0000)
* [[User:DanC|DanC]] (-0600/-0500)
** office hours: Wednesday afternoons, America/Chicago time
* [[User:Dave Cardwell|davecardwell]] (+0000)
* [[User:DeanEro|deanero]] (-0800/-0700)
* [[User:DimitriGlazkov|dglazkov]] (-0600/-0500)
* [[User:DrewMcLellan|drewinthehead]] (+0000/+0100)
* [[User:EdwardOConnor|hober]] (-0800/-0700)
* [[User:Enric|enric]] (-0800/-0700)
* [[User:Evan|evanpro]] (-0500)
* [[User:Fil|Fil]] (+0200)
* [[User:Grantbow|Grantbow]] (-0800/-0700)
* [[User:Hlb|hlb]] (+0800-0700)
* [[User:IanHickson|Hixie]] (-0800/-0700)
* [[User:Izo|IZO]]
* [[User:JoeGregorio|jcgregorio]]
* [[User:Jonathan_Arkell|jonnay]] (-0700/0600)
* [[User:Keri Henare|kerihenare]] (+1200)
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)
* [[User:Mark Mansour|Mark Mansour]] (+1100)
* [[User:MarkNormanFrancis|Mark Norman Francis]] (+0000/+0100)
* [[User:neuro|neuro`]]
* [[User:Phae|Phae]] (+0000/+0100)
* [[User:PriitLaes|plaes]] (+0200/+0300)
* [[User:DavidOsolkowski|qid]] (-0500)
* [[User:Remi|Remi]] (-0500/-0400)
* [[User:RobertBachmann|RobertBachmann]] (+0100/+0200)
** Office hours: <del>Wednesday, 18:00-20:00 UTC</del> (Currently no office hours)
* [[User:RyanKing|kingryan]] (-0800/-0700)
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC
* [[User:Csarven|csarven]] (-0500/-0400)
* [[User:Dana Benson|Snowden]] (-0800/-0700)
* [[User:Steve Ganz|SteveGanz]] (-0800/-0700)
* [[User:Tantek|Tantek]] (-0800/-0700)
* [[User:Trovster|trovster]] (-0800/-0700)
* [[User:Dan Kubb|dkubb]] (-0800/-0700)
* [[User:Ed Summers|edsu]] (-0500/-0400)
* [[User:Smackman|Steve Farrell]] (-0800/-0700)
* [[User:Enric|Enric]] (-0800/-0700)
* [[User:Charlvn|Charl]] (+0200/+0200)
* [[User:MarkoMrdjenovic|friedcell]] (+0100/+0200)
* [[User:Vant|vant]] (+0900)
* [[User:KrissWatt|VoodooChild]] (+0000/+0100)
* [[User:IwaiMasaharu|iwaim]] (+0900)
* [[User:Richard Conyard|WhiskeyM]] (+0000)
* [[User:Veeliam|William Lawrence]] (-0800/-0700)
* [[User:Ianloic|yakk]] (-0800/-0700)

=== Greetings ===

To display a brief description of who you are each time you join the channel, you can create a definition for your username. To do so pass the <tt>?def</tt> command using something like the following convention (be brief):

<code>?def jdoe is John Doe and can be found online at <nowiki>http://www.example.com</nowiki></code>

More information about using JiBot commands can be found on the [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot website]

=== bots ===

* [[mfbot]]
* [[mflogbot]]
* [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot]

== Logs ==

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

Atom feed of logs available here: http://microformat.makedatamakesense.com/log_feed/

== IRC meetups ==

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

irc

2006-10-02T07:19:09Z

Cloud:

__NOTOC__
= Microformats IRC =

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

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

== People on irc ==
A list of IRC regulars and their normal timezones. (winter/summer)

* [[User:BenWest|bewest]] (-0800/-0700)
* [[User:Adam Craven|AdamCraven]] (+0000)
* [[User:Amette|amette]] (+1000)
* [[User:B.K._DeLong|bkdelong]] (-0500/-0400)
* [[User:Ben Ward|BenWard]] (+0000)
* [[User:BenjaminCarlyle|BenjaminCarlyle]] (+1000)
* [[User:Boneill|boneill]] (+0000)
* [[User:Brian|briansuda]] (+0000)
* [[User:ColinDDevroe|cdevroe]] (-0500/-0600)
* [[User:Cgriego|cgriego]] (-0600/-0500)
* [[User:ChrisCasciano|pnhChris]] (-0500/-0400)
* [[User:ChrisMessina|factoryjoe]] (-0800/-0700)
* [[User:ChristopherStJohn|cks]] (-0600/-0500)
* [[User:Cloud]] (+0000)
* [[User:DanC|DanC]] (-0600/-0500)
** office hours: Wednesday afternoons, America/Chicago time
* [[User:Dave Cardwell|davecardwell]] (+0000)
* [[User:DeanEro|deanero]] (-0800/-0700)
* [[User:DimitriGlazkov|dglazkov]] (-0600/-0500)
* [[User:DrewMcLellan|drewinthehead]] (+0000/+0100)
* [[User:EdwardOConnor|hober]] (-0800/-0700)
* [[User:Enric|enric]] (-0800/-0700)
* [[User:Evan|evanpro]] (-0500)
* [[User:Fil|Fil]] (+0200)
* [[User:Grantbow|Grantbow]] (-0800/-0700)
* [[User:Hlb|hlb]] (+0800-0700)
* [[User:IanHickson|Hixie]] (-0800/-0700)
* [[User:Izo|IZO]]
* [[User:JoeGregorio|jcgregorio]]
* [[User:Jonathan_Arkell|jonnay]] (-0700/0600)
* [[User:Keri Henare|kerihenare]] (+1200)
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)
* [[User:Mark Mansour|Mark Mansour]] (+1100)
* [[User:MarkNormanFrancis|Mark Norman Francis]] (+0000/+0100)
* [[User:neuro|neuro`]]
* [[User:Phae|Phae]] (+0000/+0100)
* [[User:PriitLaes|plaes]] (+0200/+0300)
* [[User:DavidOsolkowski|qid]] (-0500)
* [[User:Remi|Remi]] (-0500/-0400)
* [[User:RobertBachmann|RobertBachmann]] (+0100/+0200)
** Office hours: <del>Wednesday, 18:00-20:00 UTC</del> (Currently no office hours)
* [[User:RyanKing|kingryan]] (-0800/-0700)
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC
* [[User:Csarven|csarven]] (-0500/-0400)
* [[User:Dana Benson|Snowden]] (-0800/-0700)
* [[User:Steve Ganz|SteveGanz]] (-0800/-0700)
* [[User:Tantek|Tantek]] (-0800/-0700)
* [[User:Trovster|trovster]] (-0800/-0700)
* [[User:Dan Kubb|dkubb]] (-0800/-0700)
* [[User:Ed Summers|edsu]] (-0500/-0400)
* [[User:Smackman|Steve Farrell]] (-0800/-0700)
* [[User:Enric|Enric]] (-0800/-0700)
* [[User:Charlvn|Charl]] (+0200/+0200)
* [[User:MarkoMrdjenovic|friedcell]] (+0100/+0200)
* [[User:Vant|vant]] (+0900)
* [[User:KrissWatt|VoodooChild]] (+0000/+0100)
* [[User:IwaiMasaharu|iwaim]] (+0900)
* [[User:Richard Conyard|WhiskeyM]] (+0000)
* [[User:Veeliam|William Lawrence]] (-0800/-0700)
* [[User:Ianloic|yakk]] (-0800/-0700)

=== Greetings ===

To display a brief description of who you are each time you join the channel, you can create a definition for your username. To do so pass the <tt>?def</tt> command using something like the following convention (be brief):

<code>?def jdoe is John Doe and can be found online at <nowiki>http://www.example.com</nowiki></code>

More information about using JiBot commands can be found on the [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot website]

=== bots ===

* [[mfbot]]
* [[mflogbot]]
* [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot]

== Logs ==

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

Atom feed of logs available here: http://microformat.makedatamakesense.com/log_feed/

== IRC meetups ==

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

faqs-for-rdf

2005-11-09T11:47:26Z

Cloud: /* Who else is looking at RDF and microformats? */

= FAQs for RDF Fans =

__TOC__

==== What are Microformats? ====

Microformats are a set of simple, open data formats built upon existing and widely adopted standards, in particular XHTML used ''correctly''. The processes, principles, and practices of the (open) microformats group are what make microformats "microformats", but they centre on using XHTML as designed, as a semantic language (though they can also be implemented on other XML formats, e.g. Atom).

Although the microformats initiative puts human-readability first, with the help of the [http://www.w3.org/2004/01/rdxh/spec GRDDL] mechanism, it is possible to view microformats as domain-specific [http://www.w3.org/RDF/ RDF] serializations.

See also: [http://microformats.org/about/ About Microformats]

==== For example..? ====

This [http://microformats.org/wiki/hcard-example1-steps example] shows how the hCard microformat can be used to express vCard data.

==== But I do RDF, why should I be interested? ====

Microformats can lower the barrier to putting explicit data on the Web. This is entirely in line with the aims of the [http://www.w3.org/2001/sw/ Semantic Web].

Dan Connolly [http://lists.w3.org/Archives/Public/www-rdf-interest/2000Mar/0103 rdf-interest, March 2000]:
<blockquote>
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?
</blockquote>

==== I have an RDF vocabulary I would like to use as a microformat. How do I do it? ====

Before doing anything else, read the [http://microformats.org/wiki/process Process]. In general the microformat process is data-driven. It starts with material already being published, rather than an existing format, model or schema. You should also check the list of what has already been covered and the work-in-progress on the Wiki MainPage.

It may well be that what you have in mind isn't appropriate for use as a microformat, but it may still be a good idea to develop a (semantic) XHTML representation. Existing microformats demonstrate a standards-friendly way of doing this.

See also: [http://tantek.com/presentations/2005/03/elementsofxhtml/ The Elements of Meaningful XHTML]

==== So, this is about using CSS class values to add semantics? ====

No. XHTML already expresses semantics, the '''HTML''' <code>class</code> attribute is just one of several mechanisms. From the [http://www.w3.org/TR/REC-html40/ HTML 4 spec]:

<blockquote>
The class attribute, on the other hand, assigns one or more class names to an element; the element may be said to belong to these classes.
</blockquote>

See also: [http://www.microformats.org/blog/2005/10/19/more-than-styling/ Class attributes are about more than styling]

==== What about namespaces for the attributes, should I use "xxx:term"? ====

In general, microformats rejects the use of explicit namespace prefixes in
documents as unnecessary for solving the 80/20 of problems that microformats
seeks to solve. The general approach taken is not to attempt to generalise to the extent of [http://research.talis.com/2005/erdf/wiki/Main/RdfInHtml RDF-in-HTML], rather to define more domain-specific formats.

==== But won't there be naming clashes? ====

The social aspect of the microformats [http://microformats.org/wiki/process Process] is such that conflicts ought to be prevented. The goal is to keep things as simple as possible by only focusing on '''existing''' well-defined problems, rather than trying to "boil the ocean" (solve the hypothetical general case).

==== So how do I get the data out? ====

See [http://www.w3.org/2004/01/rdxh/spec GRDDL]

==== Isn't there a clash between the semantics of XFN and FOAF? ====

The use of the page URI in XFN to identify a person appears to conflict with FOAF's by-reference approach, and to mess up the potential for saying things about the page itself. However in practice this isn't a problem. It's possible to parse the document as XFN (using e.g. [http://www.w3.org/2003/12/rdf-in-xhtml-xslts/grokXFN.xsl grokXFN.xsl]) to extract the person-related statements, e.g.
<pre>
_:personA foaf:homepage <http://example.org/this-page> .
_:personA foaf:knows _:personB .
_:personB foaf:homepage <http://example.org/linked-page> .
</pre>
- and ''independently'' parse the document using other format mappings (e.g. [http://www.w3.org/2000/06/dc-extract/dc-extract.xsl dc-extract.xsl]) to obtain other statements, e.g.
<pre>
<http://example.org/this-page> dc:creator "The Creator" .
</pre>

See also: [http://www.w3.org/2003/g/td/xfn-workalike XFN on the GRDDL], [http://www.oreillynet.com/pub/wlg/8281 XFN Delusions of Grandeur], [http://www.microformats.org/blog/2005/11/02/xfn-grandeur/ XFN Grandeur], [http://dannyayers.com/archives/2005/11/03/xfn-vs-foaf/ XFN vs. FOAF]

==== What other work has been done with microformats and RDF? ====

* [http://www.w3.org/2003/g/td/xfn-workalike XFN on the GRDDL]
* [http://people.w3.org/~dom/archives/2005/05/grddl-specification-updated/ GRDDL specification updated works with Microformats]

==== Are there Schemas for Microformats? ====

Kind of. The primary specification is XHTML, but HTML4 provides a mechanism (the 'profile' attribute of the <head> element) to point to a meta data profile that defines properties and values. There is a (HTML-based) format specified for microformat profiles - [http://www.gmpg.org/xmdp/ XHTML Meta Data Profiles]. Note that XMDP's URLs for specifying terms is compatible with those used by RDF, with "#term" at the end.

==== What RDF vocabularies (and XSLT) corresponding to microformats is available? ====

See [http://esw.w3.org/topic/MicroModels MicroModels] (on ESW Wiki)

==== Isn't this just scraping? ====

No. Because microformats (should) include URI(s) for every profile used, and the profiles are clearly defined, the explicit data contained in a document can be extracted deterministically by parsing.

==== Who else is looking at RDF and microformats? ====

Lots of folks.
Including: [http://www.w3.org/People/Connolly/ Dan Connolly], [http://internetalchemy.org/ Ian Davis], [http://sw.deri.org/~jbreslin/ John Breslin], [http://dannyayers.com Danny Ayers]....

==== How do I get involved? ====

If you're using the Web, you already *are* involved! Next place to go is the [http://microformats.org/ microformats.org] site, and maybe sign up to some of the [http://microformats.org/discuss/ mailing lists] (in particular [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss]). There's also an IRC channel [irc://irc.freenode.net#microformats #microformats on irc.freenode.net].

hatom

2005-11-07T16:02:47Z

Cloud: /* Similar Work */

= hAtom =

hAtom is a microformat for content that can be syndicated, primarily but not exclusively weblog postings. hAtom is a strongly based on a subset of the [http://www.atomenabled.org/ Atom] syndication format; every concept in hAtom has a corresponding definition in Atom.

This microformat is a draft; please address your concerns, issues, comments, etc. in [[hatom-issues]].

__TOC__

== Draft Specification ==

=== Editor ===
* [http://blogmatrix.blogmatrix.com/ David Janes], [http://www.blogmatrix.com BlogMatrix, Inc.]

=== Authors ===
* [http://blogmatrix.blogmatrix.com/ David Janes], [http://www.blogmatrix.com BlogMatrix, Inc]

=== Copyright ===
{{MicroFormatCopyrightStatement2005}}

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

== Introduction ==

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

== Format ==
=== In General ===

=== Schema ===
Schema elements are based on the Atom nomenclature and follow the microformat pattern of prefixing a unique identifier (in this case, <code>atom</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]]. Note the renaming of 'EntryGroup' to 'Feed' to be more consistent with Atom ternminology.

==== Nomenclature ====

{| width="100%" border="1" cellspacing="0"
|-
! width="150" | Concept
! Atom Identifier
! hAtom Microformat Usage
|-
| Feed
| <code>atom:feed</code>
| add <code>class="atomfeed"</code>; OR implicit in the XHTML page
|-
| Feed Title
| <code>atom:title</code>
| ''Not defined in the first iteration of this proposal.''
|-
| Feed Permalink
| <code>atom:link@rel=alternate</code>
| ''Not defined in the first iteration of this proposal.''
|-
| Entry
| <code>atom:entry</code>
| Add <code>class="atomentry"</code>; if practical, also define <code>id="unique-identifier"</code> to the Entry.
|-
| Entry Title
| <code>atom:title</code>
| Use <code><h#></code> in block elements; OR non-preferentially add <code>class="title"</code> in inline elements.
|-
| Entry Content
| <code>atom:content</code>
| Add <code>class="content"</code> to all appropriate blocks. Multiple Entry Content blocks are logically considered one concatenated <code>atom:content</code> equivalent.
|-
| Entry Summary
| <code>atom:summary</code>
| Add <code>class="summary"</code> to all appropriate blocks. Multiple Entry Summary blocks are logically considered one concatenated <code>atom:summary</code> equivalent.
|-
| Entry Permalink
| <code>atom:link</code>
| Add <code>rel="bookmark"</code>.
|-
| Entry Published
| <code>atom:published</code>
| Use <code><abbr class="published" title="YYYYMMYYThh:mm:ss±ZZ:ZZ"></code>...<code></abbr></code>, following the [[datetime-design-pattern]].
|-
| Entry Author
| <code>atom:author</code>
| Use <code><address class="author"></code>...<code></address></code>. Adding a [[hcard|hCard]] is highly recommended.
|}

==== Nesting Rules ====

{| width="100%" border="1" cellspacing="0"
|-
! Concept
! Nests In
! hAtom Opaque
! Cardinality
! Logical Cardinality
|-
| Feed
| HTML document
| No
| 0-N
| 1
|-
| Entry
| Feed<br />HTML document
| No
| 0-N
| 0-N
|-
| Entry Title
| Entry<br />Entry Permalink
| No
| 0-N
| 0-1
|-
| Entry Content
| Entry
| Yes
| 0-N
| 0-1
|-
| Entry Summary
| Entry
| Yes
| 0-N
| 0-1
|-
| Entry Permalink
| Entry<br />Entry Title<br />Entry Published
| No
| 0-N
| 1
|-
| Entry Published
| Entry<br />Entry Permalink
| No
| 0-N
| 0-1
|-
| Entry Author
| Entry
| Yes
| 0-N
| 0-N
|}

===== hAtom Opaque =====

"hAtom Opaque" specifies whether a hAtom parser should "look inside" the element for further hAtom content. If there are multiple rules applied to the same element take the OR of the two (i.e. "Yes" always wins)

: ''hAtom Opaque is designed to make parsing rules less ambiguous. In particular, it allows "quoted" hAtom elements (from another blog being blockquoted, for example) ti be ignored. It also allows 'embedded' hAtom to be potentially delivered within hAtom itself, and to prevent accidental 'leaking' of other microformat information up into the hAtom container.''

===== Cardinality =====

How many times can an element of the given type appear in it's nesting element in the XHTML document.

===== Logical Cardinality =====

From a modeling/logical perspective, how many times can an element appear.

: ''This is all rule dependent, see below. For example, an Entry Permalink may appear 6 times, but each one must be the same value; an Entry Content element may appear 3 times, but they are all concatenated together to make a single logical element.''

==== Rules and Definitions ====
See the [[#Nesting_Rules|Nesting Rules]] section above for placement of these elements.

===== Feed =====
* an XHTML Feed element is identified by <code>class="atomfeed"</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]
: ''In particular, as a container for Entrys.''
* if there is no Feed element on a page, the "logical Feed" is assumed to be the XHTML document
* hAtom documents MAY have multiple, non-nested Feed elements
: ''This may happen on news pages, or weblogs with "mini-blogs" on the sidebar.''

===== Entry =====
* an Entry element is identified by <code>class="atomentry"</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]
* a weblog entry MUST be enclosed in a single Entry element
: ''That's what it's for, after all.''
* an Entry MUST NOT belong to more than one Feed element
: ''That is, an Entry belongs to 0 or 1 Feeds.''
* an Entry SHOULD have an enclosing Feed element

===== Entry Title =====
* an Entry Title element is identified <code><h#></code> in block elements OR non-preferentially <code>class="title"</code> in inline elements
* 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]

====== Disambiguation ======

* the first hAtom valid <code><h#></code> element to appear in an hAtom document is the Entry Title
* otherwise, the first hAtom valid non-<code><abbr></code> element with a <code>class="title"</code> is the Entry Title
: ''hAtom valid meaning somewhere where we expect it (like not inside Entry Content, for example).''
* otherwise, the Entry Title is the empty string
: ''Atom does not allow for an entry not to have a title.''

===== Entry Content =====
* an Entry Content element is identified by <code>class="content"</code>
* 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
: ''We recognize this varies from the Atom spec: see the next rule.''
* the "logical Entry Content" of an Entry is the concatenation, in order of appearance, of all the Entry Contents within the Entry
: ''Many weblogs split content into multiple sections with a "Read More" link and javascript tricks. This is also needed in cases where Entry Titles are coded inline and are considered part of the content.''
* the "logical Entry Content" MUST be complete; that is, contain the entire content of the Entry
: ''Otherwise it should be marked as Entry Summary.''

===== Entry Summary =====
* an Entry Summary element is identified by <code>class="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
: ''We recognize this varies from the Atom spec: see the next rule.''
* the "logical Entry Summary" of an Entry is the concatenation, in order of appearance, of all the Entry Summarys within the Entry
* the "logical Entry Summary" may differ in different copies of the Entry
: ''There is the major difference with Entry Content. We can summarize an Entry in different way in different places with no requirement for consistency. There may be issues with this for modelers: if so, take it up in [[hatom-issues]].''

===== Entry Permalink =====

* an Entry Permalink element is identified by <code>rel="bookmark"</code>
: ''We recognize that we have broken from Atom terminology at this point. See [[hatom-issues]] for discussion.''
: ''This may be a microformat in itself: [[rel-bookmark]].''
* 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]
* Entry Permalinks MUST be absolute URIs
* Entry Permalinks MUST be the same as the <code>atom:link</code> (or <code>rss:link</code>) used in syndication feeds
: ''The intention of the previous two rules to gently force people to use strings that can be byte compared for equivalence. In general, the canonical URI should be the link used in an Atom entry.''
: ''Is there a problem with FeedBurner?''
* if an Entry has multiple elements marked as the Entry Permalink, they MUST have exactly the same URI
* an Entry SHOULD have an Entry Permalink
: ''There are circumstances (should as media pages) where this won't happen. See the next rule.''
* there can be at most 1 Entry in an XHTML document without an Entry Permalink; the Entry Permalink of this Entry is the URI of the page
: ''This rule is needed for media pages (i.e. a news article on cnn.com). There is some ugliness of with this because the URI could be non-canonical.''

====== Disambiguation ======

* The first valid element in an Entry marked as an Entry Permalink is the Entry Permalink

===== Entry Published =====

* an Entry Published element is identified by <code>class="published"</code>
* a Entry Published element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.9 atom published]
* the machine readable datetime should be encoded with an <code><abbr></code> element using the [[datetime-design-pattern]]; the machine readable datetime should be complete, that is, specified to the second with the timezone included

====== Disambiguation ======

* The first valid element in an Entry marked as an Entry Published is the Entry Published element

===== Entry Author =====
IN PROGRESS OF BEING WRITTEN

* an Entry Author element is identified by <code>class="author"</code>
* a 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]

=== XMDP Profile ===

=== Parsing Details ===

== Examples ==

This section is informative.

=== Transformation 1 ===

A well behaved weblog.

Original:

<pre><nowiki>
<body>
<div id="wrap">
<div id="content">
...
<div class="entry">
<h3 id="post-60">
<a href="http://www.microformats.org/blog/..." rel="bookmark" title="...">Wiki Attack</a>
</h3>
<p>We had a bit of trouble with ...</p>
<p>We’ve restored the wiki and ...</p>
<p>If anyone is working to combat said spammers ...</p>

<h4 class="tags">Technorati Tags:</h4>
<ul class="tags">
<li><a href="http://technorati.com/tag/mediawiki" rel="tag">mediawiki</a></li>
<li><a href="http://technorati.com/tag/microformats" rel="tag">microformats</a></li>
<li><a href="http://technorati.com/tag/spam" rel="tag">spam</a></li>
</ul>

<ul class="post-info">
<li>
<a href="http://www.microformats.org/blog/..." rel="bookmark" title="...">October 10th, 2005</a>
</li>
<li>
<address class="vcard"><a class="url fn" href="http://theryanking.com">Ryan King</a></address>
</li>
<li>
<a href="http://www.microformats.org/blog/...">4 Comments</a>
</li>
</ul>
</div>

<div class="entry">
....
</div>
...
</div>
</div>
</body>
</nowiki></pre>

Transformed to hAtom compliant (shown in UPPER CASE for visibility only):

<pre><nowiki>
<body>
<div id="wrap">
<div id="ATOMFEED content">
...
<div class="ATOMENTRY entry" ID="post-60">
<h3>
<a href="http://www.microformats.org/blog/..." rel="bookmark" title="...">Wiki Attack</a>
</h3>
<DIV CLASS="CONTENT">
<p>We had a bit of trouble with ...</p>
<p>We’ve restored the wiki and ...</p>
<p>If anyone is working to combat said spammers ...</p>
</DIV>

<h4 class="tags">Technorati Tags:</h4>
<ul class="tags">
<li><a href="http://technorati.com/tag/mediawiki" rel="tag">mediawiki</a></li>
<li><a href="http://technorati.com/tag/microformats" rel="tag">microformats</a></li>
<li><a href="http://technorati.com/tag/spam" rel="tag">spam</a></li>
</ul>

<ul class="post-info">
<li>
<a href="http://www.microformats.org/blog/..." rel="bookmark"
title="..."><ABBR CLASS="PUBLISHED" TITLE="20051010T14:07:00-0700">October 10th, 2005</ABBR></a>
</li>
<li>
<address class="vcard"><a class="url fn" href="http://theryanking.com">Ryan King</a></address>
</li>
<li>
<a href="http://www.microformats.org/blog/...">4 Comments</a>
</li>
</ul>
</div>

<div class="entry entry" ID="post-59">
....
</div>
...
</div>
</div>
</body>
</nowiki></pre>

Changes:
* Added <code>class="feed"</code> to Feed
* Added <code>class="entry"</code> to each Entry
* Moved <code>id="###"</code> from <code><h3></code> to Entry
* Added <code><div class="content"></code>...<code></div></code> around the Entry Content
* Added <code><abbr class="PUBLISHED" title="YYYYMMDDThh:mm:ss+ZZZZ"></code>...<code></abbr></code> around the Entry Datetime

Also note:
* We did not need to add a <code><address></code> element
* We did not need to add a <code><h#></code> element
* We did not need to add a <code>rel="link"</code> to Entry Permalinks

=== Transformation 2 ===

A not-so well behaved weblog (an older blogspot weblog)

Original:

<pre><nowiki>
<body bgcolor="...">

<div class="posts">
<a name="112993192128302715"> </a><br>
<div style="clear:both;"></div><strong>Nelson's final prayer</strong>
written on the night before Trafalgar:<blockquote>May the Great God, ... heart.
<div style="clear:both; padding-bottom: 0.25em;"></div>
<br>
<span class="byline">
posted by Natalie at
<a href="2005_10_16_nataliesolent_archive.html#112993192128302715">9:49 PM</a>
</span>
</div>

<div class="posts">
<a name="112993022840118939"> </a>
<br>
<div style="clear:both;"></div><strong>I really, truly </strong>didn't go ... view.
<div style="clear:both; padding-bottom: 0.25em;"></div>
<br>
<span class="byline">
posted by Natalie at
<a href="2005_10_16_nataliesolent_archive.html#112993022840118939">9:28 PM</a>
</span>
</div>
...

</body>
</nowiki></pre>

Transformed to hAtom compliant (shown in UPPER CASE for visibility only):

<pre><nowiki>
<body bgcolor="...">

<DIV CLASS="ATOMFEED">
<div class="ATOMENTRY posts" ID="112993192128302715">
<strong CLASS="TITLE CONTENT">
Nelson's final prayer
</strong>
<SPAN CLASS="CONTENT">
written on the night before Trafalgar:<blockquote>May the Great God, ... heart.
</SPAN>
<DIV>
<span class="byline">posted by <address>Natalie</address> at
<a REL="LINK" href="HTTP://NATALIESOLENT.BLOGSPOT.COM/2005_10_16_nataliesolent_archive.html#112993192128302715">
<ABBR CLASS="POSTED" TITLE="20051024T094900-0000">9:49 PM</ABBR></a>
</span>
</DIV>
</div>

<div class="entry posts" ID="112993022840118939">
<strong CLASS="TITLE CONTENT">I really, truly </strong>
<SPAN CLASS="CONTENT">
didn't go ... view.
</SPAN>
<DIV>
<span class="byline">
posted by <address>Natalie</address> at
<a REL="LINK" href="HTTP://NATALIESOLENT.BLOGSPOT.COM/2005_10_16_nataliesolent_archive.html#112993022840118939">
<ABBR CLASS="POSTED" TITLE="20051024T094900-0000">9:28 PM</ABBR></a>
</span>
</DIV>
</div>
...
</DIV>

</body>
</nowiki></pre>

Changes:
* Added <code>class="feed"</code> to Feed
* Added <code>class="entry"</code> to each Entry
* Moved <code>id="###"</code> up to the Entry (and deleted the empty anchor block)
* Added <code>rel="link"</code> to the Entry Permalinks
* Made the Entry Permalink non-relative
* Added <code><span class="title"></code>...<code></div></code> around the Entry Title
* Added <code><span class="content"></code>...<code></div></code> around the Entry Title (!)
* Added <code><span class="content"></code>...<code></div></code> around the Entry Content
* Added <code><abbr class="posted" title="YYYYMMDDThh:mm:ss+ZZZZ"></code>...<code></abbr></code> around the Entry Datetime
* Added <code><address></code> to the poster's name

Also note:
* there are multiple content blocks, because Natalie Solent embeds the title in the content
* cleaned up lots of crap HTML presentation stuff, with the assumption it would be fixed in the stylesheet
* this is one of the uglier transformations you're likely to see

=== Transformation 3 ===

A media page.

Original:

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

Transformed to hAtom compliant:

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

Changes:
*

=== Transformation 4 ===

A bulletin board ([http://forums.punbb.org/viewtopic.php?id=9135 PunBB])

Original:

<pre><nowiki>
<body>
<div id="punwrap">
<div id="punviewtopic" class="pun">

<div id="brdheader" class="block">
... header stuff ...
</div>

<div id="announce" class="block">
... announcement stuff ...
</div>

<div class="linkst">
... controls for the blog
</div>

<div id="p54390" class="blockpost rowodd firstpost">
<h2>
<span><span class="conr">#1 </span>
<a href="viewtopic.php?pid=54390#p54390">2005-10-16 10:36:24</a></span>
</h2>
<div class="box">
<div class="inbox">
<div class="postleft">
<dl>
<dt><strong><a href="profile.php?id=2">Rickard</a></strong></dt>

<dd class="usertitle"><strong>PunBB Developer</strong></dd>
<dd class="postavatar"><img src="img/avatars/2.png" width="60" height="60" alt="" /></dd>
<dd>From: 127.0.0.1</dd>
<dd>Registered: 2001-11-02</dd>
<dd>Posts: 7806</dd>
<dd class="usercontacts"><a href="http://www.punbb.org/">Website</a></dd>

</dl>
</div>
<div class="postright">
<h3>PunBB 1.2.9</h3>
<div class="postmsg">
<p>Just a quick note this time....</p>

</div>
<div class="postsignature"><hr />"Programming is like sex: ...</div>
</div>
<div class="clearer"></div>
<div class="postfootleft"><p>Offline</p></div>
<div class="postfootright"><div> </div></div>
</div>
</div>

</div>

<div id="p54392" class="blockpost roweven">
<h2><span><span class="conr">#2 </span><a href="viewtopic.php?pid=54392#p54392">2005-10-16 10:54:41</a></span></h2>
<div class="box">
<div class="inbox">
<div class="postleft">
<dl>
<dt><strong><a href="profile.php?id=5298">IdleFire</a></strong></dt>

<dd class="usertitle"><strong>Member</strong></dd>
<dd class="postavatar"></dd>
<dd>Registered: 2005-10-14</dd>
<dd>Posts: 27</dd>
</dl>
</div>
<div class="postright">

<h3> Re: PunBB 1.2.9</h3>
<div class="postmsg">
<p>...</p>
</div>
</div>
<div class="clearer"></div>
<div class="postfootleft"><p>Offline</p></div>

<div class="postfootright"><div> </div></div>
</div>
</div>
</div>

... more entries ...

<div id="brdfooter" class="block">
... footer stuff ...
</div>

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

Transformed to hAtom compliant (changes shown in UPPER CASE for visibility only):

<pre><nowiki>
<body>
<div id="punwrap">
<div id="punviewtopic" class="pun">

<div id="brdheader" class="block">
... header stuff ...
</div>

<div id="announce" class="block">
... announcement stuff ...
</div>

<div class="linkst">
... controls for the blog
</div>

<div id="p54390" class="ATOMENTRY blockpost rowodd firstpost">
<h2>
<span><span class="conr">#1 </span>
<a REL="BOOKMARK" href="HTTP://FORUMS.PUNBB.ORG/viewtopic.php?pid=54390#p54390">
<ABBR CLASS="POSTED" TITLE="20051016T103624-0500">2005-10-16 10:36:24</ABBR>
</a></span>
</h2>
<div class="box">
<div class="inbox">
<div class="postleft">
<dl>
<dt><strong><ADDRESS><a href="profile.php?id=2">Rickard</a></ADDRESS></strong></dt>

<dd class="usertitle"><strong>PunBB Developer</strong></dd>
<dd class="postavatar"><img src="img/avatars/2.png" width="60" height="60" alt="" /></dd>
<dd>From: 127.0.0.1</dd>
<dd>Registered: 2001-11-02</dd>
<dd>Posts: 7806</dd>
<dd class="usercontacts"><a href="http://www.punbb.org/">Website</a></dd>

</dl>
</div>
<div class="postright">
<h3>PunBB 1.2.9</h3>
<div class="CONTENT postmsg">
<p>Just a quick note this time....</p>

</div>
<div class="postsignature"><hr />"Programming is like sex: ...</div>
</div>
<div class="clearer"></div>
<div class="postfootleft"><p>Offline</p></div>
<div class="postfootright"><div> </div></div>
</div>
</div>

</div>

<div id="p54392" class="ATOMENTRY blockpost roweven">
<h2>
<span><span class="conr">#2 </span>
<a REL="BOOKMARK" href="HTTP://FORUMS.PUNBB.ORG/viewtopic.php?pid=54392#p54392">
<ABBR CLASS="POSTED" TITLE="20051016T1105441-0500">2005-10-16 10:54:41</ABBR>
</a></span>
</h2>
<div class="box">
<div class="inbox">
<div class="postleft">
<dl>
<dt><strong><ADDRESS><a href="profile.php?id=5298">IdleFire</a></ADDRESS></strong></dt>

<dd class="usertitle"><strong>Member</strong></dd>
<dd class="postavatar"></dd>
<dd>Registered: 2005-10-14</dd>
<dd>Posts: 27</dd>
</dl>
</div>
<div class="postright">

<h3> Re: PunBB 1.2.9</h3>
<div class="CONTENT postmsg">
<p>...</p>
</div>
</div>
<div class="clearer"></div>
<div class="postfootleft"><p>Offline</p></div>

<div class="postfootright"><div> </div></div>
</div>
</div>
</div>

... more entries ...

<div id="brdfooter" class="block">
... footer stuff ...
</div>

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

Changes:
*

Notes:
*

Questions:
* should the <code>address</code> enclose the entire author block?

=== More Examples ===

See [[hatom-examples]].

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

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

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.atomenabled.org/ Atom]

=== Informative References ===

==== Specifications That Use hAtom ====

==== Similar Work ====

* [http://rdfs.org/sioc/ Semantically-Interlinked Online Communities (SIOC) RDF Ontology]

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

== 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 [[htom-issues|hAtom issues]] document.

==See Also==
* [[hatom|hAtom]] - the draft proposal
* [[hatom-issues]] - problems? complaints? ideas? Put them here
* [[hatom-faq]] - knowledge base
* [[blog-post-brainstorming]]
* [[blog-post-formats]]
* [[blog-post-examples]]
* [[blog-description-format]] - how to describe a blog (as opposed to the individual entries, which is what we're doing here)