(+OpenDocument) |
(→BibTeX: Adding practical examples of software that supports the bib format.) |
||
Line 536: | Line 536: | ||
</div> | </div> | ||
</nowiki></pre> | </nowiki></pre> | ||
+ | |||
+ | ===Bib-enabled Applications=== | ||
+ | |||
+ | Reference-management applications that support the bib format. <strong>This is an incomplete list</strong>. | ||
+ | |||
+ | ====Desktop Applications==== | ||
+ | * [http://www.endnote.com EndNote] (Large market share) | ||
+ | * [http://bibdesk.sourceforge.net/ BibDesk] | ||
+ | * [http://www.mackichan.com/index.html?bibdb/default.htm~mainFrame BibDB] | ||
+ | * [http://sourceforge.net/projects/bib-it/ Bib-it] | ||
+ | * 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 == |
Revision as of 21:14, 30 July 2006
Contents |
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:
Comparison chart
The following chart maps the terms from one implementation to another. This is important because if all the properties are introduced to this microformats, then its possible to map them to a number of different formats. The table currently only uses Dublin Core, MODS, and bibTeX. Each column has all the properties and their equivalent in each format. If there is no corresponding property the cell is grey. At the bottom of the list are the unique terms to each format. Dublin core has basic terms and terms that extend the basic ones. If the property is an extention of a basic term it is in ()'s. MODS uses XML, so any sub-properties are listed in their tree form, property/sub-property.
THIS IS NOT DEFINIATIVE, any errors should be corrected. More formats will be added to the list as they are mapped.
Dublin Core | MODS | bibTeX | Z39.80 |
---|---|---|---|
Title (alternative) | titleInfo/title titleInfo/PartNum |
booktitle title chapter number pages volume series |
Analytic Title Collective or Series Title |
creator | name/namePart | author creator |
Author, Primary Corporate Author, Primary |
subject | subject/topic | keywords | needs mapping |
Description (abstract | tableOfContents) | abstract note tableOfContents |
abstract annotation note contents |
needs mapping |
Contributor | name | editor? | Book/Report/Volume Editor Producer |
Date (available | created | dateAccepted | dateCopyrighted | dateSubmitted | issued | modified | valid) | originInfo/dateIssued originInfo/dateCreated originInfo/dateCaptured originInfo/dateOther |
month year |
Copyright Year Date-generic Date of conference Date of Publication Date of Update/Revisou/Issuance of Database Record Former Date Entry date for Database Record Database Update Year of Publication |
Type | typeOfResource genre |
@class type |
needs mapping |
Format (extent | medium) | physicalDescription/internetMediaType physicalDescription/extent physicalDescription/form |
howpublished | needs mapping |
identifier (bibliographicCitation) | identifier | ISBN ISSN LCCN URL |
ISBN Identifier Report Identfier ISSN |
Source | relatedItem | needs mapping | |
language | language | language | |
Relation (...) | relatedItem/... | crossRef | needs mapping |
Coverage (spacial | temporal) | subject/temporal subject/geographic subject/hierarchicalGeographic subject/cartographics |
needs mapping | |
classifications | needs mapping | ||
Rights (accessRights | license) | accessConditions | copyright | needs mapping |
publisher | publisher | Publisher Name Place of Publication |
|
audience (educationLevel | mediator) | targetAudience | needs mapping | |
accualMethod accualPeriodicaty accualPolicy instrcutionalMethod provenance rightsHolder |
location extension recordInfo |
address afflilication location edition institution journal key mrnumber organization price school size |
(the following need to be mapped to the above rows or left here as other) Database Source |
Dublin Core Metadata
Dublin Core metadata uses a small vocabulary to descibe the data.
- contributor
- coverage
- creator
- date
- description
- format
- identifier
- language
- publisher
- relation
- rights
- source
- subject
- title
- type
From those there are specialised types where are just refinments of the previous, for example:
- abstract refines description.
- accessRights refines rights
Guidelines for Encoding Bibliographic Citation Information in Dublin Core Metadata
MODS (Metadata Object Description Schema)
This is a format developed for the Libray of Congress for a bibliographic element set that may be used for a variety of purposes, and particularly for library applications.
http://www.loc.gov/standards/mods/
(the schema is very big, once i devote the proper time to review it, i will post more about the structure -brian)
NLM Journal Publishing DTD
http://dtd.nlm.nih.gov/publishing/tag-library/2.1/n-fv30.html
The NLM Journal Publishing DTD defines the schema used for publishing journal articles as XML. The<citation>element can be placed with paragraphs or within a
<ref-list>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:
source | 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.) |
article-title | Title of the article |
volume | Volume of the journal |
issue | Issue of the journal |
fpage | Page number on which the article starts |
name | Name of an author or editor |
year | Year of publication |
month | Month of publication (if present) |
day | Date of publication (if present) |
Invalid language.
You need to specify a language like this: <source lang="html">...</source>
Supported languages for syntax highlighting:
abap, actionscript, actionscript3, ada, apache, applescript, apt_sources, asm, asp, autoit, bash, basic4gl, blitzbasic, bnf, boo, c, c_mac, caddcl, cadlisp, cfdg, cfm, cil, cpp, cpp-qt, csharp, css, d, delphi, diff, div, dos, dot, eiffel, fortran, freebasic, genero, gettext, glsl, gml, groovy, haskell, html4strict, idl, ini, inno, io, java, java5, javascript, kixtart, klonec, klonecpp, latex, lisp, lotusformulas, lotusscript, lua, m68k, matlab, mirc, mpasm, mxml, mysql, nsis, objc, ocaml, ocaml-brief, oobas, oracle8, pascal, per, perl, php, php-brief, plsql, powershell, python, qbasic, rails, reg, robots, ruby, sas, scala, scheme, sdlbasic, smalltalk, smarty, sql, tcl, text, thinbasic, tsql, vb, vbnet, verilog, vhdl, visualfoxpro, winbatch, xml, xorg_conf, xpp, z80