citation-examples: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
Line 570: Line 570:


'''The burden of proof is on *going* hierarchical, rather than a simpler flat solution.  Complexity must be justified, not simplicity.'''
'''The burden of proof is on *going* hierarchical, rather than a simpler flat solution.  Complexity must be justified, not simplicity.'''
Why is hierarchy necessarily complex? I'd argue just the opposite.


... 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.
... 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.
Line 575: Line 577:
'''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.'''
'''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.'''


And the problem with focusing on existing practice is it becomes self-fulfilling. I'm not saying you need to cover everything upfront, but the basic model needs to be designed in such a way that it can be easily extended to do just that. Just focusing on existing practices as manifest, for example, in BibTeX, will not get you that.


== Styles ==
== Styles ==

Revision as of 04:34, 20 February 2006

Citation Examples

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:

Contributors

Citation Mark Up in the Wild

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

View complete citations in the wild. (why is this a separate page?)

Book titles:

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

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

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

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

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

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

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

<span id="ctlBookDetailHeader_lblTitle" class="ProdTitle">Talk and Interaction in Social Research Methods</span> (SAGE Publications)

Also, many examples where books presented in table format with Title as cell header, or presented "Title: "

Book Series Name:

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

Sub-title:

<span id="subtitle" class="productsubtitle"></span>
(ABC-CLIO)


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

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


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

Author:

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


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


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


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

Publication Date:

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


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


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


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

Volumes:

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

ISBN:

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


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

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


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


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


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

Book Edition:

<div class="edition"> Revised and Expanded Edition </div>
(OUP)

Added by Tim

RFC vCard Example

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.

vCard RFC

W3C XHTML Spec Example

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

XHTML1.0 Spec references

CiteProc XHTML Output

The XHTML output for CiteProc[1] 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:

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

ACM Digital Library Search Result Examples

The 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:


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

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

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:


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

IEEE IEEExplore Search Results Markup

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



CiteSeer database search results

The 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:

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


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:

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

CiteULike.org citation listing

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:

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

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

<div class="content">

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

<h2>Authors</h2>

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

<ul>
</ul>


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

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

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

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

</ul>



</td>
</tr>
</table>

Citeproc XHTML output

I'm the author of the citeproc project, which includes a micro-format of sorts (though I never thought of it as such) in its XHTML output mode. See 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.

Why is hierarchy necessarily complex? I'd argue just the opposite.

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

And the problem with focusing on existing practice is it becomes self-fulfilling. I'm not saying you need to cover everything upfront, but the basic model needs to be designed in such a way that it can be easily extended to do just that. Just focusing on existing practices as manifest, for example, in BibTeX, will not get you that.

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.