Microformats Wiki - User contributions [en]

mobile

2010-06-11T14:19:27Z

Tim White: /* mobile non support */ added palm pre

<h1>mobile</h1>

'''This page is a stub and would benefit from your contributions!'''

{{TOC-right}}
Mobile and microformats make for a particularly powerful combination. Microformats help users complete more tasks with fewer steps, and requiring fewer steps is especially important in mobile applications. This page lists current known mobile support of microformats, and ideas/suggestions for mobile applications that could use microformats.

== mobile support ==
=== Treo ===
The Treo browser has good integration with the Treo address book and calendar.

* '''[[hCard]] support.''' Clicking on a "Add to Address Book" link (e.g. on [http://technorati.com/about/contact.html Technorati's contact page]) will prompt the user to add that [[hCard]] directly to their Treo address book.

* '''[[hCalendar]] support.''' Clicking on an "Add to Calendar" link (e.g. like on the [[events]] page) will prompt the user to add [[hCalendar]] events directly to their Treo calendar. (Note: the "Subscribe to" links that use <code>webcal:</code> do not appear to currently work on the Treo.)

=== Nokia ===
* The S60 3rd generation browser can handle vcards and icals (as those generated by X2V and technorati) extracted from hcards and vcards very well.

List of models: N80, N95, ''(please update)''.

=== Sony Ericsson ===
* The Sony Ericsson W810i can handle vCards generated by X2V (it also supports hCard to vCard to QR-Code (http://www.microform.at/hcard2qrcode/))

== mobile non support ==
Smartphones that should know better! I.e. they have a browser, they address books and/or calendar programs, and yet, they're not connected! They might even sync with a desktop that supports vCard and iCalendar (and maybe even hCard and hCalendar), but they lack built-in support.

=== BlackBerry ===
No support for hCard/vCard/hCalendar/iCalendar in BlackBerry 8700, 81xx, 88xx models. Anybody have experience either way with BlackBerry 9000?
* see [[mobile-advocacy]] for more.

=== iPhone ===
No support for hCard/vCard/hCalendar/iCalendar in first generation iPhone / Safari / Webkit.
No support on iPhone 3G software v2.0.2(5C1), clicking the "add to address book" link as above results in a message saying "Safari can't download this file".
This is particularly sad for the iPhone as the '''iPod''' has supported vCard and iCalendar for many years!
* see [[mobile-advocacy]] for more.

=== Palm Pre ===
No support for hCard/vCard/hCalendar/iCalendar in Palm Pre.
It does support url dialing and vCards generated by X2V (it also supports hCard to vCard to QR-Code (http://www.microform.at/hcard2qrcode/)).

=== Sidekick ===

On a [http://en.wikipedia.org/wiki/Danger_Hiptop#T-Mobile_Sidekick_LX_.28Danger.2FSharp.29 Sidekick LX] (2008, I think; maybe 2007), it treats text/directory as text/plain; that is: if you use h2v to get data out of a page with hCard, you get some text back; text that's less readable and useful than the hCard. This is pretty disappointing, given that the sidekick can send contacts via email. Perhaps it's not all that surprising, though, since this sidekick doesn't do anything when *receiving* vcards.

== mobile application thoughts ==
If this section gets too big, we can move it to a separate page like [[mobile-user-interface]].

=== browser address book integration ===
Every mobile browser should auto-detect [[hCards]] and provide the user a simple/unobtrusive user interface to add them to their mobile address book.

Example: you are browsing a business site, or business listings (e.g. on Google Maps) which list business name, telephone number, address, URL etc. With a simple click or two, it should be possible to save those listings in your address book for future reference or navigation (see below).

=== browser calendar integration ===
Every mobile browser should auto-detect [[hCalendar]] events and provide the user a simple/unobtrusive user interface to add (or subscribe to) them to their mobile address book.

Example: you are browsing an event site (e.g. Upcoming.org), or event listings on a business site, and see event names, start/end times, locations, etc. With a simple click or two, it should be possible to save those events in your calendar for future reference / alarms etc.

=== mapping and navigation ===
[[adr]] and [[geo]] microformats are useful for mobile mapping and navigation applications. (from tweet: [http://twitter.com/microformats/statuses/916437155]).

The most obvious thing to do is extending support for [[geo]] so you can get directions to places from browsers, so you could, for example, get off the train, go to Upcoming.org on your mobile, click the address and have the mobile mapping applications walk you there. (from tweets [http://twitter.com/markng/statuses/916433126], [http://twitter.com/markng/statuses/916436304]).

=== url dialing ===
Most phones have a way of invoking a call from the browser or from applications built in the native languages (JavaME, Python etc.) - it'd be useful if you could have a really simple way of putting in a URI, and it finding the relevant hCard on the page and auto-dials it. I can remember "companyname.com" but not some long phone number. I'm thinking of building something broadly on this line using JavaME, backed by a web service to get the numbers and return them to the device (favouring hCards, but regexing for things that look like phone numbers if it doesn't find any). This came to me a while back when I was walking around London trying to find a shop - I knew their URL but had no idea of their phone number. --[[User:TomMorris|TomMorris]] 05:07, 12 Sep 2008 (PDT)

=== effortlessly add a contact to the address book ===
By using a bit of URL voodoo we can provide a [http://en.wikipedia.org/wiki/QR_Code QR Code] (here's a [http://reader.kaywa.com/ reader])so that the user can point their phone at the image and following the URL, a popup appears prompting them to add the contact to their address book. '''Downside:''' It requires internet access.

Example: [http://chart.apis.google.com/chart?chs=500x500&cht=qr&chl=http://suda.co.uk/projects/microformats/hcard/get-contact.php?uri=http://id.andr3.net] (Thank Brian Suda for X2V!) --[[User:Andr3|Andr3]] 01:19PM, 12 Sep 2008 (WEST)

== thanks ==
* [http://twitter.com/bryanrieger @bryanrieger] for [http://twitter.com/bryanrieger/statuses/916416344 asking the question] on Twitter.
* [http://twitter.com/markng @markng] for providing some ideas with user scenarios.

== see also ==
* [[advocacy]]
* [[mobile-advocacy]]
* [[user-interface]]
* [[operator-phone-tests]]

figure

2008-03-23T13:46:42Z

Tim White: /* Minimisation */

<h1>figure <small style="font-size:90%">0.2</small></h1>
{{TOC-right}}

== Specification ==

'''This is a DRAFT specification.'''

<div class="vcard">
; <span class="role">Editor</span>
: <span class="fn">[[User:TobyInk|Toby Inkster]]</span> (<span class="url">http://tobyinkster.co.uk/</span>)
</div>
; Authors
: Toby Inkster (affiliations above)
: <div class="vcard"><span class="fn">[[User:Csarven|Sarven Capadisli]]</span> (<span class="url">http://www.csarven.ca</span>)</div>

; Acknowledgements: See [[figure#Inspiration_and_Acknowledgements|acknowledgements]].

[[figure#Copyright|Copyright]] and [[figure#Patents|patents]] statements apply.

== Introduction ==

Many HTML documents include supporting images, such as photographs, flow charts, graphs, blueprints or screen captures. These are usually incorporated using the HTML <img> element, however this offers no way of differentiating between such supplementary content and mere decorative images.

Authors often wish to annotate these images with captions or attributions. Currently there is no markup to explicitly associate such text with an image and readers must rely on the proximity of the image and text on the finished rendered page.

This specification aims to allow authors to mark up captions and credits, explicitly associating them with an image.

{{rfc-2119-intro}}

== Format ==

=== Properties ===

* '''figure''' {1}
** '''image''' {1}
** legend ?
** ''credit'' (text | [[hcard|hCard]])*
** ''subject'' (text | [[hcard|hCard]] | [[geo]] | [[adr]] | [[hcalendar|hcalendar event]])*

===Key===
Based on Perl's [http://www.perl.com/doc/manual/html/pod/perlre.html standard quantifiers]:
{| border="1" cellpadding="2"
| '''bold''' {1} || {{must}} be present exactly once
|-
| ''italic''<nowiki>*</nowiki> || {{optional}}, and {{may}} occur more than once
|-
| + || {{must}} be present, and {{may}} occur more than once
|-
| ? || {{optional}}, but {{must-not}} occur more than once
|-
| [square brackets] || list of common values
|-
| (parentheses) || data format
|-
| # || comment
|-
| ! || awaiting documentation
|}

Additionally, an figure {{may}} contain zero or more links marked up with [[rel-tag]] and {{may}} contain zero or more links marked up with [[rel-license]].

If an element with class "credit" also has class "vcard" then the element {{should}} be considered to be the [[hcard]] for a credited person or organisation. Otherwise it {{must}} be considered as a plain text credit.

If an element with class "subject" also has a class "vcard" then the element {{should}} be considered to be the [[hcard]] for the subject of the image - for example the person depicted by a photograph or sketch. If an element with class "subject" also has a class "adr" or "geo" then the element should be considered to be the [[adr|address]] or [[geo|geographic location]] of the subject of the picture - for example the location of a landscape in a photo or the address of a the building shown in blueprints. If an element with class "subject" also has a class "vevent" then the element should be considered to be the [[hcalendar|vevent]] for the subject of a figure - for example a photograph of a sporting event, or a diagram of a military operation.

Please note that the "legend" element should contain what would normally be called a "[http://en.wiktionary.org/wiki/Caption caption]". The term "legend" is used in this specification instead of "caption" in order to maintain parity with the element names used in HTML5. (In turn HTML 5 uses <legend> instead of <caption> to avoid triggering table layouts in legacy browsers.)

The subject, credit, tags and licence may be children of the legend, in which case the text within them forms part of the legend as well as part of the child elements.

=== Examples ===

<pre>
<div class="figure">
<img class="image" src="photo.jpeg" alt="">
<p class="legend">
<a rel="tag" href="http://en.wikipedia.org/wiki/Photography">Photo</a>
of <span class="subject">Albert Einstein</span> by
<span class="vcard credit">
<span class="fn">Paul Ehrenfest</span>
(<span class="role">photographer</span>)
</span>
</p>
</div>
</pre>

Parsed as:

* '''Image''': photo.jpeg
* '''Legend''': Photo of Albert Einstein by Paul Ehrenfest
* '''Credit''': Paul Ehrenfest (hCard)
* '''Subject''': Albert Einstein
* '''Categories''': Photography
* '''License''': (unspecified)

<pre>
<p class="figure">
<label style="display:block" class="legend">January sales data</label>
<img class="image" src="salesdata.png"
alt="Widget sales have fallen slightly, but widget repair kits have sold well.">
</p>
</pre>

Parsed as:

* '''Image''': salesdata.png
* '''Legend''': January sales data

=== Include Pattern ===

The [[include-pattern|include pattern]] {{may}} be used within figures.

=== ABBR Pattern ===

As the figure microformat does not specify any properties that are not human-readable, the [[abbr-design-pattern|abbr design pattern]] {{should-not}} be used directly within a figure, though it {{may}} be used within children formatted in accordance to another microformat - e.g. as [[hcalendar|vevents]] often use the abbr design pattern to specify their start time, a figure subject formatted as a vevent {{may}} use the abbr design pattern in accordance with the [[hcalendar]] specification.

== Minimisation ==

To simplify markup, a number of shortcuts are explicitly allowed by this specification.

# When no "image" class is found within the figure, the first <img> element {{must}} be taken to be the image.
# If the "legend" class is found on the same element as the "image" class (or the image inferred by the previous rule), then the title attribute {{must}} be used as the legend. If the title attribute is not present, or is empty, then the alt attribute {{may}} be used in its place.
# The "image" and/or "legend" classes may be attached to the same element as the element with the "figure" class.

=== Examples ===

The following examples {{must}} all be considered equivalent:

<pre>
<div class="figure">
<img class="image" src="foo.jpeg" alt="">
<span class="legend">Foo</span>
</div>
</pre>

<pre>
<div class="figure">
<img src="foo.jpeg" alt="">
<span class="legend">Foo</span>
</div>
</pre>

<pre>
<div class="figure">
<img class="legend" src="foo.jpeg" alt="" title="Foo">
</div>
</pre>

<pre>
<img class="figure legend" src="foo.jpeg" alt="" title="Foo">
</pre>

== HTML 5 ==

When used in [http://www.w3.org/html/wg/html5/ HTML 5], any <figure> element has an implied class "figure"; any <legend> element has an implied class "legend". For example, the following HTML 5:

<pre>
<figure>
<img src="foo.jpeg" alt="">
<legend>Foo</legend>
</figure>
</pre>

is interpreted as if it were:

<pre>
<figure class="figure">
<img src="foo.jpeg" alt="">
<legend class="legend">Foo</legend>
</figure>
</pre>

== Inspiration and Acknowledgments ==

* [http://www.w3.org/html/wg/html5/ HTML 5 Draft Specification]
* [[figure-examples]] (various authors)

== Copyright ==
This specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== Patents ==
{{MicroFormatPatentStatement}}

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

User:Tim White

2008-01-02T20:19:07Z

Tim White:

hresume

2007-11-08T20:16:36Z

Tim White: /* Experience */

<h1> hResume </h1>

hResume is a microformat for publishing resumes and CVs. hResume is one of several open microformat standards suitable for embedding in (X)HTML, 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.

<h2> Microformats Draft Specification </h2>

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

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

{{rfc-2119-intro}}

__TOC__

== Status ==
Draft, version 0.1.

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

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

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

* hResume
** summary. optional. text.
** contact info. required. {{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-name">affiliation</code> is used along with an [[hcard]] of the organization
* '''<code class="class-name">publications</code>''':: 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>
<p class="summary">
I have 10 years experience with all Web 2.0 technologies– I've been working with Ajax since 1996,
designing with pastels while others will still using tiled background images and frames...
</p>
</nowiki></pre>

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

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

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

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

==== Job Titles ====
To express one or more job titles/positions in the same experience event you should use 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>
<span class="vcard">
<a href="#j" class="include" title="Pedro Sanchez"></a>
<span class="org">Preston High School</span>
<span class="title">Class President</span>
</span>
</pre>

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

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

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

This method of hCard property indirection via an object element [[include-pattern|has been generalized]] to apply to any/all string/text properties in hCard.

Note: the object data attribute {{must}} be a local ID reference. External references (which would require a consuming application to load an external resource) are not supported by this method.

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

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

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

== Examples in the wild ==
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.

* [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)

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

hresume

2007-11-08T20:11:13Z

Tim White: /* Experience */

<h1> hResume </h1>

hResume is a microformat for publishing resumes and CVs. hResume is one of several open microformat standards suitable for embedding in (X)HTML, 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.

<h2> Microformats Draft Specification </h2>

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

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

{{rfc-2119-intro}}

__TOC__

== Status ==
Draft, version 0.1.

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

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

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

* hResume
** summary. optional. text.
** contact info. required. {{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-name">affiliation</code> is used along with an [[hcard]] of the organization
* '''<code class="class-name">publications</code>''':: 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>
<p class="summary">
I have 10 years experience with all Web 2.0 technologies– I've been working with Ajax since 1996,
designing with pastels while others will still using tiled background images and frames...
</p>
</nowiki></pre>

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

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

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

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

==== Job Titles ====
To express one or more job titles/positions in the same experience event you should use 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:

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

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

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

This method of hCard property indirection via an object element [[include-pattern|has been generalized]] to apply to any/all string/text properties in hCard.

Note: the object data attribute {{must}} be a local ID reference. External references (which would require a consuming application to load an external resource) are not supported by this method.

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

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

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

== Examples in the wild ==
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.

* [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)

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

hresume

2007-11-08T20:10:37Z

Tim White: /* Experience */

<h1> hResume </h1>

hResume is a microformat for publishing resumes and CVs. hResume is one of several open microformat standards suitable for embedding in (X)HTML, 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.

<h2> Microformats Draft Specification </h2>

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

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

{{rfc-2119-intro}}

__TOC__

== Status ==
Draft, version 0.1.

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

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

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

* hResume
** summary. optional. text.
** contact info. required. {{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-name">affiliation</code> is used along with an [[hcard]] of the organization
* '''<code class="class-name">publications</code>''':: 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>
<p class="summary">
I have 10 years experience with all Web 2.0 technologies– I've been working with Ajax since 1996,
designing with pastels while others will still using tiled background images and frames...
</p>
</nowiki></pre>

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

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

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

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

==== Job Titles ====
To express one or more job titles/positions in the same experience event you should use 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:

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

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

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

This method of hCard property indirection via an object element [[include-pattern|has been generalized]] to apply to any/all string/text properties in hCard.

Note: the object data attribute {{must}} be a local ID reference. External references (which would require a consuming application to load an external resource) are not supported by this method.

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

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

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

== Examples in the wild ==
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.

* [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)

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

include-pattern

2007-11-08T01:40:35Z

Tim White: /* background */

<h1>Include Pattern</h1>
{{TOC-right}}
Initially developed as part of [[resume-brainstorming]], the include pattern is a mechanism to include a portion of data from one area of a page into another area of the same page. The following is documentation for re-use of the pattern in other microformats, and for publishers working with it.

;Editors: Tantek Çelik
: Ben Ward

== background ==

[[hresume|hResume]] needed the ability to include a name from one hCard at the top of a resume — the person's contact details — into the separate hCards used in the same person's employment history. Repeating name information would not have matched the existing publishing techniques used in Resumes and Curriculum Vitæ, would be inconvenient to publishers, and irritating to consumers. The include pattern is a mechanism to reference data from the same page, avoiding repetition, or <em>any</em> duplicate visible information.

== scope ==

The include pattern is strictly limited to the scope of the current page. It cannot be used to include content from other URLs.

== quick reference==

The include-pattern is a mechanism to include content from one microformat into another microformat elsewhere in the same document, using hyperlinks (recommended) or OBJECT. For example:

<pre><nowiki><a class="include" href="#author" title="James Levine"></a></nowiki></pre>
<pre><nowiki><object class="include" data="#author"></object></nowiki></pre>

In specs which cite the include-pattern, either of the above code snippets will cause a microformats parser to replace the A or OBJECT element with class name "include" with the content fragment with ID "author". Full examples follow.

== in general==

To reference includes, use an include element with class name "include" and a document fragment identifier. The content to be included should have an ID attribute set, and that ID should be referenced from the HREF or DATA attribute at the point of inclusion.

The include element with class name "include" indicates a reference to a sub-tree elsewhere in the document which must be included in-place by microformat parsers. That is, the element with class "include" is _replaced_ in the DOM by the referenced sub-tree.

To prevent infinite loops, if a class="include" refers to itself or to an ancestor in the parse tree, then it is ignored and has no effect on the parser.

Per the [[include-pattern#Scope|scope]], the OBJECT 'data' attribute and hyperlink 'href' attribute MUST be local ID references when used as include pattern instances. External references (requiring a consuming application to load an external resource) are not supported by this method.

There are two HTML elements available to reference includes, hyperlink/Anchor and OBJECT. They are documented below.

These methods of property indirection via a hyperlink element can apply to any/all properties in class-based microformats, but should only be used where a microformat explicitly states that the include-pattern is a dependency. For example, [[XOXO]] does not reference the include-pattern at this time, so sub-trees cannot be included by reference in XOXO. [[hResume]] and [[hReview]] do reference the include pattern.

=== Hyperlink ===

The recommended way to reference includes within microformats is to use a hyperlink.

==== Hyperlink example====

Here is an [[hcard|hCard]] from the beginning of a resume, shown here as a verbose hCard.

<pre><nowiki>
<span class="vcard">
<span class="fn n" id="jl-name">
<span class="given-name">James</span> <span class="family-name">Levine</span>
</span>
</span>
</nowiki></pre>

Elsewhere on the page, a second hCard re-uses the "fn n" content from the first hCard:

<pre><nowiki>
<span class="vcard">
<a href="#jl-name" class="include" title="James Levine"></a>
<span class="org">SimplyHired</span>
<span class="title">Microformat Brainstormer</span>
</span>
</nowiki></pre>

Note that the lack of content inside the <code>a</code> element with <code>class="include"</code> is deliberate, as it reflects the design requirement from [[hresume|hResume]] of not having to repeat <em>any</em> name information with each job entry. The <code>title</code> attribute is used to aid useragents that wish to label the hyperlink outside its inline context.

A microformat parser must treat the second hCard as follows, with the hyperlink include element completely replaced (including inner-text) by the sub-tree that was referenced:

<pre><nowiki>
<span class="vcard">
<span class="fn n" id="jl-name">
<span class="given-name">James</span> <span class="family-name">Levine</span>
</span>
<span class="org">SimplyHired</span>
<span class="title">Microformat Brainstormer</span>
</span>
</nowiki></pre>

==== notes and issues ====

Note: The <code>id</code> attribute value in the example "jl-name" was chosen for demonstration purposes. The text of the value has no semantic per the include-pattern other than to connect the source of the include to the destination. Authors {{should}} use good [[POSH]] techniques to choose <code>id</code> and <code>class</code> names.

Using the hyperlink include pattern causes no known issues in any web browser, as long as hyperlink includes without content are hidden with CSS. See below for details.

Authors {{should}} supply content text or at least <code>title</code> attribute text for the hyperlink itself. This can require repeating a small piece of information (such as a person's name in an hCard), or including generic text suitable for the context of the page.

===== accessibility =====
<strong>Hyperlinks presented as an extracted list.</strong> There are two points of view on this. <span id="Accessibility_concerns">The first is that the user experience of Assistive Technology can(might?) be severely degraded by the presence of hyperlinks which do not contain text ('''citation needed''').</span> The second is that the first claim is only a side effect of some Assistive Technologies extracting the hyperlinks in a document and presenting them as a list, and that such technologies / features have no right to do so, and therefore it is not your problem to worry about. See [http://joeclark.org/appearances/atmedia2007/#context Joe Clark: When accessibility is not your problem: Headings and links read out of context], in particular:
<blockquote><p>As writers, we are not authorizing you or Jaws to pull out our link text and remix it. Why don’t you rearrange the sentences, too?</p></blockquote>

<strong>Hyperlinks and tab focusing in common browsers</strong>. As noted in the [http://microformats.org/wiki/include-pattern-feedback include-pattern feedback page], any visible hyperlink used with an <code>href</code> attribute ends up in the browser's tab cycle. This affects all keyboard users (both sighted users that can't/don't operate a mouse, or screen reader users in the extreme case). Even empty hyperlinks receive focus. This can be tested by modifying the code of the original [http://allinthehead.com/demo/include.html a@include test page] to visually follow the tabbing from one hyperlink to the next (using CSS or, for test purposes, subtly changing the <code>href</code>, tabbing through the page, and observing the change in the URL displayed in the browser's status bar). Hyperlinks hidden with CSS <code>display:none</code> do not end up in the browser's tab cycle.

Thus it is recommended that Hyperlink Include Pattern hyperlinks lacking inline content {{should}} be hidden with CSS. As they have no content, this stylistic change has no net effect on the document's content semantics from a user's perspective.

=== Object ===

The Object Include Pattern is semantically superior to the Hyperlink Include; it is being used to embed content into the page. The <code>object</code> element based include was the original developed include pattern. However, there are serious browser compatibility issues that can affect some implementation scenarios and thus the above Hyperlink Include Pattern was developed and is now preferred.

==== Object example ====

Here is the same [[hcard|hCard]] from the beginning of the resume in the previous example.

<pre><nowiki>
<span class="vcard">
<span class="fn n" id="jl-name">
<span class="given-name">James</span> <span class="family-name">Levine</span>
</span>
</span>
</nowiki></pre>

Elsewhere on the page, a second hCard re-uses the "fn n" content from the first hCard:

<pre><nowiki>
<span class="vcard">
<object data="#jl-name" class="include"></object>
<span class="org">SimplyHired</span>
<span class="title">Microformat Brainstormer</span>
</span>
</nowiki></pre>

A microformat parser must treat the second hCard as follows, with the <code>object</code> include element completely replaced by the sub-tree that it referenced:

<pre><nowiki>
<span class="vcard">
<span class="fn n" id="jl-name">
<span class="given-name">James</span> <span class="family-name">Levine</span>
</span>
<span class="org">SimplyHired</span>
<span class="title">Microformat Brainstormer</span>
</span>
</nowiki></pre>

This method of hCard property indirection via an object element can apply to any/all properties in class-based microformats.

=== notes and issues===
* Unlike the hyperlink pattern, the Object Include Pattern does not require any textual fallback. This makes it invisible to Assistive Technology with no adverse affect.
* Apple's Safari (WebKit-based) browser has some rendering issues with this use of <code>object</code>: You should set a width and height of "0" for the include elements to resolve this ('''version(s) affected needed''').
* Bugs have been reported in some web browsers (Internet Explorer, Safari, Firefox) that <code>object</code> elements referencing fragments of the same document erroneously cause the browser to make additional HTTP requests ('''version(s) affected needed'''). For scenarios where HTTP requests are a sensitive performance measure, this makes the Object Include Pattern inappropriate.
* Versions of Microsoft Internet Explorer with ActiveX controls disabled will throw a warning prompt upon finding an <code>object</code> element ('''version(s) affected needed''').

== acknowledgements ==

Thanks to discussions and brainstorms with a bunch of folks: [http://theryanking.com/ Ryan King], James Levine, the whole crowd at the [http://mashupcamp.com/index.cgi?HAtomFinalization Microformats specifications working session] at MashupCamp, [http://suda.co.uk/ Brian Suda], [http://randomchaos.com/ Scott Reynen], [http://allinthehead.com/ Drew McLellan].

== specifications using ==
* [[hresume|hResume]]
* [[hreview|hReview]]

=== considering ===
All class-based microformats {{should}} consider using and explicitly normatively stating support for the include pattern.
* [[hatom|hAtom]]
* [[hcalendar|hCalendar]]
* [[hcard|hCard]]

== implementations ==
* X2V implements the [[include-pattern]] when parsing [[hcard|hCards]] and [[hcalendar|hCalendars]] for both object.include and a.include.

== references ==

=== normative ===
* HTML 4.01

=== informative ===
* [[hcard|hCard]]
* [[hresume|hResume]]
* XHTML 1.0

== related pages==
{{include-pattern-related-pages}}
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

Talk:posh

2007-05-05T18:32:23Z

Tim White: /* Misuse of microformats logo for ‘POSH’ bling */

== Misuse of microformats logo for ‘POSH’ bling ==

On 3rd May Ben Ward [http://www.mail-archive.com/microformats-discuss@microformats.org/msg07543.html objected] to the use of the microformats logo in graphics promoting ‘POSH’, on grounds that it creates confusing and undesirable ambiguity between the terms ‘microformat’ and ‘POSH’. We're at a point where people are wrongly interpreting ‘microformat’ as a general term for semantic class names. The endorsement of these graphics on our own Wiki is a massive hindrance to our efforts to discourage such misuse.

Please indicate a vote below on the removal of the microformats logo POSH buttons.

*+1 — Ben Ward
*+1 — James Craig
*+1 — Jeremy Keith
*+1 — Frances Berriman
*+1 — Ben O'Neill
*+1 - Tim White

mailing-list-unmoderation

2007-03-20T00:40:09Z

Tim White:

Andy Mabbett was [http://rbach.priv.at/Microformats-IRC/2007-01-04#T011730 moderated (rather than banned for a week) on 2007-01-04] on the microformats mailing lists at the time for both his frequent/excessive off-topic posts, and his ignoring of several warnings from admins to please stop doing so (see microformats-discuss archives for details). Ernie P. (a longstanding overwhelmingly positive contributor to the community) has [http://microformats.org/discuss/mail/microformats-discuss/2007-March/009063.html proposed unmoderating Andy at this point, 2007-03-19]. Please add your opinion at the end:
* +1 Ernie P.
* +1 David Janes
* +1 Nic James Ferrier
* +1 Tantek
* +1 Scott Reynen
* +1 Steve Ganz
* +1 Joe Andrieu
* +1 M. Jackson Wilkinson
* +1 BenWest
* +1 Chris Foote (Spike)
* -0.5 Edward O'Connor (hober)
* +1 Tim Whtie
* ... add your opinion (+1 unmoderate, 0 no opinion, -1 keep moderated) and your name

===Discussion===
Moved to [[governance-issues#Mailing_List_Unmoderation_Discussion|a section on the governance issues page]].

hresume-feedback

2006-12-11T19:51:01Z

Tim White: /* General Comments */

= hresume-feedback =

This document is for keeping track of feedback about [[hresume]], one of several [[microformats]].

== Feedback ==
=== General Questions ===
See the [[hresume-faq|hresume FAQ]].

=== General Comments ===

* Upon implementing [[hresume]] at [http://davecardwell.co.uk/cv/ http://davecardwell.co.uk/cv/], I had the following observations:

** I used [[hcalendar]]'s optional "description" element to include a short paragraph of text about each section of education/employment. The examples on the [[hresume]] page could be updated to mention this ability.

** A richer way of marking up qualifications would have been nice. If you view the source of my resume you'll see I marked up each subject as a "skill". This, however, doesn't convey any information about the level or grade achieved. The minimal set for the main educational qualifications in England seems to be qualification(level, subject(s), grade(s)). A section from my resume would then be:
<pre> <tbody class="qualification">
<tr>
<td class="level" rowspan="2">
<abbr title="Advanced">A</abbr> Level
</td>
<th class="subject" scope="row">
Business Studies
</th>
<td class="grade">
B
</td>
</tr>
<tr>
<th class="subject" scope="row">
Computing
</th>
<td class="grade">
A
</td>
</tr>
</tbody></pre>

Further investigation might show the need for optional information about awarding bodies and such. Not sure if a qualification element would satisfy the 80/20 condition.

[[User:Dave Cardwell|Dave Cardwell]] 06:53, 19 Feb 2006 (GMT)

* I and others on the #microformats IRC channel have expressed a concern about the way skills are represented. Introducing unnecessary links into a resume is undesirable, especially when you have to link to a page like [http://en.wikipedia.org/wiki/Perl http://en.wikipedia.org/wiki/Perl] to conform to the rel-tag standard while [http://www.perl.org/ http://www.perl.org] might be more intuitive. Non-visual user agents like screen readers will have a great deal of meaningless links to trawl through, and search engines may infer relationships that do not exist.

[[User:Dave Cardwell|Dave Cardwell]] 04:54, 22 Feb 2006 (GMT)

* Our thoughts:
We would love to be able to mark-up the following data:

Contact Info = hCard

Experience (our issue is with current employment)*
[company name]
[position/title]
[dates]
[location]
[Description]

Education
[school]
[major]
[degree]
[dates]
[location]

Accreditation
[type] (PD, CPA, JD and so on)
[date]

*how do you represent current positions that have no end date? Maybe lack of date means present?

Here is our hResume plugin for WordPress (in development):
<a href="http://www.flickr.com/photos/alexmuse/144781779/" title="Photo Sharing"><img src="http://static.flickr.com/44/144781779_ddc4d07460_o.jpg"</a>

[[User:Alexander Muse|Alexander Muse]] 08:54, 11 May 2006 (GMT)

*Suggestion: Reference information - should there be a field of "References", where hCard information would be held for references? Also, perhaps a distinction between three types (e.g. personal (a friend), professional (e.g. previous boss), educational (e.g. university lecturer)) in a similar method to hCard's telephone type distinctions? If this is already accounted for, what method would you suggest for implementing this?

*When working on my resume I tried to mark it up as hResume but I hit a couple of show-stoppers for me. If I had the choice of marking it up to look and behave like I wanted or be a valid hResume I'd chose for former and that's what I ended up having to do. My issues were:
**It's recommended to put the contact hCard in an <address> but address is inline and I wanted to put block elements in there. I could have worked around that with CSS display: but I wanted to be able to render to text with links or w3m which don't support enough CSS for that.
*** Actually, <address> is a block-level element. And the spec says that is <strong>should</strong> be used, but not that it <strong>must</strong> be used.
**hResume builds on rel-tag for describing skills, but I didn't want my skills section filled with links (no matter how they're rendered - I don't want them clickable).
*** Skills are optional, as are linking them.
[[User:Ianloic|Ianloic]] 15:58, 10 Dec 2006 (PST)

mailing-lists

2006-10-17T14:37:59Z

Tim White:

<h1> Mailing Lists </h1>

Read the [http://microformats.org/discuss/ microformats discuss page] first.

Then read the [http://microformats.org/mailinglists-policies/ mailing list policies].

Ok, now here are some additional notes of scope and topics for each list.

__TOC__

== microformats-discuss ==
A mailing list for general discussion of microformats, with a strong leaning towards:

* starting out with microformats
* real-world content authoring

=== good topics for discussion ===
Here is a list (certainly not definitive) of good topics which are appropriate for the microformats-discuss mailing list:

* general thoughts on the design and use of semantic XHTML markup
* how to use and write microformats in content
* how to use microformat design patterns in content

=== good topics that belong somewhere else ===
* see [http://microformats.org/wiki/mailing-lists#good_topics_for_discussion_2 microformats-dev good topics for discussion]

=== bad topics for discussion ===

AKA topics better discussed elsewhere (somewhere other than microformats.org).

Here is a list (also not definitive) of topics which are undesired and inappopriate for the microformats-discuss mailing list. In fact, they're not even worth the time to bother discussing, so please do not bring them up on the microformats-discuss mailing list. We'll add more topics as people come up with more off-topic or out-of-scope or rathole topics.

# '''How to make a "general purpose" (micro)format.''' Go read [http://microformats.org/wiki/microformats#microformats_are_not what microformats are not], actually, go read the entire [[microformats|principles]] page. Sometimes this may masquerade as a "format of formats". Either way, it is one of those boil the ocean ratholes which are far outside the focus of microformats. If you really want to work on such subjects, teach yourself DTD (SGML, XML), XML Schema, Relax NG, RDF Schema, and find the communities working on those technologies.
# '''Using namespaces and namespace prefixes.''' In short, namespaces are neither necessary (the Internet ran just fine without them for decades, go read some RFCs), nor desirable (prefixes make formats far uglier and more difficult to hand-code). See also [[namespaces-considered-harmful]].
# '''Using non-English names for properties'''. This was briefly discussed on the microformats-discuss list most recently as "Language Maps" but has been raised before that. Some folks have raised the issue that microformats use English names for properties, and they would like alternate (non-English) names in other (natural) languages, and perhaps try to establish a mapping between them. As microformats property names are based on existing standards (see [[process]], and [[naming-principles]]), this is another problem that is far outside the scope of microformats. As Ryan King put it, this is a pre-existing (unsolved) "problem" with English-based HTML, the English-based CSS, the English-based HTTP and so on. Note that this is NOT about the internationalization (i18n) of the content and data itself - which is of course an excellent goal, advocated and promoted by microformats and the standards they are based on (e.g. W3C, IETF). This is purely about the names of the properties (and enumerated values) in the formats.

== microformats-dev ==
For discussion of microformats development, with a leaning towards:

* anything that involves writing code
* abstractions / models (in contrast to actual content)

=== good topics for discussion ===
These tend to be topics that belong in microformats-dev instead of microformats-discuss. This list is also not definitive, but illustrates the general areas:

* microformat parsing
* microformat "(auto)-discovery"
* comparisons of microformats with other data abstractions or data representations (e.g. XML, RDF)
* compatibility/interoperability of microformats with other data abstractions or data representations

== microformats-rest ==
For discussion of use of microformats with REST, in protocols, services, APIs etc.

== how to search the mailing list archives ==
If your post to the list starts off "I'm new to the list and microformats so I don't know if you've discussed this already" READ THROUGH THE [http://microformats.org/discuss/mail/microformats-discuss/ ARCHIVES]!

The archives are getting larger, so here are a few simple ways you can search them. Most popular search engines imploy some sort of site based results filtering. Google does this in your initial search. Type "site:http://microformats.org/discuss/ <search terms here>" to limit the search results to only our discussion list. This will help you from asking a question that has already been posted, debated, and possibly resolved. It saves everyone time and energy!

== new list proposal ==

There is a proposal for creating a new mailing list for discussing the research and creation of new microformats so that those discussions do not overwhelm microformats-discuss.

Some candidates for names with the thinking behind them. Feel free to add your name and opinion (+/- 1 or 0).

* microformats-new (focusing on discussing "new" microformats)
** +1 tantek
** +1 ScottReynen
** +1 Lachlan Hunt
** +1 Joe Andrieu
** -1 Andy Mabbett
* microformats-research (focusing on the essential, and often overlooked by first-time proposers "research" phase(s) in the process)
** +1 tantek
** +1 ScottReynen
** +1 cgriego
** +1 Phae
** +1 JustinThorp
** -1 Andy Mabbett
* microformats-process (That's really what we're talking about with research of new microformats, isn't it?)
** +1 ScottReynen
** +1 Lachlan Hunt
** -1 Andy Mabbett
* microformats-propose (it misses the point of the process, and implies that there is a desire for microformats proposals - there isn't)
** -1 tantek
** -1 ScottReynen
** +1 Andy Mabbett
* microformats-suggest (similar to propose but milder ;)
** +1 ChrisMessina
** 0 tantek
** -1 ScottReynen
** -1 Phae (I feel this is just -propose in disguise)
** - BenWest
** -1 Andy Mabbett
* nothing (fix uf-dev, do nothing else (for now))
** +1 RyanKing
** +1 BenWest
** +1 Tim White

hcard

2006-10-10T14:23:14Z

Tim White: /* New Examples */

<h1>hCard</h1>

hCard is a simple, open, distributed format for representing people, companies, organizations, and places, using a 1:1 representation of the properties and values of the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in [[semantic-xhtml|semantic XHTML]]. hCard is one of several open [[microformats|microformat]] standards suitable for embedding in (X)HTML, 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.

__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 ===
{{MicroFormatCopyrightStatement2004}}

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

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

== Introduction ==
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt 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 XHTML. 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.

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

== Format ==
=== In General ===
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt 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 XHTML elements.

=== 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 (X)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 vs. Plural Properties ===

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

For properties which can be plural (e.g. "TEL"), each class instance should create a instance of that property.

==== Singular properties ====

Singular properties: "FN", "N", "BDAY", "TZ", "GEO", "SORT-STRING", "UID", "CLASS".

All other properties are plural. This list has 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.

=== Human vs. Machine readable ===

If an <code><abbr></code> element is used for a property, then the '<code>title</code>' attribute of the <code><abbr></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.

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 should be 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 introduced 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:<br />

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

hCard:
<pre><nowiki>
<span class="tel">
<span class="type">home</span>:
<span class="value">+1.415.555.1212</span>
</span>
</nowiki></pre>

This hCard fragment could be displayed as:

<div style="border: thin dashed black; width: 95%; padding: .5em 1em;">
<span class="tel">
<span class="type">home</span>:
<span class="value">+1.415.555.1212</span>
</span>
</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.

# '''NAME''', '''PROFILE''', '''SOURCE''', '''PRODID''', '''VERSION''' properties as defined in Sections 2.1.2, 2.1.3, 2.1.4, 3.6.3, 3.6.9 of RFC 2426. 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 (X)HTML documents) to construct the NAME property, MAY output a PROFILE value of "<code>VCARD</code>" per RFC 2426, 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 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 or organization and should be treated as such. In this case the author MUST also 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) 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 on the Web 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" is treated as a "nickname" property value.
# Parsers should handle the missing "N" property by implying empty values for all the "N" sub-properties.

Note: 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 can optionally 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.

=== Root Class Name ===

The root class name for an hCard is "vcard".

=== Property List ===

This is the list of properties (and subproperties, in parentheses, like this) in hCard, taken from vCard:

* fn, n (family-name, given-name, additional-name, honorific-prefix, honorific-suffix), nickname, sort-string
* url, email (type, value), tel (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
==== 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>
<span class="tel"><span class="type">Home</span> (<span class="type">pref</span>erred):
<span class="value">+1.415.555.1212</span>
</span>
</nowiki></pre>

This could be displayed as:

<div style="border: thin dashed black; width: 95%; padding: .5em 1em; ">
<span class="tel"><span class="type">Home</span> (<span class="type">pref</span>erred):
<span class="value">+1.415.555.1212</span>
</span>
</div>

The following lists are ''informative''. See RFC 2426 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, 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 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/
ORG:Technorati
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 class="org">Technorati</div>
</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]<br />
Technorati
</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.

=== More Examples ===

See [[hcard-examples]] for more examples, including all examples from vCard RFC 2426 converted into hCard.

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

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

=== New Examples ===
Please add new examples to this section.
* [http://www.belkin.com/pressroom/releases/uploads/10_10_06NotebookExpansionDock.html Belkin Press Releases] are using hCards for PR contacts and corporate offices.
* [http://mybank.com myBank.com] uses hCard for its listings of every branch of every FDIC-insured bank in the United States.
* [http://leftlogic.com Left Logic] uses hCard for embedded contact information.
* [http://inga-art.co.uk/artist Inga Scholes] uses hCard for contact information in the sidebar.
* [http://www.lussumo.com/ Lussumo] uses hCards on user profile pages in its open-source [http://www.getvanilla.com/ Vanilla] Discussions Forum software.
* [http://www.creative-ways.nl/ Ron Kok] uses hCards to mark-up the names and URLs of commentors on his blog. He also uses hCards in combination with XFN in his blogposts to refer to friends, and has an hCard for himself in the footer of his blog.
* The [http://www.westmidlandbirdclub.com/ West Midland Bird Club] in the English Midlands uses hCard on its [http://www.westmidlandbirdclub.com/ home page], [http://www.westmidlandbirdclub.com/diary/ events diary] and [http://www.westmidlandbirdclub.com/club/contact.htm contact pages]. The former is a page footer which is gradually being rolled out across the whole site.
* [http://tagg.no Tagg Media] uses hCard for contact information and provide link to vCard download in the contact section.
* [http://en.wikipedia.org/wiki/Neo_%28The_Matrix%29 Thomas A Anderson in Wikipedia] is now marked up with hCard.
* [http://dconstruct06.madgex.com/ d.Construct 2006 Backnetwork] uses hCards for conference delegates (and provides the markup so that delegates can copy and paste cards into their own sites).
* [http://www.brown.edu Brown University] now uses hCard on the front page
* [http://www.wideblueyonderweb.co.uk Dunks at Wide Blue Yonder Web Design] has added hCard markup on his [http://www.wideblueyonderweb.co.uk/wbyw/pages/contact.htm contact page] and is looking to implement it on all past & future contact pages for clients.
* [http://southamptonrubberstamp.com Southampton Rubber Stamp Company] now has hCard markup with a vCard download link on every page.
* [http://barefoot-ceramics.com Barefoot Ceramics paint your own pottery studio] (in Newport, South Wales) has added hCard markup to its [http://barefoot-ceramics.com/find#address "Find"] page and other address instances. They hopes to implement hCalendar event lists as soon as an ics to hCalendar PHP class can be found or written.
* IBM is embracing microformats. The [http://www.ibm.com/contact/employees/ IBM Employee Directory] now returns hcards in its query results. Also see the [http://www.ibm.com/shortcuts/ Shortcuts Podcast].
* [http://dsingleton.co.uk/ David Singleton] has added a hCard to his blog.
* [http://krisswatt.co.uk/ Kriss Watt] has hidden an hCard his blog footer.
* [http://www.thestreet.org.au The Street Theatre (Canberra, Australia)] has added hCard markup to its [http://www.thestreet.org.au/contact.htm Contact Us] page. hCalendar markup will soon be added for all of our performances.
* [http://www.informatik.uni-hamburg.de/SVS/personnel/henrich/index.php Henrich C. Pöhls] has marked up his about page using hcard, including his PGP-Key that is stored in an abbr title, using class=key.
* [http://www.yalf.de Yalf Webentwicklung] has [http://www.yalf.de/kontakt contact information] available as hCard (and vCard).
* [http://www.zeldman.com/about/ Jeffrey Zeldman]. Jeffrey Zeldman has marked up his about page using hcard.
* [http://WhereAreYouCamping.com Where Are You Camping]. hCards for all members and camps, employing the include pattern as well. AFAIK this is the first Burning Man related microformats implementation, not to mention addresses in Black Rock City.
* [http://www.clacksweb.org.uk Clackmannanshire Council ]. hCard is implemented for all contact details across the site, and for specific individuals such as elected members (Councillors).
* [http://www.webdirections.org Web Directions ]. hCard is used as contact information for the conference, while speakers are marked up with hCard.
* [http://www.markthisdate.com/contactform.html MarkThisDate.com ]. An hCard is implemented on our contactform. For our calendars hCalendars will follow as soon as possible.
* [http://www.msiinet.com/contact/ MSI Systems Integrators] has its "Contact MSI" page encoded with hCards.
* [http://www.coolblue.nl/ Corporate website of Coolblue BV]. hCards were implemented in both the footer of each page, and in the "News" section for press contact information.
* [http://www.besancon.fr/index.php?p=32 Official site of Besançon (France)] uses hCard for each page concerning the small towns surrounding Besançon.
* [http://2006.dconstruct.org/speakers/ d.Construct 2006 conference speakers list] is implemented using hCards.
* [http://local.yahoo.com Yahoo Local] now supports hCards for business and places in the search results
* [http://learningtheworld.eu/imprint/ Learning the World] has hcard information on the imprint, alas we didn't succeed to mark-up the work phone and fax numbers properly.
* The [http://www.fuckparade.org F’parade] website uses hcard, though I didn't find a type to distinguish mobile and landline phone numbers.
* [http://www.miranet.nl/contact.htm Miranet Webdesign] have added a hcard to their [http://www.miranet.nl/contact.htm 'contact' page]
* [http://weblog.200ok.com.au/ Ben Buchanan] has added a vCard to the [http://weblog.200ok.com.au/about/ 'About' page on The 200ok Weblog]
* [http://www.radiantcore.com Radiant Core] has their contact information [http://www.radiantcore.com/contact/ available in hCard].
* [http://www.mikerumble.co.uk/ Mike Rumble] has [http://www.mikerumble.co.uk/contact.html uploaded his hCard].
* [http://www.saumag.edu/ Southern Arkansas University] has its contact footer encoded as hCard
* [http://main.uab.edu/ University of Alabama at Birmingham] has its contact footer encoded as hCard
* [http://www.capital.edu Capital University] has contact footer and bloggers' names encoded as hCard. Also, all page-specific contact information is encoded as hCards (see [http://www.capital.edu/Internet/Default.aspx?pid=67 Admissions] page for an example)
* [http://main.uab.edu/shrp/ UAB School of Health Professions] uses hCard in its contact footer
* [http://green.carisenda.com/ Stephen Stewart] has his hCard on the front page of his weblog ('You are here' section)
* [http://www.fberriman.com/ Frances Berriman] has a hidden vCard in the footers of her website.
* [http://www.candlescience.com/ CandleScience Candle Supply] added a hidden hcard sitewide.
* [http://www.direction.es/ Direction] uses hCard for contact information.
* [http://audiobank.tryphon.org AudioBank] uses hCard to display member informations.
* [http://www.vivabit.com/atmedia2006/speakers/ @media speakers] are marked up with hCard (photos depend on BASE tag support which makes this a good test case)
* [http://www.dougransom.com Doug Ransom] uses hCard for his financial advisory practice.
* [http://rubyandrails.org/usergroups/newcastle/members.html ncl.rb] uses hCard for contact information.
* [http://www.snowinteractive.com/ Snow Interactive] uses hCard for contact information.
* [http://flickr.com Flickr] now supports [[hcard|hCard]] and [http://gmpg.org/xfn XFN] on profile pages. See [http://flickr.com/photos/factoryjoe/113866484/ screenshot of Flickr UI in Flock browser using Flocktails extension - March 17th 2006].
* [http://www.ndiyo.org/contact Contact information for the Ndiyo project]
* [http://www.pixelenvy.co.uk/ Pixel Envy] uses hCard for contact information on every page
* [http://stilbuero.de/contact/ Klaus Hartl] uses hCard in the sidebar for contact information (maybe easier to parse through delivering xhtml as xml).
* [http://charlvn.virafrikaans.com/contact Charl van Niekerk's hCard]
* [http://billy-girlardo.com/WP/ BillyBLOGirlardo] uses hCard for contact information.
* [http://www.hicksdesign.co.uk/ Hicksdesign] uses hCard for contact information.
* http://www.gr0w.com/articles/press/growsearch_launched_press_release/ - hCard in a press release for the press contact info
* http://www.redmonk.com/cote/archives/2006/03/testing_out_mic.html - hCard with explanation
* [http://andy.ciordia.info/ it's my island], personal blog, hcard on the ''[http://andy.ciordia.info/pages/about_me About the Writer]'' page. [[User:Ciordia9|Andy Ciordia]]
* [http://www.windowonwoking.org.uk/ Window on Woking], a local community site in the UK, uses hCard in the homepage of each member organisation and local Councillor.
* [http://ChunkySoup.net/ ChunkySoup.net] has redesigned using hAtom 0.1 and hCards on the entire site -- by [[User:ChrisCasciano|Chris Casciano]]
* [http://www.30boxes.com/ 30 Boxes],a social calendar application and digital lifestyle aggregator, automatically creates an hcard for you with your account. It is found under Settings > Syndication.
* [http://www.nearwhere.com/ Nearwhere.com] allow you to put an hcard on an interactive map.
* [http://www.brentozar.com/ Brent Ozar] added a [http://www.brentozar.com/contact.php contact] page hCard.
* [http://www.kerihenare.com/ Keri Henare] has rewritten his [http://www.kerihenare.com/contact/ contact] page hCard. Now using <code><object></code> instead of <code><img></code> for photo. (Thanks Brian Suda for updating the vCard converter)
* [http://michaelraichelson.com/contact/ Michael Raichelson] had an hCard on his contact page before SXSW, but never thought to add it here until Tantek requested it.
* [http://www.commoner.com/~lsimon/lindsey_simon_hcard.html Lindsey Simon] has added an hCard to his website as per Tantek's SXSW request for folks to try it
* [http://www.davidgagne.net/ David Gagne] has an hCard in his sidebar.
* [http://www.churchzip.com/map/ Churchzip.com/map] and [http://www.skiwhere.com/map/ Skiwhere.com/map], provide churches, hotels, and ski resorts on the same maps. Locations are formatted as hcards.
* All [http://www.iqdir.com/ IQ Directory Solutions] Yellow Pages web portals use [[hcard|hCard]] markup on listings. For example [http://www.yellowpages-cambodia.com/ Cambodia Yellow Pages] and [http://www.superpages.com.my/ Malaysia Super Pages]
* Ning's cloneable Group app uses fuzzy matching to map custom fields to [[hcard|hCard]] markup on its [http://group.ning.com/index.php?controller=person&action=view&content=JonathanAquino profile] pages.
* [http://claimid.com/factoryjoe Chris Messina' ClaimID hCard]
* [http://factoryjoe.com/blog/hcard Chris Messina' hCard]
* [http://flock.com/about Flock About]
* [http://tantek.com/microformats/2006/03-01-TechPlenAgenda.html Agenda: W3C Technical Plenary Day, March 1 2006] has [[hcard|hCard]] and [[hcalendar|hCalendar]] markup. ([http://www.w3.org/2006/03/01-TechPlenAgenda.html original here]).
* [http://www.gr0w.com/articles/press/growsearch_launched_press_release/ GrowSearch Launched (Press Release)] uses an hCard to provide Press Contact Point.
* The [http://www.arborday.org/ National Arbor Day Foundation] has started using hCards for their [http://arborday.org/programs/conferences/communityforestry/index.cfm upcoming] [http://arborday.org/programs/conferences/hazardtrees-treeplanting/ conferences].
* [http://www.multipack.co.uk The Multipack] has numerous hCards, especially on the [http://www.multipack.co.uk/members/ members page], as well as the next meeting information.
* [http://deadringrancor.livejournal.com/ Justin McDowell] used an hCard when [http://deadringrancor.livejournal.com/221332.html referring to a person in his blog post]
* [http://davecardwell.co.uk/cv/ Dave Cardwell] has included his hCard in his Curriculum Vitae.
* [http://blog.usweb.com/ Shaun Shull] has written a great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], and has included his [[hcard|hCard]] as one of the examples.
* [http://www.thefutureoftheweb.com/ Jesse Skinner] has written a simple [http://www.thefutureoftheweb.com/blog/2006/1/hcard tutorial with examples]
* [http://www.w3.org/2005/12/allgroupoverview.html 2006 W3C Technical Plenary Week] has marked up the venue, contacts, and program committee members all with hCard.
* [http://www.avf-nexus.co.uk AVF-Nexus] have a hCard on their [http://www.avf-nexus.co.uk/contact/ contact page] - (by [http://creation.uk.com Creation"])
* [http://www.thefantasticos.com/andrew/ Andrew White] posted [http://www.thefantasticos.com/andrew/index.php/my-hcard/ his hCard] and [http://www.thefantasticos.com/andrew/index.php/62/microformats-the-should-have-been-obvious-web-dev-tool/ blogged about it].
* [http://www.2sheds.ru Oleg "2sheds" Kourapov] in his [http://www.2sheds.ru/blog/ blog] ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog X2V]) has turned personal profile into hCard ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/hcard.html X2V]) and his blogroll - into combination XFN/hCards ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/friends.html X2V])
* [http://www.approveddesign.co.uk Approved Design Consultancy] have a hCard on their [http://www.approveddesign.co.uk/about/contact/ contact page] as well as on their [http://www.approveddesign.co.uk/about/people/ people section] - (by [http://creation.uk.com Creation"])
* [http://weblog.200ok.com.au/ Ben Buchanan] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&format=search Colin Morris] have [http://weblog.200ok.com.au/2006/01/griffith-phonebook-adds-hcard-and.html implemented hCards and vCards] for the [http://www.griffith.edu.au Griffith University] [http://www.griffith.edu.au/find/content_phonebook.html online phone book]. Eg. [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=ben+buchanan&format=search Ben's vCard] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&format=search Colin's vCard]
* WWF-Australia [http://wwf.org.au/about/contactdetails/ contact details page]
* [http://rasterweb.net/raster/ Pete Prodoehl] used the hCard format on his [http://rasterweb.net/raster/contact.html Contact page] and his [http://rasterweb.net/portfolio/ Portfolio]
* [http://alexander-mette.de amette] uses the hCard format in a module of his TikiWiki powered blog
* [http://staff.washington.edu/oren/weblog2/ Oren Sreebny] has an hcard on his blog main index template
* [http://www.cs.brandeis.edu/~zippy/ Patrick Tufts] has an hCard on his homepage.
* [http://ascii20.blogspot.com/ Mathias Kolehmainen and Jamie Taylor] have hCards on their weblog.
* [http://www.hoppsan.org/jamesb/blogger/ Barnaby James] has a hCard on his weblog.
* [http://esa-education.com/schools/map ESA Education] Uses hCards for their 100+ schools and each of the individual school sites.
* [http://www.thereisnocat.com/#vcard Ralph Brandi] has added an hCard to the sidebar of his weblog as a result of Tantek Çelik's portion of the Microformats presentation at SXSW 2006.
* [http://www.pierce.ctc.edu/ephone/ Pierce College] -- community college directory uses hCard on all individual directory entries.
* [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/ the Institutional Web Management Workshop 2006] have marked up all their [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/committee/ speakers with hCard].
* http://wikitravel.org/en/Singapore/Sentosa. Wikitravel is experimenting with hcard on its travel guides. This guide uses hcard for all its business listings. More info on http://wikitravel.org/en/Wikitravel_talk:Listings.
* [http://www.musik-erber.de/ Musik-Erber] uses to present contact information at the sidebar
* [http://cdevroe.com/about/#contact Colin D. Devroe] uses hCard to display his contact information on his about page
* The ECS (Scool of Electronics and Computer Science at the University of Southampton) [http://www.ecs.soton.ac.uk/people People Pages] use vCard. Contact cjg@ecs.soton.ac.uk if there's any bugs.
* [http://www.southwestern.edu/~ramseyp Pat Ramsey] has his contact information on his blog marked up with hCard. Contact [mailto:ramsey.pat@gmail.com ramsey.pat@gmail.com] if there are any bugs there.
* [http://www.meryl.net/ Meryl K. Evans] has a hidden hCard on her homepage.
* [http://www.vyre.com/company/contact-us/ VYRE] is a CMS development company with a "contact us" hCard
* [http://www.lefdal.cc/info.php Alf Kåre Lefdal] uses hCard in the markup of his contact information
* [http://www.pignwhistle.com.au/ Pig N Whistle, a chain of pubs in Brisbane, Australia] is using hcard to mark up all the contact pages for its outlets and head office
* [http://kollitsch.de/ Patrick Kollitsch] has built his personal Profil as hCard
* [http://www.hbs.edu/faculty/dspar/ Harvard Business School] has hCards on their faculty pages
* [http://openmikes.org/ openmikes.org] uses hCards for open mike venue addresses in its listing detail pages.
* [http://www.intertecnollc.com/ InterTecno, LCC] publishes an hCard on the home page and contact page.
* [http://canaltcm.com/ver/sobre-tcm Turner Classic Movies TCM spanish website] has published contact details as a hCard
* [http://rejuvenation.com/ Rejuvenation] is now using hCard for contact information.
* [http://www.mattash.com/contact/ Matthew Ash] uses the hCard in his contacts section.

=== Examples ===
* [http://shiftingpixel.com/about/the-artist shifting pixel photoblog] has published an hCard.
* [http://thoughtport.blogspot.com/ Aiden Kenny] hasn't published his hCard yet, but he has [http://thoughtport.blogspot.com/2005/07/elemental-particles-of-web.html published his hCard icon]: http://photos1.blogger.com/blogger/4224/444/320/AK-Hcard-icon.gif
* [http://thedredge.org Andy Hume] uses hCards to mark-up the names and URLs of commentors on his blog, e.g. his [http://thedredge.org/2005/06/using-hcards-in-your-blog/ blog post on "Using hCards in your blog"].
* [http://www.bidclix.com/ BidClix]'s [http://www.bidclix.com/AboutContact.html Contact BidClix] page has it's ''contact info'' marked up with an hCard.
* [http://suda.co.uk/ Brian Suda] has managed to embed a photo in [http://suda.co.uk/contact/ his hCard] through the [http://www.ietf.org/rfc/rfc2397.txt data uri scheme] by converting the image to BASE64 code. View the Source to see how this is accomplished. [http://suda.co.uk/projects/X2V/get-vcard.php?uri=http%3A//suda.co.uk/contact/ The X2V link] will extract the image and encode it for a vCard which will be displayed in some address book applications.
** Inspired by this I thought to try the same for SVG at [http://barefoot-ceramics.com/find Barefoot] ...
** <img class="photo" style="display:none;" src="data:image/svg+xml;text,<?xml version='1.0' encoding='UTF-8' standalone='no'?><svg xmlns:svg='http://www.w3.org/2000/svg' xmlns='http://www.w3.org/2000/svg' version='1.0' width='50' height='80' id='svg3957'><defs id='defs3959' /><path d='M 28.91433,...32.192802 z' style='fill:#cc4d00;fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:0.625;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1' id='path9551' /></svg>" alt="Barefoot">
** Does it work?? Well it parses OK. Some automated tools replace the < with %3C (etc., eg Brian Suda's vcard form). Unfortunately Kontact (KDE contacts tool) doesn't handle SVG as a vCard photo or logo format - I don't know if this is a standard. It seems it could work and maybe even does somewhere. Maybe the text field needs to be Base64 encoded? ... see [http://slashdot.org/~pbhj/journal/142382 pbhj's slashdot journal] for a bit more on this.
* [http://cinematreasures.org Cinema Treasures] uses hCard to markup venue information for 10,000+ movie theaters.
* [http://www.w3.org/People/Connolly/events/ Dan Connolly's index of events and talks] has hCards for many of the people he has met at those events. In Mar 2006, he moved a bunch of hotel contact info from his PDA to this page; it's now up to 32 hCards.
* [http://doncrowley.blogspot.com/ Don Crowley] has published [http://www.crowley.nl/hcard.html his hCard] as well as a nifty hCard button: http://www.crowley.nl/images/hcard.png
* [http://loadaveragezero.com/hnav/contact.php Douglas W. Clifton] added all types of contact information
* [http://eventful.com Eventful] publishes all of its venue information pages with embedded hCards.
* [http://www.iowamilitaryveteransband.com/members/ Iowa Military Veterans Band Contacts] - 95 hCards [http://weblog.randomchaos.com/archive/2005/10/24/Microformats/ marked up by Scott Reynen]
* [http://JackWolfgang.blogspot.com Jack L. Wolfgang II] has [http://jack.randomata.com/resume/ converted the addresses in his resume to hCards].
* [http://www.efas.fupl.asso.fr/efas/_Mathieu-Drouet_.html Mathieu Drouet] and [http://www.efas.fupl.asso.fr/efas/_Annie-Leger_.html Annie Leger] both have hCards
* [http://www.ndunn.com Neil Dunn] has published his rather [http://www.ndunn.com/2005/10/7/hCard good looking hCard]
* [http://www.oliverbrown.me.uk/ Oliver Brown] has published his hCard.
* [http://www.paradigmproductions.org/contact/ Paradigm Productions] published a vcard as a ul (marked up by [http://www.linkingarts.com/ Peter Jacobson])
* [http://www.splintered.co.uk/ Patrick H. Lauke] has marked up [http://www.splintered.co.uk/about/ his contact info with hCard].
* [http://blah Paul Schreiber has published his hCard on [http://paulschreiber.com/about/?contact his about page].
* [http://paulschreiber.com/blog/ Paul Schreiber]'s [http://concerts.shrub.ca/ Sunnyvale House Concerts] site publishes hCards for upcoming artists, as well as an hCard for the page itself. In addition the [http://concerts.shrub.ca/shows Past Shows] page contains hCards for all past artists.
* [http://www.paulmichaelsmith.com/blog/hcard.htm Paul Smith] has created an hCard page which is Human Readable, and a link to X2V passing the same hCard page to generate a vCard.
* [http://www.windley.com/archives/2005/07/hcards_trying_o.shtml Phil Windley has published] [http://phil.windley.org/hcard.html his hCard].
* [http://www.go-curiosity.com/about.htm Piercarlo Slavazza] has published an hCard.
* [http://zooibaai.nl/ Rob Mientjes] has published his hCard on [http://zooibaai.nl/about/ his about page].
* [http://rbach.priv.at/Contact Robert Bachmann] has published his hCard and [http://rbach.priv.at/Images/hcard a button].
* [http://blah Scott Reynen has published his hCard on [http://www.randomchaos.com/document.php?source=scott_reynen his profile page].
* [http://www.stackframe.com/ StackFrame, LLC] has published [http://www.stackframe.com/people/ employee] and [http://www.stackframe.com/contact/ general] contact information as hCards.
* [http://www.wolfsreign.com Steven Ametjan] has published his hCard on [http://www.wolfsreign.com/about/ his about page].
* [http://tantek.com/microformats/2005/syndicate/speakers-list.html Syndicate - Speaker List] as a set of hCards
* [http://tagcamp.org/index.cgi?ContactList TagCamp contact list]
* [http://tantek.com/log Tantek's Thoughts] includes an inline author hCard at the bottom of the page.
* [http://technorati.com/ Technorati]'s [http://www.technorati.com/about/ About page] lists their '''Media Contact'''
* [http://www.deadringerart.com/ The Brothers McDowell] have hCards at their Contact page.
* [http://twinsparc.com/ Twinsparc] put an hCard in the header and footer of all their pages.
* [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 Conference speakers page marked up with hCard]
* [http://we05.com/ Web Essentials 05] marked up all their [http://we05.com/presenters.cfm presenters with hCard].
* [http://www.uoguelph.ca/directory/ The University of Guelph] includes hCard info in its directory.

=== Examples with some problems ===

* [http://gbraad.nl/ Gerard Braad] has published an example on his [http://gbraad.nl/site/?p=profile profile] page that is almost consistent with his original [http://gbraad.nl/files/gbraad.vcf vCard] file. Also progress is made for transforming his [http://files.gbraad.nl/foaf.rdf FoaF] file to a hCard encoded representation. (also done for my spouse:[http://spouse.gbraad.nl/site/?p=profile Yong Yuan])
** (2005-09-27) PASSED, PASSED
** WARNINGS
*** uses 'n given-name' and 'n family-name' instead of nesting the given- and family- names inside the 'n'
*** has one 'tel' value with a bunch of values stuffed in
*** probably more problems --[[User:RyanKing|RyanKing]] 17:19, 5 Jan 2006 (PST)
* [http://kinrowan.net/ Cori Schlegel] [http://kinrowan.net/blog/wp/archives/2005/07/08/a-problem-with-the-structured-blogging-plug-in-for-wordpress/ discusses how he has updated] [http://kinrowan.net/blog/contact his contact page with hCard]
** INVALID - using 'prefix' instead of 'honorific-prefix' and type's in classnames (in both adr and tel) and has two photo's (the second could be 'logo') --[[User:RyanKing|RyanKing]] 15:15, 5 Jan 2006 (PST)
* The good ship [http://styrheim.com/test/leonid.html Leonid Miloslavskiy] spotted in the North Atlantic
** INVALID --[[User:RyanKing|RyanKing]] 00:50, 27 Oct 2005 (PDT)
*** class="family" should probably be family-name
*** the "n" property is missing and the "n" optimization can't be applied
*** the first geo propery is empty, the second one is invalid (ie, it doesn't contain lat/long)
* [http://landsbank.fo/#hCard Landsbanki Føroya]
** INVALID - using embedded rdf/xml invalidly
* [http://chrischerry.name/ Chris Cherry's contact page with his hCard]
** <strike>WARNING - uses class="cell" instead of <span class="type">cell</span></strike> Fixed -- [[User:Seriph|Chris Cherry]] 19:54, 15 Sep 2006 (PST)
* [http://www.bath.ac.uk/contact/ University of Bath] Person Finder results are encoded with hCards so you can easily create a vCard from any result.
** ERROR - attempt to use Implied-N optimization where that's not possible. --[[User:RyanKing|RyanKing]] 14:29, 5 Jan 2006 (PST)
** Error appears for external users only. Won't be fixed any time soon. -- [[User:PhilWilson|PhilWilson]] 00:03, 28 Jan 2006 (GMT)
* [http://richi.co.uk/blog/2005/12/structured-blogging.html Richi Jennings] has put up his attempt
** INVALID, missing FN --[[User:RyanKing|RyanKing]] 12:47, 5 Jan 2006 (PST)
* [http://www.yellowpencil.com/contact/ Yellow Pencil] Using microformats to present company contact information
** First hcard has empty "fn" and no "n". "fn" should be with "org" -- [[User: ScottReynen |ScottReynen]] 21:29, 19 Jun 2006 (CST)

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

The following implementations have been developed which either generate or parse hCards. If you have an hCard 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://leftlogic.com/info/articles/microformats_bookmarklet Microformats Bookmarklet] is a bookmarklet designed for Safari (works in Firefox and Camino) that overlays on the current page to allow users to import individual hCards or hCalendars. Written by Remy Sharp.
*[http://elbewerk.com/2006/09/vcardexplorer-02.shtml vCardExplorer 0.2] is a Mac OS X Application, that displays VCF-Files and extracts hCards from Websites written by Daniel Kagemann.
* [http://placenamehere.com/mf/nnwextract/ Extract Microformats] is a script for NetNewsWire that supports extracting hCard and hCalendar data in blog posts (via technorati service). Written by [[User:ChrisCasciano|Chris Casciano]]
* [http://allinthehead.com/hkit/ hKit] is an open source PHP 5 parsing library with support for hCard.
* [http://kitchen.technorati.com/search Technorati Microformats Search] indexes [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] as [http://tantek.com/log/2006/05.html#d31t1802 announced by Tantek].
** list of pages with indexing Issues so they can be looked into as to why data is not being extracted
** suda.co.uk/contact
** multipack.co.uk

* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of hCards from within Dreamweaver 8.
* [http://scooch.gr0w.com/ Scooch] is a slide show and presentation creator that generates a [[hCard]] for individual slide show authors and comment authors with a CSS button to parse and download via [http://suda.co.uk/projects/X2V/ X2V]. Also uses [[hReview]] for slide ratings and [[rel-tag]] for categories.
* [http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar
*[http://opensource.reevoo.com/2006/03/08/release-uformats-12/ uformats] is a ruby library that can parse [[hCalendar]], [[hCard]], [[hReview]] and [[rel-tag]]
* [http://blog.codeeg.com/tails-firefox-extension/ Tails] is a Firefox Extension that will display the presence and details of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage. [https://addons.mozilla.org/firefox/2240/ Tails Export] is an extended version.
* [http://www.stripytshirt.co.uk/features/firefox/smartzilla Smartzilla is a Firefox Extension] that finds hCards on web pages and lets you add them to your addressbook.
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCard and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* There is [http://flickr.com/photos/factoryjoe/68755089/ evidence of built-in hCard support in the Konqueror browser]. Specifically, Konqueror 3.5, in KDE 3.5 (kubuntu Breezy w/ update).
* There is [http://tagcamp.org/index.cgi?ContactList evidence of a kwiki plugin for hCards]. Update: the [http://svn.kwiki.org/cwest/Kwiki-hCard/ hCard kwiki plugin svn repository]. See the [http://microwiki.caseywest.com/index.cgi?hCard documentation of the hCard kwiki plugin].
* [http://suda.co.uk/projects/X2V/ X2V] is a bookmarklet that parses hCard and produces a .vcf (vCard) stream. Note: needs to be updated as the spec is refined
* [http://www.stripytshirt.co.uk Duncan Walker] has built [http://www.stripytshirt.co.uk/features/firefox/smartzilla a Firefox extension] that gets hCard data from a webpage, uses Brian Suda's XSL (locally) to transform it to vcard format and opens the resulting .vcf file.
* [http://george.hotelling.net/90percent/ George] has written a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script] that detects hCards and allows users to easily add them to their address book application. Relies on the X2V web service to do the conversion.
* [http://inside.glnetworks.de/ Martin Rehfeld] has updated the work of [http://blogmatrix.blogmatrix.com/ David Janes] and produced a [[Greasemonkey]] [http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ script] that finds many microformat elements, including hCards, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. The hCard to vCard conversion is done internally within the script. ''This will work with FireFox 1.5+/GreaseMonkey 0.6.4+ now.''
* [http://diveintomark.org/ Mark Pilgrim] has also written an [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser Greasemonkey user script]. It is self-contained and does not rely on the X2V web service.
* [http://www.oliverbrown.me.uk/2005/09/03/a-working-microformats-extension-to-simplexml/ Oliver Brown] has written an "extension" to [http://www.php.net/simplexml SimpleXML] that gives simple access to hCard information in PHP 5.
* [http://thedredge.org/ Andrew D. Hume] has built a system (Wordpress plugin?) for [http://thedredge.org/2005/06/using-hcards-in-your-blog/ using hcards in your blog] to represent people leaving comments on blog posts.
* The [http://tantek.com/microformats/hcard-creator.html hCard creator] is a very simple, yet illustrative, open source user interface / form / script which creates an hCard in real-time as you type in a set of contact information.
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate hCard information ([http://ietf.org/rfc/rfc2629 RFC2629] is an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - Open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards.
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] is a collection of palmpilot and sidekick tools. It includes X2V derivatives xhtml2hcard.xsl and toICal.xsl plus some [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest] materials
* [http://www.openpsa.org/ OpenPsa 2.x] CRM application uses hCard for all person listings. The widget is [http://www.midgard-project.org/midcom-permalink-922834501b71daad856f35ec593c7a6d reusable across Midgard CMS]
* [http://www.metonymie.com Emiliano Martínez Luque] has written an experimental [http://www.metonymie.com/hCard_extract/app.html hCard finder and structured search application] that finds hCards within a given set of URLs and returns the ones that match the specified search criteria.
* [http://randomchaos.com/microformats/base/ Microformat Base] is an open-source PHP microformat aggregation crawler, currently recognizing hreview, hcalendar, and hcard.

== Additional Applications ==
This section is '''informative'''.

There are numerous potential additional uses and applications for hCards on the Web. The following are merely a few thoughts and possibilities that folks have come up with:

* As an open standard/format for [http://www.gravatar.com/ Gravatars].
* Marking up individual authors of blog posts on a group blog
* Marking up people's names and URLs in a blogroll
* Any reference to people in blog posts (e.g. when citing them, or referencing them, or describing them, by name).
* ...

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

=== Informative References ===
* [http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426]
* [http://w3.org/TR/REC-CSS1 CSS1]
* [http://tantek.com/log/2004/09.html#hcard hCard term introduced and defined on the Web, 20040930]
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]
* Contributed from http://developers.technorati.com/wiki/hCard.
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]

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

== Related Pages ==
* [http://microformats.org/code/hcard/creator hCard creator] ([[hcard-creator-feedback|feedback]]) - create your own hCard.
* [[hcard-authoring|hCard authoring]] - learn how to add hCard markup to your existing contact info.
* [[hcard-examples|hCard examples]] - Example usage of various classes within hCard,
* [[hcard-faq|hCard FAQ]] - If you have any questions about hCard, check here, and if you don't find answers, add your questions!
* [[hcard-parsing|hCard parsing]] - Normatively details of how to parse hCards.
* [[hcard-issues|hCard issues]] - Please add any issues with the specification to the issues page.
* [[hcard-profile|hCard profile]] - The XMDP profile for hCard

This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.

* [[hcard-brainstorming|hCard Brainstorming]] - where we are keeping our brainstorms and other explorations relating to hCard
* [[hcard-tests|hCard tests]] - a wiki page with actual embedded hCards to try parsing.

== 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.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page] and the [http://technorati.com/tags/hcard hCard tag]

hcard-examples-rfc2426

2006-05-23T18:11:25Z

Tim White: /* References to People and Organizations */

<h1>hCard examples</h1>

Example [[hcard|hCards]].

== Authors ==
* [http://tantek.com/log Tantek Çelik]
* Brian Suda

== Instructive Examples ==

=== Authors of Pages and Posts ===
[http://www.w3.org/TR/html401/struct/global.html#h-7.5.6 Per the HTML4.01 specification], authors should be using the <code><address></code> element to indicate the "contact information for a document or a major part of a document." E.g.

<pre><nowiki>
<address>
<a href="http://tantek.com/">Tantek Çelik</a>
</address>
</nowiki></pre>

By adding [[hcard|hCard]] to such existing semantic XHTML, you can explicitly indicate the name of the person, their URL, etc.:

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

This could be displayed as:

[http://tantek.com/ Tantek Çelik]

This works not only for whole pages, but also for "major part[s]" of pages, e.g. blog posts.

See the [http://microformats.org/blog/ microformats.org blog] (view the source) for a live example. The author of every blog post on the microformats.org blog is marked up as an <code><address class="vcard"></code> element like the example shown above.

=== References to People and Organizations ===

A common pattern in blog posts is to link mentions of people's names to their blogs, and/or organizations to their home pages. E.g.:

<pre><nowiki>
<cite><a href="http://meyerweb.com/">Eric Meyer</a></cite> wrote a post
(<cite><a href="http://meyerweb.com/eric/thoughts/2005/12/16/tax-relief/">Tax Relief</a></cite>)
about an unintentionally humorous letter he received from the
<a href="http://irs.gov/">Internal Revenue Service</a>.
</nowiki></pre>

By adding hCard to such markup, you can explicitly indicate both the person and the organization by name and URL:

<pre><nowiki>
<cite class="vcard"><a class="fn url" href="http://meyerweb.com/">Eric Meyer</a></cite> wrote a post
(<cite><a href="http://meyerweb.com/eric/thoughts/2005/12/16/tax-relief/">Tax Relief</a></cite>)
about an unintentionally humorous letter he received from the
<span class="vcard"><a class="fn org url" href="http://irs.gov/">Internal Revenue Service</a>.
</nowiki></pre>

This could be displayed as:

''[http://meyerweb.com/ Eric Meyer]'' wrote a post (''[http://meyerweb.com/eric/thoughts/2005/12/16/tax-relief/ Tax Relief]'') about an unintentionally humorous letter he received from the [http://irs.gov/ Internal Revenue Service].

References to organizations and departments can be marked up much like a person (note "org fn"):
<pre><nowiki>
<div class="vcard">
<div class="org fn">
<div class="oragnization-name">Sprinkler Fitters U.A. Local 483</div>
<div class="adr">
<div class="extended-address">Apprenticeship Training Center</div>
<div class="street-address">2531 Barrington Court</div>
<span class="locality">Hayward</span>,
<abbr title="California" class="region">CA</abbr>
<span class="postal-code">94545</span>
</div>
</div>
</div>
</nowiki></pre>

"Apprenticeship Training Center" could also be marked up as a business unit instead of part of the address:
<pre><nowiki><div class="organization-unit">Apprenticeship Training Center</div></nowiki></pre>

=== hCard and XFN ===
==== References to People in Blog Posts ====

In the above example, one person (the blogger) is referring to another person (Eric Meyer). In addition to using hCard to explicitly mark up the reference as a person, the blogger can use [http://gmpg.org/xfn/ XFN] (the XHTML Friends Network) to indicate their relationship to Eric Meyer, e.g.:

<pre><nowiki>
<cite class="vcard"><a class="fn url" rel="friend colleague met" href="http://meyerweb.com/">Eric Meyer</a></cite> wrote a post
(<cite><a href="http://meyerweb.com/eric/thoughts/2005/12/16/tax-relief/">Tax Relief</a></cite>)
about an unintentionally humorous letter he received from the
<span class="vcard"><a class="fn org url" href="http://irs.gov/">Internal Revenue Service</a></span>.
</nowiki></pre>

It would be displayed the same as the previous example.

==== References to People in Blogrolls ====

Many bloggers are using XFN (often using an easy user interface like that built into [http://wordpress.org WordPress]) to explicitly indicate their relationships to the people in their blogrolls:

<pre><nowiki>
<ul>
<li><a href="http://meyerweb.com" rel="friend colleague met">Eric Meyer</a></li>
<li><a href="http://photomatt.net" rel="friend colleague met">Matt Mullenweg</a></li>
</ul>
</nowiki></pre>

By adding hCard markup to an XFN Friendly blogroll, you can explicitly indicate the name and URL of the person in addition to their relationship:

<pre><nowiki>
<ul>
<li class="vcard"><a class="fn url" href="http://meyerweb.com" rel="friend colleague met">Eric Meyer</a></li>
<li class="vcard"><a class="fn url" href="http://photomatt.net" rel="friend colleague met">Matt Mullenweg</a></li>
</ul>
</nowiki></pre>

This could be displayed as:
* [http://meyerweb.com Eric Meyer]
* [http://photomatt.net Matt Mullenweg]

For more information on XFN, see the [http://gmpg.org/xfn/ XFN home page], [http://gmpg.org/xfn/join joining XFN], and [http://gmpg.org/xfn/background background on XFN].

=== New Types of Contact Info ===

Since vCard was designed, there have been numerous other services that provide individuals with addresses or other means of contact, e.g. instant messaging, voip, etc.

Does this mean that vCard (and hence hCard) must be extended to represent these?

Thanks to the flexibility of the URL property, the answer is no, no extensions are necessary. Instead, we use the proper URL for the service which identifies the service (protocol, machine, and/or path), and place the individual's address inside that.

==== AOL Instant Messenger (AIM) ====

AOL Instant Messenger (AIM) ids can be represented using the <code>aim:</code> protocol. Many who publish their AIM ids do so with clickable URLs e.g.:

<pre><nowiki>
<a href="aim:goim?screenname=ShoppingBuddy">IM with the AIM ShoppingBuddy</a>
</nowiki></pre>

Thus for hCard, we will adopt this existing content publisher behavior, and simply capture it as another URL for the hCard:

<pre><nowiki>
<a class="url" href="aim:goim?screenname=ShoppingBuddy">IM with the AIM ShoppingBuddy</a>
</nowiki></pre>

==== Yahoo Messenger ====

Similarly, Yahoo Instant Messenger (YIM) ids can be represented using the <code>ymsgr:</code> protocol. And similarly many publish their YIM ids as clickable URLs e.g.:

<pre><nowiki>
<a href="ymsgr:sendIM?SomeYahooFriend">IM with SomeYahooFriend</a>
</nowiki></pre>

Again, for hCard, we will adopt this existing content publisher behavior, and simply capture it as another URL for the hCard:

<pre><nowiki>
<a class="url" href="ymsgr:sendIM?SomeYahooFriend">IM with SomeYahooFriend</a>
</nowiki></pre>

==== MSN Messenger ====

<strike>Unfortunately, AFAIK, there is no hacked up defacto protocol for opening an MSN IM session with an MSN userid (which themselves are just email addresses). Thus we must simply resort to marking them up as email addresses, and expect that consumers may use some heuristic, such as "hotmail.com email addresses are also MSN IM ids". -Tantek</strike>

MSN Messenger (MSNIM) ids can be represented using the <code>msnim:</code> protocol. And similarly many publish their MSNIM ids as clickable URLs e.g.:

<pre><nowiki>
<a href="msnim:chat?contact=joebob@hotmail.com">IM with joebob@hotmail.com</a>
</nowiki></pre>

For hCard, we will adopt this existing content publisher behavior, and simply capture it as another URL for the hCard:

<pre><nowiki>
<a class="url" href="msnim:chat?contact=joebob@hotmail.com">IM with joebob@hotmail.com</a>
</nowiki></pre>

Updated 14 May 2006 - [http://www.wackomenace.co.uk/ Ruben]

Ruben, I tried this, and "msnim:" is an unrecognized protocol on MacOSX.4 (this is with the latest MSN Messenger for Mac installed and running and logged int). Could you provide links to documentation about "msnim:" and links to actual pages that publish their MSNIM ids this way? I don't know of any - [http://tantek.com/ Tantek]

==== Site profiles ====
Bloggers often indicate their identity on content hosting services using the URL to their home page, feed or profile on those services. By labeling them as URL properties, these additional facets of identity can be publish in an hCard as well.

* [http://del.icio.us delicious]:
** <code><a class="url" href="http://del.icio.us/rbach">Robert Bachmann's links</a></code>
* [http://flickr.com Flickr]:
** <code><a class="url" href="http://flickr.com/photos/tantek/">See my photos</a></code>
** <code><a class="url" href="http://flickr.com/people/tantek/">Flickr profile</a></code>
* [http://technorati.com/ Technorati]:
** <code><a class="url" href="http://technorati.com/profile/tantek/">Technorati profile</a></code>
* Add more here...
** ....

== RFC 2426 examples in hCard ==

These are 1:1 hCard examples for each example in [http://www.ietf.org/rfc/rfc2426.txt RFC 2426].

Mark Pilgrim has made these hCard examples available as separate files:
* http://diveintomark.org/projects/greasemonkey/hcard/tests/

=== 2.4.2 VCARD ===

<pre><nowiki>
AGENT:BEGIN:VCARD\nFN:Joe Friday\nTEL:+1-919-555-7878\n
TITLE:Area Administrator\, Assistant\n EMAIL\;TYPE=INTERNET:\n
jfriday@host.com\nEND:VCARD\n
</nowiki></pre>

This vCard fragment has one property whose value is another vCard, and could be represented as an hCard fragment with an embedded hCard, literally (with the unnecessary type=internet default omitted, and the implied n optimization):

<pre><nowiki>
<div class="agent vcard">
<a class="email fn" href="mailto:jfriday@host.com">Joe Friday</a>
<div class="tel">+1-919-555-7878</div>
<div class="title">Area Administrator, Assistant</div>
</div>
</nowiki></pre>

this hCard could be displayed as:

[mailto:jfriday@host.com Joe Friday]<br />
+1-919-555-7878<br />
Area Administrator, Assistant

=== 3.1.1 FN Type Definition ===

<pre><nowiki>
FN:Mr. John Q. Public\, Esq.
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="fn">Mr. John Q. Public, Esq.</span>
</nowiki></pre>

this hCard fragment could be displayed as:

Mr. John Q. Public, Esq.

=== 3.1.2 N Type Definition ===

==== Example 1 ====

<pre><nowiki>
N:Public;John;Quinlan;Mr.;Esq.
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="n">
<span class="honorific-prefix">Mr.</span>
<span class="given-name">John</span>
<span class="additional-name">Quinlan</span>
<span class="family-name">Public</span>,
<span class="honorific-suffix">Esq.</span>
</span>
</nowiki></pre>

this hCard fragment could be displayed as:

Mr. John Quinlan Public, Esq.

==== Example 2 ====

<pre><nowiki>
N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P.
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="n">
<span class="honorific-prefix">Dr.</span>
<span class="given-name">John</span>
<span class="additional-name">Philip</span>
<span class="additional-name">Paul</span>
<span class="family-name">Stevenson</span>,
<span class="honorific-suffix">Jr.</span>,
<span class="honorific-suffix">M.D.</span>,
<span class="honorific-suffix">A.C.P.</span>
</span>
</nowiki></pre>

this hCard fragment would be displayed as:

Dr. John Philip Paul Stevenson, Jr., M.D., A.C.P.

=== 3.1.3 NICKNAME Type Definition ===

==== Example 1 ====

<pre><nowiki>
NICKNAME:Robbie
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="nickname">Robbie</span>
</nowiki></pre>

this hCard fragment could be displayed as:

Robbie

==== Example 2 ====

<pre><nowiki>
NICKNAME:Jim,Jimmie
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="nickname">Jim</span>,
<span class="nickname">Jimmie</span>
</nowiki></pre>

this hCard fragment would be displayed as:

Jim, Jimmie

=== 3.1.4 PHOTO Type Definition ===

==== Example 1 ====
<pre><nowiki>
PHOTO;VALUE=uri:http://www.abc.com/pub/photos/jqpublic.gif
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<img class="photo" src="http://www.abc.com/pub/photos/jqpublic.gif" alt="" />
</nowiki></pre>

==== Example 2 ====
<pre><nowiki>
PHOTO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...remainder of "B" encoded binary data...>
</nowiki></pre>

this vCard fragment as an hCard fragment (line breaks inserted into src value for readability):

<pre><nowiki>
<img class="photo" src="data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
...remainder of B encoded binary data..." alt="" />
</nowiki></pre>

=== 3.1.5 BDAY Type Definition ===

==== Example 1 ====

<pre><nowiki>
BDAY:1996-04-15
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<abbr class="bday" title="1996-04-15">April 15, 1996</abbr>
</nowiki></pre>

this hCard fragment could be displayed as:

<abbr class="bday" title="1996-04-15">April 15, 1996</abbr>

==== Example 2 ====

<pre><nowiki>
BDAY:1953-10-15T23:10:00Z
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<abbr class="bday" title="1953-10-15T23:10:00Z">Oct 15, 1953</abbr>
</nowiki></pre>

this hCard fragment could be displayed as:

<abbr class="bday" title="1953-10-15T23:10:00Z">Oct 15, 1953</abbr>

==== Example 3 ====

<pre><nowiki>
BDAY:1987-09-27T08:30:00-06:00
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<abbr class="bday" title="1987-09-27T08:30:00-06:00">Sept 9, 1987</abbr>
</nowiki></pre>

this hCard fragment could be displayed as:

<abbr class="bday" title="1987-09-27T08:30:00-06:00">Sept 9, 1987</abbr>

=== 3.2.1 ADR Type Definition ===

<pre><nowiki>
ADR;TYPE=dom,home,postal,parcel:;;123 Main
Street;Any Town;CA;91921-1234
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<div class="adr">
<abbr class="type" title="dom">US</abbr>
<span class="type">home</span> address, for
<abbr class="type" title="postal">mail</abbr> and
<abbr class="type" title="parcel">shipments</abbr>:
<div class="street-address">123 Main Street</div>
<span class="locality">Any Town</span>, <span class="region">CA</span>,
<span class="postal-code">91921-1234</span>
</div>
</nowiki></pre>

this hCard fragment could be displayed as:

<div class="adr">
<abbr class="type" title="dom">US</abbr>
<span class="type">home</span> address, for
<abbr class="type" title="postal">mail</abbr> and
<abbr class="type" title="parcel">shipments</abbr>:
<div class="street-address">123 Main Street</div>
<span class="locality">Any Town</span>, <span class="region">CA</span>,
<span class="postal-code">91921-1234</span>
</div>

=== 3.2.2 LABEL Type Definition ===

<pre><nowiki>
LABEL;TYPE=dom,home,postal,parcel:Mr.John Q. Public\, Esq.\n
Mail Drop: TNE QB\n123 Main Street\nAny Town\, CA 91921-1234
\nU.S.A.
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
Please use the following address label for
<div class="label">
<abbr class="type" title="dom">local delivery</abbr>
<abbr class="type" title="home">to my home</abbr>
<abbr class="type" title="postal">of mail</abbr>
<abbr class="type" title="parcel">and packages:</abbr>
<pre>
Mr.John Q. Public, Esq.
Mail Drop: TNE QB
123 Main Street
Any Town, CA 91921-1234
U.S.A.
</pre>
</div>
</nowiki></pre>

'''Note:''' the above hCard fragment uses a <pre> tag inside a property value to capture/represent explicit carriage returns ("\n" characters) from the vCard fragment.

this hCard fragment could be displayed as:

Please use the following address label for
<abbr class="type" title="dom">local delivery</abbr>
<abbr class="type" title="home">to my home</abbr>
<abbr class="type" title="postal">of mail</abbr>
<abbr class="type" title="parcel">and packages:</abbr>
<pre>
Mr.John Q. Public, Esq.
Mail Drop: TNE QB
123 Main Street
Any Town, CA 91921-1234
U.S.A.
</pre>

=== 3.3.1 TEL Type Definition ===

<pre><nowiki>
TEL;TYPE=work,voice,pref,msg:+1-213-555-1234
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="tel">
<abbr class="type" title="pref">my</abbr>
<span class="type">work</span>
<abbr class="type" title="voice">phone</abbr>, with
<abbr class="type" title="msg">voicemail</abbr>:
<span class="value">+1-213-555-1234</span>
</span>
</nowiki></pre>

this hCard fragment could be displayed as:

my work phone, with voicemail: +1-213-555-1234

=== 3.3.2 EMAIL Type Definition ===

==== Example 1 ====

<pre><nowiki>
EMAIL;TYPE=internet:jqpublic@xyz.dom1.com
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<a class="email" href="mailto:jqpublic@xyz.dom1.com">email jqpublic</a>
</nowiki></pre>

this hCard fragment could be displayed as:

[mailto:jqpublic@xyz.dom1.com email jqpublic]

==== Example 2 ====

<pre><nowiki>
EMAIL;TYPE=internet:jdoe@isp.net
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<a class="email" href="mailto:jdoe@isp.net">email jdoe</a>
</nowiki></pre>

this hCard fragment could be displayed as:

[mailto:jdoe@isp.net email jdoe]

==== Example 3 ====

<pre><nowiki>
EMAIL;TYPE=internet,pref:jane_doe@abc.com
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<a class="email" href="mailto:jane_doe@abc.com">
<abbr class="type" title="pref">preferred</abbr>
email for jane_doe
</a>
</nowiki></pre>

this hCard fragment could be displayed as:

[mailto:jane_doe@abc.com preferred email for jane_doe]

=== 3.3.3 MAILER Type Definition ===

<pre><nowiki>
MAILER:PigeonMail 2.1
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
Jane Doe uses <span class="mailer">PigeonMail 2.1</span> for email.
</nowiki></pre>

this hCard fragment could be displayed as:

Jane Doe uses <span class="mailer">PigeonMail 2.1</span> for email.

=== 3.4.1 TZ Type Definition ===

==== Example 1 ====

<pre><nowiki>
TZ:-05:00
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="tz">-05:00</span>
</nowiki></pre>

this hCard fragment could be displayed as:

-05:00
==== Example 2 ====

<pre><nowiki>
TZ;VALUE=text:-05:00; EST; Raleigh/North America
;This example has a single value, not a structure text value.
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<abbr class="tz"
title="-05:00; EST; Raleigh/North America;This example has a single value, not a structure text value.">
EST
</abbr>
</nowiki></pre>

this hCard fragment could be displayed as:

<abbr class="tz" title="-05:00; EST; Raleigh/North America;This example has a single value, not a structure text value.">EST</abbr>

=== 3.4.2 GEO Type Definition ===

<pre><nowiki>
GEO:37.386013;-122.082932
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="geo">
<span class="latitude">37.386013</span>,
<span class="longitude">-122.082932</span>
</span>
</nowiki></pre>

this hCard fragment could be displayed as:

37.386013, -122.082932

=== 3.5.1 TITLE Type Definition ===

<pre><nowiki>
TITLE:Director\, Research and Development
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="title">Director, Research and Development</span>
</nowiki></pre>

this hCard fragment could be displayed as:

Director, Research and Development

=== 3.5.2 ROLE Type Definition ===

<pre><nowiki>
ROLE:Programmer
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="role">Programmer</span>
</nowiki></pre>

this hCard fragment could be displayed as:

Programmer

=== 3.5.3 LOGO Type Definition ===

==== Example 1 ====

<pre><nowiki>
LOGO;VALUE=uri:http://www.abc.com/pub/logos/abccorp.jpg
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
<img class="logo" src="http://www.abc.com/pub/logos/abccorp.jpg" alt="my logo" />
</nowiki></pre>

this hCard fragment could be displayed as (note: I used a real URL for the image):

http://microformats.org/img/mf-lg-ora.gif

==== Example 2 ====

<pre><nowiki>
LOGO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of "B" encoded binary data...>
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
<img class="logo" src="data:image/jpeg;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
...remainder of B encoded binary data..." alt="" />
</nowiki></pre>

no display equivalent given, since data: URL from original example is incomplete.

=== 3.5.4 AGENT Type Definition ===

==== Example 1 ====

<pre><nowiki>
AGENT;VALUE=uri:
CID:JQPUBLIC.part3.960129T083020.xyzMail@host3.com
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
<a class="agent" href="CID:JQPUBLIC.part3.960129T083020.xyzMail@host3.com">JQPUBLIC</a>
</nowiki></pre>

this hCard fragment could be displayed as:

JQPUBLIC

==== Example 2 ====

<pre><nowiki>
AGENT:BEGIN:VCARD\nFN:Susan Thomas\nTEL:+1-919-555-
1234\nEMAIL\;INTERNET:sthomas@host.com\nEND:VCARD\n
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
<span class="agent vcard">
<a class="email fn n" href="mailto:sthomas@host.com">Susan Thomas</a>,
<span class="tel">+1-919-555-1234</span>
</span>
</nowiki></pre>

this hCard fragment could be displayed as:

[mailto:sthomas@host.com Susan Thomas], +1-919-555-1234

Note: the vCard in the AGENT property vCard fragment is actually invalid since it lacks an "N" property. However, the hCard version *is* valid, since I added the "n" class name to the example.

=== 3.5.5 ORG Type Definition ===

<pre><nowiki>
ORG:ABC\, Inc.;North American Division;Marketing
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="org">
<span class="organization-name">ABC, Inc.</span>,
<span class="organization-unit">North American Division</span>,
<span class="organization-unit">Marketing</span>,
</span>
</nowiki></pre>

this hCard fragment could be displayed as:

ABC, Inc., North American Division, Marketing

=== 3.6.1 CATEGORIES Type Definition ===

==== Example 1 ====

<pre><nowiki>
CATEGORIES:TRAVEL AGENT
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="category">TRAVEL AGENT</span>
</nowiki></pre>

this hCard fragment could be displayed as:

TRAVEL AGENT

==== Example 2 ====

<pre><nowiki>
CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="category">INTERNET</span>,
<span class="category">IETF</span>,
<span class="category">INDUSTRY</span>,
<span class="category">INFORMATION TECHNOLOGY</span>
</nowiki></pre>

this hCard fragment would be displayed as:

INTERNET, IETF, INDUSTRY, INFORMATION TECHNOLOGY

=== 3.6.2 NOTE Type Definition ===

<pre><nowiki>
NOTE:This fax number is operational 0800 to 1715
EST\, Mon-Fri.
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<p class="note">This fax number is operational 0800 to 1715 EST, Mon-Fri.</p>
</nowiki></pre>

this hCard fragment could be displayed as:

This fax number is operational 0800 to 1715 EST, Mon-Fri.

=== 3.6.3 PRODID Type Definition ===

<pre><nowiki>
PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN
</nowiki></pre>

Note, this vCard property actually doesn't make sense as a hCard property, since it really should be filled in by whatever code transforms the hCard into a vCard, e.g. Brian Suda's X2V.

=== 3.6.4 REV Type Definition ===

==== Example 1 ====

<pre><nowiki>
REV:1995-10-31T22:27:10Z
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<abbr class="rev" title="1995-10-31T22:27:10Z">Updated: 10/31 10:27p</abbr>
</nowiki></pre>

this hCard fragment could be displayed as:

<abbr class="rev" title="1995-10-31T22:27:10Z">Updated: 10/31 10:27p</abbr>

==== Example 2 ====

<pre><nowiki>
REV:1997-11-15
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<abbr class="rev" title="1997-11-15">Updated: November 15</abbr>
</nowiki></pre>

this hCard fragment could be displayed as:

<abbr class="rev" title="1997-11-15">Updated: November 15</abbr>

=== 3.6.5 SORT-STRING Type Definition ===

==== Example 1 ====

<pre><nowiki>
FN:Rene van der Harten
N:van der Harten;Rene;J.;Sir;R.D.O.N.
SORT-STRING:Harten
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="n"
<span class="honorific-prefix">Sir</span>
<span class="fn">
<span class="given-name">Rene</span>
<span class="family-name">
van der <span class="sort-string">Harten</span>
</span>
</span>
(<span class="additional-name">J.</span>),
<span class="honorific-suffix">R.D.O.N.</span>
</span>
</nowiki></pre>

Note: The string "Harten" was NOT repeated in the hCard, even though it WAS repeated in the vCard (3 times! In N, FN, and SORT-STRING). The "SORT-STRING" property provides another good demonstration of how hCard enables better adherence to the [http://microformats.org/wiki/hcard-example1-steps#hCard_example_iteration_1:_DRY DRY principle] than vCard.

this hCard fragment could be displayed as:

Sir Rene van der Harten (J.), R.D.O.N.

==== Example 2 ====

<pre><nowiki>
FN:Robert Pau Shou Chang
N:Pau;Shou Chang;Robert
SORT-STRING:Pau
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="fn n">
<span class="additional-name">Robert</span>
<span class="family-name sort-string">Pau</span>
<span class="given-name">Shou Chang</span>
</span>
</nowiki></pre>

Note: Not only was the string "Pau" was NOT repeated in the hCard (better [http://microformats.org/wiki/hcard-example1-steps#hCard_example_iteration_1:_DRY DRY principle] adherence again), even though it WAS repeated in the vCard, but in this case since the "family-name" and "sort-string" are the same, we were able to use [http://microformats.org/wiki/hcard-example1-steps#hCard_example_iteration_2:_element_conservation element conservation] and use only one element for both properties.

this hCard fragment could be displayed as:

Robert Pau Shou Chang

==== Example 3 ====

<pre><nowiki>
FN:Osamu Koura
N:Koura;Osamu
SORT-STRING:Koura
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="fn">
Osamu <span class="sort-string">Koura</span>
</span>
</nowiki></pre>

Note: This example, in addition to illustrating better support for the [http://microformats.org/wiki/hcard-example1-steps#hCard_example_iteration_1:_DRY DRY principle], also makes use of the [http://microformats.org/wiki/hcard#Implied_.22N.22_Optimization Implied "N" Optimization].

this hCard fragment could be displayed as:

Osamu Koura

==== Example 4 ====

<pre><nowiki>
FN:Oscar del Pozo
N:del Pozo Triscon;Oscar
SORT-STRING:Pozo
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="n">
<span class="fn">
<span class="given-name">Oscar</span>
del <span class="sort-string">Pozo</span>
</span>
<span class="family-name" style="display:none">
del Pozo Triscon
</span>
</span>
</nowiki></pre>

Note: This example unfortunately could not completely adhere to the DRY principle due to the "FN" using a *substring* of the family-name, and in addition thus had to hide the extra "family-name" string value using CSS display:none, which in general should be avoided. Suggestion welcome for improvements on this hCard fragement.

this hCard fragment could be displayed as:

Oscar del Pozo

==== Example 5 ====

<pre><nowiki>
FN:Christine d'Aboville
N:d'Aboville;Christine
SORT-STRING:Aboville
</nowiki></pre>

this vCard fragment as an hCard fragment:

<pre><nowiki>
<span class="fn">
Christine d'<span class="sort-string">Aboville</span>
</span>
</nowiki></pre>

Note: This example re-demonstrates the same hCard advantages/efficiencies demonstrated in [http://microformats.org/wiki/hcard-examples#Example_3_3 example 3] above.

this hCard fragment could be displayed as:

Christine d'Aboville

=== 3.6.6 SOUND Type Definition ===

==== Example 1 ====

<pre><nowiki>
SOUND;TYPE=BASIC;VALUE=uri:CID:JOHNQPUBLIC.part8.
19960229T080000.xyzMail@host1.com
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
<object class="sound" type="audio/basic"
data="CID:JOHNQPUBLIC.part8.19960229T080000.xyzMail@host1.com">
pronounciation of "JOHN Q PUBLIC"
</object>
</nowiki></pre>

this hCard fragment would probably be displayed as

pronounciation of "JOHN Q PUBLIC"

unless your browser supports the MIME type "audio/basic" (defined in [http://www.rfc-editor.org/rfc/rfc2046.txt RFC2046 section 4.3]) and has some way of retrieving "CID:" urls.

==== Example 2 ====
<pre><nowiki>
SOUND;TYPE=BASIC;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of "B" encoded binary data...>
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
<object class="sound"
data="data:audio/basic;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
...the remainder of "B" encoded binary data...">
pronounciation
</object>
</nowiki></pre>

no display equivalent given, since data: URL from original example is incomplete.

=== 3.6.7 UID Type Definition ===

<pre><nowiki>
UID:19950401-080045-40000F192713-0052
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
Unique id:
<span class="uid">19950401-080045-40000F192713-0052</span>
</nowiki></pre>

this hCard fragment could be displayed as

Unique id:19950401-080045-40000F192713-0052

Note: in practice I don't think I've seen globally unique IDs for "contact info" records published on the web, but perhaps I am not considering enough examples.

=== 3.6.8 URL Type Definition ===

<pre><nowiki>
URL:http://www.swbyps.restaurant.french/~chezchic.html
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
<a class="url" href="http://www.swbyps.restaurant.french/~chezchic.html">Chez Chic</a>
</nowiki></pre>

this hCard fragment could be displayed as

[http://www.swbyps.restaurant.french/~chezchic.html Chez Chic]

=== 3.7.1 CLASS Type Definition ===

==== Example 1 ====

<pre><nowiki>
CLASS:PUBLIC
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
<span class="class">PUBLIC</span>
</nowiki></pre>

this hCard fragment could be displayed as

PUBLIC

==== Example 2 ====

<pre><nowiki>
CLASS:PRIVATE
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
<span class="class">PRIVATE</span>
</nowiki></pre>

this hCard fragment could be displayed as

PRIVATE

==== Example 3 ====

<pre><nowiki>
CLASS:CONFIDENTIAL
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
<span class="class">CONFIDENTIAL</span>
</nowiki></pre>

this hCard fragment could be displayed as

CONFIDENTIAL

=== 3.7.2 KEY Type Definition ===

<pre><nowiki>
KEY;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQA
wdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENbW11bmljYX
Rpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
ZW1zMRwwGgYDVQQDExNyb290Y2EubmV0c2NhcGUuY29tMB4XDTk3MDYwNj
E5NDc1OVoXDTk3MTIwMzE5NDc1OVowgYkxCzAJBgNVBAYTAlVTMSYwJAYD
VQQKEx1OZXRzY2FwZSBDb21tdW5pY2F0aW9ucyBDb3JwLjEYMBYGA1UEAx
MPVGltb3RoeSBBIEhvd2VzMSEwHwYJKoZIhvcNAQkBFhJob3dlc0BuZXRz
Y2FwZS5jb20xFTATBgoJkiaJk/IsZAEBEwVob3dlczBcMA0GCSqGSIb3DQ
EBAQUAA0sAMEgCQQC0JZf6wkg8pLMXHHCUvMfL5H6zjSk4vTTXZpYyrdN2
dXcoX49LKiOmgeJSzoiFKHtLOIboyludF90CgqcxtwKnAgMBAAGjNjA0MB
EGCWCGSAGG+EIBAQQEAwIAoDAfBgNVHSMEGDAWgBT84FToB/GV3jr3mcau
+hUMbsQukjANBgkqhkiG9w0BAQQFAAOBgQBexv7o7mi3PLXadkmNP9LcIP
mx93HGp0Kgyx1jIVMyNgsemeAwBM+MSlhMfcpbTrONwNjZYW8vJDSoi//y
rZlVt9bJbs7MNYZVsyF1unsqaln4/vy6Uawfg8VUMk1U7jt8LYpo4YULU7
UZHPYVUaSgVttImOHZIKi4hlPXBOhcUQ==
</nowiki></pre>

this vCard fragment as an hCard fragment

<pre><nowiki>
<object class="key" type="application/octet-stream"
data="data:application/octet-stream;base64,MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQA
wdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENbW11bmljYX
Rpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
ZW1zMRwwGgYDVQQDExNyb290Y2EubmV0c2NhcGUuY29tMB4XDTk3MDYwNj
E5NDc1OVoXDTk3MTIwMzE5NDc1OVowgYkxCzAJBgNVBAYTAlVTMSYwJAYD
VQQKEx1OZXRzY2FwZSBDb21tdW5pY2F0aW9ucyBDb3JwLjEYMBYGA1UEAx
MPVGltb3RoeSBBIEhvd2VzMSEwHwYJKoZIhvcNAQkBFhJob3dlc0BuZXRz
Y2FwZS5jb20xFTATBgoJkiaJk/IsZAEBEwVob3dlczBcMA0GCSqGSIb3DQ
EBAQUAA0sAMEgCQQC0JZf6wkg8pLMXHHCUvMfL5H6zjSk4vTTXZpYyrdN2
dXcoX49LKiOmgeJSzoiFKHtLOIboyludF90CgqcxtwKnAgMBAAGjNjA0MB
EGCWCGSAGG+EIBAQQEAwIAoDAfBgNVHSMEGDAWgBT84FToB/GV3jr3mcau
+hUMbsQukjANBgkqhkiG9w0BAQQFAAOBgQBexv7o7mi3PLXadkmNP9LcIP
mx93HGp0Kgyx1jIVMyNgsemeAwBM+MSlhMfcpbTrONwNjZYW8vJDSoi//y
rZlVt9bJbs7MNYZVsyF1unsqaln4/vy6Uawfg8VUMk1U7jt8LYpo4YULU7
UZHPYVUaSgVttImOHZIKi4hlPXBOhcUQ==">
Key
</object>

</nowiki></pre>

this hCard fragment could be displayed as

Key

Note: Because of the lack of a TYPE value in the RFC2426 example, I substituted application/octet-stream. Clearly for it to be of some use, the type specified must be some sort of key or certificate mime type.

=== 7. Authors' Addresses ===

<pre><nowiki>
BEGIN:vCard
VERSION:3.0
FN:Frank Dawson
ORG:Lotus Development Corporation
ADR;TYPE=WORK,POSTAL,PARCEL:;;6544 Battleford Drive
;Raleigh;NC;27613-3502;U.S.A.
TEL;TYPE=VOICE,MSG,WORK:+1-919-676-9515
TEL;TYPE=FAX,WORK:+1-919-676-9564
EMAIL;TYPE=INTERNET,PREF:Frank_Dawson@Lotus.com
EMAIL;TYPE=INTERNET:fdawson@earthlink.net
URL:http://home.earthlink.net/~fdawson
END:vCard

BEGIN:vCard
VERSION:3.0
FN:Tim Howes
ORG:Netscape Communications Corp.
ADR;TYPE=WORK:;;501 E. Middlefield Rd.;Mountain View;
CA; 94043;U.S.A.
TEL;TYPE=VOICE,MSG,WORK:+1-415-937-3419
TEL;TYPE=FAX,WORK:+1-415-528-4164
EMAIL;TYPE=INTERNET:howes@netscape.com
END:vCard
</nowiki></pre>

Note that both of these vCards are invalid since they lack the REQUIRED "N" property which is quite ironic, since these are the vCards of the authors themselves.

Nonetheless, these vCards can be represented by the following hCards:

<pre><nowiki>
<div class="vcard">
<a class="url fn" href="http://home.earthlink.net/~fdawson">Frank Dawson</a>
<div class="org">Lotus Development Corporation</div>
<div class="adr">
<span class="type">work</span> address
(<abbr class="type" title="postal">mail</abbr> and
<abbr class="type" title="parcel">packages</abbr>):
<div class="street-address">6544 Battleford Drive</div>
<span class="locality">Raleigh</span>
<span class="region">NC</span>
<span class="postal-code">27613-3502</span>
<div class="country-name">U.S.A.</div>
</div>
<div class="tel">
<span class="value">+1-919-676-9515</span>
(<abbr class="type" title="WORK">w</abbr>,
<abbr class="type" title="VOICE">v</abbr><abbr class="type" title="MSG">m</abbr>)
</div>
<div class="tel">
<span class="value">+1-919-676-9564</span>
(<abbr class="type" title="WORK">w</abbr><abbr class="type" title="FAX">f</abbr>)
</div>
<a class="email" href="mailto:Frank_Dawson@Lotus.com">
<span class="type">pref<span>erred</span> email</span>
</a>,
<a class="email" href="mailto:fdawson@earthlink.net">
alternate email
</a>
</div>
<div class="vcard">
<a class="email fn" href="mailto:howes@netscape.com">Tim Howes</a>
<div class="org">Netscape Communications Corp.</div>
<div class="adr">
<span class="type">work</span> address:
<div class="street-address">501 E. Middlefield Rd.</div>
<span class="locality">Mountain View</span>,
<span class="region">CA</span>
<span class="postal-code">94043</span>
<div class="country-name">U.S.A.</div>
</div>
<div class="tel">
<span class="value">+1-415-937-3419</span>
(<abbr class="type" title="WORK">w</abbr>,
<abbr class="type" title="VOICE">v</abbr><abbr class="type" title="MSG">m</abbr>)
</div>
<div class="tel">
<span class="value">+1-415-528-4164</span>
(<abbr class="type" title="WORK">w</abbr><abbr class="type" title="FAX">f</abbr>)
</div>
</div>
</nowiki></pre>

this hCards could be displayed as

<div class="vcard">
[http://home.earthlink.net/~fdawson Frank Dawson]
<div class="org">Lotus Development Corporation</div>
<div class="adr">
<span class="type">work</span> address
(<abbr class="type" title="postal">mail</abbr> and
<abbr class="type" title="parcel">packages</abbr>):
<div class="street-address">6544 Battleford Drive</div>
<span class="locality">Raleigh</span>
<span class="region">NC</span>
<span class="postal-code">27613-3502</span>
<div class="country-name">U.S.A.</div>
</div>
<div class="tel">
<span class="value">+1-919-676-9515</span>
(<abbr class="type" title="WORK">w</abbr>,
<abbr class="type" title="VOICE">v</abbr><abbr class="type" title="MSG">m</abbr>)
</div>
<div class="tel">
<span class="value">+1-919-676-9564</span>
(<abbr class="type" title="WORK">w</abbr><abbr class="type" title="FAX">f</abbr>)
</div>
[mailto:Frank_Dawson@Lotus.com preferred email],
[mailto:fdawson@earthlink.net alternate email]
</div>

<div class="vcard">
[mailto:howes@netscape.com Tim Howes]
<div class="org">Netscape Communications Corp.</div>
<div class="adr">
<span class="type">work</span> address:
<div class="street-address">501 E. Middlefield Rd.</div>
<span class="locality">Mountain View</span>,
<span class="region">CA</span>
<span class="postal-code">94043</span>
<div class="country-name">U.S.A.</div>
</div>
<div class="tel">
<span class="value">+1-415-937-3419</span>
(<abbr class="type" title="WORK">w</abbr>,
<abbr class="type" title="VOICE">v</abbr><abbr class="type" title="MSG">m</abbr>)
</div>
<div class="tel">
<span class="value">+1-415-528-4164</span>
(<abbr class="type" title="WORK">w</abbr><abbr class="type" title="FAX">f</abbr>)
</div>
</div>

== Test Cases ==

These are [[hcard|hCard]] examples which have been found to be particularly useful in finding bugs in hCard parsers (e.g. X2V).

=== Problem with BDAY Information ===

this example:

<pre>

<div class="bday">
<dt>Birthday</dt>
<dd>
<abbr class="value" title="1985-10-27T00:00:00Z">October 27, 1985</abbr>
</dd>
</div>
</pre>

ought to produce "BDAY:1985-10-27T00:00:00Z" but it produces "BDAY:Birthday October 27\, 1985". interesting is that the apple addressbook is still willing to accept it in this way.

=== case-INSENSITIVITY of type values ===

* "home" vs. "Home"

this example works with X2V:

<pre>
<div class="tel">
<dt>Phone (<span class="type">home</span>)</dt>
<dd><span class="value">+438123418</span></dd>
</div>
</pre>

this does not, but should. but instead it becomes just TEL without a type in the vcard

<pre>
<div class="tel">
<dt>Phone (<span class="type">Home</span>)</dt>
<dd><span class="value">+438123418</span></dd>
</div>
</pre>

=== GEO parsing ===
The following hCard:

<pre><nowiki>
<div class="vcard">
<span class="n">
<a class="url" href="http://t37.net">
<span class="given-name">Fréderic</span>
<span class="family-name">de Villamil</span>
</a>
</span>
<span class="nickname">neuro</span>
<a class="email" href="mailto:neuroNOSPAM@t37.net">
<span class="type">pref<span>erred</span> email</span>
</a>
<span class="org">Omatis</span>
<span class="adr">
<abbr class="type" title="dom">France</abbr>
<span class="type">home</span> address
<abbr class="type" title="postal">mail</abbr> and
<abbr class="type" title="parcel">shipments</abbr>:
<span class="street-address">12 rue Danton</span>
<span class="locality">Le Kremlin-Bicetre</span>
<span class="postal-code">94270</span>
<span class="country-name">France</span>
</span>
<span class="geo">
<abbr class="latitude" title="48.816667">N 48° 81.6667</abbr>
<abbr class="longitude" title="2.366667">E 2° 36.6667</abbr>
</span>
</div>
</nowiki>
</pre>

Should be translated into the following vCard:

<pre><nowiki>
BEGIN:VCARD
VERSION:3.0
URL:http://t37.net
ORG:Omatis;;
NICKNAME:neuro
N:de Villamil;Frederic;;Mr.;
EMAIL;TYPE=INTERNET,PREF:neuroNOSPAM@t37.net
ADR;TYPE=HOME:;;12 rue danton;le Kremlin-Bicetre;;94270;France
GEO:48.816667;2.366667
END:VCARD
</nowiki></pre>

X2V currently (2005-12-18) fails to parse/export the GEO property at all.

== Other ==

* See [[hcard-brainstorming]] for more examples (which may eventually be moved here) and analysis.

citation-irc-meetup

2006-03-30T02:36:03Z

Tim White: /* Attendees */

There has been an explosion of messages to the mailing list about the citation format. I think it would be best for everyone interested in contributing to try and set aside 30-60 minutes so we can all meet in the IRC room and hammer out alot of the simple things and get a road map for the larger pictures.

I would like to try to get the first meeting within the next 10 days, so please put your name with a time that works best for you. REMEMBER we span different timezone, so maybe a weekend is best?

== Attendees ==
* [http://suda.co.uk/ Brian Suda] (-0600) TZ, Any day after 19:00 (7pm) or weekends
* [http://michael-mccracken.net/ Michael McCracken] (-0800) TZ, Any day after 4pm or weekends, starting Tuesday, Apr. 4.
* [http://tjameswhite.com/ Tim White] (-0500)TZ, Weekends best (except April 7-8), or after 7pm (no Tuesdays)

== things to discuss ==
* ???
* ???

citation-examples

2006-02-26T21:16:25Z

Tim White:

<h1> Citation Examples </h1>

The following examples are real world examples of citations found on the web. Please add to this list. The idea is that we get a solid sample of examples and see what commonalities there are amonst them and try to build this microformat so that it can meet 80% of typical uses.

See also:
* [[citation]]
* [[citation-formats]]
* [[citation-brainstorming]]

__TOC__

== Contributors ==
* ...
* ...
* Tantek Çelik
* [http://michael-mccracken.net/wp/ Michael McCracken]
* Tim White

== Citation Mark Up in the Wild ==
Mark up examples from reference publisher's websites (online catalogs), including ABC-CLIO, Greenwood Press, Marshall Cavendish, Oxford University Press (USA) and Thomson Gale. Examples are broken down and organized by element.

(For a cleaner version, see [http://www.tjameswhite.com/citation-examples.htm])

=== ABC-CLIO Product [http://www.abc-clio.com/products/overview.aspx?productid=109327 detail page] ===
<pre>
<table border="0" cellpadding="0" cellspacing="0" width="430">
<tr>
<td width="101" valign="top" align="left"></td>
<td width="102" valign="top" align="left"></td>
<td width="101" valign="top" align="left"></td>
<td width="125" valign="top" align="center"></td>
</tr>
<tr>
<td width="430" colspan="4" class="productsubtitle"><span id="serieslbl" class="productsubtitle"><a href="browseseries.aspx?seriesid=33">Teaching With Documents Series</a></span></td>
</tr>
<tr>
<td width="430" colspan="4" class="producttitle"><span id="title" class="producttitle">The 1920's</span></td>
</tr>
<tr>
<td width="430" colspan="4" class="productsubtitle"><span id="subtitle" class="productsubtitle"></span></td>
</tr>
<tr>
<td width="430" colspan="4" class="productauthor"><span id="credit" class="productauthor"></span></td>
</tr>
<tr>
<td width="430" colspan="4" height="12"><img border="0" src="../images/blank-white.gif" width="1" height="12" alt=""/></td>
</tr>
<tr>
<td width="130" align="left"><img id="productImage" src="../images/dbimages/1011\101103.GIF" alt="" style="border-width:0px;width:115px;" /></td>
<td width="300" valign="top" align="right" colspan="3">
<table border="0" cellpadding="0" cellspacing="0" width="290">
<tr>
<td width="110" class="productdetailhead"><span id="pubdatelabel" class="productdetailhead">Publication Date</span></td>
<td width="180" class="productdetailbody"><span id="pubdate" class="productdetailbody">11/2001</span></td>
</tr>
<tr>
<td width="110" class="productdetailhead"><span id="pageslabel" class="productdetailhead">Pages</span></td>
<td width="180" class="productdetailbody"><span id="pages" class="productdetailbody">132</span></td>
</tr>
<tr>
<td width="110" class="productdetailhead"><span id="volumeslabel" class="productdetailhead">Volumes</span></td>
<td width="180" class="productdetailbody"><span id="volumes" class="productdetailbody">1</span></td>
</tr>
<tr>
<td width="110" class="productdetailhead"><span id="trimlabel" class="productdetailhead">Size</span></td>
<td width="180" class="productdetailbody"><span id="trimsize" class="productdetailbody">8.5x11</span></td>
</tr>
</table>


<table id="PriceTable" cellspacing="0" cellpadding="0" width="290" border="0">
<tr>
<td class="productdetailhead" width="290" height="15" colspan="4"><img src="../images/academic/blank-blue.gif" id="PriceLine" width="290" height="1" border="0" /></td>
</tr>
<tr>
<td class="productdetailhead" width="54">Format</td>
<td class="productdetailhead" width="68">Price</td>
<td class="productdetailhead" width="88"><span id="ISBNLabel">ISBN</span></td>
<td class="productdetailhead" width="80"> </td>
</tr>
<tr>
<td class="productdetailhead"><b>Print</b></td>
<td class="productdetailbody">$39.00</td>
<td class="productdetailbody">1-57607-785-3</td>
<td class="productdetailhead"> </td>
</tr>
</table>

</td>
</tr>
</table>
</div>
</pre>

=== Greenwood Press [http://www.greenwood.com/ home page] featured book ===
<pre>
<div class="title"> <a href="/books/BookDetail.asp?sku=GR2847">The Greenwood Encyclopedia of World Folklore and Folklife</a> </div>
<div class="img_box"> <a href="/books/BookDetail.asp?sku=GR2847"> <img src="/_net.templates/showImage.aspx?imgName=0313328471.jpg&s=140" alt="The Greenwood Encyclopedia of World Folklore and Folklife" border="0" /></a> </div>
<div class="sub_title">Four Volumes</div>
<div class="author">William M. Clements</div>
<div class="isbn">0-313-32847-1</div>
<div class="price">$449.95 <span class="pipe">|</span> £255.00</div>

<div class="bookDescription"> China . . . Malta . . . Madagascar . . . Wales . . . and Texas: these are among the many exotic, distant lands that capture our minds and imaginations. In an era of increasing globalization, students, general readers, and business professionals need to know about... <a href="/books/BookDetail.asp?sku=GR2847">Read more</a> </div>
</div>
</pre>

=== Greenwood Press [http://www.greenwood.com/catalog/GR2847.aspx Product detail page] ===
<pre>
<div id="pnlContent" class="pnlContent">
<div id="pnlFlyerBox" class="flyerBox"> <a id="hlFlyer" class="flyerLink" href="/books/printFlyer.aspx?sku=GR2847" target="_blank">Print book flyer</a> <br />
<a id="hlFlyerInternational" class="international_flyer" href="/books/printFlyer.aspx?sku=GR2847&location=international" target="_blank">(International version)</a> </div>
<span id="lblTitle" class="book_headline block">The Greenwood Encyclopedia of World Folklore and Folklife</span> <span id="lblSubTitle" class="book_subline">Four Volumes</span>
<div id="pnlBookDetails" class="detailsBox">
<div id="pnlImgBox" class="imgBox"> <img src="/_net.templates/showImage.aspx?imgName=0313328471.jpg&s=135" alt="" border="0" /> </div>
<a id="hlAddToCart" title="Add this item to your shopping cart" href="/shopping_cart/?sku=GR2847"><img title="Add this item to your shopping cart" src="/_net.templates/roundedButton.aspx?ButtonText=Add to Cart" alt="" border="0" /></a> <a id="hlAddToWishList" title="Save this item to your wish list" href="/wish_list/?sku=GR2847"><img title="Save this item to your wish list" src="/_net.templates/roundedButton.aspx?ButtonText=Add to Wish List" alt="" border="0" /></a> <a id="hlSharePage" title="Email this page to a friend" href="/books/sendform.asp?sku=GR2847" target="_blank"><img title="Email this page to a friend" src="/_net.templates/roundedButton.aspx?ButtonText=Email" alt="" border="0" /></a> <a id="hlPrintPage" title="Version of this page optimized for printing" href="/catalog/GR2847.aspx?print=1" target="_blank"><img title="Version of this page optimized for printing" src="/_net.templates/roundedButton.aspx?ButtonText=Print" alt="" border="0" /></a> <a id="hlWorldCat" href="http://worldcatlibraries.org/wcpa/isbn/0313328471" style="FLOAT: right"><img src="/images/world_catalog.gif" alt="" border="0" /></a>
<div class="authors"><span><a href="/catalog/author/C/229.aspx">William M. Clements</a> (ed.)</span></div>
<span id="lblAuthorsNote" class="block"></span>
<div><span class="book_options">Book Code:</span> <span id="lblBookCode">GR2847</span></div>
<div id="pnlIsbn"> <span class="book_options">ISBN:</span> <span id="lblIsbn">0-313-32847-1</span> </div>
<div id="pnlPageColation"> 1972 pages, maps; photos </div>
<span id="lblImprint" class="block">Greenwood Press</span>
<div id="pnlPubDate"> <span class="book_options">Publication Date:</span> <span id="lblPubDate">12/30/2005</span> </div>
<div id="pnlListPrice"> <span class="book_options">List Price:</span> <span id="lblListPrice">$449.95</span> (<a href="/contactus/order_info.asp?SectionID=about&Location=order_info#UKEME" title="Click for international ordering information">UK Sterling Price: £255.00</a>) </div>
<div id="pnlAvailability"> <span class="book_options">Availability:</span> <span id="lblAvailability">In Stock</span> </div>
<div id="pnlMediaType"> <span class="book_options">Media Type:</span> <span id="lblMediaType">Hardcover</span> </div>
<div class="clearing"></div>
</div>
<div id="pnlBookInformation"> <span class="book_options">Subjects:</span>
<ul class="toc">
<li> <a id="rpCategories__ctl1_hlCategory" href="/catalog/subject/Anthropology.aspx">Anthropology</a> » <a id="rpCategories__ctl1_hlSubCategory" href="/catalog/subject/Anthropology/Folklore.aspx">Folklore</a> </li>
<li> <a id="rpCategories__ctl2_hlCategory" href="/catalog/subject/Anthropology.aspx">Anthropology</a> » <a id="rpCategories__ctl2_hlSubCategory" href="/catalog/subject/Anthropology/Anthropology%2b(General).aspx">Anthropology (General)</a> </li>
<li> <a id="rpCategories__ctl3_hlCategory" href="/catalog/subject/Anthropology.aspx">Anthropology</a> » <a id="rpCategories__ctl3_hlSubCategory" href="/catalog/subject/Anthropology/Cultural%2bAnthropology.aspx">Cultural Anthropology</a> </li>
<li> <a id="rpCategories__ctl4_hlCategory" href="/catalog/subject/History.aspx">History</a> » <a id="rpCategories__ctl4_hlSubCategory" href="/catalog/subject/History/World%2bHistory%2b(General).aspx">World History (General)</a> </li>
</ul>
<div id="pnlDescription"> <span class="book_options">Description:</span> <span id="lblDescription1" class="description block">China . . . Malta . . . Madagascar . . . Wales . . . and Texas: these are among the many exotic, distant lands that capture our minds and imaginations. In an era of increasing globalization, students, general readers, and business professionals need to know about the world and its varied ways. So too, a knowledge of world cultures is fundamental to an understanding of America's ethnically rich society. Folklore isn't just about the long ago and far away. It's about the here and now, and there's no better way to learn about cultural diversity than to study the folklore and folkways of different ethnic groups. <br />
More than just Cinderella and other fairy tales, folklore encompasses the whole realm of traditional beliefs and activities that define a culture. The most comprehensive work of its kind, this massive encyclopedia engagingly and authoritatively surveys folklife and traditions from around the world. Through its vast scope and lengthy entries, it transcends other references on particular national or regional folklores and is the most ambitious undertaking of its type. Organized in four volumes, the encyclopedia provides convenient access to information about folklore generally and to the traditions of particular regions:<br />
Volume 1: Topics and Themes, Africa, Australia and Oceania<br />
Volume 2: Southeast Asia and India, Central and East Asia, Middle East<br />
Volume 3: Europe<br />
Volume 4: North and South America</span> <span id="lblDescription2" class="description block">Along with the expertise of the contributors, of Volume Editor William M. Clements, and of Advisory Editor Thomas A. Green, the encyclopedia draws upon a distinguished board of internationally recognized scholars, including:<br />
<li> Roger D. Abrahams<br />
</li>
<li> Cristina Bacchilega<br />
</li>
<li> Gillian Bennett<br />
</li>
<li> Mary Ellen Brown<br />
</li>
<li> James R. Dow<br />
</li>
<li> Alessandro Falassi<br />
</li>
<li> Barbro Klein<br />
</li>
<li> Peter Knecht<br />
</li>
<li> Natalie Kononenko<br />
</li>
<li> Frances M. Malpezzi<br />
</li>
<li> Margaret Mills<br />
</li>
<li> M. D. Muthukumaraswamy<br />
</li>
<li> Gerald Pocius<br />
</li>
<li> And John S. Ryan.<br />
<br />
<b>Features:</b><br />
</li>
<li> Brings together the knowledge of more than 200 specialists from around the world.<br />
</li>
<li> Provides 39 extended entries on topics central to world folklore.<br />
</li>
<li> Details the folklore and folkways of roughly 170 cultural groups.<br />
</li>
<li> Entries discuss the background, beliefs, oral and theatrical traditions, arts and crafts, and contemporary concerns of each cultural group.<br />
</li>
<li> Each entry cites numerous works for further reading.<br />
</li>
<li> A generous selection of maps and illustrations makes world folklore come to life.<br />
</li>
<li> A list of entries and a cumulative subject index, repeated in each volume, offer convenient access to the vast body of information contained in the encyclopedia.<br />
</li>
<li> A selected, general bibliography directs students and general readers to the most important broad studies of world folklore.<br />
</li>
<li> A glossary defines key terms, theories, and concepts.<br />
<br />
<b>Benefits:</b><br />
</li>
<li> Helps students learn about cultures, customs, and daily life around the world.<br />
</li>
<li> Fosters respect and appreciation for the many ethnic traditions behind contemporary American culture.<br />
</li>
<li> Provides valuable background information for the study of world religions, holidays, and festivals.<br />
</li>
<li> Offers a valuable context for understanding world history, politics, literature, and the arts.<br />
</li>
<li> Invites students to compare and contrast the values and experiences of different cultures.<br />
</li>
<li> Fosters critical reading skills and serves as a model for student research.<br />
<br />
<b>Volume 1: Topics and Themes, Africa, Australia and Oceania</b><br />
Certain themes and topics are central to world foklore. The thematic essays in this volume discuss such matters as:<br />
</li>
<li> Antiquarianism<br />
</li>
<li> Cultural Evolution<br />
</li>
<li> Ethnopoetics<br />
</li>
<li> Gender<br />
</li>
<li> Invented Tradition<br />
</li>
<li> Nativism<br />
</li>
<li> Primitivism<br />
</li>
<li> Public Folklore<br />
</li>
<li> Race<br />
</li>
<li> Trickster<br />
</li>
<li> And many more.<br />
<br />
<b>Volume 2: Southeast Asia and India, Central and East Asia, Middle East</b><br />
Included in this volume are entries on such cultural groups and regions as:<br />
</li>
<li> Bali<br />
</li>
<li> China<br />
</li>
<li> Duna<br />
</li>
<li> Iban<br />
</li>
<li> Kazakh<br />
</li>
<li> Mongol<br />
</li>
<li> Orissa<br />
</li>
<li> Palestine<br />
</li>
<li> Tonga<br />
</li>
<li> Uyghur<br />
</li>
<li> And many others.<br />
<br />
<b>Volume 3: Europe</b><br />
Included in this volume are entries on the folklore of such cultural regions and groups as:<br />
</li>
<li> Ashkenazim<br />
</li>
<li> Basque<br />
</li>
<li> Brittany<br />
</li>
<li> Flanders<br />
</li>
<li> Germany<br />
</li>
<li> Isle of Man<br />
</li>
<li> Roma<br />
</li>
<li> Russia<br />
</li>
<li> Sami<br />
</li>
<li> Ukraine<br />
</li>
<li> And many more.<br />
<br />
<b>Volume 4: North and South America</b><br />
The entries in this volume explore the folk traditions of such regions and groups as:<br />
</li>
<li> Appalachia<br />
</li>
<li> Choctaw<br />
</li>
<li> Haiti<br />
</li>
<li> Island Carib<br />
</li>
<li> Maya<br />
</li>
<li> Quechua<br />
</li>
<li> Seminole<br />
</li>
<li> Western Inuit and Yupik<br />
</li>
<li> Xavante<br />
</li>
<li> Yanomami<br />
</li>
<li> And many more.<br />
<br />
Because folklore is the essence of daily life, this encyclopedia addresses the curriculum needs of high school students and is also an indispensable resource for teachers. In addition, anyone researching folklore in a public library will find this the first place to look for detailed information about cultural traditions around the world.</li>
</span> </div>
<div id="pnlLCCardNumber" class="description"> <span class="book_options">LC Card Number:</span> <span id="lblLCCardNumber">2005019219</span> </div>
<div id="pnlLCCClass" class="description"> <span class="book_options">LCC Class:</span> <span id="lblLCCClass">GR35 </span> </div>
<div id="pnlDeweyClass" class="description"> <span class="book_options">Dewey Class:</span> <span id="lblDeweyClass">398</span> </div>
</div>
</div>
</div>
</pre>

=== Marshall Cavendish [http://www.marshallcavendish.com/marshallcavendish/academic/redirector.xml?url=/marshallcavendish/academic/catalogue/books/regionalism_n_regional_security/9812102108.xml product page] ===
<pre>
<table cellpadding="2" width="100%">
<tr valign="top">
<td><font id="title_catalogue_font"><b>Regionalism & Regional Security</b></font></td>
</tr>
</table>
<font id="text">
<div style="" align="">
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">ISBN Number</font></td>
<td width="65%"><font id="text">9812102108</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Series</font></td>
<td width="65%"><font id="text">null</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Title</font></td>
<td width="65%"><font id="text">The New Terrorism: Anatomy, Trends and Counter-strategies</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Imprint</font></td>
<td width="65%"><font id="text">Eastern Universities Press</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Specifications</font></td>
<td width="65%"><font id="text">152 mm X 227 mm, 368 pp, limp with flaps, 500 gms</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Authors</font></td>
<td width="65%"><font id="text">Andrew Tan & Kumar Ramakrishna (eds)</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Target Audience</font></td>
<td width="65%"><font id="text">University lecturers/researchers, undergraduate students, academicians and those interested in Regional Security Studies.</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Price (SG)</font></td>
<td width="65%"><font id="text">S$ 39.00</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Price (US)</font></td>
<td width="65%"><font id="text">US$ 30.00</font>   <a href="javascript: addToCart()"><img src="/marshallcavendish/components/db_content/MC_AC_redirector/pic/addCart.gif" border="0"/></a></td>
</tr>
</table>
<br/>
<br/>
The terrorist attacks of September 11, 2001 on the World Trade Centre in New York and the Pentagon in Washington represented a true watershed in world history.<br/>
<br/>
The attacks revealed the horrifying nature of the so-called "new terrorism" that has emerged in the post-Cold War era. The new terrorism is defined by four key features:</div>
</font>
<ul>
<li>
<p align="justify"><font id="text">sheer lethality</font></p>
</li>
<li>
<p align="justify"><font id="text">religious dimension</font></p>
</li>
<li>
<p align="justify"><font id="text">networked organizational structure</font></p>
</li>
<li>
<p align="justify"><font id="text">greatly enhanced striking power   </font></p>
</li>
</ul>
<font id="text">
<div style="" align="">As September 11 clearly demonstrated, the new terrorists can leverage on technology to inflict catastrophic damage even on superpowers, let alone other states.<br/>
<br/>
To examine the new dimensions of terrorism, a conference was organized in Singapore in late March 2002 that brought together a number of leading experts from a wide range of backgrounds from America, Europe and Asia, and the key findings are presented in this volume under the following headings:</div>
</font>
<ul>
<li>
<p align="justify"><font id="text">Anatomy of the new terrorism</font></p>
</li>
<li>
<p align="justify"><font id="text">Terrorist trends and patterns in the Asia-Pacific region</font></p>
</li>
<li>
<p align="justify"><font id="text">Religion and terrorism: Southeast Asian perspectives</font></p>
</li>
<li>
<p align="justify"><font id="text">Formulating counter-strategies   </font></p>
</li>
</ul>
<font id="text">
<div style="" align=""> <span style="font-weight: bold;"> <b> About the Author: </b> </span> <br/>
Both Andrew Tan and Kumar Ramakrishna are Assistant Professors at the Institute of Defence and Strategic Studies, Nanyang Technological University, Singapore.<br/>
Andrew Tan received his M.Phil from Cambridge and PhD from the University of Sydney. His research interests are conflict (inter-state tensions, insurgencies, terrorism and force modernization) in Southeast Asia, and security issues in Asia.<br/>
Kumar Ramakrishna obtained his PhD in History from the University of London in 1999. He teaches and writes on the history of strategic thought as well as the war on terror.</div>
</font>
<td width="18.666662" style="valign: top; background-color: white ; " rowspan="1" colspan="1"><br/>
</td>
<tr valign="top">
<td width="570.666524" style="valign: top; background-color: white ; " rowspan="1" colspan="1"><br/>
</td>
<td width="18.666662" style="valign: top; background-color: white ; " rowspan="1" colspan="1"><br/>
</td>
</tr>
</div>
</pre>

=== Oxford University Press (USA) [http://www.us.oup.com/us/?view=usa homepage] ===
<pre>
<div class="isbnSummaryDetails">
<h2> <a href="/us/catalog/general/subject/HistoryAmerican/ColonialRevolutionary/?view=usa&ci=0195162471">The Glorious Cause</a> </h2>
<div class="subTitle"> The American Revolution, 1763-1789 </div>
<div class="edition"> Revised and Expanded Edition </div>
<div class="byline"> Robert Middlekauff </div>
<span class="isbnNumber">0195162471</span>, <span class="format">hardback</span>, <span class="publicationDate"> Feb 2005 </span> <span class="price"> $37.50 </span> <span class="description"> The classic history of the American Revolution--now in an updated and expanded twentieth anniversary edition </span>
<div class="related">
<h3>More </h3>

<a href="/us/catalog/general/subject/HistoryAmerican/?view=usa&sf=all">History, American</a> > <a href="/us/catalog/general/subject/HistoryAmerican/ColonialRevolutionary/?view=usa&sf=all">Colonial & Revolutionary</a> </div>
</div>

</div>
</pre>

=== Oxford University Press (USA) [http://www.us.oup.com/us/catalog/general/subject/HistoryAmerican/ColonialRevolutionary/?view=usa&ci=0195162471#Product_Details Product page]===
<pre>
<div class="isbnProperties isbnSummary">
<div class="isbnSummaryHeading">
<h1>The Glorious Cause</h1>
<div class="subTitle"> The American Revolution, 1763-1789 </div>
<div class="edition"> Revised and Expanded Edition </div>
<div class="byline"> Robert Middlekauff </div>
</div>

<div class="cover"> <span class="bookShot"><a href="#"><img src="/images/covers/0195162471.jpg"
width="63" alt="bookshot" /> </a></span> <span class="addToCart"><a href="http://www.us.oup.com/us/cart/cart.jsp?op=a&i=0195162471&c=85&q=1&r=http%3A%2F%2Fwww.us.oup.com%2Fus%2Fcatalog%2Fgeneral%2Fsubject%2FHistoryAmerican%2FColonialRevolutionary%2F%3Fview%3Dusa%26ci%3D0195162471">Add to Cart</a></span> </div>

<div class="isbnSummaryDetails"> <span class="isbnNumber">0195162471</span>, <span class="format">hardback</span>, <span class="pages"> 760 pages </span>
<div id="generalinfo"> <span class="publicationDate">Feb 2005, </span> <span class="availability"> In Stock </span> </div>
<div class="cost">
<h2>Price:</h2>
$37.50 <span class="discountCode">(02)</span> </div>
<div class="shipping"> <a href="/us/assets/shippingInfo.jsp?si=1.5&so=3.75&sc=0&isi=5&iso=5&isc=0" target="_blank" onclick="window.open(this.href, this.target, 'height=445,width=445,scrollbars');
return false;">Shipping Details</a> </div>
<div class="moreSeries redArrow">
<h3>See more from the series</h3>
<ul>
<li><a href="/us/catalog/general/series/OxfordHistoryoftheUnitedStates/?view=usa">Oxford History of the United States, Vol. 3</a></li>
</ul>
</div>

</div>

</div>
</div>
</pre>

=== Thomson Gale product detail page ===
<pre>
<div id =" title_main">

<h2>Contemporary Literary Criticism</h2>

<div id =" credits">
<ul>
<li><h2>Excerpts from Criticism of the Works of Today's Novelists, Poets, Playwrights, Short Story Writers, Scriptwriters, & Other Creative Writers</h2>
Volume 1</li>

<li><i>Published by Thomson Gale</i></li>
</ul>
</div>

<div id =" description">
<p>Each print volume in this long-standing series profiles approximately 6-8 novelists, poets, playwrights and other creative writers by providing full-text or excerpted criticism taken from books, magazines, literary reviews, newspapers and scholarly journals. Among those profiled in this volume are:</p>
<ul>
<li>Kingsley Amis
<li>John Dos Passos
<li>Hermann Hesse
<li>Ezra Pound
</ul>
</div>

<div id =" detail">
<ul>
<li>Published/Released:<strong> March 1973</strong></li>
<li>ISBN: <strong>0-8103-0100-8</strong></li>
<li>Product number: <strong>001415</strong></li>
<li>Page count: <strong>485 pp./vol.</strong></li>
<li>Shipping Weight: <strong>5.00 lbs (2.27 kgs)</strong></li>
</ul>
</div> 

<div id =" price">
<P>Price: US $205.00</p>
</div>

</div>
</div>
</pre>

== Breakdown of Citation Elements ==

Using the above examples, various parts of the citations (titles, authors, etc.) can be grouped together for comparision:

=== Book titles: ===
<pre>
<span id="title" class="producttitle">The 1920's</span>
(ABC-CLIO product detail page)

<div class="title"> <a href="...">The Greenwood Encyclopedia of World Folklore and Folklife</a> </div>
(Greenwood Press homepage)

<span id="lblTitle" class="book_headline block">The Greenwood Encyclopedia of World Folklore and Folklife</span>
(Greenwood Press product detail page)

<td width="35%"><font id="title_catalogue_title_font">Title</font></td>
<td width="65%"><font id="text">The New Terrorism: Anatomy, Trends and Counter-strategies</font></td>
(Marshall Cavendish product detail page)

<h2> <a href="...">The Glorious Cause</a> </h2>
(Oxford Univ. Press, homepage)

<h1>The Glorious Cause</h1>
(OUP, product detail page)

<h2>Contemporary Literary Criticism</h2>
(Thomson Gale, product detail page)

<span id="ctlBookDetailHeader_lblTitle" class="ProdTitle">Talk and Interaction in Social Research Methods</span> (SAGE Publications)
</pre>
Also, many examples where books presented in table format with Title as cell header, or presented "Title: "

=== Book Series Name: ===
<pre>
<span id="serieslbl" class="productsubtitle"><a href="...">Teaching With Documents Series</a></span>
(ABC-CLIO)
</pre>

=== Sub-title: ===
<pre>
<span id="subtitle" class="productsubtitle"></span>
(ABC-CLIO)

<div class="sub_title">[Four Volumes]</div>
(Greenwood, homepage)

<span id="lblSubTitle" class="book_subline">[Four Volumes]</span>
(Greenwood, product page)

<div class="subTitle"> The American Revolution, 1763-1789 </div>
(OUP)
</pre>

=== Author: ===
<pre>
<span id="credit" class="productauthor"></span>
(ABC-CLIO)

<div class="author">William M. Clements</div>
(Greenwood)

<td width="35%"><font id="title_catalogue_title_font">Authors</font></td>
<td width="65%"><font id="text">Andrew Tan & Kumar Ramakrishna (eds)</font></td>
(Marshall Cavendish)

<div class="byline"> Robert Middlekauff </div>
(OUP)
</pre>

=== Publication Date: ===
<pre>
<span id="pubdate" class="productdetailbody">11/2001</span>
(ABC-CLIO -- see table structure)

<div id="pnlPubDate"> <span class="book_options">Publication Date:</span> <span id="lblPubDate">12/30/2005</span> </div>
(Greenwood, detail page)

<span class="publicationDate"> Feb 2005 </span>
(OUP)

<li>Published/Released:<strong> March 1973</strong></li>
(Thomson Gale)
</pre>

=== Volumes: ===
<pre>
<td width="110" class="productdetailhead"><span id="volumeslabel" class="productdetailhead">Volumes</span></td>
<td width="180" class="productdetailbody"><span id="volumes" class="productdetailbody">1</span></td>
(ABC-CLIO)
</pre>

=== ISBN: ===
<pre>
<td class="productdetailhead" width="88"><span id="ISBNLabel">ISBN</span></td>
<td class="productdetailbody">1-57607-785-3</td>
(ABC-CLIO)

<div class="isbn">0-313-32847-1</div>
(Greenwood, homepage)

<div id="pnlIsbn"> <span class="book_options">ISBN:</span> <span id="lblIsbn">0-313-32847-1</span> </div>
(Greenwood, product page)

<td width="35%"><font id="title_catalogue_title_font">ISBN Number</font></td>
<td width="65%"><font id="text">9812102108</font></td>
(Marshall Cavendish)

<span class="isbnNumber">0195162471</span>
(OUP)

<li>ISBN: <strong>0-8103-0100-8</strong></li>
(Thomson Gale)
</pre>

=== Book Edition: ===
<pre>
<div class="edition"> Revised and Expanded Edition </div>
(OUP)
</pre>
Added by [[User:Tim White|Tim]]

== RFC vCard Example ==
<pre><nowiki>
9. References

[ISO 8601] ISO 8601:1988 - Data elements and interchange formats -
Information interchange - Representation of dates and
times - The International Organization for
Standardization, June, 1988.

[ISO 8601 TC] ISO 8601, Technical Corrigendum 1 - Data elements and
interchange formats - Information interchange -
Representation of dates and times - The International
Organization for Standardization, May, 1991.

[ISO 9070] ISO 9070, Information Processing - SGML support
facilities - Registration Procedures for Public Text
Owner Identifiers, April, 1991.

[CCITT E.163] Recommendation E.163 - Numbering Plan for The
International Telephone Service, CCITT Blue Book,
Fascicle II.2, pp. 128-134, November, 1988.

[CCITT X.121] Recommendation X.121 - International Numbering Plan for
Public Data Networks, CCITT Blue Book, Fascicle VIII.3,
pp. 317-332, November, 1988.

[CCITT X.520] Recommendation X.520 - The Directory - Selected
Attribute Types, November 1988.

[CCITT X.521] Recommendation X.521 - The Directory - Selected Object
Classes, November 1988.

[MIME-DIR] Howes, T., Smith, M., and F. Dawson, "A MIME Content-
Type for Directory Information", RFC 2425, September
1998.

[RFC 1738] Berners-Lee, T., Masinter, L., and M. McCahill,
"Uniform Resource Locators (URL)", RFC 1738, December
1994.

[RFC 1766] Alvestrand, H., "Tags for the Identification of
Languages", RFC 1766, March 1995.

[RFC 1872] Levinson, E., "The MIME Multipart/Related Content-
type", RFC 1872, December 1995.

[RFC 2045] Freed, N., and N. Borenstein, "Multipurpose Internet
Mail Extensions (MIME) - Part One: Format of Internet
Message Bodies", RFC 2045, November 1996.

[RFC 2046] Freed, N., and N. Borenstein, "Multipurpose Internet
Mail Extensions (MIME) - Part Two: Media Types", RFC
2046, November 1996.

[RFC 2047] Moore, K., "Multipurpose Internet Mail Extensions
(MIME) - Part Three: Message Header Extensions for
Non-ASCII Text", RFC 2047, November 1996.

[RFC 2048] Freed, N., Klensin, J., and J. Postel, "Multipurpose
Internet Mail Extensions (MIME) - Part Four:
Registration Procedures", RFC 2048, January 1997.

[RFC 2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.

[RFC 2234] Crocker, D., and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997.

[UNICODE] "The Unicode Standard - Version 2.0", The Unicode
Consortium, July 1996.

[VCARD] Internet Mail Consortium, "vCard - The Electronic
Business Card Version 2.1",
http://www.imc.org/pdi/vcard-21.txt, September 18,
1996.
</nowiki></pre>
[http://www.faqs.org/rfcs/rfc2426.html vCard RFC]

== W3C XHTML Spec Example ==
<pre><nowiki>
<h1><a name="refs" id="refs">E.</a> References</h1>

<p><strong>This appendix is informative.</strong></p>

<dl>
<dt><a name="ref-css2" id="ref-css2"><strong>[CSS2]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/1998/REC-CSS2-19980512">Cascading Style Sheets, level 2 (CSS2) Specification</a></cite>", B. Bos, H. W. Lie, C. Lilley, I. Jacobs, 12 May 1998.<br />
<a href="http://www.w3.org/TR/REC-CSS2">Latest version</a> available at: http://www.w3.org/TR/REC-CSS2</dd>

<dt><a name="ref-dom" id="ref-dom"><strong>[DOM]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001">Document Object Model (DOM) Level 1 Specification</a></cite>", Lauren Wood <em lang="lt" xml:lang="lt">et al.</em>, 1 October
1998.<br />
<a href="http://www.w3.org/TR/REC-DOM-Level-1">Latest version</a> available at: http://www.w3.org/TR/REC-DOM-Level-1</dd>

<dt><a name="ref-dom2" id="ref-dom2"><strong>[DOM2]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113">Document Object Model (DOM) Level 2 Core Specification</a></cite>", A. Le Hors, <em lang="lt" xml:lang="lt">et
al.</em>, 13 November 2000.<br />
<a href="http://www.w3.org/TR/DOM-Level-2-Core">Latest version</a> available at: http://www.w3.org/TR/DOM-Level-2-Core</dd>

<dt><a name="ref-html4" id="ref-html4"><strong>[HTML]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/1999/REC-html401-19991224">HTML 4.01 Specification</a></cite>", D. Raggett, A. Le Hors, I. Jacobs, 24 December 1999.<br />
<a href="http://www.w3.org/TR/html401">Latest version</a> available at: http://www.w3.org/TR/html401</dd>

<dt><a name="ref-posix.1" id="ref-posix.1"><strong>[POSIX.1]</strong></a></dt>

<dd>"<cite>ISO/IEC 9945-1:1990 Information Technology - Portable Operating System Interface (POSIX) - Part 1: System Application Program Interface (API) [C Language]</cite>", Institute of Electrical
and Electronics Engineers, Inc, 1990.</dd>

<dt><a id="ref-rfc2045" name="ref-rfc2045"><strong>[RFC2045]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2045.txt">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a></cite>", N. Freed and N. Borenstein, November
1996. Note that this RFC obsoletes RFC1521, RFC1522, and RFC1590.</dd>

<dt><a name="ref-rfc2046" id="ref-rfc2046"><strong>[RFC2046]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2046.txt">RFC2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a></cite>", N. Freed and N. Borenstein, November 1996.<br />
Available at <a href="http://www.ietf.org/rfc/rfc2046.txt">http://www.ietf.org/rfc/rfc2046.txt</a>. Note that this RFC obsoletes RFC1521, RFC1522, and RFC1590.</dd>

<dt><a name="ref-rfc2119" id="ref-rfc2119"><strong>[RFC2119]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2119.txt">RFC2119: Key words for use in RFCs to Indicate Requirement Levels</a></cite>", S. Bradner, March 1997.<br />
Available at: http://www.ietf.org/rfc/rfc2119.txt</dd>

<dt><a name="ref-rfc2376" id="ref-rfc2376"><strong>[RFC2376]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2376.txt">RFC2376: XML Media Types</a></cite>", E. Whitehead, M. Murata, July 1998.<br />
This document is obsoleted by [<a href="#ref-rfc3023">RFC3023</a>].<br />
Available at: http://www.ietf.org/rfc/rfc2376.txt</dd>

<dt><a name="ref-rfc2396" id="ref-rfc2396"><strong>[RFC2396]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2396.txt">RFC2396: Uniform Resource Identifiers (URI): Generic Syntax</a></cite>", T. Berners-Lee, R. Fielding, L. Masinter, August 1998.<br />
This document updates RFC1738 and RFC1808.<br />
Available at: http://www.ietf.org/rfc/rfc2396.txt</dd>

<dt><a name="ref-rfc2854" id="ref-rfc2854"><strong>[RFC2854]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2854.txt">RFC2854: The text/html Media Type</a></cite>", D. Conolly, L. Masinter, June 2000.<br />
Available at: http://www.ietf.org/rfc/rfc2854.txt</dd>

<dt><a name="ref-rfc3023" id="ref-rfc3023"><strong>[RFC3023]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc3023.txt">RFC3023: XML Media Types</a></cite>", M. Murata, S. St.Laurent, D. Kohn, January 2001.<br />
This document obsoletes [<a href="#ref-rfc2376">RFC2376</a>].<br />
Available at: http://www.ietf.org/rfc/rfc3023.txt</dd>

<dt><a id="ref-rfc3066" name="ref-rfc3066"><strong>[RFC3066]</strong></a></dt>

<dd>"<a href="http://www.ietf.org/rfc/rfc3066.txt">Tags for the Identification of Languages</a>", H. Alvestrand, January 2001.<br />
Available at: http://www.ietf.org/rfc/rfc3066.txt</dd>

<dt><a id="ref-rfc3236" name="ref-rfc3236"><strong>[RFC3236]</strong></a></dt>

<dd>"<a href="http://www.ietf.org/rfc/rfc3236.txt">The 'application/xhtml+xml' Media Type</a>", M. Baker, P. Stark, January 2002.<br />
Available at: http://www.ietf.org/rfc/rfc3236.txt</dd>

<dt><a id="ref-xhtml-mathml" name="ref-xhtml-mathml"><strong>[XHTML+MathML]</strong></a></dt>

<dd><cite>"<a href="http://www.w3.org/TR/MathML2/dtd/xhtml-math11-f.dtd">XHTML plus Math 1.1 <abbr title="Document Type Definition">DTD</abbr></a></cite>", "A.2 MathML as a DTD Module", Mathematical
Markup Language (MathML) Version 2.0. Available at: http://www.w3.org/TR/MathML2/dtd/xhtml-math11-f.dtd</dd>

<dt><a id="ref-xhtmlmime" name="ref-xhtmlmime"><strong>[XHTMLMIME]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/2002/NOTE-xhtml-media-types-20020801">XHTML Media Types</a></cite>", Masayasu Ishikawa, 1 August 2002.<br />
<a href="http://www.w3.org/TR/xhtml-media-types">Latest version</a> available at: http://www.w3.org/TR/xhtml-media-types</dd>

<dt><a id="ref-xhtmlmod" name="ref-xhtmlmod"><strong>[XHTMLMOD]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410">Modularization of XHTML</a></cite>", M. Altheim et al., 10 April 2001.<br />
<a href="http://www.w3.org/TR/xhtml-modularization">Latest version</a> available at: http://www.w3.org/TR/xhtml-modularization</dd>

<dt><a name="ref-xml" id="ref-xml"><strong>[XML]</strong></a></dt>

<dd>"<a href="http://www.w3.org/TR/2000/REC-xml-20001006">Extensible Markup Language (XML) 1.0 Specification (Second Edition)</a>", T. Bray, J. Paoli, C. M. Sperberg-McQueen, E. Maler, 6 October
2000.<br />
<a href="http://www.w3.org/TR/REC-xml">Latest version</a> available at: http://www.w3.org/TR/REC-xml</dd>

<dt><a name="ref-xmlns" id="ref-xmlns"><strong>[XMLNS]</strong></a></dt>

<dd>"<a href="http://www.w3.org/TR/1999/REC-xml-names-19990114">Namespaces in XML</a>", T. Bray, D. Hollander, A. Layman, 14 January 1999.<br />
XML namespaces provide a simple method for qualifying names used in XML documents by associating them with namespaces identified by URI.<br />
<a href="http://www.w3.org/TR/REC-xml-names">Latest version</a> available at: http://www.w3.org/TR/REC-xml-names</dd>

<dt><a name="ref-xmlc14n" id="ref-xmlc14n"><strong>[XMLC14N]</strong></a></dt>

<dd>"<a href="http://www.w3.org/TR/2001/REC-xml-c14n-20010315">Canonical XML Version 1.0</a>", J. Boyer, 15 March 2001.<br />
This document describes a method for generating a physical representation, the canonical form, of an XML document.<br />
<a href="http://www.w3.org/TR/xml-c14n">Latest version</a> available at: http://www.w3.org/TR/xml-c14n</dd>
</dl>
</nowiki></pre>
[http://www.w3.org/TR/xhtml1/#refs XHTML1.0 Spec references]

== CiteProc XHTML Output ==

The XHTML output for CiteProc[http://xbiblio.sourceforge.net/citeproc.html] wasn't designed per se as a microformat, but is probably not a bad place to start. It is desgined to handle a wide range of content. Here is the APA output:

<pre><nowiki>
<div id="bibliography">

<h3>References</h3>

<p id="Brenner2000a" class="bibref">
<span class="creator">Brenner, N.</span>
<span class="date"> (<span class="year">2000</span>) </span>
<span class="title">The Urban Question as a Scale Question: Reflections
on Henri Lefebre, Urban Theory and the Politics of Scale, </span>
<span class="container">
<span class="title" style="font-style: italic">International Journal of
Urban and Regional Research, </span>
<span class="volume">24</span>
<span class="issue">(2)</span>
<span class="locator">, pp. 361–78</span>
</span>.
</p>

<p id="NW2000-0207" class="bibref">
<span class="creator">Newsweek</span>
<span class="date">
(<span class="year">2000a</span>
<span class="month">, February</span>
<span class="day"> 7</span>)
</span>
<span class="title">The Grandmas Pay a Visit, </span>
<span class="container">
<span class="volume">135</span>
<span class="issue">(6)</span>
<span class="locator">, pp. 45</span>
</span>.
</p>

<p id="Veer1996a" class="bibref">
<span class="creator">van der Veer, P.</span>
<span class="date"><span class="year"> (1996) </span></span>
<span class="title">Riots and Rituals: The Construction of Violence
and Public Space in Hindu Nationalism</span>
<span class="container">, In Brass, P.<span class="role"> (Ed.)</span>.
<span class="title" style="font-style: italic">Riots and Pogroms.</span>
<span class="origin"><span class="place">New York</span>
<span class="publisher">: NYU Press</span></span>
<span class="locator">, pp. 154–76</span>
</span>.
</p>
</div>
</nowiki></pre>

== ACM Digital Library Search Result Examples ==

The [http://www.acm.org/dl/ ACM Digital Library] is a heavily used computer science literature database.

First, the markup for one entry from the table of contents page for the ACM TACO (Transactions on Architecture and Code Optimization) journal:

<pre>
<nowiki>
<td align="left" class="small-text">
<a href="citation.cfm?id=1113841.1113842&coll=portal&dl=ACM&idx=1113841&part=periodical&WantType=periodical&title=ACM%20Transactions%20on%20Architecture%20and%20Code%20Optimization%20%28TACO%29&CFID=68451946&CFTOKEN=20517650"class="medium-text" target="_self">
<strong>Improving WCET by applying a WC code-positioning optimization </strong>
</a>
<br>
Wankang Zhao, David Whalley, Christopher Healy, Frank Mueller
<br>
<small> Pages: 335 - 365</small>
<br>Full text available: <A HREF="ft_gateway.cfm?id=1113842&type=pdf&coll=portal&dl=ACM&CFID=68451946&CFTOKEN=20517650" target="_blank"><img src="images/pdf_logo.gif" width="16" height="16" hspace="1" alt="pdf format" border="0" align="texttop">Pdf</A>(510 KB)

<div class="smaller-text"><table border="0" cellpadding="0" cellpadding="0"><tr valign="top"><td class="smaller-text" nowrap>Additional Information:</td>
<td class="smaller-text"><img src="img/doc_blank.gif" width="1" height="16" alt="" border="0" align="texttop">
<A HREF="citation.cfm?id=1113842&jmp=cit&coll=portal&dl=ACM&CFID=68451946&CFTOKEN=20517650#CIT" target="_self">full citation</a>,
<A HREF="citation.cfm?id=1113842&jmp=abstract&coll=portal&dl=ACM&CFID=68451946&CFTOKEN=20517650#abstract" target="_self">abstract</A>,
<A HREF="citation.cfm?id=1113842&jmp=references&coll=portal&dl=ACM&CFID=68451946&CFTOKEN=20517650#references" target="_self"> references</A>,
<A HREF="citation.cfm?id=1113842&jmp=indexterms&coll=portal&dl=ACM&CFID=68451946&CFTOKEN=20517650#indexterms" target="_self"> index terms</A></td></tr></table></div></td><td> </td></tr><tr><td> </td>
</nowiki>
</pre>

The markup for the 'full citation' page is similar, with a little more information about the authors.

Here's the markup from the 'ACM Ref' link, which apparently is how they suggest you format it:
<pre>
<nowiki>
Zhao, W., Whalley, D., Healy, C., and Mueller, F. 2005.
Improving WCET by applying a WC code-positioning optimization.
<i>ACM Trans. Archit. Code Optim.</i> 2, 4 (Dec. 2005), 335-365.
DOI= http://doi.acm.org/10.1145/1113841.1113842
</nowiki>
</pre>

== IEEE IEEExplore Search Results Markup ==

<pre><nowiki>
<td width="96%" class="bodyCopyBlackLargeSpaced" valign="middle">
<strong>On the parallel execution time of tiled loops</strong><br>
Hogstedt, K.; Carter, L.; Ferrante, J.<br>
<A href='/xpl/RecentIssue.jsp?punumber=71'>Parallel and Distributed Systems, IEEE Transactions on</A><br>
Volume: 14

 Issue: 3
 March 2003 <br />
Page(s): 307- 321<br>
Digital Object Identifier 10.1109/TPDS.2003.1189587<br>

<div id="menu0" style="display:block"><strong>Summary: </strong> Many
computationally-intensive programs, such as those for differential equations, spatial
interpolation, and dynamic programming, spend a large portion of their execution time in
multiply-nested loops that have a regular stencil of data dependences.....</div>
</td>

</nowiki>
</pre>

== CiteSeer database search results ==

The [http://citeseer.ist.psu.edu CiteSeer] database has been another heavily used Computer Science online resource, and it has minimal markup:

Here's what you see on the main page for a given paper - this information is duplicated everywhere on the page, but this is where it's formatted most like an academic citation:
<pre><nowiki>
<font size=-1>Yoshio Kataoka, Michael D. Ernst, William G. Griswold, and David Notkin.
Automated support for program refactoring using invariants. In ICSM, pages 736-- 743,
November 2001. http://citeseer.ist.psu.edu/kataoka01automated.html  
<a href="http://citeseer.ist.psu.edu/check/1791139">More</a></font><br>

</nowiki>
</pre>

Clicking on the 'More' link in the above text gets you a page with a listing of all the ways they found it written out as a citation in other papers. This is an example of how they mark up each of those entries:

<pre><nowiki>
<br>
Yoshio Kataoka, Michael D. Ernst, William G. Griswold, and David Notkin.
<i>Automated support for program refactoring using invariants</i>.
In ICSM, pages 736-- 743, November 2001.<br>
<br>
</nowiki>
</pre>

== CiteULike.org citation listing ==

[http://www.citeulike.org/ CiteULike] is a shared reference database site that allows organization using tags and ratings. The site imports from many unstructured web resources using mostly screen-scraping plugins (I think --Mike)

Here is an example of the markup for one article on the main page:
<pre><nowiki>
<tr><td colspan="2"><ul><li>
<a class="title" href="/user/jrw/article/505272">Geometric phases in adiabatic open quantum systems</a>
<div class="vague"></div>
<div class="vague">by
<a class="author" href="/user/jrw/author/Sarandy">Sarandy</a> MS, <a class="author" href="/user/jrw/author/Lidar">Lidar</a> DA</div>
<div class="vague">
posted to <a class="tag" rel="tag" href="/user/jrw/tag/geometry">geometry</a> <a class="tag" rel="tag" href="/user/jrw/tag/physics">physics</a> <a class="tag" rel="tag" href="/user/jrw/tag/quantum">quantum</a> <a class="tag" rel="tag" href="/user/jrw/tag/quantum-information">quantum-information</a>
by <a href="/user/jrw">jrw</a>
as <img alt="x"src="http://static.citeulike.org/img/star2.png" />
on 2006-02-14 18:36:22
</div>
</li>
</ul>
</td>
</tr>
</nowiki></pre>

And here is markup from the detail page for another publication:

<pre><nowiki>
<div class="content">

<table border="0"><tr><td width="100%"><h1>T-Coffee: A novel method for fast and accurate multiple sequence alignment.</h1></td><td>
</td></tr></table>
<div class="vague"><i>J Mol Biol</i>, Vol. 302, No. 1. (8 September 2000), pp. 205-217.</div>
<br>

<h2>Authors</h2>

<ul><li><span class="black">
<a class="author" href="/user/ffranca/author/Notredame">Notredame</a> C</span>,
<span class="black">
<a class="author" href="/user/ffranca/author/Higgins">Higgins</a> DG</span>,
<span class="black">
<a class="author" href="/user/ffranca/author/Heringa">Heringa</a> J</span>
</li></ul>

<ul>
</ul>

<table border="0" width="100%">
<tr>
<td valign="top">
<h2>Online Article
<span class="Z3988" title="ctx_ver=Z39.88-2004&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rfr_id=info:sid/citeulike.org/citeulike&rft.aufirst=&rft_id=info:doi/10%2e1006%2fjmbi%2e2000%2e4042&rft.spage=205&rft.issue=1&rft.aulast=Notredame&rft.title=J+Mol+Biol&rft.epage=217&rft.issn=0022%2d2836&rft.volume=302&rft.auinit=C&rft.atitle=T%2dCoffee%3a+A+novel+method+for+fast+and+accurate+multiple+sequence+alignment%2e&date=2000-9-8&rft.genre=article&genre=article"></span>

</h2>
</td>
</div>
</td>
</tr>
<tr>
<td valign="top">
<ul>

<li><span class="black">DOI:</span> <a accesskey="1" href="http://dx.doi.org/10.1006/jmbi.2000.4042" rel="nofollow">View article online</a></li>
<li><span class="black">Pubmed:</span> <a accesskey="2" href="http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?cmd=Retrieve&db=pubmed&dopt=Abstract&list_uids=10964570" rel="nofollow">View article online</a></li>

<li><span class="black">Hubmed:</span> <a accesskey="3" href="http://www.hubmed.org/display.cgi?uids=10964570" rel="nofollow">View article online</a></li>

</ul>

</td>
</tr>
</table>
</nowiki>
</pre>

== Amazon.com citation info ==

This is from a detail page on Amazon.com for a book.

<pre><nowiki>
<a name='citing' ></a><b>
This book cites 10
books:
</b><br /><ul style="margin-bottom: 20px;"><li>

<a href="http://www.amazon.com/exec/obidos/tg/detail/-/1555424236/ref=sid_dp_dp/002-6751255-9290456?%5Fencoding=UTF8&v=glance" >The New Faculty Member: Supporting and Fostering Professional Development (Jossey-Bass Higher and Adult Education Series)</a>

by Robert Boice
on <a href="/gp/reader/0780311361/ref=sib_ab_dp_pg/002-6751255-9290456?%5Fencoding=UTF8&p=S04X&checkSum=vptuDOjULIOadVNe9UFX36fnIKktwxxQOeBmFQupyrA%3D">page 156</a>, and <a href="/gp/reader/0780311361/ref=sib_ab_dp_pg/002-6751255-9290456?%5Fencoding=UTF8&p=S088&checkSum=vptuDOjULINm2bvcL37hZR%2BcnJi%2F9hhUyu1%2FlXWnOM8%3D">page 275</a></li><li>

<a href="http://www.amazon.com/exec/obidos/tg/detail/-/0137947364/ref=sid_dp_dp/002-6751255-9290456?%5Fencoding=UTF8&v=glance" >Science, Technology and Society</a>

by Robert E. McGinn
on <a href="/gp/reader/0780311361/ref=sib_ab_dp_pg/002-6751255-9290456?%5Fencoding=UTF8&p=S023&checkSum=vptuDOjULIMgFwAeeT8gWiDHmklkxfy%2BGug%2BAS7UI2Y%3D">page 54</a></li><li>

</nowiki>
</pre>

== Implied schema ==

Many of the examples have simple citations in <p>, <div>, <td> etc with no further coding; i.e. <td>Book Title. Author. Publisher, date.</td>

The following lists the most common markup:

=== Book Titles: ===

*id="title"
*class="producttitle"
*class="title"
*id="lblTitle"
*h1
*h2
*<dt></dt>
*<cite></cite>
*<strong></strong>
*<i></i>

=== Book Series: ===

*id="serieslbl"
*class="productsubtitle"

=== Sub-titles: ===

*id="subtitle"
*class="productsubtitle"
*class="sub_title"
*id="lblSubTitle"
*class="book_subline"
*class="subTitle"

=== Author: ===

*id="credit"
*class="productauthor"
*class="author"
*Authors (table cell)
*class="byline"
*class="creator"
*class="role"
*Inside <dd></dd> with other elements
*<li></li>

=== Publication Date: ===

*id="pubdate"
*Publication Date: (table cell)
*id="pnlPubDate"
*Publication Date:
*class="publicationdate"
*Published/Released:
*class="date" w/ class="year", class="month", class="day"
*Inside <dd></dd> with other elements

=== Publisher: ===

*class="publisher"
*class="origin" (publication location)

=== Volumes: ===

*class="volume"

=== Issue Number: ===

*class="issue"

=== Page Numbers: ===

*class="locator" (inclusive page numbers)

=== ISBN: ===

*class="isbn"
*id="pnlIsbn"
*id="lblIsbn"
*class="isbnNumber"

=== Book Edition: ===

*class="edition"
*Inside <dd></dd> with other elements

== Citeproc XHTML output ==

I'm the author of the [http://xbiblio.sourceforge.net/citeproc.html citeproc] project, which includes a micro-format of sorts (though I never thought of it as such) in its XHTML output mode. See [http://xbiblio.sourceforge.net/examples/apa-en.html here] for an example. The difference compared to the bibtex-derived model is that is a) more generic and b) hierachical.

It would be possible, certainly, to do a flat model if for some reason there was a good technical reason not to go hierarchical (though is there?)

'''The burden of proof is on *going* hierarchical, rather than a simpler flat solution. Complexity must be justified, not simplicity.'''

... but then you need to think outside the BibTeX box in any case. Any model of this sort ought to be able to handle legal citations, magazine articles, patents, etc. etc.; not just a narrow range of BibTeX types.

'''Per the microformats [[process]], microformats are designed to support existing practice on the Web, anything else should be omitted from at least the first version.'''

== Styles ==
This does NOT define a format, but instead shows how the format should be displayed. This is something out of the direct scope of this project. CSS styles will handle the look-and-feel of the text, and the author can put it in any order they choose. These links are mentioned for two reasons, one is informative, the other is so we know at least meet the minimum properties that are used in the styles.

* [http://www.liu.edu/cwis/cwp/library/workshop/citmla.htm MLA Style]
* [http://www.bu.edu/library/guides/citation.html Chicago, MLA, and APA styles]
* [http://www.legalbluebook.com/ Blue Book] for legal citations
* [http://www.columbia.edu/cu/cup/cgos/idx_basic.html Columbia University Citation Style] developed for modern internet citations

citation-examples

2006-02-26T20:37:04Z

Tim White:

<h1> Citation Examples </h1>

The following examples are real world examples of citations found on the web. Please add to this list. The idea is that we get a solid sample of examples and see what commonalities there are amonst them and try to build this microformat so that it can meet 80% of typical uses.

See also:
* [[citation]]
* [[citation-formats]]
* [[citation-brainstorming]]

__TOC__

== Contributors ==
* ...
* ...
* Tantek Çelik
* [http://michael-mccracken.net/wp/ Michael McCracken]
* Tim White

== Citation Mark Up in the Wild ==
Mark up examples from reference publisher's websites (online catalogs), including ABC-CLIO, Greenwood Press, Marshall Cavendish, Oxford University Press (USA) and Thomson Gale. Examples are broken down and organized by element.

(For a cleaner version, see [http://www.tjameswhite.com/citation-examples.htm])

=== ABC-CLIO Product [http://www.abc-clio.com/products/overview.aspx?productid=109327 detail page] ===
<pre>
<table border="0" cellpadding="0" cellspacing="0" width="430">
<tr>
<td width="101" valign="top" align="left"></td>
<td width="102" valign="top" align="left"></td>
<td width="101" valign="top" align="left"></td>
<td width="125" valign="top" align="center"></td>
</tr>
<tr>
<td width="430" colspan="4" class="productsubtitle"><span id="serieslbl" class="productsubtitle"><a href="browseseries.aspx?seriesid=33">Teaching With Documents Series</a></span></td>
</tr>
<tr>
<td width="430" colspan="4" class="producttitle"><span id="title" class="producttitle">The 1920's</span></td>
</tr>
<tr>
<td width="430" colspan="4" class="productsubtitle"><span id="subtitle" class="productsubtitle"></span></td>
</tr>
<tr>
<td width="430" colspan="4" class="productauthor"><span id="credit" class="productauthor"></span></td>
</tr>
<tr>
<td width="430" colspan="4" height="12"><img border="0" src="../images/blank-white.gif" width="1" height="12" alt=""/></td>
</tr>
<tr>
<td width="130" align="left"><img id="productImage" src="../images/dbimages/1011\101103.GIF" alt="" style="border-width:0px;width:115px;" /></td>
<td width="300" valign="top" align="right" colspan="3">
<table border="0" cellpadding="0" cellspacing="0" width="290">
<tr>
<td width="110" class="productdetailhead"><span id="pubdatelabel" class="productdetailhead">Publication Date</span></td>
<td width="180" class="productdetailbody"><span id="pubdate" class="productdetailbody">11/2001</span></td>
</tr>
<tr>
<td width="110" class="productdetailhead"><span id="pageslabel" class="productdetailhead">Pages</span></td>
<td width="180" class="productdetailbody"><span id="pages" class="productdetailbody">132</span></td>
</tr>
<tr>
<td width="110" class="productdetailhead"><span id="volumeslabel" class="productdetailhead">Volumes</span></td>
<td width="180" class="productdetailbody"><span id="volumes" class="productdetailbody">1</span></td>
</tr>
<tr>
<td width="110" class="productdetailhead"><span id="trimlabel" class="productdetailhead">Size</span></td>
<td width="180" class="productdetailbody"><span id="trimsize" class="productdetailbody">8.5x11</span></td>
</tr>
</table>


<table id="PriceTable" cellspacing="0" cellpadding="0" width="290" border="0">
<tr>
<td class="productdetailhead" width="290" height="15" colspan="4"><img src="../images/academic/blank-blue.gif" id="PriceLine" width="290" height="1" border="0" /></td>
</tr>
<tr>
<td class="productdetailhead" width="54">Format</td>
<td class="productdetailhead" width="68">Price</td>
<td class="productdetailhead" width="88"><span id="ISBNLabel">ISBN</span></td>
<td class="productdetailhead" width="80"> </td>
</tr>
<tr>
<td class="productdetailhead"><b>Print</b></td>
<td class="productdetailbody">$39.00</td>
<td class="productdetailbody">1-57607-785-3</td>
<td class="productdetailhead"> </td>
</tr>
</table>

</td>
</tr>
</table>
</div>
</pre>

=== Greenwood Press [http://www.greenwood.com/ home page] featured book ===
<pre>
<div class="title"> <a href="/books/BookDetail.asp?sku=GR2847">The Greenwood Encyclopedia of World Folklore and Folklife</a> </div>
<div class="img_box"> <a href="/books/BookDetail.asp?sku=GR2847"> <img src="/_net.templates/showImage.aspx?imgName=0313328471.jpg&s=140" alt="The Greenwood Encyclopedia of World Folklore and Folklife" border="0" /></a> </div>
<div class="sub_title">Four Volumes</div>
<div class="author">William M. Clements</div>
<div class="isbn">0-313-32847-1</div>
<div class="price">$449.95 <span class="pipe">|</span> £255.00</div>

<div class="bookDescription"> China . . . Malta . . . Madagascar . . . Wales . . . and Texas: these are among the many exotic, distant lands that capture our minds and imaginations. In an era of increasing globalization, students, general readers, and business professionals need to know about... <a href="/books/BookDetail.asp?sku=GR2847">Read more</a> </div>
</div>
</pre>

=== Greenwood Press [http://www.greenwood.com/catalog/GR2847.aspx Product detail page] ===
<pre>
<div id="pnlContent" class="pnlContent">
<div id="pnlFlyerBox" class="flyerBox"> <a id="hlFlyer" class="flyerLink" href="/books/printFlyer.aspx?sku=GR2847" target="_blank">Print book flyer</a> <br />
<a id="hlFlyerInternational" class="international_flyer" href="/books/printFlyer.aspx?sku=GR2847&location=international" target="_blank">(International version)</a> </div>
<span id="lblTitle" class="book_headline block">The Greenwood Encyclopedia of World Folklore and Folklife</span> <span id="lblSubTitle" class="book_subline">Four Volumes</span>
<div id="pnlBookDetails" class="detailsBox">
<div id="pnlImgBox" class="imgBox"> <img src="/_net.templates/showImage.aspx?imgName=0313328471.jpg&s=135" alt="" border="0" /> </div>
<a id="hlAddToCart" title="Add this item to your shopping cart" href="/shopping_cart/?sku=GR2847"><img title="Add this item to your shopping cart" src="/_net.templates/roundedButton.aspx?ButtonText=Add to Cart" alt="" border="0" /></a> <a id="hlAddToWishList" title="Save this item to your wish list" href="/wish_list/?sku=GR2847"><img title="Save this item to your wish list" src="/_net.templates/roundedButton.aspx?ButtonText=Add to Wish List" alt="" border="0" /></a> <a id="hlSharePage" title="Email this page to a friend" href="/books/sendform.asp?sku=GR2847" target="_blank"><img title="Email this page to a friend" src="/_net.templates/roundedButton.aspx?ButtonText=Email" alt="" border="0" /></a> <a id="hlPrintPage" title="Version of this page optimized for printing" href="/catalog/GR2847.aspx?print=1" target="_blank"><img title="Version of this page optimized for printing" src="/_net.templates/roundedButton.aspx?ButtonText=Print" alt="" border="0" /></a> <a id="hlWorldCat" href="http://worldcatlibraries.org/wcpa/isbn/0313328471" style="FLOAT: right"><img src="/images/world_catalog.gif" alt="" border="0" /></a>
<div class="authors"><span><a href="/catalog/author/C/229.aspx">William M. Clements</a> (ed.)</span></div>
<span id="lblAuthorsNote" class="block"></span>
<div><span class="book_options">Book Code:</span> <span id="lblBookCode">GR2847</span></div>
<div id="pnlIsbn"> <span class="book_options">ISBN:</span> <span id="lblIsbn">0-313-32847-1</span> </div>
<div id="pnlPageColation"> 1972 pages, maps; photos </div>
<span id="lblImprint" class="block">Greenwood Press</span>
<div id="pnlPubDate"> <span class="book_options">Publication Date:</span> <span id="lblPubDate">12/30/2005</span> </div>
<div id="pnlListPrice"> <span class="book_options">List Price:</span> <span id="lblListPrice">$449.95</span> (<a href="/contactus/order_info.asp?SectionID=about&Location=order_info#UKEME" title="Click for international ordering information">UK Sterling Price: £255.00</a>) </div>
<div id="pnlAvailability"> <span class="book_options">Availability:</span> <span id="lblAvailability">In Stock</span> </div>
<div id="pnlMediaType"> <span class="book_options">Media Type:</span> <span id="lblMediaType">Hardcover</span> </div>
<div class="clearing"></div>
</div>
<div id="pnlBookInformation"> <span class="book_options">Subjects:</span>
<ul class="toc">
<li> <a id="rpCategories__ctl1_hlCategory" href="/catalog/subject/Anthropology.aspx">Anthropology</a> » <a id="rpCategories__ctl1_hlSubCategory" href="/catalog/subject/Anthropology/Folklore.aspx">Folklore</a> </li>
<li> <a id="rpCategories__ctl2_hlCategory" href="/catalog/subject/Anthropology.aspx">Anthropology</a> » <a id="rpCategories__ctl2_hlSubCategory" href="/catalog/subject/Anthropology/Anthropology%2b(General).aspx">Anthropology (General)</a> </li>
<li> <a id="rpCategories__ctl3_hlCategory" href="/catalog/subject/Anthropology.aspx">Anthropology</a> » <a id="rpCategories__ctl3_hlSubCategory" href="/catalog/subject/Anthropology/Cultural%2bAnthropology.aspx">Cultural Anthropology</a> </li>
<li> <a id="rpCategories__ctl4_hlCategory" href="/catalog/subject/History.aspx">History</a> » <a id="rpCategories__ctl4_hlSubCategory" href="/catalog/subject/History/World%2bHistory%2b(General).aspx">World History (General)</a> </li>
</ul>
<div id="pnlDescription"> <span class="book_options">Description:</span> <span id="lblDescription1" class="description block">China . . . Malta . . . Madagascar . . . Wales . . . and Texas: these are among the many exotic, distant lands that capture our minds and imaginations. In an era of increasing globalization, students, general readers, and business professionals need to know about the world and its varied ways. So too, a knowledge of world cultures is fundamental to an understanding of America's ethnically rich society. Folklore isn't just about the long ago and far away. It's about the here and now, and there's no better way to learn about cultural diversity than to study the folklore and folkways of different ethnic groups. <br />
More than just Cinderella and other fairy tales, folklore encompasses the whole realm of traditional beliefs and activities that define a culture. The most comprehensive work of its kind, this massive encyclopedia engagingly and authoritatively surveys folklife and traditions from around the world. Through its vast scope and lengthy entries, it transcends other references on particular national or regional folklores and is the most ambitious undertaking of its type. Organized in four volumes, the encyclopedia provides convenient access to information about folklore generally and to the traditions of particular regions:<br />
Volume 1: Topics and Themes, Africa, Australia and Oceania<br />
Volume 2: Southeast Asia and India, Central and East Asia, Middle East<br />
Volume 3: Europe<br />
Volume 4: North and South America</span> <span id="lblDescription2" class="description block">Along with the expertise of the contributors, of Volume Editor William M. Clements, and of Advisory Editor Thomas A. Green, the encyclopedia draws upon a distinguished board of internationally recognized scholars, including:<br />
<li> Roger D. Abrahams<br />
</li>
<li> Cristina Bacchilega<br />
</li>
<li> Gillian Bennett<br />
</li>
<li> Mary Ellen Brown<br />
</li>
<li> James R. Dow<br />
</li>
<li> Alessandro Falassi<br />
</li>
<li> Barbro Klein<br />
</li>
<li> Peter Knecht<br />
</li>
<li> Natalie Kononenko<br />
</li>
<li> Frances M. Malpezzi<br />
</li>
<li> Margaret Mills<br />
</li>
<li> M. D. Muthukumaraswamy<br />
</li>
<li> Gerald Pocius<br />
</li>
<li> And John S. Ryan.<br />
<br />
<b>Features:</b><br />
</li>
<li> Brings together the knowledge of more than 200 specialists from around the world.<br />
</li>
<li> Provides 39 extended entries on topics central to world folklore.<br />
</li>
<li> Details the folklore and folkways of roughly 170 cultural groups.<br />
</li>
<li> Entries discuss the background, beliefs, oral and theatrical traditions, arts and crafts, and contemporary concerns of each cultural group.<br />
</li>
<li> Each entry cites numerous works for further reading.<br />
</li>
<li> A generous selection of maps and illustrations makes world folklore come to life.<br />
</li>
<li> A list of entries and a cumulative subject index, repeated in each volume, offer convenient access to the vast body of information contained in the encyclopedia.<br />
</li>
<li> A selected, general bibliography directs students and general readers to the most important broad studies of world folklore.<br />
</li>
<li> A glossary defines key terms, theories, and concepts.<br />
<br />
<b>Benefits:</b><br />
</li>
<li> Helps students learn about cultures, customs, and daily life around the world.<br />
</li>
<li> Fosters respect and appreciation for the many ethnic traditions behind contemporary American culture.<br />
</li>
<li> Provides valuable background information for the study of world religions, holidays, and festivals.<br />
</li>
<li> Offers a valuable context for understanding world history, politics, literature, and the arts.<br />
</li>
<li> Invites students to compare and contrast the values and experiences of different cultures.<br />
</li>
<li> Fosters critical reading skills and serves as a model for student research.<br />
<br />
<b>Volume 1: Topics and Themes, Africa, Australia and Oceania</b><br />
Certain themes and topics are central to world foklore. The thematic essays in this volume discuss such matters as:<br />
</li>
<li> Antiquarianism<br />
</li>
<li> Cultural Evolution<br />
</li>
<li> Ethnopoetics<br />
</li>
<li> Gender<br />
</li>
<li> Invented Tradition<br />
</li>
<li> Nativism<br />
</li>
<li> Primitivism<br />
</li>
<li> Public Folklore<br />
</li>
<li> Race<br />
</li>
<li> Trickster<br />
</li>
<li> And many more.<br />
<br />
<b>Volume 2: Southeast Asia and India, Central and East Asia, Middle East</b><br />
Included in this volume are entries on such cultural groups and regions as:<br />
</li>
<li> Bali<br />
</li>
<li> China<br />
</li>
<li> Duna<br />
</li>
<li> Iban<br />
</li>
<li> Kazakh<br />
</li>
<li> Mongol<br />
</li>
<li> Orissa<br />
</li>
<li> Palestine<br />
</li>
<li> Tonga<br />
</li>
<li> Uyghur<br />
</li>
<li> And many others.<br />
<br />
<b>Volume 3: Europe</b><br />
Included in this volume are entries on the folklore of such cultural regions and groups as:<br />
</li>
<li> Ashkenazim<br />
</li>
<li> Basque<br />
</li>
<li> Brittany<br />
</li>
<li> Flanders<br />
</li>
<li> Germany<br />
</li>
<li> Isle of Man<br />
</li>
<li> Roma<br />
</li>
<li> Russia<br />
</li>
<li> Sami<br />
</li>
<li> Ukraine<br />
</li>
<li> And many more.<br />
<br />
<b>Volume 4: North and South America</b><br />
The entries in this volume explore the folk traditions of such regions and groups as:<br />
</li>
<li> Appalachia<br />
</li>
<li> Choctaw<br />
</li>
<li> Haiti<br />
</li>
<li> Island Carib<br />
</li>
<li> Maya<br />
</li>
<li> Quechua<br />
</li>
<li> Seminole<br />
</li>
<li> Western Inuit and Yupik<br />
</li>
<li> Xavante<br />
</li>
<li> Yanomami<br />
</li>
<li> And many more.<br />
<br />
Because folklore is the essence of daily life, this encyclopedia addresses the curriculum needs of high school students and is also an indispensable resource for teachers. In addition, anyone researching folklore in a public library will find this the first place to look for detailed information about cultural traditions around the world.</li>
</span> </div>
<div id="pnlLCCardNumber" class="description"> <span class="book_options">LC Card Number:</span> <span id="lblLCCardNumber">2005019219</span> </div>
<div id="pnlLCCClass" class="description"> <span class="book_options">LCC Class:</span> <span id="lblLCCClass">GR35 </span> </div>
<div id="pnlDeweyClass" class="description"> <span class="book_options">Dewey Class:</span> <span id="lblDeweyClass">398</span> </div>
</div>
</div>
</div>
</pre>

=== Marshall Cavendish [http://www.marshallcavendish.com/marshallcavendish/academic/redirector.xml?url=/marshallcavendish/academic/catalogue/books/regionalism_n_regional_security/9812102108.xml product page] ===
<pre>
<table cellpadding="2" width="100%">
<tr valign="top">
<td><font id="title_catalogue_font"><b>Regionalism & Regional Security</b></font></td>
</tr>
</table>
<font id="text">
<div style="" align="">
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">ISBN Number</font></td>
<td width="65%"><font id="text">9812102108</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Series</font></td>
<td width="65%"><font id="text">null</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Title</font></td>
<td width="65%"><font id="text">The New Terrorism: Anatomy, Trends and Counter-strategies</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Imprint</font></td>
<td width="65%"><font id="text">Eastern Universities Press</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Specifications</font></td>
<td width="65%"><font id="text">152 mm X 227 mm, 368 pp, limp with flaps, 500 gms</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Authors</font></td>
<td width="65%"><font id="text">Andrew Tan & Kumar Ramakrishna (eds)</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Target Audience</font></td>
<td width="65%"><font id="text">University lecturers/researchers, undergraduate students, academicians and those interested in Regional Security Studies.</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Price (SG)</font></td>
<td width="65%"><font id="text">S$ 39.00</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Price (US)</font></td>
<td width="65%"><font id="text">US$ 30.00</font>   <a href="javascript: addToCart()"><img src="/marshallcavendish/components/db_content/MC_AC_redirector/pic/addCart.gif" border="0"/></a></td>
</tr>
</table>
<br/>
<br/>
The terrorist attacks of September 11, 2001 on the World Trade Centre in New York and the Pentagon in Washington represented a true watershed in world history.<br/>
<br/>
The attacks revealed the horrifying nature of the so-called "new terrorism" that has emerged in the post-Cold War era. The new terrorism is defined by four key features:</div>
</font>
<ul>
<li>
<p align="justify"><font id="text">sheer lethality</font></p>
</li>
<li>
<p align="justify"><font id="text">religious dimension</font></p>
</li>
<li>
<p align="justify"><font id="text">networked organizational structure</font></p>
</li>
<li>
<p align="justify"><font id="text">greatly enhanced striking power   </font></p>
</li>
</ul>
<font id="text">
<div style="" align="">As September 11 clearly demonstrated, the new terrorists can leverage on technology to inflict catastrophic damage even on superpowers, let alone other states.<br/>
<br/>
To examine the new dimensions of terrorism, a conference was organized in Singapore in late March 2002 that brought together a number of leading experts from a wide range of backgrounds from America, Europe and Asia, and the key findings are presented in this volume under the following headings:</div>
</font>
<ul>
<li>
<p align="justify"><font id="text">Anatomy of the new terrorism</font></p>
</li>
<li>
<p align="justify"><font id="text">Terrorist trends and patterns in the Asia-Pacific region</font></p>
</li>
<li>
<p align="justify"><font id="text">Religion and terrorism: Southeast Asian perspectives</font></p>
</li>
<li>
<p align="justify"><font id="text">Formulating counter-strategies   </font></p>
</li>
</ul>
<font id="text">
<div style="" align=""> <span style="font-weight: bold;"> <b> About the Author: </b> </span> <br/>
Both Andrew Tan and Kumar Ramakrishna are Assistant Professors at the Institute of Defence and Strategic Studies, Nanyang Technological University, Singapore.<br/>
Andrew Tan received his M.Phil from Cambridge and PhD from the University of Sydney. His research interests are conflict (inter-state tensions, insurgencies, terrorism and force modernization) in Southeast Asia, and security issues in Asia.<br/>
Kumar Ramakrishna obtained his PhD in History from the University of London in 1999. He teaches and writes on the history of strategic thought as well as the war on terror.</div>
</font>
<td width="18.666662" style="valign: top; background-color: white ; " rowspan="1" colspan="1"><br/>
</td>
<tr valign="top">
<td width="570.666524" style="valign: top; background-color: white ; " rowspan="1" colspan="1"><br/>
</td>
<td width="18.666662" style="valign: top; background-color: white ; " rowspan="1" colspan="1"><br/>
</td>
</tr>
</div>
</pre>

=== Oxford University Press (USA) [http://www.us.oup.com/us/?view=usa homepage] ===
<pre>
<div class="isbnSummaryDetails">
<h2> <a href="/us/catalog/general/subject/HistoryAmerican/ColonialRevolutionary/?view=usa&ci=0195162471">The Glorious Cause</a> </h2>
<div class="subTitle"> The American Revolution, 1763-1789 </div>
<div class="edition"> Revised and Expanded Edition </div>
<div class="byline"> Robert Middlekauff </div>
<span class="isbnNumber">0195162471</span>, <span class="format">hardback</span>, <span class="publicationDate"> Feb 2005 </span> <span class="price"> $37.50 </span> <span class="description"> The classic history of the American Revolution--now in an updated and expanded twentieth anniversary edition </span>
<div class="related">
<h3>More </h3>

<a href="/us/catalog/general/subject/HistoryAmerican/?view=usa&sf=all">History, American</a> > <a href="/us/catalog/general/subject/HistoryAmerican/ColonialRevolutionary/?view=usa&sf=all">Colonial & Revolutionary</a> </div>
</div>

</div>
</pre>

=== Oxford University Press (USA) [http://www.us.oup.com/us/catalog/general/subject/HistoryAmerican/ColonialRevolutionary/?view=usa&ci=0195162471#Product_Details Product page]===
<pre>
<div class="isbnProperties isbnSummary">
<div class="isbnSummaryHeading">
<h1>The Glorious Cause</h1>
<div class="subTitle"> The American Revolution, 1763-1789 </div>
<div class="edition"> Revised and Expanded Edition </div>
<div class="byline"> Robert Middlekauff </div>
</div>

<div class="cover"> <span class="bookShot"><a href="#"><img src="/images/covers/0195162471.jpg"
width="63" alt="bookshot" /> </a></span> <span class="addToCart"><a href="http://www.us.oup.com/us/cart/cart.jsp?op=a&i=0195162471&c=85&q=1&r=http%3A%2F%2Fwww.us.oup.com%2Fus%2Fcatalog%2Fgeneral%2Fsubject%2FHistoryAmerican%2FColonialRevolutionary%2F%3Fview%3Dusa%26ci%3D0195162471">Add to Cart</a></span> </div>

<div class="isbnSummaryDetails"> <span class="isbnNumber">0195162471</span>, <span class="format">hardback</span>, <span class="pages"> 760 pages </span>
<div id="generalinfo"> <span class="publicationDate">Feb 2005, </span> <span class="availability"> In Stock </span> </div>
<div class="cost">
<h2>Price:</h2>
$37.50 <span class="discountCode">(02)</span> </div>
<div class="shipping"> <a href="/us/assets/shippingInfo.jsp?si=1.5&so=3.75&sc=0&isi=5&iso=5&isc=0" target="_blank" onclick="window.open(this.href, this.target, 'height=445,width=445,scrollbars');
return false;">Shipping Details</a> </div>
<div class="moreSeries redArrow">
<h3>See more from the series</h3>
<ul>
<li><a href="/us/catalog/general/series/OxfordHistoryoftheUnitedStates/?view=usa">Oxford History of the United States, Vol. 3</a></li>
</ul>
</div>

</div>

</div>
</div>
</pre>

=== Thomson Gale product detail page ===
<pre>
<div id =" title_main">

<h2>Contemporary Literary Criticism</h2>

<div id =" credits">
<ul>
<li><h2>Excerpts from Criticism of the Works of Today's Novelists, Poets, Playwrights, Short Story Writers, Scriptwriters, & Other Creative Writers</h2>
Volume 1</li>

<li><i>Published by Thomson Gale</i></li>
</ul>
</div>

<div id =" description">
<p>Each print volume in this long-standing series profiles approximately 6-8 novelists, poets, playwrights and other creative writers by providing full-text or excerpted criticism taken from books, magazines, literary reviews, newspapers and scholarly journals. Among those profiled in this volume are:</p>
<ul>
<li>Kingsley Amis
<li>John Dos Passos
<li>Hermann Hesse
<li>Ezra Pound
</ul>
</div>

<div id =" detail">
<ul>
<li>Published/Released:<strong> March 1973</strong></li>
<li>ISBN: <strong>0-8103-0100-8</strong></li>
<li>Product number: <strong>001415</strong></li>
<li>Page count: <strong>485 pp./vol.</strong></li>
<li>Shipping Weight: <strong>5.00 lbs (2.27 kgs)</strong></li>
</ul>
</div> 

<div id =" price">
<P>Price: US $205.00</p>
</div>

</div>
</div>
</pre>

== Breakdown of Citation Elements ==

Using the above examples, various parts of the citations (titles, authors, etc.) can be grouped together for comparision:

=== Book titles: ===
<pre>
<span id="title" class="producttitle">The 1920's</span>
(ABC-CLIO product detail page)

<div class="title"> <a href="...">The Greenwood Encyclopedia of World Folklore and Folklife</a> </div>
(Greenwood Press homepage)

<span id="lblTitle" class="book_headline block">The Greenwood Encyclopedia of World Folklore and Folklife</span>
(Greenwood Press product detail page)

<td width="35%"><font id="title_catalogue_title_font">Title</font></td>
<td width="65%"><font id="text">The New Terrorism: Anatomy, Trends and Counter-strategies</font></td>
(Marshall Cavendish product detail page)

<h2> <a href="...">The Glorious Cause</a> </h2>
(Oxford Univ. Press, homepage)

<h1>The Glorious Cause</h1>
(OUP, product detail page)

<h2>Contemporary Literary Criticism</h2>
(Thomson Gale, product detail page)

<span id="ctlBookDetailHeader_lblTitle" class="ProdTitle">Talk and Interaction in Social Research Methods</span> (SAGE Publications)
</pre>
Also, many examples where books presented in table format with Title as cell header, or presented "Title: "

=== Book Series Name: ===
<pre>
<span id="serieslbl" class="productsubtitle"><a href="...">Teaching With Documents Series</a></span>
(ABC-CLIO)
</pre>

=== Sub-title: ===
<pre>
<span id="subtitle" class="productsubtitle"></span>
(ABC-CLIO)

<div class="sub_title">[Four Volumes]</div>
(Greenwood, homepage)

<span id="lblSubTitle" class="book_subline">[Four Volumes]</span>
(Greenwood, product page)

<div class="subTitle"> The American Revolution, 1763-1789 </div>
(OUP)
</pre>

=== Author: ===
<pre>
<span id="credit" class="productauthor"></span>
(ABC-CLIO)

<div class="author">William M. Clements</div>
(Greenwood)

<td width="35%"><font id="title_catalogue_title_font">Authors</font></td>
<td width="65%"><font id="text">Andrew Tan & Kumar Ramakrishna (eds)</font></td>
(Marshall Cavendish)

<div class="byline"> Robert Middlekauff </div>
(OUP)
</pre>

=== Publication Date: ===
<pre>
<span id="pubdate" class="productdetailbody">11/2001</span>
(ABC-CLIO -- see table structure)

<div id="pnlPubDate"> <span class="book_options">Publication Date:</span> <span id="lblPubDate">12/30/2005</span> </div>
(Greenwood, detail page)

<span class="publicationDate"> Feb 2005 </span>
(OUP)

<li>Published/Released:<strong> March 1973</strong></li>
(Thomson Gale)
</pre>

=== Volumes: ===
<pre>
<td width="110" class="productdetailhead"><span id="volumeslabel" class="productdetailhead">Volumes</span></td>
<td width="180" class="productdetailbody"><span id="volumes" class="productdetailbody">1</span></td>
(ABC-CLIO)
</pre>

=== ISBN: ===
<pre>
<td class="productdetailhead" width="88"><span id="ISBNLabel">ISBN</span></td>
<td class="productdetailbody">1-57607-785-3</td>
(ABC-CLIO)

<div class="isbn">0-313-32847-1</div>
(Greenwood, homepage)

<div id="pnlIsbn"> <span class="book_options">ISBN:</span> <span id="lblIsbn">0-313-32847-1</span> </div>
(Greenwood, product page)

<td width="35%"><font id="title_catalogue_title_font">ISBN Number</font></td>
<td width="65%"><font id="text">9812102108</font></td>
(Marshall Cavendish)

<span class="isbnNumber">0195162471</span>
(OUP)

<li>ISBN: <strong>0-8103-0100-8</strong></li>
(Thomson Gale)
</pre>

=== Book Edition: ===
<pre>
<div class="edition"> Revised and Expanded Edition </div>
(OUP)
</pre>
Added by [[User:Tim White|Tim]]

== RFC vCard Example ==
<pre><nowiki>
9. References

[ISO 8601] ISO 8601:1988 - Data elements and interchange formats -
Information interchange - Representation of dates and
times - The International Organization for
Standardization, June, 1988.

[ISO 8601 TC] ISO 8601, Technical Corrigendum 1 - Data elements and
interchange formats - Information interchange -
Representation of dates and times - The International
Organization for Standardization, May, 1991.

[ISO 9070] ISO 9070, Information Processing - SGML support
facilities - Registration Procedures for Public Text
Owner Identifiers, April, 1991.

[CCITT E.163] Recommendation E.163 - Numbering Plan for The
International Telephone Service, CCITT Blue Book,
Fascicle II.2, pp. 128-134, November, 1988.

[CCITT X.121] Recommendation X.121 - International Numbering Plan for
Public Data Networks, CCITT Blue Book, Fascicle VIII.3,
pp. 317-332, November, 1988.

[CCITT X.520] Recommendation X.520 - The Directory - Selected
Attribute Types, November 1988.

[CCITT X.521] Recommendation X.521 - The Directory - Selected Object
Classes, November 1988.

[MIME-DIR] Howes, T., Smith, M., and F. Dawson, "A MIME Content-
Type for Directory Information", RFC 2425, September
1998.

[RFC 1738] Berners-Lee, T., Masinter, L., and M. McCahill,
"Uniform Resource Locators (URL)", RFC 1738, December
1994.

[RFC 1766] Alvestrand, H., "Tags for the Identification of
Languages", RFC 1766, March 1995.

[RFC 1872] Levinson, E., "The MIME Multipart/Related Content-
type", RFC 1872, December 1995.

[RFC 2045] Freed, N., and N. Borenstein, "Multipurpose Internet
Mail Extensions (MIME) - Part One: Format of Internet
Message Bodies", RFC 2045, November 1996.

[RFC 2046] Freed, N., and N. Borenstein, "Multipurpose Internet
Mail Extensions (MIME) - Part Two: Media Types", RFC
2046, November 1996.

[RFC 2047] Moore, K., "Multipurpose Internet Mail Extensions
(MIME) - Part Three: Message Header Extensions for
Non-ASCII Text", RFC 2047, November 1996.

[RFC 2048] Freed, N., Klensin, J., and J. Postel, "Multipurpose
Internet Mail Extensions (MIME) - Part Four:
Registration Procedures", RFC 2048, January 1997.

[RFC 2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.

[RFC 2234] Crocker, D., and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997.

[UNICODE] "The Unicode Standard - Version 2.0", The Unicode
Consortium, July 1996.

[VCARD] Internet Mail Consortium, "vCard - The Electronic
Business Card Version 2.1",
http://www.imc.org/pdi/vcard-21.txt, September 18,
1996.
</nowiki></pre>
[http://www.faqs.org/rfcs/rfc2426.html vCard RFC]

== W3C XHTML Spec Example ==
<pre><nowiki>
<h1><a name="refs" id="refs">E.</a> References</h1>

<p><strong>This appendix is informative.</strong></p>

<dl>
<dt><a name="ref-css2" id="ref-css2"><strong>[CSS2]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/1998/REC-CSS2-19980512">Cascading Style Sheets, level 2 (CSS2) Specification</a></cite>", B. Bos, H. W. Lie, C. Lilley, I. Jacobs, 12 May 1998.<br />
<a href="http://www.w3.org/TR/REC-CSS2">Latest version</a> available at: http://www.w3.org/TR/REC-CSS2</dd>

<dt><a name="ref-dom" id="ref-dom"><strong>[DOM]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001">Document Object Model (DOM) Level 1 Specification</a></cite>", Lauren Wood <em lang="lt" xml:lang="lt">et al.</em>, 1 October
1998.<br />
<a href="http://www.w3.org/TR/REC-DOM-Level-1">Latest version</a> available at: http://www.w3.org/TR/REC-DOM-Level-1</dd>

<dt><a name="ref-dom2" id="ref-dom2"><strong>[DOM2]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113">Document Object Model (DOM) Level 2 Core Specification</a></cite>", A. Le Hors, <em lang="lt" xml:lang="lt">et
al.</em>, 13 November 2000.<br />
<a href="http://www.w3.org/TR/DOM-Level-2-Core">Latest version</a> available at: http://www.w3.org/TR/DOM-Level-2-Core</dd>

<dt><a name="ref-html4" id="ref-html4"><strong>[HTML]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/1999/REC-html401-19991224">HTML 4.01 Specification</a></cite>", D. Raggett, A. Le Hors, I. Jacobs, 24 December 1999.<br />
<a href="http://www.w3.org/TR/html401">Latest version</a> available at: http://www.w3.org/TR/html401</dd>

<dt><a name="ref-posix.1" id="ref-posix.1"><strong>[POSIX.1]</strong></a></dt>

<dd>"<cite>ISO/IEC 9945-1:1990 Information Technology - Portable Operating System Interface (POSIX) - Part 1: System Application Program Interface (API) [C Language]</cite>", Institute of Electrical
and Electronics Engineers, Inc, 1990.</dd>

<dt><a id="ref-rfc2045" name="ref-rfc2045"><strong>[RFC2045]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2045.txt">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a></cite>", N. Freed and N. Borenstein, November
1996. Note that this RFC obsoletes RFC1521, RFC1522, and RFC1590.</dd>

<dt><a name="ref-rfc2046" id="ref-rfc2046"><strong>[RFC2046]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2046.txt">RFC2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a></cite>", N. Freed and N. Borenstein, November 1996.<br />
Available at <a href="http://www.ietf.org/rfc/rfc2046.txt">http://www.ietf.org/rfc/rfc2046.txt</a>. Note that this RFC obsoletes RFC1521, RFC1522, and RFC1590.</dd>

<dt><a name="ref-rfc2119" id="ref-rfc2119"><strong>[RFC2119]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2119.txt">RFC2119: Key words for use in RFCs to Indicate Requirement Levels</a></cite>", S. Bradner, March 1997.<br />
Available at: http://www.ietf.org/rfc/rfc2119.txt</dd>

<dt><a name="ref-rfc2376" id="ref-rfc2376"><strong>[RFC2376]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2376.txt">RFC2376: XML Media Types</a></cite>", E. Whitehead, M. Murata, July 1998.<br />
This document is obsoleted by [<a href="#ref-rfc3023">RFC3023</a>].<br />
Available at: http://www.ietf.org/rfc/rfc2376.txt</dd>

<dt><a name="ref-rfc2396" id="ref-rfc2396"><strong>[RFC2396]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2396.txt">RFC2396: Uniform Resource Identifiers (URI): Generic Syntax</a></cite>", T. Berners-Lee, R. Fielding, L. Masinter, August 1998.<br />
This document updates RFC1738 and RFC1808.<br />
Available at: http://www.ietf.org/rfc/rfc2396.txt</dd>

<dt><a name="ref-rfc2854" id="ref-rfc2854"><strong>[RFC2854]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2854.txt">RFC2854: The text/html Media Type</a></cite>", D. Conolly, L. Masinter, June 2000.<br />
Available at: http://www.ietf.org/rfc/rfc2854.txt</dd>

<dt><a name="ref-rfc3023" id="ref-rfc3023"><strong>[RFC3023]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc3023.txt">RFC3023: XML Media Types</a></cite>", M. Murata, S. St.Laurent, D. Kohn, January 2001.<br />
This document obsoletes [<a href="#ref-rfc2376">RFC2376</a>].<br />
Available at: http://www.ietf.org/rfc/rfc3023.txt</dd>

<dt><a id="ref-rfc3066" name="ref-rfc3066"><strong>[RFC3066]</strong></a></dt>

<dd>"<a href="http://www.ietf.org/rfc/rfc3066.txt">Tags for the Identification of Languages</a>", H. Alvestrand, January 2001.<br />
Available at: http://www.ietf.org/rfc/rfc3066.txt</dd>

<dt><a id="ref-rfc3236" name="ref-rfc3236"><strong>[RFC3236]</strong></a></dt>

<dd>"<a href="http://www.ietf.org/rfc/rfc3236.txt">The 'application/xhtml+xml' Media Type</a>", M. Baker, P. Stark, January 2002.<br />
Available at: http://www.ietf.org/rfc/rfc3236.txt</dd>

<dt><a id="ref-xhtml-mathml" name="ref-xhtml-mathml"><strong>[XHTML+MathML]</strong></a></dt>

<dd><cite>"<a href="http://www.w3.org/TR/MathML2/dtd/xhtml-math11-f.dtd">XHTML plus Math 1.1 <abbr title="Document Type Definition">DTD</abbr></a></cite>", "A.2 MathML as a DTD Module", Mathematical
Markup Language (MathML) Version 2.0. Available at: http://www.w3.org/TR/MathML2/dtd/xhtml-math11-f.dtd</dd>

<dt><a id="ref-xhtmlmime" name="ref-xhtmlmime"><strong>[XHTMLMIME]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/2002/NOTE-xhtml-media-types-20020801">XHTML Media Types</a></cite>", Masayasu Ishikawa, 1 August 2002.<br />
<a href="http://www.w3.org/TR/xhtml-media-types">Latest version</a> available at: http://www.w3.org/TR/xhtml-media-types</dd>

<dt><a id="ref-xhtmlmod" name="ref-xhtmlmod"><strong>[XHTMLMOD]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410">Modularization of XHTML</a></cite>", M. Altheim et al., 10 April 2001.<br />
<a href="http://www.w3.org/TR/xhtml-modularization">Latest version</a> available at: http://www.w3.org/TR/xhtml-modularization</dd>

<dt><a name="ref-xml" id="ref-xml"><strong>[XML]</strong></a></dt>

<dd>"<a href="http://www.w3.org/TR/2000/REC-xml-20001006">Extensible Markup Language (XML) 1.0 Specification (Second Edition)</a>", T. Bray, J. Paoli, C. M. Sperberg-McQueen, E. Maler, 6 October
2000.<br />
<a href="http://www.w3.org/TR/REC-xml">Latest version</a> available at: http://www.w3.org/TR/REC-xml</dd>

<dt><a name="ref-xmlns" id="ref-xmlns"><strong>[XMLNS]</strong></a></dt>

<dd>"<a href="http://www.w3.org/TR/1999/REC-xml-names-19990114">Namespaces in XML</a>", T. Bray, D. Hollander, A. Layman, 14 January 1999.<br />
XML namespaces provide a simple method for qualifying names used in XML documents by associating them with namespaces identified by URI.<br />
<a href="http://www.w3.org/TR/REC-xml-names">Latest version</a> available at: http://www.w3.org/TR/REC-xml-names</dd>

<dt><a name="ref-xmlc14n" id="ref-xmlc14n"><strong>[XMLC14N]</strong></a></dt>

<dd>"<a href="http://www.w3.org/TR/2001/REC-xml-c14n-20010315">Canonical XML Version 1.0</a>", J. Boyer, 15 March 2001.<br />
This document describes a method for generating a physical representation, the canonical form, of an XML document.<br />
<a href="http://www.w3.org/TR/xml-c14n">Latest version</a> available at: http://www.w3.org/TR/xml-c14n</dd>
</dl>
</nowiki></pre>
[http://www.w3.org/TR/xhtml1/#refs XHTML1.0 Spec references]

== CiteProc XHTML Output ==

The XHTML output for CiteProc[http://xbiblio.sourceforge.net/citeproc.html] wasn't designed per se as a microformat, but is probably not a bad place to start. It is desgined to handle a wide range of content. Here is the APA output:

<pre><nowiki>
<div id="bibliography">

<h3>References</h3>

<p id="Brenner2000a" class="bibref">
<span class="creator">Brenner, N.</span>
<span class="date"> (<span class="year">2000</span>) </span>
<span class="title">The Urban Question as a Scale Question: Reflections
on Henri Lefebre, Urban Theory and the Politics of Scale, </span>
<span class="container">
<span class="title" style="font-style: italic">International Journal of
Urban and Regional Research, </span>
<span class="volume">24</span>
<span class="issue">(2)</span>
<span class="locator">, pp. 361–78</span>
</span>.
</p>

<p id="NW2000-0207" class="bibref">
<span class="creator">Newsweek</span>
<span class="date">
(<span class="year">2000a</span>
<span class="month">, February</span>
<span class="day"> 7</span>)
</span>
<span class="title">The Grandmas Pay a Visit, </span>
<span class="container">
<span class="volume">135</span>
<span class="issue">(6)</span>
<span class="locator">, pp. 45</span>
</span>.
</p>

<p id="Veer1996a" class="bibref">
<span class="creator">van der Veer, P.</span>
<span class="date"><span class="year"> (1996) </span></span>
<span class="title">Riots and Rituals: The Construction of Violence
and Public Space in Hindu Nationalism</span>
<span class="container">, In Brass, P.<span class="role"> (Ed.)</span>.
<span class="title" style="font-style: italic">Riots and Pogroms.</span>
<span class="origin"><span class="place">New York</span>
<span class="publisher">: NYU Press</span></span>
<span class="locator">, pp. 154–76</span>
</span>.
</p>
</div>
</nowiki></pre>

== ACM Digital Library Search Result Examples ==

The [http://www.acm.org/dl/ ACM Digital Library] is a heavily used computer science literature database.

First, the markup for one entry from the table of contents page for the ACM TACO (Transactions on Architecture and Code Optimization) journal:

<pre>
<nowiki>
<td align="left" class="small-text">
<a href="citation.cfm?id=1113841.1113842&coll=portal&dl=ACM&idx=1113841&part=periodical&WantType=periodical&title=ACM%20Transactions%20on%20Architecture%20and%20Code%20Optimization%20%28TACO%29&CFID=68451946&CFTOKEN=20517650"class="medium-text" target="_self">
<strong>Improving WCET by applying a WC code-positioning optimization </strong>
</a>
<br>
Wankang Zhao, David Whalley, Christopher Healy, Frank Mueller
<br>
<small> Pages: 335 - 365</small>
<br>Full text available: <A HREF="ft_gateway.cfm?id=1113842&type=pdf&coll=portal&dl=ACM&CFID=68451946&CFTOKEN=20517650" target="_blank"><img src="images/pdf_logo.gif" width="16" height="16" hspace="1" alt="pdf format" border="0" align="texttop">Pdf</A>(510 KB)

<div class="smaller-text"><table border="0" cellpadding="0" cellpadding="0"><tr valign="top"><td class="smaller-text" nowrap>Additional Information:</td>
<td class="smaller-text"><img src="img/doc_blank.gif" width="1" height="16" alt="" border="0" align="texttop">
<A HREF="citation.cfm?id=1113842&jmp=cit&coll=portal&dl=ACM&CFID=68451946&CFTOKEN=20517650#CIT" target="_self">full citation</a>,
<A HREF="citation.cfm?id=1113842&jmp=abstract&coll=portal&dl=ACM&CFID=68451946&CFTOKEN=20517650#abstract" target="_self">abstract</A>,
<A HREF="citation.cfm?id=1113842&jmp=references&coll=portal&dl=ACM&CFID=68451946&CFTOKEN=20517650#references" target="_self"> references</A>,
<A HREF="citation.cfm?id=1113842&jmp=indexterms&coll=portal&dl=ACM&CFID=68451946&CFTOKEN=20517650#indexterms" target="_self"> index terms</A></td></tr></table></div></td><td> </td></tr><tr><td> </td>
</nowiki>
</pre>

The markup for the 'full citation' page is similar, with a little more information about the authors.

Here's the markup from the 'ACM Ref' link, which apparently is how they suggest you format it:
<pre>
<nowiki>
Zhao, W., Whalley, D., Healy, C., and Mueller, F. 2005.
Improving WCET by applying a WC code-positioning optimization.
<i>ACM Trans. Archit. Code Optim.</i> 2, 4 (Dec. 2005), 335-365.
DOI= http://doi.acm.org/10.1145/1113841.1113842
</nowiki>
</pre>

== IEEE IEEExplore Search Results Markup ==

<pre><nowiki>
<td width="96%" class="bodyCopyBlackLargeSpaced" valign="middle">
<strong>On the parallel execution time of tiled loops</strong><br>
Hogstedt, K.; Carter, L.; Ferrante, J.<br>
<A href='/xpl/RecentIssue.jsp?punumber=71'>Parallel and Distributed Systems, IEEE Transactions on</A><br>
Volume: 14

 Issue: 3
 March 2003 <br />
Page(s): 307- 321<br>
Digital Object Identifier 10.1109/TPDS.2003.1189587<br>

<div id="menu0" style="display:block"><strong>Summary: </strong> Many
computationally-intensive programs, such as those for differential equations, spatial
interpolation, and dynamic programming, spend a large portion of their execution time in
multiply-nested loops that have a regular stencil of data dependences.....</div>
</td>

</nowiki>
</pre>

== CiteSeer database search results ==

The [http://citeseer.ist.psu.edu CiteSeer] database has been another heavily used Computer Science online resource, and it has minimal markup:

Here's what you see on the main page for a given paper - this information is duplicated everywhere on the page, but this is where it's formatted most like an academic citation:
<pre><nowiki>
<font size=-1>Yoshio Kataoka, Michael D. Ernst, William G. Griswold, and David Notkin.
Automated support for program refactoring using invariants. In ICSM, pages 736-- 743,
November 2001. http://citeseer.ist.psu.edu/kataoka01automated.html  
<a href="http://citeseer.ist.psu.edu/check/1791139">More</a></font><br>

</nowiki>
</pre>

Clicking on the 'More' link in the above text gets you a page with a listing of all the ways they found it written out as a citation in other papers. This is an example of how they mark up each of those entries:

<pre><nowiki>
<br>
Yoshio Kataoka, Michael D. Ernst, William G. Griswold, and David Notkin.
<i>Automated support for program refactoring using invariants</i>.
In ICSM, pages 736-- 743, November 2001.<br>
<br>
</nowiki>
</pre>

== CiteULike.org citation listing ==

[http://www.citeulike.org/ CiteULike] is a shared reference database site that allows organization using tags and ratings. The site imports from many unstructured web resources using mostly screen-scraping plugins (I think --Mike)

Here is an example of the markup for one article on the main page:
<pre><nowiki>
<tr><td colspan="2"><ul><li>
<a class="title" href="/user/jrw/article/505272">Geometric phases in adiabatic open quantum systems</a>
<div class="vague"></div>
<div class="vague">by
<a class="author" href="/user/jrw/author/Sarandy">Sarandy</a> MS, <a class="author" href="/user/jrw/author/Lidar">Lidar</a> DA</div>
<div class="vague">
posted to <a class="tag" rel="tag" href="/user/jrw/tag/geometry">geometry</a> <a class="tag" rel="tag" href="/user/jrw/tag/physics">physics</a> <a class="tag" rel="tag" href="/user/jrw/tag/quantum">quantum</a> <a class="tag" rel="tag" href="/user/jrw/tag/quantum-information">quantum-information</a>
by <a href="/user/jrw">jrw</a>
as <img alt="x"src="http://static.citeulike.org/img/star2.png" />
on 2006-02-14 18:36:22
</div>
</li>
</ul>
</td>
</tr>
</nowiki></pre>

And here is markup from the detail page for another publication:

<pre><nowiki>
<div class="content">

<table border="0"><tr><td width="100%"><h1>T-Coffee: A novel method for fast and accurate multiple sequence alignment.</h1></td><td>
</td></tr></table>
<div class="vague"><i>J Mol Biol</i>, Vol. 302, No. 1. (8 September 2000), pp. 205-217.</div>
<br>

<h2>Authors</h2>

<ul><li><span class="black">
<a class="author" href="/user/ffranca/author/Notredame">Notredame</a> C</span>,
<span class="black">
<a class="author" href="/user/ffranca/author/Higgins">Higgins</a> DG</span>,
<span class="black">
<a class="author" href="/user/ffranca/author/Heringa">Heringa</a> J</span>
</li></ul>

<ul>
</ul>

<table border="0" width="100%">
<tr>
<td valign="top">
<h2>Online Article
<span class="Z3988" title="ctx_ver=Z39.88-2004&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rfr_id=info:sid/citeulike.org/citeulike&rft.aufirst=&rft_id=info:doi/10%2e1006%2fjmbi%2e2000%2e4042&rft.spage=205&rft.issue=1&rft.aulast=Notredame&rft.title=J+Mol+Biol&rft.epage=217&rft.issn=0022%2d2836&rft.volume=302&rft.auinit=C&rft.atitle=T%2dCoffee%3a+A+novel+method+for+fast+and+accurate+multiple+sequence+alignment%2e&date=2000-9-8&rft.genre=article&genre=article"></span>

</h2>
</td>
</div>
</td>
</tr>
<tr>
<td valign="top">
<ul>

<li><span class="black">DOI:</span> <a accesskey="1" href="http://dx.doi.org/10.1006/jmbi.2000.4042" rel="nofollow">View article online</a></li>
<li><span class="black">Pubmed:</span> <a accesskey="2" href="http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?cmd=Retrieve&db=pubmed&dopt=Abstract&list_uids=10964570" rel="nofollow">View article online</a></li>

<li><span class="black">Hubmed:</span> <a accesskey="3" href="http://www.hubmed.org/display.cgi?uids=10964570" rel="nofollow">View article online</a></li>

</ul>

</td>
</tr>
</table>
</nowiki>
</pre>
== Citeproc XHTML output ==

I'm the author of the [http://xbiblio.sourceforge.net/citeproc.html citeproc] project, which includes a micro-format of sorts (though I never thought of it as such) in its XHTML output mode. See [http://xbiblio.sourceforge.net/examples/apa-en.html here] for an example. The difference compared to the bibtex-derived model is that is a) more generic and b) hierachical.

It would be possible, certainly, to do a flat model if for some reason there was a good technical reason not to go hierarchical (though is there?)

'''The burden of proof is on *going* hierarchical, rather than a simpler flat solution. Complexity must be justified, not simplicity.'''

... but then you need to think outside the BibTeX box in any case. Any model of this sort ought to be able to handle legal citations, magazine articles, patents, etc. etc.; not just a narrow range of BibTeX types.

'''Per the microformats [[process]], microformats are designed to support existing practice on the Web, anything else should be omitted from at least the first version.'''

== Styles ==
This does NOT define a format, but instead shows how the format should be displayed. This is something out of the direct scope of this project. CSS styles will handle the look-and-feel of the text, and the author can put it in any order they choose. These links are mentioned for two reasons, one is informative, the other is so we know at least meet the minimum properties that are used in the styles.

* [http://www.liu.edu/cwis/cwp/library/workshop/citmla.htm MLA Style]
* [http://www.bu.edu/library/guides/citation.html Chicago, MLA, and APA styles]
* [http://www.legalbluebook.com/ Blue Book] for legal citations
* [http://www.columbia.edu/cu/cup/cgos/idx_basic.html Columbia University Citation Style] developed for modern internet citations

citation-examples

2006-02-26T20:24:02Z

Tim White: /* Contributors */

citations in the wild

2006-01-31T22:25:31Z

Tim White:

(For a cleaner version, see [http://www.tjameswhite.com/citation-examples.htm])

== ABC-CLIO Product [http://www.abc-clio.com/products/overview.aspx?productid=109327 detail page] ==
<pre>
<table border="0" cellpadding="0" cellspacing="0" width="430">
<tr>
<td width="101" valign="top" align="left"></td>
<td width="102" valign="top" align="left"></td>
<td width="101" valign="top" align="left"></td>
<td width="125" valign="top" align="center"></td>
</tr>
<tr>
<td width="430" colspan="4" class="productsubtitle"><span id="serieslbl" class="productsubtitle"><a href="browseseries.aspx?seriesid=33">Teaching With Documents Series</a></span></td>
</tr>
<tr>
<td width="430" colspan="4" class="producttitle"><span id="title" class="producttitle">The 1920's</span></td>
</tr>
<tr>
<td width="430" colspan="4" class="productsubtitle"><span id="subtitle" class="productsubtitle"></span></td>
</tr>
<tr>
<td width="430" colspan="4" class="productauthor"><span id="credit" class="productauthor"></span></td>
</tr>
<tr>
<td width="430" colspan="4" height="12"><img border="0" src="../images/blank-white.gif" width="1" height="12" alt=""/></td>
</tr>
<tr>
<td width="130" align="left"><img id="productImage" src="../images/dbimages/1011\101103.GIF" alt="" style="border-width:0px;width:115px;" /></td>
<td width="300" valign="top" align="right" colspan="3">
<table border="0" cellpadding="0" cellspacing="0" width="290">
<tr>
<td width="110" class="productdetailhead"><span id="pubdatelabel" class="productdetailhead">Publication Date</span></td>
<td width="180" class="productdetailbody"><span id="pubdate" class="productdetailbody">11/2001</span></td>
</tr>
<tr>
<td width="110" class="productdetailhead"><span id="pageslabel" class="productdetailhead">Pages</span></td>
<td width="180" class="productdetailbody"><span id="pages" class="productdetailbody">132</span></td>
</tr>
<tr>
<td width="110" class="productdetailhead"><span id="volumeslabel" class="productdetailhead">Volumes</span></td>
<td width="180" class="productdetailbody"><span id="volumes" class="productdetailbody">1</span></td>
</tr>
<tr>
<td width="110" class="productdetailhead"><span id="trimlabel" class="productdetailhead">Size</span></td>
<td width="180" class="productdetailbody"><span id="trimsize" class="productdetailbody">8.5x11</span></td>
</tr>
</table>


<table id="PriceTable" cellspacing="0" cellpadding="0" width="290" border="0">
<tr>
<td class="productdetailhead" width="290" height="15" colspan="4"><img src="../images/academic/blank-blue.gif" id="PriceLine" width="290" height="1" border="0" /></td>
</tr>
<tr>
<td class="productdetailhead" width="54">Format</td>
<td class="productdetailhead" width="68">Price</td>
<td class="productdetailhead" width="88"><span id="ISBNLabel">ISBN</span></td>
<td class="productdetailhead" width="80"> </td>
</tr>
<tr>
<td class="productdetailhead"><b>Print</b></td>
<td class="productdetailbody">$39.00</td>
<td class="productdetailbody">1-57607-785-3</td>
<td class="productdetailhead"> </td>
</tr>
</table>

</td>
</tr>
</table>
</div>
</pre>

== Greenwood Press [http://www.greenwood.com/ home page] featured book ==
<pre>
<div class="title"> <a href="/books/BookDetail.asp?sku=GR2847">The Greenwood Encyclopedia of World Folklore and Folklife</a> </div>
<div class="img_box"> <a href="/books/BookDetail.asp?sku=GR2847"> <img src="/_net.templates/showImage.aspx?imgName=0313328471.jpg&s=140" alt="The Greenwood Encyclopedia of World Folklore and Folklife" border="0" /></a> </div>
<div class="sub_title">Four Volumes</div>
<div class="author">William M. Clements</div>
<div class="isbn">0-313-32847-1</div>
<div class="price">$449.95 <span class="pipe">|</span> £255.00</div>

<div class="bookDescription"> China . . . Malta . . . Madagascar . . . Wales . . . and Texas: these are among the many exotic, distant lands that capture our minds and imaginations. In an era of increasing globalization, students, general readers, and business professionals need to know about... <a href="/books/BookDetail.asp?sku=GR2847">Read more</a> </div>
</div>
</pre>

== Greenwood Press [http://www.greenwood.com/catalog/GR2847.aspx Product detail page] ==
<pre>
<div id="pnlContent" class="pnlContent">
<div id="pnlFlyerBox" class="flyerBox"> <a id="hlFlyer" class="flyerLink" href="/books/printFlyer.aspx?sku=GR2847" target="_blank">Print book flyer</a> <br />
<a id="hlFlyerInternational" class="international_flyer" href="/books/printFlyer.aspx?sku=GR2847&location=international" target="_blank">(International version)</a> </div>
<span id="lblTitle" class="book_headline block">The Greenwood Encyclopedia of World Folklore and Folklife</span> <span id="lblSubTitle" class="book_subline">Four Volumes</span>
<div id="pnlBookDetails" class="detailsBox">
<div id="pnlImgBox" class="imgBox"> <img src="/_net.templates/showImage.aspx?imgName=0313328471.jpg&s=135" alt="" border="0" /> </div>
<a id="hlAddToCart" title="Add this item to your shopping cart" href="/shopping_cart/?sku=GR2847"><img title="Add this item to your shopping cart" src="/_net.templates/roundedButton.aspx?ButtonText=Add to Cart" alt="" border="0" /></a> <a id="hlAddToWishList" title="Save this item to your wish list" href="/wish_list/?sku=GR2847"><img title="Save this item to your wish list" src="/_net.templates/roundedButton.aspx?ButtonText=Add to Wish List" alt="" border="0" /></a> <a id="hlSharePage" title="Email this page to a friend" href="/books/sendform.asp?sku=GR2847" target="_blank"><img title="Email this page to a friend" src="/_net.templates/roundedButton.aspx?ButtonText=Email" alt="" border="0" /></a> <a id="hlPrintPage" title="Version of this page optimized for printing" href="/catalog/GR2847.aspx?print=1" target="_blank"><img title="Version of this page optimized for printing" src="/_net.templates/roundedButton.aspx?ButtonText=Print" alt="" border="0" /></a> <a id="hlWorldCat" href="http://worldcatlibraries.org/wcpa/isbn/0313328471" style="FLOAT: right"><img src="/images/world_catalog.gif" alt="" border="0" /></a>
<div class="authors"><span><a href="/catalog/author/C/229.aspx">William M. Clements</a> (ed.)</span></div>
<span id="lblAuthorsNote" class="block"></span>
<div><span class="book_options">Book Code:</span> <span id="lblBookCode">GR2847</span></div>
<div id="pnlIsbn"> <span class="book_options">ISBN:</span> <span id="lblIsbn">0-313-32847-1</span> </div>
<div id="pnlPageColation"> 1972 pages, maps; photos </div>
<span id="lblImprint" class="block">Greenwood Press</span>
<div id="pnlPubDate"> <span class="book_options">Publication Date:</span> <span id="lblPubDate">12/30/2005</span> </div>
<div id="pnlListPrice"> <span class="book_options">List Price:</span> <span id="lblListPrice">$449.95</span> (<a href="/contactus/order_info.asp?SectionID=about&Location=order_info#UKEME" title="Click for international ordering information">UK Sterling Price: £255.00</a>) </div>
<div id="pnlAvailability"> <span class="book_options">Availability:</span> <span id="lblAvailability">In Stock</span> </div>
<div id="pnlMediaType"> <span class="book_options">Media Type:</span> <span id="lblMediaType">Hardcover</span> </div>
<div class="clearing"></div>
</div>
<div id="pnlBookInformation"> <span class="book_options">Subjects:</span>
<ul class="toc">
<li> <a id="rpCategories__ctl1_hlCategory" href="/catalog/subject/Anthropology.aspx">Anthropology</a> » <a id="rpCategories__ctl1_hlSubCategory" href="/catalog/subject/Anthropology/Folklore.aspx">Folklore</a> </li>
<li> <a id="rpCategories__ctl2_hlCategory" href="/catalog/subject/Anthropology.aspx">Anthropology</a> » <a id="rpCategories__ctl2_hlSubCategory" href="/catalog/subject/Anthropology/Anthropology%2b(General).aspx">Anthropology (General)</a> </li>
<li> <a id="rpCategories__ctl3_hlCategory" href="/catalog/subject/Anthropology.aspx">Anthropology</a> » <a id="rpCategories__ctl3_hlSubCategory" href="/catalog/subject/Anthropology/Cultural%2bAnthropology.aspx">Cultural Anthropology</a> </li>
<li> <a id="rpCategories__ctl4_hlCategory" href="/catalog/subject/History.aspx">History</a> » <a id="rpCategories__ctl4_hlSubCategory" href="/catalog/subject/History/World%2bHistory%2b(General).aspx">World History (General)</a> </li>
</ul>
<div id="pnlDescription"> <span class="book_options">Description:</span> <span id="lblDescription1" class="description block">China . . . Malta . . . Madagascar . . . Wales . . . and Texas: these are among the many exotic, distant lands that capture our minds and imaginations. In an era of increasing globalization, students, general readers, and business professionals need to know about the world and its varied ways. So too, a knowledge of world cultures is fundamental to an understanding of America's ethnically rich society. Folklore isn't just about the long ago and far away. It's about the here and now, and there's no better way to learn about cultural diversity than to study the folklore and folkways of different ethnic groups. <br />
More than just Cinderella and other fairy tales, folklore encompasses the whole realm of traditional beliefs and activities that define a culture. The most comprehensive work of its kind, this massive encyclopedia engagingly and authoritatively surveys folklife and traditions from around the world. Through its vast scope and lengthy entries, it transcends other references on particular national or regional folklores and is the most ambitious undertaking of its type. Organized in four volumes, the encyclopedia provides convenient access to information about folklore generally and to the traditions of particular regions:<br />
Volume 1: Topics and Themes, Africa, Australia and Oceania<br />
Volume 2: Southeast Asia and India, Central and East Asia, Middle East<br />
Volume 3: Europe<br />
Volume 4: North and South America</span> <span id="lblDescription2" class="description block">Along with the expertise of the contributors, of Volume Editor William M. Clements, and of Advisory Editor Thomas A. Green, the encyclopedia draws upon a distinguished board of internationally recognized scholars, including:<br />
<li> Roger D. Abrahams<br />
</li>
<li> Cristina Bacchilega<br />
</li>
<li> Gillian Bennett<br />
</li>
<li> Mary Ellen Brown<br />
</li>
<li> James R. Dow<br />
</li>
<li> Alessandro Falassi<br />
</li>
<li> Barbro Klein<br />
</li>
<li> Peter Knecht<br />
</li>
<li> Natalie Kononenko<br />
</li>
<li> Frances M. Malpezzi<br />
</li>
<li> Margaret Mills<br />
</li>
<li> M. D. Muthukumaraswamy<br />
</li>
<li> Gerald Pocius<br />
</li>
<li> And John S. Ryan.<br />
<br />
<b>Features:</b><br />
</li>
<li> Brings together the knowledge of more than 200 specialists from around the world.<br />
</li>
<li> Provides 39 extended entries on topics central to world folklore.<br />
</li>
<li> Details the folklore and folkways of roughly 170 cultural groups.<br />
</li>
<li> Entries discuss the background, beliefs, oral and theatrical traditions, arts and crafts, and contemporary concerns of each cultural group.<br />
</li>
<li> Each entry cites numerous works for further reading.<br />
</li>
<li> A generous selection of maps and illustrations makes world folklore come to life.<br />
</li>
<li> A list of entries and a cumulative subject index, repeated in each volume, offer convenient access to the vast body of information contained in the encyclopedia.<br />
</li>
<li> A selected, general bibliography directs students and general readers to the most important broad studies of world folklore.<br />
</li>
<li> A glossary defines key terms, theories, and concepts.<br />
<br />
<b>Benefits:</b><br />
</li>
<li> Helps students learn about cultures, customs, and daily life around the world.<br />
</li>
<li> Fosters respect and appreciation for the many ethnic traditions behind contemporary American culture.<br />
</li>
<li> Provides valuable background information for the study of world religions, holidays, and festivals.<br />
</li>
<li> Offers a valuable context for understanding world history, politics, literature, and the arts.<br />
</li>
<li> Invites students to compare and contrast the values and experiences of different cultures.<br />
</li>
<li> Fosters critical reading skills and serves as a model for student research.<br />
<br />
<b>Volume 1: Topics and Themes, Africa, Australia and Oceania</b><br />
Certain themes and topics are central to world foklore. The thematic essays in this volume discuss such matters as:<br />
</li>
<li> Antiquarianism<br />
</li>
<li> Cultural Evolution<br />
</li>
<li> Ethnopoetics<br />
</li>
<li> Gender<br />
</li>
<li> Invented Tradition<br />
</li>
<li> Nativism<br />
</li>
<li> Primitivism<br />
</li>
<li> Public Folklore<br />
</li>
<li> Race<br />
</li>
<li> Trickster<br />
</li>
<li> And many more.<br />
<br />
<b>Volume 2: Southeast Asia and India, Central and East Asia, Middle East</b><br />
Included in this volume are entries on such cultural groups and regions as:<br />
</li>
<li> Bali<br />
</li>
<li> China<br />
</li>
<li> Duna<br />
</li>
<li> Iban<br />
</li>
<li> Kazakh<br />
</li>
<li> Mongol<br />
</li>
<li> Orissa<br />
</li>
<li> Palestine<br />
</li>
<li> Tonga<br />
</li>
<li> Uyghur<br />
</li>
<li> And many others.<br />
<br />
<b>Volume 3: Europe</b><br />
Included in this volume are entries on the folklore of such cultural regions and groups as:<br />
</li>
<li> Ashkenazim<br />
</li>
<li> Basque<br />
</li>
<li> Brittany<br />
</li>
<li> Flanders<br />
</li>
<li> Germany<br />
</li>
<li> Isle of Man<br />
</li>
<li> Roma<br />
</li>
<li> Russia<br />
</li>
<li> Sami<br />
</li>
<li> Ukraine<br />
</li>
<li> And many more.<br />
<br />
<b>Volume 4: North and South America</b><br />
The entries in this volume explore the folk traditions of such regions and groups as:<br />
</li>
<li> Appalachia<br />
</li>
<li> Choctaw<br />
</li>
<li> Haiti<br />
</li>
<li> Island Carib<br />
</li>
<li> Maya<br />
</li>
<li> Quechua<br />
</li>
<li> Seminole<br />
</li>
<li> Western Inuit and Yupik<br />
</li>
<li> Xavante<br />
</li>
<li> Yanomami<br />
</li>
<li> And many more.<br />
<br />
Because folklore is the essence of daily life, this encyclopedia addresses the curriculum needs of high school students and is also an indispensable resource for teachers. In addition, anyone researching folklore in a public library will find this the first place to look for detailed information about cultural traditions around the world.</li>
</span> </div>
<div id="pnlLCCardNumber" class="description"> <span class="book_options">LC Card Number:</span> <span id="lblLCCardNumber">2005019219</span> </div>
<div id="pnlLCCClass" class="description"> <span class="book_options">LCC Class:</span> <span id="lblLCCClass">GR35 </span> </div>
<div id="pnlDeweyClass" class="description"> <span class="book_options">Dewey Class:</span> <span id="lblDeweyClass">398</span> </div>
</div>
</div>
</div>
</pre>

== Marshall Cavendish [http://www.marshallcavendish.com/marshallcavendish/academic/redirector.xml?url=/marshallcavendish/academic/catalogue/books/regionalism_n_regional_security/9812102108.xml product page] ==
<pre>
<table cellpadding="2" width="100%">
<tr valign="top">
<td><font id="title_catalogue_font"><b>Regionalism & Regional Security</b></font></td>
</tr>
</table>
<font id="text">
<div style="" align="">
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">ISBN Number</font></td>
<td width="65%"><font id="text">9812102108</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Series</font></td>
<td width="65%"><font id="text">null</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Title</font></td>
<td width="65%"><font id="text">The New Terrorism: Anatomy, Trends and Counter-strategies</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Imprint</font></td>
<td width="65%"><font id="text">Eastern Universities Press</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Specifications</font></td>
<td width="65%"><font id="text">152 mm X 227 mm, 368 pp, limp with flaps, 500 gms</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Authors</font></td>
<td width="65%"><font id="text">Andrew Tan & Kumar Ramakrishna (eds)</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Target Audience</font></td>
<td width="65%"><font id="text">University lecturers/researchers, undergraduate students, academicians and those interested in Regional Security Studies.</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Price (SG)</font></td>
<td width="65%"><font id="text">S$ 39.00</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Price (US)</font></td>
<td width="65%"><font id="text">US$ 30.00</font>   <a href="javascript: addToCart()"><img src="/marshallcavendish/components/db_content/MC_AC_redirector/pic/addCart.gif" border="0"/></a></td>
</tr>
</table>
<br/>
<br/>
The terrorist attacks of September 11, 2001 on the World Trade Centre in New York and the Pentagon in Washington represented a true watershed in world history.<br/>
<br/>
The attacks revealed the horrifying nature of the so-called "new terrorism" that has emerged in the post-Cold War era. The new terrorism is defined by four key features:</div>
</font>
<ul>
<li>
<p align="justify"><font id="text">sheer lethality</font></p>
</li>
<li>
<p align="justify"><font id="text">religious dimension</font></p>
</li>
<li>
<p align="justify"><font id="text">networked organizational structure</font></p>
</li>
<li>
<p align="justify"><font id="text">greatly enhanced striking power   </font></p>
</li>
</ul>
<font id="text">
<div style="" align="">As September 11 clearly demonstrated, the new terrorists can leverage on technology to inflict catastrophic damage even on superpowers, let alone other states.<br/>
<br/>
To examine the new dimensions of terrorism, a conference was organized in Singapore in late March 2002 that brought together a number of leading experts from a wide range of backgrounds from America, Europe and Asia, and the key findings are presented in this volume under the following headings:</div>
</font>
<ul>
<li>
<p align="justify"><font id="text">Anatomy of the new terrorism</font></p>
</li>
<li>
<p align="justify"><font id="text">Terrorist trends and patterns in the Asia-Pacific region</font></p>
</li>
<li>
<p align="justify"><font id="text">Religion and terrorism: Southeast Asian perspectives</font></p>
</li>
<li>
<p align="justify"><font id="text">Formulating counter-strategies   </font></p>
</li>
</ul>
<font id="text">
<div style="" align=""> <span style="font-weight: bold;"> <b> About the Author: </b> </span> <br/>
Both Andrew Tan and Kumar Ramakrishna are Assistant Professors at the Institute of Defence and Strategic Studies, Nanyang Technological University, Singapore.<br/>
Andrew Tan received his M.Phil from Cambridge and PhD from the University of Sydney. His research interests are conflict (inter-state tensions, insurgencies, terrorism and force modernization) in Southeast Asia, and security issues in Asia.<br/>
Kumar Ramakrishna obtained his PhD in History from the University of London in 1999. He teaches and writes on the history of strategic thought as well as the war on terror.</div>
</font>
<td width="18.666662" style="valign: top; background-color: white ; " rowspan="1" colspan="1"><br/>
</td>
<tr valign="top">
<td width="570.666524" style="valign: top; background-color: white ; " rowspan="1" colspan="1"><br/>
</td>
<td width="18.666662" style="valign: top; background-color: white ; " rowspan="1" colspan="1"><br/>
</td>
</tr>
</div>
</pre>

== Oxford University Press (USA) [http://www.us.oup.com/us/?view=usa homepage] ==
<pre>
<div class="isbnSummaryDetails">
<h2> <a href="/us/catalog/general/subject/HistoryAmerican/ColonialRevolutionary/?view=usa&ci=0195162471">The Glorious Cause</a> </h2>
<div class="subTitle"> The American Revolution, 1763-1789 </div>
<div class="edition"> Revised and Expanded Edition </div>
<div class="byline"> Robert Middlekauff </div>
<span class="isbnNumber">0195162471</span>, <span class="format">hardback</span>, <span class="publicationDate"> Feb 2005 </span> <span class="price"> $37.50 </span> <span class="description"> The classic history of the American Revolution--now in an updated and expanded twentieth anniversary edition </span>
<div class="related">
<h3>More </h3>

<a href="/us/catalog/general/subject/HistoryAmerican/?view=usa&sf=all">History, American</a> > <a href="/us/catalog/general/subject/HistoryAmerican/ColonialRevolutionary/?view=usa&sf=all">Colonial & Revolutionary</a> </div>
</div>

</div>
</pre>

== Oxford University Press (USA) [http://www.us.oup.com/us/catalog/general/subject/HistoryAmerican/ColonialRevolutionary/?view=usa&ci=0195162471#Product_Details Product page]==
<pre>
<div class="isbnProperties isbnSummary">
<div class="isbnSummaryHeading">
<h1>The Glorious Cause</h1>
<div class="subTitle"> The American Revolution, 1763-1789 </div>
<div class="edition"> Revised and Expanded Edition </div>
<div class="byline"> Robert Middlekauff </div>
</div>

<div class="cover"> <span class="bookShot"><a href="#"><img src="/images/covers/0195162471.jpg"
width="63" alt="bookshot" /> </a></span> <span class="addToCart"><a href="http://www.us.oup.com/us/cart/cart.jsp?op=a&i=0195162471&c=85&q=1&r=http%3A%2F%2Fwww.us.oup.com%2Fus%2Fcatalog%2Fgeneral%2Fsubject%2FHistoryAmerican%2FColonialRevolutionary%2F%3Fview%3Dusa%26ci%3D0195162471">Add to Cart</a></span> </div>

<div class="isbnSummaryDetails"> <span class="isbnNumber">0195162471</span>, <span class="format">hardback</span>, <span class="pages"> 760 pages </span>
<div id="generalinfo"> <span class="publicationDate">Feb 2005, </span> <span class="availability"> In Stock </span> </div>
<div class="cost">
<h2>Price:</h2>
$37.50 <span class="discountCode">(02)</span> </div>
<div class="shipping"> <a href="/us/assets/shippingInfo.jsp?si=1.5&so=3.75&sc=0&isi=5&iso=5&isc=0" target="_blank" onclick="window.open(this.href, this.target, 'height=445,width=445,scrollbars');
return false;">Shipping Details</a> </div>
<div class="moreSeries redArrow">
<h3>See more from the series</h3>
<ul>
<li><a href="/us/catalog/general/series/OxfordHistoryoftheUnitedStates/?view=usa">Oxford History of the United States, Vol. 3</a></li>
</ul>
</div>

</div>

</div>
</div>
</pre>

== Thomson Gale product detail page ==
<pre>
<div id =" title_main">

<h2>Contemporary Literary Criticism</h2>

<div id =" credits">
<ul>
<li><h2>Excerpts from Criticism of the Works of Today's Novelists, Poets, Playwrights, Short Story Writers, Scriptwriters, & Other Creative Writers</h2>
Volume 1</li>

<li><i>Published by Thomson Gale</i></li>
</ul>
</div>

<div id =" description">
<p>Each print volume in this long-standing series profiles approximately 6-8 novelists, poets, playwrights and other creative writers by providing full-text or excerpted criticism taken from books, magazines, literary reviews, newspapers and scholarly journals. Among those profiled in this volume are:</p>
<ul>
<li>Kingsley Amis
<li>John Dos Passos
<li>Hermann Hesse
<li>Ezra Pound
</ul>
</div>

<div id =" detail">
<ul>
<li>Published/Released:<strong> March 1973</strong></li>
<li>ISBN: <strong>0-8103-0100-8</strong></li>
<li>Product number: <strong>001415</strong></li>
<li>Page count: <strong>485 pp./vol.</strong></li>
<li>Shipping Weight: <strong>5.00 lbs (2.27 kgs)</strong></li>
</ul>
</div> 

<div id =" price">
<P>Price: US $205.00</p>
</div>

</div>
</div>
</pre>

citation-formats

2006-01-22T21:39:25Z

Tim White: /* Types and Roles */

= Citation Formats =

This page will display several different types of citation format types. The idea is to compare what properties are common amonst all of the formats and which ones should be blended into this microformat.

See also:
* [[cite]]
* [[cite-brainstorming]]
* [[cite-examples]]

== Comparison chart ==
The following chart maps the terms from one implementation to another. This is important because if all the properties are introduced to this microformats, then its possible to map them to a number of different formats. The table currently only uses Dublin Core, MODS, and bibTeX. Each column has all the properties and their equivalent in each format. If there is no corresponding property the cell is grey. At the bottom of the list are the unique terms to each format. Dublin core has basic terms and terms that extend the basic ones. If the property is an extention of a basic term it is in ()'s. MODS uses XML, so any sub-properties are listed in their tree form, property/sub-property.

THIS IS NOT DEFINIATIVE, any errors should be corrected. More formats will be added to the list as they are mapped.

<table border="1">
<tr>
<th>Dublin Core</th>
<th>MODS</th>
<th>bibTeX</th>
<th>Z39.80</th>
</tr>
<tr>
<td>Title (alternative)</td>
<td>titleInfo/title<br/>titleInfo/PartNum</td>
<td>booktitle<br/>title<br/>chapter<br/>number<br/>pages<br/>volume<br/>series</td>
<td>Analytic Title<br/>
Collective or Series Title<br/>
Monographic Title<br/>
Work Fraction Title<br/>
Location of Conference<br/>
Main Entry<br/>
Name of Conference<br/>
Number of Meeting<br/>
Other Title<br/>
Parallel Title<br/>
Title Abbriviation<br/>
Title of Conference Proceedings<br/>
Translated Title<br/>
Uniform Title<br/>
Abbriviated Translated Title<br/>
Symposium or Session Title<br/>
Collective or Series Edition<br/>
Video/Film Edition<br/>
</td>
</tr>
<tr>
<td>creator</td>
<td>name/namePart</td>
<td>author<br/>creator</td>
<td>Author, Primary<br/>
Corporate Author, Primary<br/>
Abstract Author<br/>
Authorship Statement<br/>
Acknowledged Supporters<br/>
Assignee for Patents<br/>
Chairperson of Conference<br/>
Director of AV Program<br/>
Other Author<br/>
Reviewed Book Author<br/>
Studio<br/>
Sponsor of Conference<br/>
Staff/Cast<br/>
Symposium Chairperson<br/>
Author Address or Affiliation<br/>
Author Country<br/>
Electronic Address of Author<br/>
</td>
</tr>
<tr>
<td>subject</td>
<td>subject/topic</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td>Description (abstract | tableOfContents)</td>
<td>abstract<br/>note<br/>tableOfContents</td>
<td>abstract<br/>annotation<br/>note<br/>contents</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Contributer</td>
<td>name</td>
<td>editor?</td>
<td>Book/Report/Volume Editor<br/>
Producer<br/>
Translator<br/>
</td>
</tr>
<tr>
<td>Date (available | created | dateAccepted | dateCopyrighted | dateSubmitted | issued | modified | valid)</td>
<td>originInfo/dateIssued<br/>originInfo/dateCreated<br/>originInfo/dateCaptured<br/>originInfo/dateOther</td>
<td>month<br/>year</td>
<td>Copyright Year<br/>Date-generic<br/>Date of conference<br/>Date of Publication<br/>Date of Update/Revisou/Issuance of Database Record<br/>Former Date<br/>Entry date for Database Record<br/>Database Update<br/>Year of Publication</td>
</tr>
<tr>
<td>Type</td>
<td>typeOfResource<br/>genre</td>
<td>@class<br/>type</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Format (extent | medium)</td>
<td>physicalDescription/internetMediaType<br/>physicalDescription/extent<br/>physicalDescription/form</td>
<td>published</td>
<td>needs mapping</td>
</tr>
<tr>
<td>identifier (bibliographicCitation)</td>
<td>identifier</td>
<td>ISBN<br/>ISSN<br/>LCCN<br/>URL</td>
<td>ISBN<br/>Identifier<br/>Report Identfier<br/>ISSN</td>
</tr>
<tr>
<td>Source</td>
<td>relatedItem</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td>language</td>
<td>language</td>
<td>language</td>
<td bgcolor="#cccccc"></td>
</tr>
<tr>
<td>Relation (...)</td>
<td>relatedItem/...</td>
<td>crossRef</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Coverage (spacial | temporal)</td>
<td>subject/temporal<br/>subject/geographic<br/>subject/hierarchicalGeographic<br/>subject/cartographics</td>
<td></td>
<td>needs mapping</td>
</tr>
<tr>
<td bgcolor="#cccccc"></td>
<td>classifications</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td>Rights (accessRights | license)</td>
<td>accessConditions</td>
<td>copyright</td>
<td>needs mapping</td>
</tr>
<tr>
<td>publisher</td>
<td bgcolor="#cccccc"></td>
<td>publisher</td>
<td>Publisher Name<br/>
Place of Publication<br/>
Country of Publication<br/>
Generic Address<br/>
</td>
</tr>
<tr>
<td>audience (educationLevel | mediator)</td>
<td>targetAudience</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td bgcolor="#999999">accualMethod<br/>accualPeriodicaty<br/>accualPolicy<br/>instrcutionalMethod<br/>provenance<br/>rightsHolder</td>
<td bgcolor="#999999">location<br/>extension<br/>recordInfo</td>
<td bgcolor="#999999">address<br/>afflilication<br/>location<br/>edition<br/>institution<br/>journal<br/>key<br/>keywords<br/>mrnumber<br/>organization<br/>price<br/>school<br/>size</td>
<td bgcolor="#999999">(the following need to be mapped to the above rows or left here as other)<br/><br/>
Database Source<br/>
Databse Record Identifier<br/>
Database Producer Name<br/>
Rights Management<br/>
Subfile<br/>
Other Source Identifier<br/>
Vendor Record Identifier<br/>
Database Vendor Name<br/>
Column Number<br/>
Edition<br/>
Frequency of Publication<br/>
Internet Location for Document<br/>
Supplement/Part/Special number identifer<br/>
Issue Identifier<br/>
Location in Work<br/>
Number of the Chapter<br/>
Number in Series<br/>
Volume Identifier<br/>
Section Indentifier<br/>
</td>
</tr>
</table>

== Dublin Core Metadata ==
[http://dublincore.org/ Dublin Core] metadata uses a small vocabulary to descibe the data.
* contributor
* coverage
* creator
* date
* description
* format
* identifier
* language
* publisher
* relation
* rights
* source
* subject
* title
* type

From those there are specialised types where are just refinments of the previous, for example:

* abstract refines description.
* accessRights refines rights

[http://dublincore.org/documents/dc-citation-guidelines/ Guidelines for Encoding Bibliographic Citation Information in Dublin Core Metadata]

== MODS (Metadata Object Description Schema) ==
This is a format developed for the Libray of Congress for a bibliographic element set that may be used for a variety of purposes, and particularly for library applications.

[http://www.loc.gov/standards/mods/ http://www.loc.gov/standards/mods/]

(the schema is very big, once i devote the proper time to review it, i will post more about the structure -brian)

== XMLResume ==
<pre>
<!ELEMENT pubs (pub+)>
<!ENTITY % pubElements "(artTitle|bookTitle|author|date|pubDate|publisher|pageNums|url)">
<!ELEMENT pub (para | %pubElements;)*>
<!ATTLIST pub id ID #IMPLIED>
<!ELEMENT artTitle (#PCDATA | link)*>
<!ELEMENT bookTitle (#PCDATA | link)*>
<!ELEMENT author (#PCDATA)>
<!ATTLIST author name IDREF #IMPLIED>
<!ELEMENT pubDate (month?, year)> 
<!ELEMENT publisher (#PCDATA | link | url)*>
<!ELEMENT pageNums (#PCDATA)>
</pre>

== BibTeX ==
=== Fields Used by Bibtex ===
<table border="1" width="100%">
<tr>
<td><strong>abstract:</strong></td>
<td>An abstract of the work.</td>
</tr>
<tr>
<td><b>address:</b></td>
<td>Publisher's address. For major publishing houses,
just the city is given. For small publishers, you can
help the reader by giving the complete address.</td>
</tr>
<tr>
<td><strong>affiliation:</strong></td>
<td>The author's affiliation.</td>
</tr>
<tr>
<td><b>annote:</b></td>
<td>An annotation. It is not used by he standard
bibliography styles, but may be used by others that
produce an annotated bibliography.</td>
</tr>
<tr>
<td><b>author:</b></td>
<td>The name(s) of the author(s).</td>
</tr>
<tr>
<td><b>booktitle: </b></td>
<td>Title of a book, part of which is being cited. For
book entries, use the <strong>title</strong> field
instead.</td>
</tr>
<tr>
<td><b>chapter:</b></td>
<td>A chapter (or section) number.</td>
</tr>
<tr>
<td><strong>contents:</strong></td>
<td>A Table of Contents.</td>
</tr>
<tr>
<td><strong>copyright:</strong></td>
<td>Copyright information.</td>
</tr>
<tr>
<td><strong>crossref:</strong></td>
<td>The database key of the entry being cross-referenced.</td>
</tr>
<tr>
<td><b>edition: </b></td>
<td>The edition of a book - for example
"Second". Notice that it is in capitals.</td>
</tr>
<tr>
<td><b>editor: </b></td>
<td>Name(s) of editor(s). If there is also an author
field, then the editor field gives the editor of the book
or collection in which the reference appears.</td>
</tr>
<tr>
<td><b>howpublished:</b></td>
<td>How something strange has been published. The first
word should be capitalized.</td>
</tr>
<tr>
<td><b>institution:</b></td>
<td>The sponsoring institution of a technical report.</td>
</tr>
<tr>
<td><strong>ISBN:</strong></td>
<td>The International Standard Book Number.</td>
</tr>
<tr>
<td><strong>ISSN:</strong></td>
<td>The International Standard Serial Number. Used to
identify a journal.</td>
</tr>
<tr>
<td><b>journal: </b></td>
<td>A journal name. Abbreviations are provided for many
journals.</td>
</tr>
<tr>
<td><b>key: </b></td>
<td>Used for alphabetizing and creating a label when the
author and editor fields are missing. This field should
not be confused with the key that appears at the
beginning of the reference.</td>
</tr>
<tr>
<td><strong>keywords:</strong></td>
<td>Key words used for searching or possibly for
annotation.</td>
</tr>
<tr>
<td><strong>language:</strong></td>
<td>The language the document is written in.</td>
</tr>
<tr>
<td><strong>LCCN:</strong></td>
<td>The Library of Congress Call Number.</td>
</tr>
<tr>
<td><strong>location:</strong></td>
<td>A location associated with the entry, such as the
city in which a conference took place.</td>
</tr>
<tr>
<td><b>month: </b></td>
<td>The month in which the work was published or, for an
unpublished work, in which it was written.</td>
</tr>
<tr>
<td><strong>mrnumber:</strong></td>
<td>The <em>Mathematical Reviews</em> number.</td>
</tr>
<tr>
<td><b>note:</b></td>
<td>Any additional information that can help the reader.
First word should be capitalized.</td>
</tr>
<tr>
<td><b>number: </b></td>
<td>The number of a journal, magazine, technical report,
or of a work in a series. An issue of a journal or
magazine is usually identified by its volume and number;
the organization that issues a technical report usually
gives it a number; and sometimes books are given numbers
in a named series.</td>
</tr>
<tr>
<td><b>organization: </b></td>
<td>The organization that sponsors a conference or
publishes a manual.</td>
</tr>
<tr>
<td><b>pages:</b></td>
<td>One or more page numbers or ranges of number, such as
37--42, or 7,53,82--94.</td>
</tr>
<tr>
<td><strong>price:</strong></td>
<td>The price of the material.</td>
</tr>
<tr>
<td><b>publisher:</b></td>
<td>The publisher's name.</td>
</tr>
<tr>
<td><b>school:</b></td>
<td>The name of the school where a thesis was written.</td>
</tr>
<tr>
<td><b>series:</b></td>
<td>Then name given a series or set of books. When citing
an entire book, the title field gives its title and the
optional series field gives the name of a series in which
the book was published.</td>
</tr>
<tr>
<td><strong>size:</strong></td>
<td>The physical dimensions of the work.</td>
</tr>
<tr>
<td><b>title:</b></td>
<td>The work's title.</td>
</tr>
<tr>
<td><b>type:</b></td>
<td>The type of technical report - for example,
"Research Note".</td>
</tr>
<tr>
<td><strong>url:</strong></td>
<td>The WWW Universal Resource Locator that points to the
item being referenced. Often used for technical reports
to point to the FTP site where it resides.</td>
</tr>
<tr>
<td><b>volume:</b></td>
<td>The volume of a journal or multivolume book.</td>
</tr>
<tr>
<td><b>year:</b></td>
<td>The year of publication or, for an unpublished work,
the year it was written. It should only consist of
numerals, such as 1976.</td>
</tr>
</table>
=== BibTeX citation Types ===
A reference can be to any of a variety of types. Following is a list of types. Each one also explains the fields associated with that type. Any fields not listed as required or optional are considered to be ignored.
<table border="1" width="100%">
<tr>
<td><b>article:</b></td>
<td>An article from a journal or magazine. Required
fields: author, title, journal, year. Optional fields:
volume, number, pages, month, note, key.</td>
</tr>
<tr>
<td><b>book:</b></td>
<td>A book with an explicit publisher. Required fields:
author or editor, title, publisher, year. Optional
fields: volume, series, address, edition, month, note,
key.</td>
</tr>
<tr>
<td><b>booklet: </b></td>
<td>A work that is printed and bound, but without a named
publisher or sponsoring institution. Required fields:
title. Optional fields: author, howpublished, address,
month, year, note, key.</td>
</tr>
<tr>
<td><strong>collection:</strong></td>
<td>A collection of works. Same as <a href="#proceedings">Proceedings</a>.</td>
</tr>
<tr>
<td><b>conference:</b></td>
<td>The same as <a href="#inproceedings">Inproceedings</a>.</td>
</tr>
<tr>
<td><b>inbook:</b></td>
<td>A part of a book, which may be a chapter and/or a
range of pages. Required fields: author or editor, title,
chapter and/or pages, publisher, year. Optional fields:
volumer, series, address, edition, month, note, key.</td>
</tr>
<tr>
<td><b>incollection:</b></td>
<td>A part of a book with its own title. Required fields:
author, title, booktitle, publisher, year. Optional
fields: editor, pages, organization, publisher, address,
month, note, key.</td>
</tr>
<tr>
<td><a name="inproceedings"></a><b>inproceedings:</b></td>
<td>An article in a conference proceedings. Required
fields: author, title, booktitle, year. Optional fields:
editor, pages, organization, publisher, address, month,
note, key.</td>
</tr>
<tr>
<td><b>manual: </b></td>
<td>Technical documentation. Required fields: title.
Optional fields: author, organization, address, edition,
month, year, note.</td>
</tr>
<tr>
<td><b>mastersthesis:</b></td>
<td>A Master's thesis. Required fields: author, title,
school, year. Optional fields: address, month, note, key.</td>
</tr>
<tr>
<td><b>misc:</b></td>
<td>Use this type when nothing else fits. Required
fields: none. Optional fields: author, title,
howpublished, month, year, note, key.</td>
</tr>
<tr>
<td><strong>patent:</strong></td>
<td>A patent.</td>
</tr>
<tr>
<td><b>phdthesis:</b></td>
<td>A Ph.D. thesis. Required fields: author, title,
school, year. Optional fields: address, month, note, key.</td>
</tr>
<tr>
<td><a name="proceedings"></a><b>proceedings:</b></td>
<td>The proceedings of a conference. Required fields:
title, year. Optional fields: editor, publisher,
organization, address, month, note, key.</td>
</tr>
<tr>
<td><b>techreport:</b></td>
<td>A report published by a school or other institution,
usually numbered within a series. Required fields:
author, title, institution, year. Optional fields: type,
number, address, month, note, key.</td>
</tr>
<tr>
<td><b>unpublished:</b></td>
<td>A document with an author and title, but not formally
published. Required fields: author, title, note. Optional
fields: month, year, key.</td>
</tr>
</table>

==== Examples ====
<pre><nowiki>
@book{kn:gnus,

AUTHOR = "Donald E. Knudson",
TITLE = "1966 World Gnus Almanac",
PUBLISHER = {Permafrost Press},
ADDRESS = {Novosibirsk} }

<div class="book" id="kn:gnus">
<div class="author">Donald E. Knudson</div>
<div class="title">1966 World Gnus Almanac</div>
<div class="publisher">Permafrost Press</div>
<div class="address">Novosibirsk</div>
</div>

@article{XAi_HSCheng_1994a,

author = "X. Ai and H. S. Cheng",
title = "Influence of moving dent on point {EHL} contacts",
journal = "Tribol. Trans.",
volume = "37",
year = "1994",
pages = "323--335",
}

<div class="article" id="XAi_HSCheng_1994a">
<div class="author">X. Ai and H. S. Cheng</div>
<div class="title">Influence of moving dent on point {EHL} contacts</div>
<div class="journal">Tribol. Trans.</div>
<div class="volume">37</div>
<div class="year">1994</div>
<div class="pages">323--335</div>
</div>
</nowiki></pre>

== OpenURL ==

OpenURL aka [http://www.niso.org/standards/standard_detail.cfm?std_id=783 Z39.88] defines a standard way of bundling citation data in a URL. It is widely deployed in academic libraries around the world to provide access to licensed content via link resolvers such as [http://www.exlibrisgroup.com/sfx_openurl.htm SFX]. The Context Object in Span ([http://ocoins.info/ COinS]) community standard represents one way to embed OpenURLs in XHTML without including a resolver target.

<pre>
<nowiki>
<span class="Z3988" title="ctx_ver=Z39.88-2004&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.issn=1045-4438"></span>
</nowiki>
</pre>

As you can see this isn't very much like semantic XHTML at all. However significant work has gone into defining the set of Key/Encoded Values (KEVs) that can be used in various [http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=ListRecords&metadataPrefix=oai_dc&set=Core:Metadata+Formats types] of citations: [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:book book], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:dissertation dissertation], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:journal journal], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:patent patent]. It would be possible to simply provide a standard XHTML bundling for these keys as a microformat.

=== Example ===

<pre>
<nowiki>

<div class="openurl-journal">
<span class="aulast">Berners-Lee</span>,
<span class="aufirst">Tim</a>; Hendler, James; Lassila, Ora.</span>
"<span class="atitle">The Semantic Web</span>".
<span class="jtitle">Scientific American</span>
<span class="volume">284</span>(<span class="issue">5</span>), pp.
pp. <span class="pages">34-43</span>.
<span class="issn">0036-8733</span>
</div>

</nowiki>
</pre>

Using OpenURL in this way would enable third party applications that could, say grab citation metadata from a blog, and without much work fire it off at your university's or public libraries openurl resolver to see if the article is available via a licensed databases. The benefits [http://www.infotoday.com/newsbreaks/nb050801-1.shtml have] [http://www.ariadne.ac.uk/issue43/chudnov/ been] [http://www.wallandbinkley.com/quaedam/?p=30 noted] [http://hublog.hubmed.org/archives/001163.html elsewhere].

== Z39.80 ==
I'm not sure the best place for a guide to Z39.80 so please add links as you see fit:

[http://www.niso.org/standards/resources/drft4rev.html http://www.niso.org/standards/resources/drft4rev.html]

== DocBook ==

A subset of the DocBook vocabulary is dedicated to representing a bibliography: http://www.docbook.org/tdg/en/html/bibliography.html

<pre><nowiki>
<!DOCTYPE bibliography PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
<bibliography>
<title>Languages and Semantics</title>
<bibliodiv>
<title>Books</title>
<biblioentry>
<title>Course in General Linguistics</title>
<abbrev>deSaussure59</abbrev>
<author><firstname>Ferdinand</firstname><surname>de Saussure</surname></author>
<editor><firstname>Charles</firstname><surname>Bally</surname></editor>
<editor><firstname>Albert</firstname><surname>Sechehaye</surname></editor>
<othercredit role="translator"><firstname>Wade</firstname><surname>Baskin</surname></othercredit>
<copyright>
<year>1959</year>
<holder>The Philosophical Library Inc.</holder>
</copyright>
<isbn>07-016524-6</isbn>
<publisher>
<publishername>McGraw-Hill Book Company</publishername>
</publisher>
</biblioentry>
</bibliodiv>
</bibliography>
</nowiki></pre>

== Ann Arbor District Library XML feed ==

Here's a record in XML format from their project to simplify
access to the catalog. More discussion on [http://www.blyberg.net John Blyberg's blog].

<pre>
<nowiki>
<p:Record>
<callnum>823 Bu</callnum>
<author>Burkart, Gina, 1971-</author>
<fulltitle>A parent's guide to Harry Potter / Gina Burkart</fulltitle>
<title>A parent's guide to Harry Potter </title>
<pubinfo>Downers Grove, Ill. : InterVarsity Press, c2005</pubinfo>
<desc>112 p</desc>
<bibliography>Includes bibliographical references</bibliography>
<contents>
The Harry hype -- More than a story -- The modern fairy tale -- Discussing fantasy with children -- Morals, not magic -- The real issues in Harry Potter -- Dealing with traumatic experiences -- Facing fears -- Battling bullies -- Delving into diversity -- Hiding hurts -- Letting go of anger -- Getting help -- Choosing good over evil -- The power of love -- Facing spiritual battles
</contents>
<isbn>0830832882</isbn>
<price>$11.00</price>
<lang>eng</lang>
<copies>0</copies>
<catdate>08-16-2005</catdate>
<mattype>a</mattype>
<avail>No copies available</avail>
<recordlink xlink:href="http://www.aadl.org/cat/seek/record=1249810"/>
</p:Record>
</nowiki>
</pre>

== SimpleDC supported by the zoom toolkit ==

<pre>
<nowiki>
<dc xmlns="http/www.loc.gov/zing/srw/dcschema/v1.0/">
<title>Kantor Salomon Sulzer und seine Zeit : eine Dokumentation /</title>
<creator>Avenary, Hanoch.</creator>
<creator>Pass, Walter.</creator>
<creator>Vielmetti, Nikolaus.</creator>
<creator>Adler, Israel, (1925-)</creator>
<subject>Sulzer, Salomon, -- 1804-1890.</subject>
<subject>Jewish composers -- Austria -- Biography.</subject>
<subject>Cantors, Jewish -- Biography.</subject>
<date>1985</date>
<publisher>Sigmaringen : Jan Thorbecke Verlag</publisher>
<identifier>3799540636</identifier>
<description>300 p., [12] p. of plates : ill., music, ports. ; 24 cm.</description>
</dc>
</nowiki>
</pre>

this is the output of marc.toSimpleDC()

== SRU from the Library of Congress ==

http://z3950.loc.gov:7090/voyager?version=1.1&operation=searchRetrieve&query=dinosaur&maximumRecords=1&recordSchema=dc

<pre>
<nowiki>
<?xml version="1.0"?>
<zs:searchRetrieveResponse xmlns:zs="http://www.loc.gov/zing/srw/"><zs:version>1.1</zs:version><zs:numberOfRecords>1701</zs:numberOfRecords><zs:records><zs:record><zs:recordSchema>info:srw/schema/1/dc-v1.1</zs:recordSchema><zs:recordPacking>xml</zs:recordPacking><zs:recordData><srw_dc:dc xmlns:srw_dc="info:srw/schema/1/dc-schema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://purl.org/dc/elements/1.1/" xsi:schemaLocation="info:srw/schema/1/dc-schema http://www.loc.gov/z3950/agency/zing/srw/dc-schema.xsd">
<title>3-D dinosaur adventure [computer file].</title>
<creator>Knowledge Adventure, Inc.</creator>
<type>software, multimedia</type>
<publisher>Glendale, CA : Knowledge Adventure,</publisher>

<date>c1995.</date>
<language>eng</language>
<description>Employs a dinosaur theme-park setting to introduce users to Triassic, Jurassic, and Cretaceous periods. Features hypertext dinosaur encyclopedia covering 150 million years of paleontology. Includes animated video simulations, three-dimensional dinosaur museum, narration, games, activities, and color illustrations.</description>
<description>Ages 5 to 10.</description>
<description>System requirements for PC: 486SX/25MHz processor or higher; 8MB RAM; Windows 3.1, 3.11, or 95; SVGA 256-color graphics adapter; hard drive with 5MB free space; double-speed CD-ROM drive; MPC-compatible sound card; mouse.</description>
<description>System requirements for Macintosh: 68040 or Power PC processor; 8MB RAM; System 7.0 or higher; 256-color graphics capability; thirteen-inch color monitor or larger; hard drive with 4MB free space; double-speed CD-ROM drive.</description>

<description>Ages 5 to 10.</description>
<description>Employs a dinosaur theme-park setting to introduce users to Triassic, Jurassic, and Cretaceous periods. Features hypertext dinosaur encyclopedia covering 150 million years of paleontology. Includes animated video simulations, three-dimensional dinosaur museum, narration, games, activities, and color illustrations.</description>
<subject>Dinosaurs--Juvenile software.</subject>
<subject>Dinosaurs.</subject>
<identifier>URN:ISBN:1569972133</identifier>
</srw_dc:dc></zs:recordData><zs:recordPosition>1</zs:recordPosition></zs:record></zs:records></zs:searchRetrieveResponse>

</nowiki>
</pre>

== Types and Roles ==
(Section is informative only as a place to capture various parts of publication citations.)

There are many different types of publications and this information should be captured in the citation. Possible types include:
* Novel/fiction (specify type -- literature, sci-fi, romance, etc.?)
* Non-fiction
* Poem
* Play
* Magazine
* Reference (seperate out encyclopedia, dictionary, almanac, etc.?)
* Journal
* Article within a journal
* Chapter within a book
* Dissertation
* Web Site
* Page within a web site
* Music Recording
* Video Recording
* Interview
* Physical object (Statue, Painting, etc.)
* ??

Question:
Certain works have specific types of citations, for example, the Bible--and, I assume, other religious works--have very specific citation formats with different relevant information (chapter/verse) than others, as do the works of Shakespeare. Should these be considered seperate types/roles?

A: I think in terms of types, we should at least note the items (chapter, verse, etc). How they get dealt with is still way up in the air. - [[User:Tim White|Tim White]]

Likewise, there are several different roles associated with publications -- author, co-author, editor, translator, etc. Should these be captured under a master "role" or treated as individual elements?

A: Good question. I think there is an important distinction, but whether we follow a design pattern of "role-*" (or more likely "author-*) or some other pattern hasn't been discussed yet. - Tim

citation-brainstorming

2006-01-22T21:38:41Z

Tim White: /* Contributors */

= Citation Brainstroming =

== Contributors ==

* ...
* ... (a bunch of good folks!)
* Tantek Çelik
* Tim White

== See also ==
* [[cite]]
* [[cite-formats]]
* [[cite-examples]]

== XHTML Structure ==
With my exprience working X2V and hCa* has taught me what elememts are easy to find and which are not. Since the Citation microformat is very new it is possible to not make a lot of the same errors twice and to make things easier for extracting application to find and imply certain properties.

* There should be some sort of 'root node' that implies all child elements are for the Citation microformat.
* Since most people will have multiple Citation there should be away to represent each Citation object as a unqiue block independant of another. This is to keep the parse from finding 'author' and applying to all citations. Each citation should be in a container (class="???") that scoped from others.
* Perhaps class="hcite" with <code><cite></code> recommended as the root element. E.g. <code><cite class="hcite"></code>

== Some Thoughts ==

What distinguishes a cite from say [[media-info]] (e.g. [[media-info-examples]]) is that a cite is a reference to something explicitly external to the current piece of content or document, whereas [[media-info]] describes information about content embedded or inline in the current document.

== Semantic Meaning ==
One of the guiding priniciple of Microformats is to use the most semantically rich element to describe each node (Point 2 of Semantic XHTML Design Principles: Use the most accurately precise semantic XHTML building block for each object etc). Since we are dealing with HTML and citations, several elements are candidates to be used to enrich the semantic meaning. [http://www.w3.org/TR/REC-html40/struct/text.html CITE, BLOCKQUOTE, Q, A], (are there more?)

The [[citation-brainstorming|Citation Brainstorming Page]] has a few development and ideas about how to give another person credit for a link. Some of the semantic ideas behind their choices of tags can be applied to a full bibliographic type reference.

== ISBN:// Protocol ==

''' THIS BELONGS IN [[cite-formats]], NOT HERE'''

[http://www.faqs.org/rfcs/rfc3187.html RFC3187] defines an isbn protocol

Example:

URN:ISBN:0-395-36341-1

I'm not sure if any browser uses this data, but it might be have an application in citations describing registered materials with an ISBN

Question: what about using something like OCLC's [http://www.oclc.org/worldcat/open/isbnissnlinking/default.htm WorldCat] for linking titles? - Tim White

== This and That ==
After reading through alot of different citation encoding formats, i noticed that each format was being used in onw of two ways. It was either to describe the Current page (THIS.PAGE) or being used to encode references that point to external resources (THAT.PAGE)

The informatation being encoded was identical for both resources (author, date, name, etc) they just reference different things. For this microformat, i'm not sure if we want to try to solve both problems, or just one? The meta tags in the head element would be the ideal place for information about the THIS.PAGE, but that is not in following with the ideals of microformats where information is human-readable. The THAT.PAGE idea where a list of references is at the end of a document in the form of a bibliography is more inline with the ideals of a microformat where the data is human-readable. That doesn't mean that data about the current document shouldn't be human-readable, so some of the same properties used to reference extermal resources can be used for the current document (THIS.PAGE). To do this a different root item could be used and transforming applications could either extract the citation data about the current page, or information about this page's references.

This is open for discussion, but either way, i believe that the properties used to describe a page will be the same for both THIS and THAT. [http://suda.co.uk/ brian suda]

== Date Formatting ==
Since microformats are all about re-use and the accepted way to encode Date-Time has been pretty much settled, then this is a good place to start when dealing with all the different date citation types.

These are all the different fields from various citation formats that are of temporal nature:
* Date (available | created | dateAccepted | dateCopyrighted | dateSubmitted | issued | modified | valid)
* originInfo/dateIssued
* originInfo/dateCreated
* originInfo/dateCaptured
* originInfo/dateOther
* month
* year
* Copyright Year
* Date - Generic
* Date of Confernce
* Date of Publication
* Date of update/revisou/issuance of database record
* Former Date
* Entry Date for Database Record
* Database Update
* Year of Publication

There are several common properties across several citation domains and will certainly be in the citation microformat, the unique instances will need further consideration, otherwise there could be no end to posiblities.

There are also several properties (year, month, Year of publication) that can be extracted from another source. Therefore, if you only encode a more specific property such as; Date of Publication, you can extract the 'year of publication' from that. Since the date-time format we are modeling after is the ISO date-time format, just the Year portion is an acceptable date. So if you ONLY know the year of publication, the you can form a valid 'Date of Publication' as a microformat (which inturn is a valid 'year of publication') - you milage may vary when it comes to importing into citation applications.

...

It seems to me that these can be collapsed to maybe one or two different date properties. As far as the specific human readable formatting of the date, that can be chosen per whatever the presentation style guide says, and the [[datetime-design-pattern]] used to simplify the markup. - Tantek

== Tags ==
Some of the citation formats has a place for 'keywords' or 'generic tags', etc. This might be a good place to re-use the [http://microformats.org/wiki/rel-tag RelTag microformat]. The downside would be that they are then forced to be links, which might be the correct way to mark-up these terms.

== OpenURL ==
''' THIS BELONGS IN [[cite-formats]], NOT HERE'''

OpenURL is in use in library software around the world to allow citation metadata to be embedded in URLs. Typically these URLs are used for targeting resolvers which essentially proxy access to licensed content. OpenURL also provides an XML encoding. The [http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=ListRecords&metadataPrefix=oai_dc&set=Core:Metadata+Formats key/value] pairs used in OpenURL could relatively easily be adapted to semantic HTML. This is a cow path that could be paved relatively easily using existing modules as appropriate.

OpenURL has a microformat-like encoding: [http://ocoins.info/ COinS]. This uses the 'title' attribute of HTML 'span' tags to embed OpenURL URLs.

Example (from a book review written using the Structured Blogging plugin):

<pre><nowiki>
<p><b>ISBN</b>: <span class='Z3988'
title='ctx_ver=Z39.88-2004&amp;rft_val_fmt=info:ofi/fmt:kev:mtx:book&amp;rft.isbn=0679426612'>
0679426612</span></p>
</nowiki></pre>

== MARC / MODS / Dublin Core ==

The MODS ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgmods.xml example]) and Dublin Core ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgdc.xml example]) transformations of MARC21 may contain some useful ideas.

Here's a first attempt at rewriting the linked examples in XHTML (written in response to a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002438.html mailing list query about encoding book information with microformats]):

<pre><nowiki>
<div class="book" lang="en">
<h3 class="fn">Arithmetic /</h3>
<p>By <span class="creator"><span class="fn">Sandburg, Carl</span>,
<span class="date">1878-1967</span></span>,
and <span class="illustrator">Rand, Ted</span></p>
<p>Publisher: <span class="publisher"><span class="fn">Harcourt Brace Jovanovich</span>,
<span class="locality">San Diego</span></span></p>
<p>Published: <span class="issued">1993</span></p>
<p class="description">A poem about numbers and their characteristics. Features
anamorphic, or distorted, drawings which can be restored to normal by viewing
from a particular angle or by viewing the image's reflection in the provided
Mylar cone.</p>
<p class="note">One Mylar sheet included in pocket.</p>
<p>Subjects:</p>
<ul>
<li class="subject">Arithmetic</li>
<li class="subject">Children's poetry, American.</li>
<li class="subject">Arithmetic</li>
<li class="subject">American poetry</li>
<li class="subject">Visual perception</li>
</ul>
</div>
</nowiki></pre>

citation-formats

2006-01-22T21:36:44Z

Tim White:

= Citation Formats =

This page will display several different types of citation format types. The idea is to compare what properties are common amonst all of the formats and which ones should be blended into this microformat.

See also:
* [[cite]]
* [[cite-brainstorming]]
* [[cite-examples]]

== Comparison chart ==
The following chart maps the terms from one implementation to another. This is important because if all the properties are introduced to this microformats, then its possible to map them to a number of different formats. The table currently only uses Dublin Core, MODS, and bibTeX. Each column has all the properties and their equivalent in each format. If there is no corresponding property the cell is grey. At the bottom of the list are the unique terms to each format. Dublin core has basic terms and terms that extend the basic ones. If the property is an extention of a basic term it is in ()'s. MODS uses XML, so any sub-properties are listed in their tree form, property/sub-property.

THIS IS NOT DEFINIATIVE, any errors should be corrected. More formats will be added to the list as they are mapped.

<table border="1">
<tr>
<th>Dublin Core</th>
<th>MODS</th>
<th>bibTeX</th>
<th>Z39.80</th>
</tr>
<tr>
<td>Title (alternative)</td>
<td>titleInfo/title<br/>titleInfo/PartNum</td>
<td>booktitle<br/>title<br/>chapter<br/>number<br/>pages<br/>volume<br/>series</td>
<td>Analytic Title<br/>
Collective or Series Title<br/>
Monographic Title<br/>
Work Fraction Title<br/>
Location of Conference<br/>
Main Entry<br/>
Name of Conference<br/>
Number of Meeting<br/>
Other Title<br/>
Parallel Title<br/>
Title Abbriviation<br/>
Title of Conference Proceedings<br/>
Translated Title<br/>
Uniform Title<br/>
Abbriviated Translated Title<br/>
Symposium or Session Title<br/>
Collective or Series Edition<br/>
Video/Film Edition<br/>
</td>
</tr>
<tr>
<td>creator</td>
<td>name/namePart</td>
<td>author<br/>creator</td>
<td>Author, Primary<br/>
Corporate Author, Primary<br/>
Abstract Author<br/>
Authorship Statement<br/>
Acknowledged Supporters<br/>
Assignee for Patents<br/>
Chairperson of Conference<br/>
Director of AV Program<br/>
Other Author<br/>
Reviewed Book Author<br/>
Studio<br/>
Sponsor of Conference<br/>
Staff/Cast<br/>
Symposium Chairperson<br/>
Author Address or Affiliation<br/>
Author Country<br/>
Electronic Address of Author<br/>
</td>
</tr>
<tr>
<td>subject</td>
<td>subject/topic</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td>Description (abstract | tableOfContents)</td>
<td>abstract<br/>note<br/>tableOfContents</td>
<td>abstract<br/>annotation<br/>note<br/>contents</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Contributer</td>
<td>name</td>
<td>editor?</td>
<td>Book/Report/Volume Editor<br/>
Producer<br/>
Translator<br/>
</td>
</tr>
<tr>
<td>Date (available | created | dateAccepted | dateCopyrighted | dateSubmitted | issued | modified | valid)</td>
<td>originInfo/dateIssued<br/>originInfo/dateCreated<br/>originInfo/dateCaptured<br/>originInfo/dateOther</td>
<td>month<br/>year</td>
<td>Copyright Year<br/>Date-generic<br/>Date of conference<br/>Date of Publication<br/>Date of Update/Revisou/Issuance of Database Record<br/>Former Date<br/>Entry date for Database Record<br/>Database Update<br/>Year of Publication</td>
</tr>
<tr>
<td>Type</td>
<td>typeOfResource<br/>genre</td>
<td>@class<br/>type</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Format (extent | medium)</td>
<td>physicalDescription/internetMediaType<br/>physicalDescription/extent<br/>physicalDescription/form</td>
<td>published</td>
<td>needs mapping</td>
</tr>
<tr>
<td>identifier (bibliographicCitation)</td>
<td>identifier</td>
<td>ISBN<br/>ISSN<br/>LCCN<br/>URL</td>
<td>ISBN<br/>Identifier<br/>Report Identfier<br/>ISSN</td>
</tr>
<tr>
<td>Source</td>
<td>relatedItem</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td>language</td>
<td>language</td>
<td>language</td>
<td bgcolor="#cccccc"></td>
</tr>
<tr>
<td>Relation (...)</td>
<td>relatedItem/...</td>
<td>crossRef</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Coverage (spacial | temporal)</td>
<td>subject/temporal<br/>subject/geographic<br/>subject/hierarchicalGeographic<br/>subject/cartographics</td>
<td></td>
<td>needs mapping</td>
</tr>
<tr>
<td bgcolor="#cccccc"></td>
<td>classifications</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td>Rights (accessRights | license)</td>
<td>accessConditions</td>
<td>copyright</td>
<td>needs mapping</td>
</tr>
<tr>
<td>publisher</td>
<td bgcolor="#cccccc"></td>
<td>publisher</td>
<td>Publisher Name<br/>
Place of Publication<br/>
Country of Publication<br/>
Generic Address<br/>
</td>
</tr>
<tr>
<td>audience (educationLevel | mediator)</td>
<td>targetAudience</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td bgcolor="#999999">accualMethod<br/>accualPeriodicaty<br/>accualPolicy<br/>instrcutionalMethod<br/>provenance<br/>rightsHolder</td>
<td bgcolor="#999999">location<br/>extension<br/>recordInfo</td>
<td bgcolor="#999999">address<br/>afflilication<br/>location<br/>edition<br/>institution<br/>journal<br/>key<br/>keywords<br/>mrnumber<br/>organization<br/>price<br/>school<br/>size</td>
<td bgcolor="#999999">(the following need to be mapped to the above rows or left here as other)<br/><br/>
Database Source<br/>
Databse Record Identifier<br/>
Database Producer Name<br/>
Rights Management<br/>
Subfile<br/>
Other Source Identifier<br/>
Vendor Record Identifier<br/>
Database Vendor Name<br/>
Column Number<br/>
Edition<br/>
Frequency of Publication<br/>
Internet Location for Document<br/>
Supplement/Part/Special number identifer<br/>
Issue Identifier<br/>
Location in Work<br/>
Number of the Chapter<br/>
Number in Series<br/>
Volume Identifier<br/>
Section Indentifier<br/>
</td>
</tr>
</table>

== Dublin Core Metadata ==
[http://dublincore.org/ Dublin Core] metadata uses a small vocabulary to descibe the data.
* contributor
* coverage
* creator
* date
* description
* format
* identifier
* language
* publisher
* relation
* rights
* source
* subject
* title
* type

From those there are specialised types where are just refinments of the previous, for example:

* abstract refines description.
* accessRights refines rights

[http://dublincore.org/documents/dc-citation-guidelines/ Guidelines for Encoding Bibliographic Citation Information in Dublin Core Metadata]

== MODS (Metadata Object Description Schema) ==
This is a format developed for the Libray of Congress for a bibliographic element set that may be used for a variety of purposes, and particularly for library applications.

[http://www.loc.gov/standards/mods/ http://www.loc.gov/standards/mods/]

(the schema is very big, once i devote the proper time to review it, i will post more about the structure -brian)

== XMLResume ==
<pre>
<!ELEMENT pubs (pub+)>
<!ENTITY % pubElements "(artTitle|bookTitle|author|date|pubDate|publisher|pageNums|url)">
<!ELEMENT pub (para | %pubElements;)*>
<!ATTLIST pub id ID #IMPLIED>
<!ELEMENT artTitle (#PCDATA | link)*>
<!ELEMENT bookTitle (#PCDATA | link)*>
<!ELEMENT author (#PCDATA)>
<!ATTLIST author name IDREF #IMPLIED>
<!ELEMENT pubDate (month?, year)> 
<!ELEMENT publisher (#PCDATA | link | url)*>
<!ELEMENT pageNums (#PCDATA)>
</pre>

== BibTeX ==
=== Fields Used by Bibtex ===
<table border="1" width="100%">
<tr>
<td><strong>abstract:</strong></td>
<td>An abstract of the work.</td>
</tr>
<tr>
<td><b>address:</b></td>
<td>Publisher's address. For major publishing houses,
just the city is given. For small publishers, you can
help the reader by giving the complete address.</td>
</tr>
<tr>
<td><strong>affiliation:</strong></td>
<td>The author's affiliation.</td>
</tr>
<tr>
<td><b>annote:</b></td>
<td>An annotation. It is not used by he standard
bibliography styles, but may be used by others that
produce an annotated bibliography.</td>
</tr>
<tr>
<td><b>author:</b></td>
<td>The name(s) of the author(s).</td>
</tr>
<tr>
<td><b>booktitle: </b></td>
<td>Title of a book, part of which is being cited. For
book entries, use the <strong>title</strong> field
instead.</td>
</tr>
<tr>
<td><b>chapter:</b></td>
<td>A chapter (or section) number.</td>
</tr>
<tr>
<td><strong>contents:</strong></td>
<td>A Table of Contents.</td>
</tr>
<tr>
<td><strong>copyright:</strong></td>
<td>Copyright information.</td>
</tr>
<tr>
<td><strong>crossref:</strong></td>
<td>The database key of the entry being cross-referenced.</td>
</tr>
<tr>
<td><b>edition: </b></td>
<td>The edition of a book - for example
"Second". Notice that it is in capitals.</td>
</tr>
<tr>
<td><b>editor: </b></td>
<td>Name(s) of editor(s). If there is also an author
field, then the editor field gives the editor of the book
or collection in which the reference appears.</td>
</tr>
<tr>
<td><b>howpublished:</b></td>
<td>How something strange has been published. The first
word should be capitalized.</td>
</tr>
<tr>
<td><b>institution:</b></td>
<td>The sponsoring institution of a technical report.</td>
</tr>
<tr>
<td><strong>ISBN:</strong></td>
<td>The International Standard Book Number.</td>
</tr>
<tr>
<td><strong>ISSN:</strong></td>
<td>The International Standard Serial Number. Used to
identify a journal.</td>
</tr>
<tr>
<td><b>journal: </b></td>
<td>A journal name. Abbreviations are provided for many
journals.</td>
</tr>
<tr>
<td><b>key: </b></td>
<td>Used for alphabetizing and creating a label when the
author and editor fields are missing. This field should
not be confused with the key that appears at the
beginning of the reference.</td>
</tr>
<tr>
<td><strong>keywords:</strong></td>
<td>Key words used for searching or possibly for
annotation.</td>
</tr>
<tr>
<td><strong>language:</strong></td>
<td>The language the document is written in.</td>
</tr>
<tr>
<td><strong>LCCN:</strong></td>
<td>The Library of Congress Call Number.</td>
</tr>
<tr>
<td><strong>location:</strong></td>
<td>A location associated with the entry, such as the
city in which a conference took place.</td>
</tr>
<tr>
<td><b>month: </b></td>
<td>The month in which the work was published or, for an
unpublished work, in which it was written.</td>
</tr>
<tr>
<td><strong>mrnumber:</strong></td>
<td>The <em>Mathematical Reviews</em> number.</td>
</tr>
<tr>
<td><b>note:</b></td>
<td>Any additional information that can help the reader.
First word should be capitalized.</td>
</tr>
<tr>
<td><b>number: </b></td>
<td>The number of a journal, magazine, technical report,
or of a work in a series. An issue of a journal or
magazine is usually identified by its volume and number;
the organization that issues a technical report usually
gives it a number; and sometimes books are given numbers
in a named series.</td>
</tr>
<tr>
<td><b>organization: </b></td>
<td>The organization that sponsors a conference or
publishes a manual.</td>
</tr>
<tr>
<td><b>pages:</b></td>
<td>One or more page numbers or ranges of number, such as
37--42, or 7,53,82--94.</td>
</tr>
<tr>
<td><strong>price:</strong></td>
<td>The price of the material.</td>
</tr>
<tr>
<td><b>publisher:</b></td>
<td>The publisher's name.</td>
</tr>
<tr>
<td><b>school:</b></td>
<td>The name of the school where a thesis was written.</td>
</tr>
<tr>
<td><b>series:</b></td>
<td>Then name given a series or set of books. When citing
an entire book, the title field gives its title and the
optional series field gives the name of a series in which
the book was published.</td>
</tr>
<tr>
<td><strong>size:</strong></td>
<td>The physical dimensions of the work.</td>
</tr>
<tr>
<td><b>title:</b></td>
<td>The work's title.</td>
</tr>
<tr>
<td><b>type:</b></td>
<td>The type of technical report - for example,
"Research Note".</td>
</tr>
<tr>
<td><strong>url:</strong></td>
<td>The WWW Universal Resource Locator that points to the
item being referenced. Often used for technical reports
to point to the FTP site where it resides.</td>
</tr>
<tr>
<td><b>volume:</b></td>
<td>The volume of a journal or multivolume book.</td>
</tr>
<tr>
<td><b>year:</b></td>
<td>The year of publication or, for an unpublished work,
the year it was written. It should only consist of
numerals, such as 1976.</td>
</tr>
</table>
=== BibTeX citation Types ===
A reference can be to any of a variety of types. Following is a list of types. Each one also explains the fields associated with that type. Any fields not listed as required or optional are considered to be ignored.
<table border="1" width="100%">
<tr>
<td><b>article:</b></td>
<td>An article from a journal or magazine. Required
fields: author, title, journal, year. Optional fields:
volume, number, pages, month, note, key.</td>
</tr>
<tr>
<td><b>book:</b></td>
<td>A book with an explicit publisher. Required fields:
author or editor, title, publisher, year. Optional
fields: volume, series, address, edition, month, note,
key.</td>
</tr>
<tr>
<td><b>booklet: </b></td>
<td>A work that is printed and bound, but without a named
publisher or sponsoring institution. Required fields:
title. Optional fields: author, howpublished, address,
month, year, note, key.</td>
</tr>
<tr>
<td><strong>collection:</strong></td>
<td>A collection of works. Same as <a href="#proceedings">Proceedings</a>.</td>
</tr>
<tr>
<td><b>conference:</b></td>
<td>The same as <a href="#inproceedings">Inproceedings</a>.</td>
</tr>
<tr>
<td><b>inbook:</b></td>
<td>A part of a book, which may be a chapter and/or a
range of pages. Required fields: author or editor, title,
chapter and/or pages, publisher, year. Optional fields:
volumer, series, address, edition, month, note, key.</td>
</tr>
<tr>
<td><b>incollection:</b></td>
<td>A part of a book with its own title. Required fields:
author, title, booktitle, publisher, year. Optional
fields: editor, pages, organization, publisher, address,
month, note, key.</td>
</tr>
<tr>
<td><a name="inproceedings"></a><b>inproceedings:</b></td>
<td>An article in a conference proceedings. Required
fields: author, title, booktitle, year. Optional fields:
editor, pages, organization, publisher, address, month,
note, key.</td>
</tr>
<tr>
<td><b>manual: </b></td>
<td>Technical documentation. Required fields: title.
Optional fields: author, organization, address, edition,
month, year, note.</td>
</tr>
<tr>
<td><b>mastersthesis:</b></td>
<td>A Master's thesis. Required fields: author, title,
school, year. Optional fields: address, month, note, key.</td>
</tr>
<tr>
<td><b>misc:</b></td>
<td>Use this type when nothing else fits. Required
fields: none. Optional fields: author, title,
howpublished, month, year, note, key.</td>
</tr>
<tr>
<td><strong>patent:</strong></td>
<td>A patent.</td>
</tr>
<tr>
<td><b>phdthesis:</b></td>
<td>A Ph.D. thesis. Required fields: author, title,
school, year. Optional fields: address, month, note, key.</td>
</tr>
<tr>
<td><a name="proceedings"></a><b>proceedings:</b></td>
<td>The proceedings of a conference. Required fields:
title, year. Optional fields: editor, publisher,
organization, address, month, note, key.</td>
</tr>
<tr>
<td><b>techreport:</b></td>
<td>A report published by a school or other institution,
usually numbered within a series. Required fields:
author, title, institution, year. Optional fields: type,
number, address, month, note, key.</td>
</tr>
<tr>
<td><b>unpublished:</b></td>
<td>A document with an author and title, but not formally
published. Required fields: author, title, note. Optional
fields: month, year, key.</td>
</tr>
</table>

==== Examples ====
<pre><nowiki>
@book{kn:gnus,

AUTHOR = "Donald E. Knudson",
TITLE = "1966 World Gnus Almanac",
PUBLISHER = {Permafrost Press},
ADDRESS = {Novosibirsk} }

<div class="book" id="kn:gnus">
<div class="author">Donald E. Knudson</div>
<div class="title">1966 World Gnus Almanac</div>
<div class="publisher">Permafrost Press</div>
<div class="address">Novosibirsk</div>
</div>

@article{XAi_HSCheng_1994a,

author = "X. Ai and H. S. Cheng",
title = "Influence of moving dent on point {EHL} contacts",
journal = "Tribol. Trans.",
volume = "37",
year = "1994",
pages = "323--335",
}

<div class="article" id="XAi_HSCheng_1994a">
<div class="author">X. Ai and H. S. Cheng</div>
<div class="title">Influence of moving dent on point {EHL} contacts</div>
<div class="journal">Tribol. Trans.</div>
<div class="volume">37</div>
<div class="year">1994</div>
<div class="pages">323--335</div>
</div>
</nowiki></pre>

== OpenURL ==

OpenURL aka [http://www.niso.org/standards/standard_detail.cfm?std_id=783 Z39.88] defines a standard way of bundling citation data in a URL. It is widely deployed in academic libraries around the world to provide access to licensed content via link resolvers such as [http://www.exlibrisgroup.com/sfx_openurl.htm SFX]. The Context Object in Span ([http://ocoins.info/ COinS]) community standard represents one way to embed OpenURLs in XHTML without including a resolver target.

<pre>
<nowiki>
<span class="Z3988" title="ctx_ver=Z39.88-2004&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.issn=1045-4438"></span>
</nowiki>
</pre>

As you can see this isn't very much like semantic XHTML at all. However significant work has gone into defining the set of Key/Encoded Values (KEVs) that can be used in various [http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=ListRecords&metadataPrefix=oai_dc&set=Core:Metadata+Formats types] of citations: [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:book book], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:dissertation dissertation], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:journal journal], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:patent patent]. It would be possible to simply provide a standard XHTML bundling for these keys as a microformat.

=== Example ===

<pre>
<nowiki>

<div class="openurl-journal">
<span class="aulast">Berners-Lee</span>,
<span class="aufirst">Tim</a>; Hendler, James; Lassila, Ora.</span>
"<span class="atitle">The Semantic Web</span>".
<span class="jtitle">Scientific American</span>
<span class="volume">284</span>(<span class="issue">5</span>), pp.
pp. <span class="pages">34-43</span>.
<span class="issn">0036-8733</span>
</div>

</nowiki>
</pre>

Using OpenURL in this way would enable third party applications that could, say grab citation metadata from a blog, and without much work fire it off at your university's or public libraries openurl resolver to see if the article is available via a licensed databases. The benefits [http://www.infotoday.com/newsbreaks/nb050801-1.shtml have] [http://www.ariadne.ac.uk/issue43/chudnov/ been] [http://www.wallandbinkley.com/quaedam/?p=30 noted] [http://hublog.hubmed.org/archives/001163.html elsewhere].

== Z39.80 ==
I'm not sure the best place for a guide to Z39.80 so please add links as you see fit:

[http://www.niso.org/standards/resources/drft4rev.html http://www.niso.org/standards/resources/drft4rev.html]

== DocBook ==

A subset of the DocBook vocabulary is dedicated to representing a bibliography: http://www.docbook.org/tdg/en/html/bibliography.html

<pre><nowiki>
<!DOCTYPE bibliography PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
<bibliography>
<title>Languages and Semantics</title>
<bibliodiv>
<title>Books</title>
<biblioentry>
<title>Course in General Linguistics</title>
<abbrev>deSaussure59</abbrev>
<author><firstname>Ferdinand</firstname><surname>de Saussure</surname></author>
<editor><firstname>Charles</firstname><surname>Bally</surname></editor>
<editor><firstname>Albert</firstname><surname>Sechehaye</surname></editor>
<othercredit role="translator"><firstname>Wade</firstname><surname>Baskin</surname></othercredit>
<copyright>
<year>1959</year>
<holder>The Philosophical Library Inc.</holder>
</copyright>
<isbn>07-016524-6</isbn>
<publisher>
<publishername>McGraw-Hill Book Company</publishername>
</publisher>
</biblioentry>
</bibliodiv>
</bibliography>
</nowiki></pre>

== Ann Arbor District Library XML feed ==

Here's a record in XML format from their project to simplify
access to the catalog. More discussion on [http://www.blyberg.net John Blyberg's blog].

<pre>
<nowiki>
<p:Record>
<callnum>823 Bu</callnum>
<author>Burkart, Gina, 1971-</author>
<fulltitle>A parent's guide to Harry Potter / Gina Burkart</fulltitle>
<title>A parent's guide to Harry Potter </title>
<pubinfo>Downers Grove, Ill. : InterVarsity Press, c2005</pubinfo>
<desc>112 p</desc>
<bibliography>Includes bibliographical references</bibliography>
<contents>
The Harry hype -- More than a story -- The modern fairy tale -- Discussing fantasy with children -- Morals, not magic -- The real issues in Harry Potter -- Dealing with traumatic experiences -- Facing fears -- Battling bullies -- Delving into diversity -- Hiding hurts -- Letting go of anger -- Getting help -- Choosing good over evil -- The power of love -- Facing spiritual battles
</contents>
<isbn>0830832882</isbn>
<price>$11.00</price>
<lang>eng</lang>
<copies>0</copies>
<catdate>08-16-2005</catdate>
<mattype>a</mattype>
<avail>No copies available</avail>
<recordlink xlink:href="http://www.aadl.org/cat/seek/record=1249810"/>
</p:Record>
</nowiki>
</pre>

== SimpleDC supported by the zoom toolkit ==

<pre>
<nowiki>
<dc xmlns="http/www.loc.gov/zing/srw/dcschema/v1.0/">
<title>Kantor Salomon Sulzer und seine Zeit : eine Dokumentation /</title>
<creator>Avenary, Hanoch.</creator>
<creator>Pass, Walter.</creator>
<creator>Vielmetti, Nikolaus.</creator>
<creator>Adler, Israel, (1925-)</creator>
<subject>Sulzer, Salomon, -- 1804-1890.</subject>
<subject>Jewish composers -- Austria -- Biography.</subject>
<subject>Cantors, Jewish -- Biography.</subject>
<date>1985</date>
<publisher>Sigmaringen : Jan Thorbecke Verlag</publisher>
<identifier>3799540636</identifier>
<description>300 p., [12] p. of plates : ill., music, ports. ; 24 cm.</description>
</dc>
</nowiki>
</pre>

this is the output of marc.toSimpleDC()

== SRU from the Library of Congress ==

http://z3950.loc.gov:7090/voyager?version=1.1&operation=searchRetrieve&query=dinosaur&maximumRecords=1&recordSchema=dc

<pre>
<nowiki>
<?xml version="1.0"?>
<zs:searchRetrieveResponse xmlns:zs="http://www.loc.gov/zing/srw/"><zs:version>1.1</zs:version><zs:numberOfRecords>1701</zs:numberOfRecords><zs:records><zs:record><zs:recordSchema>info:srw/schema/1/dc-v1.1</zs:recordSchema><zs:recordPacking>xml</zs:recordPacking><zs:recordData><srw_dc:dc xmlns:srw_dc="info:srw/schema/1/dc-schema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://purl.org/dc/elements/1.1/" xsi:schemaLocation="info:srw/schema/1/dc-schema http://www.loc.gov/z3950/agency/zing/srw/dc-schema.xsd">
<title>3-D dinosaur adventure [computer file].</title>
<creator>Knowledge Adventure, Inc.</creator>
<type>software, multimedia</type>
<publisher>Glendale, CA : Knowledge Adventure,</publisher>

<date>c1995.</date>
<language>eng</language>
<description>Employs a dinosaur theme-park setting to introduce users to Triassic, Jurassic, and Cretaceous periods. Features hypertext dinosaur encyclopedia covering 150 million years of paleontology. Includes animated video simulations, three-dimensional dinosaur museum, narration, games, activities, and color illustrations.</description>
<description>Ages 5 to 10.</description>
<description>System requirements for PC: 486SX/25MHz processor or higher; 8MB RAM; Windows 3.1, 3.11, or 95; SVGA 256-color graphics adapter; hard drive with 5MB free space; double-speed CD-ROM drive; MPC-compatible sound card; mouse.</description>
<description>System requirements for Macintosh: 68040 or Power PC processor; 8MB RAM; System 7.0 or higher; 256-color graphics capability; thirteen-inch color monitor or larger; hard drive with 4MB free space; double-speed CD-ROM drive.</description>

<description>Ages 5 to 10.</description>
<description>Employs a dinosaur theme-park setting to introduce users to Triassic, Jurassic, and Cretaceous periods. Features hypertext dinosaur encyclopedia covering 150 million years of paleontology. Includes animated video simulations, three-dimensional dinosaur museum, narration, games, activities, and color illustrations.</description>
<subject>Dinosaurs--Juvenile software.</subject>
<subject>Dinosaurs.</subject>
<identifier>URN:ISBN:1569972133</identifier>
</srw_dc:dc></zs:recordData><zs:recordPosition>1</zs:recordPosition></zs:record></zs:records></zs:searchRetrieveResponse>

</nowiki>
</pre>

== Types and Roles ==
(Section is informative only as a place to capture various parts of publication citations.)

There are many different types of publications and this information should be captured in the citation. Possible types include:
* Novel/fiction (specify type -- literature, sci-fi, romance, etc.?)
* Non-fiction
* Poem
* Play
* Magazine
* Reference (seperate out encyclopedia, dictionary, almanac, etc.?)
* Journal
* Article within a journal
* Chapter within a book
* Dissertation
* Web Site
* Page within a web site
* Music Recording
* Video Recording
* Interview
* Physical object (Statue, Painting, etc.)
* ??

Question:
Certain works have specific types of citations, for example, the Bible--and, I assume, other religious works--have very specific citation formats with different relevant information (chapter/verse) than others, as do the works of Shakespeare. Should these be considered seperate types/roles?

A: I think in terms of types, we should at least note the items (chapter, verse, etc). How they get dealt with is still way up in the air. - Tim

Likewise, there are several different roles associated with publications -- author, co-author, editor, translator, etc. Should these be captured under a master "role" or treated as individual elements?

A: Good question. I think there is an important distinction, but whether we follow a design pattern of "role-*" (or more likely "author-*) or some other pattern hasn't been discussed yet. - Tim

citation-brainstorming

2006-01-22T21:36:35Z

Tim White: /* Types and Roles */

= Citation Brainstroming =

== Contributors ==

* ...
* ... (a bunch of good folks!)
* Tantek Çelik

== See also ==
* [[cite]]
* [[cite-formats]]
* [[cite-examples]]

== XHTML Structure ==
With my exprience working X2V and hCa* has taught me what elememts are easy to find and which are not. Since the Citation microformat is very new it is possible to not make a lot of the same errors twice and to make things easier for extracting application to find and imply certain properties.

* There should be some sort of 'root node' that implies all child elements are for the Citation microformat.
* Since most people will have multiple Citation there should be away to represent each Citation object as a unqiue block independant of another. This is to keep the parse from finding 'author' and applying to all citations. Each citation should be in a container (class="???") that scoped from others.
* Perhaps class="hcite" with <code><cite></code> recommended as the root element. E.g. <code><cite class="hcite"></code>

== Some Thoughts ==

What distinguishes a cite from say [[media-info]] (e.g. [[media-info-examples]]) is that a cite is a reference to something explicitly external to the current piece of content or document, whereas [[media-info]] describes information about content embedded or inline in the current document.

== Semantic Meaning ==
One of the guiding priniciple of Microformats is to use the most semantically rich element to describe each node (Point 2 of Semantic XHTML Design Principles: Use the most accurately precise semantic XHTML building block for each object etc). Since we are dealing with HTML and citations, several elements are candidates to be used to enrich the semantic meaning. [http://www.w3.org/TR/REC-html40/struct/text.html CITE, BLOCKQUOTE, Q, A], (are there more?)

The [[citation-brainstorming|Citation Brainstorming Page]] has a few development and ideas about how to give another person credit for a link. Some of the semantic ideas behind their choices of tags can be applied to a full bibliographic type reference.

== ISBN:// Protocol ==

''' THIS BELONGS IN [[cite-formats]], NOT HERE'''

[http://www.faqs.org/rfcs/rfc3187.html RFC3187] defines an isbn protocol

Example:

URN:ISBN:0-395-36341-1

I'm not sure if any browser uses this data, but it might be have an application in citations describing registered materials with an ISBN

Question: what about using something like OCLC's [http://www.oclc.org/worldcat/open/isbnissnlinking/default.htm WorldCat] for linking titles? - Tim White

== This and That ==
After reading through alot of different citation encoding formats, i noticed that each format was being used in onw of two ways. It was either to describe the Current page (THIS.PAGE) or being used to encode references that point to external resources (THAT.PAGE)

The informatation being encoded was identical for both resources (author, date, name, etc) they just reference different things. For this microformat, i'm not sure if we want to try to solve both problems, or just one? The meta tags in the head element would be the ideal place for information about the THIS.PAGE, but that is not in following with the ideals of microformats where information is human-readable. The THAT.PAGE idea where a list of references is at the end of a document in the form of a bibliography is more inline with the ideals of a microformat where the data is human-readable. That doesn't mean that data about the current document shouldn't be human-readable, so some of the same properties used to reference extermal resources can be used for the current document (THIS.PAGE). To do this a different root item could be used and transforming applications could either extract the citation data about the current page, or information about this page's references.

This is open for discussion, but either way, i believe that the properties used to describe a page will be the same for both THIS and THAT. [http://suda.co.uk/ brian suda]

== Date Formatting ==
Since microformats are all about re-use and the accepted way to encode Date-Time has been pretty much settled, then this is a good place to start when dealing with all the different date citation types.

These are all the different fields from various citation formats that are of temporal nature:
* Date (available | created | dateAccepted | dateCopyrighted | dateSubmitted | issued | modified | valid)
* originInfo/dateIssued
* originInfo/dateCreated
* originInfo/dateCaptured
* originInfo/dateOther
* month
* year
* Copyright Year
* Date - Generic
* Date of Confernce
* Date of Publication
* Date of update/revisou/issuance of database record
* Former Date
* Entry Date for Database Record
* Database Update
* Year of Publication

There are several common properties across several citation domains and will certainly be in the citation microformat, the unique instances will need further consideration, otherwise there could be no end to posiblities.

There are also several properties (year, month, Year of publication) that can be extracted from another source. Therefore, if you only encode a more specific property such as; Date of Publication, you can extract the 'year of publication' from that. Since the date-time format we are modeling after is the ISO date-time format, just the Year portion is an acceptable date. So if you ONLY know the year of publication, the you can form a valid 'Date of Publication' as a microformat (which inturn is a valid 'year of publication') - you milage may vary when it comes to importing into citation applications.

...

It seems to me that these can be collapsed to maybe one or two different date properties. As far as the specific human readable formatting of the date, that can be chosen per whatever the presentation style guide says, and the [[datetime-design-pattern]] used to simplify the markup. - Tantek

== Tags ==
Some of the citation formats has a place for 'keywords' or 'generic tags', etc. This might be a good place to re-use the [http://microformats.org/wiki/rel-tag RelTag microformat]. The downside would be that they are then forced to be links, which might be the correct way to mark-up these terms.

== OpenURL ==
''' THIS BELONGS IN [[cite-formats]], NOT HERE'''

OpenURL is in use in library software around the world to allow citation metadata to be embedded in URLs. Typically these URLs are used for targeting resolvers which essentially proxy access to licensed content. OpenURL also provides an XML encoding. The [http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=ListRecords&metadataPrefix=oai_dc&set=Core:Metadata+Formats key/value] pairs used in OpenURL could relatively easily be adapted to semantic HTML. This is a cow path that could be paved relatively easily using existing modules as appropriate.

OpenURL has a microformat-like encoding: [http://ocoins.info/ COinS]. This uses the 'title' attribute of HTML 'span' tags to embed OpenURL URLs.

Example (from a book review written using the Structured Blogging plugin):

<pre><nowiki>
<p><b>ISBN</b>: <span class='Z3988'
title='ctx_ver=Z39.88-2004&amp;rft_val_fmt=info:ofi/fmt:kev:mtx:book&amp;rft.isbn=0679426612'>
0679426612</span></p>
</nowiki></pre>

== MARC / MODS / Dublin Core ==

The MODS ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgmods.xml example]) and Dublin Core ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgdc.xml example]) transformations of MARC21 may contain some useful ideas.

Here's a first attempt at rewriting the linked examples in XHTML (written in response to a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002438.html mailing list query about encoding book information with microformats]):

<pre><nowiki>
<div class="book" lang="en">
<h3 class="fn">Arithmetic /</h3>
<p>By <span class="creator"><span class="fn">Sandburg, Carl</span>,
<span class="date">1878-1967</span></span>,
and <span class="illustrator">Rand, Ted</span></p>
<p>Publisher: <span class="publisher"><span class="fn">Harcourt Brace Jovanovich</span>,
<span class="locality">San Diego</span></span></p>
<p>Published: <span class="issued">1993</span></p>
<p class="description">A poem about numbers and their characteristics. Features
anamorphic, or distorted, drawings which can be restored to normal by viewing
from a particular angle or by viewing the image's reflection in the provided
Mylar cone.</p>
<p class="note">One Mylar sheet included in pocket.</p>
<p>Subjects:</p>
<ul>
<li class="subject">Arithmetic</li>
<li class="subject">Children's poetry, American.</li>
<li class="subject">Arithmetic</li>
<li class="subject">American poetry</li>
<li class="subject">Visual perception</li>
</ul>
</div>
</nowiki></pre>

use

2006-01-19T03:04:25Z

Tim White: /* So you wanna use microformats? */

= So you wanna use microformats? =

Microformats are designed to be similar to current markup styles. This means that it is quite possible that you won't have to do much work to produce microformats on your site.

For example...

* Do you have events information on your site? Then mark those events up with [[hCalendar]].
** Start with the [http://microformats.org/code/hcalendar/creator hCalendar creator].
* Do you have people and their contact information? Then mark those up with [[hCard]].
** Start with the [http://microformats.org/code/hcard/creator hCard creator] and take a look at the [[hcard-examples]].
* Do you have an explicit copyright license on your content? Then markup the link to your license with [[rel-license|relLicense]].
* Do you have social networking data? Then mark that up with [http://gmpg.org/xfn/ XFN]. Are you tagging things? Then use [[rel-tag|relTag]] or [[xFolk]].
* Are you publishing lists or outlines? Then use [[XOXO]].
* Do you publish reviews? Then use [[hReview]].
** Start with the [http://microformats.org/code/hreview/creator hReview creator].
* Do you publish press releases? Then use [[hatom]].

You see, many common kinds of content can be marked up in microformats. Chances are, you already have some of them on your site. Start with the obvious ones.

And here's a few more tips:

* Try to produce clean, semantic xhtml. Often this will get you very close to microformats on its own.
** [http://tantek.com/log/2004/07.html#classmeaningnotshow Class for meaning not for show]
** http://microformats.org/wiki/SemanticXHTMLDesignPrinciples
** [http://tantek.com/presentations/20040928sdforumws/semantic-xhtml.html Semantic XHTML]
** [http://tantek.com/presentations/2005/03/elementsofxhtml Meaningful XHTML]
** [http://www.tantek.com/presentations/2004etech/realworldsemanticspres.html Real World Semantics]
** ''need more links here'' --[[User:RyanKing|RyanKing]] 14:42, 17 Jan 2006 (PST)

faq

2006-01-19T01:49:46Z

Tim White: /* Basic Microformat Questions */

= Microformats wiki FAQ =

== wiki specific questions ==

Q: ''How do I create a username? Why won't it let me use my preferred username?''

A: First, read this: http://en.wikipedia.org/wiki/Wikipedia:Username . Second, real names are preferred to pseudonyms/handles etc. Real names encourage better transparency and accountability. Third, the most common problem creating a user name is forgetting to caplitalize the first letter of the user name.

== Basic Microformat Questions ==

Q: ''Are microformats dependent upon (X)HTML?''

A: Microformats are made to be embeddable. They can be embedded in (X)HTML, RSS, Atom or anywhere (X)HTML is allowed.

Q: ''Microformats sound great. How can I help?''

A: First of all, take a look at http://microformats.org/discuss to see some ways to join the conversations about microformats.

Q: ''I'd like to make a donation to the microformat cause. How can I do this?''

A: Thank you for your willingness to support microformats. We've only recently started this site and have decided that while we are figuring out exactly how to accept donations, we will be passing along donations to other good causes. Please consider donating to another cause like Red Cross, perhaps directed to help victims of recent natural disasters.

Q: ''Which microformats have been implemented?''

See the [[implementations]] page.

Q: ''Which microformats should I implement?''

A: Chances are you that your website already has data very similar to several microformats. For example, you probably have people and/or their contact information somewhere. That information could be marked up with [[hcard]]. If you are publishing press releases, try using [[hatom]].

Q: ''Do you have any link badges I can add to my website/blog?''

A: Not yet, but we'll post them when we do...

Q. ''Are there any tools that support microformats?''

A. Yes... [[implementations]].

Q. ''What about using new URI schemes instead of class names, e.g. for geo information?''

A. In general, it is more work, and less content-publisher friendly, to ask them to use URI schemes instead of class names.

Authors aren't publishing links to geo information.

They're publishing *visible text* of [[geo]] information.

So the easiest thing to do, for the author, is to leave it as visible text.

Thus, it makes the most sense to do the simple thing of just wrapping that
visible text with a little bit of markup, rather than asking the author to
move (or copy) it into an attribute, which may or may not require a
reformatting of the data as well.

It would make sense from a usability persepective to hyperlink geo information to a maps page or something, so that clicking it actually does something. If you forced them to use a hypothetical "geo:" protocol instead, then that would interfere, since you can only hyperlink something to one destination.

== Class interactions ==

Q. ''Are there issues with page styling when specific class values are used?''

A. There might be. However, any such issues can be easily (trivially) worked around by using contextual selectors.

Q. ''How does the use of class values for semantics interact with the use of class values for attaching CSS styles?''

A. The class attribute takes a space separated set of class names [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 HTML4 reference]. Thus both author and microformat defined class names may be used in the same class attribute. In addition, microformat class names provide the author with a consistent set of class names to use for styling. If the author is already using using specific class names, they can continue to do so, and include microformat class names. If the author is already using a class name that happens to also be a microformat class name, then the author may want to consider using contextual CSS class selectors to make sure that avoid any unintentional styling effects.

See also:
* [http://tantek.com/log/2002/12.html#L20021216 A Touch Of Class]
* [http://tantek.com/log/2004/07.html#classmeaningnotshow Class For Meaning Not For Show]
* [http://www.meyerweb.com/eric/thoughts/2004/07/18/competent-classing Competant Classing], by Eric Meyer for discussion of choosing class names in (X)HTML
* [http://www.microformats.org/blog/2005/10/19/more-than-styling/ Class attributes are about more than styling] - Ryan King dispells common misconceptions about the ''HTML'' class attribute.

== <code><div></code> and <code><span></code> semantics ==

Q. Is it semantically meaningless to use divs?

A. Yes, both <code><div></code> and <code><span></code> have nearly no semantics. <code><div></code> can be used to represent a "division" of the page content. Similarly <code><span></code> can be used to reperesent that that "span" of text has some meaning, but the specifics of what that meaning is undefined by the <code><span></code>.

Q. Does the use of <code><div></code> and <code><span></code> elements add any semantics to web pages?

A. According to the [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.4 spec], <code><div></code> and <code><span></code> "offer a generic mechanism for adding structure to documents." Their only meaning is in dividing documents into sections, and as such, their presence implies that the content within has a specific, but undefined by the element markup, semantic. Thus they are nearly semantic-free.

== Class semantics ==

Q. ''Do (X)HTML class names have semantics?''

A. The HTML4 specification does not define any particular class values [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 REF], nor does it define any particular semantic for class values [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 REF], except that they "may be used for general user agent processing" [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 REF]. However, the [http://www.w3.org/TR/WD-htmllink-970328#profile" draft of "Hypertext Links in HTML"], allows for a "profile" to define meanings for those classes. [http://gmpg.org/xmdp/ XMDP] is a format for defining meta data profiles for (X)HTML, and thus an XMDP profile can be used to define the meanings of class names.

See also:
* [http://tantek.com/log/2002/12.html#L20021216 A Touch Of Class]
* [http://www.w3.org/TR/WD-htmllink-970328 Hypertext Links in HTML]

== Microformats and Spam ==

Q. Given that Google now looks at hidden content as potential spam, will microformats be considered spam?

A. Microformats aren't meant to disguise semantics -- only provide a mechanism for marking up the content you intend to make visible on a page, typically no more and no less. Where we embed semantic equivalents in the tags themselves (i.e. GMT times in abbr tags for times), it doesn't seem logic that such data could be considered spam.

citations in the wild

2006-01-13T01:19:02Z

Tim White:

(For a cleaner version, see [http://www.tjameswhite.com/citation-examples.htm])

== ABC-CLIO Product [http://www.abc-clio.com/products/overview.aspx?productid=109327 detail page] ==
<table border="0" cellpadding="0" cellspacing="0" width="430">
<tr>
<td width="101" valign="top" align="left"></td>
<td width="102" valign="top" align="left"></td>
<td width="101" valign="top" align="left"></td>
<td width="125" valign="top" align="center"></td>
</tr>
<tr>
<td width="430" colspan="4" class="productsubtitle"><span id="serieslbl" class="productsubtitle"><a href="browseseries.aspx?seriesid=33">Teaching With Documents Series</a></span></td>
</tr>
<tr>
<td width="430" colspan="4" class="producttitle"><span id="title" class="producttitle">The 1920's</span></td>
</tr>
<tr>
<td width="430" colspan="4" class="productsubtitle"><span id="subtitle" class="productsubtitle"></span></td>
</tr>
<tr>
<td width="430" colspan="4" class="productauthor"><span id="credit" class="productauthor"></span></td>
</tr>
<tr>
<td width="430" colspan="4" height="12"><img border="0" src="../images/blank-white.gif" width="1" height="12" alt=""/></td>
</tr>
<tr>
<td width="130" align="left"><img id="productImage" src="../images/dbimages/1011\101103.GIF" alt="" style="border-width:0px;width:115px;" /></td>
<td width="300" valign="top" align="right" colspan="3">
<table border="0" cellpadding="0" cellspacing="0" width="290">
<tr>
<td width="110" class="productdetailhead"><span id="pubdatelabel" class="productdetailhead">Publication Date</span></td>
<td width="180" class="productdetailbody"><span id="pubdate" class="productdetailbody">11/2001</span></td>
</tr>
<tr>
<td width="110" class="productdetailhead"><span id="pageslabel" class="productdetailhead">Pages</span></td>
<td width="180" class="productdetailbody"><span id="pages" class="productdetailbody">132</span></td>
</tr>
<tr>
<td width="110" class="productdetailhead"><span id="volumeslabel" class="productdetailhead">Volumes</span></td>
<td width="180" class="productdetailbody"><span id="volumes" class="productdetailbody">1</span></td>
</tr>
<tr>
<td width="110" class="productdetailhead"><span id="trimlabel" class="productdetailhead">Size</span></td>
<td width="180" class="productdetailbody"><span id="trimsize" class="productdetailbody">8.5x11</span></td>
</tr>
</table>


<table id="PriceTable" cellspacing="0" cellpadding="0" width="290" border="0">
<tr>
<td class="productdetailhead" width="290" height="15" colspan="4"><img src="../images/academic/blank-blue.gif" id="PriceLine" width="290" height="1" border="0" /></td>
</tr>
<tr>
<td class="productdetailhead" width="54">Format</td>
<td class="productdetailhead" width="68">Price</td>
<td class="productdetailhead" width="88"><span id="ISBNLabel">ISBN</span></td>
<td class="productdetailhead" width="80"> </td>
</tr>
<tr>
<td class="productdetailhead"><b>Print</b></td>
<td class="productdetailbody">$39.00</td>
<td class="productdetailbody">1-57607-785-3</td>
<td class="productdetailhead"> </td>
</tr>
</table>

</td>
</tr>
</table>
</div>

== Greenwood Press [http://www.greenwood.com/ home page] featured book ==
<div class="title"> <a href="/books/BookDetail.asp?sku=GR2847">The Greenwood Encyclopedia of World Folklore and Folklife</a> </div>
<div class="img_box"> <a href="/books/BookDetail.asp?sku=GR2847"> <img src="/_net.templates/showImage.aspx?imgName=0313328471.jpg&s=140" alt="The Greenwood Encyclopedia of World Folklore and Folklife" border="0" /></a> </div>
<div class="sub_title">Four Volumes</div>
<div class="author">William M. Clements</div>
<div class="isbn">0-313-32847-1</div>
<div class="price">$449.95 <span class="pipe">|</span> £255.00</div>

<div class="bookDescription"> China . . . Malta . . . Madagascar . . . Wales . . . and Texas: these are among the many exotic, distant lands that capture our minds and imaginations. In an era of increasing globalization, students, general readers, and business professionals need to know about... <a href="/books/BookDetail.asp?sku=GR2847">Read more</a> </div>
</div>

== Greenwood Press [http://www.greenwood.com/catalog/GR2847.aspx Product detail page] ==
<div id="pnlContent" class="pnlContent">
<div id="pnlFlyerBox" class="flyerBox"> <a id="hlFlyer" class="flyerLink" href="/books/printFlyer.aspx?sku=GR2847" target="_blank">Print book flyer</a> <br />
<a id="hlFlyerInternational" class="international_flyer" href="/books/printFlyer.aspx?sku=GR2847&location=international" target="_blank">(International version)</a> </div>
<span id="lblTitle" class="book_headline block">The Greenwood Encyclopedia of World Folklore and Folklife</span> <span id="lblSubTitle" class="book_subline">Four Volumes</span>
<div id="pnlBookDetails" class="detailsBox">
<div id="pnlImgBox" class="imgBox"> <img src="/_net.templates/showImage.aspx?imgName=0313328471.jpg&s=135" alt="" border="0" /> </div>
<a id="hlAddToCart" title="Add this item to your shopping cart" href="/shopping_cart/?sku=GR2847"><img title="Add this item to your shopping cart" src="/_net.templates/roundedButton.aspx?ButtonText=Add to Cart" alt="" border="0" /></a> <a id="hlAddToWishList" title="Save this item to your wish list" href="/wish_list/?sku=GR2847"><img title="Save this item to your wish list" src="/_net.templates/roundedButton.aspx?ButtonText=Add to Wish List" alt="" border="0" /></a> <a id="hlSharePage" title="Email this page to a friend" href="/books/sendform.asp?sku=GR2847" target="_blank"><img title="Email this page to a friend" src="/_net.templates/roundedButton.aspx?ButtonText=Email" alt="" border="0" /></a> <a id="hlPrintPage" title="Version of this page optimized for printing" href="/catalog/GR2847.aspx?print=1" target="_blank"><img title="Version of this page optimized for printing" src="/_net.templates/roundedButton.aspx?ButtonText=Print" alt="" border="0" /></a> <a id="hlWorldCat" href="http://worldcatlibraries.org/wcpa/isbn/0313328471" style="FLOAT: right"><img src="/images/world_catalog.gif" alt="" border="0" /></a>
<div class="authors"><span><a href="/catalog/author/C/229.aspx">William M. Clements</a> (ed.)</span></div>
<span id="lblAuthorsNote" class="block"></span>
<div><span class="book_options">Book Code:</span> <span id="lblBookCode">GR2847</span></div>
<div id="pnlIsbn"> <span class="book_options">ISBN:</span> <span id="lblIsbn">0-313-32847-1</span> </div>
<div id="pnlPageColation"> 1972 pages, maps; photos </div>
<span id="lblImprint" class="block">Greenwood Press</span>
<div id="pnlPubDate"> <span class="book_options">Publication Date:</span> <span id="lblPubDate">12/30/2005</span> </div>
<div id="pnlListPrice"> <span class="book_options">List Price:</span> <span id="lblListPrice">$449.95</span> (<a href="/contactus/order_info.asp?SectionID=about&Location=order_info#UKEME" title="Click for international ordering information">UK Sterling Price: £255.00</a>) </div>
<div id="pnlAvailability"> <span class="book_options">Availability:</span> <span id="lblAvailability">In Stock</span> </div>
<div id="pnlMediaType"> <span class="book_options">Media Type:</span> <span id="lblMediaType">Hardcover</span> </div>
<div class="clearing"></div>
</div>
<div id="pnlBookInformation"> <span class="book_options">Subjects:</span>
<ul class="toc">
<li> <a id="rpCategories__ctl1_hlCategory" href="/catalog/subject/Anthropology.aspx">Anthropology</a> » <a id="rpCategories__ctl1_hlSubCategory" href="/catalog/subject/Anthropology/Folklore.aspx">Folklore</a> </li>
<li> <a id="rpCategories__ctl2_hlCategory" href="/catalog/subject/Anthropology.aspx">Anthropology</a> » <a id="rpCategories__ctl2_hlSubCategory" href="/catalog/subject/Anthropology/Anthropology%2b(General).aspx">Anthropology (General)</a> </li>
<li> <a id="rpCategories__ctl3_hlCategory" href="/catalog/subject/Anthropology.aspx">Anthropology</a> » <a id="rpCategories__ctl3_hlSubCategory" href="/catalog/subject/Anthropology/Cultural%2bAnthropology.aspx">Cultural Anthropology</a> </li>
<li> <a id="rpCategories__ctl4_hlCategory" href="/catalog/subject/History.aspx">History</a> » <a id="rpCategories__ctl4_hlSubCategory" href="/catalog/subject/History/World%2bHistory%2b(General).aspx">World History (General)</a> </li>
</ul>
<div id="pnlDescription"> <span class="book_options">Description:</span> <span id="lblDescription1" class="description block">China . . . Malta . . . Madagascar . . . Wales . . . and Texas: these are among the many exotic, distant lands that capture our minds and imaginations. In an era of increasing globalization, students, general readers, and business professionals need to know about the world and its varied ways. So too, a knowledge of world cultures is fundamental to an understanding of America's ethnically rich society. Folklore isn't just about the long ago and far away. It's about the here and now, and there's no better way to learn about cultural diversity than to study the folklore and folkways of different ethnic groups. <br />
More than just Cinderella and other fairy tales, folklore encompasses the whole realm of traditional beliefs and activities that define a culture. The most comprehensive work of its kind, this massive encyclopedia engagingly and authoritatively surveys folklife and traditions from around the world. Through its vast scope and lengthy entries, it transcends other references on particular national or regional folklores and is the most ambitious undertaking of its type. Organized in four volumes, the encyclopedia provides convenient access to information about folklore generally and to the traditions of particular regions:<br />
Volume 1: Topics and Themes, Africa, Australia and Oceania<br />
Volume 2: Southeast Asia and India, Central and East Asia, Middle East<br />
Volume 3: Europe<br />
Volume 4: North and South America</span> <span id="lblDescription2" class="description block">Along with the expertise of the contributors, of Volume Editor William M. Clements, and of Advisory Editor Thomas A. Green, the encyclopedia draws upon a distinguished board of internationally recognized scholars, including:<br />
<li> Roger D. Abrahams<br />
</li>
<li> Cristina Bacchilega<br />
</li>
<li> Gillian Bennett<br />
</li>
<li> Mary Ellen Brown<br />
</li>
<li> James R. Dow<br />
</li>
<li> Alessandro Falassi<br />
</li>
<li> Barbro Klein<br />
</li>
<li> Peter Knecht<br />
</li>
<li> Natalie Kononenko<br />
</li>
<li> Frances M. Malpezzi<br />
</li>
<li> Margaret Mills<br />
</li>
<li> M. D. Muthukumaraswamy<br />
</li>
<li> Gerald Pocius<br />
</li>
<li> And John S. Ryan.<br />
<br />
<b>Features:</b><br />
</li>
<li> Brings together the knowledge of more than 200 specialists from around the world.<br />
</li>
<li> Provides 39 extended entries on topics central to world folklore.<br />
</li>
<li> Details the folklore and folkways of roughly 170 cultural groups.<br />
</li>
<li> Entries discuss the background, beliefs, oral and theatrical traditions, arts and crafts, and contemporary concerns of each cultural group.<br />
</li>
<li> Each entry cites numerous works for further reading.<br />
</li>
<li> A generous selection of maps and illustrations makes world folklore come to life.<br />
</li>
<li> A list of entries and a cumulative subject index, repeated in each volume, offer convenient access to the vast body of information contained in the encyclopedia.<br />
</li>
<li> A selected, general bibliography directs students and general readers to the most important broad studies of world folklore.<br />
</li>
<li> A glossary defines key terms, theories, and concepts.<br />
<br />
<b>Benefits:</b><br />
</li>
<li> Helps students learn about cultures, customs, and daily life around the world.<br />
</li>
<li> Fosters respect and appreciation for the many ethnic traditions behind contemporary American culture.<br />
</li>
<li> Provides valuable background information for the study of world religions, holidays, and festivals.<br />
</li>
<li> Offers a valuable context for understanding world history, politics, literature, and the arts.<br />
</li>
<li> Invites students to compare and contrast the values and experiences of different cultures.<br />
</li>
<li> Fosters critical reading skills and serves as a model for student research.<br />
<br />
<b>Volume 1: Topics and Themes, Africa, Australia and Oceania</b><br />
Certain themes and topics are central to world foklore. The thematic essays in this volume discuss such matters as:<br />
</li>
<li> Antiquarianism<br />
</li>
<li> Cultural Evolution<br />
</li>
<li> Ethnopoetics<br />
</li>
<li> Gender<br />
</li>
<li> Invented Tradition<br />
</li>
<li> Nativism<br />
</li>
<li> Primitivism<br />
</li>
<li> Public Folklore<br />
</li>
<li> Race<br />
</li>
<li> Trickster<br />
</li>
<li> And many more.<br />
<br />
<b>Volume 2: Southeast Asia and India, Central and East Asia, Middle East</b><br />
Included in this volume are entries on such cultural groups and regions as:<br />
</li>
<li> Bali<br />
</li>
<li> China<br />
</li>
<li> Duna<br />
</li>
<li> Iban<br />
</li>
<li> Kazakh<br />
</li>
<li> Mongol<br />
</li>
<li> Orissa<br />
</li>
<li> Palestine<br />
</li>
<li> Tonga<br />
</li>
<li> Uyghur<br />
</li>
<li> And many others.<br />
<br />
<b>Volume 3: Europe</b><br />
Included in this volume are entries on the folklore of such cultural regions and groups as:<br />
</li>
<li> Ashkenazim<br />
</li>
<li> Basque<br />
</li>
<li> Brittany<br />
</li>
<li> Flanders<br />
</li>
<li> Germany<br />
</li>
<li> Isle of Man<br />
</li>
<li> Roma<br />
</li>
<li> Russia<br />
</li>
<li> Sami<br />
</li>
<li> Ukraine<br />
</li>
<li> And many more.<br />
<br />
<b>Volume 4: North and South America</b><br />
The entries in this volume explore the folk traditions of such regions and groups as:<br />
</li>
<li> Appalachia<br />
</li>
<li> Choctaw<br />
</li>
<li> Haiti<br />
</li>
<li> Island Carib<br />
</li>
<li> Maya<br />
</li>
<li> Quechua<br />
</li>
<li> Seminole<br />
</li>
<li> Western Inuit and Yupik<br />
</li>
<li> Xavante<br />
</li>
<li> Yanomami<br />
</li>
<li> And many more.<br />
<br />
Because folklore is the essence of daily life, this encyclopedia addresses the curriculum needs of high school students and is also an indispensable resource for teachers. In addition, anyone researching folklore in a public library will find this the first place to look for detailed information about cultural traditions around the world.</li>
</span> </div>
<div id="pnlLCCardNumber" class="description"> <span class="book_options">LC Card Number:</span> <span id="lblLCCardNumber">2005019219</span> </div>
<div id="pnlLCCClass" class="description"> <span class="book_options">LCC Class:</span> <span id="lblLCCClass">GR35 </span> </div>
<div id="pnlDeweyClass" class="description"> <span class="book_options">Dewey Class:</span> <span id="lblDeweyClass">398</span> </div>
</div>
</div>
</div>

== Marshall Cavendish [http://www.marshallcavendish.com/marshallcavendish/academic/redirector.xml?url=/marshallcavendish/academic/catalogue/books/regionalism_n_regional_security/9812102108.xml product page] ==
<table cellpadding="2" width="100%">
<tr valign="top">
<td><font id="title_catalogue_font"><b>Regionalism & Regional Security</b></font></td>
</tr>
</table>
<font id="text">
<div style="" align="">
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">ISBN Number</font></td>
<td width="65%"><font id="text">9812102108</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Series</font></td>
<td width="65%"><font id="text">null</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Title</font></td>
<td width="65%"><font id="text">The New Terrorism: Anatomy, Trends and Counter-strategies</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Imprint</font></td>
<td width="65%"><font id="text">Eastern Universities Press</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Specifications</font></td>
<td width="65%"><font id="text">152 mm X 227 mm, 368 pp, limp with flaps, 500 gms</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Authors</font></td>
<td width="65%"><font id="text">Andrew Tan & Kumar Ramakrishna (eds)</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Target Audience</font></td>
<td width="65%"><font id="text">University lecturers/researchers, undergraduate students, academicians and those interested in Regional Security Studies.</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Price (SG)</font></td>
<td width="65%"><font id="text">S$ 39.00</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Price (US)</font></td>
<td width="65%"><font id="text">US$ 30.00</font>   <a href="javascript: addToCart()"><img src="/marshallcavendish/components/db_content/MC_AC_redirector/pic/addCart.gif" border="0"/></a></td>
</tr>
</table>
<br/>
<br/>
The terrorist attacks of September 11, 2001 on the World Trade Centre in New York and the Pentagon in Washington represented a true watershed in world history.<br/>
<br/>
The attacks revealed the horrifying nature of the so-called "new terrorism" that has emerged in the post-Cold War era. The new terrorism is defined by four key features:</div>
</font>
<ul>
<li>
<p align="justify"><font id="text">sheer lethality</font></p>
</li>
<li>
<p align="justify"><font id="text">religious dimension</font></p>
</li>
<li>
<p align="justify"><font id="text">networked organizational structure</font></p>
</li>
<li>
<p align="justify"><font id="text">greatly enhanced striking power   </font></p>
</li>
</ul>
<font id="text">
<div style="" align="">As September 11 clearly demonstrated, the new terrorists can leverage on technology to inflict catastrophic damage even on superpowers, let alone other states.<br/>
<br/>
To examine the new dimensions of terrorism, a conference was organized in Singapore in late March 2002 that brought together a number of leading experts from a wide range of backgrounds from America, Europe and Asia, and the key findings are presented in this volume under the following headings:</div>
</font>
<ul>
<li>
<p align="justify"><font id="text">Anatomy of the new terrorism</font></p>
</li>
<li>
<p align="justify"><font id="text">Terrorist trends and patterns in the Asia-Pacific region</font></p>
</li>
<li>
<p align="justify"><font id="text">Religion and terrorism: Southeast Asian perspectives</font></p>
</li>
<li>
<p align="justify"><font id="text">Formulating counter-strategies   </font></p>
</li>
</ul>
<font id="text">
<div style="" align=""> <span style="font-weight: bold;"> <b> About the Author: </b> </span> <br/>
Both Andrew Tan and Kumar Ramakrishna are Assistant Professors at the Institute of Defence and Strategic Studies, Nanyang Technological University, Singapore.<br/>
Andrew Tan received his M.Phil from Cambridge and PhD from the University of Sydney. His research interests are conflict (inter-state tensions, insurgencies, terrorism and force modernization) in Southeast Asia, and security issues in Asia.<br/>
Kumar Ramakrishna obtained his PhD in History from the University of London in 1999. He teaches and writes on the history of strategic thought as well as the war on terror.</div>
</font>
<td width="18.666662" style="valign: top; background-color: white ; " rowspan="1" colspan="1"><br/>
</td>
<tr valign="top">
<td width="570.666524" style="valign: top; background-color: white ; " rowspan="1" colspan="1"><br/>
</td>
<td width="18.666662" style="valign: top; background-color: white ; " rowspan="1" colspan="1"><br/>
</td>
</tr>
</div>

== Oxford University Press (USA) [http://www.us.oup.com/us/?view=usa homepage] ==
<div class="isbnSummaryDetails">
<h2> <a href="/us/catalog/general/subject/HistoryAmerican/ColonialRevolutionary/?view=usa&ci=0195162471">The Glorious Cause</a> </h2>
<div class="subTitle"> The American Revolution, 1763-1789 </div>
<div class="edition"> Revised and Expanded Edition </div>
<div class="byline"> Robert Middlekauff </div>
<span class="isbnNumber">0195162471</span>, <span class="format">hardback</span>, <span class="publicationDate"> Feb 2005 </span> <span class="price"> $37.50 </span> <span class="description"> The classic history of the American Revolution--now in an updated and expanded twentieth anniversary edition </span>
<div class="related">
<h3>More </h3>

<a href="/us/catalog/general/subject/HistoryAmerican/?view=usa&sf=all">History, American</a> > <a href="/us/catalog/general/subject/HistoryAmerican/ColonialRevolutionary/?view=usa&sf=all">Colonial & Revolutionary</a> </div>
</div>

</div>

== Oxford University Press (USA) [http://www.us.oup.com/us/catalog/general/subject/HistoryAmerican/ColonialRevolutionary/?view=usa&ci=0195162471#Product_Details Product page]==
<div class="isbnProperties isbnSummary">
<div class="isbnSummaryHeading">
<h1>The Glorious Cause</h1>
<div class="subTitle"> The American Revolution, 1763-1789 </div>
<div class="edition"> Revised and Expanded Edition </div>
<div class="byline"> Robert Middlekauff </div>
</div>

<div class="cover"> <span class="bookShot"><a href="#"><img src="/images/covers/0195162471.jpg"
width="63" alt="bookshot" /> </a></span> <span class="addToCart"><a href="http://www.us.oup.com/us/cart/cart.jsp?op=a&i=0195162471&c=85&q=1&r=http%3A%2F%2Fwww.us.oup.com%2Fus%2Fcatalog%2Fgeneral%2Fsubject%2FHistoryAmerican%2FColonialRevolutionary%2F%3Fview%3Dusa%26ci%3D0195162471">Add to Cart</a></span> </div>

<div class="isbnSummaryDetails"> <span class="isbnNumber">0195162471</span>, <span class="format">hardback</span>, <span class="pages"> 760 pages </span>
<div id="generalinfo"> <span class="publicationDate">Feb 2005, </span> <span class="availability"> In Stock </span> </div>
<div class="cost">
<h2>Price:</h2>
$37.50 <span class="discountCode">(02)</span> </div>
<div class="shipping"> <a href="/us/assets/shippingInfo.jsp?si=1.5&so=3.75&sc=0&isi=5&iso=5&isc=0" target="_blank" onclick="window.open(this.href, this.target, 'height=445,width=445,scrollbars');
return false;">Shipping Details</a> </div>
<div class="moreSeries redArrow">
<h3>See more from the series</h3>
<ul>
<li><a href="/us/catalog/general/series/OxfordHistoryoftheUnitedStates/?view=usa">Oxford History of the United States, Vol. 3</a></li>
</ul>
</div>

</div>

</div>
</div>

== Thomson Gale product detail page ==

<div id =" title_main">

<h2>Contemporary Literary Criticism</h2>

<div id =" credits">
<ul>
<li><h2>Excerpts from Criticism of the Works of Today's Novelists, Poets, Playwrights, Short Story Writers, Scriptwriters, & Other Creative Writers</h2>
Volume 1</li>

<li><i>Published by Thomson Gale</i></li>
</ul>
</div>

<div id =" description">
<p>Each print volume in this long-standing series profiles approximately 6-8 novelists, poets, playwrights and other creative writers by providing full-text or excerpted criticism taken from books, magazines, literary reviews, newspapers and scholarly journals. Among those profiled in this volume are:</p>
<ul>
<li>Kingsley Amis
<li>John Dos Passos
<li>Hermann Hesse
<li>Ezra Pound
</ul>
</div>

<div id =" detail">
<ul>
<li>Published/Released:<strong> March 1973</strong></li>
<li>ISBN: <strong>0-8103-0100-8</strong></li>
<li>Product number: <strong>001415</strong></li>
<li>Page count: <strong>485 pp./vol.</strong></li>
<li>Shipping Weight: <strong>5.00 lbs (2.27 kgs)</strong></li>
</ul>
</div> 

<div id =" price">
<P>Price: US $205.00</p>
</div>

</div>
</div>

citation-examples

2006-01-13T01:17:00Z

Tim White: /* Book titles: */

= Example Citation Formats =
The following examples are real world examples that been pulled from places around the web. Please add to this list. The idea is that we get a solid sample of examples and see what commonalities there are amonst them and try to build this microformat so that it can meet 80% of all the possible properties.

== Citation Mark Up in the Wild ==
Mark up examples from reference publisher's websites (online catalogs), including ABC-CLIO, Greenwood Press, Marshall Cavendish, Oxford University Press (USA) and Thomson Gale. Examples are broken down and organized by element.

View complete [[citations in the wild]].

=== Book titles: ===

<span id="title" class="producttitle">The 1920's</span>
(ABC-CLIO product detail page)

<div class="title"> <a href="...">The Greenwood Encyclopedia of World Folklore and Folklife</a> </div>
(Greenwood Press homepage)

<span id="lblTitle" class="book_headline block">The Greenwood Encyclopedia of World Folklore and Folklife</span>
(Greenwood Press product detail page)

<td width="35%"><font id="title_catalogue_title_font">Title</font></td>
<td width="65%"><font id="text">The New Terrorism: Anatomy, Trends and Counter-strategies</font></td>
(Marshall Cavendish product detail page)

<h2> <a href="...">The Glorious Cause</a> </h2>
(Oxford Univ. Press, homepage)

<h1>The Glorious Cause</h1>
(OUP, product detail page)

<h2>Contemporary Literary Criticism</h2>
(Thomson Gale, product detail page)

<span id="ctlBookDetailHeader_lblTitle" class="ProdTitle">Talk and Interaction in Social Research Methods</span> (SAGE Publications)

Also, many examples where books presented in table format with Title as cell header, or presented "Title: "

=== Book Series Name: ===

<span id="serieslbl" class="productsubtitle"><a href="...">Teaching With Documents Series</a></span>
(ABC-CLIO)

=== Sub-title: ===

<span id="subtitle" class="productsubtitle"></span>
(ABC-CLIO)

<div class="sub_title">[Four Volumes]</div>
(Greenwood, homepage)

<span id="lblSubTitle" class="book_subline">[Four Volumes]</span>
(Greenwood, product page)

<div class="subTitle"> The American Revolution, 1763-1789 </div>
(OUP)

=== Author: ===

<span id="credit" class="productauthor"></span>
(ABC-CLIO)

<div class="author">William M. Clements</div>
(Greenwood)

<td width="35%"><font id="title_catalogue_title_font">Authors</font></td>
<td width="65%"><font id="text">Andrew Tan & Kumar Ramakrishna (eds)</font></td>
(Marshall Cavendish)

<div class="byline"> Robert Middlekauff </div>
(OUP)

=== Publication Date: ===

<span id="pubdate" class="productdetailbody">11/2001</span>
(ABC-CLIO -- see table structure)

<div id="pnlPubDate"> <span class="book_options">Publication Date:</span> <span id="lblPubDate">12/30/2005</span> </div>
(Greenwood, detail page)

<span class="publicationDate"> Feb 2005 </span>
(OUP)

<li>Published/Released:<strong> March 1973</strong></li>
(Thomson Gale)

=== Volumes: ===

<td width="110" class="productdetailhead"><span id="volumeslabel" class="productdetailhead">Volumes</span></td>
<td width="180" class="productdetailbody"><span id="volumes" class="productdetailbody">1</span></td>
(ABC-CLIO)

=== ISBN: ===

<td class="productdetailhead" width="88"><span id="ISBNLabel">ISBN</span></td>
<td class="productdetailbody">1-57607-785-3</td>
(ABC-CLIO)

<div class="isbn">0-313-32847-1</div>
(Greenwood, homepage)

<div id="pnlIsbn"> <span class="book_options">ISBN:</span> <span id="lblIsbn">0-313-32847-1</span> </div>
(Greenwood, product page)

<td width="35%"><font id="title_catalogue_title_font">ISBN Number</font></td>
<td width="65%"><font id="text">9812102108</font></td>
(Marshall Cavendish)

<span class="isbnNumber">0195162471</span>
(OUP)

<li>ISBN: <strong>0-8103-0100-8</strong></li>
(Thomson Gale)

=== Book Edition: ===

<div class="edition"> Revised and Expanded Edition </div>
(OUP)

Added by [[User:Tim White|Tim]]

== RFC vCard Example ==
<pre><nowiki>
9. References

[ISO 8601] ISO 8601:1988 - Data elements and interchange formats -
Information interchange - Representation of dates and
times - The International Organization for
Standardization, June, 1988.

[ISO 8601 TC] ISO 8601, Technical Corrigendum 1 - Data elements and
interchange formats - Information interchange -
Representation of dates and times - The International
Organization for Standardization, May, 1991.

[ISO 9070] ISO 9070, Information Processing - SGML support
facilities - Registration Procedures for Public Text
Owner Identifiers, April, 1991.

[CCITT E.163] Recommendation E.163 - Numbering Plan for The
International Telephone Service, CCITT Blue Book,
Fascicle II.2, pp. 128-134, November, 1988.

[CCITT X.121] Recommendation X.121 - International Numbering Plan for
Public Data Networks, CCITT Blue Book, Fascicle VIII.3,
pp. 317-332, November, 1988.

[CCITT X.520] Recommendation X.520 - The Directory - Selected
Attribute Types, November 1988.

[CCITT X.521] Recommendation X.521 - The Directory - Selected Object
Classes, November 1988.

[MIME-DIR] Howes, T., Smith, M., and F. Dawson, "A MIME Content-
Type for Directory Information", RFC 2425, September
1998.

[RFC 1738] Berners-Lee, T., Masinter, L., and M. McCahill,
"Uniform Resource Locators (URL)", RFC 1738, December
1994.

[RFC 1766] Alvestrand, H., "Tags for the Identification of
Languages", RFC 1766, March 1995.

[RFC 1872] Levinson, E., "The MIME Multipart/Related Content-
type", RFC 1872, December 1995.

[RFC 2045] Freed, N., and N. Borenstein, "Multipurpose Internet
Mail Extensions (MIME) - Part One: Format of Internet
Message Bodies", RFC 2045, November 1996.

[RFC 2046] Freed, N., and N. Borenstein, "Multipurpose Internet
Mail Extensions (MIME) - Part Two: Media Types", RFC
2046, November 1996.

[RFC 2047] Moore, K., "Multipurpose Internet Mail Extensions
(MIME) - Part Three: Message Header Extensions for
Non-ASCII Text", RFC 2047, November 1996.

[RFC 2048] Freed, N., Klensin, J., and J. Postel, "Multipurpose
Internet Mail Extensions (MIME) - Part Four:
Registration Procedures", RFC 2048, January 1997.

[RFC 2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.

[RFC 2234] Crocker, D., and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997.

[UNICODE] "The Unicode Standard - Version 2.0", The Unicode
Consortium, July 1996.

[VCARD] Internet Mail Consortium, "vCard - The Electronic
Business Card Version 2.1",
http://www.imc.org/pdi/vcard-21.txt, September 18,
1996.
</nowiki></pre>
[http://www.faqs.org/rfcs/rfc2426.html vCard RFC]

== W3C XHTML Spec Example ==
<pre><nowiki>
<h1><a name="refs" id="refs">E.</a> References</h1>

<p><strong>This appendix is informative.</strong></p>

<dl>
<dt><a name="ref-css2" id="ref-css2"><strong>[CSS2]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/1998/REC-CSS2-19980512">Cascading Style Sheets, level 2 (CSS2) Specification</a></cite>", B. Bos, H. W. Lie, C. Lilley, I. Jacobs, 12 May 1998.<br />
<a href="http://www.w3.org/TR/REC-CSS2">Latest version</a> available at: http://www.w3.org/TR/REC-CSS2</dd>

<dt><a name="ref-dom" id="ref-dom"><strong>[DOM]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001">Document Object Model (DOM) Level 1 Specification</a></cite>", Lauren Wood <em lang="lt" xml:lang="lt">et al.</em>, 1 October
1998.<br />
<a href="http://www.w3.org/TR/REC-DOM-Level-1">Latest version</a> available at: http://www.w3.org/TR/REC-DOM-Level-1</dd>

<dt><a name="ref-dom2" id="ref-dom2"><strong>[DOM2]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113">Document Object Model (DOM) Level 2 Core Specification</a></cite>", A. Le Hors, <em lang="lt" xml:lang="lt">et
al.</em>, 13 November 2000.<br />
<a href="http://www.w3.org/TR/DOM-Level-2-Core">Latest version</a> available at: http://www.w3.org/TR/DOM-Level-2-Core</dd>

<dt><a name="ref-html4" id="ref-html4"><strong>[HTML]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/1999/REC-html401-19991224">HTML 4.01 Specification</a></cite>", D. Raggett, A. Le Hors, I. Jacobs, 24 December 1999.<br />
<a href="http://www.w3.org/TR/html401">Latest version</a> available at: http://www.w3.org/TR/html401</dd>

<dt><a name="ref-posix.1" id="ref-posix.1"><strong>[POSIX.1]</strong></a></dt>

<dd>"<cite>ISO/IEC 9945-1:1990 Information Technology - Portable Operating System Interface (POSIX) - Part 1: System Application Program Interface (API) [C Language]</cite>", Institute of Electrical
and Electronics Engineers, Inc, 1990.</dd>

<dt><a id="ref-rfc2045" name="ref-rfc2045"><strong>[RFC2045]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2045.txt">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a></cite>", N. Freed and N. Borenstein, November
1996. Note that this RFC obsoletes RFC1521, RFC1522, and RFC1590.</dd>

<dt><a name="ref-rfc2046" id="ref-rfc2046"><strong>[RFC2046]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2046.txt">RFC2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a></cite>", N. Freed and N. Borenstein, November 1996.<br />
Available at <a href="http://www.ietf.org/rfc/rfc2046.txt">http://www.ietf.org/rfc/rfc2046.txt</a>. Note that this RFC obsoletes RFC1521, RFC1522, and RFC1590.</dd>

<dt><a name="ref-rfc2119" id="ref-rfc2119"><strong>[RFC2119]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2119.txt">RFC2119: Key words for use in RFCs to Indicate Requirement Levels</a></cite>", S. Bradner, March 1997.<br />
Available at: http://www.ietf.org/rfc/rfc2119.txt</dd>

<dt><a name="ref-rfc2376" id="ref-rfc2376"><strong>[RFC2376]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2376.txt">RFC2376: XML Media Types</a></cite>", E. Whitehead, M. Murata, July 1998.<br />
This document is obsoleted by [<a href="#ref-rfc3023">RFC3023</a>].<br />
Available at: http://www.ietf.org/rfc/rfc2376.txt</dd>

<dt><a name="ref-rfc2396" id="ref-rfc2396"><strong>[RFC2396]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2396.txt">RFC2396: Uniform Resource Identifiers (URI): Generic Syntax</a></cite>", T. Berners-Lee, R. Fielding, L. Masinter, August 1998.<br />
This document updates RFC1738 and RFC1808.<br />
Available at: http://www.ietf.org/rfc/rfc2396.txt</dd>

<dt><a name="ref-rfc2854" id="ref-rfc2854"><strong>[RFC2854]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2854.txt">RFC2854: The text/html Media Type</a></cite>", D. Conolly, L. Masinter, June 2000.<br />
Available at: http://www.ietf.org/rfc/rfc2854.txt</dd>

<dt><a name="ref-rfc3023" id="ref-rfc3023"><strong>[RFC3023]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc3023.txt">RFC3023: XML Media Types</a></cite>", M. Murata, S. St.Laurent, D. Kohn, January 2001.<br />
This document obsoletes [<a href="#ref-rfc2376">RFC2376</a>].<br />
Available at: http://www.ietf.org/rfc/rfc3023.txt</dd>

<dt><a id="ref-rfc3066" name="ref-rfc3066"><strong>[RFC3066]</strong></a></dt>

<dd>"<a href="http://www.ietf.org/rfc/rfc3066.txt">Tags for the Identification of Languages</a>", H. Alvestrand, January 2001.<br />
Available at: http://www.ietf.org/rfc/rfc3066.txt</dd>

<dt><a id="ref-rfc3236" name="ref-rfc3236"><strong>[RFC3236]</strong></a></dt>

<dd>"<a href="http://www.ietf.org/rfc/rfc3236.txt">The 'application/xhtml+xml' Media Type</a>", M. Baker, P. Stark, January 2002.<br />
Available at: http://www.ietf.org/rfc/rfc3236.txt</dd>

<dt><a id="ref-xhtml-mathml" name="ref-xhtml-mathml"><strong>[XHTML+MathML]</strong></a></dt>

<dd><cite>"<a href="http://www.w3.org/TR/MathML2/dtd/xhtml-math11-f.dtd">XHTML plus Math 1.1 <abbr title="Document Type Definition">DTD</abbr></a></cite>", "A.2 MathML as a DTD Module", Mathematical
Markup Language (MathML) Version 2.0. Available at: http://www.w3.org/TR/MathML2/dtd/xhtml-math11-f.dtd</dd>

<dt><a id="ref-xhtmlmime" name="ref-xhtmlmime"><strong>[XHTMLMIME]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/2002/NOTE-xhtml-media-types-20020801">XHTML Media Types</a></cite>", Masayasu Ishikawa, 1 August 2002.<br />
<a href="http://www.w3.org/TR/xhtml-media-types">Latest version</a> available at: http://www.w3.org/TR/xhtml-media-types</dd>

<dt><a id="ref-xhtmlmod" name="ref-xhtmlmod"><strong>[XHTMLMOD]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410">Modularization of XHTML</a></cite>", M. Altheim et al., 10 April 2001.<br />
<a href="http://www.w3.org/TR/xhtml-modularization">Latest version</a> available at: http://www.w3.org/TR/xhtml-modularization</dd>

<dt><a name="ref-xml" id="ref-xml"><strong>[XML]</strong></a></dt>

<dd>"<a href="http://www.w3.org/TR/2000/REC-xml-20001006">Extensible Markup Language (XML) 1.0 Specification (Second Edition)</a>", T. Bray, J. Paoli, C. M. Sperberg-McQueen, E. Maler, 6 October
2000.<br />
<a href="http://www.w3.org/TR/REC-xml">Latest version</a> available at: http://www.w3.org/TR/REC-xml</dd>

<dt><a name="ref-xmlns" id="ref-xmlns"><strong>[XMLNS]</strong></a></dt>

<dd>"<a href="http://www.w3.org/TR/1999/REC-xml-names-19990114">Namespaces in XML</a>", T. Bray, D. Hollander, A. Layman, 14 January 1999.<br />
XML namespaces provide a simple method for qualifying names used in XML documents by associating them with namespaces identified by URI.<br />
<a href="http://www.w3.org/TR/REC-xml-names">Latest version</a> available at: http://www.w3.org/TR/REC-xml-names</dd>

<dt><a name="ref-xmlc14n" id="ref-xmlc14n"><strong>[XMLC14N]</strong></a></dt>

<dd>"<a href="http://www.w3.org/TR/2001/REC-xml-c14n-20010315">Canonical XML Version 1.0</a>", J. Boyer, 15 March 2001.<br />
This document describes a method for generating a physical representation, the canonical form, of an XML document.<br />
<a href="http://www.w3.org/TR/xml-c14n">Latest version</a> available at: http://www.w3.org/TR/xml-c14n</dd>
</dl>
</nowiki></pre>
[http://www.w3.org/TR/xhtml1/#refs XHTML1.0 Spec references]

== CiteProc XHTML Output ==

The XHTML output for CiteProc[http://xbiblio.sourceforge.net/citeproc.html] wasn't designed per se as a microformat, but is probably not a bad place to start. It is desgined to handle a wide range of content. Here is the APA output:

<pre><nowiki>
<div id="bibliography">

<h3>References</h3>

<p id="Brenner2000a" class="bibref">
<span class="creator">Brenner, N.</span>
<span class="date"> (<span class="year">2000</span>) </span>
<span class="title">The Urban Question as a Scale Question: Reflections
on Henri Lefebre, Urban Theory and the Politics of Scale, </span>
<span class="container">
<span class="title" style="font-style: italic">International Journal of
Urban and Regional Research, </span>
<span class="volume">24</span>
<span class="issue">(2)</span>
<span class="locator">, pp. 361–78</span>
</span>.
</p>

<p id="NW2000-0207" class="bibref">
<span class="creator">Newsweek</span>
<span class="date">
(<span class="year">2000a</span>
<span class="month">, February</span>
<span class="day"> 7</span>)
</span>
<span class="title">The Grandmas Pay a Visit, </span>
<span class="container">
<span class="volume">135</span>
<span class="issue">(6)</span>
<span class="locator">, pp. 45</span>
</span>.
</p>

<p id="Veer1996a" class="bibref">
<span class="creator">van der Veer, P.</span>
<span class="date"><span class="year"> (1996) </span></span>
<span class="title">Riots and Rituals: The Construction of Violence
and Public Space in Hindu Nationalism</span>
<span class="container">, In Brass, P.<span class="role"> (Ed.)</span>.
<span class="title" style="font-style: italic">Riots and Pogroms.</span>
<span class="origin"><span class="place">New York</span>
<span class="publisher">: NYU Press</span></span>
<span class="locator">, pp. 154–76</span>
</span>.
</p>
</div>
</nowiki></pre>

= Styles =
This does NOT define a format, but instead shows how the format should be displayed. This is something out of the direct scope of this project. CSS styles will handle the look-and-feel of the text, and the author can put it in any order they choose. These links are mentioned for two reasons, one is informative, the other is so we know atleast meet the minimum properties that are used in the styles.

* [http://www.liu.edu/cwis/cwp/library/workshop/citmla.htm MLA Style]
* [http://www.bu.edu/library/guides/citation.html Chicago, MLA, and APA styles]
* [http://www.legalbluebook.com/ Blue Book] for legal citations
* [http://www.columbia.edu/cu/cup/cgos/idx_basic.html Columbia University Citation Style] developed for modern internet citations

citation-examples

2006-01-03T00:00:59Z

Tim White: /* Citation Mark Up in the Wild */

= Example Citation Formats =
The following examples are real world examples that been pulled from places around the web. Please add to this list. The idea is that we get a solid sample of examples and see what commonalities there are amonst them and try to build this microformat so that it can meet 80% of all the possible properties.

== Citation Mark Up in the Wild ==
Mark up examples from reference publisher's websites (online catalogs), including ABC-CLIO, Greenwood Press, Marshall Cavendish, Oxford University Press (USA) and Thomson Gale. Examples are broken down and organized by element.

View complete [[citations in the wild]].

=== Book titles: ===

<span id="title" class="producttitle">The 1920's</span>
(ABC-CLIO product detail page)

<div class="title"> <a href="...">The Greenwood Encyclopedia of World Folklore and Folklife</a> </div>
(Greenwood Press homepage)

<span id="lblTitle" class="book_headline block">The Greenwood Encyclopedia of World Folklore and Folklife</span>
(Greenwood Press product detail page)

<td width="35%"><font id="title_catalogue_title_font">Title</font></td>
<td width="65%"><font id="text">The New Terrorism: Anatomy, Trends and Counter-strategies</font></td>
(Marshall Cavendish product detail page)

<h2> <a href="...">The Glorious Cause</a> </h2>
(Oxford Univ. Press, homepage)

<h1>The Glorious Cause</h1>
(OUP, product detail page)

<h2>Contemporary Literary Criticism</h2>
(Thomson Gale, product detail page)

=== Book Series Name: ===

<span id="serieslbl" class="productsubtitle"><a href="...">Teaching With Documents Series</a></span>
(ABC-CLIO)

=== Sub-title: ===

<span id="subtitle" class="productsubtitle"></span>
(ABC-CLIO)

<div class="sub_title">[Four Volumes]</div>
(Greenwood, homepage)

<span id="lblSubTitle" class="book_subline">[Four Volumes]</span>
(Greenwood, product page)

<div class="subTitle"> The American Revolution, 1763-1789 </div>
(OUP)

=== Author: ===

<span id="credit" class="productauthor"></span>
(ABC-CLIO)

<div class="author">William M. Clements</div>
(Greenwood)

<td width="35%"><font id="title_catalogue_title_font">Authors</font></td>
<td width="65%"><font id="text">Andrew Tan & Kumar Ramakrishna (eds)</font></td>
(Marshall Cavendish)

<div class="byline"> Robert Middlekauff </div>
(OUP)

=== Publication Date: ===

<span id="pubdate" class="productdetailbody">11/2001</span>
(ABC-CLIO -- see table structure)

<div id="pnlPubDate"> <span class="book_options">Publication Date:</span> <span id="lblPubDate">12/30/2005</span> </div>
(Greenwood, detail page)

<span class="publicationDate"> Feb 2005 </span>
(OUP)

<li>Published/Released:<strong> March 1973</strong></li>
(Thomson Gale)

=== Volumes: ===

<td width="110" class="productdetailhead"><span id="volumeslabel" class="productdetailhead">Volumes</span></td>
<td width="180" class="productdetailbody"><span id="volumes" class="productdetailbody">1</span></td>
(ABC-CLIO)

=== ISBN: ===

<td class="productdetailhead" width="88"><span id="ISBNLabel">ISBN</span></td>
<td class="productdetailbody">1-57607-785-3</td>
(ABC-CLIO)

<div class="isbn">0-313-32847-1</div>
(Greenwood, homepage)

<div id="pnlIsbn"> <span class="book_options">ISBN:</span> <span id="lblIsbn">0-313-32847-1</span> </div>
(Greenwood, product page)

<td width="35%"><font id="title_catalogue_title_font">ISBN Number</font></td>
<td width="65%"><font id="text">9812102108</font></td>
(Marshall Cavendish)

<span class="isbnNumber">0195162471</span>
(OUP)

<li>ISBN: <strong>0-8103-0100-8</strong></li>
(Thomson Gale)

=== Book Edition: ===

<div class="edition"> Revised and Expanded Edition </div>
(OUP)

Added by [[User:Tim White|Tim]]

== RFC vCard Example ==
<pre><nowiki>
9. References

[ISO 8601] ISO 8601:1988 - Data elements and interchange formats -
Information interchange - Representation of dates and
times - The International Organization for
Standardization, June, 1988.

[ISO 8601 TC] ISO 8601, Technical Corrigendum 1 - Data elements and
interchange formats - Information interchange -
Representation of dates and times - The International
Organization for Standardization, May, 1991.

[ISO 9070] ISO 9070, Information Processing - SGML support
facilities - Registration Procedures for Public Text
Owner Identifiers, April, 1991.

[CCITT E.163] Recommendation E.163 - Numbering Plan for The
International Telephone Service, CCITT Blue Book,
Fascicle II.2, pp. 128-134, November, 1988.

[CCITT X.121] Recommendation X.121 - International Numbering Plan for
Public Data Networks, CCITT Blue Book, Fascicle VIII.3,
pp. 317-332, November, 1988.

[CCITT X.520] Recommendation X.520 - The Directory - Selected
Attribute Types, November 1988.

[CCITT X.521] Recommendation X.521 - The Directory - Selected Object
Classes, November 1988.

[MIME-DIR] Howes, T., Smith, M., and F. Dawson, "A MIME Content-
Type for Directory Information", RFC 2425, September
1998.

[RFC 1738] Berners-Lee, T., Masinter, L., and M. McCahill,
"Uniform Resource Locators (URL)", RFC 1738, December
1994.

[RFC 1766] Alvestrand, H., "Tags for the Identification of
Languages", RFC 1766, March 1995.

[RFC 1872] Levinson, E., "The MIME Multipart/Related Content-
type", RFC 1872, December 1995.

[RFC 2045] Freed, N., and N. Borenstein, "Multipurpose Internet
Mail Extensions (MIME) - Part One: Format of Internet
Message Bodies", RFC 2045, November 1996.

[RFC 2046] Freed, N., and N. Borenstein, "Multipurpose Internet
Mail Extensions (MIME) - Part Two: Media Types", RFC
2046, November 1996.

[RFC 2047] Moore, K., "Multipurpose Internet Mail Extensions
(MIME) - Part Three: Message Header Extensions for
Non-ASCII Text", RFC 2047, November 1996.

[RFC 2048] Freed, N., Klensin, J., and J. Postel, "Multipurpose
Internet Mail Extensions (MIME) - Part Four:
Registration Procedures", RFC 2048, January 1997.

[RFC 2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.

[RFC 2234] Crocker, D., and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997.

[UNICODE] "The Unicode Standard - Version 2.0", The Unicode
Consortium, July 1996.

[VCARD] Internet Mail Consortium, "vCard - The Electronic
Business Card Version 2.1",
http://www.imc.org/pdi/vcard-21.txt, September 18,
1996.
</nowiki></pre>
[http://www.faqs.org/rfcs/rfc2426.html vCard RFC]

== W3C XHTML Spec Example ==
<pre><nowiki>
<h1><a name="refs" id="refs">E.</a> References</h1>

<p><strong>This appendix is informative.</strong></p>

<dl>
<dt><a name="ref-css2" id="ref-css2"><strong>[CSS2]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/1998/REC-CSS2-19980512">Cascading Style Sheets, level 2 (CSS2) Specification</a></cite>", B. Bos, H. W. Lie, C. Lilley, I. Jacobs, 12 May 1998.<br />
<a href="http://www.w3.org/TR/REC-CSS2">Latest version</a> available at: http://www.w3.org/TR/REC-CSS2</dd>

<dt><a name="ref-dom" id="ref-dom"><strong>[DOM]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001">Document Object Model (DOM) Level 1 Specification</a></cite>", Lauren Wood <em lang="lt" xml:lang="lt">et al.</em>, 1 October
1998.<br />
<a href="http://www.w3.org/TR/REC-DOM-Level-1">Latest version</a> available at: http://www.w3.org/TR/REC-DOM-Level-1</dd>

<dt><a name="ref-dom2" id="ref-dom2"><strong>[DOM2]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113">Document Object Model (DOM) Level 2 Core Specification</a></cite>", A. Le Hors, <em lang="lt" xml:lang="lt">et
al.</em>, 13 November 2000.<br />
<a href="http://www.w3.org/TR/DOM-Level-2-Core">Latest version</a> available at: http://www.w3.org/TR/DOM-Level-2-Core</dd>

<dt><a name="ref-html4" id="ref-html4"><strong>[HTML]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/1999/REC-html401-19991224">HTML 4.01 Specification</a></cite>", D. Raggett, A. Le Hors, I. Jacobs, 24 December 1999.<br />
<a href="http://www.w3.org/TR/html401">Latest version</a> available at: http://www.w3.org/TR/html401</dd>

<dt><a name="ref-posix.1" id="ref-posix.1"><strong>[POSIX.1]</strong></a></dt>

<dd>"<cite>ISO/IEC 9945-1:1990 Information Technology - Portable Operating System Interface (POSIX) - Part 1: System Application Program Interface (API) [C Language]</cite>", Institute of Electrical
and Electronics Engineers, Inc, 1990.</dd>

<dt><a id="ref-rfc2045" name="ref-rfc2045"><strong>[RFC2045]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2045.txt">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a></cite>", N. Freed and N. Borenstein, November
1996. Note that this RFC obsoletes RFC1521, RFC1522, and RFC1590.</dd>

<dt><a name="ref-rfc2046" id="ref-rfc2046"><strong>[RFC2046]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2046.txt">RFC2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a></cite>", N. Freed and N. Borenstein, November 1996.<br />
Available at <a href="http://www.ietf.org/rfc/rfc2046.txt">http://www.ietf.org/rfc/rfc2046.txt</a>. Note that this RFC obsoletes RFC1521, RFC1522, and RFC1590.</dd>

<dt><a name="ref-rfc2119" id="ref-rfc2119"><strong>[RFC2119]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2119.txt">RFC2119: Key words for use in RFCs to Indicate Requirement Levels</a></cite>", S. Bradner, March 1997.<br />
Available at: http://www.ietf.org/rfc/rfc2119.txt</dd>

<dt><a name="ref-rfc2376" id="ref-rfc2376"><strong>[RFC2376]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2376.txt">RFC2376: XML Media Types</a></cite>", E. Whitehead, M. Murata, July 1998.<br />
This document is obsoleted by [<a href="#ref-rfc3023">RFC3023</a>].<br />
Available at: http://www.ietf.org/rfc/rfc2376.txt</dd>

<dt><a name="ref-rfc2396" id="ref-rfc2396"><strong>[RFC2396]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2396.txt">RFC2396: Uniform Resource Identifiers (URI): Generic Syntax</a></cite>", T. Berners-Lee, R. Fielding, L. Masinter, August 1998.<br />
This document updates RFC1738 and RFC1808.<br />
Available at: http://www.ietf.org/rfc/rfc2396.txt</dd>

<dt><a name="ref-rfc2854" id="ref-rfc2854"><strong>[RFC2854]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2854.txt">RFC2854: The text/html Media Type</a></cite>", D. Conolly, L. Masinter, June 2000.<br />
Available at: http://www.ietf.org/rfc/rfc2854.txt</dd>

<dt><a name="ref-rfc3023" id="ref-rfc3023"><strong>[RFC3023]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc3023.txt">RFC3023: XML Media Types</a></cite>", M. Murata, S. St.Laurent, D. Kohn, January 2001.<br />
This document obsoletes [<a href="#ref-rfc2376">RFC2376</a>].<br />
Available at: http://www.ietf.org/rfc/rfc3023.txt</dd>

<dt><a id="ref-rfc3066" name="ref-rfc3066"><strong>[RFC3066]</strong></a></dt>

<dd>"<a href="http://www.ietf.org/rfc/rfc3066.txt">Tags for the Identification of Languages</a>", H. Alvestrand, January 2001.<br />
Available at: http://www.ietf.org/rfc/rfc3066.txt</dd>

<dt><a id="ref-rfc3236" name="ref-rfc3236"><strong>[RFC3236]</strong></a></dt>

<dd>"<a href="http://www.ietf.org/rfc/rfc3236.txt">The 'application/xhtml+xml' Media Type</a>", M. Baker, P. Stark, January 2002.<br />
Available at: http://www.ietf.org/rfc/rfc3236.txt</dd>

<dt><a id="ref-xhtml-mathml" name="ref-xhtml-mathml"><strong>[XHTML+MathML]</strong></a></dt>

<dd><cite>"<a href="http://www.w3.org/TR/MathML2/dtd/xhtml-math11-f.dtd">XHTML plus Math 1.1 <abbr title="Document Type Definition">DTD</abbr></a></cite>", "A.2 MathML as a DTD Module", Mathematical
Markup Language (MathML) Version 2.0. Available at: http://www.w3.org/TR/MathML2/dtd/xhtml-math11-f.dtd</dd>

<dt><a id="ref-xhtmlmime" name="ref-xhtmlmime"><strong>[XHTMLMIME]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/2002/NOTE-xhtml-media-types-20020801">XHTML Media Types</a></cite>", Masayasu Ishikawa, 1 August 2002.<br />
<a href="http://www.w3.org/TR/xhtml-media-types">Latest version</a> available at: http://www.w3.org/TR/xhtml-media-types</dd>

<dt><a id="ref-xhtmlmod" name="ref-xhtmlmod"><strong>[XHTMLMOD]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410">Modularization of XHTML</a></cite>", M. Altheim et al., 10 April 2001.<br />
<a href="http://www.w3.org/TR/xhtml-modularization">Latest version</a> available at: http://www.w3.org/TR/xhtml-modularization</dd>

<dt><a name="ref-xml" id="ref-xml"><strong>[XML]</strong></a></dt>

<dd>"<a href="http://www.w3.org/TR/2000/REC-xml-20001006">Extensible Markup Language (XML) 1.0 Specification (Second Edition)</a>", T. Bray, J. Paoli, C. M. Sperberg-McQueen, E. Maler, 6 October
2000.<br />
<a href="http://www.w3.org/TR/REC-xml">Latest version</a> available at: http://www.w3.org/TR/REC-xml</dd>

<dt><a name="ref-xmlns" id="ref-xmlns"><strong>[XMLNS]</strong></a></dt>

<dd>"<a href="http://www.w3.org/TR/1999/REC-xml-names-19990114">Namespaces in XML</a>", T. Bray, D. Hollander, A. Layman, 14 January 1999.<br />
XML namespaces provide a simple method for qualifying names used in XML documents by associating them with namespaces identified by URI.<br />
<a href="http://www.w3.org/TR/REC-xml-names">Latest version</a> available at: http://www.w3.org/TR/REC-xml-names</dd>

<dt><a name="ref-xmlc14n" id="ref-xmlc14n"><strong>[XMLC14N]</strong></a></dt>

<dd>"<a href="http://www.w3.org/TR/2001/REC-xml-c14n-20010315">Canonical XML Version 1.0</a>", J. Boyer, 15 March 2001.<br />
This document describes a method for generating a physical representation, the canonical form, of an XML document.<br />
<a href="http://www.w3.org/TR/xml-c14n">Latest version</a> available at: http://www.w3.org/TR/xml-c14n</dd>
</dl>
</nowiki></pre>
[http://www.w3.org/TR/xhtml1/#refs XHTML1.0 Spec references]

== CiteProc XHTML Output ==

The XHTML output for CiteProc[http://xbiblio.sourceforge.net/citeproc.html] wasn't designed per se as a microformat, but is probably not a bad place to start. It is desgined to handle a wide range of content. Here is the APA output:

<pre><nowiki>
<div id="bibliography">

<h3>References</h3>

<p id="Brenner2000a" class="bibref">
<span class="creator">Brenner, N.</span>
<span class="date"> (<span class="year">2000</span>) </span>
<span class="title">The Urban Question as a Scale Question: Reflections
on Henri Lefebre, Urban Theory and the Politics of Scale, </span>
<span class="container">
<span class="title" style="font-style: italic">International Journal of
Urban and Regional Research, </span>
<span class="volume">24</span>
<span class="issue">(2)</span>
<span class="locator">, pp. 361–78</span>
</span>.
</p>

<p id="NW2000-0207" class="bibref">
<span class="creator">Newsweek</span>
<span class="date">
(<span class="year">2000a</span>
<span class="month">, February</span>
<span class="day"> 7</span>)
</span>
<span class="title">The Grandmas Pay a Visit, </span>
<span class="container">
<span class="volume">135</span>
<span class="issue">(6)</span>
<span class="locator">, pp. 45</span>
</span>.
</p>

<p id="Veer1996a" class="bibref">
<span class="creator">van der Veer, P.</span>
<span class="date"><span class="year"> (1996) </span></span>
<span class="title">Riots and Rituals: The Construction of Violence
and Public Space in Hindu Nationalism</span>
<span class="container">, In Brass, P.<span class="role"> (Ed.)</span>.
<span class="title" style="font-style: italic">Riots and Pogroms.</span>
<span class="origin"><span class="place">New York</span>
<span class="publisher">: NYU Press</span></span>
<span class="locator">, pp. 154–76</span>
</span>.
</p>
</div>
</nowiki></pre>

= Styles =
This does NOT define a format, but instead shows how the format should be displayed. This is something out of the direct scope of this project. CSS styles will handle the look-and-feel of the text, and the author can put it in any order they choose. These links are mentioned for two reasons, one is informative, the other is so we know atleast meet the minimum properties that are used in the styles.

* [http://www.liu.edu/cwis/cwp/library/workshop/citmla.htm MLA Style]
* [http://www.bu.edu/library/guides/citation.html Chicago, MLA, and APA styles]
* [http://www.legalbluebook.com/ Blue Book] for legal citations
* [http://www.columbia.edu/cu/cup/cgos/idx_basic.html Columbia University Citation Style] developed for modern internet citations

citations in the wild

2005-12-28T22:35:43Z

Tim White:

== ABC-CLIO Product [http://www.abc-clio.com/products/overview.aspx?productid=109327 detail page] ==
<table border="0" cellpadding="0" cellspacing="0" width="430">
<tr>
<td width="101" valign="top" align="left"></td>
<td width="102" valign="top" align="left"></td>
<td width="101" valign="top" align="left"></td>
<td width="125" valign="top" align="center"></td>
</tr>
<tr>
<td width="430" colspan="4" class="productsubtitle"><span id="serieslbl" class="productsubtitle"><a href="browseseries.aspx?seriesid=33">Teaching With Documents Series</a></span></td>
</tr>
<tr>
<td width="430" colspan="4" class="producttitle"><span id="title" class="producttitle">The 1920's</span></td>
</tr>
<tr>
<td width="430" colspan="4" class="productsubtitle"><span id="subtitle" class="productsubtitle"></span></td>
</tr>
<tr>
<td width="430" colspan="4" class="productauthor"><span id="credit" class="productauthor"></span></td>
</tr>
<tr>
<td width="430" colspan="4" height="12"><img border="0" src="../images/blank-white.gif" width="1" height="12" alt=""/></td>
</tr>
<tr>
<td width="130" align="left"><img id="productImage" src="../images/dbimages/1011\101103.GIF" alt="" style="border-width:0px;width:115px;" /></td>
<td width="300" valign="top" align="right" colspan="3">
<table border="0" cellpadding="0" cellspacing="0" width="290">
<tr>
<td width="110" class="productdetailhead"><span id="pubdatelabel" class="productdetailhead">Publication Date</span></td>
<td width="180" class="productdetailbody"><span id="pubdate" class="productdetailbody">11/2001</span></td>
</tr>
<tr>
<td width="110" class="productdetailhead"><span id="pageslabel" class="productdetailhead">Pages</span></td>
<td width="180" class="productdetailbody"><span id="pages" class="productdetailbody">132</span></td>
</tr>
<tr>
<td width="110" class="productdetailhead"><span id="volumeslabel" class="productdetailhead">Volumes</span></td>
<td width="180" class="productdetailbody"><span id="volumes" class="productdetailbody">1</span></td>
</tr>
<tr>
<td width="110" class="productdetailhead"><span id="trimlabel" class="productdetailhead">Size</span></td>
<td width="180" class="productdetailbody"><span id="trimsize" class="productdetailbody">8.5x11</span></td>
</tr>
</table>


<table id="PriceTable" cellspacing="0" cellpadding="0" width="290" border="0">
<tr>
<td class="productdetailhead" width="290" height="15" colspan="4"><img src="../images/academic/blank-blue.gif" id="PriceLine" width="290" height="1" border="0" /></td>
</tr>
<tr>
<td class="productdetailhead" width="54">Format</td>
<td class="productdetailhead" width="68">Price</td>
<td class="productdetailhead" width="88"><span id="ISBNLabel">ISBN</span></td>
<td class="productdetailhead" width="80"> </td>
</tr>
<tr>
<td class="productdetailhead"><b>Print</b></td>
<td class="productdetailbody">$39.00</td>
<td class="productdetailbody">1-57607-785-3</td>
<td class="productdetailhead"> </td>
</tr>
</table>

</td>
</tr>
</table>
</div>

== Greenwood Press [http://www.greenwood.com/ home page] featured book ==
<div class="title"> <a href="/books/BookDetail.asp?sku=GR2847">The Greenwood Encyclopedia of World Folklore and Folklife</a> </div>
<div class="img_box"> <a href="/books/BookDetail.asp?sku=GR2847"> <img src="/_net.templates/showImage.aspx?imgName=0313328471.jpg&s=140" alt="The Greenwood Encyclopedia of World Folklore and Folklife" border="0" /></a> </div>
<div class="sub_title">Four Volumes</div>
<div class="author">William M. Clements</div>
<div class="isbn">0-313-32847-1</div>
<div class="price">$449.95 <span class="pipe">|</span> £255.00</div>

<div class="bookDescription"> China . . . Malta . . . Madagascar . . . Wales . . . and Texas: these are among the many exotic, distant lands that capture our minds and imaginations. In an era of increasing globalization, students, general readers, and business professionals need to know about... <a href="/books/BookDetail.asp?sku=GR2847">Read more</a> </div>
</div>

== Greenwood Press [http://www.greenwood.com/catalog/GR2847.aspx Product detail page] ==
<div id="pnlContent" class="pnlContent">
<div id="pnlFlyerBox" class="flyerBox"> <a id="hlFlyer" class="flyerLink" href="/books/printFlyer.aspx?sku=GR2847" target="_blank">Print book flyer</a> <br />
<a id="hlFlyerInternational" class="international_flyer" href="/books/printFlyer.aspx?sku=GR2847&location=international" target="_blank">(International version)</a> </div>
<span id="lblTitle" class="book_headline block">The Greenwood Encyclopedia of World Folklore and Folklife</span> <span id="lblSubTitle" class="book_subline">Four Volumes</span>
<div id="pnlBookDetails" class="detailsBox">
<div id="pnlImgBox" class="imgBox"> <img src="/_net.templates/showImage.aspx?imgName=0313328471.jpg&s=135" alt="" border="0" /> </div>
<a id="hlAddToCart" title="Add this item to your shopping cart" href="/shopping_cart/?sku=GR2847"><img title="Add this item to your shopping cart" src="/_net.templates/roundedButton.aspx?ButtonText=Add to Cart" alt="" border="0" /></a> <a id="hlAddToWishList" title="Save this item to your wish list" href="/wish_list/?sku=GR2847"><img title="Save this item to your wish list" src="/_net.templates/roundedButton.aspx?ButtonText=Add to Wish List" alt="" border="0" /></a> <a id="hlSharePage" title="Email this page to a friend" href="/books/sendform.asp?sku=GR2847" target="_blank"><img title="Email this page to a friend" src="/_net.templates/roundedButton.aspx?ButtonText=Email" alt="" border="0" /></a> <a id="hlPrintPage" title="Version of this page optimized for printing" href="/catalog/GR2847.aspx?print=1" target="_blank"><img title="Version of this page optimized for printing" src="/_net.templates/roundedButton.aspx?ButtonText=Print" alt="" border="0" /></a> <a id="hlWorldCat" href="http://worldcatlibraries.org/wcpa/isbn/0313328471" style="FLOAT: right"><img src="/images/world_catalog.gif" alt="" border="0" /></a>
<div class="authors"><span><a href="/catalog/author/C/229.aspx">William M. Clements</a> (ed.)</span></div>
<span id="lblAuthorsNote" class="block"></span>
<div><span class="book_options">Book Code:</span> <span id="lblBookCode">GR2847</span></div>
<div id="pnlIsbn"> <span class="book_options">ISBN:</span> <span id="lblIsbn">0-313-32847-1</span> </div>
<div id="pnlPageColation"> 1972 pages, maps; photos </div>
<span id="lblImprint" class="block">Greenwood Press</span>
<div id="pnlPubDate"> <span class="book_options">Publication Date:</span> <span id="lblPubDate">12/30/2005</span> </div>
<div id="pnlListPrice"> <span class="book_options">List Price:</span> <span id="lblListPrice">$449.95</span> (<a href="/contactus/order_info.asp?SectionID=about&Location=order_info#UKEME" title="Click for international ordering information">UK Sterling Price: £255.00</a>) </div>
<div id="pnlAvailability"> <span class="book_options">Availability:</span> <span id="lblAvailability">In Stock</span> </div>
<div id="pnlMediaType"> <span class="book_options">Media Type:</span> <span id="lblMediaType">Hardcover</span> </div>
<div class="clearing"></div>
</div>
<div id="pnlBookInformation"> <span class="book_options">Subjects:</span>
<ul class="toc">
<li> <a id="rpCategories__ctl1_hlCategory" href="/catalog/subject/Anthropology.aspx">Anthropology</a> » <a id="rpCategories__ctl1_hlSubCategory" href="/catalog/subject/Anthropology/Folklore.aspx">Folklore</a> </li>
<li> <a id="rpCategories__ctl2_hlCategory" href="/catalog/subject/Anthropology.aspx">Anthropology</a> » <a id="rpCategories__ctl2_hlSubCategory" href="/catalog/subject/Anthropology/Anthropology%2b(General).aspx">Anthropology (General)</a> </li>
<li> <a id="rpCategories__ctl3_hlCategory" href="/catalog/subject/Anthropology.aspx">Anthropology</a> » <a id="rpCategories__ctl3_hlSubCategory" href="/catalog/subject/Anthropology/Cultural%2bAnthropology.aspx">Cultural Anthropology</a> </li>
<li> <a id="rpCategories__ctl4_hlCategory" href="/catalog/subject/History.aspx">History</a> » <a id="rpCategories__ctl4_hlSubCategory" href="/catalog/subject/History/World%2bHistory%2b(General).aspx">World History (General)</a> </li>
</ul>
<div id="pnlDescription"> <span class="book_options">Description:</span> <span id="lblDescription1" class="description block">China . . . Malta . . . Madagascar . . . Wales . . . and Texas: these are among the many exotic, distant lands that capture our minds and imaginations. In an era of increasing globalization, students, general readers, and business professionals need to know about the world and its varied ways. So too, a knowledge of world cultures is fundamental to an understanding of America's ethnically rich society. Folklore isn't just about the long ago and far away. It's about the here and now, and there's no better way to learn about cultural diversity than to study the folklore and folkways of different ethnic groups. <br />
More than just Cinderella and other fairy tales, folklore encompasses the whole realm of traditional beliefs and activities that define a culture. The most comprehensive work of its kind, this massive encyclopedia engagingly and authoritatively surveys folklife and traditions from around the world. Through its vast scope and lengthy entries, it transcends other references on particular national or regional folklores and is the most ambitious undertaking of its type. Organized in four volumes, the encyclopedia provides convenient access to information about folklore generally and to the traditions of particular regions:<br />
Volume 1: Topics and Themes, Africa, Australia and Oceania<br />
Volume 2: Southeast Asia and India, Central and East Asia, Middle East<br />
Volume 3: Europe<br />
Volume 4: North and South America</span> <span id="lblDescription2" class="description block">Along with the expertise of the contributors, of Volume Editor William M. Clements, and of Advisory Editor Thomas A. Green, the encyclopedia draws upon a distinguished board of internationally recognized scholars, including:<br />
<li> Roger D. Abrahams<br />
</li>
<li> Cristina Bacchilega<br />
</li>
<li> Gillian Bennett<br />
</li>
<li> Mary Ellen Brown<br />
</li>
<li> James R. Dow<br />
</li>
<li> Alessandro Falassi<br />
</li>
<li> Barbro Klein<br />
</li>
<li> Peter Knecht<br />
</li>
<li> Natalie Kononenko<br />
</li>
<li> Frances M. Malpezzi<br />
</li>
<li> Margaret Mills<br />
</li>
<li> M. D. Muthukumaraswamy<br />
</li>
<li> Gerald Pocius<br />
</li>
<li> And John S. Ryan.<br />
<br />
<b>Features:</b><br />
</li>
<li> Brings together the knowledge of more than 200 specialists from around the world.<br />
</li>
<li> Provides 39 extended entries on topics central to world folklore.<br />
</li>
<li> Details the folklore and folkways of roughly 170 cultural groups.<br />
</li>
<li> Entries discuss the background, beliefs, oral and theatrical traditions, arts and crafts, and contemporary concerns of each cultural group.<br />
</li>
<li> Each entry cites numerous works for further reading.<br />
</li>
<li> A generous selection of maps and illustrations makes world folklore come to life.<br />
</li>
<li> A list of entries and a cumulative subject index, repeated in each volume, offer convenient access to the vast body of information contained in the encyclopedia.<br />
</li>
<li> A selected, general bibliography directs students and general readers to the most important broad studies of world folklore.<br />
</li>
<li> A glossary defines key terms, theories, and concepts.<br />
<br />
<b>Benefits:</b><br />
</li>
<li> Helps students learn about cultures, customs, and daily life around the world.<br />
</li>
<li> Fosters respect and appreciation for the many ethnic traditions behind contemporary American culture.<br />
</li>
<li> Provides valuable background information for the study of world religions, holidays, and festivals.<br />
</li>
<li> Offers a valuable context for understanding world history, politics, literature, and the arts.<br />
</li>
<li> Invites students to compare and contrast the values and experiences of different cultures.<br />
</li>
<li> Fosters critical reading skills and serves as a model for student research.<br />
<br />
<b>Volume 1: Topics and Themes, Africa, Australia and Oceania</b><br />
Certain themes and topics are central to world foklore. The thematic essays in this volume discuss such matters as:<br />
</li>
<li> Antiquarianism<br />
</li>
<li> Cultural Evolution<br />
</li>
<li> Ethnopoetics<br />
</li>
<li> Gender<br />
</li>
<li> Invented Tradition<br />
</li>
<li> Nativism<br />
</li>
<li> Primitivism<br />
</li>
<li> Public Folklore<br />
</li>
<li> Race<br />
</li>
<li> Trickster<br />
</li>
<li> And many more.<br />
<br />
<b>Volume 2: Southeast Asia and India, Central and East Asia, Middle East</b><br />
Included in this volume are entries on such cultural groups and regions as:<br />
</li>
<li> Bali<br />
</li>
<li> China<br />
</li>
<li> Duna<br />
</li>
<li> Iban<br />
</li>
<li> Kazakh<br />
</li>
<li> Mongol<br />
</li>
<li> Orissa<br />
</li>
<li> Palestine<br />
</li>
<li> Tonga<br />
</li>
<li> Uyghur<br />
</li>
<li> And many others.<br />
<br />
<b>Volume 3: Europe</b><br />
Included in this volume are entries on the folklore of such cultural regions and groups as:<br />
</li>
<li> Ashkenazim<br />
</li>
<li> Basque<br />
</li>
<li> Brittany<br />
</li>
<li> Flanders<br />
</li>
<li> Germany<br />
</li>
<li> Isle of Man<br />
</li>
<li> Roma<br />
</li>
<li> Russia<br />
</li>
<li> Sami<br />
</li>
<li> Ukraine<br />
</li>
<li> And many more.<br />
<br />
<b>Volume 4: North and South America</b><br />
The entries in this volume explore the folk traditions of such regions and groups as:<br />
</li>
<li> Appalachia<br />
</li>
<li> Choctaw<br />
</li>
<li> Haiti<br />
</li>
<li> Island Carib<br />
</li>
<li> Maya<br />
</li>
<li> Quechua<br />
</li>
<li> Seminole<br />
</li>
<li> Western Inuit and Yupik<br />
</li>
<li> Xavante<br />
</li>
<li> Yanomami<br />
</li>
<li> And many more.<br />
<br />
Because folklore is the essence of daily life, this encyclopedia addresses the curriculum needs of high school students and is also an indispensable resource for teachers. In addition, anyone researching folklore in a public library will find this the first place to look for detailed information about cultural traditions around the world.</li>
</span> </div>
<div id="pnlLCCardNumber" class="description"> <span class="book_options">LC Card Number:</span> <span id="lblLCCardNumber">2005019219</span> </div>
<div id="pnlLCCClass" class="description"> <span class="book_options">LCC Class:</span> <span id="lblLCCClass">GR35 </span> </div>
<div id="pnlDeweyClass" class="description"> <span class="book_options">Dewey Class:</span> <span id="lblDeweyClass">398</span> </div>
</div>
</div>
</div>

== Marshall Cavendish [http://www.marshallcavendish.com/marshallcavendish/academic/redirector.xml?url=/marshallcavendish/academic/catalogue/books/regionalism_n_regional_security/9812102108.xml product page] ==
<table cellpadding="2" width="100%">
<tr valign="top">
<td><font id="title_catalogue_font"><b>Regionalism & Regional Security</b></font></td>
</tr>
</table>
<font id="text">
<div style="" align="">
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">ISBN Number</font></td>
<td width="65%"><font id="text">9812102108</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Series</font></td>
<td width="65%"><font id="text">null</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Title</font></td>
<td width="65%"><font id="text">The New Terrorism: Anatomy, Trends and Counter-strategies</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Imprint</font></td>
<td width="65%"><font id="text">Eastern Universities Press</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Specifications</font></td>
<td width="65%"><font id="text">152 mm X 227 mm, 368 pp, limp with flaps, 500 gms</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Authors</font></td>
<td width="65%"><font id="text">Andrew Tan & Kumar Ramakrishna (eds)</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Target Audience</font></td>
<td width="65%"><font id="text">University lecturers/researchers, undergraduate students, academicians and those interested in Regional Security Studies.</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Price (SG)</font></td>
<td width="65%"><font id="text">S$ 39.00</font></td>
</tr>
</table>
<table cellpadding="2" width="100%">
<tr valign="top">
<td width="35%"><font id="title_catalogue_title_font">Price (US)</font></td>
<td width="65%"><font id="text">US$ 30.00</font>   <a href="javascript: addToCart()"><img src="/marshallcavendish/components/db_content/MC_AC_redirector/pic/addCart.gif" border="0"/></a></td>
</tr>
</table>
<br/>
<br/>
The terrorist attacks of September 11, 2001 on the World Trade Centre in New York and the Pentagon in Washington represented a true watershed in world history.<br/>
<br/>
The attacks revealed the horrifying nature of the so-called "new terrorism" that has emerged in the post-Cold War era. The new terrorism is defined by four key features:</div>
</font>
<ul>
<li>
<p align="justify"><font id="text">sheer lethality</font></p>
</li>
<li>
<p align="justify"><font id="text">religious dimension</font></p>
</li>
<li>
<p align="justify"><font id="text">networked organizational structure</font></p>
</li>
<li>
<p align="justify"><font id="text">greatly enhanced striking power   </font></p>
</li>
</ul>
<font id="text">
<div style="" align="">As September 11 clearly demonstrated, the new terrorists can leverage on technology to inflict catastrophic damage even on superpowers, let alone other states.<br/>
<br/>
To examine the new dimensions of terrorism, a conference was organized in Singapore in late March 2002 that brought together a number of leading experts from a wide range of backgrounds from America, Europe and Asia, and the key findings are presented in this volume under the following headings:</div>
</font>
<ul>
<li>
<p align="justify"><font id="text">Anatomy of the new terrorism</font></p>
</li>
<li>
<p align="justify"><font id="text">Terrorist trends and patterns in the Asia-Pacific region</font></p>
</li>
<li>
<p align="justify"><font id="text">Religion and terrorism: Southeast Asian perspectives</font></p>
</li>
<li>
<p align="justify"><font id="text">Formulating counter-strategies   </font></p>
</li>
</ul>
<font id="text">
<div style="" align=""> <span style="font-weight: bold;"> <b> About the Author: </b> </span> <br/>
Both Andrew Tan and Kumar Ramakrishna are Assistant Professors at the Institute of Defence and Strategic Studies, Nanyang Technological University, Singapore.<br/>
Andrew Tan received his M.Phil from Cambridge and PhD from the University of Sydney. His research interests are conflict (inter-state tensions, insurgencies, terrorism and force modernization) in Southeast Asia, and security issues in Asia.<br/>
Kumar Ramakrishna obtained his PhD in History from the University of London in 1999. He teaches and writes on the history of strategic thought as well as the war on terror.</div>
</font>
<td width="18.666662" style="valign: top; background-color: white ; " rowspan="1" colspan="1"><br/>
</td>
<tr valign="top">
<td width="570.666524" style="valign: top; background-color: white ; " rowspan="1" colspan="1"><br/>
</td>
<td width="18.666662" style="valign: top; background-color: white ; " rowspan="1" colspan="1"><br/>
</td>
</tr>
</div>

== Oxford University Press (USA) [http://www.us.oup.com/us/?view=usa homepage] ==
<div class="isbnSummaryDetails">
<h2> <a href="/us/catalog/general/subject/HistoryAmerican/ColonialRevolutionary/?view=usa&ci=0195162471">The Glorious Cause</a> </h2>
<div class="subTitle"> The American Revolution, 1763-1789 </div>
<div class="edition"> Revised and Expanded Edition </div>
<div class="byline"> Robert Middlekauff </div>
<span class="isbnNumber">0195162471</span>, <span class="format">hardback</span>, <span class="publicationDate"> Feb 2005 </span> <span class="price"> $37.50 </span> <span class="description"> The classic history of the American Revolution--now in an updated and expanded twentieth anniversary edition </span>
<div class="related">
<h3>More </h3>

<a href="/us/catalog/general/subject/HistoryAmerican/?view=usa&sf=all">History, American</a> > <a href="/us/catalog/general/subject/HistoryAmerican/ColonialRevolutionary/?view=usa&sf=all">Colonial & Revolutionary</a> </div>
</div>

</div>

== Oxford University Press (USA) [http://www.us.oup.com/us/catalog/general/subject/HistoryAmerican/ColonialRevolutionary/?view=usa&ci=0195162471#Product_Details Product page]==
<div class="isbnProperties isbnSummary">
<div class="isbnSummaryHeading">
<h1>The Glorious Cause</h1>
<div class="subTitle"> The American Revolution, 1763-1789 </div>
<div class="edition"> Revised and Expanded Edition </div>
<div class="byline"> Robert Middlekauff </div>
</div>

<div class="cover"> <span class="bookShot"><a href="#"><img src="/images/covers/0195162471.jpg"
width="63" alt="bookshot" /> </a></span> <span class="addToCart"><a href="http://www.us.oup.com/us/cart/cart.jsp?op=a&i=0195162471&c=85&q=1&r=http%3A%2F%2Fwww.us.oup.com%2Fus%2Fcatalog%2Fgeneral%2Fsubject%2FHistoryAmerican%2FColonialRevolutionary%2F%3Fview%3Dusa%26ci%3D0195162471">Add to Cart</a></span> </div>

<div class="isbnSummaryDetails"> <span class="isbnNumber">0195162471</span>, <span class="format">hardback</span>, <span class="pages"> 760 pages </span>
<div id="generalinfo"> <span class="publicationDate">Feb 2005, </span> <span class="availability"> In Stock </span> </div>
<div class="cost">
<h2>Price:</h2>
$37.50 <span class="discountCode">(02)</span> </div>
<div class="shipping"> <a href="/us/assets/shippingInfo.jsp?si=1.5&so=3.75&sc=0&isi=5&iso=5&isc=0" target="_blank" onclick="window.open(this.href, this.target, 'height=445,width=445,scrollbars');
return false;">Shipping Details</a> </div>
<div class="moreSeries redArrow">
<h3>See more from the series</h3>
<ul>
<li><a href="/us/catalog/general/series/OxfordHistoryoftheUnitedStates/?view=usa">Oxford History of the United States, Vol. 3</a></li>
</ul>
</div>

</div>

</div>
</div>

== Thomson Gale product detail page ==

<div id =" title_main">

<h2>Contemporary Literary Criticism</h2>

<div id =" credits">
<ul>
<li><h2>Excerpts from Criticism of the Works of Today's Novelists, Poets, Playwrights, Short Story Writers, Scriptwriters, & Other Creative Writers</h2>
Volume 1</li>

<li><i>Published by Thomson Gale</i></li>
</ul>
</div>

<div id =" description">
<p>Each print volume in this long-standing series profiles approximately 6-8 novelists, poets, playwrights and other creative writers by providing full-text or excerpted criticism taken from books, magazines, literary reviews, newspapers and scholarly journals. Among those profiled in this volume are:</p>
<ul>
<li>Kingsley Amis
<li>John Dos Passos
<li>Hermann Hesse
<li>Ezra Pound
</ul>
</div>

<div id =" detail">
<ul>
<li>Published/Released:<strong> March 1973</strong></li>
<li>ISBN: <strong>0-8103-0100-8</strong></li>
<li>Product number: <strong>001415</strong></li>
<li>Page count: <strong>485 pp./vol.</strong></li>
<li>Shipping Weight: <strong>5.00 lbs (2.27 kgs)</strong></li>
</ul>
</div> 

<div id =" price">
<P>Price: US $205.00</p>
</div>

</div>
</div>

citation-examples

2005-12-28T22:25:36Z

Tim White: /* Example Citation Formats */

= Example Citation Formats =
The following examples are real world examples that been pulled from places around the web. Please add to this list. The idea is that we get a solid sample of examples and see what commonalities there are amonst them and try to build this microformat so that it can meet 80% of all the possible properties.

== Citation Mark Up in the Wild ==
Mark up examples from reference publisher's websites (online catalogs), including ABC-CLIO, Greenwood Press, Marshall Cavendish, Oxford University Press (USA) and Thomson Gale. Examples are broken down and organized by element.

View complete [[citations in the wild]].

=== Book titles: ===

<span id="title" class="producttitle">The 1920's</span>
(ABC-CLIO product detail page)

<div class="title"> <a href="...">The Greenwood Encyclopedia of World Folklore and Folklife</a> </div>
(Greenwood Press homepage)

<span id="lblTitle" class="book_headline block">The Greenwood Encyclopedia of World Folklore and Folklife</span>
(Greenwood Press product detail page)

<td width="35%"><font id="title_catalogue_title_font">Title</font></td>
<td width="65%"><font id="text">The New Terrorism: Anatomy, Trends and Counter-strategies</font></td>
(Marshall Cavendish product detail page)

<h2> <a href="...">The Glorious Cause</a> </h2>
(Oxford Univ. Press, homepage)

<h1>The Glorious Cause</h1>
(OUP, product detail page)

<h2>Contemporary Literary Criticism</h2>
(Thomson Gale, product detail page)

=== Book Series Name: ===

<span id="serieslbl" class="productsubtitle"><a href="...">Teaching With Documents Series</a></span>
(ABC-CLIO)

=== Sub-title: ===

<span id="subtitle" class="productsubtitle"></span>
(ABC-CLIO)

<div class="sub_title">[Four Volumes]</div>
(Greenwood, homepage)

<span id="lblSubTitle" class="book_subline">[Four Volumes]</span>
(Greenwood, product page)

<div class="subTitle"> The American Revolution, 1763-1789 </div>
(OUP)

=== Author: ===

<span id="credit" class="productauthor"></span>
(ABC-CLIO)

<div class="author">William M. Clements</div>
(Greenwood)

<td width="35%"><font id="title_catalogue_title_font">Authors</font></td>
<td width="65%"><font id="text">Andrew Tan & Kumar Ramakrishna (eds)</font></td>
(Marshall Cavendish)

<div class="byline"> Robert Middlekauff </div>
(OUP)

=== Publication Date: ===

<span id="pubdate" class="productdetailbody">11/2001</span>
(ABC-CLIO -- see table structure)

<div id="pnlPubDate"> <span class="book_options">Publication Date:</span> <span id="lblPubDate">12/30/2005</span> </div>
(Greenwood, detail page)

<span class="publicationDate"> Feb 2005 </span>
(OUP)

<li>Published/Released:<strong> March 1973</strong></li>
(Thomson Gale)

=== Volumes: ===

<td width="110" class="productdetailhead"><span id="volumeslabel" class="productdetailhead">Volumes</span></td>
<td width="180" class="productdetailbody"><span id="volumes" class="productdetailbody">1</span></td>
(ABC-CLIO)

=== ISBN: ===

<td class="productdetailhead" width="88"><span id="ISBNLabel">ISBN</span></td>
<td class="productdetailbody">1-57607-785-3</td>
(ABC-CLIO)

<div class="isbn">0-313-32847-1</div>
(Greenwood, homepage)

<div id="pnlIsbn"> <span class="book_options">ISBN:</span> <span id="lblIsbn">0-313-32847-1</span> </div>
(Greenwood, product page)

<td width="35%"><font id="title_catalogue_title_font">ISBN Number</font></td>
<td width="65%"><font id="text">9812102108</font></td>
(Marshall Cavendish)

<span class="isbnNumber">0195162471</span>
(OUP)

<li>ISBN: <strong>0-8103-0100-8</strong></li>
(Thomson Gale)

=== Book Edition: ===

<div class="edition"> Revised and Expanded Edition </div>
(OUP)

== RFC vCard Example ==
<pre><nowiki>
9. References

[ISO 8601] ISO 8601:1988 - Data elements and interchange formats -
Information interchange - Representation of dates and
times - The International Organization for
Standardization, June, 1988.

[ISO 8601 TC] ISO 8601, Technical Corrigendum 1 - Data elements and
interchange formats - Information interchange -
Representation of dates and times - The International
Organization for Standardization, May, 1991.

[ISO 9070] ISO 9070, Information Processing - SGML support
facilities - Registration Procedures for Public Text
Owner Identifiers, April, 1991.

[CCITT E.163] Recommendation E.163 - Numbering Plan for The
International Telephone Service, CCITT Blue Book,
Fascicle II.2, pp. 128-134, November, 1988.

[CCITT X.121] Recommendation X.121 - International Numbering Plan for
Public Data Networks, CCITT Blue Book, Fascicle VIII.3,
pp. 317-332, November, 1988.

[CCITT X.520] Recommendation X.520 - The Directory - Selected
Attribute Types, November 1988.

[CCITT X.521] Recommendation X.521 - The Directory - Selected Object
Classes, November 1988.

[MIME-DIR] Howes, T., Smith, M., and F. Dawson, "A MIME Content-
Type for Directory Information", RFC 2425, September
1998.

[RFC 1738] Berners-Lee, T., Masinter, L., and M. McCahill,
"Uniform Resource Locators (URL)", RFC 1738, December
1994.

[RFC 1766] Alvestrand, H., "Tags for the Identification of
Languages", RFC 1766, March 1995.

[RFC 1872] Levinson, E., "The MIME Multipart/Related Content-
type", RFC 1872, December 1995.

[RFC 2045] Freed, N., and N. Borenstein, "Multipurpose Internet
Mail Extensions (MIME) - Part One: Format of Internet
Message Bodies", RFC 2045, November 1996.

[RFC 2046] Freed, N., and N. Borenstein, "Multipurpose Internet
Mail Extensions (MIME) - Part Two: Media Types", RFC
2046, November 1996.

[RFC 2047] Moore, K., "Multipurpose Internet Mail Extensions
(MIME) - Part Three: Message Header Extensions for
Non-ASCII Text", RFC 2047, November 1996.

[RFC 2048] Freed, N., Klensin, J., and J. Postel, "Multipurpose
Internet Mail Extensions (MIME) - Part Four:
Registration Procedures", RFC 2048, January 1997.

[RFC 2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.

[RFC 2234] Crocker, D., and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997.

[UNICODE] "The Unicode Standard - Version 2.0", The Unicode
Consortium, July 1996.

[VCARD] Internet Mail Consortium, "vCard - The Electronic
Business Card Version 2.1",
http://www.imc.org/pdi/vcard-21.txt, September 18,
1996.
</nowiki></pre>
[http://www.faqs.org/rfcs/rfc2426.html vCard RFC]

== W3C XHTML Spec Example ==
<pre><nowiki>
<h1><a name="refs" id="refs">E.</a> References</h1>

<p><strong>This appendix is informative.</strong></p>

<dl>
<dt><a name="ref-css2" id="ref-css2"><strong>[CSS2]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/1998/REC-CSS2-19980512">Cascading Style Sheets, level 2 (CSS2) Specification</a></cite>", B. Bos, H. W. Lie, C. Lilley, I. Jacobs, 12 May 1998.<br />
<a href="http://www.w3.org/TR/REC-CSS2">Latest version</a> available at: http://www.w3.org/TR/REC-CSS2</dd>

<dt><a name="ref-dom" id="ref-dom"><strong>[DOM]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001">Document Object Model (DOM) Level 1 Specification</a></cite>", Lauren Wood <em lang="lt" xml:lang="lt">et al.</em>, 1 October
1998.<br />
<a href="http://www.w3.org/TR/REC-DOM-Level-1">Latest version</a> available at: http://www.w3.org/TR/REC-DOM-Level-1</dd>

<dt><a name="ref-dom2" id="ref-dom2"><strong>[DOM2]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113">Document Object Model (DOM) Level 2 Core Specification</a></cite>", A. Le Hors, <em lang="lt" xml:lang="lt">et
al.</em>, 13 November 2000.<br />
<a href="http://www.w3.org/TR/DOM-Level-2-Core">Latest version</a> available at: http://www.w3.org/TR/DOM-Level-2-Core</dd>

<dt><a name="ref-html4" id="ref-html4"><strong>[HTML]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/1999/REC-html401-19991224">HTML 4.01 Specification</a></cite>", D. Raggett, A. Le Hors, I. Jacobs, 24 December 1999.<br />
<a href="http://www.w3.org/TR/html401">Latest version</a> available at: http://www.w3.org/TR/html401</dd>

<dt><a name="ref-posix.1" id="ref-posix.1"><strong>[POSIX.1]</strong></a></dt>

<dd>"<cite>ISO/IEC 9945-1:1990 Information Technology - Portable Operating System Interface (POSIX) - Part 1: System Application Program Interface (API) [C Language]</cite>", Institute of Electrical
and Electronics Engineers, Inc, 1990.</dd>

<dt><a id="ref-rfc2045" name="ref-rfc2045"><strong>[RFC2045]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2045.txt">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a></cite>", N. Freed and N. Borenstein, November
1996. Note that this RFC obsoletes RFC1521, RFC1522, and RFC1590.</dd>

<dt><a name="ref-rfc2046" id="ref-rfc2046"><strong>[RFC2046]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2046.txt">RFC2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a></cite>", N. Freed and N. Borenstein, November 1996.<br />
Available at <a href="http://www.ietf.org/rfc/rfc2046.txt">http://www.ietf.org/rfc/rfc2046.txt</a>. Note that this RFC obsoletes RFC1521, RFC1522, and RFC1590.</dd>

<dt><a name="ref-rfc2119" id="ref-rfc2119"><strong>[RFC2119]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2119.txt">RFC2119: Key words for use in RFCs to Indicate Requirement Levels</a></cite>", S. Bradner, March 1997.<br />
Available at: http://www.ietf.org/rfc/rfc2119.txt</dd>

<dt><a name="ref-rfc2376" id="ref-rfc2376"><strong>[RFC2376]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2376.txt">RFC2376: XML Media Types</a></cite>", E. Whitehead, M. Murata, July 1998.<br />
This document is obsoleted by [<a href="#ref-rfc3023">RFC3023</a>].<br />
Available at: http://www.ietf.org/rfc/rfc2376.txt</dd>

<dt><a name="ref-rfc2396" id="ref-rfc2396"><strong>[RFC2396]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2396.txt">RFC2396: Uniform Resource Identifiers (URI): Generic Syntax</a></cite>", T. Berners-Lee, R. Fielding, L. Masinter, August 1998.<br />
This document updates RFC1738 and RFC1808.<br />
Available at: http://www.ietf.org/rfc/rfc2396.txt</dd>

<dt><a name="ref-rfc2854" id="ref-rfc2854"><strong>[RFC2854]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2854.txt">RFC2854: The text/html Media Type</a></cite>", D. Conolly, L. Masinter, June 2000.<br />
Available at: http://www.ietf.org/rfc/rfc2854.txt</dd>

<dt><a name="ref-rfc3023" id="ref-rfc3023"><strong>[RFC3023]</strong></a></dt>

<dd>"<cite><a href="http://www.ietf.org/rfc/rfc3023.txt">RFC3023: XML Media Types</a></cite>", M. Murata, S. St.Laurent, D. Kohn, January 2001.<br />
This document obsoletes [<a href="#ref-rfc2376">RFC2376</a>].<br />
Available at: http://www.ietf.org/rfc/rfc3023.txt</dd>

<dt><a id="ref-rfc3066" name="ref-rfc3066"><strong>[RFC3066]</strong></a></dt>

<dd>"<a href="http://www.ietf.org/rfc/rfc3066.txt">Tags for the Identification of Languages</a>", H. Alvestrand, January 2001.<br />
Available at: http://www.ietf.org/rfc/rfc3066.txt</dd>

<dt><a id="ref-rfc3236" name="ref-rfc3236"><strong>[RFC3236]</strong></a></dt>

<dd>"<a href="http://www.ietf.org/rfc/rfc3236.txt">The 'application/xhtml+xml' Media Type</a>", M. Baker, P. Stark, January 2002.<br />
Available at: http://www.ietf.org/rfc/rfc3236.txt</dd>

<dt><a id="ref-xhtml-mathml" name="ref-xhtml-mathml"><strong>[XHTML+MathML]</strong></a></dt>

<dd><cite>"<a href="http://www.w3.org/TR/MathML2/dtd/xhtml-math11-f.dtd">XHTML plus Math 1.1 <abbr title="Document Type Definition">DTD</abbr></a></cite>", "A.2 MathML as a DTD Module", Mathematical
Markup Language (MathML) Version 2.0. Available at: http://www.w3.org/TR/MathML2/dtd/xhtml-math11-f.dtd</dd>

<dt><a id="ref-xhtmlmime" name="ref-xhtmlmime"><strong>[XHTMLMIME]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/2002/NOTE-xhtml-media-types-20020801">XHTML Media Types</a></cite>", Masayasu Ishikawa, 1 August 2002.<br />
<a href="http://www.w3.org/TR/xhtml-media-types">Latest version</a> available at: http://www.w3.org/TR/xhtml-media-types</dd>

<dt><a id="ref-xhtmlmod" name="ref-xhtmlmod"><strong>[XHTMLMOD]</strong></a></dt>

<dd>"<cite><a href="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410">Modularization of XHTML</a></cite>", M. Altheim et al., 10 April 2001.<br />
<a href="http://www.w3.org/TR/xhtml-modularization">Latest version</a> available at: http://www.w3.org/TR/xhtml-modularization</dd>

<dt><a name="ref-xml" id="ref-xml"><strong>[XML]</strong></a></dt>

<dd>"<a href="http://www.w3.org/TR/2000/REC-xml-20001006">Extensible Markup Language (XML) 1.0 Specification (Second Edition)</a>", T. Bray, J. Paoli, C. M. Sperberg-McQueen, E. Maler, 6 October
2000.<br />
<a href="http://www.w3.org/TR/REC-xml">Latest version</a> available at: http://www.w3.org/TR/REC-xml</dd>

<dt><a name="ref-xmlns" id="ref-xmlns"><strong>[XMLNS]</strong></a></dt>

<dd>"<a href="http://www.w3.org/TR/1999/REC-xml-names-19990114">Namespaces in XML</a>", T. Bray, D. Hollander, A. Layman, 14 January 1999.<br />
XML namespaces provide a simple method for qualifying names used in XML documents by associating them with namespaces identified by URI.<br />
<a href="http://www.w3.org/TR/REC-xml-names">Latest version</a> available at: http://www.w3.org/TR/REC-xml-names</dd>

<dt><a name="ref-xmlc14n" id="ref-xmlc14n"><strong>[XMLC14N]</strong></a></dt>

<dd>"<a href="http://www.w3.org/TR/2001/REC-xml-c14n-20010315">Canonical XML Version 1.0</a>", J. Boyer, 15 March 2001.<br />
This document describes a method for generating a physical representation, the canonical form, of an XML document.<br />
<a href="http://www.w3.org/TR/xml-c14n">Latest version</a> available at: http://www.w3.org/TR/xml-c14n</dd>
</dl>
</nowiki></pre>
[http://www.w3.org/TR/xhtml1/#refs XHTML1.0 Spec references]

== CiteProc XHTML Output ==

The XHTML output for CiteProc[http://xbiblio.sourceforge.net/citeproc.html] wasn't designed per se as a microformat, but is probably not a bad place to start. It is desgined to handle a wide range of content. Here is the APA output:

<pre><nowiki>
<div id="bibliography">

<h3>References</h3>

<p id="Brenner2000a" class="bibref">
<span class="creator">Brenner, N.</span>
<span class="date"> (<span class="year">2000</span>) </span>
<span class="title">The Urban Question as a Scale Question: Reflections
on Henri Lefebre, Urban Theory and the Politics of Scale, </span>
<span class="container">
<span class="title" style="font-style: italic">International Journal of
Urban and Regional Research, </span>
<span class="volume">24</span>
<span class="issue">(2)</span>
<span class="locator">, pp. 361–78</span>
</span>.
</p>

<p id="NW2000-0207" class="bibref">
<span class="creator">Newsweek</span>
<span class="date">
(<span class="year">2000a</span>
<span class="month">, February</span>
<span class="day"> 7</span>)
</span>
<span class="title">The Grandmas Pay a Visit, </span>
<span class="container">
<span class="volume">135</span>
<span class="issue">(6)</span>
<span class="locator">, pp. 45</span>
</span>.
</p>

<p id="Veer1996a" class="bibref">
<span class="creator">van der Veer, P.</span>
<span class="date"><span class="year"> (1996) </span></span>
<span class="title">Riots and Rituals: The Construction of Violence
and Public Space in Hindu Nationalism</span>
<span class="container">, In Brass, P.<span class="role"> (Ed.)</span>.
<span class="title" style="font-style: italic">Riots and Pogroms.</span>
<span class="origin"><span class="place">New York</span>
<span class="publisher">: NYU Press</span></span>
<span class="locator">, pp. 154–76</span>
</span>.
</p>
</div>
</nowiki></pre>

= Styles =
This does NOT define a format, but instead shows how the format should be displayed. This is something out of the direct scope of this project. CSS styles will handle the look-and-feel of the text, and the author can put it in any order they choose. These links are mentioned for two reasons, one is informative, the other is so we know atleast meet the minimum properties that are used in the styles.

* [http://www.liu.edu/cwis/cwp/library/workshop/citmla.htm MLA Style]
* [http://www.bu.edu/library/guides/citation.html Chicago, MLA, and APA styles]
* [http://www.legalbluebook.com/ Blue Book] for legal citations
* [http://www.columbia.edu/cu/cup/cgos/idx_basic.html Columbia University Citation Style] developed for modern internet citations

citation-brainstorming

2005-12-28T18:01:25Z

Tim White: /* Types and Roles */

= Citation Brainstroming =

== XHTML Structure ==
With my exprience working X2V and hCa* has taught me what elememts are easy to find and which are not. Since the Citation microformat is very new it is possible to not make a lot of the same errors twice and to make things easier for extracting application to find and imply certain properties.

* There should be some sort of 'root node' that implies all child elements are for the Citation microformat.
* Since most people will have multiple Citation there should be away to represent each Citation object as a unqiue block independant of another. This is to keep the parse from finding 'author' and applying to all citations. Each citation should be in a container (class="???") that scoped from others.

@@ more points will be posted as i remember of them

== Semantic Meaning ==
One of the guiding priniciple of Microformats is to use the most semantically rich element to describe each node (Point 2 of Semantic XHTML Design Principles: Use the most accurately precise semantic XHTML building block for each object etc). Since we are dealing with HTML and citations, several elements are candidates to be used to enrich the semantic meaning. [http://www.w3.org/TR/REC-html40/struct/text.html CITE, BLOCKQUOTE, Q, A], (are there more?)

The [[citation-brainstorming|Citation Brainstorming Page]] has a few development and ideas about how to give another person credit for a link. Some of the semantic ideas behind their choices of tags can be applied to a full bibliographic type reference.

== ISBN:// Protocol ==
[http://www.faqs.org/rfcs/rfc3187.html RFC3187] defines an isbn protocol

Example:

URN:ISBN:0-395-36341-1

I'm not sure if any browser uses this data, but it might be have an application in citations describing registered materials with an ISBN

Question: what about using something like OCLC's [http://www.oclc.org/worldcat/open/isbnissnlinking/default.htm WorldCat] for linking titles? - Tim White

== This and That ==
After reading through alot of different citation encoding formats, i noticed that each format was being used in onw of two ways. It was either to describe the Current page (THIS.PAGE) or being used to encode references that point to external resources (THAT.PAGE)

The informatation being encoded was identical for both resources (author, date, name, etc) they just reference different things. For this microformat, i'm not sure if we want to try to solve both problems, or just one? The meta tags in the head element would be the ideal place for information about the THIS.PAGE, but that is not in following with the ideals of microformats where information is human-readable. The THAT.PAGE idea where a list of references is at the end of a document in the form of a bibliography is more inline with the ideals of a microformat where the data is human-readable. That doesn't mean that data about the current document shouldn't be human-readable, so some of the same properties used to reference extermal resources can be used for the current document (THIS.PAGE). To do this a different root item could be used and transforming applications could either extract the citation data about the current page, or information about this page's references.

This is open for discussion, but either way, i believe that the properties used to describe a page will be the same for both THIS and THAT. [http://suda.co.uk/ brian suda]

== Date Formatting ==
Since microformats are all about re-use and the accepted way to encode Date-Time has been pretty much settled, then this is a good place to start when dealing with all the different date citation types.

These are all the different fields from various citation formats that are of temporal nature:
* Date (available | created | dateAccepted | dateCopyrighted | dateSubmitted | issued | modified | valid)
* originInfo/dateIssued
* originInfo/dateCreated
* originInfo/dateCaptured
* originInfo/dateOther
* month
* year
* Copyright Year
* Date - Generic
* Date of Confernce
* Date of Publication
* Date of update/revisou/issuance of database record
* Former Date
* Entry Date for Database Record
* Database Update
* Year of Publication

There are several common properties across several citation domains and will certainly be in the citation microformat, the unique instances will need further consideration, otherwise there could be no end to posiblities.

There are also several properties (year, month, Year of publication) that can be extracted from another source. Therefore, if you only encode a more specific property such as; Date of Publication, you can extract the 'year of publication' from that. Since the date-time format we are modeling after is the ISO date-time format, just the Year portion is an acceptable date. So if you ONLY know the year of publication, the you can form a valid 'Date of Publication' as a microformat (which inturn is a valid 'year of publication') - you milage may vary when it comes to importing into citation applications.

== Types and Roles ==
(Section is informative only as a place to capture varioua=s parts of publication citations.)

There are many different types of publications and this information should be captured in the citation. Possible types include:
* Novel/fiction (specify type -- literature, sci-fi, romance, etc.?)
* Non-fiction
* Poem
* Play
* Magazine
* Reference (seperate out encyclopedia, dictionary, almanac, etc.?)
* Journal
* Article within a journal
* Chapter within a book
* Dissertation
* Web Site
* Page within a web site
* Music Recording
* Video Recording
* Interview
* Physical object (Statue, Painting, etc.)
* ??

Question:
Certain works have specific types of citations, for example, the Bible--and, I assume, other religious works--have very specific citation formats with different relevant information (chapter/verse) than others, as do the works of Shakespeare. Should these be considered seperate types/roles?

A: I think in terms of types, we should at least note the items (chapter, verse, etc). How they get dealt with is still way up in the air. - Tim

Likewise, there are several different roles associated with publications -- author, co-author, editor, translator, etc. Should these be captured under a master "role" or treated as individual elements?

A: Good question. I think there is an important distinction, but whether we follow a design pattern of "role-*" (or more likely "author-*) or some other pattern hasn't been discussed yet. - Tim

== Tags ==
Some of the citation formats has a place for 'keywords' or 'generic tags', etc. This might be a good place to re-use the [http://microformats.org/wiki/rel-tag RelTag microformat]. The downside would be that they are then forced to be links, which might be the correct way to mark-up these terms.

== OpenURL ==

OpenURL is in use in library software around the world to allow citation metadata to be embedded in URLs. Typically these URLs are used for targeting resolvers which essentially proxy access to licensed content. OpenURL also provides an XML encoding. The [http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=ListRecords&metadataPrefix=oai_dc&set=Core:Metadata+Formats key/value] pairs used in OpenURL could relatively easily be adapted to semantic HTML. This is a cow path that could be paved relatively easily using existing modules as appropriate.

OpenURL has a microformat-like encoding: [http://ocoins.info/ COinS]. This uses the 'title' attribute of HTML 'span' tags to embed OpenURL URLs.

Example (from a book review written using the Structured Blogging plugin):

<pre><nowiki>
<p><b>ISBN</b>: <span class='Z3988'
title='ctx_ver=Z39.88-2004&amp;rft_val_fmt=info:ofi/fmt:kev:mtx:book&amp;rft.isbn=0679426612'>
0679426612</span></p>
</nowiki></pre>

== MARC / MODS / Dublin Core ==

The MODS ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgmods.xml example]) and Dublin Core ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgdc.xml example]) transformations of MARC21 may contain some useful ideas.

Here's a first attempt at rewriting the linked examples in XHTML (written in response to a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002438.html mailing list query about encoding book information with microformats]):

<pre><nowiki>
<div class="book" lang="en">
<h3 class="fn">Arithmetic /</h3>
<p>By <span class="creator"><span class="fn">Sandburg, Carl</span>,
<span class="date">1878-1967</span></span>,
and <span class="illustrator">Rand, Ted</span></p>
<p>Publisher: <span class="publisher"><span class="fn">Harcourt Brace Jovanovich</span>,
<span class="locality">San Diego</span></span></p>
<p>Published: <span class="issued">1993</span></p>
<p class="description">A poem about numbers and their characteristics. Features
anamorphic, or distorted, drawings which can be restored to normal by viewing
from a particular angle or by viewing the image's reflection in the provided
Mylar cone.</p>
<p class="note">One Mylar sheet included in pocket.</p>
<p>Subjects:</p>
<ul>
<li class="subject">Arithmetic</li>
<li class="subject">Children's poetry, American.</li>
<li class="subject">Arithmetic</li>
<li class="subject">American poetry</li>
<li class="subject">Visual perception</li>
</ul>
</div>
</nowiki></pre>

Here is [http://www.aadl.org/cat/seek/search/X?SEARCH=knitting&searchscope=26&x=0&y=0&SORT=D&sourceid=Mozilla-search&rss=1 an example of the HTML (inside an RSS feed)] that the [http://www.aadl.org Ann Arbor District Library ] is generating and wants to mark up with some sort of publication microformat.

citation-brainstorming

2005-11-22T18:30:31Z

Tim White: /* ISBN:// Protocol */

citation-formats

2005-11-04T19:40:34Z

Tim White: /* Comparison chart */

This page will display several different types of citation format types. The idea is to compare what properties are common amonst all of the formats and which ones should be blended into this microformat.

== Comparison chart ==
The following chart maps the terms from one implementation to another. This is important because if all the properties are introduced to this microformats, then its possible to map them to a number of different formats. The table currently only uses Dublin Core, MODS, and bibTeX. Each column has all the properties and their equivalent in each format. If there is no corresponding property the cell is grey. At the bottom of the list are the unique terms to each format. Dublin core has basic terms and terms that extend the basic ones. If the property is an extention of a basic term it is in ()'s. MODS uses XML, so any sub-properties are listed in their tree form, property/sub-property.

THIS IS NOT DEFINIATIVE, any errors should be corrected. More formats will be added to the list as they are mapped.

<table border="1">
<tr>
<th>Dublin Core</th>
<th>MODS</th>
<th>bibTeX</th>
<th>Z39.80</th>
</tr>
<tr>
<td>Title (alternative)</td>
<td>titleInfo/title<br/>titleInfo/PartNum</td>
<td>booktitle<br/>title<br/>chapter<br/>number<br/>pages<br/>volume<br/>series</td>
<td>Analytic Title<br/>
Collective or Series Title<br/>
Monographic Title<br/>
Work Fraction Title<br/>
Location of Conference<br/>
Main Entry<br/>
Name of Conference<br/>
Number of Meeting<br/>
Other Title<br/>
Parallel Title<br/>
Title Abbriviation<br/>
Title of Conference Proceedings<br/>
Translated Title<br/>
Uniform Title<br/>
Abbriviated Translated Title<br/>
Symposium or Session Title<br/>
Collective or Series Edition<br/>
Video/Film Edition<br/>
</td>
</tr>
<tr>
<td>creator</td>
<td>name/namePart</td>
<td>author<br/>creator</td>
<td>Author, Primary<br/>
Corporate Author, Primary<br/>
Abstract Author<br/>
Authorship Statement<br/>
Acknowledged Supporters<br/>
Assignee for Patents<br/>
Chairperson of Conference<br/>
Director of AV Program<br/>
Other Author<br/>
Reviewed Book Author<br/>
Studio<br/>
Sponsor of Conference<br/>
Staff/Cast<br/>
Symposium Chairperson<br/>
Author Address or Affiliation<br/>
Author Country<br/>
Electronic Address of Author<br/>
</td>
</tr>
<tr>
<td>subject</td>
<td>subject/topic</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td>Description (abstract | tableOfContents)</td>
<td>abstract<br/>note<br/>tableOfContents</td>
<td>abstract<br/>annotation<br/>note<br/>contents</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Contributer</td>
<td>name</td>
<td>editor?</td>
<td>Book/Report/Volume Editor<br/>
Producer<br/>
Translator<br/>
</td>
</tr>
<tr>
<td>Date (available | created | dateAccepted | dateCopyrighted | dateSubmitted | issued | modified | valid)</td>
<td>originInfo/dateIssued<br/>originInfo/dateCreated<br/>originInfo/dateCaptured<br/>originInfo/dateOther</td>
<td>month<br/>year</td>
<td>Copyright Year<br/>Date-generic<br/>Date of conference<br/>Date of Publication<br/>Date of Update/Revisou/Issuance of Database Record<br/>Former Date<br/>Entry date for Database Record<br/>Database Update<br/>Year of Publication</td>
</tr>
<tr>
<td>Type</td>
<td>typeOfResource<br/>genre</td>
<td>@class<br/>type</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Format (extent | medium)</td>
<td>physicalDescription/internetMediaType<br/>physicalDescription/extent<br/>physicalDescription/form</td>
<td>published</td>
<td>needs mapping</td>
</tr>
<tr>
<td>identifier (bibliographicCitation)</td>
<td>identifier</td>
<td>ISBN<br/>ISSN<br/>LCCN<br/>URL</td>
<td>ISBN<br/>Identifier<br/>Report Identfier<br/>ISSN</td>
</tr>
<tr>
<td>Source</td>
<td>relatedItem</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td>language</td>
<td>language</td>
<td>language</td>
<td bgcolor="#cccccc"></td>
</tr>
<tr>
<td>Relation (...)</td>
<td>relatedItem/...</td>
<td>crossRef</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Coverage (spacial | temporal)</td>
<td>subject/temporal<br/>subject/geographic<br/>subject/hierarchicalGeographic<br/>subject/cartographics</td>
<td></td>
<td>needs mapping</td>
</tr>
<tr>
<td bgcolor="#cccccc"></td>
<td>classifications</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td>Rights (accessRights | license)</td>
<td>accessConditions</td>
<td>copyright</td>
<td>needs mapping</td>
</tr>
<tr>
<td>publisher</td>
<td bgcolor="#cccccc"></td>
<td>publisher</td>
<td>Publisher Name<br/>
Place of Publication<br/>
Country of Publication<br/>
Generic Address<br/>
</td>
</tr>
<tr>
<td>audience (educationLevel | mediator)</td>
<td>targetAudience</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td bgcolor="#999999">accualMethod<br/>accualPeriodicaty<br/>accualPolicy<br/>instrcutionalMethod<br/>provenance<br/>rightsHolder</td>
<td bgcolor="#999999">location<br/>extension<br/>recordInfo</td>
<td bgcolor="#999999">address<br/>afflilication<br/>location<br/>edition<br/>institution<br/>journal<br/>key<br/>keywords<br/>mrnumber<br/>organization<br/>price<br/>school<br/>size</td>
<td bgcolor="#999999">(the following need to be mapped to the above rows or left here as other)<br/><br/>
Database Source<br/>
Databse Record Identifier<br/>
Database Producer Name<br/>
Rights Management<br/>
Subfile<br/>
Other Source Identifier<br/>
Vendor Record Identifier<br/>
Database Vendor Name<br/>
Column Number<br/>
Edition<br/>
Frequency of Publication<br/>
Internet Location for Document<br/>
Supplement/Part/Special number identifer<br/>
Issue Identifier<br/>
Location in Work<br/>
Number of the Chapter<br/>
Number in Series<br/>
Volume Identifier<br/>
Section Indentifier<br/>
</td>
</tr>
</table>

== Dublin Core Metadata ==
[http://dublincore.org/ Dublin Core] metadata uses a small vocabulary to descibe the data.
* contributor
* coverage
* creator
* date
* description
* format
* identifier
* language
* publisher
* relation
* rights
* source
* subject
* title
* type

From those there are specialised types where are just refinments of the previous, for example:

* abstract refines description.
* accessRights refines rights

[http://dublincore.org/documents/dc-citation-guidelines/ Guidelines for Encoding Bibliographic Citation Information in Dublin Core Metadata]

== MODS (Metadata Object Description Schema) ==
This is a format developed for the Libray of Congress for a bibliographic element set that may be used for a variety of purposes, and particularly for library applications.

[http://www.loc.gov/standards/mods/ http://www.loc.gov/standards/mods/]

(the schema is very big, once i devote the proper time to review it, i will post more about the structure -brian)

== XMLResume ==
<pre>
<!ELEMENT pubs (pub+)>
<!ENTITY % pubElements "(artTitle|bookTitle|author|date|pubDate|publisher|pageNums|url)">
<!ELEMENT pub (para | %pubElements;)*>
<!ATTLIST pub id ID #IMPLIED>
<!ELEMENT artTitle (#PCDATA | link)*>
<!ELEMENT bookTitle (#PCDATA | link)*>
<!ELEMENT author (#PCDATA)>
<!ATTLIST author name IDREF #IMPLIED>
<!ELEMENT pubDate (month?, year)> 
<!ELEMENT publisher (#PCDATA | link | url)*>
<!ELEMENT pageNums (#PCDATA)>
</pre>

== BibTeX ==
=== Fields Used by Bibtex ===
<table border="1" width="100%">
<tr>
<td><strong>abstract:</strong></td>
<td>An abstract of the work.</td>
</tr>
<tr>
<td><b>address:</b></td>
<td>Publisher's address. For major publishing houses,
just the city is given. For small publishers, you can
help the reader by giving the complete address.</td>
</tr>
<tr>
<td><strong>affiliation:</strong></td>
<td>The author's affiliation.</td>
</tr>
<tr>
<td><b>annote:</b></td>
<td>An annotation. It is not used by he standard
bibliography styles, but may be used by others that
produce an annotated bibliography.</td>
</tr>
<tr>
<td><b>author:</b></td>
<td>The name(s) of the author(s).</td>
</tr>
<tr>
<td><b>booktitle: </b></td>
<td>Title of a book, part of which is being cited. For
book entries, use the <strong>title</strong> field
instead.</td>
</tr>
<tr>
<td><b>chapter:</b></td>
<td>A chapter (or section) number.</td>
</tr>
<tr>
<td><strong>contents:</strong></td>
<td>A Table of Contents.</td>
</tr>
<tr>
<td><strong>copyright:</strong></td>
<td>Copyright information.</td>
</tr>
<tr>
<td><strong>crossref:</strong></td>
<td>The database key of the entry being cross-referenced.</td>
</tr>
<tr>
<td><b>edition: </b></td>
<td>The edition of a book - for example
"Second". Notice that it is in capitals.</td>
</tr>
<tr>
<td><b>editor: </b></td>
<td>Name(s) of editor(s). If there is also an author
field, then the editor field gives the editor of the book
or collection in which the reference appears.</td>
</tr>
<tr>
<td><b>howpublished:</b></td>
<td>How something strange has been published. The first
word should be capitalized.</td>
</tr>
<tr>
<td><b>institution:</b></td>
<td>The sponsoring institution of a technical report.</td>
</tr>
<tr>
<td><strong>ISBN:</strong></td>
<td>The International Standard Book Number.</td>
</tr>
<tr>
<td><strong>ISSN:</strong></td>
<td>The International Standard Serial Number. Used to
identify a journal.</td>
</tr>
<tr>
<td><b>journal: </b></td>
<td>A journal name. Abbreviations are provided for many
journals.</td>
</tr>
<tr>
<td><b>key: </b></td>
<td>Used for alphabetizing and creating a label when the
author and editor fields are missing. This field should
not be confused with the key that appears at the
beginning of the reference.</td>
</tr>
<tr>
<td><strong>keywords:</strong></td>
<td>Key words used for searching or possibly for
annotation.</td>
</tr>
<tr>
<td><strong>language:</strong></td>
<td>The language the document is written in.</td>
</tr>
<tr>
<td><strong>LCCN:</strong></td>
<td>The Library of Congress Call Number.</td>
</tr>
<tr>
<td><strong>location:</strong></td>
<td>A location associated with the entry, such as the
city in which a conference took place.</td>
</tr>
<tr>
<td><b>month: </b></td>
<td>The month in which the work was published or, for an
unpublished work, in which it was written.</td>
</tr>
<tr>
<td><strong>mrnumber:</strong></td>
<td>The <em>Mathematical Reviews</em> number.</td>
</tr>
<tr>
<td><b>note:</b></td>
<td>Any additional information that can help the reader.
First word should be capitalized.</td>
</tr>
<tr>
<td><b>number: </b></td>
<td>The number of a journal, magazine, technical report,
or of a work in a series. An issue of a journal or
magazine is usually identified by its volume and number;
the organization that issues a technical report usually
gives it a number; and sometimes books are given numbers
in a named series.</td>
</tr>
<tr>
<td><b>organization: </b></td>
<td>The organization that sponsors a conference or
publishes a manual.</td>
</tr>
<tr>
<td><b>pages:</b></td>
<td>One or more page numbers or ranges of number, such as
37--42, or 7,53,82--94.</td>
</tr>
<tr>
<td><strong>price:</strong></td>
<td>The price of the material.</td>
</tr>
<tr>
<td><b>publisher:</b></td>
<td>The publisher's name.</td>
</tr>
<tr>
<td><b>school:</b></td>
<td>The name of the school where a thesis was written.</td>
</tr>
<tr>
<td><b>series:</b></td>
<td>Then name given a series or set of books. When citing
an entire book, the title field gives its title and the
optional series field gives the name of a series in which
the book was published.</td>
</tr>
<tr>
<td><strong>size:</strong></td>
<td>The physical dimensions of the work.</td>
</tr>
<tr>
<td><b>title:</b></td>
<td>The work's title.</td>
</tr>
<tr>
<td><b>type:</b></td>
<td>The type of technical report - for example,
"Research Note".</td>
</tr>
<tr>
<td><strong>url:</strong></td>
<td>The WWW Universal Resource Locator that points to the
item being referenced. Often used for technical reports
to point to the FTP site where it resides.</td>
</tr>
<tr>
<td><b>volume:</b></td>
<td>The volume of a journal or multivolume book.</td>
</tr>
<tr>
<td><b>year:</b></td>
<td>The year of publication or, for an unpublished work,
the year it was written. It should only consist of
numerals, such as 1976.</td>
</tr>
</table>
=== BibTeX citation Types ===
A reference can be to any of a variety of types. Following is a list of types. Each one also explains the fields associated with that type. Any fields not listed as required or optional are considered to be ignored.
<table border="1" width="100%">
<tr>
<td><b>article:</b></td>
<td>An article from a journal or magazine. Required
fields: author, title, journal, year. Optional fields:
volume, number, pages, month, note, key.</td>
</tr>
<tr>
<td><b>book:</b></td>
<td>A book with an explicit publisher. Required fields:
author or editor, title, publisher, year. Optional
fields: volume, series, address, edition, month, note,
key.</td>
</tr>
<tr>
<td><b>booklet: </b></td>
<td>A work that is printed and bound, but without a named
publisher or sponsoring institution. Required fields:
title. Optional fields: author, howpublished, address,
month, year, note, key.</td>
</tr>
<tr>
<td><strong>collection:</strong></td>
<td>A collection of works. Same as <a href="#proceedings">Proceedings</a>.</td>
</tr>
<tr>
<td><b>conference:</b></td>
<td>The same as <a href="#inproceedings">Inproceedings</a>.</td>
</tr>
<tr>
<td><b>inbook:</b></td>
<td>A part of a book, which may be a chapter and/or a
range of pages. Required fields: author or editor, title,
chapter and/or pages, publisher, year. Optional fields:
volumer, series, address, edition, month, note, key.</td>
</tr>
<tr>
<td><b>incollection:</b></td>
<td>A part of a book with its own title. Required fields:
author, title, booktitle, publisher, year. Optional
fields: editor, pages, organization, publisher, address,
month, note, key.</td>
</tr>
<tr>
<td><a name="inproceedings"></a><b>inproceedings:</b></td>
<td>An article in a conference proceedings. Required
fields: author, title, booktitle, year. Optional fields:
editor, pages, organization, publisher, address, month,
note, key.</td>
</tr>
<tr>
<td><b>manual: </b></td>
<td>Technical documentation. Required fields: title.
Optional fields: author, organization, address, edition,
month, year, note.</td>
</tr>
<tr>
<td><b>mastersthesis:</b></td>
<td>A Master's thesis. Required fields: author, title,
school, year. Optional fields: address, month, note, key.</td>
</tr>
<tr>
<td><b>misc:</b></td>
<td>Use this type when nothing else fits. Required
fields: none. Optional fields: author, title,
howpublished, month, year, note, key.</td>
</tr>
<tr>
<td><strong>patent:</strong></td>
<td>A patent.</td>
</tr>
<tr>
<td><b>phdthesis:</b></td>
<td>A Ph.D. thesis. Required fields: author, title,
school, year. Optional fields: address, month, note, key.</td>
</tr>
<tr>
<td><a name="proceedings"></a><b>proceedings:</b></td>
<td>The proceedings of a conference. Required fields:
title, year. Optional fields: editor, publisher,
organization, address, month, note, key.</td>
</tr>
<tr>
<td><b>techreport:</b></td>
<td>A report published by a school or other institution,
usually numbered within a series. Required fields:
author, title, institution, year. Optional fields: type,
number, address, month, note, key.</td>
</tr>
<tr>
<td><b>unpublished:</b></td>
<td>A document with an author and title, but not formally
published. Required fields: author, title, note. Optional
fields: month, year, key.</td>
</tr>
</table>

==== Examples ====
<pre><nowiki>
@book{kn:gnus,

AUTHOR = "Donald E. Knudson",
TITLE = "1966 World Gnus Almanac",
PUBLISHER = {Permafrost Press},
ADDRESS = {Novosibirsk} }

<div class="book" id="kn:gnus">
<div class="author">Donald E. Knudson</div>
<div class="title">1966 World Gnus Almanac</div>
<div class="publisher">Permafrost Press</div>
<div class="address">Novosibirsk</div>
</div>

@article{XAi_HSCheng_1994a,

author = "X. Ai and H. S. Cheng",
title = "Influence of moving dent on point {EHL} contacts",
journal = "Tribol. Trans.",
volume = "37",
year = "1994",
pages = "323--335",
}

<div class="article" id="XAi_HSCheng_1994a">
<div class="author">X. Ai and H. S. Cheng</div>
<div class="title">Influence of moving dent on point {EHL} contacts</div>
<div class="journal">Tribol. Trans.</div>
<div class="volume">37</div>
<div class="year">1994</div>
<div class="pages">323--335</div>
</div>
</nowiki></pre>

== OpenURL ==

OpenURL aka [http://www.niso.org/standards/standard_detail.cfm?std_id=783 Z39.88] defines a standard way of bundling citation data in a URL. It is widely deployed in academic libraries around the world to provide access to licensed content via link resolvers such as [http://www.exlibrisgroup.com/sfx_openurl.htm SFX]. The Context Object in Span ([http://ocoins.info/ COinS]) community standard represents one way to embed OpenURLs in XHTML without including a resolver target.

<pre>
<nowiki>
<span class="Z3988" title="ctx_ver=Z39.88-2004&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.issn=1045-4438"></span>
</nowiki>
</pre>

As you can see this isn't very much like semantic XHTML at all. However significant work has gone into defining the set of Key/Encoded Values (KEVs) that can be used in various [http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=ListRecords&metadataPrefix=oai_dc&set=Core:Metadata+Formats types] of citations: [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:book book], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:dissertation dissertation], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:journal journal], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:patent patent]. It would be possible to simply provide a standard XHTML bundling for these keys as a microformat.

=== Example ===

<pre>
<nowiki>

<div class="openurl-journal">
<span class="aulast">Berners-Lee</span>,
<span class="aufirst">Tim</a>; Hendler, James; Lassila, Ora.
"<span class="atitle">The Semantic Web</span>".
<span class="jtitle">Scientific American</span>
<span class="volume">284(<span class="issue">5</a>), pp.
pp. <span class="pages">34-43</a>.
<span class="issn">0036-8733</span>
</div>

</nowiki>
</pre>

Using OpenURL in this way would enable third party applications that could, say grab citation metadata from a blog, and without much work fire it off at your university's or public libraries openurl resolver to see if the article is available via a licensed databases. The benefits [http://www.infotoday.com/newsbreaks/nb050801-1.shtml have] [http://www.ariadne.ac.uk/issue43/chudnov/ been] [http://www.wallandbinkley.com/quaedam/?p=30 noted] [http://hublog.hubmed.org/archives/001163.html elsewhere].

== Z39.80 ==
I'm not sure the best place for a guide to Z39.80 so please add links as you see fit:

[http://www.niso.org/standards/resources/drft4rev.html http://www.niso.org/standards/resources/drft4rev.html]

citation-brainstorming

2005-11-04T19:16:55Z

Tim White:

hreview

2005-10-28T13:31:21Z

Tim White: /* Examples in the wild */

= hReview 0.2 =

hReview is a simple, open, distributed reviews format suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. hReview is one of several [[microformats]] open standards.

__TOC__

== Draft Specification 2005-06-07 ==

=== Editor ===
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]

=== Authors ===
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]
* [http://360.yahoo.com/alidiabali Ali Diab],[http://yahoo.com Yahoo! Inc.]
* [http://spaces.msn.com/members/ianmcallister/ Ian McAllister], [http://microsoft.com/ Microsoft Corporation]
* [http://journals.aol.com/panzerjohn/abstractioneer John Panzer], [http://www.aol.com America Online, Inc.]
* [http://ifindkarma.com/blog Adam Rifkin], [http://labs.commerce.net/ CommerceNet Labs]
* [http://sippey.typepad.com/ Michael Sippey], [http://sixapart.com Six Apart, Ltd.]

== Introduction ==
Numerous web sites publish reviews using a broad variety of schema for all sorts of things from products (movies, music, books), to businesses (restaurants, hotels, stores), to events (concerts, theatre), to people (artists, leaders, celebrities), to places (landmarks, parks), to online resources (web pages, files), to reviews of reviews themselves.

In order to enable and encourage the sharing, distribution, syndication, and aggregation, of reviews, the authors propose the hReview MicroFormat, an open standard for distributed reviews. The authors have researched numerous earlier attempts at ReviewsFormats, and have designed hReview around a simple minimal schema for reviews. Feedback is encouraged on the ["hReviewFeedback"] page.

=== Working Name ===
The name "hReview" is a working name for this microformat. The name was suggested as it shares much with the hCard and hCalendar microformats, despite not having an IETF RFC to reference for a normative schema.

=== Copyright ===
{{MicroformatCopyrightStatement2005}}

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

=== Inspiration and Acknowledgments ===
Thanks to everyone who responded to the open call for implementor participation for hReview. The authors in particular wish to thank the following individuals for their constructive input and feedback: [http://www.richardault.com/ Richard Ault], [http://dannyayers.com Danny Ayers], [http://www.vertexdev.com/~jeff/ Jeffrey Barr],[http://adriancuthbert.blogspot.com/ Adrian Cuthbert],[http://jason.defillippo.com/ Jason DeFillippo], [http://www.hybernaut.com/bdv Brian Del Vecchio], Scott Derringer, [http://budgibson.com/home/ Bud Gibson], [http://joi.ito.com/ Joi Ito], [http://www.kanai.net/weblog/ Gen Kanai],[http://niallkennedy.com/ Niall Kennedy], [http://labs.commerce.net/wiki/index.php/Rohit_Khare Rohit Khare], [http://theryanking.com/ Ryan King], [http://www.jluster.org/ Jonas Luster], [http://epeus.blogspot.com/ Kevin Marks], [http://www.powazek.com/ Derek Powazek], [http://www.judysbook.com/ Jeff Rodenburg], [http://sifry.com/alerts/ David Sifry], [http://jystewart.net/ James Stewart], [http://kung-foo.tv/ Adriaan Tijsseling], [http://www.flashenabled.com/ Phillip Torrone], Thai Tran, [http://w6daily.winn.com/ Phillip Winn], [http://yohei-y.blogspot.com YAMAMOTO Yohei].

=== Scope ===
Reviews consistently share several common fields. Where possible hReview has been based on this minimal common subset.

==== Out of scope ====
Fields that are type-specific have been omitted from hReview. It is important that hReview be kept simple and minimal from the start. Additional features can be added as deemed necessary by practical implementation experience.

The concept of a "universal object identifier", that is, how to identify the same object/item/product across different shopping sites, though something very useful to have, is outside the scope of this format.

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

== Format ==
=== In General ===
The hReview format is based on a set of fields common to numerous review sites and formats in use today on the web. Where possible field names have been chosen based on those defined by the related [[hcard|hCard]] and [[hcalendar|hCalendar]] standards.

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

* hReview
** version. optional. text.
** summary. optional. text.
** item type. optional. product | business | event | person | place | website | url.
** item info. required. (fn || url || photo ) | [[hcard|hCard]] (for person or business).
** reviewer. required. [[hcard|hCard]] | fn | email | url.
** dtreviewed. required. ISO8601 absolute date time.
** rating. optional. integer [1-5], with optional alternate worst (default:1) and/or best (default:5), also integers.
** description. optional. text with optional valid XHTML markup.
** tags. optional. keywords or phrases, using RelTag, each with optional rating.
** permalink. optional.

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

'''version''':: This optional field permits hReview publishers to specify a particular version of hReview that their content uses. By omitting this field, the publisher is stating that implementations may interpret the hReviews according to any version of the hReview specification v0.2 or later. In practice the authors of this specification are comitted to maintaining backward compatibility with content produced using earlier versions of the specification. This field is syntax compatible with, and thus reuses the semantics of "VERSION" as defined in vCard RFC2426 section "3.6.9 VERSION Type Definition". The value of this field for this specification is "0.2".

'''summary''':: This optional field serves as a title for the review itself.

'''item type''':: This optional field "type" provides the type of the item being reviewed, one of the following: product, business, event, person, place, website, url.

'''item info''':: This required field MUST have at a minimum the name ("fn" - the formatted text corresponding to the name) of the item , SHOULD provide at least one URI ("url") for the item, and MAY provide at least one URL to a photo or depiction ("photo") of the item. For items of type person or business, the item info (fn, url, photo) SHOULD be encapsulated in an [[hcard|hCard]]. Unique item IDs (e.g. ISBNs, UPCs) MAY be represented as a URN ("url") for the item.

'''reviewer''':: The person who authored the review. An hCard representing the reviewer SHOULD be provided with full name and URL. Alternatively, just a name, email address, or URL to the person MAY be provided. To specify more than one of those, encapsulate them in an hCard. For anonymous reviews, use "anonymous" (without quotes) for the full name of the reviewer.

'''dtreviewed''':: This required field MUST provide an ISO8601 absolute date time of when the review was written or otherwise authored. This field SHOULD use UTC, but MAY use the time zone offset syntax.

'''rating''':: The rating is an integer from 1 to 5 inclusive indicating a rating for the item, higher indicating a better rating. Optionally a different integral "worst" value and/or "best" value MAY be specified (e.g. 6 from 0-10).

'''description''':: This optional field contains the full text representing the written opinion of the reviewer. The field MAY include valid XHTML markup (e.g. paragraphs). User agents SHOULD preserve any markup. Multiple descriptions or section descriptions (e.g. pros and cons, plusses and minusses) SHOULD be included in the description field.

'''tags''':: Tags are represented using a list of keywords or phrases (using the [[rel-tag|RelTag]] microformat for each individual keyword or phrase tag) that the reviewer associates with the item. The reviewer MAY optionally provide a tag-specific rating inside each [[rel-tag|RelTag]], e.g. ambience:5. Tag-specific ratings by default use the same range as an overall rating for the item if present, and MAY also have a custom worst...best range specified. Authors MAY enclose all tags for a review inside an element with a specific classname, e.g. "categories" (from vCard RFC2426 and iCalendar RFC2445), but are not required to do so.

'''permalink''':: This optional field is a URL for the hReview. In addition to using the <code><a href></code> tag for this field, the attribute <code>rel="self bookmark"</code> MUST be used to indicate that the hyperlink is a permalink for the review itself. If the hyperlink already contains a <code>rel</code> attribute, then the values <code>self</code> and <code>bookmark</code> MUST be included among the space-separated set of values in the attribute. Indexers MAY treat the permalink of a review as a unique ID in order to identify and collate the same review from multiple sources (such as indexing a page multiple times). The permalink MAY also be used to indicate or imply the origin of the review. Authors MAY use the classname of "permalink" on the element representing the permalink, but are not required to do so.

The following field names have been reused from the [[hcard|hCard]] and [[hcalendar|hCalendar]] microformats: <code>version, summary, fn, url, email, photo, description, categories</code>. In addition, items and reviewers described by hCards MAY contain any hCard field. The rel value "self" has been reused from the [http://atompub.org/2005/07/11/draft-ietf-atompub-format-10.html Atom 1.0 specification].

=== More Semantic Equivalents ===

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For any "url", use <code><a class="url" href="...">...</a></code> inside the element with class="hreview" in hReview.
* Similarly, any "email", use <code><nowiki><a class="email" href="mailto:...">...</a></nowiki></code>
* And for "photo", use <code><img class="photo" src="..." alt="Photo of ..." /></code>

* Ratings are often presented either as a set of images or characters, e.g. "***". For these, the <code><abbr></code> element is particularly useful, as such characters are an abbreviation for the precise rating, e.g. <code><abbr class="rating" title="3">***</abbr></code>. This is further explored in the next section.

==== Language ====
* To explicitly convey the natural language that an hReview is written in, use the standard (X)HTML 'lang' attribute on the element with class="hreview", e.g. <code><div class="hreview" lang="en"> ... </div></code> If portions of an hReview (e.g. the item name) are in a different language, use the 'lang' attribute on those portions.
* hReview processors which need to handle the language of reviews MUST process the standard (X)HTML 'lang' attribute as specified.

=== Human vs. Machine Readable ===
If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

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

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

* By marking up a review with the hReview microformat, the expectation is communicated that the review MAY be indexed. This has no impact on the copyright of the review itself.
* The enumerated list of item types is under development and may be extended.
* Each type may have custom hReview fields that follow the common set.
* Additional details about a particular item should be specified with the rest of the item's info at the URL provided for the item.
* Most rating systems use the range 1 to 5, and most of those represent the rating as a number of stars. Sites may use whatever graphic they wish to represent the rating.

== Examples ==
Here are a few examples of reviews from current web sites, and how they could be easily enhanced to support the hReview structured review microformat.

=== Restaurant reviews ===

Here is an example of a simple online restaurant review:

<pre><nowiki>
<div>
<span>5 stars out of 5 stars</span>
<h4>Crepes on Cole is awesome</h4>
<span>Reviewer: <span>Tantek</span> - April 18, 2005</span>
<blockquote><p>
Crepes on Cole is one of the best little creperies in San Francisco.
Excellent food and service. Plenty of tables in a variety of sizes
for parties large and small. Window seating makes for excellent
people watching to/from the N-Judah which stops right outside.
I've had many fun social gatherings here, as well as gotten
plenty of work done thanks to neighborhood WiFi.
</p></blockquote>
<p>Visit date: <span>April 2005</span></p>
<p>Food eaten: <span>Florentine crepe</span></p>
</div>
</nowiki></pre>

Adding hReview to this review is quite simple:

<pre><nowiki>
<div class="hreview">
<span><span class="rating">5</span> out of 5 stars</span>
<h4 class="summary"><span class="item fn">Crepes on Cole</span> is awesome</h4>
<span>Reviewer: <span class="reviewer fn">Tantek</span> -
<abbr class="dtreviewed" title="20050418T2300-0700">April 18, 2005</abbr></span>
<blockquote class="description"><p>
Crepes on Cole is one of the best little creperies in San Francisco.
Excellent food and service. Plenty of tables in a variety of sizes
for parties large and small. Window seating makes for excellent
people watching to/from the N-Judah which stops right outside.
I've had many fun social gatherings here, as well as gotten
plenty of work done thanks to neighborhood WiFi.
</p></blockquote>
<p>Visit date: <span>April 2005</span></p>
<p>Food eaten: <span>Florentine crepe</span></p>
</div>
</nowiki></pre>

Note that some of the properties of this sample review are not captured by hReview (visit date, food eaten). This is deliberate per the scope of keeping hReview minimal and simple.

This sample hReview could be rendered like this:

5 stars out of 5 stars<br />
'''Crepes on Cole is awesome'''<br />
Reviewer: Tantek - April 18, 2005<br />

<blockquote>Crepes on Cole is one of the best little creperies in San Francisco. Excellent food and service. Plenty of tables in a variety of sizes for parties large and small. Window seating makes for excellent people watching to/from the N-Judah which stops right outside. I've had many fun social gatherings here, as well as gotten plenty of work done thanks to neighborhood wifi.</blockquote>

Visit date: April 2005<br />
Food eaten: Florentine crepe<br />

==== Multidimensional Restaurant Review ====
Some restaurant reviews indicate ratings for different aspects of the restaurant. Such details are represented in hReview using tagged ratings. In addition, note the inline tags inside the description of this review.

Here is one such review in text format:

Cafe Borrone

1010 El Camino Real, Menlo Park, CA 94025, +1-650-327-0830;
cafeborrone.com

Food: 18/30; Ambience: 19/30; Service: 15/30; Price: $$...

This cafe is a welcoming oasis on the Peninsula. It even has a fountain
outside which cloaks the nearby sounds of El Camino traffic. Next door to a
superb indy bookstore, Cafe Borrone is an ideal spot to grab a coffee or a
snack to accompany a newly purchased book or imported periodical. Soups and
sandwich specials rotate daily. The corn chowder with croutons and big
chunks of cheese goes especially well with a freshly toasted mini-baguette.
Evenings are often crowded and may require sharing a table with a perfect
stranger. Espresso afficionados will appreciate the Illy coffee. Noise
levels can vary from peaceful in the late mornings to nearly overwhelming on
jazz band nights.

As an hReview:

<pre><nowiki>
<div class="hreview">
<div class="item vcard">
<div class="fn org summary">Cafe Borrone</div>
<span class="adr">
<span class="street-address">1010 El Camino Real</span>,
<span class="locality">San Francisco</span>,
<span class="region">CA</span>
<span class="postal-code">94025</span>,
</span>
<span class="tel"><span class="voice work">+1-650-327-0830</span></span>;
<a class="url" href="http://cafeborrone.com">cafeborrone.com</a>
</div>
<ul class="categories">
<li><a href="http://en.wikipedia.org/wiki/Food" rel="tag">
Food: <span class="rating">18</span>/<span class="best">30</span></a>;</li>
<li><a href="http://flickr.com/photos/tags/Ambience" rel="tag">
Ambience: <span class="rating">19</span>/<span class="best">30</span></a>;</li>
<li><a href="http://en.wikipedia.org/wiki/Service" rel="tag">
Service: <span class="rating">15</span>/<span class="best">30</span></a>;</li>
<li><a href="http://en.wikipedia.org/wiki/Price" rel="tag">
Price: <abbr class="rating" title="2">$$</abbr>...</a></li>
</ul>
<blockquote class="description"><p>
This <abbr class="type" title="business">
<a href="http://en.wikipedia.org/wiki/cafe" rel="tag">cafe</a></abbr>
is a welcoming oasis on the Peninsula.
It even has a fountain outside which nearly eliminates
the sounds of El Camino traffic. Next door to a superb indy bookstore,
Cafe Borrone is an ideal spot to grab a
<a href="http://en.wikipedia.org/wiki/coffee" rel="tag">coffee</a>
or a meal to accompany a newly purchased book or imported periodical.
<a href="http://technorati.com/tag/soup" rel="tag">Soups</a> and
<a href="http://technorati.com/tag/sandwich" rel="tag">sandwich</a>
specials rotate daily. The corn chowder with croutons and big chunks of cheese
goes especially well with a freshly toasted mini-baguette. Evenings are
often crowded and may require sharing a table with a perfect stranger.
<a href="http://flickr.com/photos/tags/espresso" rel="tag">Espresso</a>
afficionados will appreciate the
<a href="http://en.wikipedia.org/wiki/Illy" rel="tag">Illy</a> coffee.
Noise levels can vary from peaceful in the late mornings to nearly overwhelming on
<a href="http://en.wikipedia.org/wiki/jazz" rel="tag">jazz</a> band nights.
</p></blockquote>
Review (<a href="http://microformats.org/wiki/hreview">
hReview v<span class="version">0.2</span></a>)
by <span class="reviewer">anonymous</span>,
<abbr class="dtreviewed" title="20050428T2130-0700">April 28th, 2005</abbr>.
</div>
</nowiki></pre>

With an accompanying CSS style sheet like:

<pre><nowiki>
a.url { display:block }
ul.categories { margin:1em 0; padding:0 }
.categories li { display:inline }
</nowiki></pre>

This hReview could be presented similar to the original text:

Cafe Borrone<br />
1010 El Camino Real, Menlo Park, CA 94025, +1-650-327-0830;<br />
[http://cafeborrone.com/ cafeborrone.com]<br />
<br />
[http://en.wikipedia.org/wiki/Food Food: 18/30];
[http://flickr.com/photos/tags/Ambience Ambience: 19/30];
[http://en.wikipedia.org/wiki/Service Service: 15/30];
[http://en.wikipedia.org/wiki/Price Price: $$...]<br />

<blockquote>This [http://en.wikipedia.org/wiki/cafe cafe] is a welcoming oasis on the Peninsula. It even has a fountain outside which cloaks the nearby sounds of El Camino traffic. Next door to a superb indy bookstore, Cafe Borrone is an ideal spot to grab a [http://en.wikipedia.org/wiki/coffee coffee] or a snack to accompany a newly purchased book or imported periodical. [http://technorati.com/tag/soup Soups] and [http://technorati.com/tag/sandwich sandwich] specials rotate daily. The corn chowder with croutons and big chunks of cheese goes especially well with a freshly toasted mini-baguette. Evenings are often crowded and may require sharing a table with a perfect stranger. [http://flickr.com/photos/tags/espresso Espresso] afficionados will appreciate the [http://en.wikipedia.org/wiki/Illy Illy] coffee. Noise levels can vary from peaceful in the late mornings to nearly overwhelming on [http://en.wikipedia.org/wiki/jazz jazz] band nights.</blockquote>

Review ([http://microformats.org/wiki/hreview hReview v0.2]) by anonymous, April 28th, 2005.

=== Product review ===
Here is an example of a product review:

<pre><nowiki>
<div>
<a href="http://www.amazon.com/exec/obidos/ASIN/B000089CJI/">
<img src="http://images.amazon.com/images/P/B000089CJI.01._SCTHUMBZZZ_.jpg"
alt="Album cover photo: The Postal Service: Give Up." />
The Postal Service: Give Up</a>
<blockquote><p>
"The people thought they were just being rewarded for treating others
as they like to be treated, for obeying stop signs and curing diseases,
for mailing letters with the address of the sender... Don't wake me,
I plan on sleeping in..."
</p><p>
"Nothing Better" is a great track on this album, too...
</p></blockquote>
(*****)
</div>
</nowiki></pre>

Adding hReview to this review is also quite simple, but in this case requires a few more elements for the rating and reviewer which are required by hReview:

<pre><nowiki>
<div class="hreview">
<a class="item url" href="http://www.amazon.com/exec/obidos/ASIN/B000089CJI/">
<img src="http://images.amazon.com/images/P/B000089CJI.01._SCTHUMBZZZ_.jpg"
alt="Album cover photo: The Postal Service: Give Up. "
class="photo" />
<span class="fn">The Postal Service: Give Up</span></a>
<blockquote class="description"><p>
"The people thought they were just being rewarded for treating others
as they like to be treated, for obeying stop signs and curing diseases,
for mailing letters with the address of the sender... Don't wake me,
I plan on sleeping in..."
</p><p>
"Nothing Better" is a great track on this album, too...
</p></blockquote>
(<abbr class="rating" title="5">*****</abbr>)
<p class="reviewer vcard">Review by
<a class="url fn" href="http://ifindkarma.com/blog/">Adam Rifkin</a>,
<abbr class="dtreviewed" title="200502">February 2005</abbr>
</p>
</div>
</nowiki></pre>

And this hReview might be presented like this:

[Album cover photo: ]
[The Postal Service:]
[ Give Up ]

The Postal Service: Give Up

<blockquote>"The people thought they were just being rewarded for treating others as they like to be treated, for obeying stop signs and curing diseases, for mailing letters with the address of the sender... Don't wake me, I plan on sleeping in..."</blockquote>

<blockquote>"Nothing Better" is a great track on this album, too... </blockquote>

(*****)

Review by Adam Rifkin, February 2005.

=== Movie Review ===
Finally, here is an example of a movie review.

<pre><nowiki>
<div>
<span>anonymous, April 18th, 2005</span>
<div>
<a lang="zh" href="http://www.imdb.com/title/tt0299977/">
Ying Xiong (<span lang="en">HERO</span>)
</a>
</div>
<div>Rating: 4 out of 5</div>
<blockquote><p>
This movie has great visuals and music.
</p></blockquote>
</div>
</nowiki></pre>

With hReview:

<pre><nowiki>
<div class="hreview">
<span class="reviewer">
<span class="fn">anonymous</span>,
<abbr class="dtreviewed" title="20050418">April 18th, 2005</abbr>
</span>
<div class="item">
<a lang="zh" class="url fn" href="http://www.imdb.com/title/tt0299977/">
Ying Xiong (<span lang="en">HERO</span>)
</a>
</div>
<div>Rating: <span class="rating">4</span> out of 5</div>
<blockquote class="description"><p>
This movie has great music and visuals.
</p></blockquote>
</div>
</nowiki></pre>

Which could be presented like this:

anonymous, April 18th, 2005<br />
Ying Xiong (HERO)<br />
Rating: 4 out of 5<br />

This movie has great music and visuals.

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

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

* [http://blog.ftwr.co.uk/ Peter Westwood] has written an [http://blog.ftwr.co.uk/archives/2005/10/03/blubeckers-hampton-court/ hReview of Blubeckers Hampton Court]
* [http://dougal.gunters.org/blog/ Dougal] has published an [http://dougal.gunters.org/blog/2005/08/03/french-vanilla-latte hReview of Wolfgang Puck’s Gourmet French Vanilla Latte].
* [http://www.dinnerbuzz.com/ Dinnerbuzz] is a great site for posting tagged reviews of restaurants, and they publish and summarize all their reviews in hReview!
* [http://soldierant.net/ Bryce Glass] posted an [http://soldierant.net/archives/2005/06/product_review.html hReview of the Uniden ELBT 595 Bluetooth Cordless Phone].
* dda posted an [http://sungnyemun.org/wordpress/?p=20 hReview of hReview] :)
* An [http://tbp.xomerang.com/?p=3 hReview of Caffè Camardo coffee].
* [http://loadaveragezero.com/hnav/contact.php Douglas Clifton] posted [http://loadaveragezero.com/#May-12-2005 comments] regarding adapting his list of ~800 [http://loadaveragezero.com/app/drx Developer Resources] as a format for evaluating hReview.
* [http://www.oliverbrown.me.uk/ Oliver Brown] [http://www.oliverbrown.me.uk/2005/05/09/sitereviewsorg-supports-hreview-i-think/ has announced] that his [http://en-us.sitereviews.org/ SiteReviews.org] (which reviews websites) publishes its reviews using hReview, e.g. here is the [http://en-us.sitereviews.org/review-photomatt.net review on SiteReviews.org for photomatt.net].
* [http://www.myelin.co.nz/post/ Phillip Pearson] is publishing hReviews in the [http://coffee.gen.nz/rss/reviews RSS feed of cafe reviews] on his [http://coffee.gen.nz/ kiwi coffee review site], which of course has the reviews in HTML with embedded hReview markup as well.
* [http://station11.net/ticker/ Kjell] is publishing his link blog as a [http://station11.net/ticker/ list of hReviews].
* [http://epeus.blogspot.com/ Kevin Marks] has [http://epeus.blogspot.com/2005_04_01_epeus_archive.html#111484565269684374 published two hReviews] and used unicode "star" characters for his ratings!
* JamesStewart is publishing hReviews in the location pages at his [http://grwifi.net Grand Rapids WiFi site].
* [http://soldierant.net/ Soldier Ant] has [http://soldierant.net/archives/2005/06/product_review.html reviewed a cordless phone].
* [http://www.happenchance.co.uk/ Paul Livingstone] uses hreview to voice his opinion on [http://www.happenchance.co.uk/archives/2005/07/war_of_the_worl.php books], [http://www.happenchance.co.uk/archives/2005/03/im_going_to_fin.php movies] and [http://www.happenchance.co.uk/archives/2005/05/eels_carling_ac.php music].
* [http://www.stuffandnonsense.co.uk/ Andy Clarke] uses hReview for his [http://www.stuffandnonsense.co.uk/general/recommended-reading.html recommended reading list]
* [http://www.tjameswhite.com/blog Tim White] has begun implementing hReviews at [http://reviews.gale.com at work].

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

The following implementations have been developed which either generate or parse hReviews. If you have an hReview 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://www.goodpic.com/mt/aws/index_us.html Goodpic] has written:
** [http://www.goodpic.com/mt/aws/index_us.html hReview creator for Amazon.com products]
** [http://www.goodpic.com/mt/aws/index_uk.html hReview creator for Amazon.co.uk products]
** [http://www.goodpic.com/mt/aws/index_uk.html hReview creator for Amazon.co.jp products]
** be sure to choose the "hRview" tab from among the choices on the page that says "You can choose from more than 30 designs, please click the tab to select categories."
* See the microformats.org [http://microformats.org/code/hreview/creator hReview creator]
* [http://www.eigaseikatu.com/ Eigaseikatu], one of the largest movie community sites in Japan, provides [http://www.eigaseikatu.com/hreview/ hReview creator] for movie review.
* [http://sungnyemun.org/wordpress/?p=22 hReview plugin for WordPress]
* [http://theryanking.com/ Ryan King] has an [http://theryanking.com/microformats/hreview-creator.html hReview Creator].
* [http://rvu.ning.com/ Rvu] is a [http://ning.com Ning] app that lets you write reviews of reviews and publishes them in hReview

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[hcalendar|hCalendar]]
* [[rel-tag]]
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]
* [http://www.ietf.org/rfc/rfc3986.txt RFC3986]
* [http://atompub.org/2005/07/11/draft-ietf-atompub-format-10.html Atom 1.0]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.ietf.org/rfc/rfc3667.txt RFC3667]
* [http://www.ietf.org/rfc/rfc3668.txt RFC3668]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other reviews efforts. See [[reviews-formats]].
* Contributed from http://developers.technorati.com/wiki/hReview.

==== Similar Work ====
* [[xoxo]]

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

=== Changes from v0.1 ===
The following changes have been made in hReview v0.2:
# '''version'''. Added optional "version" field.
# '''language'''. Made explicit the reuse of (X)HTML 'lang' attribute to convey natural language information.
# '''tags requirement removed'''. Removed requirement of classname "tags" for the tags field, and thus removed the requirement to have an explicit tags field at all, permitting tags anywhere inside the hReview, e.g. inside the description.
# '''permalink requirement removed'''. Removed requirement of classname "permalink", as it is unnecessary, given that the permalink field explicitly requires a hyperlink with rel values of "self" and "bookmark".
# Updated examples accordingly.

== Discussions ==

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

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

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