citation-formats-fr: Difference between revisions
| Line 492: | Line 492: | ||
<tr> | <tr> | ||
<td><b>unpublished:</b></td> | <td><b>unpublished:</b></td> | ||
<td> | <td>Un document avec un author et un title, mais non formellement publié. Champs requis : author, title, note. Champs optionnels : month, year, key.</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
Revision as of 12:04, 31 July 2006
Formats de Citation
Cette page affichera plusieurs types différents de format de citations. L'idée est de comparer ce qui est commun parmi tout les formats et ceux qui seront fusionnés dans ce microformat.
Voir aussi :
Chart de Comparaison
Le chart suivant cartographie les termes d'une implémentation à l'autre. C'est important parce que sit toutes les propriétés sont introduites dans ce microformat, alors il sera possible de les faire correspondre à un certain nombre de différents formats. La table n'utilise actuellement que Dublin Core, MODS, et bibTeX. Chaque colonne a toutes les propriétés et leurs équivalents dans chaque format. S'il n'y a pas de propriété correspondante, la cellule est grise. En bas de la liste les termes uniques pour chaque format. Dublin core a des termes basiques et des termes qui étendent les basiques. Si la propriété est une extension d'un terme basique elle est entre ()'s. MODS utilise XML, ainsi n'importe quelle sous propriété est listé dans sa forme arbre, propriété/sous-propriété.
CECI N'EST PAS DEFINITIF, toute erreur devrait être corrigée. Des formats supplémentaires seront ajoutés à la liste au fur et à mesure qu'ils seront mappés.
| Dublin Core | MODS | bibTeX | Z39.80 |
|---|---|---|---|
| Title (alternative) | titleInfo/title titleInfo/PartNum |
booktitle title chapter number pages volume series |
Analytic Title Collective or Series Title |
| creator | name/namePart | author creator |
Author, Primary Corporate Author, Primary |
| subject | subject/topic | keywords | needs mapping |
| Description (abstract | tableOfContents) | abstract note tableOfContents |
abstract annotation note contents |
needs mapping |
| Contributor | name | editor? | Book/Report/Volume Editor Producer |
| Date (available | created | dateAccepted | dateCopyrighted | dateSubmitted | issued | modified | valid) | originInfo/dateIssued originInfo/dateCreated originInfo/dateCaptured originInfo/dateOther |
month year |
Copyright Year Date-generic Date of conference Date of Publication Date of Update/Revisou/Issuance of Database Record Former Date Entry date for Database Record Database Update Year of Publication |
| Type | typeOfResource genre |
@class type |
needs mapping |
| Format (extent | medium) | physicalDescription/internetMediaType physicalDescription/extent physicalDescription/form |
howpublished | needs mapping |
| identifier (bibliographicCitation) | identifier | ISBN ISSN LCCN URL |
ISBN Identifier Report Identfier ISSN |
| Source | relatedItem | needs mapping | |
| language | language | language | |
| Relation (...) | relatedItem/... | crossRef | needs mapping |
| Coverage (spacial | temporal) | subject/temporal subject/geographic subject/hierarchicalGeographic subject/cartographics |
needs mapping | |
| classifications | needs mapping | ||
| Rights (accessRights | license) | accessConditions | copyright | needs mapping |
| publisher | publisher | Publisher Name Place of Publication |
|
| audience (educationLevel | mediator) | targetAudience | needs mapping | |
| accualMethod accualPeriodicaty accualPolicy instrcutionalMethod provenance rightsHolder |
location extension recordInfo |
address afflilication location edition institution journal key mrnumber organization price school size |
(the following need to be mapped to the above rows or left here as other) Database Source |
Dublin Core Metadata
La métadonnée Dublin Core utilise un petit vocabulaire pour décrire la donnée.
- contributor
- coverage
- creator
- date
- description
- format
- identifier
- language
- publisher
- relation
- rights
- source
- subject
- title
- type
From those there are specialised types where are just refinments of the previous, for example:
- abstract refines description.
- accessRights refines rights
Guidelines for Encoding Bibliographic Citation Information in Dublin Core Metadata
MODS (Metadata Object Description Schema)
Un format développé pour la Bibliothèque du Congrès pour un ensemble d'élément bibliographique qui peut être utilisé pour plusieurs objectifs et particulièrement pour les applications de Bibliothèque.
http://www.loc.gov/standards/mods/
(le schéma est très gros, une fois que je consacrerai le temps approprié pour le critiquer, je posterai plus à propos de la structure -brian)
NLM Journal Publishing DTD
http://dtd.nlm.nih.gov/publishing/tag-library/2.1/n-fv30.html
La NLM Journal Publishing DTD définit le schéma pour publier des articles de journaux sous XML. L'élément
<citation>
peut être placé avec des paragraphes ou dans un élément
<ref-list>
à la fin de l'article.
"Bien que la DTD ne l'exécute pas, une citation vers un article de journal devrait être taguée avec autant que possible ce qui suit, de façon que PubMed Central, CrossRef, ou d'autres services équivalents puissent produire la citation dans un lien vivant :
| source | Le titre d'un journal, livre, comptes-rendus de conférence, etc. qui est la source d'un contenu cité. (Note : Dans le processus PubMed Central, ceci est typiquement l'abréviation MEDLINE du nom du journal.) |
| article-title | Titre de l'article |
| volume | Volume du journal |
| issue | Numéro du journal |
| fpage | Numéro de page sur lequel l'article démarre |
| name | Nom de l'auteur et de l'éditeur |
| year | Année de publication |
| month | Mois de publication (si présent) |
| day | Date de publication (si présent) |
Les autres éléments (décrits ici) peuvent être tagués si désiré. Utilisez l'élément <source> pour les titres de livres, comptes-rendus de conférences, etc."
XMLResume
<!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)> <!-- Deprécié dans 1.4.0. --> <!ELEMENT publisher (#PCDATA | link | url)*> <!ELEMENT pageNums (#PCDATA)>
- author
- publication date
- publisher
- pages
- title (article/livre)
- url
BibTeX
Champs utilisés par Bibtex
| abstract: | Un abstract du travail. |
| address: | L'adresse de l'éditeur. Pour les grandes maisons d'éditions, seule la ville est donnée. Pour les petites maisons d'éditions, vous pouvez aider le lecteur en donnant l'adresse complète. |
| affiliation: | L'affiliation de l'auteur. |
| annote: | Une annotation. Ce n'est pas utilisé par les style de bibliographie standards, mais peut être utilisé par d'autres qui produisent une bibliographie annotée. |
| author: | Le(s) nom(s) de(s) auteur(s). |
| booktitle: | Titre d'un livre, partie de ce qui est cité. Pour les entrées de livre utilisez à la place le champ title. |
| chapter: | un numéro de chapitre (ou section). |
| contents: | Une Table des Matières. |
| copyright: | Information de Copyright. |
| crossref: | La clé database de l'entrée étant cross-référencée. |
| edition: | L'édition d'un livre- par exemple "Seconde". Notez que c'est en capitales. |
| editor: | Nom(s) des éditeur(s). S'il y a aussi un champ author, alors le champ editor du livre ou de la collection dans laquelle la référence apparaît. |
| howpublished: | Comment quelque chose d'étrange a été publié. Le premier mot devrait être mis en capitales. |
| institution: | L'institution qui sponsorise un rapport technique. |
| ISBN: | L'International Standard Book Number. |
| ISSN: | L'International Standard Serial Number. Utilisé pour identifier un journal. |
| journal: | un nom de journal. Les abréviations sont fournis pour beaucoup de journaux. |
| key: | Utilisé pour mettre en ordre alphabétique et créer une étiquette quand les champs author et editor sont manquants. Ce champ ne devrait pas être confondu avec la clé qui apparaît au début de la référence.. |
| keywords: | Les mots-clés utilisés pour chercher ou possiblement pour l'annotation. |
| language: | La langue dans laquelle le document est écrit . |
| LCCN: | Le Library of Congress Call Number. |
| location: | Un endroit associé avec l'entrée, tel que la ville dans laqulle une conférence s'est déroulée. |
| month: | Le mois dans lequel le travail a été publié, pour un travail non publié, le mois dans lequel il a été écrit. |
| mrnumber: | The Mathematical Reviews number. |
| note: | Toute information additionnelle qui peut aider le lecteur. Le premier mot devrait être mis en lettres capitales. |
| number: | Le numéro d'un journal, magazine, compte-rendu technique, ou d'un travail dans une série. Un numéro d'un journal ou magazine est généralement identifié par son volume et un nombre ; l'organisation qui sort un rapport technique lui donne en général un nombre ; et parfois les livres sont des numéros données dans une série nommée. |
| organization: | L'organisation qui sponsorise une conférence ou publie un manuel. |
| pages: | Un ou plusieurs numéros de pages ou des intervalles de nombres, comme 37--42, ou 7,53,82--94. |
| price: | Le prix du contenu. |
| publisher: | Le nom de l'éditeur. |
| school: | Le nom de l'école dans laquelle a été écrite une thèse. |
| series: | Nom donné à une série ou un ensemble de livres. Quand on cite un livre complet, le champ title donne son titre et le champ series optionnel donne le nom d'une série dans laquelle le livre a été publié. |
| size: | Les dimensions physiques du travail. |
| title: | Le titre du travail. |
| type: | Le type du compte-rendu - par exemple, "Research Note". |
| url: | Le Universal Resource Locator WWW qui pointe vers l'item étant référencé. Souvent utilisé pour des comptes-rendus techniques pour pointer vers le site FTP où il réside. |
| volume: | Le volume d'un journal ou d'un livre en plusieurs volumes. |
| year: | L'année de publication ou, pour un travail non publié, l'année à laquelle il a été écrit, comme 1976. |
Types citation BibTeX
Une référence peut être vers n'importe quelle variété de types. Ce qui suit est une liste des types. Chacun d'eux explique aussi les champs associés avec ces types. Tout champ non listé comme requis ou optionnel sera considéré comme ignoré.
| article: | Un article extrait d'un journal ou magazine. Champs requis : author, title, journal, year. Champs optionnels : volume, number, pages, month, note, key. |
| book: | Un livre avec un éditeur explicite. Champs requis : author ou editor, title, publisher, year. Champs optionnels : volume, series, address, edition, month, note, key. |
| booklet: | Un travail qui est imprimé et relié, mais sans un éditeur nommé ou une institution sponsor. Champs obligatoires : title. Champs optionnels : author, howpublished, address, month, year, note, key. |
| collection : | Une collection de travaux. Idem aux Proceedings. |
| conference: | Même chose que Inproceedings. |
| inbook: | Une partie d'un livre qui peut être un chapitre et/ou l'arrangement de pages. Champs requis : author ou editor, title, chapter et/ou pages, publisher, year. Champs optionnels : volume, series, address, edition, month, note, key. |
| incollection: | Une partie d'un livre avec son propre title. Champs requis : author, title, booktitle, publisher, year. Champs optionnels : editor, pages, organization, publisher, address, month, note, key. |
| inproceedings: | Un article dans un compte-rendu de conférence. Champs requis : author, title, booktitle, year. Champs optionnels : editor, pages, organization, publisher, address, month, note, key. |
| manual: | Documentation Technique : Champs requis : title. Champs optionnels : author, organization, address, edition, month, year, note. |
| mastersthesis: | Une thèse de Master. Champs requis : author, title, school, year. Champs optionnels : address, month, note, key. |
| misc: | Utiliser ce type quand rien d'autre ne concorde. Champs requis : aucun. Champs optionnels : author, title, howpublished, month, year, note, key. |
| patent: | Un brevet. |
| phdthesis: | Une thèse Ph.D. Champs requis : author, title, school, year. Champs optionnels : address, month, note, key. |
| proceedings: | Les comptes-rendus d'une conférence. Champs requis : title, year. Champs optionnels : editor, publisher, organization, address, month, note, key. |
| techreport: | Un rapport publié par une école ou autre institution, généralement numéroté dans une série. Champs requis : author, title, institution, year. Champs optionnels : type, number, address, month, note, key. |
| unpublished: | Un document avec un author et un title, mais non formellement publié. Champs requis : author, title, note. Champs optionnels : month, year, key. |
Exemples
@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>
Applications Bib
Reference-management applications that support the bib format. This is an incomplete list.
Applications de Bureau
Applications Web
- RefWorks (Large market share)
- CiteULike
- CiteSeer
- BibSonomy
- Connotea
- Amatex - converts Amazon to Bib format
- Many others can be found at Wikipedia
Bases de données Académiques
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
In particular, see the list of different reference types.
A sample item in RIS format:
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 -
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 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 SFX. The Context Object in Span (COinS) community standard represents one way to embed OpenURLs in XHTML without including a resolver target. OpenURL also provides an XML encoding.
Exemple (extrait d'une critique de livre écrite en utilisant le plugin Structured Blogging) :
<p><b>ISBN</b>: <span class='Z3988' title='ctx_ver=Z39.88-2004&rft_val_fmt=info:ofi/fmt:kev:mtx:book&rft.isbn=0679426612'> 0679426612</span></p>
Un autre exemple, un journal :
<span class="Z3988" title="ctx_ver=Z39.88-2004&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.issn=1045-4438"></span>
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 types of citations: book, dissertation, journal, patent. It would be possible to simply provide a standard XHTML bundling for these keys as a microformat.
Exemple
<div class="openurl-journal"> <span class="aulast">Berners-Lee</span>, <span class="aufirst">Tim</a>; Hendler, James; Lassila, Ora.</span> "<span class="atitle">The Semantic Web</span>". <span class="jtitle">Scientific American</span> <span class="volume">284</span>(<span class="issue">5</span>), pp. pp. <span class="pages">34-43</span>. <span class="issn">0036-8733</span> </div>
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 have been noted elsewhere.
OpenURL Rapidement Expliqué
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 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: 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
DocBook
A subset of the DocBook vocabulary is dedicated to representing a bibliography: http://www.docbook.org/tdg/en/html/bibliography.html
<!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>
- 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 John Blyberg's blog.
<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>
- url
- availablity
- identifier (ISBN/call number)
- author
- title
- publisher
- pages
- description/contents
SimpleDC supporté par le toolkit zoom
<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>
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 de la Bibliothèque du Congrès
<?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>
NOTE: this is just Dublin Core data in a special LOC envelope
Université de Bath reference type
<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>
- author
- date
- url
- description
- type (book/journal/conference)
- title
- artile
- volume
- issue
- chapter
- pages
- publisher
- publisher data (address, city, ...)
Schéma Implicite
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 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 et 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. - 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 biblio schema provides a comprehensive set of classes to describe citation metadata. It might prove useful as a guide for a micro-format. The primary classes are Agent, Reference, Collection, and Event. An "Article", then, would be a subclass of "Part", which in turn is a subclass of Reference. Likewise, a "Journal" is a subclass of a "Periodical," which in turn is a subclass of "Collection." An article would typically be linked to a journal through a dcterms:isPartOf relation.
ISBN:// Protocol
RFC3187 defines an isbn protocol
Example:
I'm not sure if any browser uses this data, but it might be have an application in citations describing registered materials with an ISBN
Vous devriez savoir
- 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) [1]. Why don't you try to work with the professionals instead of amateurishly trying to reinvent the wheel and create yet another incompatible format? -- 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 [2] and csl [3]).
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. -- JakobVoss 11:48, 19 Jul 2006 (PDT)
OpenDocument
The OpenDocument Format also includes parts for citation and bibliography. See also the OpenOffice Bibliographic project. -- JakobVoss 11:55, 19 Jul 2006 (PDT)