Microformats Wiki - User contributions [en]

plain-old-xml-considered-harmful

2006-09-07T17:43:12Z

DavidOsolkowski: The wiki automatically links RFC references

= plain old xml considered harmful =

(This article is a stub, feel free to expand upon it)

The plain old xml approach has already been tried by *numerous* others
since 1998 and has failed on the Web.

http://blog.davidjanes.com/:entry:davidjanes-2005-10-04-0000/

OTOH, [[semantic-xhtml|XHTML]] + [[semantic-class-names]] has seen widespread adoption among the
web authoring/design/IA/publishing community. Microformats is leveraging
the approach that is both working better and frankly dominating in practice
on the Web.

http://microformats.org/blog/2006/01/09/tim-bray-on-creating-xml-dialects/

See also [[namespaces-considered-harmful]].

XML elements are limited to only one "name" and thus only one meaning, whereas the
class attribute is a space separated set of names and can thus capture
multiple meanings, providing a much more flexible semantic structure for
authors, and greatly aiding in following DRY.

There are 1000s more web authors/developers that write/understand (X)HTML
+ semantic class names + CSS as compared to the number of folks that
write/understand either plain or namespaced XML.

It's the publishers that matter, not the programmers. To put it
another way, programmers can solve problems once and share open source.
Publishers have to keep solving markup/publishing problems for content and
design numerous times continuously, and have much less chance of being able
to share their solutions. That, plus the fact that there are many more web
designers than programmers, plus simple economics, means the best solution is
to optimize for ease of publishing, and let iterative open source solve the
programming problems.

XML also has disadvantages in that an XML processor is required to abort when it encounters an error, so a single unescaped ampersand can cause an XML document to be entirely unreadable. This is hardly appropriate for an end-user application, so many people ignore this requirement and break the spec, so they're not actually using XML. Furthermore, serving XML over HTTP is difficult; there are all kinds of complicated issues dealing with character encodings; start with RFC 3023.

== See Also ==

* [[namespaces-considered-harmful]]
* [[microformats-easier-than-xml]]
* [[semantic-xhtml]]
* [[semantic-class-names]]

plain-old-xml-considered-harmful

2006-09-07T17:41:46Z

DavidOsolkowski: Added issues with draconian error handling, character encoding complexities

= plain old xml considered harmful =

(This article is a stub, feel free to expand upon it)

The plain old xml approach has already been tried by *numerous* others
since 1998 and has failed on the Web.

http://blog.davidjanes.com/:entry:davidjanes-2005-10-04-0000/

OTOH, [[semantic-xhtml|XHTML]] + [[semantic-class-names]] has seen widespread adoption among the
web authoring/design/IA/publishing community. Microformats is leveraging
the approach that is both working better and frankly dominating in practice
on the Web.

http://microformats.org/blog/2006/01/09/tim-bray-on-creating-xml-dialects/

See also [[namespaces-considered-harmful]].

XML elements are limited to only one "name" and thus only one meaning, whereas the
class attribute is a space separated set of names and can thus capture
multiple meanings, providing a much more flexible semantic structure for
authors, and greatly aiding in following DRY.

There are 1000s more web authors/developers that write/understand (X)HTML
+ semantic class names + CSS as compared to the number of folks that
write/understand either plain or namespaced XML.

It's the publishers that matter, not the programmers. To put it
another way, programmers can solve problems once and share open source.
Publishers have to keep solving markup/publishing problems for content and
design numerous times continuously, and have much less chance of being able
to share their solutions. That, plus the fact that there are many more web
designers than programmers, plus simple economics, means the best solution is
to optimize for ease of publishing, and let iterative open source solve the
programming problems.

XML also has disadvantages in that an XML processor is required to abort when it encounters an error, so a single unescaped ampersand can cause an XML document to be entirely unreadable. This is hardly appropriate for an end-user application, so many people ignore this requirement and break the spec, so they're not actually using XML. Furthermore, serving XML over HTTP is difficult; there are all kinds of complicated issues dealing with character encodings; start with [http://www.ietf.org/rfc/rfc3023.txt RFC 3023].

== See Also ==

* [[namespaces-considered-harmful]]
* [[microformats-easier-than-xml]]
* [[semantic-xhtml]]
* [[semantic-class-names]]

media-info-examples

2006-08-30T00:30:50Z

DavidOsolkowski: Added Discogs

= Media Info Examples =

== Contributors ==

* [http://tantek.com/log/ Tantek Çelik]
* [http://joshkinberg.com/blog/ Joshua Kinberg]
* [http://napsterization.org/stories/ Mary Hodder]
* [http://onlisareinsradar.com/ Lisa Rein]
* [[User:ChrisMessina | ChrisMessina]]
* [[User:RodBegbie | RodBegbie]]

== Introduction ==

Examples of what people actually publish on the Web when discussing, linking to, referring to media. This is focused predominantly on time based media such as audio and video, but may consider aspects of static media as well such as still images.

== Emphasis on Practical, Simple, and Minimal ==

Since all previous known attempts at this problem area have ended up quite complex and over-designed, this attempt will place simplicity and minimalism first and foremost.

Thus for now, this document is deliberately restricted to examples that are:
* ''Actual'' examples in practice on the Web '''with URLs''' to the originals (note, all *-examples pages should be like this, but previous attempts at documenting media info examples have mostly ignored this requirement, and thus it is necessary to be explicit).
* Representative of ''very common'' publishing behavior on the Web. This focus on common, representative examples is essential. If possible, include an estimate of the number of similar examples. E.g. ~10k.
* Simple and minimalist. As simple as possible. Go read [http://microformats.org/wiki/microformats#the_microformats_principles the microformats principles] right now before proceeding any further.

Any examples added which do not conform to these requirements will be deleted.

Any generic analysis will also be deleted. Analysis before examples is premature. Once there are sufficient media-info-examples, and hopefully a simple/clean listing of [[media-info-formats]], we'll hopefully start a [[media-info-brainstorming]] page to do aggregate analysis of the examples.

== Table of Contents ==

__TOC__

== Real World Examples ==

=== Overall Notes About Examples ===
These examples are organized into a short list of top level media categories, in the hopes that it will be easier to determine if there are media specific publishing behaviors, in addition to common behaviors across multiple types of media. Some may be subcategorized and distinguished by whether it was published by an individual publisher or a service:
* Audio (Speech, Music)
* Video
* Photos

The numbers after some of the examples' descriptions are based on numbers found pulling in media records at Dabble. Others may have higher numbers and would be encouraged to restate them if that's true.

=== Audio ===
==== Speech ====
Publication of audio speeches on blogs is often called "podcasting". In essence though, it is simply audio speech publishing. Quotes of audio files are beginning to appear, and publishers are putting up files with links to other audio files they've quoted from. Most audio appears to often have the same base elements as video and photos, with the exception of quotes.

===== Individual Publishing of Speech =====

* [http://www.microformats.org/blog/2005/09/30/web-essentials-audio/ Microformats: Web Essentials Audio]
** Appears to be composed of:
*** title/summary of the recording
*** clickable hyperlink to the recording (MP3)
** Contextual:
*** (primary) speaker is indicated in nearby text

* [http://www.thechrispirilloshow.com/help/20060119_chuck_cummins_on_windows_vista_interface_design.phtml Chris Pirillo podcast]
** This example has a Title, Html URL, media URL(s), description or summary, categories/tags underneath what is viewable, and date. +10k

* [http://yukelzon.blogspot.com/2006/01/podcasts.html Reflog's Random Thoughts podcast]
** This example has a Title, Html URL, description or summary, creator, tags and publish time and date. +10k records.

* [http://www.evilgeniuschronicles.org/wordpress/2006/01/12/egc-clambake-for-january-12-2006/ Evil Genius Chronicles podcast]
** This example has a Title, Html URL, description or summary, quotes URLs and descriptions, licence, creator, tags and publish time and date. +10k records.

* [http://www(dot)bizbyjake.com/2006/01/how-are-you-doing.html media published from a blog, Jake Steinfeld's Audio Blog] NOTE: this record had trouble because mediawiki blocks any DOTbiz domains and so while this domain coincidentally has a DOTbizbyjake.com name that is not a TLD, it was still blocked in the loading of the page with this example. So please adjust the URL manually and then visit the site.
** This example has a Title, Html URL, media URL, creator and publish time and date. +10k records.

==== Music ====
* [http://www.somesongs.com/ somesongs]
** Has song title (linked to more info), artist (linked to more info), play link (to mp3), and rating

* [http://www.bradsucks.net/music/ Brad Sucks » music]
** Has album title, song title, separate link to more info, inline flash player, and play link (to mp3)

* [http://www.scottandrew.com/music/ Scott Andrew - lo-fi acoustic pop superhero! > music >]
** Has album title, song title, album artwork, streaming link (to m3u), and play link (to mp3)

* [http://magnatune.com/genres/rock/ Magnatune]
** Has artist (linked to more info), artist description, album title (linked to more info), lofi streaming link (to m3u), hifi streaming link (to m3u), link to more info, link to license info, link to purchase info.

* [http://www.songfight.org/ SONG FIGHT!]
** Has theme, artist/play link (to mp3).

* [http://www.yes.com/ Yes.com]
** Music played in last hour ([http://www.yes.com/lookup.php?s=WERS example])
*** Flash page with track play time, artist, title, cover art. Affiliate linked to iTunes music store.
** Top 100 Chart ([http://www.yes.com/top100.php?s=WXKS example])
*** HTML page with chart position, last week's chart position, artist, title (affiliate link to iTunes music store)

* [http://www.hearingdouble.co.uk/dumb/index2.html Portishead Remixed]
** Whole page is for one album (a mash-up remix of a Portishead album). Has Album Track Number and Title (linked to mp3) and Remixer's name, plus cover art. Also a link to the BitTorrent download of the whole album.

* MySpace (examples: [http://myspace.com/theradioknives] [http://www.myspace.com/singsinguk] [http://www.myspace.com/arcticmonkeys])
** Artist pages containing embedded flash players. Song title starts song playing on embedded player. Download link optionally links to mp3.
** Link to artist's homepage, band members, influences, biography.

* [http://musicbrainz.org MusicBrainz.org]
** MusicBrainz provides a catalog of music metadata such as the [http://wiki.musicbrainz.org/ArtistName artist name], the [http://wiki.musicbrainz.org/ReleaseTitle release title], and the list of [http://wiki.musicbrainz.org/Track tracks] that appear on a release.
** Since 2005, users have the option to further relate each of these entities using a detailed set of [http://wiki.musicbrainz.org/AdvancedRelationships relationships] (i.e. who played which instrument on a release/track).
** Examples: [http://musicbrainz.org/browseartists.html browse] and [http://musicbrainz.org/search.html search] the catalog

* [http://reactor-core.org/ogg-tagging.html Vorbis Comment Recommendations]
** Comment fields development by the Ogg/Vorbis community to consistently describe audio files.

* [http://www.apple.com/itunes/podcasts/techspecs.html iTunes RSS extensions]
** The DTD used to add richer data to media available in podcasts via the iTunes Music Store.

* [http://www.discogs.com/ Discogs]
** Extensive database with labels, artists, albums, etc. Also has extremely detailed submission guidelines that probably qualify for a media-info format.

=== Video ===
Publication of video on blogs often goes by "videoblogging", "vlogging", "VODcasting", or "video podcasting". The typical process involves publishing a direct link to the video file within the blog entry. The blog entry can, but does not have to, include an embedded video player. Many videos include a thumbnail jpg which is clickable to the media object and player. Some video includes links to those other source videos, photos and audio that have been quoted. Most videos have the same base elements as photos and audio, with the exception of quotes.

==== Individual publishing of video ====

* [http://FreeVlog.org FreeVlog]: the most popular tutorial on the web describing the videoblogging process by combining free tools and services (Blogger, OurMedia/Internet Archive, FeedBurner).
** According to this process, a videoblog entry contains:
*** Direct link to the video file
*** Clickable thumbnail image/screen capture of the video
*** Contextual information about the video (title, description, etc) is usually contained in the surrounding blog entry

* [http://joshkinberg.com/popupmaker Video Pop Up Maker]
** This example based on the process taught at [http://FreeVlog.org FreeVlog] generates code to create a dynamic pop up window with embedded video player. The reasons for this are enumerated [http://www.unmediated.org/archives/2005/10/easily_create_p.php here]

* [http://ryanedit.blogspot.com/2006/01/light-water-music-2.html Ryanne's Video Blog]
** This example has a Title, Html URL, media URL, thumbnail url, description or summary, creator, and publish time. +50k

* [http://www.prototypen.com/blog/vjblog/archives/001244.html Artificial Eye: fALks world news view 05|07|11 video post]
** This example has a Title, Html URL, media URL, thumbnail url, description or summary, creator, quotes URLs and description, and publish time. +10k (quotes +5k)

* [http://www.itsjerrytime.com/ It's JerryTime! - episodic video content]
** This example has a Title, Html URL, media URL, thumbnail url and creator. +10k records.

* [http://www.bottomunion.com/blog/ Bottom Union combined video + text blog]
** This example has a Title, Html URL, media URL, thumbnail URL, description or summary, creator, tags and publish time and date. +5k blogs

* [http://kitchenarts.blogspot.com/ KitchenArts instructional/marketing video blog]
** This example has a Title, Html URL, media URL, thumbnail URL, description or summary, creator, and publish time and date. +5k blogs

* [http://weblog.infoworld.com/udell/2005/12/06.html#a1348 Jon Udell's Weblog: Greasemonkeying Google Videomedia - blog post with quoting of video via greasemonkey plugin]. This example *may* be better suited to a study from the perspective of a citation.
** This example has a Title, Html URL, media URL, description or summary, creator, quote URLs and description, license and publish time. >100 records but is climbing rapidly.

* [http://rocketboom.com/vlog/ Rocketboom daily with amanda congdon - daily video posting in a blog-like format, with quoting of video, audio photos]
** This example has a Title, Html URL, media URL, description or summary, creator, quote URLs and description, license and publish time. This example also "auto-plays", that is, starts playing the video in the normal browser/HTML view upon loading of the page. +20k

==== Service publishing of video ====

* [http://blip.tv/ blip.tv - video blogging, podcasting and sharing service]
** This example has a Title, Html URL, media URL, thumbnail URL, description or summary, license, creator, tags and upload time. +1m across all hosters. +10k records.

* [http://youtube.com/ YouTube - Broadcast Yourself - video hosting and sharing service]
** This example has a Title, Html URL, thumbnail URL, description or summary, license, creator, tags and upload time. +1m across all hosters. +15k records.

* [http://mefeedia.com/ Mefeedia] - Mefeedia is the best place to find free videoblogs or video podcasts.
** This example has a Title, Html URL, thumbnail URL, thumbnail title, media type overlay icon, creator.

* [http://vimeo.com/ Vimeo] - The Flickr of Video
** This example has a Title, thumbnail (class=moduleClipThumb), thumbnail URL, Html URL, creator.

* [http://DailyMotion.com/ DailyMotion] - Watch, publish, share
** This example has a thumbnail (class=category_minilist_item_video_preview_image), with an Html URL, thumbnail URL, certain info (class=category_minilist_infos), title (class=category_minilist_item_title), href to country tag (with image icon with class=category_minilist_item_flag, image title set to country name).

=== Photos ===
* A few photos online have region annotation and quoting. But as tools are developed that are usable for mass publishers, this will likely increase.
* Many videos have thumbnails that are jpgs.
* Many videos use pictures and therefore the pictures themselves are quotes from the video.
* Most photos have the same elements as videos and audio, with the exception of quotes.

==== Individual Publishing of Photos ====
* [http://blog.bouckenooghe.com/2005/09/01/em6-a-est-fache-avec-le-centimetre/ Blog A Brac » E=m6 a est fâché avec le centimètre - photo with annotated screen-caps]
** This example has a Title, Html URL, media URL, description or summary, creator, quotes and descriptions, tags/categories, and publish date and time. +200 across all individually blogged photos.
* [http://scribbling.net/projects/fotonotesrolloverviewer/fotonotesplugin.php?p=helicopterovernyc.jpg Scribbling.net implementation of Fotonotes Plugin demonstrating the fotonotes annotation tool for photos]
** This example has media url, quotes and descriptions, creator. +200 across all individually blogged photos.

* For more work along the lines of 2d annotations, please see (and add to) [[photo-note-examples]].

==== Service publishing of photos ====

* [http://www.flickr.com/photos/500hats/50282408/ Flickr - Photo Sharing instance of a photo.]
** This example has a Title, Html URL, media URL, description or summary, quotes URLs and descriptions, licence, tags, upload time, playlist (set), license, creator, and other capture data. +millions across all hosters. +millions of records.

* [http://www.webshots.com/search?query=san+francisco&new=1&source=search_results_top Webshots - Search results, gallery view.]
** This example has a Title, Html URL, creator, licence, Premium/Standard access.

* [http://www.webshots.com/g/32/579-sh/25695.html Webshots - Single photo view.]
** This example has a Title, Html URL, creator, licence, link to creator's other photos. Three alternate download sizes, link to buy a print. Link to add as favorite. Link to next, previous photos in collection. Photo belongs to generic category (no tags). Links to related photo searches.

== Notes on Existing Practices ==

Mary Hodder:
* We are finding as we look at thousands of user generated media records, that all have titles, creator, at least a default licensing, most have tags whose functionality is made available through the hosting service (the richer the media, the more likely tagging goes toward 100%), Html and media URLs, thumbnail URLs, publishing date, and about 25% have quoting information of some sort (quotes of video or audio, and region quotes of photos).
* Tags apparently appear at the upload point on 61% of photos in Flickr, and within a short period, 80+% have tags. 12% of users in Flickr apparently tag photos other than their own.

== Next Steps ==
# Add more real-world, simple, minimal examples.
# Research and organize existing/previous [[media-info-formats]], with a focus on formats for publishing '''common''', '''user-visible''' media information.
# Start [[media-info-brainstorming]] based on examples.

== See Also ==
* [[media-metadata-examples]] - previous attempt to catalog and organize top down metadata systems generated by engineers and committees, as examples of elements, and includes formats which should be in a separate page. Useful as a source of research but this microformat needs to embrace the bottomup ways users are publishing photos, video and audio online.

namespaces-considered-harmful

2006-08-29T20:33:18Z

DavidOsolkowski: Reorganized a couple links, added another paragraph

= namespaces considered harmful =

(This article is a stub, feel free to expand upon it)

The mixed namespace approach has already been tried by *numerous* others since 1998 and has failed on the Web.
* [http://blog.davidjanes.com/:entry:davidjanes-2005-10-04-0000/ XML - what is it good for? by David Janes]
* [http://www.xml.com/pub/a/2004/07/21/dive.html XML on the Web has Failed by Mark Pilgrim]
* [http://microformats.org/blog/2006/01/09/tim-bray-on-creating-xml-dialects/ Tim Bray on creating XML dialects]

On the other hand, XHTML + [[semantic-class-names]] has seen widespread adoption among the web authoring/design/IA/publishing community. Microformats is leveraging the approach that is both working better and frankly dominating in practice on the Web.

Namespaces are actually a *huge* negative. Search for:
* [http://www.google.com/search?q=namespaces%20Tower%20of%20Babel namespaces Tower of Babel]
* [http://www.google.com/search?q=namespaces+syntactic+vinegar namespaces syntactic vinegar]

Namespaces are actually *not* well supported in sufficient modern browsers, nor even sufficiently with enough W3C technologies or test suites as compared to [[semantic-xhtml|(X)HTML]] + [[semantic-class-names]] + CSS.

Namespaces encourage people to seclude themselves in their own namespace and invent their own schema rather than reusing existing elements in existing formats. This hurts interoperability because a dozen different namespaces can all have their own slightly different semantics for the same element.

If you start thinking about the web in terms of OOP and polymorphism, namespaces break the polymorphic model that allows you handle widely varied data structures using the same methods.

== See Also ==

* [[plain-old-xml-considered-harmful]]
* [[microformats-easier-than-xml]]
* [[semantic-xhtml]]
* [[semantic-class-names]]

microformats-easier-than-xml

2006-08-29T19:56:55Z

DavidOsolkowski: Cleaner grammar

= microformats easier than xml =

(This article is a stub, feel free to expand upon it)

From Sören Nils 'chucker' Kuklau:

* As a spec writer, you don't have to come up with wholly [[plain-old-xml-considered-harmful|new XML]] or XML+RDF dialects.
* As an author, you don't have to learn about how to deal with [[namespaces-considered-harmful|XML namespaces]] and, generally, embedding other XML into XHTML.
* Even more importantly, you don't have to deal with the numerous quirks in XML namespace support in browsers.

All you have to do is learn to use a few more [[semantic-class-names|class names]], which virtually every browser already supports anyway, due to their extensive use in CSS.

And because you're just using HTML/XHTML classes, you can already benefit from the way a browser treats them. You don't have to reinvent the wheel, so to speak. Namespaced elements would require you to come up with styling for every single element, but using (X)HTML classes lets you take advantage of the existing styling of (X)HTML elements.

== See Also ==

* [[namespaces-considered-harmful]]
* [[plain-old-xml-considered-harmful]]
* [[semantic-xhtml]]
* [[semantic-class-names]]

plain-old-xml-considered-harmful

2006-08-29T19:53:56Z

DavidOsolkowski: Cleaner grammar

= plain old xml considered harmful =

(This article is a stub, feel free to expand upon it)

The plain old xml approach has already been tried by *numerous* others
since 1998 and has failed on the Web.

http://blog.davidjanes.com/:entry:davidjanes-2005-10-04-0000/

OTOH, [[semantic-xhtml|XHTML]] + [[semantic-class-names]] has seen widespread adoption among the
web authoring/design/IA/publishing community. Microformats is leveraging
the approach that is both working better and frankly dominating in practice
on the Web.

http://microformats.org/blog/2006/01/09/tim-bray-on-creating-xml-dialects/

See also [[namespaces-considered-harmful]].

XML elements are limited to only one "name" and thus only one meaning, whereas the
class attribute is a space separated set of names and can thus capture
multiple meanings, providing a much more flexible semantic structure for
authors, and greatly aiding in following DRY.

There are 1000s more web authors/developers that write/understand (X)HTML
+ semantic class names + CSS as compared to the number of folks that
write/understand either plain or namespaced XML.

It's the publishers that matter, not the programmers. To put it
another way, programmers can solve problems once and share open source.
Publishers have to keep solving markup/publishing problems for content and
design numerous times continuously, and have much less chance of being able
to share their solutions. That, plus the fact that there are many more web
designers than programmers, plus simple economics, means the best solution is
to optimize for ease of publishing, and let iterative open source solve the
programming problems.

== See Also ==

* [[namespaces-considered-harmful]]
* [[microformats-easier-than-xml]]
* [[semantic-xhtml]]
* [[semantic-class-names]]

plain-old-xml-considered-harmful

2006-08-29T19:49:33Z

DavidOsolkowski: Fixed URL for David Janes article

= plain old xml considered harmful =

(This article is a stub, feel free to expand upon it)

The plain old xml approach has already been tried by *numerous* others
since 1998 and has failed on the Web.

http://blog.davidjanes.com/:entry:davidjanes-2005-10-04-0000/

OTOH, [[semantic-xhtml|XHTML]] + [[semantic-class-names]] has seen widespread adoption among the
web authoring/design/IA/publishing community. Microformats is leveraging
the approach that is both working better and frankly dominating in practice
on the Web.

http://microformats.org/blog/2006/01/09/tim-bray-on-creating-xml-dialects/

See also [[namespaces-considered-harmful]].

XML elements are limited to one "name" and thus semantic, whereas the
class attribute is a space separated set of names and can thus capture
multiple semantics, providing a much more flexible semantic structure for
authors, and greatly aiding in following DRY.

There are 1000s more web authors/developers that write/understand (X)HTML
+ semantic class names + CSS as compared to the number of folks that
write/understand either plain or namespaced XML.

It's the publishers that matter, not the programmers. Or to put it
another way, programmers can solve problems once and share open source.
Publishers have to keep solving markup/publishing problems for content and
design numerous times continuously, and have much less chance of being able
to share their solutions. That plus the fact that there are 1000s more web
designers than programmers plus simple economics means the best solution is
to optimize for ease of publishing, and let iterative open source solve the
programming problems.

== See Also ==

* [[namespaces-considered-harmful]]
* [[microformats-easier-than-xml]]
* [[semantic-xhtml]]
* [[semantic-class-names]]

namespaces-considered-harmful

2006-08-29T19:48:26Z

DavidOsolkowski: Fixed URL for David Janes article

= namespaces considered harmful =

(This article is a stub, feel free to expand upon it)

The mixed namespace approach has already been tried by *numerous* others
since 1998 and has failed on the Web.

http://blog.davidjanes.com/:entry:davidjanes-2005-10-04-0000/

OTOH, XHTML + [[semantic-class-names]] has seen widespread adoption among the
web authoring/design/IA/publishing community. Microformats is leveraging
the approach that is both working better and frankly dominating in practice
on the Web.

http://microformats.org/blog/2006/01/09/tim-bray-on-creating-xml-dialects/

Namespaces are actually a *huge* negative. Search for:
* [http://www.google.com/search?q=namespaces%20Tower%20of%20Babel namespaces Tower of Babel]
* [http://www.google.com/search?q=namespaces+syntactic+vinegar namespaces syntactic vinegar]

Namespaces are actually *not* well supported in sufficient modern browsers, nor even sufficiently with enough W3C technologies or test suites as compared to [[semantic-xhtml|(X)HTML]] + [[semantic-class-names]] + CSS.

If you start thinking about the web in terms of OOP and polymorphism, namespaces break the polymorphic model that allows you handle widely varied data structures using the same methods.

== See Also ==

* [[plain-old-xml-considered-harmful]]
* [[microformats-easier-than-xml]]
* [[semantic-xhtml]]
* [[semantic-class-names]]

citation-formats

2006-07-31T13:23:10Z

DavidOsolkowski: /* ISBN:// Protocol */

= Citation Formats =

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

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

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

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

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

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

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

* abstract refines description.
* accessRights refines rights

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

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

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

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

== NLM Journal Publishing DTD ==

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

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

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

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

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

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

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

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

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

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

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

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

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

@article{XAi_HSCheng_1994a,

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

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

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

irc

2006-07-31T02:33:46Z

DavidOsolkowski: /* Microformats IRC */

__NOTOC__
= Microformats IRC =

We have an IRC channel, [irc://irc.freenode.net/microformats #microformats on the freenode network].

There's typically someone there at any point during the day, though there isn't always active discussion. Sometimes, though this is the best place to discuss issues that need lots of back and forth discussion.

== People on irc ==
A list of IRC regulars and their normal timezones. (winter/summer)

* [[User:Adam Craven|AdamCraven]] (+0000)
* [[User:Amette|amette]] (+1000)
* [[User:B.K._DeLong|bkdelong]] (-0500/-0400)
* [[User:Ben Ward|BenWard]] (+0000)
* [[User:BenjaminCarlyle|BenjaminCarlyle]] (+1000)
* [[User:Boneill|boneill]] (+0000)
* [[User:Brian|briansuda]] (-0600/-0500)
* [[User:ColinDDevroe|cdevroe]] (-0500/-0600)
* [[User:Cgriego|cgriego]] (-0600/-0500)
* [[User:ChrisCasciano|pnhChris]] (-0500/-0400)
* [[User:ChrisMessina|factoryjoe]] (-0800/-0700)
* [[User:ChristopherStJohn|cks]] (-0600/-0500)
* [[User:DanC|DanC]] (-0600/-0500)
** office hours: Wednesday afternoons, America/Chicago time
* [[User:Dave Cardwell|davecardwell]] (+0000)
* [[User:DeanEro|deanero]] (-0800/-0700)
* [[User:DimitriGlazkov|dglazkov]] (-0600/-0500)
* [[User:DrewMcLellan|drewinthehead]] (+0000/+0100)
* [[User:EdwardOConnor|hober]] (-0800/-0700)
* [[User:Enric|enric]] (-0800/-0700)
* [[User:Evan|evanpro]] (-0500)
* [[User:Fil|Fil]] (+0200)
* [[User:Grantbow|Grantbow]] (-0800/-0700)
* [[User:Hlb|hlb]] (+0800-0700)
* [[User:IanHickson|Hixie]] (-0800/-0700)
* [[User:Izo|IZO]]
* [[User:JoeGregorio|jcgregorio]]
* [[User:Jonathan_Arkell|jonnay]] (-0700/0600)
* [[User:Keri Henare|kerihenare]] (+1200)
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)
* [[User:Mark Mansour|Mark Mansour]] (+1100)
* [[User:MarkNormanFrancis|Mark Norman Francis]] (+0000/+0100)
* [[User:neuro|neuro`]]
* [[User:Phae|Phae]] (+0000/+0100)
* [[User:PriitLaes|plaes]] (+0200/+0300)
* [[User:DavidOsolkowski|qid]] (-0500)
* [[User:Remi|Remi]] (-0500/-0400)
* [[User:RobertBachmann|RobertBachmann]] (+0100/+0200)
** Office hours: <del>Wednesday, 18:00-20:00 UTC</del> (Currently no office hours)
* [[User:RyanKing|kingryan]] (-0800/-0700)
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC
* [[User:Csarven|csarven]] (-0500/-0400)
* [[User:Dana Benson|Snowden]] (-0800/-0700)
* [[User:Steve Ganz|SteveGanz]] (-0800/-0700)
* [[User:Tantek|Tantek]] (-0800/-0700)
* [[User:Trovster|trovster]] (-0800/-0700)
* [[User:Dan Kubb|dkubb]] (-0800/-0700)
* [[User:Ed Summers|edsu]] (-0500/-0400)
* [[User:Smackman|Steve Farrell]] (-0800/-0700)
* [[User:Enric|Enric]] (-0800/-0700)
* [[User:Charlvn|Charl]] (+0200/+0200)
* [[User:MarkoMrdjenovic|friedcell]] (+0100/+0200)
* [[User:Vant|vant]] (+0900)
* [[User:IwaiMasaharu|iwaim]] (+0900)
* [[User:Richard Conyard|WhiskeyM]] (+0000)

=== Greetings ===

To display a brief description of who you are each time you join the channel, you can create a definition for your username. To do so pass the <tt>?def</tt> command using something like the following convention (be brief):

<code>?def jdoe is John Doe and can be found online at <nowiki>http://www.jdoewebsite.com</nowiki></code>

More information about using JiBot commands can be found on the [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot website]

=== bots ===

* [[mfbot]]
* [[mflogbot]]
* [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot]

== Logs ==

Available here: http://rbach.priv.at/Microformats-IRC/

Atom feed of logs available here: http://microformat.makedatamakesense.com/log_feed/

== IRC meetups ==

The idea of having IRC meetups (that is, a set time for meeting on IRC) has been suggested by [[User:RyanKing|Ryan King]], as it appears to work well for the WordPress community and may help us from time-to-time. As of yet, there are no plans to have meetups, though.

User:DavidOsolkowski

2006-07-31T02:29:09Z

DavidOsolkowski: About David Osolkowski

http://wadny.com/ - in hiatus pending a rewrite of my weblog system

Student studying software engineering in the US, western New York state.

irc

2006-07-31T02:28:07Z

DavidOsolkowski: /* People on irc */

__NOTOC__
= Microformats IRC =

We have an IRC channel, [irc://irc.freenode.net#microformats #microformats on the freenode network].

There's typically someone there at any point during the day, though there isn't always active discussion. Sometimes, though this is the best place to discuss issues that need lots of back and forth discussion.

== People on irc ==
A list of IRC regulars and their normal timezones. (winter/summer)

* [[User:Adam Craven|AdamCraven]] (+0000)
* [[User:Amette|amette]] (+1000)
* [[User:B.K._DeLong|bkdelong]] (-0500/-0400)
* [[User:Ben Ward|BenWard]] (+0000)
* [[User:BenjaminCarlyle|BenjaminCarlyle]] (+1000)
* [[User:Boneill|boneill]] (+0000)
* [[User:Brian|briansuda]] (-0600/-0500)
* [[User:ColinDDevroe|cdevroe]] (-0500/-0600)
* [[User:Cgriego|cgriego]] (-0600/-0500)
* [[User:ChrisCasciano|pnhChris]] (-0500/-0400)
* [[User:ChrisMessina|factoryjoe]] (-0800/-0700)
* [[User:ChristopherStJohn|cks]] (-0600/-0500)
* [[User:DanC|DanC]] (-0600/-0500)
** office hours: Wednesday afternoons, America/Chicago time
* [[User:Dave Cardwell|davecardwell]] (+0000)
* [[User:DeanEro|deanero]] (-0800/-0700)
* [[User:DimitriGlazkov|dglazkov]] (-0600/-0500)
* [[User:DrewMcLellan|drewinthehead]] (+0000/+0100)
* [[User:EdwardOConnor|hober]] (-0800/-0700)
* [[User:Enric|enric]] (-0800/-0700)
* [[User:Evan|evanpro]] (-0500)
* [[User:Fil|Fil]] (+0200)
* [[User:Grantbow|Grantbow]] (-0800/-0700)
* [[User:Hlb|hlb]] (+0800-0700)
* [[User:IanHickson|Hixie]] (-0800/-0700)
* [[User:Izo|IZO]]
* [[User:JoeGregorio|jcgregorio]]
* [[User:Jonathan_Arkell|jonnay]] (-0700/0600)
* [[User:Keri Henare|kerihenare]] (+1200)
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)
* [[User:Mark Mansour|Mark Mansour]] (+1100)
* [[User:MarkNormanFrancis|Mark Norman Francis]] (+0000/+0100)
* [[User:neuro|neuro`]]
* [[User:Phae|Phae]] (+0000/+0100)
* [[User:PriitLaes|plaes]] (+0200/+0300)
* [[User:DavidOsolkowski|qid]] (-0500)
* [[User:Remi|Remi]] (-0500/-0400)
* [[User:RobertBachmann|RobertBachmann]] (+0100/+0200)
** Office hours: <del>Wednesday, 18:00-20:00 UTC</del> (Currently no office hours)
* [[User:RyanKing|kingryan]] (-0800/-0700)
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC
* [[User:Csarven|csarven]] (-0500/-0400)
* [[User:Dana Benson|Snowden]] (-0800/-0700)
* [[User:Steve Ganz|SteveGanz]] (-0800/-0700)
* [[User:Tantek|Tantek]] (-0800/-0700)
* [[User:Trovster|trovster]] (-0800/-0700)
* [[User:Dan Kubb|dkubb]] (-0800/-0700)
* [[User:Ed Summers|edsu]] (-0500/-0400)
* [[User:Smackman|Steve Farrell]] (-0800/-0700)
* [[User:Enric|Enric]] (-0800/-0700)
* [[User:Charlvn|Charl]] (+0200/+0200)
* [[User:MarkoMrdjenovic|friedcell]] (+0100/+0200)
* [[User:Vant|vant]] (+0900)
* [[User:IwaiMasaharu|iwaim]] (+0900)
* [[User:Richard Conyard|WhiskeyM]] (+0000)

=== Greetings ===

To display a brief description of who you are each time you join the channel, you can create a definition for your username. To do so pass the <tt>?def</tt> command using something like the following convention (be brief):

<code>?def jdoe is John Doe and can be found online at <nowiki>http://www.jdoewebsite.com</nowiki></code>

More information about using JiBot commands can be found on the [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot website]

=== bots ===

* [[mfbot]]
* [[mflogbot]]
* [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot]

== Logs ==

Available here: http://rbach.priv.at/Microformats-IRC/

Atom feed of logs available here: http://microformat.makedatamakesense.com/log_feed/

== IRC meetups ==

The idea of having IRC meetups (that is, a set time for meeting on IRC) has been suggested by [[User:RyanKing|Ryan King]], as it appears to work well for the WordPress community and may help us from time-to-time. As of yet, there are no plans to have meetups, though.