articles: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
(looks liked twitter broke /user/favourites (en-GB spelling))
(→‎2012: Emily Lewis on the future of microformats)
Line 13: Line 13:
Copy and paste this template to create new news items:
Copy and paste this template to create new news items:


*<span class="hentry h-entry"><time class="published dt-published">YYYY-MM-DD</time>: <span class="entry-summary p-entry-summary"><cite class="entry-title p-entry-title">TITLE</cite> by <span class="author p-author vcard h-card"><span class="fn">AUTHOR</span></span>: <span class="url u-url">http://example.com</span></span></span>
*<span class="h-entry hentry"><time class="dt-published published">YYYY-MM-DD</time>: <span class="p-entry-summary entry-summary ">PUBLICATION: <cite class="p-name entry-title">TITLE</cite> by <span class="p-author author h-card vcard"><span class="fn">AUTHOR</span></span>: <span class="u-url url">http://example.com/article-permalink</span></span></span>


-->
-->
*<span class="hentry h-entry"><time class="published dt-published">2012-01-09</time>: <span class="entry-summary p-entry-summary"><cite class="entry-title p-entry-title">How to enable hreview microformat on your blog and get more traffic!</cite> by <span class="author p-author vcard h-card"><span class="fn">Michael Aulia</span></span>: <span class="url u-url">http://www.cravingtech.com/how-to-enable-hreview-microformat-on-your-blog-and-get-more-traffic.html</span></span></span>
 
 
*<span class="h-entry hentry"><time class="dt-published published">2012-06-04</time>: <span class="p-entry-summary entry-summary">.net magazine: <cite class="p-name entry-title ">Emily Lewis on the future of microformats</cite> by <span class="p-author author h-card vcard"><span class="fn">Tanya Combrinck</span></span>: <span class="u-url url">http://www.netmagazine.com/interviews/emily-lewis-future-microformats
</span></span></span>
 
*<span class="hentry h-entry"><time class="published dt-published">2012-01-09</time>: <span class="entry-summary p-entry-summary"><cite class="entry-title p-name">How to enable hreview microformat on your blog and get more traffic!</cite> by <span class="author p-author vcard h-card"><span class="fn">Michael Aulia</span></span>: <span class="url u-url">http://www.cravingtech.com/how-to-enable-hreview-microformat-on-your-blog-and-get-more-traffic.html</span></span></span>


== 2011 ==
== 2011 ==

Revision as of 22:14, 18 June 2012

<entry-title>Articles</entry-title> This article is a stub. You can help the microformats.org wiki by expanding it.

Help expand this page by adding articles about microformats in reverse-chronological order (newest first).

Check the following for sources:

2012

2011

2010

...many more! Collect from http://twitter.com/microformats/favourites

2009

2008

2007

2006

2005

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.

  • Data First vs. Structure First
    • 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.
  • 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