citation-examples: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
Line 245: Line 245:
This is from a detail page on Amazon.com for a book.
This is from a detail page on Amazon.com for a book.


<pre><nowiki>
* title
<a name='citing' ></a><b>This book cites 10 books:</b><br />
* author
<ul...>
* publicationseriesname
  <li>
* page
    <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 ==  
== PubMed Medical Journal Example ==  

Revision as of 05:42, 10 April 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.

(For a cleaner version, see [1])

ABC-CLIO Product detail page

  • subtitle
  • title
  • author
  • Image
  • pubdate
  • pages
  • volumes
  • trimsize (book dimentions 8.5x11)
  • Format
  • Price
  • ISBN

Greenwood Press home page featured book

  • title
  • sub_title
  • author
  • isbn
  • price
  • bookDescription

Greenwood Press Product detail page

  • Title
  • SubTitle
  • authors
  • AuthorsNote
  • BookCode
  • Isbn
  • PageColation
  • Imprint
  • PubDate
  • ListPrice
  • Availability
  • MediaType
  • BookInformation (categories)
  • LC Card Number
  • LCC Class
  • Dewey Class:

Marshall Cavendish product page

  • ISBN Number
  • Series
  • Title
  • Imprint
  • Specifications (dimentions/weight)
  • Authors
  • Target Audience
  • Price
  • description

Oxford University Press (USA) homepage

  • title
  • subTitle
  • edition
  • byline
  • isbnNumber
  • format - hardback
  • publicationDate
  • price
  • description
  • related

Oxford University Press (USA) Product page

  • title
  • subTitle
  • edition
  • byline
  • image
  • isbnNumber
  • format - hardback
  • pages
  • publicationDate
  • availability
  • cost

Thomson Gale product detail page

  • title_main
  • excerp
  • Volume
  • Published by
  • description
  • Published/Released
  • ISBN:
  • Product number
  • Page count:
  • Shipping Weight:
  • price

Breakdown of Citation Elements

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

Book titles:

Book Series Name:

Sub-title:

Author:

Publication Date:

Volumes:

ISBN:

Book Edition:

Added by Tim

RFC vCard Example

  • refID
  • title
  • publication
  • title
  • Journal
  • Volume
  • Issue
  • page
  • pubdate
  • RFC ID

W3C XHTML Spec Example

  • refID
  • URL
  • title
  • subtitle
  • part (1 of X)
  • journal
  • authors
  • pubdate
  • language
  • ISO/IEC ID
  • RFC ID

XHTML1.0 Spec references

CiteProc XHTML Output

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

  • refID
  • author
  • date
  • title
  • volume
  • issue
  • page
  • issue
  • type (book, newspaper, proceedings)
  • Edition
  • publisher

ACM Digital Library Search Result Examples

The ACM Digital Library is a heavily used computer science literature database.

  • title
  • authors
  • Pages
  • format
  • Additional Information
  • abstract
  • index terms
  • journal
  • issue
  • volume
  • pubdate
  • DOI

IEEE IEEExplore Search Results Markup

  • title
  • authors
  • issue
  • Volume
  • Issue
  • pubdate
  • Page
  • Digital Object Identifier (DOI)
  • Summary

CiteSeer database search results

The CiteSeer database has been another heavily used Computer Science online resource, and it has minimal markup:

  • author
  • title
  • publication (where it was found)
  • pages
  • pubdate
  • URL

CiteULike.org citation listing

CiteULike

  • title
  • author
  • subjects
  • image
  • Vol
  • No.
  • pubdate
  • page

Links to services with the following IDs embedded in the link

  • Z3988
  • DOI
  • Pubmed
  • Hubmed

Amazon.com citation info

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

  • title
  • author
  • publicationseriesname
  • page

PubMed Medical Journal Example

  • abstract
  • title
  • publisher
  • date/time published
  • Review (BOOLEAN YES/NO)
  • PubMedID

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

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