Microformats Wiki - User contributions [en]

citation

2006-10-25T10:46:28Z

Ed Summers: pointed dublincore reference to the citation work that was recently approved

<h1> Citation microformat efforts </h1>

This wiki page outlines the overall effort to develop a citation microformat. We are documenting current examples of cites/citations on the web today, their implicit/explicit schemas, and current cite/citation formats, with the intent of deriving a cite microformat from that research.

__TOC__

== Authors ==
* [http://tantek.com/ Tantek Çelik]
* [http://suda.co.uk/ Brian Suda]
* [http://www.inkdroid.org Ed Summers]

== Copyright ==
{{MicroFormatCopyrightStatement2004}}

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

== Example Citations ==
[[citation-examples|Citation Examples]] are citations found in the wild that could benefit from semantic mark-up. This is a growing list of examples from all sorts of places including W3C specifications, RFCs and others. These are the examples which will determine the schema for the citation microformat.

== Known Citation Formats ==
The [[citation-formats|Citation Formats Page]] will be a running tab of known formats for publishing citations.

Eventually, i would like to see a chart of how each value from the implicit schema determined by the [[citation-examples]] is represented in each format, and what formats have additional properties that do not map between them. (For example, Format1 calls 'author' 'author', in format2 'author' is called 'writer'. etc)

== To Do ==
* [http://microformats.org/wiki/existing-classes Using existing class names] and creating new names, create property names for the profile
* Based on implicit schemas in [[citation-examples]], and terms from one or more [[citation-formats]], do some [[citation-brainstorming]] for a simple citation microformat.
* Create additional strawman proposals

== Modularity ==
My hope for this microformat is that it can be a sort of module that can be used in other microformats. Once this is developed and flushed out, citation references could easily be used for publications on a Resume/CV, therefore the citation microformat would be a module (subset) of all the possible Resume Values.

Other Microformats that could use the Citation Module
* [[hresume|hResume]]
* [[work-of-art]]

Other Microformats that the Citation Module will use
* [http://microformats.com/wiki/hcard hCard] encodings for things like Author, Publisher (people and companies)
* [http://microformats.org/wiki/hatom hAtom] encodings as a possible container, and author/date-time properties
* [http://microformats.org/wiki/rel-tag rel-tag] encoding for keywords
* [http://microformats.org/wiki/rel-license rel-license] encoding for copyright

== References ==
=== Informative References ===
* [http://ocoins.info/ COinS]
* [http://xmlresume.sourceforge.net/ XMLResume]: if part of the drive for citations is for publications for a resume/CV then some of this information could be useful
* [http://www.citeulike.org/ CiteUlike] is a free service to help academics to share, store, and organise the academic papers they are reading
* [http://www.ariadne.ac.uk/issue43/chudnov/ OpenURL] with Autodiscovery
* [http://cipolo.med.yale.edu/mailman/listinfo/gcs-pcs-list "Gather, Create, Share" and "Personal Collection Systems" memes, and systems implementing either or both]
* [http://www.loc.gov/standards/mods/ Metadata Object Description Schema] developed by the Library of Congress
* [http://www.dublincore.org/documents/dc-citation-guidelines/ Guidelines for Encoding Bibliographic Citation Information in Dublin Core Metadata]
* [http://www.ecst.csuchico.edu/~jacobsd/bib/formats/bibtex.html BibTeX reference] from Dana Jacobsen
* [http://www.refman.com/support/risformat_intro.asp RIS Format Specification] from Thomson ResearchSoft, makers of ReferenceManager
* [http://www.zotero.org/ Zotero] - "Firefox extension to help you collect, manage, and cite your research sources"

== See Also ==
* [[citation-examples]]
* [[citation-examples-markup]]
* [[citation-formats]]
* [[citation-brainstorming]]
* [[citation-faq]]

citation-examples-markup

2006-10-08T03:46:31Z

Ed Summers: added ed

<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]
* [http://inkdroid.org Ed Summers]
* 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] ===
* subtitle
* title
* author
* Image
* pubdate
* pages
* volumes
* trimsize (book dimentions 8.5x11)
* Format
* Price
* ISBN

=== 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" ...>(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".../>
</a>
<a id="hlSharePage" title="Email this page to a friend" href="/books/sendform.asp?sku=GR2847"...>
<img title="Email this page to a friend" src="/_net.templates/roundedButton.aspx?ButtonText=Email".../>
</a>
<a id="hlPrintPage" title="Version of this page optimized for printing" href="/catalog/GR2847.aspx?print=1" ...>
<img title="Version of this page optimized for printing" src="/_net.templates/roundedButton.aspx?ButtonText=Print".../>
</a>
<a id="hlWorldCat" href="http://worldcatlibraries.org/wcpa/isbn/0313328471"...>
<img src="/images/world_catalog.gif".../>
</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"
... 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 ... class="productdetailhead"><span id="volumeslabel" class="productdetailhead">Volumes</span></td>
<td ... class="productdetailbody"><span id="volumes" class="productdetailbody">1</span></td>
(ABC-CLIO)
</pre>

=== ISBN: ===
<pre>
<td class="productdetailhead" ...><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" ... 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" ... 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...>
<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...>
<tr>
<td...><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>
..
<table...>
<tr>
<td ...>
<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 ...>
<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...>
<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>

== PubMed Medical Journal Example ==

Still another example of markup in the wild, coming from a search for "pancreas" in the New England Journal of Medicine from pubmed.org.

Note the title attribute with the expanded version of the canonical abbreviation for the journal.

<pre><nowiki>
<tr>
<td ...>
<a href="/entrez/query.fcgi?cmd=Retrieve&db=pubmed&dopt=Abstract&list_uids=15371579&itool=iconnoabstr&query_hl=2&itool=pubmed_docsum">
<img alt="No abstract" id="No abstract_15371579" ... Title="No abstract">
</a>
</td>
<td ...>Cystic neoplasms of the pancreas.<br>
<font size="-1">
<span title="The New England journal of medicine.">N Engl J Med.</span>
2004 Sep 16;351(12):1218-26. Review. No abstract available. <br>
PMID: 15371579 [PubMed - indexed for MEDLINE]
</font>
</td>
</nowiki></pre>

== Wikipedia Examples ==

=== Wikipedia Book ===

<pre><nowiki>
<li id="_note-8"><b><a href="#_ref-8" title="">^</a></b>
<i>Tuva Or Bust!</i>, Ralph Leighton, W. W. Norton & Company, 2000,
<a href="/w/index.php?title=Special:Booksources&isbn=0393320693"
class="internal">ISBN 0393320693</a>
</li>
</nowiki></pre>

=== Wikipedia Journal Article ===

<pre><nowiki>
<li id="_note-science1982-Dickerson">
<b><a href="#_ref-science1982-Dickerson_0" title="">^</a></b>
<cite style="font-style:normal">Dickerson et al. (1982). "The Anatomy of A-, B-, and Z-DNA".
<i>Science</i> <b>216</b>: 475-485. DOI: 10.1126/science.7071593.</cite>
<sup><a href="..." class="external text" title="...">PubMed</a></sup></li>
</nowiki></pre>

=== Wikipedia Court Case ===

<pre><nowiki>
<tr>
<td><i><a href="/wiki/Perfect_10_v._Google_Inc" title="Perfect 10 v. Google Inc">Perfect 10 v. Google Inc</a></i></td>
<td>CASE NO. CV 04-9484 AHM (SHx)</td>
<td><a href="/wiki/Central_District_of_California" title="Central District of California">CDCA</a> 2006</td>
<td>Thumbnails in Web searches that impinged upon market for images of that size were not fair use.</td>
</tr>
</nowiki>
</pre>

=== Wikipedia US Law ===

<pre><nowiki>
<li><cite id="endnote_FISA" style="font-style: normal;">
<a href="#ref_FISA" title=""><b>↑</b></a></cite> 
<a href="http://www.law.cornell.edu/uscode/html/uscode50/usc_sup_01_50_10_36.html"
class="external text" title="...">50 U.S.C Chapter 36 Foreign Intelligence Surveillance</a>
The complete text of the Foreign Intelligence Surveillance Act
</li>
</nowiki></pre>

The sections of the law are cited inline, without markup, as "50 U.S.C. §1801(a) (4),(5),(6)" for example.

=== Wikipedia Conference Presentation ===

<pre><nowiki>
<h3>Conference presentation by Pillar</h3>
<ul>
<li>
<a href="http://www.duke.edu/web/tiss/archives/conferencerecords/media/Pillar.htm"
class="external text" title="...">Foreign and Domestic Publics and the Counter-terrorism Effort</a>
(Duke University, 21-2 March 2003).</li>
</ul>
</nowiki>
</pre>

=== Wikipedia Primary Historical Source ===

<pre><nowiki>
<li>U.S. War Dept., <a href="http://cdl.library.cornell.edu/moa/browse.monographs/waro.html"
class="external text" title="...">
<i>The War of the Rebellion: a Compilation of the Official Records of the Union and Confederate Armies</i></a>,
U.S. Government Printing Office, 1880–1901. 70 very large volumes of letters and reports written by both armies.
Online at <a href="http://cdl.library.cornell.edu/moa/browse.monographs/waro.html"
class="external autonumber" title="...">[6]</a>
</li>
</nowiki>
</pre>

== EPrints.org generated output ==

EPrints uses the DC terms for information in the head element of an entry:

<pre><nowiki>
<head>
<title>ECS EPrints Service - Winnowing Ontologies based on Application Use</title>
<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC" />
<meta content="Winnowing Ontologies based on Application Use" name="DC.title" />
<meta content="Alani, Harith" name="DC.creator" />
<meta content="Harris, Stephen" name="DC.creator" />
<meta content="O'Neil, Ben" name="DC.creator" />
<meta content="The requirements of specific ... that ontology." name="DC.description" />
<meta content="2006-01-01" name="DC.date" />
<meta content="Conference or Workshop Item" name="DC.type" />
<meta content="http://eprints.ecs.soton.ac.uk/12070/" name="DC.identifier" />
<meta content="pdf http://eprints.ecs.soton.ac.uk/12070/01/Alani-final.pdf" name="DC.format" />
<link title="Full Text (application/pdf)" href="http://eprints.ecs.soton.ac.uk/12070/01/Alani-final.pdf"
class="fulltext" type="application/pdf" rel="alternate" />
</nowiki></pre>

And the following markup for the page's HTML:

<pre><nowiki>
<td valign="top"><div class="page">
<h1 class="pagetitle">
<span class="field_title">Winnowing Ontologies based on Application Use</span></h1>
<p class="intro">
<span class="citation">
<span class="field_authors">Alani, H., Harris, S. and O'Neil, B.</span>
(<span class="field_year">2006</span>)
<span class="field_title">Winnowing Ontologies based on Application Use</span>.
In <i>Proceedings of
<span class="field_conference">3rd European Semantic Web Conference (ESWC)</span></i>,
<span class="field_confloc">Budva, Montenegro</span>.
</nowiki></pre>

== BibDesk default HTML export example ==

Due to some recent improvements, BibDesk allows extensive user customization of its HTML output.
It has had an HTML template system since 2004, and the default template hasn't changed much since then.
Here is the default template, which I wrote long before I knew what little I know now of semantic HTML - Mike.

<pre><nowiki>
<div class="content">
<h1><$fileName.lastPathComponent/></h1>
<dl>
<dt class="Key" id="<$citeKey/>"><$citeKey/><dt />
<dd class="Pub">
<span class="Title"><$fields.Title/></span><br />
<span class="Author"><$pubAuthorsForDisplay/></span><br />
<span class="Journal"><$fields.Journal/></span> 
<span class="Volume"><$fields.Volume/></span> 
<span class="Pages"><$fields.Pages/></span> 
(<span class="Date"><$fields.Year/></span>)<br />
<span class="Url"><a href="<$fields.Url/>"><$fields.Url/></a></span><br />
<div class="Abstract"><$fields.Abstract/></div>
<dd />
</dl>
</div>
</nowiki></pre>

Here's a popular modification to the default template, also from 2004, which was used to make this [http://craftsrv1.epfl.ch/~cherubini/extranet/bib/CSCL.bib.html annotated reading list].

<pre><nowiki>
<p class="trigger">
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr>
<td width="20%"><span class="Author"><$pubFields.Author/></span></td>
<td width="5%"><span class="Year"><$pubFields.Year/></span></td>
<td width="55%"><span class="Title"><$pubFields.Title/></span></td>
<td width="10%"><span class="url"><$pubType/></span></td>
</tr>
</table>
</p>
<div>
<span class="url">
<a href="<$pubFields.Url/>"> <img src="pdf_icon.gif" border="0"> <$citeKey/> ~ <$pubFields.Url/></a>
</span>

<p class="Annote">Abstract:<br><$pubFields.Abstract/>
<br>Notes: <br><$pubFields.Annote/><br>
<br>Keywords: <$pubFields.Keywords/>
<br>BibTeX: <$bibTeXString/> <br>
<br><$RTFValue/>
</p>
</div>
</nowiki></pre>

Note that the tags that look like <$foo/> are templating entries and are replaced by values from each cited publication object.

== OCLC WorldCat Online ==

=== Book ===

<pre>
<nowiki>

<div id="item">
<table cellspacing="0">
<tr>
<td class="illustration"><img src="/wcpa/servlet/DCARead?standardNo=0062515861&standardNoType=1" alt="Weaving the Web : the original design and ultimate destiny of the World Wide Web by its inventor " /></td>
<td class="info">
<h1 class="title"> Weaving the Web : the original design and ultimate destiny of the World Wide Web by its inventor </h1>
<p class="author"><strong>by <a href="/search?q=au%3ATim+Berners-Lee&qt=hot_author" title="Search for more by this author">Tim Berners-Lee</a>; 
<a href="/search?q=au%3AMark+Fischetti&qt=hot_author" title="Search for more by this author">Mark Fischetti</a></strong></p>
<ul class="detailed">
<li class="type"><strong>Type: </strong>English : <img src="/wcpa/images/icon-bks.gif" height=16 width=16 alt="" title="Book" class="icn"/> <nobr>Book
</nobr><nobr></nobr></li>
<li class="publisher"><strong>Publisher: </strong> San Francisco : HarperSanFrancisco, ©1999.</li>
<li class="isbn"><strong>ISBN: </strong>0062515861 006251587X</li>
<li class="oclc"><strong>OCLC: </strong>41238513</li>
</ul><ul class="subjects"><li><strong>Subjects: </strong><a href="/search?q=su%3AWorld+Wide+Web+History.&qt=hot_subject" title="Search for more with this subject">World Wide Web -- History.</a> | <a href="/search?q=su%3ABerners-Lee%2C+Tim.&qt=hot_subject" title="Search for more with this subject">Berners-Lee, Tim.</a> | <a href="/search?q=su%3ABerners-Lee%2C+Tim.&qt=hot_subject" title="Search for more with this subject">Berners-Lee, Tim.</a> | <a HREF="/oclc/41238513?tab=subjects" title="More ...">More ...</a></li></ul>
</td>
<td class="bookmark">
<a href="javascript:bookmarksite(document.title, 'http://www.worldcatlibraries.org/oclc/41238513');" onmouseover="MM_displayStatusMsg('Bookmark This Page');return document.MM_returnValue;" onmouseout="MM_displayStatusMsg('');return document.MM_returnValue;">Bookmark</a> | <a href="/oclc/41238513">Permalink</a>
<br><br><span class="Z3988" title="url_ver=Z39.88-2004&rfr_id=info:sid/worldcatlibraries.org:worldcat&rft_val_fmt=info:ofi/fmt:kev:mtx:book&rft_ref_fmt=info:ofi/fmt:xml:xsd:oai_dc&rft_ref=http://partneraccess.oclc.org/wcpa/servlet/OUDCXML?oclcnum=41238513&rft_id=info:oclcnum/41238513&rft_id=urn:ISBN:0062515861&rft_id=urn:ISSN:&rft.aulast=Berners-Lee&rft.aufirst=Tim&rft.auinitm=&rft.btitle=Weaving+the+Web+%3A+the+original+design+and+ultimate+destiny+of+the+World+Wide+Web+by+its+inventor++&rft.atitle=&rft.date=&rft.tpages=&rft.isbn=0062515861&rft.aucorp=&rft.place=San+Francisco&rft.pub=HarperSanFrancisco&rft.edition=1st+ed.&rft.series=&rft.genre=book"></span>
</td>
</tr>
</table>
</div>

</nowiki>
</pre>

=== Journal ===

<pre>
<nowiki>

<div id="item">
<table cellspacing="0">
<tr>
<td class="info">
<h1 class="title"> Cataloging & classification quarterly.</h1>
<ul class="detailed">
<li class="type"><strong>Type: </strong>English : <img src="/wcpa/images/icon-ser.gif" height=16 width=16 alt="" title="Serial Publication" class="icn"/> <nobr>Serial Publication
</nobr> : <nobr>Periodical</nobr>
<nobr><span title="Internet Resource"><img height=16 width=16 border=0 align="absmiddle" src="/wcpa/images/icon-url.gif" alt="Internet Resource"> Internet Resource</span>
</nobr></li>
<li class="publisher"><strong>Publisher: </strong> New York, N.Y. : Haworth Press, [©1981]-</li>
<li class="isbn"><strong>ISSN: </strong>0163-9374 1544-4554</li>
<li class="oclc"><strong>OCLC: </strong>4538259</li>
</ul><ul class="subjects"><li><strong>Subjects: </strong><a href="/search?q=su%3ACataloging+Periodicals.&qt=hot_subject" title="Search for more with this subject">Cataloging -- Periodicals.</a> | <a href="/search?q=su%3AClassification+Books+Periodicals.&qt=hot_subject" title="Search for more with this subject">Classification -- Books -- Periodicals.</a> | <a href="/search?q=su%3AClassification+Periodicals.&qt=hot_subject" title="Search for more with this subject">Classification -- Periodicals.</a> | <a HREF="/oclc/4538259?tab=subjects" title="More ...">More ...</a></li></ul>
</td>
<td class="bookmark">
<a href="javascript:bookmarksite(document.title, 'http://www.worldcatlibraries.org/oclc/4538259');" onmouseover="MM_displayStatusMsg('Bookmark This Page');return document.MM_returnValue;" onmouseout="MM_displayStatusMsg('');return document.MM_returnValue;">Bookmark</a> | <a href="/oclc/4538259">Permalink</a>
<br><br><span class="Z3988" title="url_ver=Z39.88-2004&rfr_id=info:sid/worldcatlibraries.org:worldcat&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft_ref_fmt=info:ofi/fmt:xml:xsd:oai_dc&rft_ref=http://partneraccess.oclc.org/wcpa/servlet/OUDCXML?oclcnum=4538259&rft_id=info:oclcnum/4538259&rft_id=urn:ISBN:&rft_id=urn:ISSN:0163-9374&rft.aulast=&rft.aufirst=&rft.auinitm=&rft.atitle=&rft.jtitle=Cataloging+%26+classification+quarterly.&rft.date=&rft.volume=&rft.issue=&rft.spage=&rft.epage=&rft.pages=&rft.issn=0163-9374&rft.eissn=1544-4554&rft.aucorp=&rft.place=&rft.pub=&rft.edition=&rft.series=&rft.genre=journal"></span>
</td>
</tr>
</table>
</div>

</nowiki>
</pre>
<nowiki>Insert non-formatted text here</nowiki><nowiki>Insert non-formatted text here</nowiki>

== 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-10-08T03:41:35Z

Ed Summers: added links to example markup

citation-examples-markup

2006-10-08T03:40:05Z

Ed Summers: added openworldcat

<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] ===
* subtitle
* title
* author
* Image
* pubdate
* pages
* volumes
* trimsize (book dimentions 8.5x11)
* Format
* Price
* ISBN

=== 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" ...>(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".../>
</a>
<a id="hlSharePage" title="Email this page to a friend" href="/books/sendform.asp?sku=GR2847"...>
<img title="Email this page to a friend" src="/_net.templates/roundedButton.aspx?ButtonText=Email".../>
</a>
<a id="hlPrintPage" title="Version of this page optimized for printing" href="/catalog/GR2847.aspx?print=1" ...>
<img title="Version of this page optimized for printing" src="/_net.templates/roundedButton.aspx?ButtonText=Print".../>
</a>
<a id="hlWorldCat" href="http://worldcatlibraries.org/wcpa/isbn/0313328471"...>
<img src="/images/world_catalog.gif".../>
</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"
... 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 ... class="productdetailhead"><span id="volumeslabel" class="productdetailhead">Volumes</span></td>
<td ... class="productdetailbody"><span id="volumes" class="productdetailbody">1</span></td>
(ABC-CLIO)
</pre>

=== ISBN: ===
<pre>
<td class="productdetailhead" ...><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" ... 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" ... 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...>
<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...>
<tr>
<td...><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>
..
<table...>
<tr>
<td ...>
<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 ...>
<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...>
<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>

== PubMed Medical Journal Example ==

Still another example of markup in the wild, coming from a search for "pancreas" in the New England Journal of Medicine from pubmed.org.

Note the title attribute with the expanded version of the canonical abbreviation for the journal.

<pre><nowiki>
<tr>
<td ...>
<a href="/entrez/query.fcgi?cmd=Retrieve&db=pubmed&dopt=Abstract&list_uids=15371579&itool=iconnoabstr&query_hl=2&itool=pubmed_docsum">
<img alt="No abstract" id="No abstract_15371579" ... Title="No abstract">
</a>
</td>
<td ...>Cystic neoplasms of the pancreas.<br>
<font size="-1">
<span title="The New England journal of medicine.">N Engl J Med.</span>
2004 Sep 16;351(12):1218-26. Review. No abstract available. <br>
PMID: 15371579 [PubMed - indexed for MEDLINE]
</font>
</td>
</nowiki></pre>

== Wikipedia Examples ==

=== Wikipedia Book ===

<pre><nowiki>
<li id="_note-8"><b><a href="#_ref-8" title="">^</a></b>
<i>Tuva Or Bust!</i>, Ralph Leighton, W. W. Norton & Company, 2000,
<a href="/w/index.php?title=Special:Booksources&isbn=0393320693"
class="internal">ISBN 0393320693</a>
</li>
</nowiki></pre>

=== Wikipedia Journal Article ===

<pre><nowiki>
<li id="_note-science1982-Dickerson">
<b><a href="#_ref-science1982-Dickerson_0" title="">^</a></b>
<cite style="font-style:normal">Dickerson et al. (1982). "The Anatomy of A-, B-, and Z-DNA".
<i>Science</i> <b>216</b>: 475-485. DOI: 10.1126/science.7071593.</cite>
<sup><a href="..." class="external text" title="...">PubMed</a></sup></li>
</nowiki></pre>

=== Wikipedia Court Case ===

<pre><nowiki>
<tr>
<td><i><a href="/wiki/Perfect_10_v._Google_Inc" title="Perfect 10 v. Google Inc">Perfect 10 v. Google Inc</a></i></td>
<td>CASE NO. CV 04-9484 AHM (SHx)</td>
<td><a href="/wiki/Central_District_of_California" title="Central District of California">CDCA</a> 2006</td>
<td>Thumbnails in Web searches that impinged upon market for images of that size were not fair use.</td>
</tr>
</nowiki>
</pre>

=== Wikipedia US Law ===

<pre><nowiki>
<li><cite id="endnote_FISA" style="font-style: normal;">
<a href="#ref_FISA" title=""><b>↑</b></a></cite> 
<a href="http://www.law.cornell.edu/uscode/html/uscode50/usc_sup_01_50_10_36.html"
class="external text" title="...">50 U.S.C Chapter 36 Foreign Intelligence Surveillance</a>
The complete text of the Foreign Intelligence Surveillance Act
</li>
</nowiki></pre>

The sections of the law are cited inline, without markup, as "50 U.S.C. §1801(a) (4),(5),(6)" for example.

=== Wikipedia Conference Presentation ===

<pre><nowiki>
<h3>Conference presentation by Pillar</h3>
<ul>
<li>
<a href="http://www.duke.edu/web/tiss/archives/conferencerecords/media/Pillar.htm"
class="external text" title="...">Foreign and Domestic Publics and the Counter-terrorism Effort</a>
(Duke University, 21-2 March 2003).</li>
</ul>
</nowiki>
</pre>

=== Wikipedia Primary Historical Source ===

<pre><nowiki>
<li>U.S. War Dept., <a href="http://cdl.library.cornell.edu/moa/browse.monographs/waro.html"
class="external text" title="...">
<i>The War of the Rebellion: a Compilation of the Official Records of the Union and Confederate Armies</i></a>,
U.S. Government Printing Office, 1880–1901. 70 very large volumes of letters and reports written by both armies.
Online at <a href="http://cdl.library.cornell.edu/moa/browse.monographs/waro.html"
class="external autonumber" title="...">[6]</a>
</li>
</nowiki>
</pre>

== EPrints.org generated output ==

EPrints uses the DC terms for information in the head element of an entry:

<pre><nowiki>
<head>
<title>ECS EPrints Service - Winnowing Ontologies based on Application Use</title>
<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC" />
<meta content="Winnowing Ontologies based on Application Use" name="DC.title" />
<meta content="Alani, Harith" name="DC.creator" />
<meta content="Harris, Stephen" name="DC.creator" />
<meta content="O'Neil, Ben" name="DC.creator" />
<meta content="The requirements of specific ... that ontology." name="DC.description" />
<meta content="2006-01-01" name="DC.date" />
<meta content="Conference or Workshop Item" name="DC.type" />
<meta content="http://eprints.ecs.soton.ac.uk/12070/" name="DC.identifier" />
<meta content="pdf http://eprints.ecs.soton.ac.uk/12070/01/Alani-final.pdf" name="DC.format" />
<link title="Full Text (application/pdf)" href="http://eprints.ecs.soton.ac.uk/12070/01/Alani-final.pdf"
class="fulltext" type="application/pdf" rel="alternate" />
</nowiki></pre>

And the following markup for the page's HTML:

<pre><nowiki>
<td valign="top"><div class="page">
<h1 class="pagetitle">
<span class="field_title">Winnowing Ontologies based on Application Use</span></h1>
<p class="intro">
<span class="citation">
<span class="field_authors">Alani, H., Harris, S. and O'Neil, B.</span>
(<span class="field_year">2006</span>)
<span class="field_title">Winnowing Ontologies based on Application Use</span>.
In <i>Proceedings of
<span class="field_conference">3rd European Semantic Web Conference (ESWC)</span></i>,
<span class="field_confloc">Budva, Montenegro</span>.
</nowiki></pre>

== BibDesk default HTML export example ==

Due to some recent improvements, BibDesk allows extensive user customization of its HTML output.
It has had an HTML template system since 2004, and the default template hasn't changed much since then.
Here is the default template, which I wrote long before I knew what little I know now of semantic HTML - Mike.

<pre><nowiki>
<div class="content">
<h1><$fileName.lastPathComponent/></h1>
<dl>
<dt class="Key" id="<$citeKey/>"><$citeKey/><dt />
<dd class="Pub">
<span class="Title"><$fields.Title/></span><br />
<span class="Author"><$pubAuthorsForDisplay/></span><br />
<span class="Journal"><$fields.Journal/></span> 
<span class="Volume"><$fields.Volume/></span> 
<span class="Pages"><$fields.Pages/></span> 
(<span class="Date"><$fields.Year/></span>)<br />
<span class="Url"><a href="<$fields.Url/>"><$fields.Url/></a></span><br />
<div class="Abstract"><$fields.Abstract/></div>
<dd />
</dl>
</div>
</nowiki></pre>

Here's a popular modification to the default template, also from 2004, which was used to make this [http://craftsrv1.epfl.ch/~cherubini/extranet/bib/CSCL.bib.html annotated reading list].

<pre><nowiki>
<p class="trigger">
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr>
<td width="20%"><span class="Author"><$pubFields.Author/></span></td>
<td width="5%"><span class="Year"><$pubFields.Year/></span></td>
<td width="55%"><span class="Title"><$pubFields.Title/></span></td>
<td width="10%"><span class="url"><$pubType/></span></td>
</tr>
</table>
</p>
<div>
<span class="url">
<a href="<$pubFields.Url/>"> <img src="pdf_icon.gif" border="0"> <$citeKey/> ~ <$pubFields.Url/></a>
</span>

<p class="Annote">Abstract:<br><$pubFields.Abstract/>
<br>Notes: <br><$pubFields.Annote/><br>
<br>Keywords: <$pubFields.Keywords/>
<br>BibTeX: <$bibTeXString/> <br>
<br><$RTFValue/>
</p>
</div>
</nowiki></pre>

Note that the tags that look like <$foo/> are templating entries and are replaced by values from each cited publication object.

== OCLC WorldCat Online ==

=== Book ===

<pre>
<nowiki>

<div id="item">
<table cellspacing="0">
<tr>
<td class="illustration"><img src="/wcpa/servlet/DCARead?standardNo=0062515861&standardNoType=1" alt="Weaving the Web : the original design and ultimate destiny of the World Wide Web by its inventor " /></td>
<td class="info">
<h1 class="title"> Weaving the Web : the original design and ultimate destiny of the World Wide Web by its inventor </h1>
<p class="author"><strong>by <a href="/search?q=au%3ATim+Berners-Lee&qt=hot_author" title="Search for more by this author">Tim Berners-Lee</a>; 
<a href="/search?q=au%3AMark+Fischetti&qt=hot_author" title="Search for more by this author">Mark Fischetti</a></strong></p>
<ul class="detailed">
<li class="type"><strong>Type: </strong>English : <img src="/wcpa/images/icon-bks.gif" height=16 width=16 alt="" title="Book" class="icn"/> <nobr>Book
</nobr><nobr></nobr></li>
<li class="publisher"><strong>Publisher: </strong> San Francisco : HarperSanFrancisco, ©1999.</li>
<li class="isbn"><strong>ISBN: </strong>0062515861 006251587X</li>
<li class="oclc"><strong>OCLC: </strong>41238513</li>
</ul><ul class="subjects"><li><strong>Subjects: </strong><a href="/search?q=su%3AWorld+Wide+Web+History.&qt=hot_subject" title="Search for more with this subject">World Wide Web -- History.</a> | <a href="/search?q=su%3ABerners-Lee%2C+Tim.&qt=hot_subject" title="Search for more with this subject">Berners-Lee, Tim.</a> | <a href="/search?q=su%3ABerners-Lee%2C+Tim.&qt=hot_subject" title="Search for more with this subject">Berners-Lee, Tim.</a> | <a HREF="/oclc/41238513?tab=subjects" title="More ...">More ...</a></li></ul>
</td>
<td class="bookmark">
<a href="javascript:bookmarksite(document.title, 'http://www.worldcatlibraries.org/oclc/41238513');" onmouseover="MM_displayStatusMsg('Bookmark This Page');return document.MM_returnValue;" onmouseout="MM_displayStatusMsg('');return document.MM_returnValue;">Bookmark</a> | <a href="/oclc/41238513">Permalink</a>
<br><br><span class="Z3988" title="url_ver=Z39.88-2004&rfr_id=info:sid/worldcatlibraries.org:worldcat&rft_val_fmt=info:ofi/fmt:kev:mtx:book&rft_ref_fmt=info:ofi/fmt:xml:xsd:oai_dc&rft_ref=http://partneraccess.oclc.org/wcpa/servlet/OUDCXML?oclcnum=41238513&rft_id=info:oclcnum/41238513&rft_id=urn:ISBN:0062515861&rft_id=urn:ISSN:&rft.aulast=Berners-Lee&rft.aufirst=Tim&rft.auinitm=&rft.btitle=Weaving+the+Web+%3A+the+original+design+and+ultimate+destiny+of+the+World+Wide+Web+by+its+inventor++&rft.atitle=&rft.date=&rft.tpages=&rft.isbn=0062515861&rft.aucorp=&rft.place=San+Francisco&rft.pub=HarperSanFrancisco&rft.edition=1st+ed.&rft.series=&rft.genre=book"></span>
</td>
</tr>
</table>
</div>

</nowiki>
</pre>

=== Journal ===

<pre>
<nowiki>

<div id="item">
<table cellspacing="0">
<tr>
<td class="info">
<h1 class="title"> Cataloging & classification quarterly.</h1>
<ul class="detailed">
<li class="type"><strong>Type: </strong>English : <img src="/wcpa/images/icon-ser.gif" height=16 width=16 alt="" title="Serial Publication" class="icn"/> <nobr>Serial Publication
</nobr> : <nobr>Periodical</nobr>
<nobr><span title="Internet Resource"><img height=16 width=16 border=0 align="absmiddle" src="/wcpa/images/icon-url.gif" alt="Internet Resource"> Internet Resource</span>
</nobr></li>
<li class="publisher"><strong>Publisher: </strong> New York, N.Y. : Haworth Press, [©1981]-</li>
<li class="isbn"><strong>ISSN: </strong>0163-9374 1544-4554</li>
<li class="oclc"><strong>OCLC: </strong>4538259</li>
</ul><ul class="subjects"><li><strong>Subjects: </strong><a href="/search?q=su%3ACataloging+Periodicals.&qt=hot_subject" title="Search for more with this subject">Cataloging -- Periodicals.</a> | <a href="/search?q=su%3AClassification+Books+Periodicals.&qt=hot_subject" title="Search for more with this subject">Classification -- Books -- Periodicals.</a> | <a href="/search?q=su%3AClassification+Periodicals.&qt=hot_subject" title="Search for more with this subject">Classification -- Periodicals.</a> | <a HREF="/oclc/4538259?tab=subjects" title="More ...">More ...</a></li></ul>
</td>
<td class="bookmark">
<a href="javascript:bookmarksite(document.title, 'http://www.worldcatlibraries.org/oclc/4538259');" onmouseover="MM_displayStatusMsg('Bookmark This Page');return document.MM_returnValue;" onmouseout="MM_displayStatusMsg('');return document.MM_returnValue;">Bookmark</a> | <a href="/oclc/4538259">Permalink</a>
<br><br><span class="Z3988" title="url_ver=Z39.88-2004&rfr_id=info:sid/worldcatlibraries.org:worldcat&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft_ref_fmt=info:ofi/fmt:xml:xsd:oai_dc&rft_ref=http://partneraccess.oclc.org/wcpa/servlet/OUDCXML?oclcnum=4538259&rft_id=info:oclcnum/4538259&rft_id=urn:ISBN:&rft_id=urn:ISSN:0163-9374&rft.aulast=&rft.aufirst=&rft.auinitm=&rft.atitle=&rft.jtitle=Cataloging+%26+classification+quarterly.&rft.date=&rft.volume=&rft.issue=&rft.spage=&rft.epage=&rft.pages=&rft.issn=0163-9374&rft.eissn=1544-4554&rft.aucorp=&rft.place=&rft.pub=&rft.edition=&rft.series=&rft.genre=journal"></span>
</td>
</tr>
</table>
</div>

</nowiki>
</pre>
<nowiki>Insert non-formatted text here</nowiki><nowiki>Insert non-formatted text here</nowiki>

== 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-10-08T03:35:22Z

Ed Summers: added oclc worldcat online

citation

2006-10-08T03:25:41Z

Ed Summers: added link to markup page

<h1> Citation microformat efforts </h1>

This wiki page outlines the overall effort to develop a citation microformat. We are documenting current examples of cites/citations on the web today, their implicit/explicit schemas, and current cite/citation formats, with the intent of deriving a cite microformat from that research.

__TOC__

== Authors ==
* [http://tantek.com/ Tantek Çelik]
* [http://suda.co.uk/ Brian Suda]
* [http://www.inkdroid.org Ed Summers]

== Copyright ==
{{MicroFormatCopyrightStatement2004}}

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

== Example Citations ==
[[citation-examples|Citation Examples]] are citations found in the wild that could benefit from semantic mark-up. This is a growing list of examples from all sorts of places including W3C specifications, RFCs and others. These are the examples which will determine the schema for the citation microformat.

== Known Citation Formats ==
The [[citation-formats|Citation Formats Page]] will be a running tab of known formats for publishing citations.

Eventually, i would like to see a chart of how each value from the implicit schema determined by the [[citation-examples]] is represented in each format, and what formats have additional properties that do not map between them. (For example, Format1 calls 'author' 'author', in format2 'author' is called 'writer'. etc)

== To Do ==
* [http://microformats.org/wiki/existing-classes Using existing class names] and creating new names, create property names for the profile
* Based on implicit schemas in [[citation-examples]], and terms from one or more [[citation-formats]], do some [[citation-brainstorming]] for a simple citation microformat.
* Create additional strawman proposals

== Modularity ==
My hope for this microformat is that it can be a sort of module that can be used in other microformats. Once this is developed and flushed out, citation references could easily be used for publications on a Resume/CV, therefore the citation microformat would be a module (subset) of all the possible Resume Values.

Other Microformats that could use the Citation Module
* [[hresume|hResume]]
* [[work-of-art]]

Other Microformats that the Citation Module will use
* [http://microformats.com/wiki/hcard hCard] encodings for things like Author, Publisher (people and companies)
* [http://microformats.org/wiki/hatom hAtom] encodings as a possible container, and author/date-time properties
* [http://microformats.org/wiki/rel-tag rel-tag] encoding for keywords
* [http://microformats.org/wiki/rel-license rel-license] encoding for copyright

== References ==
=== Informative References ===
* [http://ocoins.info/ COinS]
* [http://xmlresume.sourceforge.net/ XMLResume]: if part of the drive for citations is for publications for a resume/CV then some of this information could be useful
* [http://www.citeulike.org/ CiteUlike] is a free service to help academics to share, store, and organise the academic papers they are reading
* [http://www.ariadne.ac.uk/issue43/chudnov/ OpenURL] with Autodiscovery
* [http://cipolo.med.yale.edu/mailman/listinfo/gcs-pcs-list "Gather, Create, Share" and "Personal Collection Systems" memes, and systems implementing either or both]
* [http://www.loc.gov/standards/mods/ Metadata Object Description Schema] developed by the Library of Congress
* [http://dublincore.org/ Dublin Core Metadata]
* [http://www.ecst.csuchico.edu/~jacobsd/bib/formats/bibtex.html BibTeX reference] from Dana Jacobsen
* [http://www.refman.com/support/risformat_intro.asp RIS Format Specification] from Thomson ResearchSoft, makers of ReferenceManager

== See Also ==
* [[citation-examples]]
* [[citation-examples-markup]]
* [[citation-formats]]
* [[citation-brainstorming]]
* [[citation-faq]]

User:Ed Summers

2006-05-16T15:42:29Z

Ed Summers:

Ed Summers writes software for libraries/archives and is currently working at the Library of Congress. He has a [http://www.inkdroid.org blog].

irc

2006-05-16T15:40:32Z

Ed Summers: added edsu

__NOTOC__
= Microformats IRC =

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

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

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

* [[User:Amette|amette]] (+1000)
* [[User:B.K._DeLong|bkdelong]] (-0500/-0400)
* [[User:Ben Ward|BenWard]] (+0000)
* [[User:BenjaminCarlyle|BenjaminCarlyle]] (+1000)
* [[User:Boneill|boneill]] (+0000)
* [[User:Brian|briansuda]] (-0600/-0500)
* [[User:ColinDDevroe|cdevroe]] (-0500/-0600)
* [[User:Cgriego|cgriego]] (-0600/-0500)
* [[User:ChrisCasciano|pnhChris]] (-0500/-0400)
* [[User:ChrisMessina|factoryjoe]] (-0800/-0700)
* [[User:ChristopherStJohn|cks]] (-0600/-0500)
* [[User:DanC|DanC]] (-0600/-0500)
** office hours: Wednesday afternoons, America/Chicago time
* [[User:Dave Cardwell|davecardwell]] (+0000)
* [[User:DimitriGlazkov|dglazkov]] (-0600/-0500)
* [[User:EdwardOConnor|hober]] (-0800/-0700)
* [[User:Enric|enric]] (-0800/-0700)
* [[User:Evan|evanpro]] (-0500)
* [[User:Fil|Fil]] (+0200)
* [[User:Hlb|hlb]] (+0800-0700)
* [[User:IanHickson|Hixie]] (-0800/-0700)
* [[User:Izo|IZO]]
* [[User:JoeGregorio|jcgregorio]]
* [[User:Jonathan_Arkell|jonnay]] (-0700/0600)
* [[User:Keri Henare|kerihenare]] (+1200)
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)
* [[User:Mark Mansour|Mark Mansour]] (+1100)
* [[User:neuro|neuro`]]
* [[User:RobertBachmann|RobertBachmann]] (+0100/+0200)
** Office hours: Wednesday, 20:30-21:30 UTC
* [[User:RyanKing|kingryan]] (-0800/-0700)
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC
* [[User:Dana Benson|Snowden]] (-0800/-0700)
* [[User:Steve Ganz|SteveGanz]] (-0800/-0700)
* [[User:Tantek|Tantek]] (-0800/-0700)
* [[User:Dan Kubb|dkubb]] (-0800/-0700)
* [[User:Ed Summers|edsu]] (-0500/-0400)

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

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

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

=== bots ===

* [[mfbot]]
* [[mflogbot]]
* [http://joi.ito.com/joiwiki/JiBot jibot]

== Logs ==

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

== IRC meetups ==

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

citation-brainstorming

2006-05-03T15:14:22Z

Ed Summers: added note about ROLE

<h1> Citation Brainstroming </h1>

__TOC__

== Contributors ==

* ...
* ... (a bunch of good folks!)
* Tantek Çelik
* Tim White
* Michael McCracken

== See also ==
* [[citation]]
* [[citation-examples]]
* [[citation-formats]]
* [[citation-faq]]

== Use Cases ==

To focus the discussion, please add use cases below that will help show what problems the citation microformat will be solving.

I've included two, focusing on consuming information - I've assumed that use cases for generating microformatted content would just involve the desire to enable your content to be consumed better, but I'm interested to see if there's something I'm missing here -Mike

=== Acquiring reference information from the web ===

A user either finds an author's papers page, or is viewing the results of a search and would like to import the information about the displayed papers into their local reference database, for the purposes of cataloging things they've read, adding notes, and using the information to generate later citations, potentially in other forms, such as BibTeX or Docbook, for inclusion in a publication of their own.

Notes: In this case, it isn't important to the user what format the citation takes as displayed on the page where they find it. What *is* important is that it contains enough information to allow generation of the format they will ultimately re-publish it in. This implies that it may be worthwhile to err a little on the side of verbosity.

Also, links to downloadable full representations of the cited work are very important - e.g. a link to the PDF of a journal article, or to a music file.

=== Subscribing to reading lists, periodicals, etc ===

I would like to be able to leverage my news aggregator with hAtom to subscribe to a remote source for citation information, for example:

* a reading list for a seminar
* The publication list for a conference (e.g., subscribe to SIGGRAPH and see the updated conference proceedings every year)
* the issues of a journal
* a particular research group or researcher's publications
* Not just research: a popular author's publications (e.g., [http://www.gladwell.com/archive.html Malcolm Gladwell's Archive])

=== Aggregating reading lists and reviews ===

A citation microformat-specific aggregator could provide a decentralized version of [http://citeulike.org/ CiteULike]. Libraries, authors, research groups, and publishers could mark up their collections, while other people on weblogs or review sites could add tags and reviews.

At least, having a well-adopted microformat would make writing tools like CiteULike much better, since it relies in some cases on screen-scraping publisher web-sites.

== Original hBib Discussion ==

During the WWW2005 Developer's Day [[microformats]] track, Rohit Khare gave a [[presentations|presentation]] where he discussed the microformats [[process]], and then did a quick demonstration wherein a bunch of us got on a shared Subethaedit document, and brainstormed some thoughts on what an "hBib" bibliography citation microformat would look like. Rohit placed the [http://cnlabs.commerce.net/~rohit/hBib%20Discussion.html document on his Commercenet site].

* http://cnlabs.commerce.net/~rohit/hBib%20Discussion.html

''An attempt to summarize and inline the linked document follows. -Mike''

Two major goals were outlined by the group:

* Avoid re-keying references
* Adapt to new journal styles by changing CSS

The fundamental problem was discussed in terms of display - the ability to transform XHTML+hBib into the many journal-specific formats. For example, how to display "et.al" when all authors are present in the source, and how to re-order the elements if a style defines a set order of elements that conflicts with the ordering in the source. Using hCard for authors was agreed on, and the beginnings of an example were shown.

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

== Citation vs. [[media-info]] ==

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. ''Does this sentence make sense only historically? -Mike''

== OCLC's WorldCat for titles ==
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]

== More on This and That ==

Citation microformats are being explored as a possibility for citing genealogical information at [http://eatslikeahuman.blogspot.com Dan Lawyer's blog].

This is a case where frequently the citation would refer to (THIS.PAGE), but would have nested within it a reference to (THAT.PAGE), possibly a few levels deep. For instance, a web page might contain data extracted from a microfilm of a census. The citation would need to include information about the web page, information about the microfilm, and information about the census. Genealogical citations are expected to include the repository (where can this book or microfilm be found. Is this the same as ''venue''?). So, at each level the information should contain the repository of the referenced item. A nesting (recursive) mechanism for citation microformats would be useful in this case. Is this the function of the "container" element in the Straw Format?

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

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

== Basic Citation Stuctures ==
There are basic structures to any citation, this is an overview of some of the types
[http://www.users.muohio.edu/darcusb/misc/citations-spec.html http://www.users.muohio.edu/darcusb/misc/citations-spec.html]

== Brian's Straw format ==

=== implied schema (examples) ===
+ publisher
+ language
+ description
+ title
+ creator
+ volume
+ issue
+ page
+ edition
+ identifier
+ tags
+ format
+ date published
+ copyright
- audience

=== implied schema (formats) ===
+ publisher
+ language
+ description
+ title
+ creator
+ volume
+ pages
+ edition
+ issue
+ identifier
+ tags
+ format
+ date published
+ date copyrighted
- subtitle
- image
- excerpt
- index terms
- series title
- publication
- journal
- part (1 of X)

UNION of the two schemas
+ (PLUS) means common properties
- (MINUS) means unique to the schema

=== Example ===
<pre>
<nowiki>
<ul class="bibliography">
<li class="citation" xml:lang="en-gb">


<div class="publisher vcard">
<span class="fn org">ABC Publishing Co.</span>
<span class="country-name">United Kingdom</span>
...
</div>


<div class="creator vcard">
<span class="fn n"><span class="given-name">John <span class="family-name">Doe</span></span>
...
</div>


<span class="title">Foobar!</span>
<span class="description">World Class Book about foobar</span>
<span class="volume">1</span>
<span class="issue">1</span>
<span class="edition">1</span>
<span class="pages">1-10</span>
<span class="format">article</span>


<span class="identifier">12345678</span>


<span class="keyword">foo</span>
<span class="keyword">bar</span>


Published <abbr class="dtpublished" title="20060101">January 1st 1006</abbr>
Copyright <abbr class="copyright" title="20060101">2006</abbr>
</li>
...
</ul>

<p class="citation">Have you read <span class="title"><abbr title="book" class="format">Foo Bar</abbr></span>?
It was written by <span class="author vcard"><span class="fn">John Doe</span></span>.
It only came out a <abbr class="dtpublished" title="20060101">few months ago</abbr></p>
</nowiki>
</pre>

Note: the "format" property above is incorrect. Format would refer more the physical characteristics of an item, rather than its type or genre (e.g. "article", "book", etc.). I'd rather have the main class for the li be "article" in this context, than the fairly meaningless "citation." Of course, one could have both, which would be fine too. -- bruce

Note: Could we use ROLE from hCard to identify editors, translators, authors, etc?

== Mike straw format suggestion ==

In the interests of starting debate and having something concrete to fix, I suggest the following structure for a format. It is probably very incomplete and I claim no microformat expertise. I'm just trying to follow existing patterns. Comments and ridicule are both solicited. -Mike

=== In General ===

The ''citation'' format is based on a set of fields common to many bibliographic data formats, which are often implied by standard citation display styles but not explicitly marked up in practice on the web.

=== Schema ===

The citation schema consists of the following:

* cite
** title: required, text (class = fn)
** subtitle: optional, text
** authors: optional, use hCard
** publication date: optional
** link(s) to instantiations, optional, url or use rel-enclosure? (class=url)
** UID, optional (for ISBN, DOI - use existing uid class) | permalink
** series (aka volume/issuenum) , optional (''not as sure how to handle these - suggestions?'')
** pages: startpage & endpage, optional, text
** venue, optional (hCard)
** publisher, optional (hCard)
** container: optional (nested hCite)
** abstract, optional (blockquote + class="abstract" ?)
** notes, optional (blockquote + class="notes" ?)
** keywords, optional (rel-tag)
** image, optional (for inclusion inline, unlike the url)
** copyright, optional (rel-license)
** ''what else am I missing?''
*** language, optional

''Looks good, but I question the use of hCard for names. Due to ambiguity issues, requring hCard would lead to extra markup in order to apply just a name, hence [http://microformats.org/discuss/mail/microformats-discuss/2006-March/003487.html the need for a root element]. We should extract the N optimization of hCard like we did with adr, in order to ease this problem.'' --[[User:RCanine|Ryan Cannon]]

Perhaps a Retrieved Date or Access Date would be appropriate for citing online resources. For example at http://www.crlt.umich.edu/publinks/facment_biblio.html
you see citations like this<nowiki>:</nowiki>
<blockquote>
Chief Academic Officers of the Big 12 Universities (2000). Big 12 Faculty Fellowship Program. Retrieved December 20, 2000 from the World Wide Wed: http://www.k-state.edu/provost/academic/big12/big12guide.htm.
</blockquote>
--[[User:JoeAndrieu|Joe Andrieu]]

=== Examples ===

The following are translations into the ''citation'' format.

Note: some of these are just placeholders right now. Please feel free to fill them in!

==== Citing Private Communication ====
* published-date seems a weird fit, but it works...
private communication, Michael Jordan, May 2004

Needs a formatted example.

==== Citing Legal Cases ====
Needs an example. Here's some info I found about citing law:

I'm not a lawyer, so I'm relying on the published [http://www.legalbluebook.com "blue book" standard], at least the only part of it I can get without paying $25. I'd be happy to hear improvements from experts in the field - how do lawyers mark up references to case law in HTML now?

From groklaw.net and eff.org, I find mostly just links to PDFs with the name of the case as the link text. Or just this, from EFF:
<pre><nowiki>
<h1>The Betamax Case</h1>
<h2>Sony Corp. of America v. Universal City Studios, 464 U.S. 417 (1984)</h2>
</nowiki></pre>

From an example at the sample bluepages: http://www.legalbluebook.com/pdfs/bluepages.pdf
5 basic components:
*1 name of the case (citation title)
*2 published source in which case may be found (citation containing publication?)
*3 a parenthetical indicating the court and year of decision (citation venue?)
*4 other parenthetical information, if any (citation notes?)
*5 subsequent history of the case, if any (citation notes?)

Here's two examples from the bluebook. Note that there are very strict rules about abbreviations in that source!

Holland v. Donnelly, 216 F. Supp. 2d 227, 230 (S.D.N.Y. 2002), aff'd, 324 F.3d 99 (2d Cir. 2003).

Green v. Georgia, 442 U.S. 95, 97 (1979) (per curiam) (holding that exclusion of relevant evidence at sentencing hearing constitutes denial of due process).

==== Citing a Book ====

needs an example

==== Citing a journal article ====

needs an example

==== Citing a magazine article ====

needs an example

==== Citing a Patent ====

Patents are often just cited by number. Here's a citation that accomplishes the same thing with some extra information:

<pre><nowiki>
<cite class="citation">
<a class="fn url" href="http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=/netahtml/search-bool.html&r=3&f=G&l=50&co1=AND&d=ptxt&s1=tevanian&OS=tevanian&RS=tevanian">US Patent #6,704,928</a>
<span class="author vcard">Richard Shann</span>
<abbr class="dtpublished" title="20000828T0000-0500">August 28, 2000</abbr>
<blockquote class="abstract">
An executable program is prepared from a plurality of object code modules, at least one of the object code modules including section data specifying a plurality of code sequences each associated with relocation instructions identifying condition parameters. Only one of the code sequences is selected for inclusion in the executable program, determined by whether the condition for that parameter is satisfied. A linker for preparing the executable program includes a stack, a relocation module for reading the relocations, carrying out the relocation operations and selecting code sequences for inclusion in the executable program in dependence on values taken from the stack, a section data module for holding section data which is subject to the relocation operations, and a program forming module for preparing executable programs. Also disclosed is a method of assembling an object code module such that the assembled object code module includes the conditional code sequences.</blockquote>
</cite>
</nowiki></pre>

==== Citing a conference publication====

Based on the following reference, plus some more information from the ACM site and a little of my own input (the tags)

L. Hochstein, J. Carver, F. Shull, S. Asgari, V. Basili, J. K. Hollingsworth, and M. Zelkowitz, “Hpc programmer productivity: A case study of novice hpc programmers,” in Proceedings of ACM/IEEE Supercomputing Conference, 2005.

<pre><nowiki>
<cite class="citation">
<span class="author vcard">Lorin Hochstein</span>,
<span class="author vcard"> Jeff Carver </span>,
<span class="author vcard"> Forrest Shull </span>,
<span class="author vcard"> Sima Asgari</span>,
<span class="author vcard"> Victor Basili</span>,
<span class="author vcard"> Jeffrey K. Hollingsworth</span>, and
<span class="author vcard"> Marv Zelkowitz</span>,
<a class="fn url" href="http://dx.doi.org/10.1109/SC.2005.53">HPC Programmer Productivity: A Case Study of Novice HPC Programmers</a>.
<cite class="container citation">
<a class="fn url" href="">Proceedings of ACM/IEEE Supercomputing Conference</a>
<abbr class="dtpublished" title="20051126T0000-0800">2005</abbr>
</cite>
page <span class="startpage">35</span>
<div class="publisher vcard">
<span class=" fn">IEEE Computer Society
</span>
<div class="adr">
<span class="locality">Washington</span>,
<span class="region">DC</span>
</div>
</div>
<a class="url instantiation" href="http://portal.acm.org/ft_gateway.cfm?id=1105800&type=pdf&coll=portal&dl=ACM&CFID=68330711&CFTOKEN=39187329">PDF of full text from ACM</a>

DOI: <a class="url uid" href="http://dx.doi.org/10.1109/SC.2005.53">10.1109/SC.2005.53</a>
Tags: <a href="http://citeulike.org/tag/productivity" rel="tag">productivity</a>, <a href="http://citeulike.org/tag/hpc" rel="tag">hpc</a>, <a href="http://citeulike.org/tag/performance" rel="tag">performance</a>
<blockquote class="abstract">In developing High-Performance Computing (HPC) software, time to solution is an important metric. This metric is comprised of two main components: the human effort required developing the software, plus the amount of machine time required to execute it. To date, little empirical work has been done to study the first component: the human effort required and the effects of approaches and practices that may be used to reduce it. In this paper, we describe a series of studies that address this problem. We instrumented the development process used in multiple HPC classroom environments. We analyzed data within and across such studies, varying factors such as the parallel programming model used and the application being developed, to understand their impact on the development process.
</blockquote>
</cite>
</nowiki></pre>

==== Citing an external website ====

This is based on a formal citation of a website in the references section of a research paper, but could also be used for in-line links that had added information. Here's the original:

[25] David Stern, "eprint Moderator Model", http://www.library.yale.edu/scilib/modmodexplain.html (version dated Jan 25, 1999)

<pre><nowiki>
<cite class="citation">
<a class="fn url" href="http://www.library.yale.edu/scilib/modmodexplain.html">eprint Moderator Model</a>
<span class="author vcard">
<a href="http://pantheon.yale.edu/~dstern/dsbio.html" class="url fn">David Stern</a>
</span>
<abbr class="dtpublished" title="19990125T0000-0500">
Jan 25, 1999
</abbr>
</cite>
</nowiki></pre>

== discussions ==

* [[citation-irc-notes-2006-04-09]]

citation-examples

2006-05-03T08:52:36Z

Ed Summers: /* Contributors */

citation-examples

2006-05-03T08:48:08Z

Ed Summers: /* PubMed Medical Journal Example */

citation-examples

2006-05-03T08:47:12Z

Ed Summers: /* CiteSeer database search results */

citation-examples

2006-05-03T08:43:58Z

Ed Summers: added journal that was missing

uid

2006-04-26T16:47:49Z

Ed Summers: /* UID */

= UID =

This page documents an effort to define a microformat for [http://en.wikipedia.org/wiki/Category:Identifiers identifiers]. This effort came about from two angles:

* the need for a module that hCard and hCalendar could reference for defining the behavior of UID</li>
* the need for marking up freeform identifiers that are found in web content

Per the microformats [[process]]

* [[uid-examples]]
* [[uid-formats]]
* [[uid-brainstorming]]

Please take a look, and contribute your thoughts and ideas.

uid

2006-04-26T16:47:25Z

Ed Summers: this is a wiki, no need for ul, li etc :-)

= UID =

This page documents an effort to define a microformat for [http://en.wikipedia.org/wiki/Category:Identifiers identifiers]. This effort came about from two angles:

* the need for a module that hCard and hCalendar could reference for defining the behavior of UID</li>
* the need for marking up freeform identifiers that are found in web content<

Per the microformats [[process]]

* [[uid-examples]]
* [[uid-formats]]
* [[uid-brainstorming]]

Please take a look, and contribute your thoughts and ideas.

uid

2006-04-26T16:46:39Z

Ed Summers: removed examples, added a bit more background on 'why' uid

= UID =

This page documents an effort to define a microformat for [http://en.wikipedia.org/wiki/Category:Identifiers identifiers]. This effort came about from two angles:

<ul>
<li>the need for a module that hCard and hCalendar could reference for defining the behavior of UID</li>
<li>the need for marking up freeform identifiers that are found in web content</li>

Per the microformats [[process]]

* [[uid-examples]]
* [[uid-formats]]
* [[uid-brainstorming]]

Please take a look, and contribute your thoughts and ideas.

uid-brainstorming

2006-04-26T03:00:56Z

Ed Summers: /* ID attribute */

= UID Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a UID microformat.

== Authors ==

* Tantek Çelik
* Ed Summers

== Experience ==

* a microformat for indicating something *is* an identifier rather than the solved problem of providing a microformat *for* identifiers ([http://www.ietf.org/rfc/rfc2396.txt RFC 2396])

* Tantek has had conversations with LiveClipboard folks and upcoming.org who have had questions about how to do UID properly in hCard and hCalendar. So a separate microformat that those two could call out to would serve a real need.

* It would be useful for autodiscovery puposes to be able to follow a network resolvabale UID and extract more metadata from the referenced UID. Having a well defined UID pattern would prevent an explosion of rel values: rel-vcard, rel-vevent, etc.

* Efforts such as [http://unapi.info unAPI] have a real need for marking up identifiers so that they can be used for retrieving more detailed metadata.

* Greasemonkey and other browser based scripts could make real use of URIs found in pages as opposed to resorting to elaborate regexen. See Jon Udell's [http://weblog.infoworld.com/udell/stories/2002/12/11/librarylookup.html LibraryLookup] project.

* GoogleScholar embed identifiers in their citations and it would enable moving citations from the browser to a citation manager greatly if there were a way to mark them up.

== Goals Requirements ==

* a method of publishing an asserted globally unique identifier for a piece of content or a referenced item

== Thoughts ==

=== UIDs that are URLs ===

It seems like in the 80% case (perhaps 99.99% case on the Web), a UID is going to be a URL, thus a common pattern will likely be things like:

<pre><nowiki>
<a class="url uid" href="http://example.com/contentspace/somenumber">the item</a>
</nowiki></pre>

=== SHOULD rather than MUST ===

A UID SHOULD be a URL rather than MUST. The UID microformat will ordinarily be a URL, but it should be flexible enough to allow it to contain non-network resolvable URIs.

=== UID + URL -> permalink? ===

Can you infer that if something is a URL and a UID that it is also a permalink? It seems so. I can't think of any semantic of "permalink" that isn't covered by the union of the semantics of URL and UID.

=== abbr pattern ===

Use the [[abbr-design-pattern]] to allow identifiers to be more fully described.
<pre>
<abbr class="uid" title="urn:isbn:0950788120">0 9507881-2-0</abbr>
</pre>

=== HTML ID attribute ===

How does/doesn't the ID attribute from HTML fit into all this? Can it be repurposed to help here?

== Proposals ==

=== Just use UID from hCard ===

* Tantek proposed that we see if we can reuse uid from [[hcard|hCard]], similar to how we have reused [[geo]] and [[adr]] from [[hcard|hCard]].

=== Create a URI microformat ===

* Xiaoming proposed leaving UID intact in hcalendar and hcard, because whatever written in rfc2426/rfc2445 and their examples cannot be easily changed, and they seem to work well with hcalendar/hcard. Instead a new "URI" microformat should be established for the purpose of indicating something *is* an identifier in general.In this case you can easily reference URI RFC and no further elaboration about persistence, resolvability or uniqueness will be necessary because these issues are addressed by various URI specifications.

== References ==
* [[adr]]
* [[geo]]
* [[hcard|hCard]]
* [[hcalendar|hCalendar]]
* [[abbr-design-pattern]]

== See Also ==
* [http://www.iana.org/assignments/urn-namespaces IANA URN Namespaces - RFC2141, RFC3406]
* [http://www.iana.org/assignments/uri-schemes.html IANA Uniform Resource Identifer (URI) Schemes]
* [http://ocoins.info COinS] for putting attaching openurl context objexts to a span.
* [http://unapi.info unAPI] has a technique for embedding IDs in html so that they can be retrieved from an unAPI service.
* [http://www.taguri.org/ Tag URI] an algorithm that lets people mint identifiers that no one else using the same algorithm could ever mint.

== Related Discussion ==
* [http://microformats.org/discuss/mail/microformats-discuss/2006-April/003726.html UID, URL, live microformats]
* [http://microformats.org/discuss/mail/microformats-discuss/2005-November/002046.html format for identifiers]

uid-brainstorming

2006-04-26T03:00:42Z

Ed Summers: added html id note

= UID Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a UID microformat.

== Authors ==

* Tantek Çelik
* Ed Summers

== Experience ==

* a microformat for indicating something *is* an identifier rather than the solved problem of providing a microformat *for* identifiers ([http://www.ietf.org/rfc/rfc2396.txt RFC 2396])

* Tantek has had conversations with LiveClipboard folks and upcoming.org who have had questions about how to do UID properly in hCard and hCalendar. So a separate microformat that those two could call out to would serve a real need.

* It would be useful for autodiscovery puposes to be able to follow a network resolvabale UID and extract more metadata from the referenced UID. Having a well defined UID pattern would prevent an explosion of rel values: rel-vcard, rel-vevent, etc.

* Efforts such as [http://unapi.info unAPI] have a real need for marking up identifiers so that they can be used for retrieving more detailed metadata.

* Greasemonkey and other browser based scripts could make real use of URIs found in pages as opposed to resorting to elaborate regexen. See Jon Udell's [http://weblog.infoworld.com/udell/stories/2002/12/11/librarylookup.html LibraryLookup] project.

* GoogleScholar embed identifiers in their citations and it would enable moving citations from the browser to a citation manager greatly if there were a way to mark them up.

== Goals Requirements ==

* a method of publishing an asserted globally unique identifier for a piece of content or a referenced item

== Thoughts ==

=== UIDs that are URLs ===

It seems like in the 80% case (perhaps 99.99% case on the Web), a UID is going to be a URL, thus a common pattern will likely be things like:

<pre><nowiki>
<a class="url uid" href="http://example.com/contentspace/somenumber">the item</a>
</nowiki></pre>

=== SHOULD rather than MUST ===

A UID SHOULD be a URL rather than MUST. The UID microformat will ordinarily be a URL, but it should be flexible enough to allow it to contain non-network resolvable URIs.

=== UID + URL -> permalink? ===

Can you infer that if something is a URL and a UID that it is also a permalink? It seems so. I can't think of any semantic of "permalink" that isn't covered by the union of the semantics of URL and UID.

=== abbr pattern ===

Use the [[abbr-design-pattern]] to allow identifiers to be more fully described.
<pre>
<abbr class="uid" title="urn:isbn:0950788120">0 9507881-2-0</abbr>
</pre>

=== ID attribute ===

How does/doesn't the ID attribute from HTML fit into all this? Can it be repurposed to help here?

== Proposals ==

=== Just use UID from hCard ===

* Tantek proposed that we see if we can reuse uid from [[hcard|hCard]], similar to how we have reused [[geo]] and [[adr]] from [[hcard|hCard]].

=== Create a URI microformat ===

* Xiaoming proposed leaving UID intact in hcalendar and hcard, because whatever written in rfc2426/rfc2445 and their examples cannot be easily changed, and they seem to work well with hcalendar/hcard. Instead a new "URI" microformat should be established for the purpose of indicating something *is* an identifier in general.In this case you can easily reference URI RFC and no further elaboration about persistence, resolvability or uniqueness will be necessary because these issues are addressed by various URI specifications.

== References ==
* [[adr]]
* [[geo]]
* [[hcard|hCard]]
* [[hcalendar|hCalendar]]
* [[abbr-design-pattern]]

== See Also ==
* [http://www.iana.org/assignments/urn-namespaces IANA URN Namespaces - RFC2141, RFC3406]
* [http://www.iana.org/assignments/uri-schemes.html IANA Uniform Resource Identifer (URI) Schemes]
* [http://ocoins.info COinS] for putting attaching openurl context objexts to a span.
* [http://unapi.info unAPI] has a technique for embedding IDs in html so that they can be retrieved from an unAPI service.
* [http://www.taguri.org/ Tag URI] an algorithm that lets people mint identifiers that no one else using the same algorithm could ever mint.

== Related Discussion ==
* [http://microformats.org/discuss/mail/microformats-discuss/2006-April/003726.html UID, URL, live microformats]
* [http://microformats.org/discuss/mail/microformats-discuss/2005-November/002046.html format for identifiers]

uid-brainstorming

2006-04-26T02:54:47Z

Ed Summers: /* Experience */

= UID Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a UID microformat.

== Authors ==

* Tantek Çelik
* Ed Summers

== Experience ==

* a microformat for indicating something *is* an identifier rather than the solved problem of providing a microformat *for* identifiers ([http://www.ietf.org/rfc/rfc2396.txt RFC 2396])

* Tantek has had conversations with LiveClipboard folks and upcoming.org who have had questions about how to do UID properly in hCard and hCalendar. So a separate microformat that those two could call out to would serve a real need.

* It would be useful for autodiscovery puposes to be able to follow a network resolvabale UID and extract more metadata from the referenced UID. Having a well defined UID pattern would prevent an explosion of rel values: rel-vcard, rel-vevent, etc.

* Efforts such as [http://unapi.info unAPI] have a real need for marking up identifiers so that they can be used for retrieving more detailed metadata.

* Greasemonkey and other browser based scripts could make real use of URIs found in pages as opposed to resorting to elaborate regexen. See Jon Udell's [http://weblog.infoworld.com/udell/stories/2002/12/11/librarylookup.html LibraryLookup] project.

* GoogleScholar embed identifiers in their citations and it would enable moving citations from the browser to a citation manager greatly if there were a way to mark them up.

== Goals Requirements ==

* a method of publishing an asserted globally unique identifier for a piece of content or a referenced item

== Thoughts ==

=== UIDs that are URLs ===

It seems like in the 80% case (perhaps 99.99% case on the Web), a UID is going to be a URL, thus a common pattern will likely be things like:

<pre><nowiki>
<a class="url uid" href="http://example.com/contentspace/somenumber">the item</a>
</nowiki></pre>

=== SHOULD rather than MUST ===

A UID SHOULD be a URL rather than MUST. The UID microformat will ordinarily be a URL, but it should be flexible enough to allow it to contain non-network resolvable URIs.

=== UID + URL -> permalink? ===

Can you infer that if something is a URL and a UID that it is also a permalink? It seems so. I can't think of any semantic of "permalink" that isn't covered by the union of the semantics of URL and UID.

=== abbr pattern ===

Use the [[abbr-design-pattern]] to allow identifiers to be more fully described.
<pre>
<abbr class="uid" title="urn:isbn:0950788120">0 9507881-2-0</abbr>
</pre>

== Proposals ==

=== Just use UID from hCard ===

* Tantek proposed that we see if we can reuse uid from [[hcard|hCard]], similar to how we have reused [[geo]] and [[adr]] from [[hcard|hCard]].

=== Create a URI microformat ===

* Xiaoming proposed leaving UID intact in hcalendar and hcard, because whatever written in rfc2426/rfc2445 and their examples cannot be easily changed, and they seem to work well with hcalendar/hcard. Instead a new "URI" microformat should be established for the purpose of indicating something *is* an identifier in general.In this case you can easily reference URI RFC and no further elaboration about persistence, resolvability or uniqueness will be necessary because these issues are addressed by various URI specifications.

== References ==
* [[adr]]
* [[geo]]
* [[hcard|hCard]]
* [[hcalendar|hCalendar]]
* [[abbr-design-pattern]]

== See Also ==
* [http://www.iana.org/assignments/urn-namespaces IANA URN Namespaces - RFC2141, RFC3406]
* [http://www.iana.org/assignments/uri-schemes.html IANA Uniform Resource Identifer (URI) Schemes]
* [http://ocoins.info COinS] for putting attaching openurl context objexts to a span.
* [http://unapi.info unAPI] has a technique for embedding IDs in html so that they can be retrieved from an unAPI service.
* [http://www.taguri.org/ Tag URI] an algorithm that lets people mint identifiers that no one else using the same algorithm could ever mint.

== Related Discussion ==
* [http://microformats.org/discuss/mail/microformats-discuss/2006-April/003726.html UID, URL, live microformats]
* [http://microformats.org/discuss/mail/microformats-discuss/2005-November/002046.html format for identifiers]

uid-brainstorming

2006-04-26T02:52:34Z

Ed Summers: added some experience

= UID Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a UID microformat.

== Authors ==

* Tantek Çelik
* Ed Summers

== Experience ==

* a microformat for indicating something *is* an identifier rather than the solved problem of providing a microformat *for* identifiers ([http://www.ietf.org/rfc/rfc2396.txt RFC 2396])

* Tantek has had conversations with LiveClipboard folks and upcoming.org who have had questions about how to do UID properly in hCard and hCalendar so a separate microformat that those two could call out to would serve a real need.

* It would be useful for autodiscovery puposes to be able to follow a network resolvabale UID and extract more metadata from the referenced UID.

* Efforts such as [http://unapi.info unAPI] have a real need for marking up identifiers so that they can be used for retrieving more detailed metadata.

* Greasemonkey and other browser based scripts could make real use of URIs found in pages as opposed to resorting to elaborate regexen. See Jon Udell's [http://weblog.infoworld.com/udell/stories/2002/12/11/librarylookup.html LibraryLookup] project.

* GoogleScholar embed identifiers in their citations and it would enable moving citations from the browser to a citation manager greatly if there were a way to mark them up.

== Goals Requirements ==

* a method of publishing an asserted globally unique identifier for a piece of content or a referenced item

== Thoughts ==

=== UIDs that are URLs ===

It seems like in the 80% case (perhaps 99.99% case on the Web), a UID is going to be a URL, thus a common pattern will likely be things like:

<pre><nowiki>
<a class="url uid" href="http://example.com/contentspace/somenumber">the item</a>
</nowiki></pre>

=== SHOULD rather than MUST ===

A UID SHOULD be a URL rather than MUST. The UID microformat will ordinarily be a URL, but it should be flexible enough to allow it to contain non-network resolvable URIs.

=== UID + URL -> permalink? ===

Can you infer that if something is a URL and a UID that it is also a permalink? It seems so. I can't think of any semantic of "permalink" that isn't covered by the union of the semantics of URL and UID.

=== abbr pattern ===

Use the [[abbr-design-pattern]] to allow identifiers to be more fully described.
<pre>
<abbr class="uid" title="urn:isbn:0950788120">0 9507881-2-0</abbr>
</pre>

== Proposals ==

=== Just use UID from hCard ===

* Tantek proposed that we see if we can reuse uid from [[hcard|hCard]], similar to how we have reused [[geo]] and [[adr]] from [[hcard|hCard]].

=== Create a URI microformat ===

* Xiaoming proposed leaving UID intact in hcalendar and hcard, because whatever written in rfc2426/rfc2445 and their examples cannot be easily changed, and they seem to work well with hcalendar/hcard. Instead a new "URI" microformat should be established for the purpose of indicating something *is* an identifier in general.In this case you can easily reference URI RFC and no further elaboration about persistence, resolvability or uniqueness will be necessary because these issues are addressed by various URI specifications.

== References ==
* [[adr]]
* [[geo]]
* [[hcard|hCard]]
* [[hcalendar|hCalendar]]
* [[abbr-design-pattern]]

== See Also ==
* [http://www.iana.org/assignments/urn-namespaces IANA URN Namespaces - RFC2141, RFC3406]
* [http://www.iana.org/assignments/uri-schemes.html IANA Uniform Resource Identifer (URI) Schemes]
* [http://ocoins.info COinS] for putting attaching openurl context objexts to a span.
* [http://unapi.info unAPI] has a technique for embedding IDs in html so that they can be retrieved from an unAPI service.
* [http://www.taguri.org/ Tag URI] an algorithm that lets people mint identifiers that no one else using the same algorithm could ever mint.

== Related Discussion ==
* [http://microformats.org/discuss/mail/microformats-discuss/2006-April/003726.html UID, URL, live microformats]
* [http://microformats.org/discuss/mail/microformats-discuss/2005-November/002046.html format for identifiers]

uid-brainstorming

2006-04-26T02:36:42Z

Ed Summers: removed specific URI schemes

= UID Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a UID microformat.

== Authors ==

* Tantek Çelik
* Ed Summers

== Experience ==

* a microformat for indicating something *is* an identifier rather than the solved problem of providing a microformat *for* identifiers ([http://www.ietf.org/rfc/rfc2396.txt RFC 2396])

== Goals Requirements ==

* a method of publishing an asserted globally unique identifier for a piece of content or a referenced item

== Thoughts ==

=== UIDs that are URLs ===

It seems like in the 80% case (perhaps 99.99% case on the Web), a UID is going to be a URL, thus a common pattern will likely be things like:

<pre><nowiki>
<a class="url uid" href="http://example.com/contentspace/somenumber">the item</a>
</nowiki></pre>

=== Should rather than Must ===

A UID *should* rather than *must* be a URL. The UID microformat will ordinarily be a URL, but it should be flexible enough to allow it to contain non-network resolvable URIs.

=== UID + URL -> permalink? ===

Can you infer that if something is a URL and a UID that it is also a permalink? It seems so. I can't think of any semantic of "permalink" that isn't covered by the union of the semantics of URL and UID.

=== abbr pattern ===

Use the [[abbr-design-pattern]] to allow identifiers to be more fully described.
<pre>
<abbr class="uid" title="urn:isbn:0950788120">0 9507881-2-0</abbr>
</pre>

== Proposals ==

=== Just use UID from hCard ===

* Tantek proposed that we see if we can reuse uid from [[hcard|hCard]], similar to how we have reused [[geo]] and [[adr]] from [[hcard|hCard]].

=== Create a URI microformat ===

* Xiaoming proposed leaving UID intact in hcalendar and hcard, because whatever written in rfc2426/rfc2445 and their examples cannot be easily changed, and they seem to work well with hcalendar/hcard. Instead a new "URI" microformat should be established for the purpose of indicating something *is* an identifier in general.In this case you can easily reference URI RFC and no further elaboration about persistence, resolvability or uniqueness will be necessary because these issues are addressed by various URI specifications.

== References ==
* [[adr]]
* [[geo]]
* [[hcard|hCard]]
* [[hcalendar|hCalendar]]
* [[abbr-design-pattern]]

== See Also ==
* [http://www.iana.org/assignments/urn-namespaces IANA URN Namespaces - RFC2141, RFC3406]
* [http://www.iana.org/assignments/uri-schemes.html IANA Uniform Resource Identifer (URI) Schemes]
* [http://ocoins.info COinS] for putting attaching openurl context objexts to a span.
* [http://unapi.info unAPI] has a technique for embedding IDs in html so that they can be retrieved from an unAPI service.
* [http://www.taguri.org/ Tag URI] an algorithm that lets people mint identifiers that no one else using the same algorithm could ever mint.

== Related Discussion ==
* [http://microformats.org/discuss/mail/microformats-discuss/2006-April/003726.html UID, URL, live microformats]
* [http://microformats.org/discuss/mail/microformats-discuss/2005-November/002046.html format for identifiers]

uid-brainstorming

2006-04-26T02:04:52Z

Ed Summers: /* create a URI microformat */

= UID Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a UID microformat.

== Authors ==

* Tantek Çelik
* Ed Summers

== Experience ==

* a microformat for indicating something *is* an identifier rather than the solved problem of providing a microformat *for* identifiers ([http://www.ietf.org/rfc/rfc2396.txt RFC 2396])

== Goals Requirements ==

* a method of publishing an asserted globally unique identifier for a piece of content or a referenced item

== Thoughts ==

=== UIDs that are URLs ===

It seems like in the 80% case (perhaps 99.99% case on the Web), a UID is going to be a URL, thus a common pattern will likely be things like:

<pre><nowiki>
<a class="url uid" href="http://example.com/contentspace/somenumber">the item</a>
</nowiki></pre>

=== Should rather than Must ===

A UID *should* rather than *must* be a URL. The UID microformat will ordinarily be a URL, but it should be flexible enough to allow it to contain non-network resolvable URIs.

=== UID + URL -> permalink? ===

Can you infer that if something is a URL and a UID that it is also a permalink? It seems so. I can't think of any semantic of "permalink" that isn't covered by the union of the semantics of URL and UID.

=== abbr pattern ===

Use the [[abbr-design-pattern]] to allow identifiers to be more fully described.
<pre>
<abbr class="uid" title="urn:isbn:0950788120">0 9507881-2-0</abbr>
</pre>

== Proposals ==

=== Just use UID from hCard ===

* Tantek proposed that we see if we can reuse uid from [[hcard|hCard]], similar to how we have reused [[geo]] and [[adr]] from [[hcard|hCard]].

=== Create a URI microformat ===

* Xiaoming proposed leaving UID intact in hcalendar and hcard, because whatever written in rfc2426/rfc2445 and their examples cannot be easily changed, and they seem to work well with hcalendar/hcard. Instead a new "URI" microformat should be established for the purpose of indicating something *is* an identifier in general.In this case you can easily reference URI RFC and no further elaboration about persistence, resolvability or uniqueness will be necessary because these issues are addressed by various URI specifications.

== References ==
* [[adr]]
* [[geo]]
* [[hcard|hCard]]
* [[hcalendar|hCalendar]]
* [[abbr-design-pattern]]

== See Also ==
* [http://www.ietf.org/rfc/rfc2396.txt RFC 2396] Uniform Resource Identifiers
* [http://www.ietf.org/rfc/rfc4452.txt RFC 4452] the "info" URI scheme for information assets with identifiers in public namespaces.
* [http://ocoins.info COinS] for putting attaching openurl context objexts to a span.
* [http://unapi.info unAPI] has a technique for embedding IDs in html so that they can be retrieved from an unAPI service.
* [http://www.taguri.org/ Tag URI] an algorithm that lets people mint identifiers that no one else using the same algorithm could ever mint.
* [http://www.iana.org/assignments/urn-namespaces IANA URN Namespaces - RFC2141, RFC3406]
* [http://www.iana.org/assignments/uri-schemes.html IANA Uniform Resource Identifer (URI) Schemes]

== Related Discussion ==
* [http://microformats.org/discuss/mail/microformats-discuss/2006-April/003726.html UID, URL, live microformats]
* [http://microformats.org/discuss/mail/microformats-discuss/2005-November/002046.html format for identifiers]

uid-brainstorming

2006-04-26T02:04:29Z

Ed Summers: /* create a URI microformat */

= UID Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a UID microformat.

== Authors ==

* Tantek Çelik
* Ed Summers

== Experience ==

* a microformat for indicating something *is* an identifier rather than the solved problem of providing a microformat *for* identifiers ([http://www.ietf.org/rfc/rfc2396.txt RFC 2396])

== Goals Requirements ==

* a method of publishing an asserted globally unique identifier for a piece of content or a referenced item

== Thoughts ==

=== UIDs that are URLs ===

It seems like in the 80% case (perhaps 99.99% case on the Web), a UID is going to be a URL, thus a common pattern will likely be things like:

<pre><nowiki>
<a class="url uid" href="http://example.com/contentspace/somenumber">the item</a>
</nowiki></pre>

=== Should rather than Must ===

A UID *should* rather than *must* be a URL. The UID microformat will ordinarily be a URL, but it should be flexible enough to allow it to contain non-network resolvable URIs.

=== UID + URL -> permalink? ===

Can you infer that if something is a URL and a UID that it is also a permalink? It seems so. I can't think of any semantic of "permalink" that isn't covered by the union of the semantics of URL and UID.

=== abbr pattern ===

Use the [[abbr-design-pattern]] to allow identifiers to be more fully described.
<pre>
<abbr class="uid" title="urn:isbn:0950788120">0 9507881-2-0</abbr>
</pre>

== Proposals ==

=== Just use UID from hCard ===

* Tantek proposed that we see if we can reuse uid from [[hcard|hCard]], similar to how we have reused [[geo]] and [[adr]] from [[hcard|hCard]].

=== create a URI microformat ===

* Xiaoming proposed leaving UID intact in hcalendar and hcard, because whatever written in rfc2426/rfc2445 and their examples cannot be easily changed, and they seem to work well with hcalendar/hcard. Instead a new "URI" microformat should be established for the purpose of indicating something *is* an identifier in general.In this case you can easily reference URI RFC and no further elaboration about persistence, resolvability or uniqueness will be necessary because these issues are addressed by various URI specifications.

== References ==
* [[adr]]
* [[geo]]
* [[hcard|hCard]]
* [[hcalendar|hCalendar]]
* [[abbr-design-pattern]]

== See Also ==
* [http://www.ietf.org/rfc/rfc2396.txt RFC 2396] Uniform Resource Identifiers
* [http://www.ietf.org/rfc/rfc4452.txt RFC 4452] the "info" URI scheme for information assets with identifiers in public namespaces.
* [http://ocoins.info COinS] for putting attaching openurl context objexts to a span.
* [http://unapi.info unAPI] has a technique for embedding IDs in html so that they can be retrieved from an unAPI service.
* [http://www.taguri.org/ Tag URI] an algorithm that lets people mint identifiers that no one else using the same algorithm could ever mint.
* [http://www.iana.org/assignments/urn-namespaces IANA URN Namespaces - RFC2141, RFC3406]
* [http://www.iana.org/assignments/uri-schemes.html IANA Uniform Resource Identifer (URI) Schemes]

== Related Discussion ==
* [http://microformats.org/discuss/mail/microformats-discuss/2006-April/003726.html UID, URL, live microformats]
* [http://microformats.org/discuss/mail/microformats-discuss/2005-November/002046.html format for identifiers]

uid-brainstorming

2006-04-26T02:03:23Z

Ed Summers: reformatting

= UID Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a UID microformat.

== Authors ==

* Tantek Çelik
* Ed Summers

== Experience ==

* a microformat for indicating something *is* an identifier rather than the solved problem of providing a microformat *for* identifiers ([http://www.ietf.org/rfc/rfc2396.txt RFC 2396])

== Goals Requirements ==

* a method of publishing an asserted globally unique identifier for a piece of content or a referenced item

== Thoughts ==

=== UIDs that are URLs ===

It seems like in the 80% case (perhaps 99.99% case on the Web), a UID is going to be a URL, thus a common pattern will likely be things like:

<pre><nowiki>
<a class="url uid" href="http://example.com/contentspace/somenumber">the item</a>
</nowiki></pre>

=== Should rather than Must ===

A UID *should* rather than *must* be a URL. The UID microformat will ordinarily be a URL, but it should be flexible enough to allow it to contain non-network resolvable URIs.

=== UID + URL -> permalink? ===

Can you infer that if something is a URL and a UID that it is also a permalink? It seems so. I can't think of any semantic of "permalink" that isn't covered by the union of the semantics of URL and UID.

=== abbr pattern ===

Use the [[abbr-design-pattern]] to allow identifiers to be more fully described.
<pre>
<abbr class="uid" title="urn:isbn:0950788120">0 9507881-2-0</abbr>
</pre>

== Proposals ==

=== Just use UID from hCard ===

* Tantek proposed that we see if we can reuse uid from [[hcard|hCard]], similar to how we have reused [[geo]] and [[adr]] from [[hcard|hCard]].

=== create a URI microformat ===

* Xiaoming proposed leaving UID intact in hcalendar and hcard, because whatever written in rfc2426/rfc2445 and their examples cannot be easily changed, and they seem to work well with hcalendar/hcard. Instead a new "URI" microformat should be established for the purpose of indicating something *is* an identifier in general.In this case you can easily reference URI RFC and no further elaboration about persistence/resovlable/uniqueness, because these issues are addressed by various URI specifications.

== References ==
* [[adr]]
* [[geo]]
* [[hcard|hCard]]
* [[hcalendar|hCalendar]]
* [[abbr-design-pattern]]

== See Also ==
* [http://www.ietf.org/rfc/rfc2396.txt RFC 2396] Uniform Resource Identifiers
* [http://www.ietf.org/rfc/rfc4452.txt RFC 4452] the "info" URI scheme for information assets with identifiers in public namespaces.
* [http://ocoins.info COinS] for putting attaching openurl context objexts to a span.
* [http://unapi.info unAPI] has a technique for embedding IDs in html so that they can be retrieved from an unAPI service.
* [http://www.taguri.org/ Tag URI] an algorithm that lets people mint identifiers that no one else using the same algorithm could ever mint.
* [http://www.iana.org/assignments/urn-namespaces IANA URN Namespaces - RFC2141, RFC3406]
* [http://www.iana.org/assignments/uri-schemes.html IANA Uniform Resource Identifer (URI) Schemes]

== Related Discussion ==
* [http://microformats.org/discuss/mail/microformats-discuss/2006-April/003726.html UID, URL, live microformats]
* [http://microformats.org/discuss/mail/microformats-discuss/2005-November/002046.html format for identifiers]

uid-brainstorming

2006-04-26T02:02:39Z

Ed Summers: added xiaoming's proposal for a uri microformat

= UID Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a UID microformat.

== Authors ==

* Tantek Çelik
* Ed Summers

== Experience ==

* a microformat for indicating something *is* an identifier rather than the solved problem of providing a microformat *for* identifiers ([http://www.ietf.org/rfc/rfc2396.txt RFC 2396])

== Goals Requirements ==

* a method of publishing an asserted globally unique identifier for a piece of content or a referenced item

== Thoughts ==

=== UIDs that are URLs ===

It seems like in the 80% case (perhaps 99.99% case on the Web), a UID is going to be a URL, thus a common pattern will likely be things like:

<pre><nowiki>
<a class="url uid" href="http://example.com/contentspace/somenumber">the item</a>
</nowiki></pre>

=== Should rather than Must ===

A UID *should* rather than *must* be a URL. The UID microformat will ordinarily be a URL, but it should be flexible enough to allow it to contain non-network resolvable URIs.

=== UID + URL -> permalink? ===

Can you infer that if something is a URL and a UID that it is also a permalink? It seems so. I can't think of any semantic of "permalink" that isn't covered by the union of the semantics of URL and UID.

=== abbr pattern ===

Use the [[abbr-design-pattern]] to allow identifiers to be more fully described.
<pre>
<abbr class="uid" title="urn:isbn:0950788120">0 9507881-2-0</abbr>
</pre>

== Proposals ==

=== Just use UID from hCard ===

* Tantek proposed that we see if we can reuse uid from [[hcard|hCard]], similar to how we have reused [[geo]] and [[adr]] from [[hcard|hCard]].

=== create a URI microformat ===

* Xiaoming proposed leaving UID intact in hcalendar and hcard, because
whatever written in rfc2426/rfc2445 and their examples cannot be
easily changed, and they seem to work well with hcalendar/hcard.

Instead a new "URI" microformat should be established for the purpose of indicating something *is* an identifier in general.In this case you can easily reference URI RFC and no further elaboration about persistence/resovlable/uniqueness, because these issues are addressed by various URI specifications.

== References ==
* [[adr]]
* [[geo]]
* [[hcard|hCard]]
* [[hcalendar|hCalendar]]
* [[abbr-design-pattern]]

== See Also ==
* [http://www.ietf.org/rfc/rfc2396.txt RFC 2396] Uniform Resource Identifiers
* [http://www.ietf.org/rfc/rfc4452.txt RFC 4452] the "info" URI scheme for information assets with identifiers in public namespaces.
* [http://ocoins.info COinS] for putting attaching openurl context objexts to a span.
* [http://unapi.info unAPI] has a technique for embedding IDs in html so that they can be retrieved from an unAPI service.
* [http://www.taguri.org/ Tag URI] an algorithm that lets people mint identifiers that no one else using the same algorithm could ever mint.
* [http://www.iana.org/assignments/urn-namespaces IANA URN Namespaces - RFC2141, RFC3406]
* [http://www.iana.org/assignments/uri-schemes.html IANA Uniform Resource Identifer (URI) Schemes]

== Related Discussion ==
* [http://microformats.org/discuss/mail/microformats-discuss/2006-April/003726.html UID, URL, live microformats]
* [http://microformats.org/discuss/mail/microformats-discuss/2005-November/002046.html format for identifiers]

uid-brainstorming

2006-04-26T01:57:09Z

Ed Summers: /* References */

uid-brainstorming

2006-04-26T01:53:53Z

Ed Summers: added notes about should & must

uid-examples

2006-04-23T20:11:18Z

Ed Summers: /* PubMed */

= UID Examples =

This page serves to document the current list of identifier examples from real world sites for the design of a simple identifier microformat.

== Participants ==

* Ed Summers

== Real-World Examples ==

=== Amazon ===

* [http://www.amazon.com/gp/product/073571245X/ book page]
* ISBN - Internation Standard Business Number

<pre>
<li><b>ISBN:</b> 073571245X</li>
</pre>

=== PubMed ===

* [http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?cmd=Retrieve&db=pubmed&dopt=Abstract&list_uids=16627279&query_hl=2&itool=pubmed_docsum citation]
* PubMedID
<pre>
<br>PMID: 16627279 [PubMed - as supplied by publisher]
</pre>

== Existing Practices ==

== See Also ==

* [[uid]]
* [[uid-formats]]
* [[uid-brainstorming]]
* [[hCard]]

uid-examples

2006-04-23T20:10:52Z

Ed Summers: /* Amazon */

= UID Examples =

This page serves to document the current list of identifier examples from real world sites for the design of a simple identifier microformat.

== Participants ==

* Ed Summers

== Real-World Examples ==

=== Amazon ===

* [http://www.amazon.com/gp/product/073571245X/ book page]
* ISBN - Internation Standard Business Number

<pre>
<li><b>ISBN:</b> 073571245X</li>
</pre>

=== PubMed ===

* [http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?cmd=Retrieve&db=pubmed&dopt=Abstract&list_uids=16627279&query_hl=2&itool=pubmed_docsum citation]
* PubMedID
*
<pre>
<br>PMID: 16627279 [PubMed - as supplied by publisher]
</pre>

== Existing Practices ==

== See Also ==

* [[uid]]
* [[uid-formats]]
* [[uid-brainstorming]]
* [[hCard]]

uid-examples

2006-04-23T15:35:27Z

Ed Summers:

uid-brainstorming

2006-04-23T15:03:22Z

Ed Summers: moved abbr stuff to Thoughts as it's not a proposal

uid-brainstorming

2006-04-23T13:27:34Z

Ed Summers: /* References */

uid-brainstorming

2006-04-23T13:25:57Z

Ed Summers: /* Just use UID from hCard */

uid-brainstorming

2006-04-23T13:24:27Z

Ed Summers: added abbr example

uid-brainstorming

2006-04-23T03:35:20Z

Ed Summers: /* Related Discussion */

uid

2006-04-22T17:37:52Z

Ed Summers: /* UID */

= UID =

This page documents an effort to define a microformat for [http://en.wikipedia.org/wiki/Category:Identifiers identifiers]. HTML already deals well with Uniform Resource Identifiers (URIs). However there are lots of other types of identifiers in web content that cannot be easily identified as such. Some of these include [http://www.isbn.org/standards/home/index.asp ISBN], [http://www.issn.org/ ISSN] [http://www.upcdatabase.com/ UPC], [http://en.wikipedia.org/wiki/ASIN ASIN], [http://musicbrainz.org/tagger/id-intro.html MusicBrainz IDs].

Per the microformats [[process]]

* [[uid-examples]]
* [[uid-formats]]
* [[uid-brainstorming]]

Please take a look, and contribute your thoughts and ideas.

uid-brainstorming

2006-04-22T04:40:50Z

Ed Summers: /* See Also */

= UID Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a UID microformat.

== Authors ==

* Ed Summers

== Experience ==

* a microformat for indicating something *is* an identifier rather than the solved problem of providing a microformat *for* identifiers ([http://www.ietf.org/rfc/rfc2396.txt RFC 2396])

== Goals Requirements ==

* can we reuse uid from [[hCard]]

== See Also ==
* [http://www.ietf.org/rfc/rfc2396.txt RFC 2396] Uniform Resource Identifiers
* [http://www.ietf.org/rfc/rfc4452.txt RFC 4452] the "info" URI scheme for information assets with identifiers in public namespaces.
* [http://ocoins.info COinS] for putting attaching openurl context objexts to a span.
* [http://unapi.info unAPI] has a technique for embedding IDs in html so that they can be retrieved from an unAPI service.
* [http://www.taguri.org/ Tag URI] an algorithm that lets people mint identifiers that no one else using the same algorithm could ever mint.

== Related Discussion ==
* [http://microformats.org/discuss/mail/microformats-discuss/2006-April/003726.html UID, URL, live microformats]

* [http://microformats.org/discuss/mail/microformats-discuss/2005-November/002046.html format for identifiers]

uid-brainstorming

2006-04-22T04:40:12Z

Ed Summers: /* See Also */

= UID Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a UID microformat.

== Authors ==

* Ed Summers

== Experience ==

* a microformat for indicating something *is* an identifier rather than the solved problem of providing a microformat *for* identifiers ([http://www.ietf.org/rfc/rfc2396.txt RFC 2396])

== Goals Requirements ==

* can we reuse uid from [[hCard]]

== See Also ==
* [http://www.ietf.org/rfc/rfc2396.txt RFC2396] Uniform Resource Identifiers
* [http://www.ietf.org/rfc/rfc4452.txt RFC4452] the "info" URI scheme for information assets with identifiers in public namespaces.
* [http://ocoins.info COinS] for putting attaching openurl context objexts to a span.
* [http://unapi.info unAPI] has a technique for embedding IDs in html so that they can be retrieved from an unAPI service.
* [http://www.taguri.org/ Tag URI] an algorithm that lets people mint identifiers that no one else using the same algorithm could ever mint.

== Related Discussion ==
* [http://microformats.org/discuss/mail/microformats-discuss/2006-April/003726.html UID, URL, live microformats]

* [http://microformats.org/discuss/mail/microformats-discuss/2005-November/002046.html format for identifiers]

uid-brainstorming

2006-04-22T04:39:41Z

Ed Summers: /* See Also */

= UID Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a UID microformat.

== Authors ==

* Ed Summers

== Experience ==

* a microformat for indicating something *is* an identifier rather than the solved problem of providing a microformat *for* identifiers ([http://www.ietf.org/rfc/rfc2396.txt RFC 2396])

== Goals Requirements ==

* can we reuse uid from [[hCard]]

== See Also ==

* [http://www.ietf.org/rfc/rfc2396.txt RFC 2396] Uniform Resource Identifiers
* [http://www.ietf.org/rfc/rfc4452.txt RFC 4452] the "info" URI scheme for information assets with identifiers in public namespaces.
* [http://ocoins.info COinS] for putting attaching openurl context objexts to a span.
* [http://unapi.info unAPI] has a technique for embedding IDs in html so that they can be retrieved from an unAPI service.
* [http://www.taguri.org/ Tag URI] an algorithm that lets people mint identifiers that no one else using the same algorithm could ever mint.

== Related Discussion ==
* [http://microformats.org/discuss/mail/microformats-discuss/2006-April/003726.html UID, URL, live microformats]

* [http://microformats.org/discuss/mail/microformats-discuss/2005-November/002046.html format for identifiers]

uid-brainstorming

2006-04-22T04:38:17Z

Ed Summers: /* Experience */

= UID Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a UID microformat.

== Authors ==

* Ed Summers

== Experience ==

* a microformat for indicating something *is* an identifier rather than the solved problem of providing a microformat *for* identifiers ([http://www.ietf.org/rfc/rfc2396.txt RFC 2396])

== Goals Requirements ==

* can we reuse uid from [[hCard]]

== See Also ==

* [http://www.ietf.org/rfc/rfc4452.txt RFC 4452] the "info" URI scheme for information assets with identifiers in public namespaces.
* [http://ocoins.info COinS] for putting attaching openurl context objexts to a span.
* [http://unapi.info unAPI] has a technique for embedding IDs in html so that they can be retrieved from an unAPI service.
* [http://www.taguri.org/ Tag URI] an algorithm that lets people mint identifiers that no one else using the same algorithm could ever mint.

== Related Discussion ==
* [http://microformats.org/discuss/mail/microformats-discuss/2006-April/003726.html UID, URL, live microformats]

* [http://microformats.org/discuss/mail/microformats-discuss/2005-November/002046.html format for identifiers]

uid-brainstorming

2006-04-22T04:14:27Z

Ed Summers: /* Related Discussion */

= UID Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a UID microformat.

== Authors ==

* Ed Summers

== Experience ==

== Goals Requirements ==

* can we reuse uid from [[hCard]]

== See Also ==

* [http://www.ietf.org/rfc/rfc4452.txt RFC 4452] the "info" URI scheme for information assets with identifiers in public namespaces.
* [http://ocoins.info COinS] for putting attaching openurl context objexts to a span.
* [http://unapi.info unAPI] has a technique for embedding IDs in html so that they can be retrieved from an unAPI service.
* [http://www.taguri.org/ Tag URI] an algorithm that lets people mint identifiers that no one else using the same algorithm could ever mint.

== Related Discussion ==
* [http://microformats.org/discuss/mail/microformats-discuss/2006-April/003726.html UID, URL, live microformats]

* [http://microformats.org/discuss/mail/microformats-discuss/2005-November/002046.html format for identifiers]

uid-brainstorming

2006-04-22T04:13:23Z

Ed Summers: /* Goals Requirements */

uid-brainstorming

2006-04-22T04:12:12Z

Ed Summers: /* UID Brainstorming */

= UID Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a UID microformat.

== Authors ==

* Ed Summers

== Experience ==

== Goals Requirements ==

* leverage uid from [[hCard]]

== See Also ==

* [http://www.ietf.org/rfc/rfc4452.txt RFC 4452] the "info" URI scheme for information assets with identifiers in public namespaces.
* [http://ocoins.info COinS] for putting attaching openurl context objexts to a span.
* [http://unapi.info unAPI] has a technique for embedding IDs in html so that they can be retrieved from an unAPI service.
* [http://www.taguri.org/ Tag URI] an algorithm that lets people mint identifiers that no one else using the same algorithm could ever mint.

== Related Discussion ==
* [http://microformats.org/discuss/mail/microformats-discuss/2006-April/003726.html UID, URL, live microformats]

* [http://microformats.org/discuss/mail/microformats-discuss/2005-November/002106.html format for identifiers]

uid-brainstorming

2006-04-21T21:31:12Z

Ed Summers: /* See Also */

= UID Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a UID microformat.

== Authors ==

* Ed Summers

== Experience ==

== Goals Requirements ==

== See Also ==

* [http://www.ietf.org/rfc/rfc4452.txt RFC 4452] the "info" URI scheme for information assets with identifiers in public namespaces.
* [http://ocoins.info COinS] for putting attaching openurl context objexts to a span.
* [http://unapi.info unAPI] has a technique for embedding IDs in html so that they can be retrieved from an unAPI service.
* [http://www.taguri.org/ Tag URI] an algorithm that lets people mint identifiers that no one else using the same algorithm could ever mint.

== Related Discussion ==
* [http://microformats.org/discuss/mail/microformats-discuss/2006-April/003726.html UID, URL, live microformats]

* [http://microformats.org/discuss/mail/microformats-discuss/2005-November/002106.html format for identifiers]

uid-brainstorming

2006-04-21T21:30:55Z

Ed Summers: /* See Also */

= UID Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a UID microformat.

== Authors ==

* Ed Summers

== Experience ==

== Goals Requirements ==

== See Also ==

* [http://www.ietf.org/rfc/rfc4452.txt RFC 4452] the "info" URI scheme for information assets with identifiers in public namespaces.
* [http://ocoins.info COinS] for putting attaching openurl context objexts to a span.
* [http://unapi.info unAPI] has a technique for embedding IDs in html so that they can be retrieved from an unAPI service.
* [http://www.taguri.org/ Tag URI] an algorithm lets people mint identifiers that no one else using the same algorithm could ever mint.

== Related Discussion ==
* [http://microformats.org/discuss/mail/microformats-discuss/2006-April/003726.html UID, URL, live microformats]

* [http://microformats.org/discuss/mail/microformats-discuss/2005-November/002106.html format for identifiers]

uid-brainstorming

2006-04-21T21:30:01Z

Ed Summers: /* See Also */

= UID Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a UID microformat.

== Authors ==

* Ed Summers

== Experience ==

== Goals Requirements ==

== See Also ==

* [http://www.ietf.org/rfc/rfc4452.txt RFC 4452] the "info" URI scheme for information assets with identifiers in public namespaces.
* [http://ocoins.info COinS] for putting attaching openurl context objexts to a span.
* [http://unapi.info unAPI] has a technique for embedding IDs in html so that they can be retrieved from an unAPI service.
* [http://www.taguri.org/ Tag URI] an algorithm lets people mint — create — identifiers that no one else using the same algorithm could ever mint.

== Related Discussion ==
* [http://microformats.org/discuss/mail/microformats-discuss/2006-April/003726.html UID, URL, live microformats]

* [http://microformats.org/discuss/mail/microformats-discuss/2005-November/002106.html format for identifiers]

uid

2006-04-21T21:27:32Z

Ed Summers: /* UID */

= UID =

This page documents the effort to define a microformat for [http://en.wikipedia.org/wiki/Category:Identifiers identifiers]. Identifiers are currently found all over the web but not in a predictable way. Examples of identifiers include [http://www.isbn.org/standards/home/index.asp ISBN], [http://www.issn.org/ ISSN] [http://www.upcdatabase.com/ UPC], [http://en.wikipedia.org/wiki/ASIN ASIN], [http://musicbrainz.org/tagger/id-intro.html MusicBrainz IDs]. Indeed it could be argued that URLs themselves are identifiers in the abstract. How cool would it be to able to identify, capture and repurpose these while browsing the web? First step is to simply allow them to be discovered.

Per the microformats [[process]]

* [[uid-examples]]
* [[uid-formats]]
* [[uid-brainstorming]]

Please take a look, and contribute your thoughts and ideas.

uid-brainstorming

2006-04-21T21:16:02Z

Ed Summers: /* See Also */

= UID Brainstorming =

This page is for brainstorming about ideas, proposals, constraints, requirements for a UID microformat.

== Authors ==

* Ed Summers

== Experience ==

== Goals Requirements ==

== See Also ==

* [http://ocoins.info COinS] for putting attaching openurl context objexts to a span.
* [http://unapi.info unAPI] has a technique for embedding IDs in html so that they can be retrieved from an unAPI service.

== Related Discussion ==
* [http://microformats.org/discuss/mail/microformats-discuss/2006-April/003726.html UID, URL, live microformats]

* [http://microformats.org/discuss/mail/microformats-discuss/2005-November/002106.html format for identifiers]

uid

2006-04-21T21:08:52Z

Ed Summers: /* UID */

= UID =

This page documents the effort to define a microformat for [http://en.wikipedia.org/wiki/Category:Identifiers identifiers]. Identifiers are currently found all over the web but not in a predictable way. Examples of identifiers include [http://www.isbn.org/standards/home/index.asp ISBN], [http://www.issn.org/ ISSN] [http://www.upcdatabase.com/ UPC], [http://en.wikipedia.org/wiki/ASIN ASIN], [http://musicbrainz.org/tagger/id-intro.html MusicBrainz IDs]. Indeed it could be argued that URLs themselves are identifiers in the abstract. How cool would it be to able to identify these and resolve them? Welcome to the dream of the semantic web.

Per the microformats [[process]]

* [[uid-examples]]
* [[uid-formats]]
* [[uid-brainstorming]]

Please take a look, and contribute your thoughts and ideas.

uid

2006-04-21T21:06:53Z

Ed Summers: /* UID */

= UID =

This page documents the effort to define a microformat for identifiers. Identifiers are currently found all over the web but not in a predictable way. Examples of identifiers include [http://www.isbn.org/standards/home/index.asp ISBN], [http://www.issn.org/ ISSN] [http://www.upcdatabase.com/ UPC], [http://en.wikipedia.org/wiki/ASIN ASIN], [http://musicbrainz.org/tagger/id-intro.html MusicBrainz IDs]. Indeed it could be argued that URLs themselves are identifiers in the abstract. How cool would it be to able to identify these and resolve them? Welcome to the dream of the semantic web.

Per the microformats [[process]]

* [[uid-examples]]
* [[uid-formats]]
* [[uid-brainstorming]]

Please take a look, and contribute your thoughts and ideas.