citation-formats

From Microformats Wiki
Revision as of 02:07, 3 November 2005 by Brian (talk | contribs) (→‎OpenURL)
Jump to navigation Jump to search

This page will display several different types of citation format types. The idea is to compare what properties are common amonst all of the formats and which ones should be blended into this microformat.

Comparison chart

The following chart maps the terms from one implementation to another. This is important because if all the properties are introduced to this microformats, then its possible to map them to a number of different formats. The table currently only uses Dublin Core, MODS, and bibTeX. Each column has all the properties and their equivalent in each format. If there is no corresponding property the cell is grey. At the bottom of the list are the unique terms to each format. Dublin core has basic terms and terms that extend the basic ones. If the property is an extention of a basic term it is in ()'s. MODS uses XML, so any sub-properties are listed in their tree form, property/sub-property.

THIS IS NOT DEFINIATIVE, any errors should be corrected. More formats will be added to the list as they are mapped.

Dublin Core MODS bibTeX Z39.80
Title (alternative) titleInfo/title
titleInfo/PartNum		 booktitle
title
chapter
number
pages
volume
series		 needs mapping
creator name/namePart author
creator		 needs mapping
subject subject/topic needs mapping
Description (abstract | tableOfContents) abstract
note
tableOfContents		 abstract
annotation
note
contents		 needs mapping
Contributer name editor? needs mapping
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 conference
Date of Publication
Date of Update/Revisou/Issuance of Database Record
Former Date
Entry date for Database Record
Database Update
Year of Publication
Type typeOfResource
genre		 @class
type		 needs mapping
Format (extent | medium) physicalDescription/internetMediaType
physicalDescription/extent
physicalDescription/form		 published needs mapping
identifier (bibliographicCitation) identifier ISBN
ISSN
LCCN
URL		 ISBN
Identifier
Report Identfier
ISSN
Source relatedItem needs mapping
language language language needs mapping
Relation (...) relatedItem/... crossRef needs mapping
Coverage (spacial | temporal) subject/temporal
subject/geographic
subject/hierarchicalGeographic
subject/cartographics		 needs mapping
classifications needs mapping
Rights (accessRights | license) accessConditions copyright needs mapping
publisher publisher needs mapping
audience (educationLevel | mediator) targetAudience needs mapping
accualMethod
accualPeriodicaty
accualPolicy
instrcutionalMethod
provenance
rightsHolder		 location
extension
recordInfo		 address
afflilication
location
edition
institution
journal
key
keywords
mrnumber
organization
price
school
size		 needs mapping

Dublin Core Metadata

Dublin Core metadata uses a small vocabulary to descibe the data.

  • contributor
  • coverage
  • creator
  • date
  • description
  • format
  • identifier
  • language
  • publisher
  • relation
  • rights
  • source
  • subject
  • title
  • type

From those there are specialised types where are just refinments of the previous, for example:

  • abstract refines description.
  • accessRights refines rights

Guidelines for Encoding Bibliographic Citation Information in Dublin Core Metadata

MODS (Metadata Object Description Schema)

This is a format developed for the Libray of Congress for a bibliographic element set that may be used for a variety of purposes, and particularly for library applications.

http://www.loc.gov/standards/mods/

(the schema is very big, once i devote the proper time to review it, i will post more about the structure -brian)

XMLResume

<!ELEMENT pubs (pub+)>
<!ENTITY % pubElements "(artTitle|bookTitle|author|date|pubDate|publisher|pageNums|url)">
<!ELEMENT pub (para | %pubElements;)*>
<!ATTLIST pub id ID #IMPLIED>
<!ELEMENT artTitle (#PCDATA | link)*>
<!ELEMENT bookTitle (#PCDATA | link)*>
<!ELEMENT author (#PCDATA)>
<!ATTLIST author name IDREF #IMPLIED>
<!ELEMENT pubDate (month?, year)> <!-- Deprecated in 1.4.0. -->
<!ELEMENT publisher (#PCDATA | link | url)*>
<!ELEMENT pageNums (#PCDATA)>

BibTeX

Fields Used by Bibtex

abstract: An abstract of the work.
address: Publisher's address. For major publishing houses, 
       just the city is given. For small publishers, you can
help the reader by giving the complete address.
affiliation: The author's affiliation.
annote: An annotation. It is not used by he standard 
       bibliography styles, but may be used by others that
produce an annotated bibliography.
author: The name(s) of the author(s).
booktitle:  Title of a book, part of which is being cited. For 
       book entries, use the title field
instead.
chapter: A chapter (or section) number.
contents: A Table of Contents.
copyright: Copyright information.
crossref: The database key of the entry being cross-referenced.
edition:  The edition of a book - for example "Second". Notice that it is in capitals.
editor:  Name(s) of editor(s). If there is also an author 
       field, then the editor field gives the editor of the book
or collection in which the reference appears.
howpublished: How something strange has been published. The first word should be capitalized.
institution: The sponsoring institution of a technical report.
ISBN: The International Standard Book Number.
ISSN: The International Standard Serial Number. Used to identify a journal.
journal:  A journal name. Abbreviations are provided for many journals.
key:  Used for alphabetizing and creating a label when the 
       author and editor fields are missing. This field should
       not be confused with the key that appears at the
beginning of the reference.
keywords: Key words used for searching or possibly for annotation.
language: The language the document is written in.
LCCN: The Library of Congress Call Number.
location: A location associated with the entry, such as the city in which a conference took place.
month:  The month in which the work was published or, for an unpublished work, in which it was written.
mrnumber: The Mathematical Reviews number.
note: Any additional information that can help the reader. First word should be capitalized.
number:  The number of a journal, magazine, technical report, 
       or of a work in a series. An issue of a journal or
       magazine is usually identified by its volume and number;
       the organization that issues a technical report usually
       gives it a number; and sometimes books are given numbers
in a named series.
organization:  The organization that sponsors a conference or publishes a manual.
pages: One or more page numbers or ranges of number, such as 37--42, or 7,53,82--94.
price: The price of the material.
publisher: The publisher's name.
school: The name of the school where a thesis was written.
series: Then name given a series or set of books. When citing 
       an entire book, the title field gives its title and the
       optional series field gives the name of a series in which
the book was published.
size: The physical dimensions of the work.
title: The work's title.
type: The type of technical report - for example, "Research Note".
url: The WWW Universal Resource Locator that points to the 
       item being referenced. Often used for technical reports
to point to the FTP site where it resides.
volume: The volume of a journal or multivolume book.
year: The year of publication or, for an unpublished work, 
       the year it was written. It should only consist of
numerals, such as 1976.

BibTeX citation Types

A reference can be to any of a variety of types. Following is a list of types. Each one also explains the fields associated with that type. Any fields not listed as required or optional are considered to be ignored.

article: An article from a journal or magazine. Required 
       fields: author, title, journal, year. Optional fields:
volume, number, pages, month, note, key.
book: A book with an explicit publisher. Required fields: 
       author or editor, title, publisher, year. Optional
       fields: volume, series, address, edition, month, note,
key.
booklet:  A work that is printed and bound, but without a named 
       publisher or sponsoring institution. Required fields:
       title. Optional fields: author, howpublished, address,
month, year, note, key.
collection: A collection of works. Same as <a href="#proceedings">Proceedings</a>.
conference: The same as <a href="#inproceedings">Inproceedings</a>.
inbook: A part of a book, which may be a chapter and/or a 
       range of pages. Required fields: author or editor, title,
       chapter and/or pages, publisher, year. Optional fields:
volumer, series, address, edition, month, note, key.
incollection: A part of a book with its own title. Required fields: 
       author, title, booktitle, publisher, year. Optional
       fields: editor, pages, organization, publisher, address,
month, note, key.
<a name="inproceedings"></a>inproceedings: An article in a conference proceedings. Required 
       fields: author, title, booktitle, year. Optional fields:
       editor, pages, organization, publisher, address, month,
note, key.
manual:  Technical documentation. Required fields: title. 
       Optional fields: author, organization, address, edition,
month, year, note.
mastersthesis: A Master's thesis. Required fields: author, title, school, year. Optional fields: address, month, note, key.
misc: Use this type when nothing else fits. Required 
       fields: none. Optional fields: author, title,
howpublished, month, year, note, key.
patent: A patent.
phdthesis: A Ph.D. thesis. Required fields: author, title, school, year. Optional fields: address, month, note, key.
<a name="proceedings"></a>proceedings: The proceedings of a conference. Required fields: 
       title, year. Optional fields: editor, publisher,
organization, address, month, note, key.
techreport: A report published by a school or other institution, 
       usually numbered within a series. Required fields:
       author, title, institution, year. Optional fields: type,
number, address, month, note, key.
unpublished: A document with an author and title, but not formally 
       published. Required fields: author, title, note. Optional
fields: month, year, key.

Examples

@book{kn:gnus,

AUTHOR = "Donald E. Knudson",
TITLE = "1966 World Gnus Almanac",
PUBLISHER = {Permafrost Press},
ADDRESS = {Novosibirsk} }

<div class="book" id="kn:gnus">
  <div class="author">Donald E. Knudson</div>
  <div class="title">1966 World Gnus Almanac</div>
  <div class="publisher">Permafrost Press</div>
  <div class="address">Novosibirsk</div>
</div>


@article{XAi_HSCheng_1994a,

author = "X. Ai and H. S. Cheng",
title = "Influence of moving dent on point {EHL} contacts",
journal = "Tribol. Trans.",
volume = "37",
year = "1994",
pages = "323--335",
}

<div class="article" id="XAi_HSCheng_1994a">
  <div class="author">X. Ai and H. S. Cheng</div>
  <div class="title">Influence of moving dent on point {EHL} contacts</div>
  <div class="journal">Tribol. Trans.</div>
  <div class="volume">37</div>
  <div class="year">1994</div>
  <div class="pages">323--335</div>
</div>

OpenURL

OpenURL aka Z39.88 defines a standard way of bundling citation data in a URL. It is widely deployed in academic libraries around the world to provide access to licensed content via link resolvers such as SFX. The Context Object in Span (COinS) community standard represents one way to embed OpenURLs in XHTML without including a resolver target. 


<span class="Z3988" title="ctx_ver=Z39.88-2004&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.issn=1045-4438"></span>

As you can see this isn't very much like semantic XHTML at all. However significant work has gone into defining the set of Key/Encoded Values (KEVs) that can be used in various types of citations: book, dissertation, journal, patent. It would be possible to simply provide a standard XHTML bundling for these keys as a microformat.

Example



<div class="openurl-journal">
   <span class="aulast">Berners-Lee</span>, 
   <span class="aufirst">Tim</a>; Hendler, James; Lassila, Ora.
   "<span class="atitle">The Semantic Web</span>". 
   <span class="jtitle">Scientific American</span>
   <span class="volume">284(<span class="issue">5</a>), pp.
   pp. <span class="pages">34-43</a>. 
   <span class="issn">0036-8733</span>
</div>


Using OpenURL in this way would enable third party applications that could, say grab citation metadata from a blog, and without much work fire it off at your university's or public libraries openurl resolver to see if the article is available via a licensed databases. The benefits have been noted elsewhere.


Z39.80

I'm not sure the best place for a guide to Z39.80 so please add links as you see fit:

http://www.niso.org/standards/resources/drft4rev.html

Retrieved from "http://microformats.org/wiki/index.php?title=citation-formats&oldid=2569"