Microformats Wiki - User contributions [en]

datetime-design-pattern

2006-09-07T04:28:24Z

TerrellRussell: /* Current uses */ added an alternative for UTC

'''This page is a draft.'''

= Datetime Design Pattern =
This is a page for exploring a datetime design pattern.

== Purpose ==
* Use the [[datetime-design-pattern]] to make datetimes that are human readable also formally machine readable.

== Practical Need ==
* This design pattern arose as a result of solving the practical need for human readable dates for [[hcalendar|hCalendar]].

== How to use it ==
* enclose the human-friendly datetime that you want to make machine readable with <code><abbr></code>
* as per the [[class-design-pattern]], add the appropriate <code>class</code> attribute to the <code>abbr</code> element
* add a <code>title</code> attribute to the <code>abbr</code> element with the machine readable ISO8601 datetime or date as the value

== Current uses ==

The pattern which is now used in [[hcalendar|hCalendar]] and [[hreview|hReview]] is something like this:

<pre><abbr class="foo" title="YYYY-MM-DDTHH:MM:SS+ZZ:ZZ">Date Time</abbr></pre>

where foo is the semantic classname which is being applied to this date/time, the title of the <abbr> is an ISO 8601 date/time and "Date Time" is a human-friendly representation of the same date/time.

An alternative, if you are using UTC-based timestamps, would be:

<pre><abbr class="foo" title="YYYY-MM-DDTHH:MM:SSZ">Date Time</abbr></pre>

with a single "Z" as per [http://en.wikipedia.org/wiki/ISO_8601 ISO 8601]

== Profile of ISO8601 ==

We recommend that any [[microformat]] using the date-time-design pattern use a profile of ISO8601. There are currently two widely used profiles which SHOULD be reused.

* RFC 3339
* [http://www.w3.org/TR/NOTE-datetime W3C Note on Datetimes]

== Discussion ==

This pattern is likely to be highly resuable.

--[[User:RyanKing]]

Can this not be viewed as a microformat in itself?

--[[User:DimitriGlazkov]]

It could, but inventing a microformat for the sake of inventing a microformat is against the microformat principles.
If there is a specific real world problem (and uses cases) that such an elemental microformat would solve, then it would be worth considering.

Until then it is best to keep the <abbr> datetime concept merely as a microformat design pattern, to be used in _actual_ microformats that have a demonstrated practical need.

-- [http://tantek.com/log/ Tantek]

Excerpt from #microformats Aug 18th. Please edit!

<pre>
Aug 18 15:16:14 <Tantek> DanC, what do you think of RFC3339?
Aug 18 15:17:14 <Tantek> ISO8601 subset
Aug 18 15:17:19 <DanC> Date and Time on the Internet: Timestamps http://www.ietf.org/rfc/rfc3339.txt
Aug 18 15:17:30 <DanC> Klyne is a good guy. I wonder if I talked with him about this.
Aug 18 15:17:32 <Tantek> compat with W3C-NOTE-DATETIME
Aug 18 15:17:50 <Tantek> compat with xsd:dateTime
Aug 18 15:17:57 <Tantek> it's a strict intersection subset
Aug 18 15:17:59 <DanC> I consider W3C-NOTE-DATETIME obsoleted by XML Schema datatype-- yeah.. xsd:dateTime
Aug 18 15:18:32 <Tantek> compare/contrast normatively using xsd:dateTime vs. RFC3339
Aug 18 15:18:41 <Tantek> note: Atom 1.0 chose RFC3339
Aug 18 15:18:50 <Tantek> i would like input from the microformats community on this
Aug 18 15:19:27 <DanC> in what context are you evaluating RFC 3339?
Aug 18 15:19:28 <jcgregorio> http://bitworking.org/news/Date_Constructs_in_the_Atom_Syndication_Format
Aug 18 15:21:24 <DanC> which microformat is the question coming from, Tantek ?
Aug 18 15:23:31 <DanC> " The grammar element time-second may have the value "60" at the end of
Aug 18 15:23:31 <DanC> months in which a leap second occurs" The XML Schema WG is in the 27th level of
leap-second-hell for the past few months, I gather.
Aug 18 15:24:21 <DanC> yeah... here's the scary bit: " Leap seconds cannot be predicted far into the
future. The
Aug 18 15:24:21 <DanC> International Earth Rotation Service publishes bulletins [IERS] that
Aug 18 15:24:21 <DanC> announce leap seconds with a few weeks' warning."
Aug 18 15:26:03 <Tantek> DanC, which microformats? any/all that use datetime fields.
Aug 18 15:26:36 <DanC> hard to give useful advice, then.
Aug 18 15:26:58 <DanC> I expect they'll use datetime fields for different things that have different
cost/benefit trade-offs
Aug 18 15:27:26 <DanC> do you know of any particular differences that matter to anybody?
Aug 18 15:56:43 <KragenSitaker> RFC3339 suggests -07:00, which seems like an improvement over -0700 anyway
Aug 18 15:56:49 <Tantek> Kragen, agreed
Aug 18 15:57:01 <Tantek> RFC3339 is certainly preferable to the ISO8601 subset in iCalendar
Aug 18 16:05:57 <DanC> Tantek's right, Kragen; iCalendar looks like it solves the local timezone
problem but doesn't.
Aug 18 16:06:14 <DanC> and it's true that there's no standard solution to the local timezone problem
Aug 18 16:06:39 <Tantek> so instead of appearing to solve the problem but not solving it, we chose to
provide the ability to *approximate* the local timezone using e.g. "-07:00"
Aug 18 16:06:49 <DanC> the simplest thing is to have people use Z time in hCalendar. But I gather
that's unacceptably unusable?
Aug 18 16:07:35 <Tantek> DanC, yes, the simplest thing is to have everyone use UTC Z
Aug 18 16:07:38 <Tantek> However
Aug 18 16:07:50 <Tantek> it is not *nearly* as usuable/verifiable
Aug 18 16:07:55 <Tantek> as -07:00 etc.
Aug 18 16:08:02 <Tantek> hence the decision to go with the latter
Aug 18 16:08:12 <Tantek> some degree of human verifiability is important here
Aug 18 16:14:21 <Tantek> DanC, my perception is that RFC3339 is a subset
Aug 18 16:17:00 <DanC> time-numoffset = ("+" / "-") time-hour ":" time-minute
Aug 18 16:17:34 <DanC> ok, then I can't see any differences. (modulo recent leap seconds issues that
may affect xsd:dateTime )
Aug 18 16:18:07 <Tantek> would be interesting to know why Atom 1.0 chose RFC3339 over xsd:dateTime
Aug 18 16:18:21 <Tantek> if there was a "real" reason or if it was arbitrary / coin-flip.
</pre>

Here's an exhaustive [http://www.imc.org/atom-syntax/mail-archive/msg13103.html comparison] from ndw. I think xsd:dateTime also allows unqualified local times, while RFC3339 allows only UTC with no known timezone (-00:00). In the end, Atompub followed the advice of [http://www.imc.org/atom-syntax/mail-archive/msg13244.html Sam Ruby] and [http://www.imc.org/atom-syntax/mail-archive/msg13248.html Scott Hollenbeck], our area director. Atom dates make some additional restrictions on RFC3339, such as uppercase T and Z characters for compatibility with xsd:dateTime, RFC3339, W3C-DTF, and ISO8601. --[http://franklinmint.fm Robert Sayre]

<pre>
Aug 18 16:18:43 <KragenSitaker> rfc3339 is pretty short.
Aug 18 16:19:36 <Tantek> DanC, BTW, which came first? REC for xsd:dateTime or RFC3339?
Aug 18 16:19:50 <DanC> RFC3339 is dated July 2002 ...
Aug 18 16:19:54 <KragenSitaker> Right --- and you might be able to understand xsd:dateTime without
reading all of xml schema, you wouldn't be confident of it
Aug 18 16:20:25 <DanC> W3C Recommendation 28 October 2004 ... but that's 2nd ed...
Aug 18 16:20:47 <DanC> W3C Recommendation 02 May 2001
Aug 18 16:22:10 <DanC> I don't see a BNF in http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#dateTime ...
Aug 18 16:22:43 <KragenSitaker> yeah, appendix D of the current xml schema datatypes document seems
a little scanty, actually
Aug 18 16:23:28 <DanC> ah... 2nd ed of http://www.w3.org/TR/xmlschema-2/#date is much more
explicit about syntax.
Aug 18 16:23:30 <KragenSitaker> it's 1100 words but still doesn't give any examples
Aug 18 16:23:35 <DanC> still, it's given in prose and not BNF
Aug 18 16:24:17 <KragenSitaker> sections 3.2.9 through 3.2.14 seem to be the relevant ones around #date
Aug 18 16:24:29 <KragenSitaker> which is another 2200 words
Aug 18 16:24:42 <DanC> wow... they changed the canonical form of date from always-Z to
timezone-allowed between 1st edition and 2nd edition
Aug 18 16:25:01 <Tantek> Kragen, DanC, these are very good analyses
Aug 18 16:25:21 <Tantek> could I ask you to summarize the pros/cons for each in a new section at
end of http://microformats.org/wiki/datetime-design-pattern
Aug 18 16:25:22 <Tantek> ?
Aug 18 16:25:58 <KragenSitaker> rfc 3339 is 4000 words, excluding the last two pages of boilerplate.
Aug 18 16:26:31 <KragenSitaker> so it's actually longer than the datetime-relevant parts of XSD but it
seems much more rigorous and clear
Aug 18 16:28:37 <DanC> my advice is: normatively cite both, and claim they specify the same
syntax, and let anybody who discovers otherwise send you a bug report
with a test case
Aug 18 16:29:12 <KragenSitaker> danc: nice hack
</pre>

The RFC3339 has a mandatory TIME portion of the DATE-TIME. Some vCard/iCalendar DATE-TIME stamps can omit the TIME. For instance, DTSTART, if that is a full day event, then you can omit the time. BDAY in vCard can be respresented by only a DATE. I like the idea of restricting the possible date formats, but i think that TIME should be optional, which it isn't in RFC3339. - [http://suda.co.uk/ brian suda]

RFC 3339 allows lowercase 't' and 'z' while XSD doesn't. Specifying RFC 3339 plus 'T' and 'Z' MUST be caps will make them the same. - [http://bitworking.org Joe Gregorio]

== Code ==
The following regular expression (parsed VERBOSE) should break apart a datetime and cover many lightly broken cases seen in the wild. This has been tested under Python.

<pre><nowiki>
^
(?P<year>\d\d\d\d)
([-])?(?P<month>\d\d)
([-])?(?P<day>\d\d)
(
(T|\s+)
(?P<hour>\d\d)
(
([:])?(?P<minute>\d\d)
(
([:])?(?P<second>\d\d)
(
([.])?(?P<fraction>\d+)
)?
)?
)?
)?
(
(?P<tzzulu>Z)
|
(?P<tzoffset>[-+])
(?P<tzhour>\d\d)
([:])?(?P<tzminute>\d\d)
)?
$
</nowiki></pre>

== See Also ==

* [[Main_Page#Design_Patterns|All microformat design patterns]]
* [[abbr-design-pattern]] is used by [[datetime-design-pattern]]
* HTML 4.01 definition of <code><[http://www.w3.org/TR/REC-html40/struct/text.html#edef-ABBR abbr]></code> element
* RFC [http://www.faqs.org/rfcs/rfc3339.html 3339]: Date and Time on the Internet: Timestamps
* W3C: [http://www.w3.org/TR/NOTE-datetime Note on Datetimes]
* Markus Kuhn: [http://www.cl.cam.ac.uk/~mgk25/iso-time.html A summary of the international standard date and time notation]
* Wikipedia: [http://en.wikipedia.org/wiki/ISO_8601 ISO 8601]

hcard

2006-08-24T16:56:07Z

TerrellRussell: /* Examples in the wild */ added brown.edu

<h1>hCard</h1>

hCard is a simple, open, distributed format for representing people, companies, organizations, and places, using a 1:1 representation of the properties and values of the vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) in [[semantic-xhtml|semantic XHTML]]. hCard is one of several open [[microformats|microformat]] standards suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML.

Want to get started with writing an [[hcard|hCard]]? Use the [http://microformats.org/code/hcard/creator hCard creator] to write up some contact information and publish it, or follow the [[hcard-authoring|hCard authoring tips]] to add hCard markup to your current contact page.

__TOC__

== Specification ==

=== Editor ===
[http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]

=== Authors ===
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]
* [http://suda.co.uk/ Brian Suda]

=== Copyright ===
{{MicroFormatCopyrightStatement2004}}

=== Patents ===
{{MicroFormatPatentStatement}}

=== Inspiration and Acknowledgments ===
Thanks to: my good friend [http://vadim.com/ Vadim] who introduced me to vCard ''many'' years ago, and if I'd only paid more attention then, perhaps I could have helped a lot of people avoid wasting a lot of time reinventing various standards wheels.

== Introduction ==
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), has been broadly interoperably implemented (e.g. Apple's "Address Book" application built into MacOSX).

In addition, many bloggers identify themselves by name and discuss their friends and family. With just a tad bit of structure, bloggers can discuss people in their blog(s) in such a way that spiders and other aggregators can retrieve this information, automatically convert them to vCards, and use them in any vCard application or service.

This specification introduces the '''hCard''' format, which uses a 1:1 representation of the properties and values of the aforementioned vCard standard, in semantic XHTML. Bloggers can both embed hCards directly in their web pages, and style them with CSS to make them appear as desired. In addition, hCard enables applications to retrieve information directly from web pages without having to reference a separate file.

Use the [http://microformats.org/code/hcard/creator hCard creator] and copy the HTML code it generates to your blog or website to publish your contact info.

== Semantic XHTML Design Principles ==
{{semantic-xhtml-design-principles}}

== Format ==
=== In General ===
The vCard standard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) forms the basis of hCard.

The basic format of hCard is to use vCard object/property names in lower-case for class names, and to map the nesting of vCard objects directly into nested XHTML elements.

=== More Semantic Equivalents ===
However, for some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:
* <code>URL</code> in vCard becomes <code><a class="url" href="...">...</a></code> inside the element with <code>class="vcard"</code> in hCard.
* Similarly, <code>EMAIL</code> in vCard becomes <code><nowiki><a class="email" href="mailto:...">...</a></nowiki></code>
* <code>PHOTO</code> in vCard becomes <code><img class="photo" src="..." alt="Photo of ..." /></code> or <code><object class="photo" data="..." type="...">Photo of ...</object></code>
* <code>UID</code> in vCard simply becomes another semantic applied to a specific URL (or EMAIL) for an hCard.

=== Singular vs. Plural Properties ===

For properties which are singular (e.g. "N" and "FN"), the first descendant element with that class should take effect, any others being ignored.

For properties which can be plural (e.g. "TEL"), each class instance should create a instance of that property.

==== Singular properties ====

Singular properties: "FN", "N", "BDAY", "TZ", "GEO", "SORT-STRING", "UID", "CLASS".

All other properties are plural. This list has been derived by analyzing the semantics of the individual properties in vCard RFC2426 and determining logically that they MUST be singular per their semantics. See [[hcard-singular-properties]] for explanations.

==== Plural Properties Singularized ====

Since plural property names become their singular equivalents, even if the original plural property permitted only a single value with multiple components, those multiple components are represented each with their own singularly named property and the the property is effectively multivalued and subject to the above treatment of multivalued properties.

=== Human vs. Machine readable ===

If an <code><abbr></code> element is used for a property, then the '<code>title</code>' attribute of the <code><abbr></code> element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value.

If an <code><a></code> element is used for one or more properties, it must be treated as follows:
# For the "PHOTO" property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for one or more properties, it must be treated as follows:
# For the "PHOTO" property and any other property that takes a URL as its value, the <code>src="..."</code> attribute provides the property value.
# For other properties, the <code><img></code> element's '<code>alt</code>' attribute is the value of the property.

If an <code><object></code> element is used for one or more properties, it must be treated as follows:
# For the "PHOTO" property and any other property that takes a URL as its value, the <code>data="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

=== Value excerpting ===

Sometimes only part of an element which is the equivalent for a property should be used for the value of the property. This typically occurs when a property has a subtype, like TEL. For this purpose, the special class name "<code>value</code>" is introduced to excerpt out the subset of the element that is the value of the property. E.g. here is an hCard fragment for marking up a home phone number:

<pre><nowiki>

home:
+1.415.555.1212

</nowiki></pre>

This hCard fragment could be displayed as:

home: +1.415.555.1212

=== Property Exceptions ===

vCard has several properties which either do not make sense on, or are already implied within the context of a web page. This section explains what to (not) do with them.

# '''NAME''', '''PROFILE''', '''SOURCE''', '''PRODID''', '''VERSION''' properties as defined in Sections 2.1.2, 2.1.3, 2.1.4, 3.6.3, 3.6.9 of RFC 2426. Content publishers MUST NOT use these properties in their hCards, and as such, hCard consumers/parsers MUST IGNORE these properties if they are found within an hCard. Instead. hCard to vCard converters SHOULD use the title of the page where the hCard is found (e.g. the <code><title></code> element in (X)HTML documents) to construct the NAME property, MAY output a PROFILE value of "<code>VCARD</code>" per RFC 2426, SHOULD use the URL of the page where the hCard is found to construct the SOURCE property (e.g. perhaps as a parameter to a URL/service that converts hCards to vCards), for an output vCard stream (e.g. a .vcf file). Only services/applications that output actual vCards should write the PRODID property, with the product identifier for said service/application. Similarly only such services/applications should write the VERSION property, with the value "3.0" (without quotes) per RFC2426 Section 3.6.9.

=== Organization Contact Info ===

If the "FN" and "ORG" properties have the exact same value (typically because they are set on the same element, e.g. class="fn org"), then the hCard represents contact information for a company or organization and should be treated as such. In this case the author MUST also NOT set the "N" property, or set it (and any sub-properties) explicitly to the empty string "". Thus parsers should handle the missing "N" property in this case by implying empty values for all the "N" sub-properties.

=== Implied "n" Optimization ===

Although vCard requires that the "N" property be present, the authors of the vCard specification (RFC 2426) themselves do not include "N" properties in their vCards near the end of the spec (p.38). This apparent contradiction can be resolved by simply allowing the "FN" property to imply "N" property values in typical cases provided in the spec. We do so explicitly in hCard.

If "FN" and "ORG" are not the same (see previous section), and the value of the "FN" property is exactly two words (separated by whitespace), and there is no explicit "N" property, then the "N" property is inferred from the "FN" property. For "FN"s with either one word see below, and for three or more, the author MUST explicitly markup the "N", except for the organization contact info case, [http://microformats.org/wiki/hcard#Organization_Contact_Info see above] for that.

# The content of "FN" is broken into two "words" separated by whitespace.
# The ''first'' word of the "FN" is interpreted as the "given-name" for the "N" property.
# The ''second/last'' word of the "FN" is interpreted as the "family-name" for the "N" property.
# Exception: If the first word ends in a "," comma OR if the second word is a single character (optionally followed by a period "."), then the first word (minus the comma at the end if any) is interpreted as the "family-name" and the second word is interpreted as the "given-name".

This allows simplification in the typical case of people stating:
* given-name (space) family-name
* family-name (comma) given-name
* family-name (comma) given-name-first-initial
* family-name (space) given-name-first-initial (optional period)

=== Implied "nickname" Optimization ===

Due to the prevalence of the use of nicknames/handles/usernames on the Web in actual content published on the Web (e.g. authors of [[hReview|reviews]]), hCard also has an implied "nickname" optimization to handle this.

Similar to the implied "n" optimization, if "FN" and "ORG" are not the same, and the value of the "FN" property is exactly one word, and there is no explicit "N" property, then:

# The content of the "FN" is treated as a "nickname" property value.
# Parsers should handle the missing "N" property by implying empty values for all the "N" sub-properties.

Note: the hCard may have additional explicit "nickname" property values in addition to the implied nickname.

=== Implied "organization-name" Optimization ===

The "ORG" property has two subproperties, organization-name and organization-unit. Very often authors only publish the organization-name. Thus if an "ORG" property has no "organization-name" inside it, then its entire contents MUST be treated as the "organization-name".

=== Tags as Categories ===

Categories in hCard can optionally be represented by tags with rel-tag. When a category property is a rel-tag, the tag (as defined by rel-tag) is used for that category.

=== Root Class Name ===

The root class name for an hCard is "vcard".

=== Property List ===

This is the list of properties (and subproperties, in parentheses, like this) in hCard, taken from vCard:

* fn, n (family-name, given-name, additional-name, honorific-prefix, honorific-suffix), nickname, sort-string
* url, email (type, value), tel (type, value)
* adr (post-office-box, extended-address, street-address, locality, region, postal-code, country-name, type, value), label
* geo (latitude, longitude), tz
* photo, logo, sound, bday
* title, role, org (organization-name, organization-unit)
* category, note
* class, key, mailer, uid, rev
==== type subproperty values ====

The 'type' subproperty in particular takes different values depending on which property it is a subproperty of. These 'type' subproperty values are case-INSENSITIVE, meaning "Home" is the same as "home", as well as multivalued, e.g. a tel can be home and preferred:
<pre><nowiki>
Home (preferred):
+1.415.555.1212

</nowiki></pre>

The following lists are ''informative''. See RFC 2426 sections 3.2.1 ADR, 3.3.1 TEL, and 3.3.2 EMAIL respectively for normative type values. They are repeated here for convenience. Default type subproperty value(s) is(are) first in each list and indicated in ALL CAPS. types may be multivalued.

* adr type: INTL, POSTAL, PARCEL, WORK, dom, home, pref
* tel type: VOICE, home, msg, work, pref, fax, cell, video, pager, bbs, modem, car, isdn, pcs
* email type: INTERNET, x400, pref, "other IANA registered address types"

=== XMDP Profile ===

See [[hcard-profile]] for the [http://gmpg.org/xmdp XMDP] profile of hCard which contains the above complete list of properties, with references to their RFC 2426 definitions.

=== Parsing Details ===

See [[hcard-parsing|hCard parsing]].

== Examples ==

This section is informative.

=== Sample vCard ===

Here is a sample vCard:

<pre><nowiki>
BEGIN:VCARD
VERSION:3.0
N:Çelik;Tantek
FN:Tantek Çelik
URL:http://tantek.com/
ORG:Technorati
END:VCARD
</nowiki></pre>

and an equivalent in hCard with various elements optimized appropriately. See [[hcard-example1-steps| hCard Example 1]] for the derivation.

<pre><nowiki>
<div class="vcard">
<a class="url fn" href="http://tantek.com/">Tantek Çelik</a>
<div class="org">Technorati</div>
</div>
</nowiki></pre>

This hCard might be displayed as:

[http://tantek.com/ Tantek Çelik] 
Technorati

Note: The version information is unnecessary in hCard markup directly since the version will be defined by the profile of hCard that is used/referred to in the 'profile' attribute of the <head> element.

=== More Examples ===

See [[hcard-examples]] for more examples, including all examples from vCard RFC 2426 converted into hCard.

== Examples in the wild ==
This section is '''informative'''.

The following sites have published hCards, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If you have an hCard on your own page, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

=== New Examples ===
Please add new examples to this section.
* [http://www.brown.edu Brown University] now uses hCard on the front page
* [http://www.wideblueyonderweb.co.uk Dunks at Wide Blue Yonder Web Design] has added hCard markup on his [http://www.wideblueyonderweb.co.uk/wbyw/pages/contact.htm contact page] and is looking to implement it on all past & future contact pages for clients.
* [http://southamptonrubberstamp.com Southampton Rubber Stamp Company] now has hCard markup with a vCard download link on every page.
* [http://barefoot-ceramics.com Barefoot Ceramics paint your own pottery studio] (in Newport, South Wales) has added hCard markup to its [http://barefoot-ceramics.com/find#address "Find"] page and other address instances. They hopes to implement hCalendar event lists as soon as an ics to hCalendar PHP class can be found or written.
* IBM is embracing microformats. The [http://www.ibm.com/contact/employees/ IBM Employee Directory] now returns hcards in its query results. Also see the [http://www.ibm.com/shortcuts/ Shortcuts Podcast].
* [http://dsingleton.co.uk/ David Singleton] has added a hCard to his blog.
* [http://www.thestreet.org.au The Street Theatre (Canberra, Australia)] has added hCard markup to its [http://www.thestreet.org.au/contact.htm Contact Us] page. hCalendar markup will soon be added for all of our performances.
* [http://www.informatik.uni-hamburg.de/SVS/personnel/henrich/index.php Henrich C. Pöhls] has marked up his about page using hcard, including his PGP-Key that is stored in an abbr title, using class=key.
* [http://www.yalf.de Yalf Webentwicklung] has [http://www.yalf.de/kontakt contact information] available as hCard (and vCard).
* [http://www.zeldman.com/about/ Jeffrey Zeldman]. Jeffrey Zeldman has marked up his about page using hcard.
* [http://WhereAreYouCamping.com Where Are You Camping]. hCards for all members and camps, employing the include pattern as well. AFAIK this is the first Burning Man related microformats implementation, not to mention addresses in Black Rock City.
* [http://www.clacksweb.org.uk Clackmannanshire Council ]. hCard is implemented for all contact details across the site, and for specific individuals such as elected members (Councillors).
* [http://www.webdirections.org Web Directions ]. hCard is used as contact information for the conference, while speakers are marked up with hCard.
* [http://www.markthisdate.com/contactform.html MarkThisDate.com ]. An hCard is implemented on our contactform. For our calendars hCalendars will follow as soon as possible.
* [http://www.msiinet.com/contact/ MSI Systems Integrators] has its "Contact MSI" page encoded with hCards.
* [http://www.coolblue.nl/ Corporate website of Coolblue BV]. hCards were implemented in both the footer of each page, and in the "News" section for press contact information.
* [http://www.besancon.fr/index.php?p=32 Official site of Besançon (France)] uses hCard for each page concerning the small towns surrounding Besançon.
* [http://2006.dconstruct.org/speakers/ d.Construct 2006 conference speakers list] is implemented using hCards.
* [http://local.yahoo.com Yahoo Local] now supports hCards for business and places in the search results
* [http://learningtheworld.eu/imprint/ Learning the World] has hcard information on the imprint, alas we didn't succeed to mark-up the work phone and fax numbers properly.
* The [http://www.fuckparade.org F’parade] website uses hcard, though I didn't find a type to distinguish mobile and landline phone numbers.
* [http://www.miranet.nl/contact.htm Miranet Webdesign] have added a hcard to their [http://www.miranet.nl/contact.htm 'contact' page]
* [http://weblog.200ok.com.au/ Ben Buchanan] has added a vCard to the [http://weblog.200ok.com.au/about/ 'About' page on The 200ok Weblog]
* [http://www.radiantcore.com Radiant Core] has their contact information [http://www.radiantcore.com/contact/ available in hCard].
* [http://www.mikerumble.co.uk/ Mike Rumble] has [http://www.mikerumble.co.uk/contact.html uploaded his hCard].
* [http://www.saumag.edu/ Southern Arkansas University] has its contact footer encoded as hCard
* [http://main.uab.edu/ University of Alabama at Birmingham] has its contact footer encoded as hCard
* [http://www.capital.edu Capital University] has contact footer and bloggers' names encoded as hCard. Also, all page-specific contact information is encoded as hCards (see [http://www.capital.edu/Internet/Default.aspx?pid=67 Admissions] page for an example)
* [http://main.uab.edu/shrp/ UAB School of Health Professions] uses hCard in its contact footer
* [http://green.carisenda.com/ Stephen Stewart] has his hCard on the front page of his weblog ('You are here' section)
* [http://www.fberriman.com/ Frances Berriman] has a hidden vCard in the footers of her website.
* [http://www.candlescience.com/ CandleScience Candle Supply] added a hidden hcard sitewide.
* [http://www.direction.es/ Direction] uses hCard for contact information.
* [http://audiobank.tryphon.org AudioBank] uses hCard to display member informations.
* [http://www.vivabit.com/atmedia2006/speakers/ @media speakers] are marked up with hCard (photos depend on BASE tag support which makes this a good test case)
* [http://www.dougransom.com Doug Ransom] uses hCard for his financial advisory practice.
* [http://rubyandrails.org/usergroups/newcastle/members.html ncl.rb] uses hCard for contact information.
* [http://www.snowinteractive.com/ Snow Interactive] uses hCard for contact information.
* [http://flickr.com Flickr] now supports [[hcard|hCard]] and [http://gmpg.org/xfn XFN] on profile pages. See [http://flickr.com/photos/factoryjoe/113866484/ screenshot of Flickr UI in Flock browser using Flocktails extension - March 17th 2006].
* [http://www.ndiyo.org/contact Contact information for the Ndiyo project]
* [http://www.pixelenvy.co.uk/ Pixel Envy] uses hCard for contact information on every page
* [http://stilbuero.de/contact/ Klaus Hartl] uses hCard in the sidebar for contact information (maybe easier to parse through delivering xhtml as xml).
* [http://charlvn.virafrikaans.com/contact Charl van Niekerk's hCard]
* [http://billy-girlardo.com/WP/ BillyBLOGirlardo] uses hCard for contact information.
* [http://www.hicksdesign.co.uk/ Hicksdesign] uses hCard for contact information.
* http://www.gr0w.com/articles/press/growsearch_launched_press_release/ - hCard in a press release for the press contact info
* http://www.redmonk.com/cote/archives/2006/03/testing_out_mic.html - hCard with explanation
* [http://andy.ciordia.info/ it's my island], personal blog, hcard on the ''[http://andy.ciordia.info/pages/about_me About the Writer]'' page. [[User:Ciordia9|Andy Ciordia]]
* [http://www.windowonwoking.org.uk/ Window on Woking], a local community site in the UK, uses hCard in the homepage of each member organisation and local Councillor.
* [http://ChunkySoup.net/ ChunkySoup.net] has redesigned using hAtom 0.1 and hCards on the entire site -- by [[User:ChrisCasciano|Chris Casciano]]
* [http://www.30boxes.com/ 30 Boxes],a social calendar application and digital lifestyle aggregator, automatically creates an hcard for you with your account. It is found under Settings > Syndication.
* [http://www.nearwhere.com/ Nearwhere.com] allow you to put an hcard on an interactive map.
* [http://www.brentozar.com/ Brent Ozar] added a [http://www.brentozar.com/contact.php contact] page hCard.
* [http://www.kerihenare.com/ Keri Henare] has rewritten his [http://www.kerihenare.com/contact/ contact] page hCard. Now using <code><object></code> instead of <code><img></code> for photo. (Thanks Brian Suda for updating the vCard converter)
* [http://michaelraichelson.com/contact/ Michael Raichelson] had an hCard on his contact page before SXSW, but never thought to add it here until Tantek requested it.
* [http://www.commoner.com/~lsimon/lindsey_simon_hcard.html Lindsey Simon] has added an hCard to his website as per Tantek's SXSW request for folks to try it
* [http://www.davidgagne.net/ David Gagne] has an hCard in his sidebar.
* [http://www.churchzip.com/map/ Churchzip.com/map] and [http://www.skiwhere.com/map/ Skiwhere.com/map], provide churches, hotels, and ski resorts on the same maps. Locations are formatted as hcards.
* All [http://www.iqdir.com/ IQ Directory Solutions] Yellow Pages web portals use [[hcard|hCard]] markup on listings. For example [http://www.yellowpages-cambodia.com/ Cambodia Yellow Pages] and [http://www.superpages.com.my/ Malaysia Super Pages]
* Ning's cloneable Group app uses fuzzy matching to map custom fields to [[hcard|hCard]] markup on its [http://group.ning.com/index.php?controller=person&action=view&content=JonathanAquino profile] pages.
* [http://claimid.com/factoryjoe Chris Messina' ClaimID hCard]
* [http://factoryjoe.com/blog/hcard Chris Messina' hCard]
* [http://flock.com/about Flock About]
* [http://tantek.com/microformats/2006/03-01-TechPlenAgenda.html Agenda: W3C Technical Plenary Day, March 1 2006] has [[hcard|hCard]] and [[hcalendar|hCalendar]] markup. ([http://www.w3.org/2006/03/01-TechPlenAgenda.html original here]).
* [http://www.gr0w.com/articles/press/growsearch_launched_press_release/ GrowSearch Launched (Press Release)] uses an hCard to provide Press Contact Point.
* The [http://www.arborday.org/ National Arbor Day Foundation] has started using hCards for their [http://arborday.org/programs/conferences/communityforestry/index.cfm upcoming] [http://arborday.org/programs/conferences/hazardtrees-treeplanting/ conferences].
* [http://www.multipack.co.uk The Multipack] has numerous hCards, especially on the [http://www.multipack.co.uk/members/ members page], as well as the next meeting information.
* [http://deadringrancor.livejournal.com/ Justin McDowell] used an hCard when [http://deadringrancor.livejournal.com/221332.html referring to a person in his blog post]
* [http://davecardwell.co.uk/cv/ Dave Cardwell] has included his hCard in his Curriculum Vitae.
* [http://blog.usweb.com/ Shaun Shull] has written a great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], and has included his [[hcard|hCard]] as one of the examples.
* [http://www.thefutureoftheweb.com/ Jesse Skinner] has written a simple [http://www.thefutureoftheweb.com/blog/2006/1/hcard tutorial with examples]
* [http://www.w3.org/2005/12/allgroupoverview.html 2006 W3C Technical Plenary Week] has marked up the venue, contacts, and program committee members all with hCard.
* [http://www.avf-nexus.co.uk AVF-Nexus] have a hCard on their [http://www.avf-nexus.co.uk/contact/ contact page] - (by [http://creation.uk.com Creation"])
* [http://www.thefantasticos.com/andrew/ Andrew White] posted [http://www.thefantasticos.com/andrew/index.php/my-hcard/ his hCard] and [http://www.thefantasticos.com/andrew/index.php/62/microformats-the-should-have-been-obvious-web-dev-tool/ blogged about it].
* [http://www.2sheds.ru Oleg "2sheds" Kourapov] in his [http://www.2sheds.ru/blog/ blog] ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog X2V]) has turned personal profile into hCard ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/hcard.html X2V]) and his blogroll - into combination XFN/hCards ([http://suda.co.uk/projects/X2V/get-vcard.php?uri=http://www.2sheds.ru/blog/friends.html X2V])
* [http://www.approveddesign.co.uk Approved Design Consultancy] have a hCard on their [http://www.approveddesign.co.uk/about/contact/ contact page] as well as on their [http://www.approveddesign.co.uk/about/people/ people section] - (by [http://creation.uk.com Creation"])
* [http://weblog.200ok.com.au/ Ben Buchanan] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&format=search Colin Morris] have [http://weblog.200ok.com.au/2006/01/griffith-phonebook-adds-hcard-and.html implemented hCards and vCards] for the [http://www.griffith.edu.au Griffith University] [http://www.griffith.edu.au/find/content_phonebook.html online phone book]. Eg. [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=ben+buchanan&format=search Ben's vCard] and [http://www.griffith.edu.au/cgi-bin/phone_search.pl?string=colin+morris&format=search Colin's vCard]
* WWF-Australia [http://wwf.org.au/about/contactdetails/ contact details page]
* [http://rasterweb.net/raster/ Pete Prodoehl] used the hCard format on his [http://rasterweb.net/raster/contact.html Contact page]
* [http://alexander-mette.de amette] uses the hCard format in a module of his TikiWiki powered blog
* [http://staff.washington.edu/oren/weblog2/ Oren Sreebny] has an hcard on his blog main index template
* [http://www.cs.brandeis.edu/~zippy/ Patrick Tufts] has an hCard on his homepage.
* [http://ascii20.blogspot.com/ Mathias Kolehmainen and Jamie Taylor] have hCards on their weblog.
* [http://www.hoppsan.org/jamesb/blogger/ Barnaby James] has a hCard on his weblog.
* [http://esa-education.com/schools/map ESA Education] Uses hCards for their 100+ schools and each of the individual school sites.
* [http://www.thereisnocat.com/#vcard Ralph Brandi] has added an hCard to the sidebar of his weblog as a result of Tantek Çelik's portion of the Microformats presentation at SXSW 2006.
* [http://www.pierce.ctc.edu/ephone/ Pierce College] -- community college directory uses hCard on all individual directory entries.
* [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/ the Institutional Web Management Workshop 2006] have marked up all their [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/committee/ speakers with hCard].
* http://wikitravel.org/en/Singapore/Sentosa. Wikitravel is experimenting with hcard on its travel guides. This guide uses hcard for all its business listings. More info on http://wikitravel.org/en/Wikitravel_talk:Listings.
* [http://www.musik-erber.de/ Musik-Erber] uses to present contact information at the sidebar
* [http://cdevroe.com/about/#contact Colin D. Devroe] uses hCard to display his contact information on his about page
* The ECS (Scool of Electronics and Computer Science at the University of Southampton) [http://www.ecs.soton.ac.uk/people People Pages] use vCard. Contact cjg@ecs.soton.ac.uk if there's any bugs.
* [http://www.southwestern.edu/~ramseyp Pat Ramsey] has his contact information on his blog marked up with hCard. Contact [mailto:ramsey.pat@gmail.com ramsey.pat@gmail.com] if there are any bugs there.
* [http://www.meryl.net/ Meryl K. Evans] has a hidden hCard on her homepage.
* [http://www.vyre.com/company/contact-us/ VYRE] is a CMS development company with a "contact us" hCard
* [http://www.lefdal.cc/info.php Alf Kåre Lefdal] uses hCard in the markup of his contact information
* [http://www.pignwhistle.com.au/ Pig N Whistle, a chain of pubs in Brisbane, Australia] is using hcard to mark up all the contact pages for its outlets and head office
* [http://kollitsch.de/ Patrick Kollitsch] has built his personal Profil as hCard
* [http://www.hbs.edu/faculty/dspar/ Harvard Business School] has hCards on their faculty pages
* [http://openmikes.org/ openmikes.org] uses hCards for open mike venue addresses in its listing detail pages.

=== Examples ===
* [http://shiftingpixel.com/about/the-artist shifting pixel photoblog] has published an hCard.
* [http://thoughtport.blogspot.com/ Aiden Kenny] hasn't published his hCard yet, but he has [http://thoughtport.blogspot.com/2005/07/elemental-particles-of-web.html published his hCard icon]: http://photos1.blogger.com/blogger/4224/444/320/AK-Hcard-icon.gif
* [http://thedredge.org Andy Hume] uses hCards to mark-up the names and URLs of commentors on his blog, e.g. his [http://thedredge.org/2005/06/using-hcards-in-your-blog/ blog post on "Using hCards in your blog"].
* [http://www.bidclix.com/ BidClix]'s [http://www.bidclix.com/AboutContact.html Contact BidClix] page has it's ''contact info'' marked up with an hCard.
* [http://suda.co.uk/ Brian Suda] has managed to embed a photo in [http://suda.co.uk/contact/ his hCard] through the [http://www.ietf.org/rfc/rfc2397.txt data uri scheme] by converting the image to BASE64 code. View the Source to see how this is accomplished. [http://suda.co.uk/projects/X2V/get-vcard.php?uri=http%3A//suda.co.uk/contact/ The X2V link] will extract the image and encode it for a vCard which will be displayed in some address book applications.
** Inspired by this I thought to try the same for SVG at [http://barefoot-ceramics.com/find Barefoot] ...
** <img class="photo" style="display:none;" src="data:image/svg+xml;text,<?xml version='1.0' encoding='UTF-8' standalone='no'?><svg xmlns:svg='http://www.w3.org/2000/svg' xmlns='http://www.w3.org/2000/svg' version='1.0' width='50' height='80' id='svg3957'><defs id='defs3959' /><path d='M 28.91433,...32.192802 z' style='fill:#cc4d00;fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:0.625;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1' id='path9551' /></svg>" alt="Barefoot">
** Does it work?? Well it parses OK. Some automated tools replace the < with %3C (etc., eg Brian Suda's vcard form). Unfortunately Kontact (KDE contacts tool) doesn't handle SVG as a vCard photo or logo format - I don't know if this is a standard. It seems it could work and maybe even does somewhere. Maybe the text field needs to be Base64 encoded? ... see [http://slashdot.org/~pbhj/journal/142382 pbhj's slashdot journal] for a bit more on this.
* [http://cinematreasures.org Cinema Treasures] uses hCard to markup venue information for 10,000+ movie theaters.
* [http://www.w3.org/People/Connolly/events/ Dan Connolly's index of events and talks] has hCards for many of the people he has met at those events. In Mar 2006, he moved a bunch of hotel contact info from his PDA to this page; it's now up to 32 hCards.
* [http://doncrowley.blogspot.com/ Don Crowley] has published [http://www.crowley.nl/hcard.html his hCard] as well as a nifty hCard button: http://www.crowley.nl/images/hcard.png
* [http://loadaveragezero.com/hnav/contact.php Douglas W. Clifton] added all types of contact information
* [http://eventful.com Eventful] publishes all of its venue information pages with embedded hCards.
* [http://www.iowamilitaryveteransband.com/members/ Iowa Military Veterans Band Contacts] - 95 hCards [http://weblog.randomchaos.com/archive/2005/10/24/Microformats/ marked up by Scott Reynen]
* [http://JackWolfgang.blogspot.com Jack L. Wolfgang II] has [http://jack.randomata.com/resume/ converted the addresses in his resume to hCards].
* [http://www.efas.fupl.asso.fr/efas/_Mathieu-Drouet_.html Mathieu Drouet] and [http://www.efas.fupl.asso.fr/efas/_Annie-Leger_.html Annie Leger] both have hCards
* [http://www.ndunn.com Neil Dunn] has published his rather [http://www.ndunn.com/2005/10/7/hCard good looking hCard]
* [http://www.oliverbrown.me.uk/ Oliver Brown] has published his hCard.
* [http://www.paradigmproductions.org/contact/ Paradigm Productions] published a vcard as a ul (marked up by [http://www.linkingarts.com/ Peter Jacobson])
* [http://www.splintered.co.uk/ Patrick H. Lauke] has marked up [http://www.splintered.co.uk/about/ his contact info with hCard].
* [http://blah Paul Schreiber has published his hCard on [http://paulschreiber.com/about/?contact his about page].
* [http://paulschreiber.com/blog/ Paul Schreiber]'s [http://concerts.shrub.ca/ Sunnyvale House Concerts] site publishes hCards for upcoming artists, as well as an hCard for the page itself. In addition the [http://concerts.shrub.ca/shows Past Shows] page contains hCards for all past artists.
* [http://www.paulmichaelsmith.com/blog/hcard.htm Paul Smith] has created an hCard page which is Human Readable, and a link to X2V passing the same hCard page to generate a vCard.
* [http://www.windley.com/archives/2005/07/hcards_trying_o.shtml Phil Windley has published] [http://phil.windley.org/hcard.html his hCard].
* [http://www.go-curiosity.com/about.htm Piercarlo Slavazza] has published an hCard.
* [http://zooibaai.nl/ Rob Mientjes] has published his hCard on [http://zooibaai.nl/about/ his about page].
* [http://rbach.priv.at/Contact Robert Bachmann] has published his hCard and [http://rbach.priv.at/Images/hcard a button].
* [http://blah Scott Reynen has published his hCard on [http://www.randomchaos.com/document.php?source=scott_reynen his profile page].
* [http://www.stackframe.com/ StackFrame, LLC] has published [http://www.stackframe.com/people/ employee] and [http://www.stackframe.com/contact/ general] contact information as hCards.
* [http://www.wolfsreign.com Steven Ametjan] has published his hCard on [http://www.wolfsreign.com/about/ his about page].
* [http://tantek.com/microformats/2005/syndicate/speakers-list.html Syndicate - Speaker List] as a set of hCards
* [http://tagcamp.org/index.cgi?ContactList TagCamp contact list]
* [http://tantek.com/log Tantek's Thoughts] includes an inline author hCard at the bottom of the page.
* [http://technorati.com/ Technorati]'s [http://www.technorati.com/about/ About page] lists their '''Media Contact'''
* [http://www.deadringerart.com/ The Brothers McDowell] have hCards at their Contact page.
* [http://twinsparc.com/ Twinsparc] put an hCard in the header and footer of all their pages.
* [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 Conference speakers page marked up with hCard]
* [http://we05.com/ Web Essentials 05] marked up all their [http://we05.com/presenters.cfm presenters with hCard].

=== Examples with some problems ===

* [http://gbraad.nl/ Gerard Braad] has published an example on his [http://gbraad.nl/site/?p=profile profile] page that is almost consistent with his original [http://gbraad.nl/files/gbraad.vcf vCard] file. Also progress is made for transforming his [http://files.gbraad.nl/foaf.rdf FoaF] file to a hCard encoded representation. (also done for my spouse:[http://spouse.gbraad.nl/site/?p=profile Yong Yuan])
** (2005-09-27) PASSED, PASSED
** WARNINGS
*** uses 'n given-name' and 'n family-name' instead of nesting the given- and family- names inside the 'n'
*** has one 'tel' value with a bunch of values stuffed in
*** probably more problems --[[User:RyanKing|RyanKing]] 17:19, 5 Jan 2006 (PST)
* [http://kinrowan.net/ Cori Schlegel] [http://kinrowan.net/blog/wp/archives/2005/07/08/a-problem-with-the-structured-blogging-plug-in-for-wordpress/ discusses how he has updated] [http://kinrowan.net/blog/contact his contact page with hCard]
** INVALID - using 'prefix' instead of 'honorific-prefix' and type's in classnames (in both adr and tel) and has two photo's (the second could be 'logo') --[[User:RyanKing|RyanKing]] 15:15, 5 Jan 2006 (PST)
* The good ship [http://styrheim.com/test/leonid.html Leonid Miloslavskiy] spotted in the North Atlantic
** INVALID --[[User:RyanKing|RyanKing]] 00:50, 27 Oct 2005 (PDT)
*** class="family" should probably be family-name
*** the "n" property is missing and the "n" optimization can't be applied
*** the first geo propery is empty, the second one is invalid (ie, it doesn't contain lat/long)
* [http://landsbank.fo/#hCard Landsbanki Føroya]
** INVALID - using embedded rdf/xml invalidly
* [http://chrischerry.name/blog/contact/ Chris Cherry's contact page with his hCard]
** WARNING - uses class="cell" instead of cell
* [http://www.bath.ac.uk/contact/ University of Bath] Person Finder results are encoded with hCards so you can easily create a vCard from any result.
** ERROR - attempt to use Implied-N optimization where that's not possible. --[[User:RyanKing|RyanKing]] 14:29, 5 Jan 2006 (PST)
** Error appears for external users only. Won't be fixed any time soon. -- [[User:PhilWilson|PhilWilson]] 00:03, 28 Jan 2006 (GMT)
* [http://richi.co.uk/blog/2005/12/structured-blogging.html Richi Jennings] has put up his attempt
** INVALID, missing FN --[[User:RyanKing|RyanKing]] 12:47, 5 Jan 2006 (PST)
* [http://www.yellowpencil.com/contact/ Yellow Pencil] Using microformats to present company contact information
** First hcard has empty "fn" and no "n". "fn" should be with "org" -- [[User: ScottReynen |ScottReynen]] 21:29, 19 Jun 2006 (CST)

== Implementations ==
This section is '''informative'''.

The following implementations have been developed which either generate or parse hCards. If you have an hCard implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.
* [http://placenamehere.com/mf/nnwextract/ Extract Microformats] is a script for NetNewsWire that supports extracting hCard and hCalendar data in blog posts (via technorati service). Written by [[User:ChrisCasciano|Chris Casciano]]
* [http://allinthehead.com/hkit/ hKit] is an open source PHP 5 parsing library with support for hCard.
* [http://kitchen.technorati.com/search Technorati Microformats Search] indexes [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] as [http://tantek.com/log/2006/05.html#d31t1802 announced by Tantek].
** list of pages with indexing Issues so they can be looked into as to why data is not being extracted
** suda.co.uk/contact
** multipack.co.uk

* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of hCards from within Dreamweaver 8.
* [http://scooch.gr0w.com/ Scooch] is a slide show and presentation creator that generates a [[hCard]] for individual slide show authors and comment authors with a CSS button to parse and download via [http://suda.co.uk/projects/X2V/ X2V]. Also uses [[hReview]] for slide ratings and [[rel-tag]] for categories.
* [http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar
*[http://opensource.reevoo.com/2006/03/08/release-uformats-12/ uformats] is a ruby library that can parse [[hCalendar]], [[hCard]], [[hReview]] and [[rel-tag]]
* [http://blog.codeeg.com/tails-firefox-extension/ Tails] is a Firefox Extension that will display the presence and details of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage. [https://addons.mozilla.org/firefox/2240/ Tails Export] is an extended version.
* [http://www.stripytshirt.co.uk/features/firefox/smartzilla Smartzilla is a Firefox Extension] that finds hCards on web pages and lets you add them to your addressbook.
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCard and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* There is [http://flickr.com/photos/factoryjoe/68755089/ evidence of built-in hCard support in the Konqueror browser]. Specifically, Konqueror 3.5, in KDE 3.5 (kubuntu Breezy w/ update).
* There is [http://tagcamp.org/index.cgi?ContactList evidence of a kwiki plugin for hCards]. Update: the [http://svn.kwiki.org/cwest/Kwiki-hCard/ hCard kwiki plugin svn repository]. See the [http://microwiki.caseywest.com/index.cgi?hCard documentation of the hCard kwiki plugin].
* [http://suda.co.uk/projects/X2V/ X2V] is a bookmarklet that parses hCard and produces a .vcf (vCard) stream. Note: needs to be updated as the spec is refined
* [http://www.stripytshirt.co.uk Duncan Walker] has built [http://www.stripytshirt.co.uk/features/firefox/smartzilla a Firefox extension] that gets hCard data from a webpage, uses Brian Suda's XSL (locally) to transform it to vcard format and opens the resulting .vcf file.
* [http://george.hotelling.net/90percent/ George] has written a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script] that detects hCards and allows users to easily add them to their address book application. Relies on the X2V web service to do the conversion.
* [http://inside.glnetworks.de/ Martin Rehfeld] has updated the work of [http://blogmatrix.blogmatrix.com/ David Janes] and produced a [[Greasemonkey]] [http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ script] that finds many microformat elements, including hCards, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. The hCard to vCard conversion is done internally within the script. ''This will work with FireFox 1.5+/GreaseMonkey 0.6.4+ now.''
* [http://diveintomark.org/ Mark Pilgrim] has also written an [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser Greasemonkey user script]. It is self-contained and does not rely on the X2V web service.
* [http://www.oliverbrown.me.uk/2005/09/03/a-working-microformats-extension-to-simplexml/ Oliver Brown] has written an "extension" to [http://www.php.net/simplexml SimpleXML] that gives simple access to hCard information in PHP 5.
* [http://thedredge.org/ Andrew D. Hume] has built a system (Wordpress plugin?) for [http://thedredge.org/2005/06/using-hcards-in-your-blog/ using hcards in your blog] to represent people leaving comments on blog posts.
* The [http://tantek.com/microformats/hcard-creator.html hCard creator] is a very simple, yet illustrative, open source user interface / form / script which creates an hCard in real-time as you type in a set of contact information.
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate hCard information ([http://ietf.org/rfc/rfc2629 RFC2629] is an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - Open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards.
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] is a collection of palmpilot and sidekick tools. It includes X2V derivatives xhtml2hcard.xsl and toICal.xsl plus some [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest] materials
* [http://www.openpsa.org/ OpenPsa 2.x] CRM application uses hCard for all person listings. The widget is [http://www.midgard-project.org/midcom-permalink-922834501b71daad856f35ec593c7a6d reusable across Midgard CMS]
* [http://www.metonymie.com Emiliano Martínez Luque] has written an experimental [http://www.metonymie.com/hCard_extract/app.html hCard finder and structured search application] that finds hCards within a given set of URLs and returns the ones that match the specified search criteria.
* [http://randomchaos.com/microformats/base/ Microformat Base] is an open-source PHP microformat aggregation crawler, currently recognizing hreview, hcalendar, and hcard.

== Additional Applications ==
This section is '''informative'''.

There are numerous potential additional uses and applications for hCards on the Web. The following are merely a few thoughts and possibilities that folks have come up with:

* As an open standard/format for [http://www.gravatar.com/ Gravatars].
* Marking up individual authors of blog posts on a group blog
* Marking up people's names and URLs in a blogroll
* Any reference to people in blog posts (e.g. when citing them, or referencing them, or describing them, by name).
* ...

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426]

=== Informative References ===
* [http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426]
* [http://w3.org/TR/REC-CSS1 CSS1]
* [http://tantek.com/log/2004/09.html#hcard hCard term introduced and defined on the Web, 20040930]
* [http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats FOO Camp 2004 Simple Semantic Formats presentation, 20040910]
* Contributed from http://developers.technorati.com/wiki/hCard.
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]

==== Specifications That Use hCard ====
* [[adr]]
* [[geo]]
* [[hcalendar|hCalendar]]
* [[hreview|hReview]]

==== Similar Work ====
* [http://www.intertwingly.net/wiki/pie/PaceBetterPersonElement Atom PaceBetterPersonElement]
* [http://www.jabber.org/jeps/jep-0054.html JEP-0054: vcard-temp]

== Related Pages ==
* [http://microformats.org/code/hcard/creator hCard creator] ([[hcard-creator-feedback|feedback]]) - create your own hCard.
* [[hcard-authoring|hCard authoring]] - learn how to add hCard markup to your existing contact info.
* [[hcard-faq|hCard FAQ]] - If you have any questions about hCard, check here, and if you don't find answers, add your questions!
* [[hcard-parsing|hCard parsing]] - Normatively details of how to parse hCards.
* [[hcard-issues|hCard issues]] - Please add any issues with the specification to the issues page.
* [[hcard-profile|hCard profile]] - The XMDP profile for hCard

This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.

* [[hcard-brainstorming|hCard Brainstorming]] - where we are keeping our brainstorms and other explorations relating to hCard
* [[hcard-tests|hCard tests]] - a wiki page with actual embedded hCards to try parsing.

== Further Reading ==
* [http://www.digital-web.com/articles/microformats_primer/ Digital Web Magazine: Microformats Primer] by Garrett Dimon has a good intro to hCard
* [http://24ways.org/advent/practical-microformats-with-hcard Practical Microformats with hCard] by Drew McLellan
* [http://thedredge.org/ Andrew D. Hume] has written a blog post on [http://usabletype.com/articles/2005/usable-microformats/ usable microformats] which discusses hCard
* [http://www.thefutureoftheweb.com/blog/2006/1/hcard Jesse Skinner's introduction to hCard]
* [http://blog.usweb.com/ Shaun Shull's] great post on [http://blog.usweb.com/archives/how-microformats-affect-search-engine-optimization-seo How Microformats Affect SEO], including his [[hcard|hCard]] as an example.
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page] and the [http://technorati.com/tags/hcard hCard tag]

citation-formats

2006-08-05T22:10:22Z

TerrellRussell: /* MODS (Metadata Object Description Schema) */

= Citation Formats =

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

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

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

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

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

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

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

* abstract refines description.
* accessRights refines rights

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

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

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

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

== NLM Journal Publishing DTD ==

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

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

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

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

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

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

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

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

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

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

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

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

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

@article{XAi_HSCheng_1994a,

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

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

===Bib-enabled Applications===

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

====Desktop Applications====
* [http://www.endnote.com EndNote] (Large market share)
* [http://bibdesk.sourceforge.net/ BibDesk]
* [http://www.mackichan.com/index.html?bibdb/default.htm~mainFrame BibDB]
* [http://sourceforge.net/projects/bib-it/ Bib-it]
* Large list of other apps at [http://dmoz.org/Computers/Software/Typesetting/TeX/BibTeX/ dmoz] and [http://en.wikipedia.org/wiki/BibTeX#Software Wikipedia]

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

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

== RIS ==

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

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

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

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

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

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

== OpenURL ==

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

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

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

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

</nowiki>
</pre>

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

=== Example ===

<pre>
<nowiki>

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

</nowiki>
</pre>

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

== The OpenURL Briefly Explained ==

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

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

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

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

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

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

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

== DocBook ==

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

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

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

== Ann Arbor District Library XML feed ==

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

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

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

== SimpleDC supported by the zoom toolkit ==

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

this is the output of marc.toSimpleDC()

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

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

== SRU from the Library of Congress ==

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

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

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

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

</nowiki>
</pre>

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

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

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

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

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

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

common location information
* volume
* issue
* page
* edition

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

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

Other fields
* Copyright/usage
* audience

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

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

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

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

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

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

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

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

== ISBN Uniform Resource Names ==

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

Example:

URN:ISBN:0-395-36341-1

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

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

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

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

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

citation-formats

2006-08-05T22:09:49Z

TerrellRussell: /* Dublin Core Metadata */

= Citation Formats =

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

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

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

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

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

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

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

* abstract refines description.
* accessRights refines rights

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

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

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

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

== NLM Journal Publishing DTD ==

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

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

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

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

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

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

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

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

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

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

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

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

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

@article{XAi_HSCheng_1994a,

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

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

===Bib-enabled Applications===

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

====Desktop Applications====
* [http://www.endnote.com EndNote] (Large market share)
* [http://bibdesk.sourceforge.net/ BibDesk]
* [http://www.mackichan.com/index.html?bibdb/default.htm~mainFrame BibDB]
* [http://sourceforge.net/projects/bib-it/ Bib-it]
* Large list of other apps at [http://dmoz.org/Computers/Software/Typesetting/TeX/BibTeX/ dmoz] and [http://en.wikipedia.org/wiki/BibTeX#Software Wikipedia]

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

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

== RIS ==

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

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

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

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

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

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

== OpenURL ==

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

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

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

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

</nowiki>
</pre>

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

=== Example ===

<pre>
<nowiki>

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

</nowiki>
</pre>

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

== The OpenURL Briefly Explained ==

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

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

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

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

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

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

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

== DocBook ==

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

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

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

== Ann Arbor District Library XML feed ==

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

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

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

== SimpleDC supported by the zoom toolkit ==

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

this is the output of marc.toSimpleDC()

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

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

== SRU from the Library of Congress ==

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

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

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

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

</nowiki>
</pre>

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

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

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

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

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

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

common location information
* volume
* issue
* page
* edition

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

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

Other fields
* Copyright/usage
* audience

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

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

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

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

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

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

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

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

== ISBN Uniform Resource Names ==

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

Example:

URN:ISBN:0-395-36341-1

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

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

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

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

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

citation-formats

2006-08-05T22:08:52Z

TerrellRussell: /* Comparison chart */

= Citation Formats =

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

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

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

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

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

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

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

* abstract refines description.
* accessRights refines rights

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

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

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

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

== NLM Journal Publishing DTD ==

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

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

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

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

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

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

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

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

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

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

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

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

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

@article{XAi_HSCheng_1994a,

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

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

===Bib-enabled Applications===

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

====Desktop Applications====
* [http://www.endnote.com EndNote] (Large market share)
* [http://bibdesk.sourceforge.net/ BibDesk]
* [http://www.mackichan.com/index.html?bibdb/default.htm~mainFrame BibDB]
* [http://sourceforge.net/projects/bib-it/ Bib-it]
* Large list of other apps at [http://dmoz.org/Computers/Software/Typesetting/TeX/BibTeX/ dmoz] and [http://en.wikipedia.org/wiki/BibTeX#Software Wikipedia]

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

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

== RIS ==

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

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

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

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

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

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

== OpenURL ==

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

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

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

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

</nowiki>
</pre>

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

=== Example ===

<pre>
<nowiki>

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

</nowiki>
</pre>

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

== The OpenURL Briefly Explained ==

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

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

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

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

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

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

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

== DocBook ==

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

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

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

== Ann Arbor District Library XML feed ==

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

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

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

== SimpleDC supported by the zoom toolkit ==

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

this is the output of marc.toSimpleDC()

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

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

== SRU from the Library of Congress ==

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

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

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

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

</nowiki>
</pre>

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

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

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

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

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

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

common location information
* volume
* issue
* page
* edition

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

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

Other fields
* Copyright/usage
* audience

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

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

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

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

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

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

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

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

== ISBN Uniform Resource Names ==

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

Example:

URN:ISBN:0-395-36341-1

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

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

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

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

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

User:TerrellRussell

2006-07-28T19:31:28Z

TerrellRussell:

[http://terrellrussell.com Terrell] is a [http://sils.unc.edu/people/phd.html#russell PhD student in SILS at UNC-CH] and half of the team behind [http://claimid.com/people claimID].

He writes [http://weblog.terrellrussell.com here].

His claimID page is [http://claimid.com/terrell here].