<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>tjameswhite &#187; Microformats</title>
	<atom:link href="http://tjameswhite.com/archives/category/web-development/microformats/feed/" rel="self" type="application/rss+xml" />
	<link>http://tjameswhite.com</link>
	<description>My infrequent thoughts, ideas and ramblings.</description>
	<lastBuildDate>Thu, 01 Jul 2010 03:09:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Microformat Design Pattern</title>
		<link>http://tjameswhite.com/archives/microformat-design-pattern/</link>
		<comments>http://tjameswhite.com/archives/microformat-design-pattern/#comments</comments>
		<pubDate>Thu, 15 Dec 2005 19:12:43 +0000</pubDate>
		<dc:creator>Tim</dc:creator>
				<category><![CDATA[Microformats]]></category>

		<guid isPermaLink="false">http://www.tjameswhite.com/blog/archives/2005/12/microformat-design-pattern/</guid>
		<description><![CDATA[In which we propose not a format per se, but a pattern to build upon.]]></description>
			<content:encoded><![CDATA[<p>Building a complete citation microformat from the ground up is a daunting task; and one that may not actually need to be done. <a href="http://suda.co.uk/">Brian Suda</a> and I have shot emails back and forth for the past couple of months discussing such a microformat. <span id="more-371"></span></p>
<p>In addition to a greater understanding of microformats for me, we believe that we have come up with a starting point: instead of addressing a full citation microformat, we have a couple of design patterns that address what people have been asking for.</p>
<p>For my concern, that means starting with how to format a book title.</p>
<p>The design pattern that Brian floated is the schema class=&#8221;title-*&#8221;. The beauty is that it is simple and extensible &#8212; i.e. title-movie, title-poem, title-novel, title-song &#8212; providing a semantic hook on which to hang our css:<br />
<code><br />
I was reading &lt;cite class="title-book"&gt;The Stars My Destination&lt;/cite&gt;, which was originally titled &lt;cite class="title-book"&gt;Tiger! Tiger!&lt;/cite&gt; after William Blake's poem &lt;span class="title-poem"&gt;The Tyger!&lt;/span&gt;. You can find more information in &lt;span class="title-reference"&gt;Science Fiction Writers&lt;/span&gt;.<br />
</code></p>
<p><code><br />
.title-book { font-style: italic; }<br />
.title-poem:before { content: open-quote; }<br />
.title-poem:after { content: close-quote; }<br />
.title-reference { text-decoration: underline; }<br />
</code></p>
<p>Resulting in:</p>
<blockquote><p>
I was reading <cite class="title-book">The Stars My Destination</cite>, which was originally titled <cite class="title-book">Tiger! Tiger!</cite> after William Blake&#8217;s poem <span class="title-poem">The Tyger!</span>. You can find more information in <span class="title-reference">Science Fiction Writers</span>.
</p></blockquote>
<p>[This is, of course, just a sample of how the titles could be styled. Also note that the use of :before and :after is ignored by Internet Explorer.]</p>
<p>Now that the human quotient is taken care of, we have something for machines as well. Since I&#8217;m not a programmer, I&#8217;ll just excerpt from one of Brian&#8217;s emails:</p>
<blockquote><p>
When we convert this to BibTeX we have to use X2C-bibtex.xsl, since a bibtext reference can only handle one title it looks for class=&#8221;title&#8221;and would ignore title-alternative and alt-title, so there is no +/- for which style to use (the general title-* or the specific name like alt-title, producer, editor, etc.)</p>
<p>The next format we choose is something like Z39.80. When we transform that we use X2C-z39.80.xsl, since there is a specific place for alternate title and regular title, when populating that citation the xslt looks for class=&#8221;title&#8221; for the title and class=&#8221;title-alternative&#8221; or class=&#8221;alt-title&#8221; for the alternate title, so no +/- for general or specific because it is looking for specific instances anyway.</p>
<p>Now the third possibility (and this is a mythical format, but I&#8217;m sure one exists, we&#8217;ll call it FOOBAR). In foobar you can have multiple title elements:<br />
<code>&lt;foobar&gt;<br />
&lt;title&gt;&lt;/title&gt;<br />
&lt;title&gt;&lt;/title&gt;<br />
&lt;/foobar&gt;</code></p>
<p>Now when we use X2C-foobar, it will look for class=&#8221;title-*&#8221;, so it will find title and title-alternate and apply them BOTH to just the <code>&lt;title&gt;</code> element in the output. It will ever actually find the class=&#8221;alternative-title&#8221; unless we specifically are searching for that.</p>
<p>The title-* (i think) make things more extensible, so this year we have title, title-alternate, title-translated. But next year or in the future there might be a need for title-webversion, or title-trailer. Formats like bibtext and z39.80 are not effected because they never had a place to stick these things anyway, but foobar does, and instead of &#8216;rewriting&#8217; the X2C code for each now title-XXXX that appears (or in the specific case adding a class=&#8221;webversion-title&#8221;) and account for that, we can just fall back on the title-* wildcard.
</p></blockquote>
<p>Brian wants to apply the same design pattern to date-time: . class=&#8221;dt-published&#8221;, dt-created, dt-modified, dt-revision-2, dt-release-us, dt-release-uk, etc.</p>
<p>Now, this is not to say that I&#8217;m completely abandoning a full bibliographic microformat. In fact, we need something fairly quickly at work, so I&#8217;m going to forge ahead with something, probably along the lines of:<br />
<span class="small">Note: this isn&#8217;t meant to be a Microformat, just a format for use at work</span><br />
<code>
<pre>
&lt;span class="citation"&gt;
    &lt;span class="title-article"&gt;"FROG."&lt;/span&gt;
    &lt;span class="title-"&gt;Acronyms, Initialisms and Abbreviations Dictionary&lt;/span&gt;.
    &lt;span class="editor"&gt;Ed. Kathleen Edgar&lt;/span&gt;.
    &lt;span class="volume"&gt;Vol. 2&lt;/span&gt;.
    &lt;span class="edition"&gt;34th ed.&lt;/span&gt;
    &lt;span class="publisher"&gt;Detroit: Gale&lt;/span&gt;,
    &lt;abbr class="dt-published" title="2005"&gt;2005&lt;/abbr&gt;.
    &lt;span class="title-publication"&gt;Gale Virtual Reference Library&lt;/span&gt;.
    &lt;span class="publisher"&gt;Thomson Gale&lt;/span&gt;.
    &lt;span class="user"&gt;Gale Internal User&lt;/span&gt;.
    &lt;abbr class="dt-accessed" title="2005-12-14"&gt;14 December 2005&lt;/abbr&gt;
&lt;/span&gt;
</pre>
<p></code></p>
<div>
<span class="title-article">&#8220;FROG.&#8221;</span> <span class="title-book">Acronyms, Initialisms and Abbreviations Dictionary.</span> <span class="editor">Ed. Kathleen Edgar.</span> <span class="volume">Vol. 2.</span> <span class="edition">34th ed.</span> <span class="publisher">Detroit: Gale, 2005.</span> <span class="title-book">Gale Virtual Reference Library.</span> <span class="publisher">Thomson Gale.</span> <span class="user">Gale Internal User.</span> <abbr class="dt-accessed" title="2005-12-14">14 December 2005</abbr>
</div>
]]></content:encoded>
			<wfw:commentRss>http://tjameswhite.com/archives/microformat-design-pattern/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Citation Microformat</title>
		<link>http://tjameswhite.com/archives/citation-microformat/</link>
		<comments>http://tjameswhite.com/archives/citation-microformat/#comments</comments>
		<pubDate>Tue, 01 Nov 2005 18:38:12 +0000</pubDate>
		<dc:creator>Tim</dc:creator>
				<category><![CDATA[Microformats]]></category>

		<guid isPermaLink="false">http://www.tjameswhite.com/blog/archives/2005/11/citation-microformat/</guid>
		<description><![CDATA[In which we drop in some examples.]]></description>
			<content:encoded><![CDATA[<p>Thoughts on what is needed for a citations <a href="http://microformats.com/">microformat</a>. <span id="more-362"></span></p>
<p>Brian&#8217;s <a href="http://microformats.com/wiki/cite">citation pages</a> look to be on target to me. We should certainly move forward with choosing a format to follow and go from there. (Brian &#8211; any thought of adding z39.80 to your formats table?)</p>
<p>As for a separate book review format, there really isn&#8217;t a need. Microformats are modular by nature (yes?) so you would simply use relevant bits of the citation format within <a href="http://microformats.com/wiki/hreview">hReview</a>. Likewise, author names in the citation format could be marked up based on the <a href="http://microformats.com/wiki/hcard">hCard</a> format. I&#8217;ve recently added hReview (using hCard for reviews&#8217; names) to the reference reviews on our Web site (<a href="http://reviews.gale.com">reviews.gale.com</a>). I&#8217;d also like to mark up the products being reviewed and a citation format seems natural. On a personal note, I&#8217;d simply like a way to mark up book titles. There just isn&#8217;t a good way to do that at the moment.</p>
<p>Additionally, as I mentioned in my last email, we are rebuilding our online products core code at the moment to be semantically driven XHTML. We produce reference products for all libraries of all levels. So, when conducting a search on, say frogs, a number of articles (journal, newspaper, etc) citations are returned. We need to do a couple of things with these and having them semantically marked up would certainly help.</p>
<p>First, users can create bibliographic citations right from the results page or the article page. Citation formats include MLA, APA and Z39.80. Current output looks something like (with book titles set in italics):</p>
<p>[MLA style]<br />
&#8220;Frog, Goliath.&#8221; <em>Endangered Species</em>. Eds. Sonia Benson and Rob Nagel. <em>Vol. 3: Amphibians, Fish, Plants, and Reptiles</em>. 2nd ed. Detroit: U*X*L, 2004. p533-535. 3 vols.</p>
<p>[z39.80]</p>
<pre>
AT Frog
CT Acronyms, Initialisms and Abbreviations Dictionary
CY 2005
DB Gale Virtual Reference Library
XX Service Name: Thomson Gale
XX Date of Access:31 October 2005
IL http://find.galegroup.com/gvrl/infomark.do ... [truncated by me]
AL General
BE Edgar, Kathleen
BN 0-7876-6667-X
CV Information and Publishing
DI CX3440403163
DP 2005
EB 0-7876-9383-9
ED 34th
LG English
ND 20041220
OT D-I
PB Gale
PL Detroit
RM COPYRIGHT Thomson Gale
VI CX3440403163
VO 2
XX Full Text
ZZ
</pre>
<p>It only makes sense to mark up the citations right from the beginning in a way that would allow output in either of these (or other) formats. Knowing each piece of the citation would make that pretty easy.</p>
<p>Secondly, from a purely presentation point of view, we need to present citations on screen in a standard manner. While most products present them in MLA format, some break the elements onto multiple lines.</p>
<p>&#8220;Frog, Goliath.&#8221; <em>Endangered Species</em><br />
Eds. Sonia Benson and Rob Nagel<br />
<em>Vol. 3: Amphibians, Fish, Plants, and Reptiles</em>. 2nd ed. Detroit: U*X*L, 2004. p533-535. 3 vols.</p>
<p> Again, knowing each piece of the puzzle makes this pretty easy to do.</p>
]]></content:encoded>
			<wfw:commentRss>http://tjameswhite.com/archives/citation-microformat/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
