Microformats Wiki - User contributions [en]

citation-formats

2007-07-26T12:37:01Z

JakobVoss: /* SRU from the Library of Congress */ there is more at LOC

= Citation Formats =

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

See also:
* [[citation]]
* [[citation-brainstorming]]
* [[citation-examples]]
* [[citation-faq]]

== 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 microformat, then it's 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 extension 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 DEFINITIVE, any errors should be corrected. More formats will be added to the list as they are mapped.

<table border="1">
<tr>
<th>Dublin Core</th>
<th>MODS</th>
<th>bibTeX</th>
<th>Z39.80</th>
</tr>
<tr>
<td>Title (alternative)</td>
<td>titleInfo/title titleInfo/PartNum</td>
<td>booktitle title chapter number pages volume series</td>
<td>Analytic Title 
Collective or Series Title 
Monographic Title 
Work Fraction Title 
Location of Conference 
Main Entry 
Name of Conference 
Number of Meeting 
Other Title 
Parallel Title 
Title Abbriviation 
Title of Conference Proceedings 
Translated Title 
Uniform Title 
Abbriviated Translated Title 
Symposium or Session Title 
Collective or Series Edition 
Video/Film Edition 
</td>
</tr>
<tr>
<td>creator</td>
<td>name/namePart</td>
<td>author creator</td>
<td>Author, Primary 
Corporate Author, Primary 
Abstract Author 
Authorship Statement 
Acknowledged Supporters 
Assignee for Patents 
Chairperson of Conference 
Director of AV Program 
Other Author 
Reviewed Book Author 
Studio 
Sponsor of Conference 
Staff/Cast 
Symposium Chairperson 
Author Address or Affiliation 
Author Country 
Electronic Address of Author 
</td>
</tr>
<tr>
<td>subject</td>
<td>subject/topic</td>
<td>keywords</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Description (abstract | tableOfContents)</td>
<td>abstract note tableOfContents</td>
<td>abstract annotation note contents</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Contributor</td>
<td>name</td>
<td>editor?</td>
<td>Book/Report/Volume Editor 
Producer 
Translator 
</td>
</tr>
<tr>
<td>Date (available | created | dateAccepted | dateCopyrighted | dateSubmitted | issued | modified | valid)</td>
<td>originInfo/dateIssued originInfo/dateCreated originInfo/dateCaptured originInfo/dateOther</td>
<td>month year</td>
<td>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</td>
</tr>
<tr>
<td>Type</td>
<td>typeOfResource genre</td>
<td>@class type</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Format (extent | medium)</td>
<td>physicalDescription/internetMediaType physicalDescription/extent physicalDescription/form</td>
<td>howpublished</td>
<td>needs mapping</td>
</tr>
<tr>
<td>identifier (bibliographicCitation)</td>
<td>identifier</td>
<td>ISBN ISSN LCCN URL</td>
<td>ISBN Identifier Report Identfier ISSN</td>
</tr>
<tr>
<td>Source</td>
<td>relatedItem</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td>language</td>
<td>language</td>
<td>language</td>
<td bgcolor="#cccccc"></td>
</tr>
<tr>
<td>Relation (...)</td>
<td>relatedItem/...</td>
<td>crossRef</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Coverage (spacial | temporal)</td>
<td>subject/temporal subject/geographic subject/hierarchicalGeographic subject/cartographics</td>
<td></td>
<td>needs mapping</td>
</tr>
<tr>
<td bgcolor="#cccccc"></td>
<td>classifications</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td>Rights (accessRights | license)</td>
<td>accessConditions</td>
<td>copyright</td>
<td>needs mapping</td>
</tr>
<tr>
<td>publisher</td>
<td bgcolor="#cccccc"></td>
<td>publisher</td>
<td>Publisher Name 
Place of Publication 
Country of Publication 
Generic Address 
</td>
</tr>
<tr>
<td>audience (educationLevel | mediator)</td>
<td>targetAudience</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td bgcolor="#999999">accualMethod accualPeriodicaty accualPolicy instrcutionalMethod provenance rightsHolder</td>
<td bgcolor="#999999">location extension recordInfo</td>
<td bgcolor="#999999">address afflilication location edition institution journal key mrnumber organization price school size</td>
<td bgcolor="#999999">(the following need to be mapped to the above rows or left here as other) 
Database Source 
Databse Record Identifier 
Database Producer Name 
Rights Management 
Subfile 
Other Source Identifier 
Vendor Record Identifier 
Database Vendor Name 
Column Number 
Edition 
Frequency of Publication 
Internet Location for Document 
Supplement/Part/Special number identifer 
Issue Identifier 
Location in Work 
Number of the Chapter 
Number in Series 
Volume Identifier 
Section Indentifier 
</td>
</tr>
</table>

== Dublin Core Metadata ==
[http://dublincore.org/ Dublin Core] metadata uses a small vocabulary to describe the data.
* contributor
* coverage
* creator
* date
* description
* format
* identifier
* language
* publisher
* relation
* rights
* source
* subject
* title
* type

From those there are specialised types which are just refinements of the previous, for example:

* abstract refines description.
* accessRights refines rights

[http://dublincore.org/documents/dc-citation-guidelines/ Guidelines for Encoding Bibliographic Citation Information in Dublin Core Metadata]

== MODS (Metadata Object Description Schema) ==
This is a format developed for the Library of Congress for a bibliographic element set that may be used for a variety of purposes, and particularly for library applications.

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

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

== NLM Journal Publishing DTD ==

[http://dtd.nlm.nih.gov/publishing/tag-library/2.1/n-fv30.html http://dtd.nlm.nih.gov/publishing/tag-library/2.1/n-fv30.html]

The [http://dtd.nlm.nih.gov/publishing/tag-library/ NLM Journal Publishing DTD] defines the schema used for publishing journal articles as XML. The <pre><citation></pre> element can be placed with paragraphs or within a <pre><ref-list></pre> element at the end of the article.

"Although the DTD does not enforce it, a citation to a journal article should be tagged with as many as possible of the following, so that PubMed Central, CrossRef, or other matching service can make the citation into a live link:

<table border="1">
<tr><td>source</td><td>The title of a journal, book, conference proceedings, etc. that is the source of the cited material. (Note: In PubMed Central processing, this is typically the MEDLINE abbreviation of the journal name.)</td></tr>
<tr><td>article-title</td><td>Title of the article</td></tr>
<tr><td>volume</td><td>Volume of the journal</td></tr>
<tr><td>issue</td><td>Issue of the journal</td></tr>
<tr><td>fpage</td><td>Page number on which the article starts</td></tr>
<tr><td>name</td><td>Name of an author or editor</td></tr>
<tr><td>year</td><td>Year of publication</td></tr>
<tr><td>month</td><td>Month of publication (if present)</td></tr>
<tr><td>day</td><td>Date of publication (if present)</td></tr>
</table>

The other elements (described [http://dtd.nlm.nih.gov/publishing/tag-library/2.1/n-fv30.html here]) may be tagged if desired. Use the <source> element for titles of books, conference proceedings, etc."

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

* author
* publication date
* publisher
* pages
* title (article/book)
* url

== BibTeX ==
=== Fields Used by Bibtex ===

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

=== BibTeX citation Types ===
A reference can be to any of a variety of types. Following is a list of types. Each one also explains the fields associated with that type. Any fields not listed as required or optional are considered to be ignored.
<table border="1" width="100%">
<tr>
<td>article:</td>
<td>An article from a journal or magazine. Required fields: author, title, journal, year. Optional fields: volume, number, pages, month, note, key.</td>
</tr>
<tr>
<td>book:</td>
<td>A book with an explicit publisher. Required fields: author or editor, title, publisher, year. Optional fields: volume, series, address, edition, month, note, key.</td>
</tr>
<tr>
<td>booklet: </td>
<td>A work that is printed and bound, but without a named publisher or sponsoring institution. Required fields: title. Optional fields: author, howpublished, address, month, year, note, key.</td>
</tr>
<tr>
<td>collection:</td>
<td>A collection of works. Same as Proceedings.</td>
</tr>
<tr>
<td>conference:</td>
<td>The same as Inproceedings.</td>
</tr>
<tr>
<td>inbook:</td>
<td>A part of a book, which may be a chapter and/or arange of pages. Required fields: author or editor, title, chapter and/or pages, publisher, year. Optional fields: volumer, series, address, edition, month, note, key.</td>
</tr>
<tr>
<td>incollection:</td>
<td>A part of a book with its own title. Required fields: author, title, booktitle, publisher, year. Optional fields: editor, pages, organization, publisher, address, month, note, key.</td>
</tr>
<tr>
<td>inproceedings:</td>
<td>An article in a conference proceedings. Required fields: author, title, booktitle, year. Optional fields: editor, pages, organization, publisher, address, month, note, key.</td>
</tr>
<tr>
<td>manual: </td>
<td>Technical documentation. Required fields: title. Optional fields: author, organization, address, edition, month, year, note.</td>
</tr>
<tr>
<td>mastersthesis:</td>
<td>A Master's thesis. Required fields: author, title, school, year. Optional fields: address, month, note, key.</td>
</tr>
<tr>
<td>misc:</td>
<td>Use this type when nothing else fits. Required fields: none. Optional fields: author, title, howpublished, month, year, note, key.</td>
</tr>
<tr>
<td>patent:</td>
<td>A patent.</td>
</tr>
<tr>
<td>phdthesis:</td>
<td>A Ph.D. thesis. Required fields: author, title, school, year. Optional fields: address, month, note, key.</td>
</tr>
<tr>
<td>proceedings:</td>
<td>The proceedings of a conference. Required fields: title, year. Optional fields: editor, publisher, organization, address, month, note, key.</td>
</tr>
<tr>
<td>techreport:</td>
<td>A report published by a school or other institution, usually numbered within a series. Required fields: author, title, institution, year. Optional fields: type, number, address, month, note, key.</td>
</tr>
<tr>
<td>unpublished:</td>
<td>A document with an author and title, but not formally published. Required fields: author, title, note. Optional fields: month, year, key.</td>
</tr>
</table>

==== Examples ====
<pre><nowiki>
@book{kn:gnus,

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

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

@article{XAi_HSCheng_1994a,

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

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

===Bib-enabled Applications===

Reference-management applications that support the bib format. This is an incomplete list.

====Desktop Applications====
* [http://www.endnote.com EndNote] (Large market share) (but not really BiBTeX oriented, importation macros are old and you must first use Jabref and export to Endnote formats)
* [http://bibdesk.sourceforge.net/ BibDesk]
* [http://www.mackichan.com/index.html?bibdb/default.htm~mainFrame BibDB]
* [http://sourceforge.net/projects/bib-it/ Bib-it]
* [http://jabref.sourceforge.net Jabref] Probably the most useful application because of its facility to search Pubmed (and also to export in many other formats).
* Large list of other apps at [http://dmoz.org/Computers/Software/Typesetting/TeX/BibTeX/ dmoz] and [http://en.wikipedia.org/wiki/BibTeX#Software Wikipedia]

====Web Applications====
* [http://www.refworks.com RefWorks] (Large market share)
* [http://www.citeulike.org/ CiteULike]
* [http://citeseer.ist.psu.edu/ CiteSeer]
* [http://www.bibsonomy.org/ BibSonomy]
* [http://www.connotea.org Connotea]
* [http://www.2ndminute.org:8080/amatex Amatex - converts Amazon to Bib format]
* Many others can be found at [http://en.wikipedia.org/wiki/BibTeX#External_links Wikipedia]

====Academic Databases====
* [http://academic.live.com/ Windows Live Academic Search]
* [http://portal.acm.org/dl.cfm?dl=ACM ACM Digital Library]
* [http://www.ncbi.nlm.nih.gov/books/bv.fcgi PubMed] via TexMed

== RIS ==

RIS is similar to BibTeX and is handled by most desktop and web-based bibliography management software.

The specification and field types/tags are described at [http://www.refman.com/support/risformat_intro.asp http://www.refman.com/support/risformat_intro.asp]

In particular, see [http://www.refman.com/support/risformat_reftypes.asp the list of different reference types].

A sample item in RIS format:
<pre>
TY - JOUR
A1 - Baldwin,S.A.
A1 - Fugaccia,I.
A1 - Brown,D.R.
A1 - Brown,L.V.
A1 - Scheff,S.W.
T1 - Blood-brain barrier breach following
cortical contusion in the rat
JO - J.Neurosurg.
Y1 - 1996
VL - 85
SP - 476
EP - 481
RP - Not In File
KW - cortical contusion
KW - blood-brain barrier
KW - horseradish peroxidase
KW - head trauma
KW - hippocampus
KW - rat
ER -
</pre>

[http://www-static.cc.gatech.edu/classes/RWL/Projects/citation/Applet/OnlineHelp/refer_doc.html Refer] is a similar, smaller bibliographic format.

* author
* title
* type
* Identifier
* notes/abstract
* reprint status
* keyword
* volume
* issue
* pages
* year
* periodical name (where published)
* publisher
** publisher city
** publisher address
* related links
* link to PDF
* availablity

== OpenURL ==

OpenURL aka [http://www.niso.org/standards/standard_detail.cfm?std_id=783 Z39.88] defines a standard way of bundling citation data in a URL. It is widely deployed in academic libraries around the world to provide access to licensed content via link resolvers such as [http://www.exlibrisgroup.com/sfx_openurl.htm SFX]. The Context Object in Span ([http://ocoins.info/ COinS]) community standard represents one way to embed OpenURLs in XHTML without including a resolver target. OpenURL also provides an XML encoding.

Example (from a book review written using the Structured Blogging plugin):

<pre><nowiki>
ISBN: 
0679426612
</nowiki></pre>

Another example, a journal this time:
<pre>
<nowiki>

</nowiki>
</pre>

As you can see this isn't very much like semantic XHTML at all. However significant work has gone into defining the set of Key/Encoded Values (KEVs) that can be used in various [http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=ListRecords&metadataPrefix=oai_dc&set=Core:Metadata+Formats types] of citations: [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:book book], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:dissertation dissertation], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:journal journal], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:patent patent]. It would be possible to simply provide a standard XHTML bundling for these keys as a microformat.

=== Example ===

<pre>
<nowiki>

<div class="openurl-journal">
Berners-Lee,
Tim</a>; Hendler, James; Lassila, Ora.
"The Semantic Web".
Scientific American
284(5), pp.
pp. 34-43.
0036-8733
</div>

</nowiki>
</pre>

Using OpenURL in this way would enable third party applications that could, say grab citation metadata from a blog, and without much work fire it off at your university's or public libraries openurl resolver to see if the article is available via a licensed databases. The benefits [http://www.infotoday.com/newsbreaks/nb050801-1.shtml have] [http://www.ariadne.ac.uk/issue43/chudnov/ been] [http://www.wallandbinkley.com/quaedam/?p=30 noted] [http://hublog.hubmed.org/archives/001163.html elsewhere].

== The OpenURL Briefly Explained ==

An OpenURL consists of two independent parts: the ContextObject (or the bibliographic metadata surrounding a citation) and the location of resolver to parse the metadata and present contextual services based on said metadata. The problem is that the term "OpenURL" is also used as a catch-all for all of the independent parts and how they work. This is mainly because it's a catchier term than "Z39.88", which is the [http://www.niso.org/standards/standard_detail.cfm?std_id=783 NISO standard all this is based upon].

The most common representation of the OpenURL ContextObject is seen as arguments in a URL string (which is referred to as "San Antonio Profile 1" -- more commonly SAP1 -- and is represented in Key Encoded Values -- KEVs). This "representation" is independent of the ContextObject (from here on known as CO) itself and is only intended to permit the CO to be transmitted via an HTTP GET request.

There is also SAP2, which is an XML representation of the CO (see: [http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadataPrefix=oai_dc&identifier=info:ofi/fmt:xml:xsd:ctx here] for more information) and is a much more human readable format. This still falls outside the scope of microformats, but makes the point that encoding has nothing to do with the CO itself. They are just agreed upon means of conveying the CO to enable machines act upon them consistently.

The ContextObject could be conveyed just as easily in XHTML using attributes, as long as the terms follow the vocabulary defined in the OpenURL framework. The important thing to focus on here is the ContextObject -- the address of the link resolver ''is'' institution-specific and should be handled by a user's (or machine's) activating agent.

However, the link resolver is still a very important component to this whole process. Getting users "appropriate copy" is a very real (and very difficult) problem that libraries are trying to solve. Link resolvers are a pretty efficient means of overcoming this hurdle, so it would make sense to mark up bibiographic citations in a way that link resolvers can easily parse.

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

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

== DocBook ==

A subset of the DocBook vocabulary is dedicated to representing a bibliography: http://www.docbook.org/tdg/en/html/bibliography.html

<pre><nowiki>
<!DOCTYPE bibliography PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
<bibliography>
<title>Languages and Semantics</title>
<bibliodiv>
<title>Books</title>
<biblioentry>
<title>Course in General Linguistics</title>
<abbrev>deSaussure59</abbrev>
<author><firstname>Ferdinand</firstname><surname>de Saussure</surname></author>
<editor><firstname>Charles</firstname><surname>Bally</surname></editor>
<editor><firstname>Albert</firstname><surname>Sechehaye</surname></editor>
<othercredit role="translator"><firstname>Wade</firstname><surname>Baskin</surname></othercredit>
<copyright>
<year>1959</year>
<holder>The Philosophical Library Inc.</holder>
</copyright>
<isbn>07-016524-6</isbn>
<publisher>
<publishername>McGraw-Hill Book Company</publishername>
</publisher>
</biblioentry>
</bibliodiv>
</bibliography>
</nowiki></pre>

* publisher
* copyright
* identifier (ISBN)
* title
* author/editor/other credit/
* type (book)

== Ann Arbor District Library XML feed ==

Here's a record in XML format from their project to simplify
access to the catalog. More discussion on [http://www.blyberg.net John Blyberg's blog].

<pre>
<nowiki>
<p:Record>
<callnum>823 Bu</callnum>
<author>Burkart, Gina, 1971-</author>
<fulltitle>A parent's guide to Harry Potter / Gina Burkart</fulltitle>
<title>A parent's guide to Harry Potter </title>
<pubinfo>Downers Grove, Ill. : InterVarsity Press, c2005</pubinfo>
<desc>112 p</desc>
<bibliography>Includes bibliographical references</bibliography>
<contents>
The Harry hype -- More than a story -- The modern fairy tale -- Discussing fantasy with children --
Morals, not magic -- The real issues in Harry Potter -- Dealing with traumatic experiences -- Facing
fears -- Battling bullies -- Delving into diversity -- Hiding hurts -- Letting go of anger -- Getting
help -- Choosing good over evil -- The power of love -- Facing spiritual battles
</contents>
<isbn>0830832882</isbn>
<price>$11.00</price>
<lang>eng</lang>
<copies>0</copies>
<catdate>08-16-2005</catdate>
<mattype>a</mattype>
<avail>No copies available</avail>
<recordlink xlink:href="http://www.aadl.org/cat/seek/record=1249810"/>
</p:Record>
</nowiki>
</pre>

* url
* availablity
* identifier (ISBN/call number)
* author
* title
* publisher
* pages
* description/contents

== SimpleDC supported by the zoom toolkit ==

<pre>
<nowiki>
<dc xmlns="http/www.loc.gov/zing/srw/dcschema/v1.0/">
<title>Kantor Salomon Sulzer und seine Zeit : eine Dokumentation /</title>
<creator>Avenary, Hanoch.</creator>
<creator>Pass, Walter.</creator>
<creator>Vielmetti, Nikolaus.</creator>
<creator>Adler, Israel, (1925-)</creator>
<subject>Sulzer, Salomon, -- 1804-1890.</subject>
<subject>Jewish composers -- Austria -- Biography.</subject>
<subject>Cantors, Jewish -- Biography.</subject>
<date>1985</date>
<publisher>Sigmaringen : Jan Thorbecke Verlag</publisher>
<identifier>3799540636</identifier>
<description>300 p., [12] p. of plates : ill., music, ports. ; 24 cm.</description>
</dc>
</nowiki>
</pre>

this is the output of marc.toSimpleDC()

* title
* creator (author)
* subjects
* date
* publisher
* identifier
* description

(NOTE: this schema is from the example, not the source schema)

== SRU from the Library of Congress ==

http://z3950.loc.gov:7090/voyager?version=1.1&operation=searchRetrieve&query=dinosaur&maximumRecords=1&recordSchema=dc

<pre>
<nowiki>
<?xml version="1.0"?>
<zs:searchRetrieveResponse xmlns:zs="http://www.loc.gov/zing/srw/">
<zs:version>1.1</zs:version>
<zs:numberOfRecords>1701</zs:numberOfRecords>
<zs:records>
<zs:record>
<zs:recordSchema>info:srw/schema/1/dc-v1.1</zs:recordSchema>
<zs:recordPacking>xml</zs:recordPacking>
<zs:recordData>
<srw_dc:dc xmlns:srw_dc="info:srw/schema/1/dc-schema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://purl.org/dc/elements/1.1/"
xsi:schemaLocation="info:srw/schema/1/dc-schema http://www.loc.gov/z3950/agency/zing/srw/dc-schema.xsd">
<title>3-D dinosaur adventure [computer file].</title>
<creator>Knowledge Adventure, Inc.</creator>
<type>software, multimedia</type>
<publisher>Glendale, CA : Knowledge Adventure,</publisher>

<date>c1995.</date>
<language>eng</language>
<description>Employs a dinosaur theme-park setting to introduce users to Triassic, Jurassic, and
Cretaceous periods. Features hypertext dinosaur encyclopedia covering 150 million years of
paleontology. Includes animated video simulations, three-dimensional dinosaur museum, narration,
games, activities, and color illustrations.</description>
<description>Ages 5 to 10.</description>
<description>System requirements for PC: 486SX/25MHz processor or higher; 8MB RAM; Windows 3.1,
3.11, or 95; SVGA 256-color graphics adapter; hard drive with 5MB free space; double-speed CD-ROM
drive; MPC-compatible sound card; mouse.</description>
<description>System requirements for Macintosh: 68040 or Power PC processor; 8MB RAM; System 7.0 or
higher; 256-color graphics capability; thirteen-inch color monitor or larger; hard drive with 4MB
free space; double-speed CD-ROM drive.</description>

<description>Ages 5 to 10.</description>
<description>Employs a dinosaur theme-park setting to introduce users to Triassic, Jurassic, and
Cretaceous periods. Features hypertext dinosaur encyclopedia covering 150 million years of paleontology.
Includes animated video simulations, three-dimensional dinosaur museum, narration, games, activities,
and color illustrations.</description>
<subject>Dinosaurs--Juvenile software.</subject>
<subject>Dinosaurs.</subject>
<identifier>URN:ISBN:1569972133</identifier>
</srw_dc:dc>
</zs:recordData>
<zs:recordPosition>1</zs:recordPosition>
</zs:record>
</zs:records>
</zs:searchRetrieveResponse>

</nowiki>
</pre>

NOTE: this is just Dublin Core data in a special LOC envelope

:LOC also delivers [http://www.loc.gov/standards/marcxml/ MARCXML], and [http://www.loc.gov/standards/mods/ MODS], see http://z3950.loc.gov:7090/voyager?version=1.1&operation=explain -- [[User:JakobVoss|JakobVoss]] 05:37, 26 Jul 2007 (PDT)

== University of Bath reference type ==
<pre>
<nowiki>
<reference>
<authors>
<author>
<forename>E</forename>
<forename>M</forename>
<surname>Phillips</surname>
</author>
<author>
<forename>D</forename>
<forename>S</forename>
<surname>Pugh</surname>
</author>
</authors>
<date>1994</date>
<entity>
<book title="How to get a PhD: A handbook for students and their supervisors">
<location>
<placeofpublication>Buckinghamshire</placeofpublication>
<publisher>Open University</publisher>
</location>
</book>
</entity>
</reference>

<reference>
<authors>
<author>
<forename>Michael</forename>
<surname>Fumento</surname>
</author>
</authors>
<date>1996</date>
<entity>
<website pagetitle="Radon's Real Threat is to the EPA"
uri="http://www.consumeralert.org/fumento/radon1.htm"/>
</entity>
<frdescription>an article by a prolific newspaper columnist in the USA -
quotes empirical scientific research showing no provable link between radon in homes and elevated
cases of lung cancer</frdescription>
</reference>
</nowiki>
</pre>
[http://www.bath.ac.uk/schemas/screenshots/referencetype.png Schema extract]

* author
* date
* url
* description
* type (book/journal/conference)
* title
* artile
* volume
* issue
* chapter
* pages
* publisher
** publisher data (address, city, ...)

== Implied Schema ==
This is the start of the short list of common properties across documented formats. Once this is finished, there will be a union of Implied schemas between EXAMPLES and IMPLEMENTATIONS and we will see what that looks like. (This currently only covers a few of the formats listed, some documented formats still need to be explored)

* creator (author, editor, translator, contributor) - this can be handled with hCard, but will need an additional property to refine what "creator" means
* publisher (this can also be handled with hCard)
* subject/topics/keywords/categories/genre (there is a rel="tag" microformat)
* Description (abstract, note, tableOfContents)
* typeOfResource/format

common location information
* volume
* issue
* page
* edition

Date Fields
* Date Published (some formats have YEAR/MONTH sperately)
* Date Accessed (see [http://www.apastyle.org/elecsource.html here] for discussion from APA style guide.)

Again, I'll emphasize: "date published" is problematic. If one needs specificity, then better to have the following list of date classes: date (the generic), issued (braoder than published), copyright (often not the same as issuance date), accessed. -- bruce

Other fields
* Copyright/usage
* audience

* identifier (ISBN, ISSN, id, internal only, other)
* language (this can be handled by the xml:lang attribute native to HTML)

== Types and Roles ==
(Section is informative only as a place to capture various parts of publication citations.)

There are many different types of publications and this information should be captured in the citation. Possible types include:
* Novel/fiction (specify type -- literature, SF, romance, etc.?)
* Non-fiction
* Poem
* Play
* Magazine
* Reference (separate out encyclopedia, dictionary, almanac, etc.?)
* Journal
* Article within a journal
* Chapter within a book
* Dissertation
* Web Site
* Page within a web site
* Music Recording
* Video Recording
* Interview
* Physical object (Statue, Painting, etc.)
* ??

Question:
Certain works have specific types of citations, for example, the Bible--and, I assume, other religious works--have very specific citation formats with different relevant information (chapter/verse) than others, as do the works of Shakespeare. Should these be considered separate types/roles?

A: I think in terms of types, we should at least note the items (chapter, verse, etc). How they get dealt with is still way up in the air. - [[User:Tim White|Tim White]]

Likewise, there are several different roles associated with publications -- author, co-author, editor, translator, etc. Should these be captured under a master "role" or treated as individual elements?

A: Good question. I think there is an important distinction, but whether we follow a design pattern of "role-*" (or more likely "author-*) or some other pattern hasn't been discussed yet. - Tim

== Biblio RDF Class Schema ==
Regading the issue of types notes above, the [http://vocab.org/biblio/schema biblio schema] provides a comprehensive set of classes to describe citation metadata. It might prove useful as a guide for a micro-format. The primary classes are Agent, Reference, Collection, and Event. An "Article", then, would be a subclass of "Part", which in turn is a subclass of Reference. Likewise, a "Journal" is a subclass of a "Periodical," which in turn is a subclass of "Collection." An article would typically be linked to a journal through a dcterms:isPartOf relation.

== ISBN Uniform Resource Names ==

[http://www.faqs.org/rfcs/rfc3187.html RFC3187] defines an ISBN namespace for Uniform Resource Names (URNs).

Example:

URN:ISBN:0-395-36341-1

I'm not sure if any browser uses this data, but it might have an application in citations describing registered materials with an ISBN.

There is also a URN namespace for ISSN (International Standard Serial Number), which identifies serials/periodicals e.g. [http://alistapart.com A List Apart]. It is defined in [http://www.faqs.org/rfcs/rfc3044.html RFC3044]. Additional URN namespaces are listed at http://www.iana.org/assignments/urn-namespaces.

== You should know ==
* There are more then 1.300 citation ''styles'' in EndNote 9.
* Libraries have developed formats and rules for publications since more than 100 years. There are millions of records in library catalougues. You should '''at least''' be familiar with AACR and FRBR. There '''already are''' effords to create a new "microformat" called ''Resource Description and Access'' (RDA) [http://www.collectionscanada.ca/jsc/rdaprospectus.html]. Why don't you try to work with the professionals instead of amateurishly trying to reinvent the wheel and create yet another incompatible format? -- [[User:JakobVoss|JakobVoss]] 01:39, 5 Jun 2006 (PDT)
** I agree that the people involved in developing this microformat (including me) ought to be aware of these efforts (in particular FRBR), but I also think your argument is hopelessly naive and pretentious. The professionals you refer to are in fact library professionals, with their own bizarre traditios and unique information needs. Those are different than the professional scholars for whom citations are critical (me), or to the professional web developers who might want to implement these formats. What I do think is important is for us to understand the different design traditions, and their trade-offs, rather than to blindly create a microformat based on one of them -- Bruce (author of citeproc [http://xbiblio.sourceforge.net/citeproc] and csl [http://xbiblio.sourceforge.net/csl]).

Nice to meet you, Bruce! Maybe I'm naive but it still think that there is a way to combine the best of both worlds: scholars and library professionals. Both have developed bizarre traditions and it would be a pitty to create a new bizarre microformat that is not based on both of them. Thanks to your links to xbiblio. I a stumbled upon it a while ago but have to look at it deeper. -- [[User:JakobVoss|JakobVoss]] 11:48, 19 Jul 2006 (PDT)

=== ISBD ===

Oh, already a year ago! I was just trying to explain Microformats and its relevance for libraries ([http://jakoblog.de/2007/07/26/von-isbd-zum-web-20-mit-mikroformaten/ here (in German)]. You should have a look at the [http://en.wikipedia.org/wiki/International_Standard_Bibliographic_Description International Standard Bibliographic Description] (ISBD). These rules specify how a bibliographic should be displayed in a library catalouge. This format could be used as basis for hCitation because millions of records are availble in ISBD or variants in library catalouges all over the world.

Here is an example:

<pre>
Title: Harry Potter and the deathly hallows / Joanne K. Rowling. - [Children’s ed.], 1. ed. - London : Bloomsbury, 2007
ISBN: 0-7475-9105-9 - 978-0-7475-9105-4 (Children’s edition)
</pre>

This could be broken into "semantic peaces":

<pre>
<div class='hCitation'>
Titel:
Harry Potter and the deathly hallows /

Joanne K.
Rowling
</div>. -
[Children's ed.], 1. ed. -
London : Bloomsbury,
2007
</div>
<div>
ISBN:
0-7475-9105-9 -
978-0-7475-9105-4
(Children's edition)
</div>
</pre>

The advantage of ISBD is that it is very elaborated and covers many field and types of publications and special cases. Of course you need to simplifiy parts of it for the microformat. I'd prefer a bottom up design with the current mass of real-world records in todays libraries instead of top-down by thinking of an "ideal record" or limited playing databases. -- [[User:JakobVoss|JakobVoss]] 05:34, 26 Jul 2007 (PDT)

== OpenDocument ==
The OpenDocument Format also includes parts for citation and bibliography. See also the [http://bibliographic.openoffice.org/ OpenOffice Bibliographic project]. -- [[User:JakobVoss|JakobVoss]] 11:55, 19 Jul 2006 (PDT)

citation-formats

2007-07-26T12:34:38Z

JakobVoss: /* You should know */

= Citation Formats =

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

See also:
* [[citation]]
* [[citation-brainstorming]]
* [[citation-examples]]
* [[citation-faq]]

== 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 microformat, then it's 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 extension 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 DEFINITIVE, any errors should be corrected. More formats will be added to the list as they are mapped.

<table border="1">
<tr>
<th>Dublin Core</th>
<th>MODS</th>
<th>bibTeX</th>
<th>Z39.80</th>
</tr>
<tr>
<td>Title (alternative)</td>
<td>titleInfo/title titleInfo/PartNum</td>
<td>booktitle title chapter number pages volume series</td>
<td>Analytic Title 
Collective or Series Title 
Monographic Title 
Work Fraction Title 
Location of Conference 
Main Entry 
Name of Conference 
Number of Meeting 
Other Title 
Parallel Title 
Title Abbriviation 
Title of Conference Proceedings 
Translated Title 
Uniform Title 
Abbriviated Translated Title 
Symposium or Session Title 
Collective or Series Edition 
Video/Film Edition 
</td>
</tr>
<tr>
<td>creator</td>
<td>name/namePart</td>
<td>author creator</td>
<td>Author, Primary 
Corporate Author, Primary 
Abstract Author 
Authorship Statement 
Acknowledged Supporters 
Assignee for Patents 
Chairperson of Conference 
Director of AV Program 
Other Author 
Reviewed Book Author 
Studio 
Sponsor of Conference 
Staff/Cast 
Symposium Chairperson 
Author Address or Affiliation 
Author Country 
Electronic Address of Author 
</td>
</tr>
<tr>
<td>subject</td>
<td>subject/topic</td>
<td>keywords</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Description (abstract | tableOfContents)</td>
<td>abstract note tableOfContents</td>
<td>abstract annotation note contents</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Contributor</td>
<td>name</td>
<td>editor?</td>
<td>Book/Report/Volume Editor 
Producer 
Translator 
</td>
</tr>
<tr>
<td>Date (available | created | dateAccepted | dateCopyrighted | dateSubmitted | issued | modified | valid)</td>
<td>originInfo/dateIssued originInfo/dateCreated originInfo/dateCaptured originInfo/dateOther</td>
<td>month year</td>
<td>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</td>
</tr>
<tr>
<td>Type</td>
<td>typeOfResource genre</td>
<td>@class type</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Format (extent | medium)</td>
<td>physicalDescription/internetMediaType physicalDescription/extent physicalDescription/form</td>
<td>howpublished</td>
<td>needs mapping</td>
</tr>
<tr>
<td>identifier (bibliographicCitation)</td>
<td>identifier</td>
<td>ISBN ISSN LCCN URL</td>
<td>ISBN Identifier Report Identfier ISSN</td>
</tr>
<tr>
<td>Source</td>
<td>relatedItem</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td>language</td>
<td>language</td>
<td>language</td>
<td bgcolor="#cccccc"></td>
</tr>
<tr>
<td>Relation (...)</td>
<td>relatedItem/...</td>
<td>crossRef</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Coverage (spacial | temporal)</td>
<td>subject/temporal subject/geographic subject/hierarchicalGeographic subject/cartographics</td>
<td></td>
<td>needs mapping</td>
</tr>
<tr>
<td bgcolor="#cccccc"></td>
<td>classifications</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td>Rights (accessRights | license)</td>
<td>accessConditions</td>
<td>copyright</td>
<td>needs mapping</td>
</tr>
<tr>
<td>publisher</td>
<td bgcolor="#cccccc"></td>
<td>publisher</td>
<td>Publisher Name 
Place of Publication 
Country of Publication 
Generic Address 
</td>
</tr>
<tr>
<td>audience (educationLevel | mediator)</td>
<td>targetAudience</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td bgcolor="#999999">accualMethod accualPeriodicaty accualPolicy instrcutionalMethod provenance rightsHolder</td>
<td bgcolor="#999999">location extension recordInfo</td>
<td bgcolor="#999999">address afflilication location edition institution journal key mrnumber organization price school size</td>
<td bgcolor="#999999">(the following need to be mapped to the above rows or left here as other) 
Database Source 
Databse Record Identifier 
Database Producer Name 
Rights Management 
Subfile 
Other Source Identifier 
Vendor Record Identifier 
Database Vendor Name 
Column Number 
Edition 
Frequency of Publication 
Internet Location for Document 
Supplement/Part/Special number identifer 
Issue Identifier 
Location in Work 
Number of the Chapter 
Number in Series 
Volume Identifier 
Section Indentifier 
</td>
</tr>
</table>

== Dublin Core Metadata ==
[http://dublincore.org/ Dublin Core] metadata uses a small vocabulary to describe the data.
* contributor
* coverage
* creator
* date
* description
* format
* identifier
* language
* publisher
* relation
* rights
* source
* subject
* title
* type

From those there are specialised types which are just refinements of the previous, for example:

* abstract refines description.
* accessRights refines rights

[http://dublincore.org/documents/dc-citation-guidelines/ Guidelines for Encoding Bibliographic Citation Information in Dublin Core Metadata]

== MODS (Metadata Object Description Schema) ==
This is a format developed for the Library of Congress for a bibliographic element set that may be used for a variety of purposes, and particularly for library applications.

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

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

== NLM Journal Publishing DTD ==

[http://dtd.nlm.nih.gov/publishing/tag-library/2.1/n-fv30.html http://dtd.nlm.nih.gov/publishing/tag-library/2.1/n-fv30.html]

The [http://dtd.nlm.nih.gov/publishing/tag-library/ NLM Journal Publishing DTD] defines the schema used for publishing journal articles as XML. The <pre><citation></pre> element can be placed with paragraphs or within a <pre><ref-list></pre> element at the end of the article.

"Although the DTD does not enforce it, a citation to a journal article should be tagged with as many as possible of the following, so that PubMed Central, CrossRef, or other matching service can make the citation into a live link:

<table border="1">
<tr><td>source</td><td>The title of a journal, book, conference proceedings, etc. that is the source of the cited material. (Note: In PubMed Central processing, this is typically the MEDLINE abbreviation of the journal name.)</td></tr>
<tr><td>article-title</td><td>Title of the article</td></tr>
<tr><td>volume</td><td>Volume of the journal</td></tr>
<tr><td>issue</td><td>Issue of the journal</td></tr>
<tr><td>fpage</td><td>Page number on which the article starts</td></tr>
<tr><td>name</td><td>Name of an author or editor</td></tr>
<tr><td>year</td><td>Year of publication</td></tr>
<tr><td>month</td><td>Month of publication (if present)</td></tr>
<tr><td>day</td><td>Date of publication (if present)</td></tr>
</table>

The other elements (described [http://dtd.nlm.nih.gov/publishing/tag-library/2.1/n-fv30.html here]) may be tagged if desired. Use the <source> element for titles of books, conference proceedings, etc."

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

* author
* publication date
* publisher
* pages
* title (article/book)
* url

== BibTeX ==
=== Fields Used by Bibtex ===

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

=== BibTeX citation Types ===
A reference can be to any of a variety of types. Following is a list of types. Each one also explains the fields associated with that type. Any fields not listed as required or optional are considered to be ignored.
<table border="1" width="100%">
<tr>
<td>article:</td>
<td>An article from a journal or magazine. Required fields: author, title, journal, year. Optional fields: volume, number, pages, month, note, key.</td>
</tr>
<tr>
<td>book:</td>
<td>A book with an explicit publisher. Required fields: author or editor, title, publisher, year. Optional fields: volume, series, address, edition, month, note, key.</td>
</tr>
<tr>
<td>booklet: </td>
<td>A work that is printed and bound, but without a named publisher or sponsoring institution. Required fields: title. Optional fields: author, howpublished, address, month, year, note, key.</td>
</tr>
<tr>
<td>collection:</td>
<td>A collection of works. Same as Proceedings.</td>
</tr>
<tr>
<td>conference:</td>
<td>The same as Inproceedings.</td>
</tr>
<tr>
<td>inbook:</td>
<td>A part of a book, which may be a chapter and/or arange of pages. Required fields: author or editor, title, chapter and/or pages, publisher, year. Optional fields: volumer, series, address, edition, month, note, key.</td>
</tr>
<tr>
<td>incollection:</td>
<td>A part of a book with its own title. Required fields: author, title, booktitle, publisher, year. Optional fields: editor, pages, organization, publisher, address, month, note, key.</td>
</tr>
<tr>
<td>inproceedings:</td>
<td>An article in a conference proceedings. Required fields: author, title, booktitle, year. Optional fields: editor, pages, organization, publisher, address, month, note, key.</td>
</tr>
<tr>
<td>manual: </td>
<td>Technical documentation. Required fields: title. Optional fields: author, organization, address, edition, month, year, note.</td>
</tr>
<tr>
<td>mastersthesis:</td>
<td>A Master's thesis. Required fields: author, title, school, year. Optional fields: address, month, note, key.</td>
</tr>
<tr>
<td>misc:</td>
<td>Use this type when nothing else fits. Required fields: none. Optional fields: author, title, howpublished, month, year, note, key.</td>
</tr>
<tr>
<td>patent:</td>
<td>A patent.</td>
</tr>
<tr>
<td>phdthesis:</td>
<td>A Ph.D. thesis. Required fields: author, title, school, year. Optional fields: address, month, note, key.</td>
</tr>
<tr>
<td>proceedings:</td>
<td>The proceedings of a conference. Required fields: title, year. Optional fields: editor, publisher, organization, address, month, note, key.</td>
</tr>
<tr>
<td>techreport:</td>
<td>A report published by a school or other institution, usually numbered within a series. Required fields: author, title, institution, year. Optional fields: type, number, address, month, note, key.</td>
</tr>
<tr>
<td>unpublished:</td>
<td>A document with an author and title, but not formally published. Required fields: author, title, note. Optional fields: month, year, key.</td>
</tr>
</table>

==== Examples ====
<pre><nowiki>
@book{kn:gnus,

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

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

@article{XAi_HSCheng_1994a,

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

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

===Bib-enabled Applications===

Reference-management applications that support the bib format. This is an incomplete list.

====Desktop Applications====
* [http://www.endnote.com EndNote] (Large market share) (but not really BiBTeX oriented, importation macros are old and you must first use Jabref and export to Endnote formats)
* [http://bibdesk.sourceforge.net/ BibDesk]
* [http://www.mackichan.com/index.html?bibdb/default.htm~mainFrame BibDB]
* [http://sourceforge.net/projects/bib-it/ Bib-it]
* [http://jabref.sourceforge.net Jabref] Probably the most useful application because of its facility to search Pubmed (and also to export in many other formats).
* Large list of other apps at [http://dmoz.org/Computers/Software/Typesetting/TeX/BibTeX/ dmoz] and [http://en.wikipedia.org/wiki/BibTeX#Software Wikipedia]

====Web Applications====
* [http://www.refworks.com RefWorks] (Large market share)
* [http://www.citeulike.org/ CiteULike]
* [http://citeseer.ist.psu.edu/ CiteSeer]
* [http://www.bibsonomy.org/ BibSonomy]
* [http://www.connotea.org Connotea]
* [http://www.2ndminute.org:8080/amatex Amatex - converts Amazon to Bib format]
* Many others can be found at [http://en.wikipedia.org/wiki/BibTeX#External_links Wikipedia]

====Academic Databases====
* [http://academic.live.com/ Windows Live Academic Search]
* [http://portal.acm.org/dl.cfm?dl=ACM ACM Digital Library]
* [http://www.ncbi.nlm.nih.gov/books/bv.fcgi PubMed] via TexMed

== RIS ==

RIS is similar to BibTeX and is handled by most desktop and web-based bibliography management software.

The specification and field types/tags are described at [http://www.refman.com/support/risformat_intro.asp http://www.refman.com/support/risformat_intro.asp]

In particular, see [http://www.refman.com/support/risformat_reftypes.asp the list of different reference types].

A sample item in RIS format:
<pre>
TY - JOUR
A1 - Baldwin,S.A.
A1 - Fugaccia,I.
A1 - Brown,D.R.
A1 - Brown,L.V.
A1 - Scheff,S.W.
T1 - Blood-brain barrier breach following
cortical contusion in the rat
JO - J.Neurosurg.
Y1 - 1996
VL - 85
SP - 476
EP - 481
RP - Not In File
KW - cortical contusion
KW - blood-brain barrier
KW - horseradish peroxidase
KW - head trauma
KW - hippocampus
KW - rat
ER -
</pre>

[http://www-static.cc.gatech.edu/classes/RWL/Projects/citation/Applet/OnlineHelp/refer_doc.html Refer] is a similar, smaller bibliographic format.

* author
* title
* type
* Identifier
* notes/abstract
* reprint status
* keyword
* volume
* issue
* pages
* year
* periodical name (where published)
* publisher
** publisher city
** publisher address
* related links
* link to PDF
* availablity

== OpenURL ==

OpenURL aka [http://www.niso.org/standards/standard_detail.cfm?std_id=783 Z39.88] defines a standard way of bundling citation data in a URL. It is widely deployed in academic libraries around the world to provide access to licensed content via link resolvers such as [http://www.exlibrisgroup.com/sfx_openurl.htm SFX]. The Context Object in Span ([http://ocoins.info/ COinS]) community standard represents one way to embed OpenURLs in XHTML without including a resolver target. OpenURL also provides an XML encoding.

Example (from a book review written using the Structured Blogging plugin):

<pre><nowiki>
ISBN: 
0679426612
</nowiki></pre>

Another example, a journal this time:
<pre>
<nowiki>

</nowiki>
</pre>

As you can see this isn't very much like semantic XHTML at all. However significant work has gone into defining the set of Key/Encoded Values (KEVs) that can be used in various [http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=ListRecords&metadataPrefix=oai_dc&set=Core:Metadata+Formats types] of citations: [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:book book], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:dissertation dissertation], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:journal journal], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:patent patent]. It would be possible to simply provide a standard XHTML bundling for these keys as a microformat.

=== Example ===

<pre>
<nowiki>

<div class="openurl-journal">
Berners-Lee,
Tim</a>; Hendler, James; Lassila, Ora.
"The Semantic Web".
Scientific American
284(5), pp.
pp. 34-43.
0036-8733
</div>

</nowiki>
</pre>

Using OpenURL in this way would enable third party applications that could, say grab citation metadata from a blog, and without much work fire it off at your university's or public libraries openurl resolver to see if the article is available via a licensed databases. The benefits [http://www.infotoday.com/newsbreaks/nb050801-1.shtml have] [http://www.ariadne.ac.uk/issue43/chudnov/ been] [http://www.wallandbinkley.com/quaedam/?p=30 noted] [http://hublog.hubmed.org/archives/001163.html elsewhere].

== The OpenURL Briefly Explained ==

An OpenURL consists of two independent parts: the ContextObject (or the bibliographic metadata surrounding a citation) and the location of resolver to parse the metadata and present contextual services based on said metadata. The problem is that the term "OpenURL" is also used as a catch-all for all of the independent parts and how they work. This is mainly because it's a catchier term than "Z39.88", which is the [http://www.niso.org/standards/standard_detail.cfm?std_id=783 NISO standard all this is based upon].

The most common representation of the OpenURL ContextObject is seen as arguments in a URL string (which is referred to as "San Antonio Profile 1" -- more commonly SAP1 -- and is represented in Key Encoded Values -- KEVs). This "representation" is independent of the ContextObject (from here on known as CO) itself and is only intended to permit the CO to be transmitted via an HTTP GET request.

There is also SAP2, which is an XML representation of the CO (see: [http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadataPrefix=oai_dc&identifier=info:ofi/fmt:xml:xsd:ctx here] for more information) and is a much more human readable format. This still falls outside the scope of microformats, but makes the point that encoding has nothing to do with the CO itself. They are just agreed upon means of conveying the CO to enable machines act upon them consistently.

The ContextObject could be conveyed just as easily in XHTML using attributes, as long as the terms follow the vocabulary defined in the OpenURL framework. The important thing to focus on here is the ContextObject -- the address of the link resolver ''is'' institution-specific and should be handled by a user's (or machine's) activating agent.

However, the link resolver is still a very important component to this whole process. Getting users "appropriate copy" is a very real (and very difficult) problem that libraries are trying to solve. Link resolvers are a pretty efficient means of overcoming this hurdle, so it would make sense to mark up bibiographic citations in a way that link resolvers can easily parse.

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

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

== DocBook ==

A subset of the DocBook vocabulary is dedicated to representing a bibliography: http://www.docbook.org/tdg/en/html/bibliography.html

<pre><nowiki>
<!DOCTYPE bibliography PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
<bibliography>
<title>Languages and Semantics</title>
<bibliodiv>
<title>Books</title>
<biblioentry>
<title>Course in General Linguistics</title>
<abbrev>deSaussure59</abbrev>
<author><firstname>Ferdinand</firstname><surname>de Saussure</surname></author>
<editor><firstname>Charles</firstname><surname>Bally</surname></editor>
<editor><firstname>Albert</firstname><surname>Sechehaye</surname></editor>
<othercredit role="translator"><firstname>Wade</firstname><surname>Baskin</surname></othercredit>
<copyright>
<year>1959</year>
<holder>The Philosophical Library Inc.</holder>
</copyright>
<isbn>07-016524-6</isbn>
<publisher>
<publishername>McGraw-Hill Book Company</publishername>
</publisher>
</biblioentry>
</bibliodiv>
</bibliography>
</nowiki></pre>

* publisher
* copyright
* identifier (ISBN)
* title
* author/editor/other credit/
* type (book)

== Ann Arbor District Library XML feed ==

Here's a record in XML format from their project to simplify
access to the catalog. More discussion on [http://www.blyberg.net John Blyberg's blog].

<pre>
<nowiki>
<p:Record>
<callnum>823 Bu</callnum>
<author>Burkart, Gina, 1971-</author>
<fulltitle>A parent's guide to Harry Potter / Gina Burkart</fulltitle>
<title>A parent's guide to Harry Potter </title>
<pubinfo>Downers Grove, Ill. : InterVarsity Press, c2005</pubinfo>
<desc>112 p</desc>
<bibliography>Includes bibliographical references</bibliography>
<contents>
The Harry hype -- More than a story -- The modern fairy tale -- Discussing fantasy with children --
Morals, not magic -- The real issues in Harry Potter -- Dealing with traumatic experiences -- Facing
fears -- Battling bullies -- Delving into diversity -- Hiding hurts -- Letting go of anger -- Getting
help -- Choosing good over evil -- The power of love -- Facing spiritual battles
</contents>
<isbn>0830832882</isbn>
<price>$11.00</price>
<lang>eng</lang>
<copies>0</copies>
<catdate>08-16-2005</catdate>
<mattype>a</mattype>
<avail>No copies available</avail>
<recordlink xlink:href="http://www.aadl.org/cat/seek/record=1249810"/>
</p:Record>
</nowiki>
</pre>

* url
* availablity
* identifier (ISBN/call number)
* author
* title
* publisher
* pages
* description/contents

== SimpleDC supported by the zoom toolkit ==

<pre>
<nowiki>
<dc xmlns="http/www.loc.gov/zing/srw/dcschema/v1.0/">
<title>Kantor Salomon Sulzer und seine Zeit : eine Dokumentation /</title>
<creator>Avenary, Hanoch.</creator>
<creator>Pass, Walter.</creator>
<creator>Vielmetti, Nikolaus.</creator>
<creator>Adler, Israel, (1925-)</creator>
<subject>Sulzer, Salomon, -- 1804-1890.</subject>
<subject>Jewish composers -- Austria -- Biography.</subject>
<subject>Cantors, Jewish -- Biography.</subject>
<date>1985</date>
<publisher>Sigmaringen : Jan Thorbecke Verlag</publisher>
<identifier>3799540636</identifier>
<description>300 p., [12] p. of plates : ill., music, ports. ; 24 cm.</description>
</dc>
</nowiki>
</pre>

this is the output of marc.toSimpleDC()

* title
* creator (author)
* subjects
* date
* publisher
* identifier
* description

(NOTE: this schema is from the example, not the source schema)

== SRU from the Library of Congress ==

http://z3950.loc.gov:7090/voyager?version=1.1&operation=searchRetrieve&query=dinosaur&maximumRecords=1&recordSchema=dc

<pre>
<nowiki>
<?xml version="1.0"?>
<zs:searchRetrieveResponse xmlns:zs="http://www.loc.gov/zing/srw/">
<zs:version>1.1</zs:version>
<zs:numberOfRecords>1701</zs:numberOfRecords>
<zs:records>
<zs:record>
<zs:recordSchema>info:srw/schema/1/dc-v1.1</zs:recordSchema>
<zs:recordPacking>xml</zs:recordPacking>
<zs:recordData>
<srw_dc:dc xmlns:srw_dc="info:srw/schema/1/dc-schema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://purl.org/dc/elements/1.1/"
xsi:schemaLocation="info:srw/schema/1/dc-schema http://www.loc.gov/z3950/agency/zing/srw/dc-schema.xsd">
<title>3-D dinosaur adventure [computer file].</title>
<creator>Knowledge Adventure, Inc.</creator>
<type>software, multimedia</type>
<publisher>Glendale, CA : Knowledge Adventure,</publisher>

<date>c1995.</date>
<language>eng</language>
<description>Employs a dinosaur theme-park setting to introduce users to Triassic, Jurassic, and
Cretaceous periods. Features hypertext dinosaur encyclopedia covering 150 million years of
paleontology. Includes animated video simulations, three-dimensional dinosaur museum, narration,
games, activities, and color illustrations.</description>
<description>Ages 5 to 10.</description>
<description>System requirements for PC: 486SX/25MHz processor or higher; 8MB RAM; Windows 3.1,
3.11, or 95; SVGA 256-color graphics adapter; hard drive with 5MB free space; double-speed CD-ROM
drive; MPC-compatible sound card; mouse.</description>
<description>System requirements for Macintosh: 68040 or Power PC processor; 8MB RAM; System 7.0 or
higher; 256-color graphics capability; thirteen-inch color monitor or larger; hard drive with 4MB
free space; double-speed CD-ROM drive.</description>

<description>Ages 5 to 10.</description>
<description>Employs a dinosaur theme-park setting to introduce users to Triassic, Jurassic, and
Cretaceous periods. Features hypertext dinosaur encyclopedia covering 150 million years of paleontology.
Includes animated video simulations, three-dimensional dinosaur museum, narration, games, activities,
and color illustrations.</description>
<subject>Dinosaurs--Juvenile software.</subject>
<subject>Dinosaurs.</subject>
<identifier>URN:ISBN:1569972133</identifier>
</srw_dc:dc>
</zs:recordData>
<zs:recordPosition>1</zs:recordPosition>
</zs:record>
</zs:records>
</zs:searchRetrieveResponse>

</nowiki>
</pre>

NOTE: this is just Dublin Core data in a special LOC envelope

== University of Bath reference type ==
<pre>
<nowiki>
<reference>
<authors>
<author>
<forename>E</forename>
<forename>M</forename>
<surname>Phillips</surname>
</author>
<author>
<forename>D</forename>
<forename>S</forename>
<surname>Pugh</surname>
</author>
</authors>
<date>1994</date>
<entity>
<book title="How to get a PhD: A handbook for students and their supervisors">
<location>
<placeofpublication>Buckinghamshire</placeofpublication>
<publisher>Open University</publisher>
</location>
</book>
</entity>
</reference>

<reference>
<authors>
<author>
<forename>Michael</forename>
<surname>Fumento</surname>
</author>
</authors>
<date>1996</date>
<entity>
<website pagetitle="Radon's Real Threat is to the EPA"
uri="http://www.consumeralert.org/fumento/radon1.htm"/>
</entity>
<frdescription>an article by a prolific newspaper columnist in the USA -
quotes empirical scientific research showing no provable link between radon in homes and elevated
cases of lung cancer</frdescription>
</reference>
</nowiki>
</pre>
[http://www.bath.ac.uk/schemas/screenshots/referencetype.png Schema extract]

* author
* date
* url
* description
* type (book/journal/conference)
* title
* artile
* volume
* issue
* chapter
* pages
* publisher
** publisher data (address, city, ...)

== Implied Schema ==
This is the start of the short list of common properties across documented formats. Once this is finished, there will be a union of Implied schemas between EXAMPLES and IMPLEMENTATIONS and we will see what that looks like. (This currently only covers a few of the formats listed, some documented formats still need to be explored)

* creator (author, editor, translator, contributor) - this can be handled with hCard, but will need an additional property to refine what "creator" means
* publisher (this can also be handled with hCard)
* subject/topics/keywords/categories/genre (there is a rel="tag" microformat)
* Description (abstract, note, tableOfContents)
* typeOfResource/format

common location information
* volume
* issue
* page
* edition

Date Fields
* Date Published (some formats have YEAR/MONTH sperately)
* Date Accessed (see [http://www.apastyle.org/elecsource.html here] for discussion from APA style guide.)

Again, I'll emphasize: "date published" is problematic. If one needs specificity, then better to have the following list of date classes: date (the generic), issued (braoder than published), copyright (often not the same as issuance date), accessed. -- bruce

Other fields
* Copyright/usage
* audience

* identifier (ISBN, ISSN, id, internal only, other)
* language (this can be handled by the xml:lang attribute native to HTML)

== Types and Roles ==
(Section is informative only as a place to capture various parts of publication citations.)

There are many different types of publications and this information should be captured in the citation. Possible types include:
* Novel/fiction (specify type -- literature, SF, romance, etc.?)
* Non-fiction
* Poem
* Play
* Magazine
* Reference (separate out encyclopedia, dictionary, almanac, etc.?)
* Journal
* Article within a journal
* Chapter within a book
* Dissertation
* Web Site
* Page within a web site
* Music Recording
* Video Recording
* Interview
* Physical object (Statue, Painting, etc.)
* ??

Question:
Certain works have specific types of citations, for example, the Bible--and, I assume, other religious works--have very specific citation formats with different relevant information (chapter/verse) than others, as do the works of Shakespeare. Should these be considered separate types/roles?

A: I think in terms of types, we should at least note the items (chapter, verse, etc). How they get dealt with is still way up in the air. - [[User:Tim White|Tim White]]

Likewise, there are several different roles associated with publications -- author, co-author, editor, translator, etc. Should these be captured under a master "role" or treated as individual elements?

A: Good question. I think there is an important distinction, but whether we follow a design pattern of "role-*" (or more likely "author-*) or some other pattern hasn't been discussed yet. - Tim

== Biblio RDF Class Schema ==
Regading the issue of types notes above, the [http://vocab.org/biblio/schema biblio schema] provides a comprehensive set of classes to describe citation metadata. It might prove useful as a guide for a micro-format. The primary classes are Agent, Reference, Collection, and Event. An "Article", then, would be a subclass of "Part", which in turn is a subclass of Reference. Likewise, a "Journal" is a subclass of a "Periodical," which in turn is a subclass of "Collection." An article would typically be linked to a journal through a dcterms:isPartOf relation.

== ISBN Uniform Resource Names ==

[http://www.faqs.org/rfcs/rfc3187.html RFC3187] defines an ISBN namespace for Uniform Resource Names (URNs).

Example:

URN:ISBN:0-395-36341-1

I'm not sure if any browser uses this data, but it might have an application in citations describing registered materials with an ISBN.

There is also a URN namespace for ISSN (International Standard Serial Number), which identifies serials/periodicals e.g. [http://alistapart.com A List Apart]. It is defined in [http://www.faqs.org/rfcs/rfc3044.html RFC3044]. Additional URN namespaces are listed at http://www.iana.org/assignments/urn-namespaces.

== You should know ==
* There are more then 1.300 citation ''styles'' in EndNote 9.
* Libraries have developed formats and rules for publications since more than 100 years. There are millions of records in library catalougues. You should '''at least''' be familiar with AACR and FRBR. There '''already are''' effords to create a new "microformat" called ''Resource Description and Access'' (RDA) [http://www.collectionscanada.ca/jsc/rdaprospectus.html]. Why don't you try to work with the professionals instead of amateurishly trying to reinvent the wheel and create yet another incompatible format? -- [[User:JakobVoss|JakobVoss]] 01:39, 5 Jun 2006 (PDT)
** I agree that the people involved in developing this microformat (including me) ought to be aware of these efforts (in particular FRBR), but I also think your argument is hopelessly naive and pretentious. The professionals you refer to are in fact library professionals, with their own bizarre traditios and unique information needs. Those are different than the professional scholars for whom citations are critical (me), or to the professional web developers who might want to implement these formats. What I do think is important is for us to understand the different design traditions, and their trade-offs, rather than to blindly create a microformat based on one of them -- Bruce (author of citeproc [http://xbiblio.sourceforge.net/citeproc] and csl [http://xbiblio.sourceforge.net/csl]).

Nice to meet you, Bruce! Maybe I'm naive but it still think that there is a way to combine the best of both worlds: scholars and library professionals. Both have developed bizarre traditions and it would be a pitty to create a new bizarre microformat that is not based on both of them. Thanks to your links to xbiblio. I a stumbled upon it a while ago but have to look at it deeper. -- [[User:JakobVoss|JakobVoss]] 11:48, 19 Jul 2006 (PDT)

=== ISBD ===

Oh, already a year ago! I was just trying to explain Microformats and its relevance for libraries ([http://jakoblog.de/2007/07/26/von-isbd-zum-web-20-mit-mikroformaten/ here (in German)]. You should have a look at the [http://en.wikipedia.org/wiki/International_Standard_Bibliographic_Description International Standard Bibliographic Description] (ISBD). These rules specify how a bibliographic should be displayed in a library catalouge. This format could be used as basis for hCitation because millions of records are availble in ISBD or variants in library catalouges all over the world.

Here is an example:

<pre>
Title: Harry Potter and the deathly hallows / Joanne K. Rowling. - [Children’s ed.], 1. ed. - London : Bloomsbury, 2007
ISBN: 0-7475-9105-9 - 978-0-7475-9105-4 (Children’s edition)
</pre>

This could be broken into "semantic peaces":

<pre>
<div class='hCitation'>
Titel:
Harry Potter and the deathly hallows /

Joanne K.
Rowling
</div>. -
[Children's ed.], 1. ed. -
London : Bloomsbury,
2007
</div>
<div>
ISBN:
0-7475-9105-9 -
978-0-7475-9105-4
(Children's edition)
</div>
</pre>

The advantage of ISBD is that it is very elaborated and covers many field and types of publications and special cases. Of course you need to simplifiy parts of it for the microformat. I'd prefer a bottom up design with the current mass of real-world records in todays libraries instead of top-down by thinking of an "ideal record" or limited playing databases. -- [[User:JakobVoss|JakobVoss]] 05:34, 26 Jul 2007 (PDT)

== OpenDocument ==
The OpenDocument Format also includes parts for citation and bibliography. See also the [http://bibliographic.openoffice.org/ OpenOffice Bibliographic project]. -- [[User:JakobVoss|JakobVoss]] 11:55, 19 Jul 2006 (PDT)

citation-formats

2006-07-19T18:55:51Z

JakobVoss: +OpenDocument

= Citation Formats =

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

See also:
* [[citation]]
* [[citation-brainstorming]]
* [[citation-examples]]
* [[citation-faq]]

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

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

<table border="1">
<tr>
<th>Dublin Core</th>
<th>MODS</th>
<th>bibTeX</th>
<th>Z39.80</th>
</tr>
<tr>
<td>Title (alternative)</td>
<td>titleInfo/title titleInfo/PartNum</td>
<td>booktitle title chapter number pages volume series</td>
<td>Analytic Title 
Collective or Series Title 
Monographic Title 
Work Fraction Title 
Location of Conference 
Main Entry 
Name of Conference 
Number of Meeting 
Other Title 
Parallel Title 
Title Abbriviation 
Title of Conference Proceedings 
Translated Title 
Uniform Title 
Abbriviated Translated Title 
Symposium or Session Title 
Collective or Series Edition 
Video/Film Edition 
</td>
</tr>
<tr>
<td>creator</td>
<td>name/namePart</td>
<td>author creator</td>
<td>Author, Primary 
Corporate Author, Primary 
Abstract Author 
Authorship Statement 
Acknowledged Supporters 
Assignee for Patents 
Chairperson of Conference 
Director of AV Program 
Other Author 
Reviewed Book Author 
Studio 
Sponsor of Conference 
Staff/Cast 
Symposium Chairperson 
Author Address or Affiliation 
Author Country 
Electronic Address of Author 
</td>
</tr>
<tr>
<td>subject</td>
<td>subject/topic</td>
<td>keywords</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Description (abstract | tableOfContents)</td>
<td>abstract note tableOfContents</td>
<td>abstract annotation note contents</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Contributor</td>
<td>name</td>
<td>editor?</td>
<td>Book/Report/Volume Editor 
Producer 
Translator 
</td>
</tr>
<tr>
<td>Date (available | created | dateAccepted | dateCopyrighted | dateSubmitted | issued | modified | valid)</td>
<td>originInfo/dateIssued originInfo/dateCreated originInfo/dateCaptured originInfo/dateOther</td>
<td>month year</td>
<td>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</td>
</tr>
<tr>
<td>Type</td>
<td>typeOfResource genre</td>
<td>@class type</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Format (extent | medium)</td>
<td>physicalDescription/internetMediaType physicalDescription/extent physicalDescription/form</td>
<td>howpublished</td>
<td>needs mapping</td>
</tr>
<tr>
<td>identifier (bibliographicCitation)</td>
<td>identifier</td>
<td>ISBN ISSN LCCN URL</td>
<td>ISBN Identifier Report Identfier ISSN</td>
</tr>
<tr>
<td>Source</td>
<td>relatedItem</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td>language</td>
<td>language</td>
<td>language</td>
<td bgcolor="#cccccc"></td>
</tr>
<tr>
<td>Relation (...)</td>
<td>relatedItem/...</td>
<td>crossRef</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Coverage (spacial | temporal)</td>
<td>subject/temporal subject/geographic subject/hierarchicalGeographic subject/cartographics</td>
<td></td>
<td>needs mapping</td>
</tr>
<tr>
<td bgcolor="#cccccc"></td>
<td>classifications</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td>Rights (accessRights | license)</td>
<td>accessConditions</td>
<td>copyright</td>
<td>needs mapping</td>
</tr>
<tr>
<td>publisher</td>
<td bgcolor="#cccccc"></td>
<td>publisher</td>
<td>Publisher Name 
Place of Publication 
Country of Publication 
Generic Address 
</td>
</tr>
<tr>
<td>audience (educationLevel | mediator)</td>
<td>targetAudience</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td bgcolor="#999999">accualMethod accualPeriodicaty accualPolicy instrcutionalMethod provenance rightsHolder</td>
<td bgcolor="#999999">location extension recordInfo</td>
<td bgcolor="#999999">address afflilication location edition institution journal key mrnumber organization price school size</td>
<td bgcolor="#999999">(the following need to be mapped to the above rows or left here as other) 
Database Source 
Databse Record Identifier 
Database Producer Name 
Rights Management 
Subfile 
Other Source Identifier 
Vendor Record Identifier 
Database Vendor Name 
Column Number 
Edition 
Frequency of Publication 
Internet Location for Document 
Supplement/Part/Special number identifer 
Issue Identifier 
Location in Work 
Number of the Chapter 
Number in Series 
Volume Identifier 
Section Indentifier 
</td>
</tr>
</table>

== Dublin Core Metadata ==
[http://dublincore.org/ Dublin Core] metadata uses a small vocabulary to descibe the data.
* contributor
* coverage
* creator
* date
* description
* format
* identifier
* language
* publisher
* relation
* rights
* source
* subject
* title
* type

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

* abstract refines description.
* accessRights refines rights

[http://dublincore.org/documents/dc-citation-guidelines/ Guidelines for Encoding Bibliographic Citation Information in Dublin Core Metadata]

== MODS (Metadata Object Description Schema) ==
This is a format developed for the Libray of Congress for a bibliographic element set that may be used for a variety of purposes, and particularly for library applications.

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

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

== NLM Journal Publishing DTD ==

[http://dtd.nlm.nih.gov/publishing/tag-library/2.1/n-fv30.html http://dtd.nlm.nih.gov/publishing/tag-library/2.1/n-fv30.html]

The [http://dtd.nlm.nih.gov/publishing/tag-library/ NLM Journal Publishing DTD] defines the schema used for publishing journal articles as XML. The <pre><citation></pre> element can be placed with paragraphs or within a <pre><ref-list></pre> element at the end of the article.

"Although the DTD does not enforce it, a citation to a journal article should be tagged with as many as possible of the following, so that PubMed Central, CrossRef, or other matching service can make the citation into a live link:

<table border="1">
<tr><td>source</td><td>The title of a journal, book, conference proceedings, etc. that is the source of the cited material. (Note: In PubMed Central processing, this is typically the MEDLINE abbreviation of the journal name.)</td></tr>
<tr><td>article-title</td><td>Title of the article</td></tr>
<tr><td>volume</td><td>Volume of the journal</td></tr>
<tr><td>issue</td><td>Issue of the journal</td></tr>
<tr><td>fpage</td><td>Page number on which the article starts</td></tr>
<tr><td>name</td><td>Name of an author or editor</td></tr>
<tr><td>year</td><td>Year of publication</td></tr>
<tr><td>month</td><td>Month of publication (if present)</td></tr>
<tr><td>day</td><td>Date of publication (if present)</td></tr>
</table>

The other elements (described [http://dtd.nlm.nih.gov/publishing/tag-library/2.1/n-fv30.html here]) may be tagged if desired. Use the <source> element for titles of books, conference proceedings, etc."

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

* author
* publication date
* publisher
* pages
* title (article/book)
* url

== BibTeX ==
=== Fields Used by Bibtex ===

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

=== BibTeX citation Types ===
A reference can be to any of a variety of types. Following is a list of types. Each one also explains the fields associated with that type. Any fields not listed as required or optional are considered to be ignored.
<table border="1" width="100%">
<tr>
<td>article:</td>
<td>An article from a journal or magazine. Required fields: author, title, journal, year. Optional fields: volume, number, pages, month, note, key.</td>
</tr>
<tr>
<td>book:</td>
<td>A book with an explicit publisher. Required fields: author or editor, title, publisher, year. Optional fields: volume, series, address, edition, month, note, key.</td>
</tr>
<tr>
<td>booklet: </td>
<td>A work that is printed and bound, but without a named publisher or sponsoring institution. Required fields: title. Optional fields: author, howpublished, address, month, year, note, key.</td>
</tr>
<tr>
<td>collection:</td>
<td>A collection of works. Same as Proceedings.</td>
</tr>
<tr>
<td>conference:</td>
<td>The same as Inproceedings.</td>
</tr>
<tr>
<td>inbook:</td>
<td>A part of a book, which may be a chapter and/or arange of pages. Required fields: author or editor, title, chapter and/or pages, publisher, year. Optional fields: volumer, series, address, edition, month, note, key.</td>
</tr>
<tr>
<td>incollection:</td>
<td>A part of a book with its own title. Required fields: author, title, booktitle, publisher, year. Optional fields: editor, pages, organization, publisher, address, month, note, key.</td>
</tr>
<tr>
<td>inproceedings:</td>
<td>An article in a conference proceedings. Required fields: author, title, booktitle, year. Optional fields: editor, pages, organization, publisher, address, month, note, key.</td>
</tr>
<tr>
<td>manual: </td>
<td>Technical documentation. Required fields: title. Optional fields: author, organization, address, edition, month, year, note.</td>
</tr>
<tr>
<td>mastersthesis:</td>
<td>A Master's thesis. Required fields: author, title, school, year. Optional fields: address, month, note, key.</td>
</tr>
<tr>
<td>misc:</td>
<td>Use this type when nothing else fits. Required fields: none. Optional fields: author, title, howpublished, month, year, note, key.</td>
</tr>
<tr>
<td>patent:</td>
<td>A patent.</td>
</tr>
<tr>
<td>phdthesis:</td>
<td>A Ph.D. thesis. Required fields: author, title, school, year. Optional fields: address, month, note, key.</td>
</tr>
<tr>
<td>proceedings:</td>
<td>The proceedings of a conference. Required fields: title, year. Optional fields: editor, publisher, organization, address, month, note, key.</td>
</tr>
<tr>
<td>techreport:</td>
<td>A report published by a school or other institution, usually numbered within a series. Required fields: author, title, institution, year. Optional fields: type, number, address, month, note, key.</td>
</tr>
<tr>
<td>unpublished:</td>
<td>A document with an author and title, but not formally published. Required fields: author, title, note. Optional fields: month, year, key.</td>
</tr>
</table>

==== Examples ====
<pre><nowiki>
@book{kn:gnus,

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

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

@article{XAi_HSCheng_1994a,

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

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

== RIS ==

RIS is similar to BibTeX and is handled by most desktop and web-based bibliography management software.

The specification and field types/tags are described at [http://www.refman.com/support/risformat_intro.asp http://www.refman.com/support/risformat_intro.asp]

In particular, see [http://www.refman.com/support/risformat_reftypes.asp the list of different reference types].

A sample item in RIS format:
<pre>
TY - JOUR
A1 - Baldwin,S.A.
A1 - Fugaccia,I.
A1 - Brown,D.R.
A1 - Brown,L.V.
A1 - Scheff,S.W.
T1 - Blood-brain barrier breach following
cortical contusion in the rat
JO - J.Neurosurg.
Y1 - 1996
VL - 85
SP - 476
EP - 481
RP - Not In File
KW - cortical contusion
KW - blood-brain barrier
KW - horseradish peroxidase
KW - head trauma
KW - hippocampus
KW - rat
ER -
</pre>

[http://www-static.cc.gatech.edu/classes/RWL/Projects/citation/Applet/OnlineHelp/refer_doc.html Refer] is a similar, smaller bibliographic format.

* author
* title
* type
* Identifier
* notes/abstract
* reprint status
* keyword
* volume
* issue
* pages
* year
* periodical name (where published)
* publisher
** publisher city
** publisher address
* related links
* link to PDF
* availablity

== OpenURL ==

OpenURL aka [http://www.niso.org/standards/standard_detail.cfm?std_id=783 Z39.88] defines a standard way of bundling citation data in a URL. It is widely deployed in academic libraries around the world to provide access to licensed content via link resolvers such as [http://www.exlibrisgroup.com/sfx_openurl.htm SFX]. The Context Object in Span ([http://ocoins.info/ COinS]) community standard represents one way to embed OpenURLs in XHTML without including a resolver target. OpenURL also provides an XML encoding.

Example (from a book review written using the Structured Blogging plugin):

<pre><nowiki>
ISBN: 
0679426612
</nowiki></pre>

Another example, a journal this time:
<pre>
<nowiki>

</nowiki>
</pre>

As you can see this isn't very much like semantic XHTML at all. However significant work has gone into defining the set of Key/Encoded Values (KEVs) that can be used in various [http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=ListRecords&metadataPrefix=oai_dc&set=Core:Metadata+Formats types] of citations: [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:book book], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:dissertation dissertation], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:journal journal], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:patent patent]. It would be possible to simply provide a standard XHTML bundling for these keys as a microformat.

=== Example ===

<pre>
<nowiki>

<div class="openurl-journal">
Berners-Lee,
Tim</a>; Hendler, James; Lassila, Ora.
"The Semantic Web".
Scientific American
284(5), pp.
pp. 34-43.
0036-8733
</div>

</nowiki>
</pre>

Using OpenURL in this way would enable third party applications that could, say grab citation metadata from a blog, and without much work fire it off at your university's or public libraries openurl resolver to see if the article is available via a licensed databases. The benefits [http://www.infotoday.com/newsbreaks/nb050801-1.shtml have] [http://www.ariadne.ac.uk/issue43/chudnov/ been] [http://www.wallandbinkley.com/quaedam/?p=30 noted] [http://hublog.hubmed.org/archives/001163.html elsewhere].

== The OpenURL Briefly Explained ==

An OpenURL consists of two independent parts: the ContextObject (or the bibliographic metadata surrounding a citation) and the location of resolver to parse the metadata and present contextual services based on said metadata. The problem is that the term "OpenURL" is also used as a catch-all for all of the independent parts and how they work. This is mainly because it's a catchier term than "Z39.88", which is the [http://www.niso.org/standards/standard_detail.cfm?std_id=783 NISO standard all this is based upon].

The most common representation of the OpenURL ContextObject is seen as arguments in a URL string (which is referred to as "San Antonio Profile 1" -- more commonly SAP1 -- and is represented in Key Encoded Values -- KEVs). This "representation" is independent of the ContextObject (from here on known as CO) itself and is only intended to permit the CO to be transmitted via an HTTP GET request.

There is also SAP2, which is an XML representation of the CO (see: [http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadataPrefix=oai_dc&identifier=info:ofi/fmt:xml:xsd:ctx here] for more information) and is a much more human readable format. This still falls outside the scope of microformats, but makes the point that encoding has nothing to do with the CO itself. They are just agreed upon means of conveying the CO to enable machines act upon them consistently.

The ContextObject could be conveyed just as easily in XHTML using attributes, as long as the terms follow the vocabulary defined in the OpenURL framework. The important thing to focus on here is the ContextObject -- the address of the link resolver ''is'' institution-specific and should be handled by a user's (or machine's) activating agent.

However, the link resolver is still a very important component to this whole process. Getting users "appropriate copy" is a very real (and very difficult) problem that libraries are trying to solve. Link resolvers are a pretty efficient means of overcoming this hurdle, so it would make sense to mark up bibiographic citations in a way that link resolvers can easily parse.

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

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

== DocBook ==

A subset of the DocBook vocabulary is dedicated to representing a bibliography: http://www.docbook.org/tdg/en/html/bibliography.html

<pre><nowiki>
<!DOCTYPE bibliography PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
<bibliography>
<title>Languages and Semantics</title>
<bibliodiv>
<title>Books</title>
<biblioentry>
<title>Course in General Linguistics</title>
<abbrev>deSaussure59</abbrev>
<author><firstname>Ferdinand</firstname><surname>de Saussure</surname></author>
<editor><firstname>Charles</firstname><surname>Bally</surname></editor>
<editor><firstname>Albert</firstname><surname>Sechehaye</surname></editor>
<othercredit role="translator"><firstname>Wade</firstname><surname>Baskin</surname></othercredit>
<copyright>
<year>1959</year>
<holder>The Philosophical Library Inc.</holder>
</copyright>
<isbn>07-016524-6</isbn>
<publisher>
<publishername>McGraw-Hill Book Company</publishername>
</publisher>
</biblioentry>
</bibliodiv>
</bibliography>
</nowiki></pre>

* publisher
* copyright
* identifier (ISBN)
* title
* author/editor/other credit/
* type (book)

== Ann Arbor District Library XML feed ==

Here's a record in XML format from their project to simplify
access to the catalog. More discussion on [http://www.blyberg.net John Blyberg's blog].

<pre>
<nowiki>
<p:Record>
<callnum>823 Bu</callnum>
<author>Burkart, Gina, 1971-</author>
<fulltitle>A parent's guide to Harry Potter / Gina Burkart</fulltitle>
<title>A parent's guide to Harry Potter </title>
<pubinfo>Downers Grove, Ill. : InterVarsity Press, c2005</pubinfo>
<desc>112 p</desc>
<bibliography>Includes bibliographical references</bibliography>
<contents>
The Harry hype -- More than a story -- The modern fairy tale -- Discussing fantasy with children --
Morals, not magic -- The real issues in Harry Potter -- Dealing with traumatic experiences -- Facing
fears -- Battling bullies -- Delving into diversity -- Hiding hurts -- Letting go of anger -- Getting
help -- Choosing good over evil -- The power of love -- Facing spiritual battles
</contents>
<isbn>0830832882</isbn>
<price>$11.00</price>
<lang>eng</lang>
<copies>0</copies>
<catdate>08-16-2005</catdate>
<mattype>a</mattype>
<avail>No copies available</avail>
<recordlink xlink:href="http://www.aadl.org/cat/seek/record=1249810"/>
</p:Record>
</nowiki>
</pre>

* url
* availablity
* identifier (ISBN/call number)
* author
* title
* publisher
* pages
* description/contents

== SimpleDC supported by the zoom toolkit ==

<pre>
<nowiki>
<dc xmlns="http/www.loc.gov/zing/srw/dcschema/v1.0/">
<title>Kantor Salomon Sulzer und seine Zeit : eine Dokumentation /</title>
<creator>Avenary, Hanoch.</creator>
<creator>Pass, Walter.</creator>
<creator>Vielmetti, Nikolaus.</creator>
<creator>Adler, Israel, (1925-)</creator>
<subject>Sulzer, Salomon, -- 1804-1890.</subject>
<subject>Jewish composers -- Austria -- Biography.</subject>
<subject>Cantors, Jewish -- Biography.</subject>
<date>1985</date>
<publisher>Sigmaringen : Jan Thorbecke Verlag</publisher>
<identifier>3799540636</identifier>
<description>300 p., [12] p. of plates : ill., music, ports. ; 24 cm.</description>
</dc>
</nowiki>
</pre>

this is the output of marc.toSimpleDC()

* title
* creator (author)
* subjects
* date
* publisher
* identifier
* description

(NOTE: this schema is from the example, not the source schema)

== SRU from the Library of Congress ==

http://z3950.loc.gov:7090/voyager?version=1.1&operation=searchRetrieve&query=dinosaur&maximumRecords=1&recordSchema=dc

<pre>
<nowiki>
<?xml version="1.0"?>
<zs:searchRetrieveResponse xmlns:zs="http://www.loc.gov/zing/srw/">
<zs:version>1.1</zs:version>
<zs:numberOfRecords>1701</zs:numberOfRecords>
<zs:records>
<zs:record>
<zs:recordSchema>info:srw/schema/1/dc-v1.1</zs:recordSchema>
<zs:recordPacking>xml</zs:recordPacking>
<zs:recordData>
<srw_dc:dc xmlns:srw_dc="info:srw/schema/1/dc-schema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://purl.org/dc/elements/1.1/"
xsi:schemaLocation="info:srw/schema/1/dc-schema http://www.loc.gov/z3950/agency/zing/srw/dc-schema.xsd">
<title>3-D dinosaur adventure [computer file].</title>
<creator>Knowledge Adventure, Inc.</creator>
<type>software, multimedia</type>
<publisher>Glendale, CA : Knowledge Adventure,</publisher>

<date>c1995.</date>
<language>eng</language>
<description>Employs a dinosaur theme-park setting to introduce users to Triassic, Jurassic, and
Cretaceous periods. Features hypertext dinosaur encyclopedia covering 150 million years of
paleontology. Includes animated video simulations, three-dimensional dinosaur museum, narration,
games, activities, and color illustrations.</description>
<description>Ages 5 to 10.</description>
<description>System requirements for PC: 486SX/25MHz processor or higher; 8MB RAM; Windows 3.1,
3.11, or 95; SVGA 256-color graphics adapter; hard drive with 5MB free space; double-speed CD-ROM
drive; MPC-compatible sound card; mouse.</description>
<description>System requirements for Macintosh: 68040 or Power PC processor; 8MB RAM; System 7.0 or
higher; 256-color graphics capability; thirteen-inch color monitor or larger; hard drive with 4MB
free space; double-speed CD-ROM drive.</description>

<description>Ages 5 to 10.</description>
<description>Employs a dinosaur theme-park setting to introduce users to Triassic, Jurassic, and
Cretaceous periods. Features hypertext dinosaur encyclopedia covering 150 million years of paleontology.
Includes animated video simulations, three-dimensional dinosaur museum, narration, games, activities,
and color illustrations.</description>
<subject>Dinosaurs--Juvenile software.</subject>
<subject>Dinosaurs.</subject>
<identifier>URN:ISBN:1569972133</identifier>
</srw_dc:dc>
</zs:recordData>
<zs:recordPosition>1</zs:recordPosition>
</zs:record>
</zs:records>
</zs:searchRetrieveResponse>

</nowiki>
</pre>

NOTE: this is just Dublin Core data in a special LOC envelope

== University of Bath reference type ==
<pre>
<nowiki>
<reference>
<authors>
<author>
<forename>E</forename>
<forename>M</forename>
<surname>Phillips</surname>
</author>
<author>
<forename>D</forename>
<forename>S</forename>
<surname>Pugh</surname>
</author>
</authors>
<date>1994</date>
<entity>
<book title="How to get a PhD: A handbook for students and their supervisors">
<location>
<placeofpublication>Buckinghamshire</placeofpublication>
<publisher>Open University</publisher>
</location>
</book>
</entity>
</reference>

<reference>
<authors>
<author>
<forename>Michael</forename>
<surname>Fumento</surname>
</author>
</authors>
<date>1996</date>
<entity>
<website pagetitle="Radon's Real Threat is to the EPA"
uri="http://www.consumeralert.org/fumento/radon1.htm"/>
</entity>
<frdescription>an article by a prolific newspaper columnist in the USA -
quotes empirical scientific research showing no provable link between radon in homes and elevated
cases of lung cancer</frdescription>
</reference>
</nowiki>
</pre>
[http://www.bath.ac.uk/schemas/screenshots/referencetype.png Schema extract]

* author
* date
* url
* description
* type (book/journal/conference)
* title
* artile
* volume
* issue
* chapter
* pages
* publisher
** publisher data (address, city, ...)

== Implied Schema ==
This is the start of the short list of common properties across documented formats. Once this is finished, there will be a union of Implied schemas between EXAMPLES and IMPLEMENTATIONS and we will see what that looks like. (This currently only covers a few of the formats listed, some documented formats still need to be explored)

* creator (author, editor, translator, contributor) - this can be handled with hCard, but will need an additional property to refine what "creator" means
* publisher (this can also be handled with hCard)
* subject/topics/keywords/categories/genre (there is a rel="tag" microformat)
* Description (abstract, note, tableOfContents)
* typeOfResource/format

common location information
* volume
* issue
* page
* edition

Date Fields
* Date Published (some formats have YEAR/MONTH sperately)
* Date accessed (see [http://www.columbia.edu/cu/cup/cgos/basic.html here] for examples)

Again, I'll emphasize: "date published" is problematic. If one needs specificity, then better to have the following list of date classes: date (the generic), issued (braoder than published), copyright (often not the same as issuance date), accessed. -- bruce

Other fields
* Copyright/usage
* audience

* identifier (ISBN, ISSN, id, internal only, other)
* language (this can be handled by the xml:lang attribute native to HTML)

== Types and Roles ==
(Section is informative only as a place to capture various parts of publication citations.)

There are many different types of publications and this information should be captured in the citation. Possible types include:
* Novel/fiction (specify type -- literature, SF, romance, etc.?)
* Non-fiction
* Poem
* Play
* Magazine
* Reference (separate out encyclopedia, dictionary, almanac, etc.?)
* Journal
* Article within a journal
* Chapter within a book
* Dissertation
* Web Site
* Page within a web site
* Music Recording
* Video Recording
* Interview
* Physical object (Statue, Painting, etc.)
* ??

Question:
Certain works have specific types of citations, for example, the Bible--and, I assume, other religious works--have very specific citation formats with different relevant information (chapter/verse) than others, as do the works of Shakespeare. Should these be considered separate types/roles?

A: I think in terms of types, we should at least note the items (chapter, verse, etc). How they get dealt with is still way up in the air. - [[User:Tim White|Tim White]]

Likewise, there are several different roles associated with publications -- author, co-author, editor, translator, etc. Should these be captured under a master "role" or treated as individual elements?

A: Good question. I think there is an important distinction, but whether we follow a design pattern of "role-*" (or more likely "author-*) or some other pattern hasn't been discussed yet. - Tim

== Biblio RDF Class Schema ==
Regading the issue of types notes above, the [http://vocab.org/biblio/schema biblio schema] provides a comprehensive set of classes to describe citation metadata. It might prove useful as a guide for a micro-format. The primary classes are Agent, Reference, Collection, and Event. An "Article", then, would be a subclass of "Part", which in turn is a subclass of Reference. Likewise, a "Journal" is a subclass of a "Periodical," which in turn is a subclass of "Collection." An article would typically be linked to a journal through a dcterms:isPartOf relation.

== ISBN:// Protocol ==

[http://www.faqs.org/rfcs/rfc3187.html RFC3187] defines an isbn protocol

Example:

URN:ISBN:0-395-36341-1

I'm not sure if any browser uses this data, but it might be have an application in citations describing registered materials with an ISBN

== You should know ==
* There are more then 1.300 citation ''styles'' in EndNote 9.
* Libraries have developed formats and rules for publications since more than 100 years. There are millions of records in library catalougues. You should '''at least''' be familiar with AACR and FRBR. There '''already are''' effords to create a new "microformat" called ''Resource Description and Access'' (RDA) [http://www.collectionscanada.ca/jsc/rdaprospectus.html]. Why don't you try to work with the professionals instead of amateurishly trying to reinvent the wheel and create yet another incompatible format? -- [[User:JakobVoss|JakobVoss]] 01:39, 5 Jun 2006 (PDT)
** I agree that the people involved in developing this microformat (including me) ought to be aware of these efforts (in particular FRBR), but I also think your argument is hopelessly naive and pretentious. The professionals you refer to are in fact library professionals, with their own bizarre traditios and unique information needs. Those are different than the professional scholars for whom citations are critical (me), or to the professional web developers who might want to implement these formats. What I do think is important is for us to understand the different design traditions, and their trade-offs, rather than to blindly create a microformat based on one of them -- Bruce (author of citeproc [http://xbiblio.sourceforge.net/citeproc] and csl [http://xbiblio.sourceforge.net/csl]).

Nice to meet you, Bruce! Maybe I'm naive but it still think that there is a way to combine the best of both worlds: scholars and library professionals. Both have developed bizarre traditions and it would be a pitty to create a new bizarre microformat that is not based on both of them. Thanks to your links to xbiblio. I a stumbled upon it a while ago but have to look at it deeper. -- [[User:JakobVoss|JakobVoss]] 11:48, 19 Jul 2006 (PDT)

== OpenDocument ==
The OpenDocument Format also includes parts for citation and bibliography. See also the [http://bibliographic.openoffice.org/ OpenOffice Bibliographic project]. -- [[User:JakobVoss|JakobVoss]] 11:55, 19 Jul 2006 (PDT)

citation-formats

2006-07-19T18:48:55Z

JakobVoss: /* You should know */ nice to meet you :-)

= Citation Formats =

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

See also:
* [[citation]]
* [[citation-brainstorming]]
* [[citation-examples]]
* [[citation-faq]]

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

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

<table border="1">
<tr>
<th>Dublin Core</th>
<th>MODS</th>
<th>bibTeX</th>
<th>Z39.80</th>
</tr>
<tr>
<td>Title (alternative)</td>
<td>titleInfo/title titleInfo/PartNum</td>
<td>booktitle title chapter number pages volume series</td>
<td>Analytic Title 
Collective or Series Title 
Monographic Title 
Work Fraction Title 
Location of Conference 
Main Entry 
Name of Conference 
Number of Meeting 
Other Title 
Parallel Title 
Title Abbriviation 
Title of Conference Proceedings 
Translated Title 
Uniform Title 
Abbriviated Translated Title 
Symposium or Session Title 
Collective or Series Edition 
Video/Film Edition 
</td>
</tr>
<tr>
<td>creator</td>
<td>name/namePart</td>
<td>author creator</td>
<td>Author, Primary 
Corporate Author, Primary 
Abstract Author 
Authorship Statement 
Acknowledged Supporters 
Assignee for Patents 
Chairperson of Conference 
Director of AV Program 
Other Author 
Reviewed Book Author 
Studio 
Sponsor of Conference 
Staff/Cast 
Symposium Chairperson 
Author Address or Affiliation 
Author Country 
Electronic Address of Author 
</td>
</tr>
<tr>
<td>subject</td>
<td>subject/topic</td>
<td>keywords</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Description (abstract | tableOfContents)</td>
<td>abstract note tableOfContents</td>
<td>abstract annotation note contents</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Contributor</td>
<td>name</td>
<td>editor?</td>
<td>Book/Report/Volume Editor 
Producer 
Translator 
</td>
</tr>
<tr>
<td>Date (available | created | dateAccepted | dateCopyrighted | dateSubmitted | issued | modified | valid)</td>
<td>originInfo/dateIssued originInfo/dateCreated originInfo/dateCaptured originInfo/dateOther</td>
<td>month year</td>
<td>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</td>
</tr>
<tr>
<td>Type</td>
<td>typeOfResource genre</td>
<td>@class type</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Format (extent | medium)</td>
<td>physicalDescription/internetMediaType physicalDescription/extent physicalDescription/form</td>
<td>howpublished</td>
<td>needs mapping</td>
</tr>
<tr>
<td>identifier (bibliographicCitation)</td>
<td>identifier</td>
<td>ISBN ISSN LCCN URL</td>
<td>ISBN Identifier Report Identfier ISSN</td>
</tr>
<tr>
<td>Source</td>
<td>relatedItem</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td>language</td>
<td>language</td>
<td>language</td>
<td bgcolor="#cccccc"></td>
</tr>
<tr>
<td>Relation (...)</td>
<td>relatedItem/...</td>
<td>crossRef</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Coverage (spacial | temporal)</td>
<td>subject/temporal subject/geographic subject/hierarchicalGeographic subject/cartographics</td>
<td></td>
<td>needs mapping</td>
</tr>
<tr>
<td bgcolor="#cccccc"></td>
<td>classifications</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td>Rights (accessRights | license)</td>
<td>accessConditions</td>
<td>copyright</td>
<td>needs mapping</td>
</tr>
<tr>
<td>publisher</td>
<td bgcolor="#cccccc"></td>
<td>publisher</td>
<td>Publisher Name 
Place of Publication 
Country of Publication 
Generic Address 
</td>
</tr>
<tr>
<td>audience (educationLevel | mediator)</td>
<td>targetAudience</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td bgcolor="#999999">accualMethod accualPeriodicaty accualPolicy instrcutionalMethod provenance rightsHolder</td>
<td bgcolor="#999999">location extension recordInfo</td>
<td bgcolor="#999999">address afflilication location edition institution journal key mrnumber organization price school size</td>
<td bgcolor="#999999">(the following need to be mapped to the above rows or left here as other) 
Database Source 
Databse Record Identifier 
Database Producer Name 
Rights Management 
Subfile 
Other Source Identifier 
Vendor Record Identifier 
Database Vendor Name 
Column Number 
Edition 
Frequency of Publication 
Internet Location for Document 
Supplement/Part/Special number identifer 
Issue Identifier 
Location in Work 
Number of the Chapter 
Number in Series 
Volume Identifier 
Section Indentifier 
</td>
</tr>
</table>

== Dublin Core Metadata ==
[http://dublincore.org/ Dublin Core] metadata uses a small vocabulary to descibe the data.
* contributor
* coverage
* creator
* date
* description
* format
* identifier
* language
* publisher
* relation
* rights
* source
* subject
* title
* type

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

* abstract refines description.
* accessRights refines rights

[http://dublincore.org/documents/dc-citation-guidelines/ Guidelines for Encoding Bibliographic Citation Information in Dublin Core Metadata]

== MODS (Metadata Object Description Schema) ==
This is a format developed for the Libray of Congress for a bibliographic element set that may be used for a variety of purposes, and particularly for library applications.

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

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

== NLM Journal Publishing DTD ==

[http://dtd.nlm.nih.gov/publishing/tag-library/2.1/n-fv30.html http://dtd.nlm.nih.gov/publishing/tag-library/2.1/n-fv30.html]

The [http://dtd.nlm.nih.gov/publishing/tag-library/ NLM Journal Publishing DTD] defines the schema used for publishing journal articles as XML. The <pre><citation></pre> element can be placed with paragraphs or within a <pre><ref-list></pre> element at the end of the article.

"Although the DTD does not enforce it, a citation to a journal article should be tagged with as many as possible of the following, so that PubMed Central, CrossRef, or other matching service can make the citation into a live link:

<table border="1">
<tr><td>source</td><td>The title of a journal, book, conference proceedings, etc. that is the source of the cited material. (Note: In PubMed Central processing, this is typically the MEDLINE abbreviation of the journal name.)</td></tr>
<tr><td>article-title</td><td>Title of the article</td></tr>
<tr><td>volume</td><td>Volume of the journal</td></tr>
<tr><td>issue</td><td>Issue of the journal</td></tr>
<tr><td>fpage</td><td>Page number on which the article starts</td></tr>
<tr><td>name</td><td>Name of an author or editor</td></tr>
<tr><td>year</td><td>Year of publication</td></tr>
<tr><td>month</td><td>Month of publication (if present)</td></tr>
<tr><td>day</td><td>Date of publication (if present)</td></tr>
</table>

The other elements (described [http://dtd.nlm.nih.gov/publishing/tag-library/2.1/n-fv30.html here]) may be tagged if desired. Use the <source> element for titles of books, conference proceedings, etc."

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

* author
* publication date
* publisher
* pages
* title (article/book)
* url

== BibTeX ==
=== Fields Used by Bibtex ===

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

=== BibTeX citation Types ===
A reference can be to any of a variety of types. Following is a list of types. Each one also explains the fields associated with that type. Any fields not listed as required or optional are considered to be ignored.
<table border="1" width="100%">
<tr>
<td>article:</td>
<td>An article from a journal or magazine. Required fields: author, title, journal, year. Optional fields: volume, number, pages, month, note, key.</td>
</tr>
<tr>
<td>book:</td>
<td>A book with an explicit publisher. Required fields: author or editor, title, publisher, year. Optional fields: volume, series, address, edition, month, note, key.</td>
</tr>
<tr>
<td>booklet: </td>
<td>A work that is printed and bound, but without a named publisher or sponsoring institution. Required fields: title. Optional fields: author, howpublished, address, month, year, note, key.</td>
</tr>
<tr>
<td>collection:</td>
<td>A collection of works. Same as Proceedings.</td>
</tr>
<tr>
<td>conference:</td>
<td>The same as Inproceedings.</td>
</tr>
<tr>
<td>inbook:</td>
<td>A part of a book, which may be a chapter and/or arange of pages. Required fields: author or editor, title, chapter and/or pages, publisher, year. Optional fields: volumer, series, address, edition, month, note, key.</td>
</tr>
<tr>
<td>incollection:</td>
<td>A part of a book with its own title. Required fields: author, title, booktitle, publisher, year. Optional fields: editor, pages, organization, publisher, address, month, note, key.</td>
</tr>
<tr>
<td>inproceedings:</td>
<td>An article in a conference proceedings. Required fields: author, title, booktitle, year. Optional fields: editor, pages, organization, publisher, address, month, note, key.</td>
</tr>
<tr>
<td>manual: </td>
<td>Technical documentation. Required fields: title. Optional fields: author, organization, address, edition, month, year, note.</td>
</tr>
<tr>
<td>mastersthesis:</td>
<td>A Master's thesis. Required fields: author, title, school, year. Optional fields: address, month, note, key.</td>
</tr>
<tr>
<td>misc:</td>
<td>Use this type when nothing else fits. Required fields: none. Optional fields: author, title, howpublished, month, year, note, key.</td>
</tr>
<tr>
<td>patent:</td>
<td>A patent.</td>
</tr>
<tr>
<td>phdthesis:</td>
<td>A Ph.D. thesis. Required fields: author, title, school, year. Optional fields: address, month, note, key.</td>
</tr>
<tr>
<td>proceedings:</td>
<td>The proceedings of a conference. Required fields: title, year. Optional fields: editor, publisher, organization, address, month, note, key.</td>
</tr>
<tr>
<td>techreport:</td>
<td>A report published by a school or other institution, usually numbered within a series. Required fields: author, title, institution, year. Optional fields: type, number, address, month, note, key.</td>
</tr>
<tr>
<td>unpublished:</td>
<td>A document with an author and title, but not formally published. Required fields: author, title, note. Optional fields: month, year, key.</td>
</tr>
</table>

==== Examples ====
<pre><nowiki>
@book{kn:gnus,

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

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

@article{XAi_HSCheng_1994a,

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

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

== RIS ==

RIS is similar to BibTeX and is handled by most desktop and web-based bibliography management software.

The specification and field types/tags are described at [http://www.refman.com/support/risformat_intro.asp http://www.refman.com/support/risformat_intro.asp]

In particular, see [http://www.refman.com/support/risformat_reftypes.asp the list of different reference types].

A sample item in RIS format:
<pre>
TY - JOUR
A1 - Baldwin,S.A.
A1 - Fugaccia,I.
A1 - Brown,D.R.
A1 - Brown,L.V.
A1 - Scheff,S.W.
T1 - Blood-brain barrier breach following
cortical contusion in the rat
JO - J.Neurosurg.
Y1 - 1996
VL - 85
SP - 476
EP - 481
RP - Not In File
KW - cortical contusion
KW - blood-brain barrier
KW - horseradish peroxidase
KW - head trauma
KW - hippocampus
KW - rat
ER -
</pre>

[http://www-static.cc.gatech.edu/classes/RWL/Projects/citation/Applet/OnlineHelp/refer_doc.html Refer] is a similar, smaller bibliographic format.

* author
* title
* type
* Identifier
* notes/abstract
* reprint status
* keyword
* volume
* issue
* pages
* year
* periodical name (where published)
* publisher
** publisher city
** publisher address
* related links
* link to PDF
* availablity

== OpenURL ==

OpenURL aka [http://www.niso.org/standards/standard_detail.cfm?std_id=783 Z39.88] defines a standard way of bundling citation data in a URL. It is widely deployed in academic libraries around the world to provide access to licensed content via link resolvers such as [http://www.exlibrisgroup.com/sfx_openurl.htm SFX]. The Context Object in Span ([http://ocoins.info/ COinS]) community standard represents one way to embed OpenURLs in XHTML without including a resolver target. OpenURL also provides an XML encoding.

Example (from a book review written using the Structured Blogging plugin):

<pre><nowiki>
ISBN: 
0679426612
</nowiki></pre>

Another example, a journal this time:
<pre>
<nowiki>

</nowiki>
</pre>

As you can see this isn't very much like semantic XHTML at all. However significant work has gone into defining the set of Key/Encoded Values (KEVs) that can be used in various [http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=ListRecords&metadataPrefix=oai_dc&set=Core:Metadata+Formats types] of citations: [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:book book], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:dissertation dissertation], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:journal journal], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:patent patent]. It would be possible to simply provide a standard XHTML bundling for these keys as a microformat.

=== Example ===

<pre>
<nowiki>

<div class="openurl-journal">
Berners-Lee,
Tim</a>; Hendler, James; Lassila, Ora.
"The Semantic Web".
Scientific American
284(5), pp.
pp. 34-43.
0036-8733
</div>

</nowiki>
</pre>

Using OpenURL in this way would enable third party applications that could, say grab citation metadata from a blog, and without much work fire it off at your university's or public libraries openurl resolver to see if the article is available via a licensed databases. The benefits [http://www.infotoday.com/newsbreaks/nb050801-1.shtml have] [http://www.ariadne.ac.uk/issue43/chudnov/ been] [http://www.wallandbinkley.com/quaedam/?p=30 noted] [http://hublog.hubmed.org/archives/001163.html elsewhere].

== The OpenURL Briefly Explained ==

An OpenURL consists of two independent parts: the ContextObject (or the bibliographic metadata surrounding a citation) and the location of resolver to parse the metadata and present contextual services based on said metadata. The problem is that the term "OpenURL" is also used as a catch-all for all of the independent parts and how they work. This is mainly because it's a catchier term than "Z39.88", which is the [http://www.niso.org/standards/standard_detail.cfm?std_id=783 NISO standard all this is based upon].

The most common representation of the OpenURL ContextObject is seen as arguments in a URL string (which is referred to as "San Antonio Profile 1" -- more commonly SAP1 -- and is represented in Key Encoded Values -- KEVs). This "representation" is independent of the ContextObject (from here on known as CO) itself and is only intended to permit the CO to be transmitted via an HTTP GET request.

There is also SAP2, which is an XML representation of the CO (see: [http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadataPrefix=oai_dc&identifier=info:ofi/fmt:xml:xsd:ctx here] for more information) and is a much more human readable format. This still falls outside the scope of microformats, but makes the point that encoding has nothing to do with the CO itself. They are just agreed upon means of conveying the CO to enable machines act upon them consistently.

The ContextObject could be conveyed just as easily in XHTML using attributes, as long as the terms follow the vocabulary defined in the OpenURL framework. The important thing to focus on here is the ContextObject -- the address of the link resolver ''is'' institution-specific and should be handled by a user's (or machine's) activating agent.

However, the link resolver is still a very important component to this whole process. Getting users "appropriate copy" is a very real (and very difficult) problem that libraries are trying to solve. Link resolvers are a pretty efficient means of overcoming this hurdle, so it would make sense to mark up bibiographic citations in a way that link resolvers can easily parse.

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

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

== DocBook ==

A subset of the DocBook vocabulary is dedicated to representing a bibliography: http://www.docbook.org/tdg/en/html/bibliography.html

<pre><nowiki>
<!DOCTYPE bibliography PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
<bibliography>
<title>Languages and Semantics</title>
<bibliodiv>
<title>Books</title>
<biblioentry>
<title>Course in General Linguistics</title>
<abbrev>deSaussure59</abbrev>
<author><firstname>Ferdinand</firstname><surname>de Saussure</surname></author>
<editor><firstname>Charles</firstname><surname>Bally</surname></editor>
<editor><firstname>Albert</firstname><surname>Sechehaye</surname></editor>
<othercredit role="translator"><firstname>Wade</firstname><surname>Baskin</surname></othercredit>
<copyright>
<year>1959</year>
<holder>The Philosophical Library Inc.</holder>
</copyright>
<isbn>07-016524-6</isbn>
<publisher>
<publishername>McGraw-Hill Book Company</publishername>
</publisher>
</biblioentry>
</bibliodiv>
</bibliography>
</nowiki></pre>

* publisher
* copyright
* identifier (ISBN)
* title
* author/editor/other credit/
* type (book)

== Ann Arbor District Library XML feed ==

Here's a record in XML format from their project to simplify
access to the catalog. More discussion on [http://www.blyberg.net John Blyberg's blog].

<pre>
<nowiki>
<p:Record>
<callnum>823 Bu</callnum>
<author>Burkart, Gina, 1971-</author>
<fulltitle>A parent's guide to Harry Potter / Gina Burkart</fulltitle>
<title>A parent's guide to Harry Potter </title>
<pubinfo>Downers Grove, Ill. : InterVarsity Press, c2005</pubinfo>
<desc>112 p</desc>
<bibliography>Includes bibliographical references</bibliography>
<contents>
The Harry hype -- More than a story -- The modern fairy tale -- Discussing fantasy with children --
Morals, not magic -- The real issues in Harry Potter -- Dealing with traumatic experiences -- Facing
fears -- Battling bullies -- Delving into diversity -- Hiding hurts -- Letting go of anger -- Getting
help -- Choosing good over evil -- The power of love -- Facing spiritual battles
</contents>
<isbn>0830832882</isbn>
<price>$11.00</price>
<lang>eng</lang>
<copies>0</copies>
<catdate>08-16-2005</catdate>
<mattype>a</mattype>
<avail>No copies available</avail>
<recordlink xlink:href="http://www.aadl.org/cat/seek/record=1249810"/>
</p:Record>
</nowiki>
</pre>

* url
* availablity
* identifier (ISBN/call number)
* author
* title
* publisher
* pages
* description/contents

== SimpleDC supported by the zoom toolkit ==

<pre>
<nowiki>
<dc xmlns="http/www.loc.gov/zing/srw/dcschema/v1.0/">
<title>Kantor Salomon Sulzer und seine Zeit : eine Dokumentation /</title>
<creator>Avenary, Hanoch.</creator>
<creator>Pass, Walter.</creator>
<creator>Vielmetti, Nikolaus.</creator>
<creator>Adler, Israel, (1925-)</creator>
<subject>Sulzer, Salomon, -- 1804-1890.</subject>
<subject>Jewish composers -- Austria -- Biography.</subject>
<subject>Cantors, Jewish -- Biography.</subject>
<date>1985</date>
<publisher>Sigmaringen : Jan Thorbecke Verlag</publisher>
<identifier>3799540636</identifier>
<description>300 p., [12] p. of plates : ill., music, ports. ; 24 cm.</description>
</dc>
</nowiki>
</pre>

this is the output of marc.toSimpleDC()

* title
* creator (author)
* subjects
* date
* publisher
* identifier
* description

(NOTE: this schema is from the example, not the source schema)

== SRU from the Library of Congress ==

http://z3950.loc.gov:7090/voyager?version=1.1&operation=searchRetrieve&query=dinosaur&maximumRecords=1&recordSchema=dc

<pre>
<nowiki>
<?xml version="1.0"?>
<zs:searchRetrieveResponse xmlns:zs="http://www.loc.gov/zing/srw/">
<zs:version>1.1</zs:version>
<zs:numberOfRecords>1701</zs:numberOfRecords>
<zs:records>
<zs:record>
<zs:recordSchema>info:srw/schema/1/dc-v1.1</zs:recordSchema>
<zs:recordPacking>xml</zs:recordPacking>
<zs:recordData>
<srw_dc:dc xmlns:srw_dc="info:srw/schema/1/dc-schema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://purl.org/dc/elements/1.1/"
xsi:schemaLocation="info:srw/schema/1/dc-schema http://www.loc.gov/z3950/agency/zing/srw/dc-schema.xsd">
<title>3-D dinosaur adventure [computer file].</title>
<creator>Knowledge Adventure, Inc.</creator>
<type>software, multimedia</type>
<publisher>Glendale, CA : Knowledge Adventure,</publisher>

<date>c1995.</date>
<language>eng</language>
<description>Employs a dinosaur theme-park setting to introduce users to Triassic, Jurassic, and
Cretaceous periods. Features hypertext dinosaur encyclopedia covering 150 million years of
paleontology. Includes animated video simulations, three-dimensional dinosaur museum, narration,
games, activities, and color illustrations.</description>
<description>Ages 5 to 10.</description>
<description>System requirements for PC: 486SX/25MHz processor or higher; 8MB RAM; Windows 3.1,
3.11, or 95; SVGA 256-color graphics adapter; hard drive with 5MB free space; double-speed CD-ROM
drive; MPC-compatible sound card; mouse.</description>
<description>System requirements for Macintosh: 68040 or Power PC processor; 8MB RAM; System 7.0 or
higher; 256-color graphics capability; thirteen-inch color monitor or larger; hard drive with 4MB
free space; double-speed CD-ROM drive.</description>

<description>Ages 5 to 10.</description>
<description>Employs a dinosaur theme-park setting to introduce users to Triassic, Jurassic, and
Cretaceous periods. Features hypertext dinosaur encyclopedia covering 150 million years of paleontology.
Includes animated video simulations, three-dimensional dinosaur museum, narration, games, activities,
and color illustrations.</description>
<subject>Dinosaurs--Juvenile software.</subject>
<subject>Dinosaurs.</subject>
<identifier>URN:ISBN:1569972133</identifier>
</srw_dc:dc>
</zs:recordData>
<zs:recordPosition>1</zs:recordPosition>
</zs:record>
</zs:records>
</zs:searchRetrieveResponse>

</nowiki>
</pre>

NOTE: this is just Dublin Core data in a special LOC envelope

== University of Bath reference type ==
<pre>
<nowiki>
<reference>
<authors>
<author>
<forename>E</forename>
<forename>M</forename>
<surname>Phillips</surname>
</author>
<author>
<forename>D</forename>
<forename>S</forename>
<surname>Pugh</surname>
</author>
</authors>
<date>1994</date>
<entity>
<book title="How to get a PhD: A handbook for students and their supervisors">
<location>
<placeofpublication>Buckinghamshire</placeofpublication>
<publisher>Open University</publisher>
</location>
</book>
</entity>
</reference>

<reference>
<authors>
<author>
<forename>Michael</forename>
<surname>Fumento</surname>
</author>
</authors>
<date>1996</date>
<entity>
<website pagetitle="Radon's Real Threat is to the EPA"
uri="http://www.consumeralert.org/fumento/radon1.htm"/>
</entity>
<frdescription>an article by a prolific newspaper columnist in the USA -
quotes empirical scientific research showing no provable link between radon in homes and elevated
cases of lung cancer</frdescription>
</reference>
</nowiki>
</pre>
[http://www.bath.ac.uk/schemas/screenshots/referencetype.png Schema extract]

* author
* date
* url
* description
* type (book/journal/conference)
* title
* artile
* volume
* issue
* chapter
* pages
* publisher
** publisher data (address, city, ...)

== Implied Schema ==
This is the start of the short list of common properties across documented formats. Once this is finished, there will be a union of Implied schemas between EXAMPLES and IMPLEMENTATIONS and we will see what that looks like. (This currently only covers a few of the formats listed, some documented formats still need to be explored)

* creator (author, editor, translator, contributor) - this can be handled with hCard, but will need an additional property to refine what "creator" means
* publisher (this can also be handled with hCard)
* subject/topics/keywords/categories/genre (there is a rel="tag" microformat)
* Description (abstract, note, tableOfContents)
* typeOfResource/format

common location information
* volume
* issue
* page
* edition

Date Fields
* Date Published (some formats have YEAR/MONTH sperately)
* Date accessed (see [http://www.columbia.edu/cu/cup/cgos/basic.html here] for examples)

Again, I'll emphasize: "date published" is problematic. If one needs specificity, then better to have the following list of date classes: date (the generic), issued (braoder than published), copyright (often not the same as issuance date), accessed. -- bruce

Other fields
* Copyright/usage
* audience

* identifier (ISBN, ISSN, id, internal only, other)
* language (this can be handled by the xml:lang attribute native to HTML)

== Types and Roles ==
(Section is informative only as a place to capture various parts of publication citations.)

There are many different types of publications and this information should be captured in the citation. Possible types include:
* Novel/fiction (specify type -- literature, SF, romance, etc.?)
* Non-fiction
* Poem
* Play
* Magazine
* Reference (separate out encyclopedia, dictionary, almanac, etc.?)
* Journal
* Article within a journal
* Chapter within a book
* Dissertation
* Web Site
* Page within a web site
* Music Recording
* Video Recording
* Interview
* Physical object (Statue, Painting, etc.)
* ??

Question:
Certain works have specific types of citations, for example, the Bible--and, I assume, other religious works--have very specific citation formats with different relevant information (chapter/verse) than others, as do the works of Shakespeare. Should these be considered separate types/roles?

A: I think in terms of types, we should at least note the items (chapter, verse, etc). How they get dealt with is still way up in the air. - [[User:Tim White|Tim White]]

Likewise, there are several different roles associated with publications -- author, co-author, editor, translator, etc. Should these be captured under a master "role" or treated as individual elements?

A: Good question. I think there is an important distinction, but whether we follow a design pattern of "role-*" (or more likely "author-*) or some other pattern hasn't been discussed yet. - Tim

== Biblio RDF Class Schema ==
Regading the issue of types notes above, the [http://vocab.org/biblio/schema biblio schema] provides a comprehensive set of classes to describe citation metadata. It might prove useful as a guide for a micro-format. The primary classes are Agent, Reference, Collection, and Event. An "Article", then, would be a subclass of "Part", which in turn is a subclass of Reference. Likewise, a "Journal" is a subclass of a "Periodical," which in turn is a subclass of "Collection." An article would typically be linked to a journal through a dcterms:isPartOf relation.

== ISBN:// Protocol ==

[http://www.faqs.org/rfcs/rfc3187.html RFC3187] defines an isbn protocol

Example:

URN:ISBN:0-395-36341-1

I'm not sure if any browser uses this data, but it might be have an application in citations describing registered materials with an ISBN

== You should know ==
* There are more then 1.300 citation ''styles'' in EndNote 9.
* Libraries have developed formats and rules for publications since more than 100 years. There are millions of records in library catalougues. You should '''at least''' be familiar with AACR and FRBR. There '''already are''' effords to create a new "microformat" called ''Resource Description and Access'' (RDA) [http://www.collectionscanada.ca/jsc/rdaprospectus.html]. Why don't you try to work with the professionals instead of amateurishly trying to reinvent the wheel and create yet another incompatible format? -- [[User:JakobVoss|JakobVoss]] 01:39, 5 Jun 2006 (PDT)
** I agree that the people involved in developing this microformat (including me) ought to be aware of these efforts (in particular FRBR), but I also think your argument is hopelessly naive and pretentious. The professionals you refer to are in fact library professionals, with their own bizarre traditios and unique information needs. Those are different than the professional scholars for whom citations are critical (me), or to the professional web developers who might want to implement these formats. What I do think is important is for us to understand the different design traditions, and their trade-offs, rather than to blindly create a microformat based on one of them -- Bruce (author of citeproc [http://xbiblio.sourceforge.net/citeproc] and csl [http://xbiblio.sourceforge.net/csl]).

Nice to meet you, Bruce! Maybe I'm naive but it still think that there is a way to combine the best of both worlds: scholars and library professionals. Both have developed bizarre traditions and it would be a pitty to create a new bizarre microformat that is not based on both of them. Thanks to your links to xbiblio. I a stumbled upon it a while ago but have to look at it deeper. -- [[User:JakobVoss|JakobVoss]] 11:48, 19 Jul 2006 (PDT)

citation-examples

2006-06-05T09:42:43Z

JakobVoss: /* Wikipedia */ there is more than English!

<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]]
* [[citation-faq]]

__TOC__

== Contributors ==
* ...
* [http://suda.co.uk/ Brian Suda]
* Tantek Çelik
* [http://michael-mccracken.net/wp/ Michael McCracken]
* Tim White
* [http://inkdroid.org Ed Summers]

== 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] ===
[http://microformats.org/wiki/citation-examples-markup#ABC-CLIO_Product_detail_page.C2.A0.28http:.2F.2Fwww.abc-clio.com.2Fproducts.2Foverview.aspx.3Fproductid.3D109327.29 Original Markup]
* title
* subtitle
* author
* image
* publication date
* pages
* volumes
* specifications (book dimentions 8.5x11, weight, etc)
* Format - (Hardback, softback)
* Price
* ISBN

=== Greenwood Press [http://www.greenwood.com/ home page] featured book ===
[http://microformats.org/wiki/citation-examples-markup#Greenwood_Press_home_page.C2.A0.28http:.2F.2Fwww.greenwood.com.2F.29_featured_book Original Markup]
* title
* subtitle
* author
* ISBN
* Price
* Description

=== Greenwood Press [http://www.greenwood.com/catalog/GR2847.aspx Product detail page] ===
[http://microformats.org/wiki/citation-examples-markup#Greenwood_Press_Product_detail_page.C2.A0.28http:.2F.2Fwww.greenwood.com.2Fcatalog.2FGR2847.aspx.29 Original Markup]

* Title
* subtitle
* authors
* AuthorsNote
* BookCode (internal code system)
* ISBN
* Page
* Publisher
* Publication Date
* Price
* Availability
* MediaType
* categories
* LC Card Number
* LCC Class
* Dewey Class

=== Marshall Cavendish [http://www.marshallcavendish.com/marshallcavendish/academic/redirector.xml?url=/marshallcavendish/academic/catalogue/books/regionalism_n_regional_security/9812102108.xml product page] ===
[http://microformats.org/wiki/citation-examples-markup#Marshall_Cavendish_product_page.C2.A0.28http:.2F.2Fwww.marshallcavendish.com.2Fmarshallcavendish.2Facademic.2Fredirector.xml.3Furl.3D.2Fmarshallcavendish.2Facademic.2Fcatalogue.2Fbooks.2Fregionalism_n_regional_security.2F9812102108.xml.29 Original Markup]

* ISBN
* Series
* Title
* publisher
* Specifications (dimentions/weight)
* Authors
* Target Audience
* Price
* description

=== Oxford University Press (USA) [http://www.us.oup.com/us/?view=usa homepage] ===
[http://microformats.org/wiki/citation-examples-markup#Oxford_University_Press_.28USA.29_homepage.C2.A0.28http:.2F.2Fwww.us.oup.com.2Fus.2F.3Fview.3Dusa.29 Original Markup]

* title
* subTitle
* edition
* byline
* ISBN
* format - hardback
* publication Date
* price
* description
* related

=== Oxford University Press (USA) [http://www.us.oup.com/us/catalog/general/subject/HistoryAmerican/ColonialRevolutionary/?view=usa&ci=0195162471#Product_Details Product page]===
[http://microformats.org/wiki/citation-examples-markup#Oxford_University_Press_.28USA.29_Product_page.C2.A0.28http:.2F.2Fwww.us.oup.com.2Fus.2Fcatalog.2Fgeneral.2Fsubject.2FHistoryAmerican.2FColonialRevolutionary.2F.3Fview.3Dusa.26ci.3D0195162471.23Product_Details.29 Original Markup]

* title
* subTitle
* edition
* byline
* image
* isbnNumber
* format - hardback
* pages
* publication Date
* availability
* price

=== Thomson Gale product detail page ===
[http://microformats.org/wiki/citation-examples-markup#Thomson_Gale_product_detail_page Original Markup]

* title
* excerp
* Volume
* Publisher
* description
* Published date
* ISBN
* Product number (internal code system)
* Pages
* Shipping Weight
* price

== RFC vCard Example ==
[http://microformats.org/wiki/citation-examples-markup#RFC_vCard_Example Original Markup]

* refID (HTML @ID)
* title
* publication
* title
* Journal
* Volume
* Issue
* page
* pubdate
* RFC ID

== W3C XHTML Spec Example ==
[http://microformats.org/wiki/citation-examples-markup#W3C_XHTML_Spec_Example Original Markup]

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

[http://www.w3.org/TR/xhtml1/#refs XHTML1.0 Spec references]

== CiteProc XHTML Output ==
[http://microformats.org/wiki/citation-examples-markup#CiteProc_XHTML_Output Original Markup]

The XHTML output for CiteProc[http://xbiblio.sourceforge.net/citeproc/] 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 (HTML @ID)
* creator
* role (to indicate editors and translators)
* date
* title
* volume
* issue
* page
* issue
* container (a book serves as container for a chapter)
* type (book, newspaper, proceedings)
* edition
* publisher
* place
* location (for urls and physical locations)
* access date (for online items)

== ACM Digital Library Search Result Examples ==

The [http://www.acm.org/dl/ ACM Digital Library] is a heavily used computer science literature database.
[http://microformats.org/wiki/citation-examples-markup#ACM_Digital_Library_Search_Result_Examples Original Markup]

* title
* authors
* Pages
* format (PDF)
* Additional Information
* abstract
* index terms
* journal
* issue
* volume
* pubdate
* DOI

== IEEE IEEExplore Search Results Markup ==
[http://microformats.org/wiki/citation-examples-markup#IEEE_IEEExplore_Search_Results_Markup Original Markup]

* title
* authors
* journal
* issue
* volume
* issue
* pubdate
* page
* Digital Object Identifier (DOI)
* summary

== 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:
[http://microformats.org/wiki/citation-examples-markup#CiteSeer_database_search_results Original Markup]

* author
* title
* journal
* pages
* publication date
* URL

== CiteULike.org citation listing ==

[http://www.citeulike.org/ CiteULike]
[http://microformats.org/wiki/citation-examples-markup#CiteULike.org_citation_listing Original Markup]

* title
* author
* subjects
* image
* Volume
* Number
* publication date
* 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.
[http://microformats.org/wiki/citation-examples-markup#Amazon.com_citation_info Original Markup]

* title
* author
* series title
* page

== PubMed Medical Journal Example ==
[http://microformats.org/wiki/citation-examples-markup#PubMed_Medical_Journal_Example Original Markup]

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

== Wikipedia ==
[http://wikpedia.org Wikipedia] makes extensive use of bibliographic citations, in particular to point readers to further information sources. There are differing formats depending on Wikipedia's language:

=== English Wikipdia ===
The kinds of citations used on the site run the full gamut; from [http://en.wikipedia.org/wiki/DNA#Citations scientific articles] published in journals, to [http://en.wikipedia.org/wiki/List_of_leading_legal_cases_in_copyright_law legal cases], to [http://en.wikipedia.org/wiki/Weblog#References conference presentations], to [http://en.wikipedia.org/wiki/American_Civil_War#Primary_sources primary historical sources].

=== German Wikipedia ===
* [http://de.wikipedia.org/wiki/Wikipedia:Literatur citing styles]

== Self-Citation Example ==
[http://cbio.mskcc.org/~hoffmann/lifecycles/olv/index.html One example] of an article that includes a statement "please cite as" (a self-description):

* title
* author
* periodical (journal) title
* volume
* issue
* pages
* year

== Citation of an Online Resource ==
At University of Michigan's [http://www.crlt.umich.edu/publinks/facment_biblio.html Center for Research on Learning and Teaching] you see citations like this:

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.

* title
* publication year
* department/author
* retrieval date
* URL

== Implied schema ==

=== List of all properties ===
This are a summation of all the properties in the examples, I have tried to logically group them together.

* title
* subtitle
* author
* editor
* translator
* image
* date (issued, copyrighted, accessed)
* language
* description/Summary/abstract
* excerpt
* index terms
* categories (keywords, tags, labels, etc.)

RELATIONS
* container (publication; periodicals, books, etc.)
* collection (series and so forth)
* event (conference, etc.)
* original (for republished material)

LOCATION INFORMATION
* pages
* volume
* series title
* Series
* edition
* issue
* publication
* journal
* part (1 of X)

PHYSICAL ATTRIBUTES
* Specifications (dimentions/weight)
* Format/type (book, newspaper, proceedings)

IDENTIFIERS
* ISBN
* LC Card Number
* LCC Class
* Dewey Class
* URL
* RFC ID
* ISO/IEC ID
* DOI
* PubMedID

PUBLISHER
* publisher

These are sort of left overs, the are not really about citations, but more about commerce or other things. If they are important we can move them to the above list.
* refID (HTML @ID)
* Reviewed (BOOLEAN YES/NO)
* Availability
* Price
* Shipping Weight
* related
* Product number (internal system code)
* BookCode (internal system code)
* AuthorsNote
* Additional Information
* Target Audience

=== Analysis of Examples ===
With exception of just a few properties, all of the above appeared in atleast two different examples. The following properties were very common in most the example formats:
* title
* subtitle
* author
* publication date
* description
* pages
* ISBN
* publisher

== 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.english.uiuc.edu/cws/wworkshop/writer_resources/citation_styles/citation_styles.htm Writer's Workshop citation style page] (detailed citation style info)
* [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

User:JakobVoss

2006-06-05T08:40:55Z

JakobVoss: about me

I studied computer science and library and information science, and I'm very active in the German Wikipedia (see [http://de.wikipedia.org/wiki/Benutzer:JakobVoss my user page]).

citation-formats

2006-06-05T08:39:16Z

JakobVoss: /* ISBN:// Protocol */ You should know

= Citation Formats =

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

See also:
* [[citation]]
* [[citation-brainstorming]]
* [[citation-examples]]
* [[citation-faq]]

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

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

<table border="1">
<tr>
<th>Dublin Core</th>
<th>MODS</th>
<th>bibTeX</th>
<th>Z39.80</th>
</tr>
<tr>
<td>Title (alternative)</td>
<td>titleInfo/title titleInfo/PartNum</td>
<td>booktitle title chapter number pages volume series</td>
<td>Analytic Title 
Collective or Series Title 
Monographic Title 
Work Fraction Title 
Location of Conference 
Main Entry 
Name of Conference 
Number of Meeting 
Other Title 
Parallel Title 
Title Abbriviation 
Title of Conference Proceedings 
Translated Title 
Uniform Title 
Abbriviated Translated Title 
Symposium or Session Title 
Collective or Series Edition 
Video/Film Edition 
</td>
</tr>
<tr>
<td>creator</td>
<td>name/namePart</td>
<td>author creator</td>
<td>Author, Primary 
Corporate Author, Primary 
Abstract Author 
Authorship Statement 
Acknowledged Supporters 
Assignee for Patents 
Chairperson of Conference 
Director of AV Program 
Other Author 
Reviewed Book Author 
Studio 
Sponsor of Conference 
Staff/Cast 
Symposium Chairperson 
Author Address or Affiliation 
Author Country 
Electronic Address of Author 
</td>
</tr>
<tr>
<td>subject</td>
<td>subject/topic</td>
<td>keywords</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Description (abstract | tableOfContents)</td>
<td>abstract note tableOfContents</td>
<td>abstract annotation note contents</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Contributor</td>
<td>name</td>
<td>editor?</td>
<td>Book/Report/Volume Editor 
Producer 
Translator 
</td>
</tr>
<tr>
<td>Date (available | created | dateAccepted | dateCopyrighted | dateSubmitted | issued | modified | valid)</td>
<td>originInfo/dateIssued originInfo/dateCreated originInfo/dateCaptured originInfo/dateOther</td>
<td>month year</td>
<td>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</td>
</tr>
<tr>
<td>Type</td>
<td>typeOfResource genre</td>
<td>@class type</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Format (extent | medium)</td>
<td>physicalDescription/internetMediaType physicalDescription/extent physicalDescription/form</td>
<td>howpublished</td>
<td>needs mapping</td>
</tr>
<tr>
<td>identifier (bibliographicCitation)</td>
<td>identifier</td>
<td>ISBN ISSN LCCN URL</td>
<td>ISBN Identifier Report Identfier ISSN</td>
</tr>
<tr>
<td>Source</td>
<td>relatedItem</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td>language</td>
<td>language</td>
<td>language</td>
<td bgcolor="#cccccc"></td>
</tr>
<tr>
<td>Relation (...)</td>
<td>relatedItem/...</td>
<td>crossRef</td>
<td>needs mapping</td>
</tr>
<tr>
<td>Coverage (spacial | temporal)</td>
<td>subject/temporal subject/geographic subject/hierarchicalGeographic subject/cartographics</td>
<td></td>
<td>needs mapping</td>
</tr>
<tr>
<td bgcolor="#cccccc"></td>
<td>classifications</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td>Rights (accessRights | license)</td>
<td>accessConditions</td>
<td>copyright</td>
<td>needs mapping</td>
</tr>
<tr>
<td>publisher</td>
<td bgcolor="#cccccc"></td>
<td>publisher</td>
<td>Publisher Name 
Place of Publication 
Country of Publication 
Generic Address 
</td>
</tr>
<tr>
<td>audience (educationLevel | mediator)</td>
<td>targetAudience</td>
<td bgcolor="#cccccc"></td>
<td>needs mapping</td>
</tr>
<tr>
<td bgcolor="#999999">accualMethod accualPeriodicaty accualPolicy instrcutionalMethod provenance rightsHolder</td>
<td bgcolor="#999999">location extension recordInfo</td>
<td bgcolor="#999999">address afflilication location edition institution journal key mrnumber organization price school size</td>
<td bgcolor="#999999">(the following need to be mapped to the above rows or left here as other) 
Database Source 
Databse Record Identifier 
Database Producer Name 
Rights Management 
Subfile 
Other Source Identifier 
Vendor Record Identifier 
Database Vendor Name 
Column Number 
Edition 
Frequency of Publication 
Internet Location for Document 
Supplement/Part/Special number identifer 
Issue Identifier 
Location in Work 
Number of the Chapter 
Number in Series 
Volume Identifier 
Section Indentifier 
</td>
</tr>
</table>

== Dublin Core Metadata ==
[http://dublincore.org/ Dublin Core] metadata uses a small vocabulary to descibe the data.
* contributor
* coverage
* creator
* date
* description
* format
* identifier
* language
* publisher
* relation
* rights
* source
* subject
* title
* type

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

* abstract refines description.
* accessRights refines rights

[http://dublincore.org/documents/dc-citation-guidelines/ Guidelines for Encoding Bibliographic Citation Information in Dublin Core Metadata]

== MODS (Metadata Object Description Schema) ==
This is a format developed for the Libray of Congress for a bibliographic element set that may be used for a variety of purposes, and particularly for library applications.

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

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

== NLM Journal Publishing DTD ==

[http://dtd.nlm.nih.gov/publishing/tag-library/2.1/n-fv30.html http://dtd.nlm.nih.gov/publishing/tag-library/2.1/n-fv30.html]

The [http://dtd.nlm.nih.gov/publishing/tag-library/ NLM Journal Publishing DTD] defines the schema used for publishing journal articles as XML. The <pre><citation></pre> element can be placed with paragraphs or within a <pre><ref-list></pre> element at the end of the article.

"Although the DTD does not enforce it, a citation to a journal article should be tagged with as many as possible of the following, so that PubMed Central, CrossRef, or other matching service can make the citation into a live link:

<table border="1">
<tr><td>source</td><td>The title of a journal, book, conference proceedings, etc. that is the source of the cited material. (Note: In PubMed Central processing, this is typically the MEDLINE abbreviation of the journal name.)</td></tr>
<tr><td>article-title</td><td>Title of the article</td></tr>
<tr><td>volume</td><td>Volume of the journal</td></tr>
<tr><td>issue</td><td>Issue of the journal</td></tr>
<tr><td>fpage</td><td>Page number on which the article starts</td></tr>
<tr><td>name</td><td>Name of an author or editor</td></tr>
<tr><td>year</td><td>Year of publication</td></tr>
<tr><td>month</td><td>Month of publication (if present)</td></tr>
<tr><td>day</td><td>Date of publication (if present)</td></tr>
</table>

The other elements (described [http://dtd.nlm.nih.gov/publishing/tag-library/2.1/n-fv30.html here]) may be tagged if desired. Use the <source> element for titles of books, conference proceedings, etc."

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

* author
* publication date
* publisher
* pages
* title (article/book)
* url

== BibTeX ==
=== Fields Used by Bibtex ===

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

=== BibTeX citation Types ===
A reference can be to any of a variety of types. Following is a list of types. Each one also explains the fields associated with that type. Any fields not listed as required or optional are considered to be ignored.
<table border="1" width="100%">
<tr>
<td>article:</td>
<td>An article from a journal or magazine. Required fields: author, title, journal, year. Optional fields: volume, number, pages, month, note, key.</td>
</tr>
<tr>
<td>book:</td>
<td>A book with an explicit publisher. Required fields: author or editor, title, publisher, year. Optional fields: volume, series, address, edition, month, note, key.</td>
</tr>
<tr>
<td>booklet: </td>
<td>A work that is printed and bound, but without a named publisher or sponsoring institution. Required fields: title. Optional fields: author, howpublished, address, month, year, note, key.</td>
</tr>
<tr>
<td>collection:</td>
<td>A collection of works. Same as Proceedings.</td>
</tr>
<tr>
<td>conference:</td>
<td>The same as Inproceedings.</td>
</tr>
<tr>
<td>inbook:</td>
<td>A part of a book, which may be a chapter and/or arange of pages. Required fields: author or editor, title, chapter and/or pages, publisher, year. Optional fields: volumer, series, address, edition, month, note, key.</td>
</tr>
<tr>
<td>incollection:</td>
<td>A part of a book with its own title. Required fields: author, title, booktitle, publisher, year. Optional fields: editor, pages, organization, publisher, address, month, note, key.</td>
</tr>
<tr>
<td>inproceedings:</td>
<td>An article in a conference proceedings. Required fields: author, title, booktitle, year. Optional fields: editor, pages, organization, publisher, address, month, note, key.</td>
</tr>
<tr>
<td>manual: </td>
<td>Technical documentation. Required fields: title. Optional fields: author, organization, address, edition, month, year, note.</td>
</tr>
<tr>
<td>mastersthesis:</td>
<td>A Master's thesis. Required fields: author, title, school, year. Optional fields: address, month, note, key.</td>
</tr>
<tr>
<td>misc:</td>
<td>Use this type when nothing else fits. Required fields: none. Optional fields: author, title, howpublished, month, year, note, key.</td>
</tr>
<tr>
<td>patent:</td>
<td>A patent.</td>
</tr>
<tr>
<td>phdthesis:</td>
<td>A Ph.D. thesis. Required fields: author, title, school, year. Optional fields: address, month, note, key.</td>
</tr>
<tr>
<td>proceedings:</td>
<td>The proceedings of a conference. Required fields: title, year. Optional fields: editor, publisher, organization, address, month, note, key.</td>
</tr>
<tr>
<td>techreport:</td>
<td>A report published by a school or other institution, usually numbered within a series. Required fields: author, title, institution, year. Optional fields: type, number, address, month, note, key.</td>
</tr>
<tr>
<td>unpublished:</td>
<td>A document with an author and title, but not formally published. Required fields: author, title, note. Optional fields: month, year, key.</td>
</tr>
</table>

==== Examples ====
<pre><nowiki>
@book{kn:gnus,

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

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

@article{XAi_HSCheng_1994a,

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

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

== RIS ==

RIS is similar to BibTeX and is handled by most desktop and web-based bibliography management software.

The specification and field types/tags are described at [http://www.refman.com/support/risformat_intro.asp http://www.refman.com/support/risformat_intro.asp]

In particular, see [http://www.refman.com/support/risformat_reftypes.asp the list of different reference types].

A sample item in RIS format:
<pre>
TY - JOUR
A1 - Baldwin,S.A.
A1 - Fugaccia,I.
A1 - Brown,D.R.
A1 - Brown,L.V.
A1 - Scheff,S.W.
T1 - Blood-brain barrier breach following
cortical contusion in the rat
JO - J.Neurosurg.
Y1 - 1996
VL - 85
SP - 476
EP - 481
RP - Not In File
KW - cortical contusion
KW - blood-brain barrier
KW - horseradish peroxidase
KW - head trauma
KW - hippocampus
KW - rat
ER -
</pre>

[http://www-static.cc.gatech.edu/classes/RWL/Projects/citation/Applet/OnlineHelp/refer_doc.html Refer] is a similar, smaller bibliographic format.

* author
* title
* type
* Identifier
* notes/abstract
* reprint status
* keyword
* volume
* issue
* pages
* year
* periodical name (where published)
* publisher
** publisher city
** publisher address
* related links
* link to PDF
* availablity

== OpenURL ==

OpenURL aka [http://www.niso.org/standards/standard_detail.cfm?std_id=783 Z39.88] defines a standard way of bundling citation data in a URL. It is widely deployed in academic libraries around the world to provide access to licensed content via link resolvers such as [http://www.exlibrisgroup.com/sfx_openurl.htm SFX]. The Context Object in Span ([http://ocoins.info/ COinS]) community standard represents one way to embed OpenURLs in XHTML without including a resolver target. OpenURL also provides an XML encoding.

Example (from a book review written using the Structured Blogging plugin):

<pre><nowiki>
ISBN: 
0679426612
</nowiki></pre>

Another example, a journal this time:
<pre>
<nowiki>

</nowiki>
</pre>

As you can see this isn't very much like semantic XHTML at all. However significant work has gone into defining the set of Key/Encoded Values (KEVs) that can be used in various [http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=ListRecords&metadataPrefix=oai_dc&set=Core:Metadata+Formats types] of citations: [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:book book], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:dissertation dissertation], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:journal journal], [http://www.openurl.info/registry/docs/mtx/info:ofi/fmt:kev:mtx:patent patent]. It would be possible to simply provide a standard XHTML bundling for these keys as a microformat.

=== Example ===

<pre>
<nowiki>

<div class="openurl-journal">
Berners-Lee,
Tim</a>; Hendler, James; Lassila, Ora.
"The Semantic Web".
Scientific American
284(5), pp.
pp. 34-43.
0036-8733
</div>

</nowiki>
</pre>

Using OpenURL in this way would enable third party applications that could, say grab citation metadata from a blog, and without much work fire it off at your university's or public libraries openurl resolver to see if the article is available via a licensed databases. The benefits [http://www.infotoday.com/newsbreaks/nb050801-1.shtml have] [http://www.ariadne.ac.uk/issue43/chudnov/ been] [http://www.wallandbinkley.com/quaedam/?p=30 noted] [http://hublog.hubmed.org/archives/001163.html elsewhere].

== The OpenURL Briefly Explained ==

An OpenURL consists of two independent parts: the ContextObject (or the bibliographic metadata surrounding a citation) and the location of resolver to parse the metadata and present contextual services based on said metadata. The problem is that the term "OpenURL" is also used as a catch-all for all of the independent parts and how they work. This is mainly because it's a catchier term than "Z39.88", which is the [http://www.niso.org/standards/standard_detail.cfm?std_id=783 NISO standard all this is based upon].

The most common representation of the OpenURL ContextObject is seen as arguments in a URL string (which is referred to as "San Antonio Profile 1" -- more commonly SAP1 -- and is represented in Key Encoded Values -- KEVs). This "representation" is independent of the ContextObject (from here on known as CO) itself and is only intended to permit the CO to be transmitted via an HTTP GET request.

There is also SAP2, which is an XML representation of the CO (see: [http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadataPrefix=oai_dc&identifier=info:ofi/fmt:xml:xsd:ctx here] for more information) and is a much more human readable format. This still falls outside the scope of microformats, but makes the point that encoding has nothing to do with the CO itself. They are just agreed upon means of conveying the CO to enable machines act upon them consistently.

The ContextObject could be conveyed just as easily in XHTML using attributes, as long as the terms follow the vocabulary defined in the OpenURL framework. The important thing to focus on here is the ContextObject -- the address of the link resolver ''is'' institution-specific and should be handled by a user's (or machine's) activating agent.

However, the link resolver is still a very important component to this whole process. Getting users "appropriate copy" is a very real (and very difficult) problem that libraries are trying to solve. Link resolvers are a pretty efficient means of overcoming this hurdle, so it would make sense to mark up bibiographic citations in a way that link resolvers can easily parse.

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

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

== DocBook ==

A subset of the DocBook vocabulary is dedicated to representing a bibliography: http://www.docbook.org/tdg/en/html/bibliography.html

<pre><nowiki>
<!DOCTYPE bibliography PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
<bibliography>
<title>Languages and Semantics</title>
<bibliodiv>
<title>Books</title>
<biblioentry>
<title>Course in General Linguistics</title>
<abbrev>deSaussure59</abbrev>
<author><firstname>Ferdinand</firstname><surname>de Saussure</surname></author>
<editor><firstname>Charles</firstname><surname>Bally</surname></editor>
<editor><firstname>Albert</firstname><surname>Sechehaye</surname></editor>
<othercredit role="translator"><firstname>Wade</firstname><surname>Baskin</surname></othercredit>
<copyright>
<year>1959</year>
<holder>The Philosophical Library Inc.</holder>
</copyright>
<isbn>07-016524-6</isbn>
<publisher>
<publishername>McGraw-Hill Book Company</publishername>
</publisher>
</biblioentry>
</bibliodiv>
</bibliography>
</nowiki></pre>

* publisher
* copyright
* identifier (ISBN)
* title
* author/editor/other credit/
* type (book)

== Ann Arbor District Library XML feed ==

Here's a record in XML format from their project to simplify
access to the catalog. More discussion on [http://www.blyberg.net John Blyberg's blog].

<pre>
<nowiki>
<p:Record>
<callnum>823 Bu</callnum>
<author>Burkart, Gina, 1971-</author>
<fulltitle>A parent's guide to Harry Potter / Gina Burkart</fulltitle>
<title>A parent's guide to Harry Potter </title>
<pubinfo>Downers Grove, Ill. : InterVarsity Press, c2005</pubinfo>
<desc>112 p</desc>
<bibliography>Includes bibliographical references</bibliography>
<contents>
The Harry hype -- More than a story -- The modern fairy tale -- Discussing fantasy with children --
Morals, not magic -- The real issues in Harry Potter -- Dealing with traumatic experiences -- Facing
fears -- Battling bullies -- Delving into diversity -- Hiding hurts -- Letting go of anger -- Getting
help -- Choosing good over evil -- The power of love -- Facing spiritual battles
</contents>
<isbn>0830832882</isbn>
<price>$11.00</price>
<lang>eng</lang>
<copies>0</copies>
<catdate>08-16-2005</catdate>
<mattype>a</mattype>
<avail>No copies available</avail>
<recordlink xlink:href="http://www.aadl.org/cat/seek/record=1249810"/>
</p:Record>
</nowiki>
</pre>

* url
* availablity
* identifier (ISBN/call number)
* author
* title
* publisher
* pages
* description/contents

== SimpleDC supported by the zoom toolkit ==

<pre>
<nowiki>
<dc xmlns="http/www.loc.gov/zing/srw/dcschema/v1.0/">
<title>Kantor Salomon Sulzer und seine Zeit : eine Dokumentation /</title>
<creator>Avenary, Hanoch.</creator>
<creator>Pass, Walter.</creator>
<creator>Vielmetti, Nikolaus.</creator>
<creator>Adler, Israel, (1925-)</creator>
<subject>Sulzer, Salomon, -- 1804-1890.</subject>
<subject>Jewish composers -- Austria -- Biography.</subject>
<subject>Cantors, Jewish -- Biography.</subject>
<date>1985</date>
<publisher>Sigmaringen : Jan Thorbecke Verlag</publisher>
<identifier>3799540636</identifier>
<description>300 p., [12] p. of plates : ill., music, ports. ; 24 cm.</description>
</dc>
</nowiki>
</pre>

this is the output of marc.toSimpleDC()

* title
* creator (author)
* subjects
* date
* publisher
* identifier
* description

(NOTE: this schema is from the example, not the source schema)

== SRU from the Library of Congress ==

http://z3950.loc.gov:7090/voyager?version=1.1&operation=searchRetrieve&query=dinosaur&maximumRecords=1&recordSchema=dc

<pre>
<nowiki>
<?xml version="1.0"?>
<zs:searchRetrieveResponse xmlns:zs="http://www.loc.gov/zing/srw/">
<zs:version>1.1</zs:version>
<zs:numberOfRecords>1701</zs:numberOfRecords>
<zs:records>
<zs:record>
<zs:recordSchema>info:srw/schema/1/dc-v1.1</zs:recordSchema>
<zs:recordPacking>xml</zs:recordPacking>
<zs:recordData>
<srw_dc:dc xmlns:srw_dc="info:srw/schema/1/dc-schema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://purl.org/dc/elements/1.1/"
xsi:schemaLocation="info:srw/schema/1/dc-schema http://www.loc.gov/z3950/agency/zing/srw/dc-schema.xsd">
<title>3-D dinosaur adventure [computer file].</title>
<creator>Knowledge Adventure, Inc.</creator>
<type>software, multimedia</type>
<publisher>Glendale, CA : Knowledge Adventure,</publisher>

<date>c1995.</date>
<language>eng</language>
<description>Employs a dinosaur theme-park setting to introduce users to Triassic, Jurassic, and
Cretaceous periods. Features hypertext dinosaur encyclopedia covering 150 million years of
paleontology. Includes animated video simulations, three-dimensional dinosaur museum, narration,
games, activities, and color illustrations.</description>
<description>Ages 5 to 10.</description>
<description>System requirements for PC: 486SX/25MHz processor or higher; 8MB RAM; Windows 3.1,
3.11, or 95; SVGA 256-color graphics adapter; hard drive with 5MB free space; double-speed CD-ROM
drive; MPC-compatible sound card; mouse.</description>
<description>System requirements for Macintosh: 68040 or Power PC processor; 8MB RAM; System 7.0 or
higher; 256-color graphics capability; thirteen-inch color monitor or larger; hard drive with 4MB
free space; double-speed CD-ROM drive.</description>

<description>Ages 5 to 10.</description>
<description>Employs a dinosaur theme-park setting to introduce users to Triassic, Jurassic, and
Cretaceous periods. Features hypertext dinosaur encyclopedia covering 150 million years of paleontology.
Includes animated video simulations, three-dimensional dinosaur museum, narration, games, activities,
and color illustrations.</description>
<subject>Dinosaurs--Juvenile software.</subject>
<subject>Dinosaurs.</subject>
<identifier>URN:ISBN:1569972133</identifier>
</srw_dc:dc>
</zs:recordData>
<zs:recordPosition>1</zs:recordPosition>
</zs:record>
</zs:records>
</zs:searchRetrieveResponse>

</nowiki>
</pre>

NOTE: this is just Dublin Core data in a special LOC envelope

== University of Bath reference type ==
<pre>
<nowiki>
<reference>
<authors>
<author>
<forename>E</forename>
<forename>M</forename>
<surname>Phillips</surname>
</author>
<author>
<forename>D</forename>
<forename>S</forename>
<surname>Pugh</surname>
</author>
</authors>
<date>1994</date>
<entity>
<book title="How to get a PhD: A handbook for students and their supervisors">
<location>
<placeofpublication>Buckinghamshire</placeofpublication>
<publisher>Open University</publisher>
</location>
</book>
</entity>
</reference>

<reference>
<authors>
<author>
<forename>Michael</forename>
<surname>Fumento</surname>
</author>
</authors>
<date>1996</date>
<entity>
<website pagetitle="Radon's Real Threat is to the EPA"
uri="http://www.consumeralert.org/fumento/radon1.htm"/>
</entity>
<frdescription>an article by a prolific newspaper columnist in the USA -
quotes empirical scientific research showing no provable link between radon in homes and elevated
cases of lung cancer</frdescription>
</reference>
</nowiki>
</pre>
[http://www.bath.ac.uk/schemas/screenshots/referencetype.png Schema extract]

* author
* date
* url
* description
* type (book/journal/conference)
* title
* artile
* volume
* issue
* chapter
* pages
* publisher
** publisher data (address, city, ...)

== Implied Schema ==
This is the start of the short list of common properties across documented formats. Once this is finished, there will be a union of Implied schemas between EXAMPLES and IMPLEMENTATIONS and we will see what that looks like. (This currently only covers a few of the formats listed, some documented formats still need to be explored)

* creator (author, editor, translator, contributor) - this can be handled with hCard, but will need an additional property to refine what "creator" means
* publisher (this can also be handled with hCard)
* subject/topics/keywords/categories/genre (there is a rel="tag" microformat)
* Description (abstract, note, tableOfContents)
* typeOfResource/format

common location information
* volume
* issue
* page
* edition

Date Fields
* Date Published (some formats have YEAR/MONTH sperately)
* Date accessed (see [http://www.columbia.edu/cu/cup/cgos/basic.html here] for examples)

Again, I'll emphasize: "date published" is problematic. If one needs specificity, then better to have the following list of date classes: date (the generic), issued (braoder than published), copyright (often not the same as issuance date), accessed. -- bruce

Other fields
* Copyright/usage
* audience

* identifier (ISBN, ISSN, id, internal only, other)
* language (this can be handled by the xml:lang attribute native to HTML)

== Types and Roles ==
(Section is informative only as a place to capture various parts of publication citations.)

There are many different types of publications and this information should be captured in the citation. Possible types include:
* Novel/fiction (specify type -- literature, SF, romance, etc.?)
* Non-fiction
* Poem
* Play
* Magazine
* Reference (separate out encyclopedia, dictionary, almanac, etc.?)
* Journal
* Article within a journal
* Chapter within a book
* Dissertation
* Web Site
* Page within a web site
* Music Recording
* Video Recording
* Interview
* Physical object (Statue, Painting, etc.)
* ??

Question:
Certain works have specific types of citations, for example, the Bible--and, I assume, other religious works--have very specific citation formats with different relevant information (chapter/verse) than others, as do the works of Shakespeare. Should these be considered separate types/roles?

A: I think in terms of types, we should at least note the items (chapter, verse, etc). How they get dealt with is still way up in the air. - [[User:Tim White|Tim White]]

Likewise, there are several different roles associated with publications -- author, co-author, editor, translator, etc. Should these be captured under a master "role" or treated as individual elements?

A: Good question. I think there is an important distinction, but whether we follow a design pattern of "role-*" (or more likely "author-*) or some other pattern hasn't been discussed yet. - Tim

== Biblio RDF Class Schema ==
Regading the issue of types notes above, the [http://vocab.org/biblio/schema biblio schema] provides a comprehensive set of classes to describe citation metadata. It might prove useful as a guide for a micro-format. The primary classes are Agent, Reference, Collection, and Event. An "Article", then, would be a subclass of "Part", which in turn is a subclass of Reference. Likewise, a "Journal" is a subclass of a "Periodical," which in turn is a subclass of "Collection." An article would typically be linked to a journal through a dcterms:isPartOf relation.

== ISBN:// Protocol ==

[http://www.faqs.org/rfcs/rfc3187.html RFC3187] defines an isbn protocol

Example:

URN:ISBN:0-395-36341-1

I'm not sure if any browser uses this data, but it might be have an application in citations describing registered materials with an ISBN

== You should know ==
* There are more then 1.300 citation ''styles'' in EndNote 9.
* Libraries have developed formats and rules for publications since more than 100 years. There are millions of records in library catalougues. You should '''at least''' be familiar with AACR and FRBR. There '''already are''' effords to create a new "microformat" called ''Resource Description and Access'' (RDA) [http://www.collectionscanada.ca/jsc/rdaprospectus.html]. Why don't you try to work with the professionals instead of amateurishly trying to reinvent the wheel and create yet another incompatible format? -- [[User:JakobVoss|JakobVoss]] 01:39, 5 Jun 2006 (PDT)