Microformats Wiki - User contributions [en]

User:EdwardVielmetti

2008-01-02T15:39:23Z

EdwardVielmetti: try the vcard span; it needs a template

Edward Vielmetti
Ann Arbor, MI

Edward Vielmetti

edward.vielmetti@gmail.com

{{cc-public-domain-release}}

User:EdwardVielmetti

2008-01-02T15:34:46Z

EdwardVielmetti:

Edward Vielmetti
Ann Arbor, MI

edward.vielmetti@gmail.com

{{cc-public-domain-release}}

User:EdwardVielmetti

2008-01-02T15:33:55Z

EdwardVielmetti:

Edward Vielmetti
Ann Arbor, MI

edward.vielmetti@gmail.com

[[Category: User pages]]

page-summary-formats

2006-11-02T21:58:03Z

EdwardVielmetti: initial links pointers etc; needs refactoring for style and formats

Firefox 2.0 has "microsummary" support for bookmarks.

Documentation:
* http://wiki.mozilla.org/Microsummaries

Code:
* WP-Microsummary plugin for WordPress: http://www.xs4all.nl/~jlpoutre/BoT/WP/microsummary/

Some examples of discussion:
* George Hotelling: http://george.hotelling.net/90percent/geekery/firefox_2s_great_new_feature_with_a_horrible_ui.php

Main Page

2006-11-02T21:54:16Z

EdwardVielmetti: /* Exploratory Discussions */

__NOTOC__

<h1> Microformats Wiki </h1>

'''Hello!''' Welcome to the microformats wiki. If this is your first visit, please see the [[introduction]] page.

Please read [[how-to-play]] before making any edits.

Please read [[process]] before proposing any new microformats.

__TOC__

==Getting Started==

[[what-are-microformats|What are microformats]]? [[what-can-you-do-with-microformats|What can you do with them]]?

The [http://microformats.org/about/ about page], plus recent [[press]], [[presentations]], [[podcasts]], and [[screencasts]] are also good places for some background information.

Frequently asked questions about the wiki and microformats in general are answered in the [[faq|FAQ]].

Want to learn more in person? Check out [[events|microformats events]].

==Definition==

One popular definition from our [http://microformats.org/discuss/ mailing list] (see also: [[mailing-lists]]) is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:
:simple conventions
:for embedding semantic markup
::for a specific problem domain
:in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML
::that normalize existing content usage patterns
::using brief, descriptive class names
::often based on existing interoperable standards
:to enable decentralized development
::of resources, tools, and services

"Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]

== How to contribute ==

Do you want to help take microformats to the next level? You can:

*Check out our open [[to-do|to do list]] for things to help get done.
*Join the [http://microformats.org/discuss mailing lists] and [[irc|IRC Channel]] to learn and help answer questions about microformats.
*[[advocacy|Advocate]] the use of microformats.
*help to [[Main_Page#microformats_wiki_in_other_languages|translate the microformats wiki into other languagses]] to make microformats globally accessible.

== Specifications ==
[[microformats|Microformats]] open standards specifications (see also: [[implementations]])
* [[hcalendar|hCalendar]]
* [[hcard|hCard]]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])
* [http://gmpg.org/xmdp/ XMDP]
* [[xoxo|XOXO]]

== Drafts ==
* [[adr|adr]]
* [[geo|geo]]
* [[hatom|hAtom]] {{NewMarker}}
* [[hresume|hResume]] {{NewMarker}}
* [[hreview|hReview]]
* [[rel-directory]]
* [[rel-enclosure]]
* [[rel-home]]
* [[relpayment-research | rel-payment]]
* [[robots-exclusion|Robots Exclusion]]
* [[xfolk|xFolk]]

== Design Patterns ==

{{design_patterns}} 

== Exploratory Discussions ==
Research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat.
*alternates [[alternates-brainstorming|brainstorming]], [[alternates-examples|examples]]
*[[attention]]
* blog description [[blog-description-examples|examples]]
* blog info [[blog-info-examples|examples]]
* blog post [[blog-post-examples|examples]], [[blog-post-formats|formats]], and [[blog-post-brainstorming|brainstorming]] (yielded the [[hatom|hAtom]] draft)
* book [[book-examples|examples]], [[book-formats|formats]], and [[book-brainstorming|brainstorming]]
* chat [[chat-examples|examples]], [[chat-formats|formats]], and [[chat-brainstorming|brainstorming]]
* citation [[citation|effort]], [[citation-examples|examples]], [[citation-formats|formats]], [[citation-brainstorming|brainstorming]], and [[citation-faq|FAQ]]
* comment [[comment-problem|problem]], [[comment-examples|examples]], and [[comments-formats|formats]] (Some stuff needs to be extracted from [[comments-formats]])
* [[currency]]; [[currency-examples]]; [[currency-brainstorming]] {{NewMarker}}
* directions [[directions-examples|examples]] {{NewMarker}}
* directory inclusion [[directory-inclusion-examples|examples]], [[directory-inclusion-formats|formats]]. (see also [[rel-directory]])
* distributed conversation [[distributed-conversation|overview]], [[distributed-conversation-brainstorming|brainstorming]], [[distributed-conversation-examples|examples]], and [[distributed-conversation-formats|formats]]
* forms [[forms-examples|examples]]
* genealogy [[genealogy-formats|examples]]
* group [[group-brainstorming|brainstorming]] and [[group-examples|examples]]
* hash [[hash-examples|examples]]
* job listing [[job-listing-examples|examples]] and [[job-listing-brainstorming|brainstorming]]
* last modified [[last-modified-examples|examples]], [[last-modified-formats|formats]], and [[last-modified-brainstorming|brainstorming]]
* hListing [[hlisting-proposal|proposal]], and [[hlisting-feedback|feedback]] {{NewMarker}}
** Also, listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]
* location [[location-formats|formats]]. (see also [[adr]] and [[geo]])
* [[luna]] ([[geo]]-like co-ordinates, for places on The Moon) {{NewMarker}}
* [[mars]] ([[geo]]-like co-ordinates, for places on the planet Mars) {{NewMarker}}
* measures and measurement units [[measure]]
* [[media-info]] ([[media-info-examples|examples]], [[media-info-formats|formats]], [[media-info-brainstorming|brainstorming]])
* meeting minutes [[meeting-minutes-examples|examples]], [[meeting-minutes-formats|formats]], and [[meeting-minutes-brainstorming|brainstorming]]
* metalink [[metalink-examples|examples]] {{NewMarker}}
* microsummary [[microsummary-brainstorming|brainstorming]] {{NewMarker}}
* [[mfo-examples|MFO examples]]
* music [[music-examples|examples]]
* photo note [[photo-note-examples|examples]]
* recipe [[recipe-examples|examples]]
* rel-product [[rel-product-brainstorming|brainstorming]]
* requirements testing [[requirements-testing|overview]], and [[requirements-testing-examples|examples]]
* [[rest-examples|REST examples]]
* resume [[resume-brainstorming|brainstorming]], and [[resume-formats|formats]]
* review [[review-examples|examples]], and [[review-formats|formats]] (yielded the [[hreview|hReview]] draft)
* search results [[search-results-example|example]]
* show [[show-brainstorming|brainstorming]]
* showroll [[showroll-brainstorming|brainstorming]]
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]]; [[species-brainstorming]] {{NewMarker}}
* table [[table-examples|examples]]
* tagspeak [[tagspeak-examples|examples]]
* tagcloud [[tagcloud-examples|examples]], and [[tagcloud-brainstorming | brainstorming]]. {{NewMarker}}
* transit table [[transit-table-examples|examples]]
* [[uid]]
* widget [[widget-examples|examples]], and [[widget-brainstorming|brainstorming]]
* [[wiki-formats|wiki formats]]
* work of art [[work-of-art|overview]], [[workofart-examples|examples]], [[workofart-formats|formats]], and [[workofart-brainstorming|brainstorming]] {{NewMarker}}
*[[xmdp-brainstorming|XMDP brainstorming]] (see also [[xmdp-faq]])

== Examples ==
* [[examples]]
* [[zen-garden]]

== Tools & Test Cases & Additional Research ==

The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.

*[[accessibility]]
*[[faqs-for-rdf]]
*[[icalendar-implementations]]
*[[parsing-microformats]]
*[[selected-test-cases-from-the-web]]
*[http://hg.microformats.org/ Source code repository] -- [[mercurial-quick-start|HowTo: Download code from the repository]]
*[[vcard-implementations]], [[vcard-errata]]
*[[why-are-content-standards-hard]]

== shared work areas ==
* [[buttons]]
* [[spread-microformats]] {{NewMarker}}
* [[demo]] - a page with links for quickly demonstrating microformats working in practice.
* [[events]] {{NewMarker}}
* [[to-do]]
* [[user-interface]]
* [[marked-for-deletion]]

== microformats wiki in other languages ==

You may read and edit microformats articles in many other languages:

* languages with over 50 articles
** [[Main_Page-fr|Français (French)]] {{NewMarker-fr}}
* languages with over 2 articles
** [[Main_Page-ja|日本語 (Japanese)]]
** [[Main_Page-es|Español (Spanish)]]
* languages with 2 articles
** [[Main_Page-de|Deutsch (German)]]

==== microformats translations elsewhere ====
These are offsite pages/sites with translations about microformats. If you are working on one of these, please consider translating the main microformats website!
* [http://mikroformate.pbwiki.com/ Deutsch (German) mikroformate.pbwiki.com] {{NewMarker}}

=== Start a microformats wiki in another language ===

Don't see the language you want? Help translate the microformats wiki into another language!

We're still figuring this out.

For now, see the [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Wikipedia page on Multilingual coordination], and [http://meta.wikimedia.org/wiki/How_to_start_a_new_Wikipedia How to start a new Wikipedia] for some good general tips, advice, and community conventions.

You may want to start with the list of [[stable-pages]], which are pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions, by using the [[Special:Watchlist|my watchlist]] feature (use it to watch the pages you've translated for changes).

Page naming: for the translated version of a page, use the same name for the page, and simply add the RFC 3066 language identifier code as a dash suffix. E.g. for the French version, [[Main_Page]] becomes [[Main_Page-fr]], and [[how-to-play]] becomes [[how-to-play-fr]].

==== more languages folks want to see ====

* Chinese: 微格式 (Microformats) (see [http://msittig.blogspot.com/2005/11/since-i-translated-schedule-of.html source of translation])

citation-formats

2006-01-19T03:04:02Z

EdwardVielmetti: /* SimpleDC supported by the zoom toolkit */

= 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:
* [[cite]]
* [[cite-brainstorming]]
* [[cite-examples]]

== 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 bgcolor="#cccccc"></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>Contributer</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>published</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 keywords 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)

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

== 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 <a href="#proceedings">Proceedings</a>.</td>
</tr>
<tr>
<td>conference:</td>
<td>The same as <a href="#inproceedings">Inproceedings</a>.</td>
</tr>
<tr>
<td>inbook:</td>
<td>A part of a book, which may be a chapter and/or a
range of pages. Required fields: author or editor, title,
chapter and/or pages, publisher, year. Optional fields:
volumer, series, address, edition, month, note, key.</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><a name="inproceedings"></a>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><a name="proceedings"></a>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>

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

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

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

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

== 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()

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

citation-formats

2006-01-18T20:45:12Z

EdwardVielmetti: /* Ann Arbor District Library XML feed */

User:EdwardVielmetti

2006-01-18T05:37:22Z

EdwardVielmetti: eh

Patron of the [http://www.aadl.org Ann Arbor District Library] and member of
its technical advisory board. Interested in [[cite-formats]] and other ways
to get microformats into library catalog output.

Learning python at the moment.

Blog: [http://vielmetti.typepad.com/superpatron Superpatron].

edward.vielmetti@gmail.com

citation-formats

2006-01-18T05:34:53Z

EdwardVielmetti: /* Ann Arbor District Library XML feed */

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

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

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

<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 bgcolor="#cccccc"></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>Contributer</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>published</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 keywords 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)

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

== 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 <a href="#proceedings">Proceedings</a>.</td>
</tr>
<tr>
<td>conference:</td>
<td>The same as <a href="#inproceedings">Inproceedings</a>.</td>
</tr>
<tr>
<td>inbook:</td>
<td>A part of a book, which may be a chapter and/or a
range of pages. Required fields: author or editor, title,
chapter and/or pages, publisher, year. Optional fields:
volumer, series, address, edition, month, note, key.</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><a name="inproceedings"></a>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><a name="proceedings"></a>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>

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

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

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

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

citation-formats

2006-01-18T05:34:30Z

EdwardVielmetti: /* Ann Arbor District Library XML feed */

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

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

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

<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 bgcolor="#cccccc"></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>Contributer</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>published</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 keywords 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)

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

== 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 <a href="#proceedings">Proceedings</a>.</td>
</tr>
<tr>
<td>conference:</td>
<td>The same as <a href="#inproceedings">Inproceedings</a>.</td>
</tr>
<tr>
<td>inbook:</td>
<td>A part of a book, which may be a chapter and/or a
range of pages. Required fields: author or editor, title,
chapter and/or pages, publisher, year. Optional fields:
volumer, series, address, edition, month, note, key.</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><a name="inproceedings"></a>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><a name="proceedings"></a>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>

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

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

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

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

citation-formats

2006-01-18T05:33:28Z

EdwardVielmetti: /* DocBook */

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

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

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

<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 bgcolor="#cccccc"></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>Contributer</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>published</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 keywords 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)

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

== 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 <a href="#proceedings">Proceedings</a>.</td>
</tr>
<tr>
<td>conference:</td>
<td>The same as <a href="#inproceedings">Inproceedings</a>.</td>
</tr>
<tr>
<td>inbook:</td>
<td>A part of a book, which may be a chapter and/or a
range of pages. Required fields: author or editor, title,
chapter and/or pages, publisher, year. Optional fields:
volumer, series, address, edition, month, note, key.</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><a name="inproceedings"></a>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><a name="proceedings"></a>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>

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

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

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

== Ann Arbor District Library XML feed ==
''' THIS BELONGS IN [[cite-formats]], NOT HERE'''

Here is [http://www.aadl.org/cat/seek/search/X?SEARCH=knitting&searchscope=26&x=0&y=0&SORT=D&sourceid=Mozilla-search&rss=1 an example of the HTML (inside an RSS feed)] that the [http://www.aadl.org Ann Arbor District Library ] is generating and wants to mark up with some sort of publication microformat.

Here's a record in XML format from their project:

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

citation-brainstorming

2006-01-18T05:33:03Z

EdwardVielmetti: /* Ann Arbor District Library XML feed */

= Citation Brainstroming =

== XHTML Structure ==
With my exprience working X2V and hCa* has taught me what elememts are easy to find and which are not. Since the Citation microformat is very new it is possible to not make a lot of the same errors twice and to make things easier for extracting application to find and imply certain properties.

* There should be some sort of 'root node' that implies all child elements are for the Citation microformat.
* Since most people will have multiple Citation there should be away to represent each Citation object as a unqiue block independant of another. This is to keep the parse from finding 'author' and applying to all citations. Each citation should be in a container (class="???") that scoped from others.

@@ more points will be posted as i remember of them

== Semantic Meaning ==
One of the guiding priniciple of Microformats is to use the most semantically rich element to describe each node (Point 2 of Semantic XHTML Design Principles: Use the most accurately precise semantic XHTML building block for each object etc). Since we are dealing with HTML and citations, several elements are candidates to be used to enrich the semantic meaning. [http://www.w3.org/TR/REC-html40/struct/text.html CITE, BLOCKQUOTE, Q, A], (are there more?)

The [[citation-brainstorming|Citation Brainstorming Page]] has a few development and ideas about how to give another person credit for a link. Some of the semantic ideas behind their choices of tags can be applied to a full bibliographic type reference.

== ISBN:// Protocol ==

''' THIS BELONGS IN [[cite-formats]], NOT HERE'''

[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

Question: what about using something like OCLC's [http://www.oclc.org/worldcat/open/isbnissnlinking/default.htm WorldCat] for linking titles? - Tim White

== This and That ==
After reading through alot of different citation encoding formats, i noticed that each format was being used in onw of two ways. It was either to describe the Current page (THIS.PAGE) or being used to encode references that point to external resources (THAT.PAGE)

The informatation being encoded was identical for both resources (author, date, name, etc) they just reference different things. For this microformat, i'm not sure if we want to try to solve both problems, or just one? The meta tags in the head element would be the ideal place for information about the THIS.PAGE, but that is not in following with the ideals of microformats where information is human-readable. The THAT.PAGE idea where a list of references is at the end of a document in the form of a bibliography is more inline with the ideals of a microformat where the data is human-readable. That doesn't mean that data about the current document shouldn't be human-readable, so some of the same properties used to reference extermal resources can be used for the current document (THIS.PAGE). To do this a different root item could be used and transforming applications could either extract the citation data about the current page, or information about this page's references.

This is open for discussion, but either way, i believe that the properties used to describe a page will be the same for both THIS and THAT. [http://suda.co.uk/ brian suda]

== Date Formatting ==
Since microformats are all about re-use and the accepted way to encode Date-Time has been pretty much settled, then this is a good place to start when dealing with all the different date citation types.

These are all the different fields from various citation formats that are of temporal nature:
* 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 Confernce
* Date of Publication
* Date of update/revisou/issuance of database record
* Former Date
* Entry Date for Database Record
* Database Update
* Year of Publication

There are several common properties across several citation domains and will certainly be in the citation microformat, the unique instances will need further consideration, otherwise there could be no end to posiblities.

There are also several properties (year, month, Year of publication) that can be extracted from another source. Therefore, if you only encode a more specific property such as; Date of Publication, you can extract the 'year of publication' from that. Since the date-time format we are modeling after is the ISO date-time format, just the Year portion is an acceptable date. So if you ONLY know the year of publication, the you can form a valid 'Date of Publication' as a microformat (which inturn is a valid 'year of publication') - you milage may vary when it comes to importing into citation applications.

...

It seems to me that these can be collapsed to maybe one or two different date properties. As far as the specific human readable formatting of the date, that can be chosen per whatever the presentation style guide says, and the [[datetime-design-pattern]] used to simplify the markup. - Tantek

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

''' THIS BELONGS IN [[cite-formats]], NOT HERE'''

There are many different types of publications and this information should be captured in the citation. Possible types include:
* Novel/fiction (specify type -- literature, sci-fi, romance, etc.?)
* Non-fiction
* Poem
* Play
* Magazine
* Reference (seperate 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 seperate 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. - Tim

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

== Tags ==
Some of the citation formats has a place for 'keywords' or 'generic tags', etc. This might be a good place to re-use the [http://microformats.org/wiki/rel-tag RelTag microformat]. The downside would be that they are then forced to be links, which might be the correct way to mark-up these terms.

== OpenURL ==
''' THIS BELONGS IN [[cite-formats]], NOT HERE'''

OpenURL is in use in library software around the world to allow citation metadata to be embedded in URLs. Typically these URLs are used for targeting resolvers which essentially proxy access to licensed content. OpenURL also provides an XML encoding. The [http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=ListRecords&metadataPrefix=oai_dc&set=Core:Metadata+Formats key/value] pairs used in OpenURL could relatively easily be adapted to semantic HTML. This is a cow path that could be paved relatively easily using existing modules as appropriate.

OpenURL has a microformat-like encoding: [http://ocoins.info/ COinS]. This uses the 'title' attribute of HTML 'span' tags to embed OpenURL URLs.

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

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

== MARC / MODS / Dublin Core ==

The MODS ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgmods.xml example]) and Dublin Core ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgdc.xml example]) transformations of MARC21 may contain some useful ideas.

Here's a first attempt at rewriting the linked examples in XHTML (written in response to a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002438.html mailing list query about encoding book information with microformats]):

<pre><nowiki>
<div class="book" lang="en">
<h3 class="fn">Arithmetic /</h3>
By Sandburg, Carl,
1878-1967,
and Rand, Ted
Publisher: Harcourt Brace Jovanovich,
San Diego
Published: 1993
A poem about numbers and their characteristics. Features
anamorphic, or distorted, drawings which can be restored to normal by viewing
from a particular angle or by viewing the image's reflection in the provided
Mylar cone.
One Mylar sheet included in pocket.
Subjects:
<ul>
<li class="subject">Arithmetic</li>
<li class="subject">Children's poetry, American.</li>
<li class="subject">Arithmetic</li>
<li class="subject">American poetry</li>
<li class="subject">Visual perception</li>
</ul>
</div>
</nowiki></pre>

citation-brainstorming

2006-01-18T05:21:58Z

EdwardVielmetti: /* MARC / MODS / Dublin Core */

= Citation Brainstroming =

== XHTML Structure ==
With my exprience working X2V and hCa* has taught me what elememts are easy to find and which are not. Since the Citation microformat is very new it is possible to not make a lot of the same errors twice and to make things easier for extracting application to find and imply certain properties.

* There should be some sort of 'root node' that implies all child elements are for the Citation microformat.
* Since most people will have multiple Citation there should be away to represent each Citation object as a unqiue block independant of another. This is to keep the parse from finding 'author' and applying to all citations. Each citation should be in a container (class="???") that scoped from others.

@@ more points will be posted as i remember of them

== Semantic Meaning ==
One of the guiding priniciple of Microformats is to use the most semantically rich element to describe each node (Point 2 of Semantic XHTML Design Principles: Use the most accurately precise semantic XHTML building block for each object etc). Since we are dealing with HTML and citations, several elements are candidates to be used to enrich the semantic meaning. [http://www.w3.org/TR/REC-html40/struct/text.html CITE, BLOCKQUOTE, Q, A], (are there more?)

The [[citation-brainstorming|Citation Brainstorming Page]] has a few development and ideas about how to give another person credit for a link. Some of the semantic ideas behind their choices of tags can be applied to a full bibliographic type reference.

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

Question: what about using something like OCLC's [http://www.oclc.org/worldcat/open/isbnissnlinking/default.htm WorldCat] for linking titles? - Tim White

== This and That ==
After reading through alot of different citation encoding formats, i noticed that each format was being used in onw of two ways. It was either to describe the Current page (THIS.PAGE) or being used to encode references that point to external resources (THAT.PAGE)

The informatation being encoded was identical for both resources (author, date, name, etc) they just reference different things. For this microformat, i'm not sure if we want to try to solve both problems, or just one? The meta tags in the head element would be the ideal place for information about the THIS.PAGE, but that is not in following with the ideals of microformats where information is human-readable. The THAT.PAGE idea where a list of references is at the end of a document in the form of a bibliography is more inline with the ideals of a microformat where the data is human-readable. That doesn't mean that data about the current document shouldn't be human-readable, so some of the same properties used to reference extermal resources can be used for the current document (THIS.PAGE). To do this a different root item could be used and transforming applications could either extract the citation data about the current page, or information about this page's references.

This is open for discussion, but either way, i believe that the properties used to describe a page will be the same for both THIS and THAT. [http://suda.co.uk/ brian suda]

== Date Formatting ==
Since microformats are all about re-use and the accepted way to encode Date-Time has been pretty much settled, then this is a good place to start when dealing with all the different date citation types.

These are all the different fields from various citation formats that are of temporal nature:
* 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 Confernce
* Date of Publication
* Date of update/revisou/issuance of database record
* Former Date
* Entry Date for Database Record
* Database Update
* Year of Publication

There are several common properties across several citation domains and will certainly be in the citation microformat, the unique instances will need further consideration, otherwise there could be no end to posiblities.

There are also several properties (year, month, Year of publication) that can be extracted from another source. Therefore, if you only encode a more specific property such as; Date of Publication, you can extract the 'year of publication' from that. Since the date-time format we are modeling after is the ISO date-time format, just the Year portion is an acceptable date. So if you ONLY know the year of publication, the you can form a valid 'Date of Publication' as a microformat (which inturn is a valid 'year of publication') - you milage may vary when it comes to importing into citation applications.

== Types and Roles ==
(Section is informative only as a place to capture varioua=s 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, sci-fi, romance, etc.?)
* Non-fiction
* Poem
* Play
* Magazine
* Reference (seperate 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 seperate 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. - Tim

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

== Tags ==
Some of the citation formats has a place for 'keywords' or 'generic tags', etc. This might be a good place to re-use the [http://microformats.org/wiki/rel-tag RelTag microformat]. The downside would be that they are then forced to be links, which might be the correct way to mark-up these terms.

== OpenURL ==

OpenURL is in use in library software around the world to allow citation metadata to be embedded in URLs. Typically these URLs are used for targeting resolvers which essentially proxy access to licensed content. OpenURL also provides an XML encoding. The [http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=ListRecords&metadataPrefix=oai_dc&set=Core:Metadata+Formats key/value] pairs used in OpenURL could relatively easily be adapted to semantic HTML. This is a cow path that could be paved relatively easily using existing modules as appropriate.

OpenURL has a microformat-like encoding: [http://ocoins.info/ COinS]. This uses the 'title' attribute of HTML 'span' tags to embed OpenURL URLs.

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

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

== MARC / MODS / Dublin Core ==

The MODS ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgmods.xml example]) and Dublin Core ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgdc.xml example]) transformations of MARC21 may contain some useful ideas.

Here's a first attempt at rewriting the linked examples in XHTML (written in response to a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002438.html mailing list query about encoding book information with microformats]):

<pre><nowiki>
<div class="book" lang="en">
<h3 class="fn">Arithmetic /</h3>
By Sandburg, Carl,
1878-1967,
and Rand, Ted
Publisher: Harcourt Brace Jovanovich,
San Diego
Published: 1993
A poem about numbers and their characteristics. Features
anamorphic, or distorted, drawings which can be restored to normal by viewing
from a particular angle or by viewing the image's reflection in the provided
Mylar cone.
One Mylar sheet included in pocket.
Subjects:
<ul>
<li class="subject">Arithmetic</li>
<li class="subject">Children's poetry, American.</li>
<li class="subject">Arithmetic</li>
<li class="subject">American poetry</li>
<li class="subject">Visual perception</li>
</ul>
</div>
</nowiki></pre>

== Ann Arbor District Library XML feed ==

Here is [http://www.aadl.org/cat/seek/search/X?SEARCH=knitting&searchscope=26&x=0&y=0&SORT=D&sourceid=Mozilla-search&rss=1 an example of the HTML (inside an RSS feed)] that the [http://www.aadl.org Ann Arbor District Library ] is generating and wants to mark up with some sort of publication microformat.

Here's a record in XML format from their project:

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

citation-brainstorming

2005-12-21T04:42:00Z

EdwardVielmetti: /* MARC / MODS / Dublin Core */

= Citation Brainstroming =

== XHTML Structure ==
With my exprience working X2V and hCa* has taught me what elememts are easy to find and which are not. Since the Citation microformat is very new it is possible to not make a lot of the same errors twice and to make things easier for extracting application to find and imply certain properties.

* There should be some sort of 'root node' that implies all child elements are for the Citation microformat.
* Since most people will have multiple Citation there should be away to represent each Citation object as a unqiue block independant of another. This is to keep the parse from finding 'author' and applying to all citations. Each citation should be in a container (class="???") that scoped from others.

@@ more points will be posted as i remember of them

== Semantic Meaning ==
One of the guiding priniciple of Microformats is to use the most semantically rich element to describe each node (Point 2 of Semantic XHTML Design Principles: Use the most accurately precise semantic XHTML building block for each object etc). Since we are dealing with HTML and citations, several elements are candidates to be used to enrich the semantic meaning. [http://www.w3.org/TR/REC-html40/struct/text.html CITE, BLOCKQUOTE, Q, A], (are there more?)

The [[citation-brainstorming|Citation Brainstorming Page]] has a few development and ideas about how to give another person credit for a link. Some of the semantic ideas behind their choices of tags can be applied to a full bibliographic type reference.

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

Question: what about using something like OCLC's [http://www.oclc.org/worldcat/open/isbnissnlinking/default.htm WorldCat] for linking titles? - Tim White

== This and That ==
After reading through alot of different citation encoding formats, i noticed that each format was being used in onw of two ways. It was either to describe the Current page (THIS.PAGE) or being used to encode references that point to external resources (THAT.PAGE)

The informatation being encoded was identical for both resources (author, date, name, etc) they just reference different things. For this microformat, i'm not sure if we want to try to solve both problems, or just one? The meta tags in the head element would be the ideal place for information about the THIS.PAGE, but that is not in following with the ideals of microformats where information is human-readable. The THAT.PAGE idea where a list of references is at the end of a document in the form of a bibliography is more inline with the ideals of a microformat where the data is human-readable. That doesn't mean that data about the current document shouldn't be human-readable, so some of the same properties used to reference extermal resources can be used for the current document (THIS.PAGE). To do this a different root item could be used and transforming applications could either extract the citation data about the current page, or information about this page's references.

This is open for discussion, but either way, i believe that the properties used to describe a page will be the same for both THIS and THAT. [http://suda.co.uk/ brian suda]

== Date Formatting ==
Since microformats are all about re-use and the accepted way to encode Date-Time has been pretty much settled, then this is a good place to start when dealing with all the different date citation types.

These are all the different fields from various citation formats that are of temporal nature:
* 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 Confernce
* Date of Publication
* Date of update/revisou/issuance of database record
* Former Date
* Entry Date for Database Record
* Database Update
* Year of Publication

There are several common properties across several citation domains and will certainly be in the citation microformat, the unique instances will need further consideration, otherwise there could be no end to posiblities.

There are also several properties (year, month, Year of publication) that can be extracted from another source. Therefore, if you only encode a more specific property such as; Date of Publication, you can extract the 'year of publication' from that. Since the date-time format we are modeling after is the ISO date-time format, just the Year portion is an acceptable date. So if you ONLY know the year of publication, the you can form a valid 'Date of Publication' as a microformat (which inturn is a valid 'year of publication') - you milage may vary when it comes to importing into citation applications.

== Types and Roles ==
There are many different types of publications and this information should be captured in the citation. Possible types include:
* Novel/fiction (specify type -- literature, sci-fi, romance, etc.?)
* Non-fiction
* Poem
* Play
* Magazine
* Reference (seperate out encyclopedia, dictionary, almanac, etc.?)
* Journal
* Article
* ??

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?

== Tags ==
Some of the citation formats has a place for 'keywords' or 'generic tags', etc. This might be a good place to re-use the [http://microformats.org/wiki/rel-tag RelTag microformat]. The downside would be that they are then forced to be links, which might be the correct way to mark-up these terms.

== OpenURL ==

OpenURL is in use in library software around the world to allow citation metadata to be embedded in URLs. Typically these URLs are used for targeting resolvers which essentially proxy access to licensed content. OpenURL also provides an XML encoding. The [http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=ListRecords&metadataPrefix=oai_dc&set=Core:Metadata+Formats key/value] pairs used in OpenURL could relatively easily be adapted to semantic HTML. This is a cow path that could be paved relatively easily using existing modules as appropriate.

== MARC / MODS / Dublin Core ==

The MODS ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgmods.xml example]) and Dublin Core ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgdc.xml example]) transformations of MARC21 may contain some useful ideas.

Here's a first attempt at rewriting the linked examples in XHTML (written in response to a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002438.html mailing list query about encoding book information with microformats]):

<pre><nowiki>
<div class="book" lang="en">
<h3 class="fn">Arithmetic /</h3>
By Sandburg, Carl,
1878-1967,
and Rand, Ted
Publisher: Harcourt Brace Jovanovich,
San Diego
Published: 1993
A poem about numbers and their characteristics. Features
anamorphic, or distorted, drawings which can be restored to normal by viewing
from a particular angle or by viewing the image's reflection in the provided
Mylar cone.
One Mylar sheet included in pocket.
Subjects:
<ul>
<li class="subject">Arithmetic</li>
<li class="subject">Children's poetry, American.</li>
<li class="subject">Arithmetic</li>
<li class="subject">American poetry</li>
<li class="subject">Visual perception</li>
</ul>
</div>
</nowiki></pre>

Here is [http://www.aadl.org/cat/seek/search/X?SEARCH=knitting&searchscope=26&x=0&y=0&SORT=D&sourceid=Mozilla-search&rss=1 an example of the HTML (inside an RSS feed)] that the [http://www.aadl.org Ann Arbor District Library ] is generating and wants to mark up with some sort of publication microformat.

citation-brainstorming

2005-12-21T04:40:45Z

EdwardVielmetti: /* MARC / MODS / Dublin Core */

= Citation Brainstroming =

== XHTML Structure ==
With my exprience working X2V and hCa* has taught me what elememts are easy to find and which are not. Since the Citation microformat is very new it is possible to not make a lot of the same errors twice and to make things easier for extracting application to find and imply certain properties.

* There should be some sort of 'root node' that implies all child elements are for the Citation microformat.
* Since most people will have multiple Citation there should be away to represent each Citation object as a unqiue block independant of another. This is to keep the parse from finding 'author' and applying to all citations. Each citation should be in a container (class="???") that scoped from others.

@@ more points will be posted as i remember of them

== Semantic Meaning ==
One of the guiding priniciple of Microformats is to use the most semantically rich element to describe each node (Point 2 of Semantic XHTML Design Principles: Use the most accurately precise semantic XHTML building block for each object etc). Since we are dealing with HTML and citations, several elements are candidates to be used to enrich the semantic meaning. [http://www.w3.org/TR/REC-html40/struct/text.html CITE, BLOCKQUOTE, Q, A], (are there more?)

The [[citation-brainstorming|Citation Brainstorming Page]] has a few development and ideas about how to give another person credit for a link. Some of the semantic ideas behind their choices of tags can be applied to a full bibliographic type reference.

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

Question: what about using something like OCLC's [http://www.oclc.org/worldcat/open/isbnissnlinking/default.htm WorldCat] for linking titles? - Tim White

== This and That ==
After reading through alot of different citation encoding formats, i noticed that each format was being used in onw of two ways. It was either to describe the Current page (THIS.PAGE) or being used to encode references that point to external resources (THAT.PAGE)

The informatation being encoded was identical for both resources (author, date, name, etc) they just reference different things. For this microformat, i'm not sure if we want to try to solve both problems, or just one? The meta tags in the head element would be the ideal place for information about the THIS.PAGE, but that is not in following with the ideals of microformats where information is human-readable. The THAT.PAGE idea where a list of references is at the end of a document in the form of a bibliography is more inline with the ideals of a microformat where the data is human-readable. That doesn't mean that data about the current document shouldn't be human-readable, so some of the same properties used to reference extermal resources can be used for the current document (THIS.PAGE). To do this a different root item could be used and transforming applications could either extract the citation data about the current page, or information about this page's references.

This is open for discussion, but either way, i believe that the properties used to describe a page will be the same for both THIS and THAT. [http://suda.co.uk/ brian suda]

== Date Formatting ==
Since microformats are all about re-use and the accepted way to encode Date-Time has been pretty much settled, then this is a good place to start when dealing with all the different date citation types.

These are all the different fields from various citation formats that are of temporal nature:
* 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 Confernce
* Date of Publication
* Date of update/revisou/issuance of database record
* Former Date
* Entry Date for Database Record
* Database Update
* Year of Publication

There are several common properties across several citation domains and will certainly be in the citation microformat, the unique instances will need further consideration, otherwise there could be no end to posiblities.

There are also several properties (year, month, Year of publication) that can be extracted from another source. Therefore, if you only encode a more specific property such as; Date of Publication, you can extract the 'year of publication' from that. Since the date-time format we are modeling after is the ISO date-time format, just the Year portion is an acceptable date. So if you ONLY know the year of publication, the you can form a valid 'Date of Publication' as a microformat (which inturn is a valid 'year of publication') - you milage may vary when it comes to importing into citation applications.

== Types and Roles ==
There are many different types of publications and this information should be captured in the citation. Possible types include:
* Novel/fiction (specify type -- literature, sci-fi, romance, etc.?)
* Non-fiction
* Poem
* Play
* Magazine
* Reference (seperate out encyclopedia, dictionary, almanac, etc.?)
* Journal
* Article
* ??

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?

== Tags ==
Some of the citation formats has a place for 'keywords' or 'generic tags', etc. This might be a good place to re-use the [http://microformats.org/wiki/rel-tag RelTag microformat]. The downside would be that they are then forced to be links, which might be the correct way to mark-up these terms.

== OpenURL ==

OpenURL is in use in library software around the world to allow citation metadata to be embedded in URLs. Typically these URLs are used for targeting resolvers which essentially proxy access to licensed content. OpenURL also provides an XML encoding. The [http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=ListRecords&metadataPrefix=oai_dc&set=Core:Metadata+Formats key/value] pairs used in OpenURL could relatively easily be adapted to semantic HTML. This is a cow path that could be paved relatively easily using existing modules as appropriate.

== MARC / MODS / Dublin Core ==

The MODS ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgmods.xml example]) and Dublin Core ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgdc.xml example]) transformations of MARC21 may contain some useful ideas.

Here's a first attempt at rewriting the linked examples in XHTML (written in response to a [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002438.html mailing list query about encoding book information with microformats]):

<pre><nowiki>
<div class="book" lang="en">
<h3 class="fn">Arithmetic /</h3>
By Sandburg, Carl,
1878-1967,
and Rand, Ted
Publisher: Harcourt Brace Jovanovich,
San Diego
Published: 1993
A poem about numbers and their characteristics. Features
anamorphic, or distorted, drawings which can be restored to normal by viewing
from a particular angle or by viewing the image's reflection in the provided
Mylar cone.
One Mylar sheet included in pocket.
Subjects:
<ul>
<li class="subject">Arithmetic</li>
<li class="subject">Children's poetry, American.</li>
<li class="subject">Arithmetic</li>
<li class="subject">American poetry</li>
<li class="subject">Visual perception</li>
</ul>
</div>
</nowiki></pre>

Here is [http://www.aadl.org/cat/seek/search/X?SEARCH=knitting&searchscope=26&x=0&y=0&SORT=D&sourceid=Mozilla-search&rss=1 an example of the HTML (inside an RSS feed) that the [http://www.aadl.org Ann Arbor District Library] is generating] and wants to mark up with some sort of publication microformat.