citation-brainstorming-fr
Citation Brainstroming
Contributeurs
- ...
- ... (un paquet de types biens !)
- Tantek Çelik
- Tim White
- Michael McCracken
(traduction en cours Christophe Ducamp)
Voir aussi
Cas d'utilisation
Pour concentrer la discussion, ajoutez svp des cas d'utilisation en dessous qui aideront à montrer quels problèmes le microformat citation essaiera de résoudre.
J'en ai inclus deux, se concentrant sur la consommation de l'information - j'ai imaginé qu'utiliser des cas pour générer du contenu microformaté impliquerait simplement de permettre à votre contenu d'être mieux consommé, mais me suis intéressé pour voir s'il y a quelque chose qui m'échappe ici - Mike
Acquérir l'information de référence à partir du web
Un utilisateur trouve soit une page d'un article d'un auteur, ou visualise les résultats d'une recherche et aimerait importer l'information sur les articles affichés dans sa database locale de références, à des fins de cataloguer les choses qu'il a lues, d'y ajouter des notes, et d'utiliser l'information pour générer des citations pour plus tard, potentiellement sous d'autres formes, telles que BibTeX ou Docbook, pour inclusion dans une publication de son cru.
Notes : Dans ce cas, il n'est pas important pour l'utilisateur quel format prend la citation comme affichée sur la page où il la trouve. Ce qui *est* important est qu'elle contienne suffisamment d'inforamtion pour permettre la génération du format dans lequel il la republiera pour finir. Ceci sous-tend qu'il puisse être valable de dégrader un peu du côté de la verbosité.
Ainsi, les liens vers les représentations complètes téléchargeables du travail cité sont très importants - par ex. un lien vers le PDF d'un article de journal ou vers un fichier de musique.
S'abonner à des listes de lectures, périodiques, etc.
J'aimerais pouvoir influencer mon agrégateur de nouvelles avec hAtom pour m'abonner à une source distante pour l'information de citation, par exemple :
- une liste de lecture pour un séminaire
- la liste de publication pour une conférence (par ex, m'abonner à SIGGRAPH et voir les comptes-rendus mis à jour chaque année)
- les éditions d'un journal
- un groupe de recherche particulier ou des publications d'un chercheur
- Pas simplement de la recherche : les publications populaires d'un auteur (par ex., l'Archive de Malcolm Gladwell)
Agréger les listes de lectures et critiques
Un agrégateur de citation spécifique microformat pourrait fournir une version décentralisée de CiteULike. Les bibliothèques, auteurs, groupes de recherche et éditeurs pourraient baliser leurs collections, tandis que d'autres personnes sur les blogs ou sites de critiques pourraient ajouter des tags et critiques.
Au moins, disposer d'un microformat bien adopté rendrait les outils d'écriture comme CiteULike bien meilleur, parce que cela reposerait dans certains cas sur le raclage-écran de sites web.
Discussion hBib originale
Durant la Journée WWW2005 des Développeurs sur la session microformats, Rohit Khare a fait une présentation où il a discuté du processus des microformats et puis il a fait une démonstration rapide où un paquet d'entre nous a reçu un document partagé Subethaedit et a brainstormé quelques idées sur ce à quoi pourrait ressembler un microformat de citation "hBib". Rohit a placé le document sur son site Commercenet.
Un essai pour résumer et mettre le document lié dans ligne suit. -Mike
Deux objectifs essentiels ont été soulignés par le groupe :
- Eviter de re-keying references
- S'Adapter aux nouveaux styles de journaux en modifiant CSS
Le problème fondamental a été discuté en termes d'affichage - la capacité de transformer XHTML+hBib dans les nombreux formats spécifiques aux journaux. Par exemple, comment afficher "et.al" quand tous les auteurs sont présents dans le source, et comment réordonner les éléments si un style définit un ensemble trié d'éléments qui entrent en conflit avec le tri dans la source. Utiliser hCard pour les auteurs fût agréé par les participants, et les débuts d'un exemple ont été montrés.
Structure XHTML
Mon expérience de travail avec X2V et hCa* m'a enseigné quels éléments sont faciles à trouver et quels sont ceux qui ne le sont pas. Le fait que le microformat Citation soit très nouveau, il est possible de ne pas réitérer une fois de plus les mêmes erreurs et de rendre les choses plus faciles pour que l'application d'extraction trouve et sous-tende certaines propriétés.
- Il devrait y avoir une sorte de 'root node' qui sous-tend tous les éléments enfants pour le microformat Citation.
- Parce que la plupart des personnes auront plusieurs Citation il devrait y avoir une façon de représenter chaque objet Citation comme un unique bloc indépendant d'un autre. Ceci pour éviter que le parsage de trouver un 'author' et de l'appliquer à toutes les citations. Chaque citation devrait être dans un container (class="???") qui s'étendait à partir d'autres.
- Peut-être que class="hcite" avec
<cite>est recommandé comme l'élément racine. Par exemple<cite class="hcite">
Citation vs. media-info
What distinguishes a cite from say media-info (e.g. media-info-examples) is that a cite is a reference to something explicitly external to the current piece of content or document, whereas media-info describes information about content embedded or inline in the current document.
Sens Sémantique
One of the guiding priniciple of Microformats is to use the most semantically rich element to describe each node (Point 2 of Semantic XHTML Design Principles: Use the most accurately precise semantic XHTML building block for each object etc). Since we are dealing with HTML and citations, several elements are candidates to be used to enrich the semantic meaning. CITE, BLOCKQUOTE, Q, A, (are there more?)
The Citation Brainstorming Page has a few development and ideas about how to give another person credit for a link. Some of the semantic ideas behind their choices of tags can be applied to a full bibliographic type reference. Does this sentence make sense only historically? -Mike
WorldCat d'OCLC pour les titres
Question: what about using something like OCLC's WorldCat for linking titles? - Tim White
Ceci et ça
After reading through alot of different citation encoding formats, i noticed that each format was being used in onw of two ways. It was either to describe the Current page (THIS.PAGE) or being used to encode references that point to external resources (THAT.PAGE)
The informatation being encoded was identical for both resources (author, date, name, etc) they just reference different things. For this microformat, i'm not sure if we want to try to solve both problems, or just one? The meta tags in the head element would be the ideal place for information about the THIS.PAGE, but that is not in following with the ideals of microformats where information is human-readable. The THAT.PAGE idea where a list of references is at the end of a document in the form of a bibliography is more inline with the ideals of a microformat where the data is human-readable. That doesn't mean that data about the current document shouldn't be human-readable, so some of the same properties used to reference extermal resources can be used for the current document (THIS.PAGE). To do this a different root item could be used and transforming applications could either extract the citation data about the current page, or information about this page's references.
This is open for discussion, but either way, i believe that the properties used to describe a page will be the same for both THIS and THAT. brian suda
Plus sur Ci et ça
Citation microformats are being explored as a possibility for citing genealogical information at Dan Lawyer's blog.
This is a case where frequently the citation would refer to (THIS.PAGE), but would have nested within it a reference to (THAT.PAGE), possibly a few levels deep. For instance, a web page might contain data extracted from a microfilm of a census. The citation would need to include information about the web page, information about the microfilm, and information about the census. Genealogical citations are expected to include the repository (where can this book or microfilm be found. Is this the same as venue?). So, at each level the information should contain the repository of the referenced item. A nesting (recursive) mechanism for citation microformats would be useful in this case. Is this the function of the "container" element in the Straw Format?
Mise en Forme de Date
Since microformats are all about re-use and the accepted way to encode Date-Time has been pretty much settled, then this is a good place to start when dealing with all the different date citation types.
These are all the different fields from various citation formats that are of temporal nature:
* Date (available | created | dateAccepted | dateCopyrighted | dateSubmitted | issued | modified | valid) * originInfo/dateIssued * originInfo/dateCreated * originInfo/dateCaptured * originInfo/dateOther * month * year * Copyright Year * Date - Generic * Date of Confernce * Date of Publication * Date of update/revisou/issuance of database record * Former Date * Entry Date for Database Record * Database Update * Year of Publication
There are several common properties across several citation domains and will certainly be in the citation microformat, the unique instances will need further consideration, otherwise there could be no end to posiblities.
There are also several properties (year, month, Year of publication) that can be extracted from another source. Therefore, if you only encode a more specific property such as; Date of Publication, you can extract the 'year of publication' from that. Since the date-time format we are modeling after is the ISO date-time format, just the Year portion is an acceptable date. So if you ONLY know the year of publication, the you can form a valid 'Date of Publication' as a microformat (which inturn is a valid 'year of publication') - you milage may vary when it comes to importing into citation applications.
...
It seems to me that these can be collapsed to maybe one or two different date properties. As far as the specific human readable formatting of the date, that can be chosen per whatever the presentation style guide says, and the datetime-design-pattern used to simplify the markup. - Tantek
Tags
Some of the citation formats has a place for 'keywords' or 'generic tags', etc. This might be a good place to re-use the RelTag microformat. The downside would be that they are then forced to be links, which might be the correct way to mark-up these terms.
MARC / MODS / Dublin Core
The MODS (example) and Dublin Core (example) transformations of MARC21 may contain some useful ideas.
Here's a first attempt at rewriting the linked examples in XHTML (written in response to a mailing list query about encoding book information with microformats):
<div class="book" lang="en">
<h3 class="fn">Arithmetic /</h3>
<p>By <span class="creator"><span class="fn">Sandburg, Carl</span>,
<span class="date">1878-1967</span></span>,
and <span class="illustrator">Rand, Ted</span></p>
<p>Publisher: <span class="publisher"><span class="fn">Harcourt Brace Jovanovich</span>,
<span class="locality">San Diego</span></span></p>
<p>Published: <span class="issued">1993</span></p>
<p class="description">A poem about numbers and their characteristics. Features
anamorphic, or distorted, drawings which can be restored to normal by viewing
from a particular angle or by viewing the image's reflection in the provided
Mylar cone.</p>
<p class="note">One Mylar sheet included in pocket.</p>
<p>Subjects:</p>
<ul>
<li class="subject">Arithmetic</li>
<li class="subject">Children's poetry, American.</li>
<li class="subject">Arithmetic</li>
<li class="subject">American poetry</li>
<li class="subject">Visual perception</li>
</ul>
</div>
Basic Citation Stuctures
There are basic structures to any citation, this is an overview of some of the types http://www.users.muohio.edu/darcusb/misc/citations-spec.html
Format Epouvantaille de Brian
schéma implicite (exemples)
+ publisher + language + description + title + creator + journal + volume + issue + page + edition + identifier + tags + format + date published + copyright - audience
schéma implicite (formats)
+ publisher + language + description + title + creator + volume + pages + edition + issue + identifier + tags + format + date published + date copyrighted - subtitle - image - excerpt - index terms - series title - publication - journal - part (1 of X)
UNION of the two schemas
+ (PLUS) means common properties - (MINUS) means unique to the schema
Exemple
<ul class="bibliography"> <li class="citation" xml:lang="en-gb"> <!-- publisher data as hCard--> <div class="publisher vcard"> <span class="fn org">ABC Publishing Co.</span> <span class="country-name">United Kingdom</span> ... </div> <!-- author(s) data as hCard --> <div class="creator vcard"> <span class="fn n"><span class="given-name">John <span class="family-name">Doe</span></span> ... </div> <!-- location data --> <span class="title">Foobar!</span> <span class="description">World Class Book about foobar</span> <span class="volume">1</span> <span class="issue">1</span> <span class="edition">1</span> <span class="pages">1-10</span> <span class="format">article</span> <!-- differed to the UID debate --> <span class="identifier">12345678</span> <!-- keywords --> <span class="keyword">foo</span> <span class="keyword">bar</span> <!-- date properties --> Published <abbr class="dtpublished" title="20060101">January 1st 1006</abbr> Copyright <abbr class="copyright" title="20060101">2006</abbr> </li> ... </ul> <p class="citation">Have you read <span class="title"><abbr title="book" class="format">Foo Bar</abbr></span>? It was written by <span class="author vcard"><span class="fn">John Doe</span></span>. It only came out a <abbr class="dtpublished" title="20060101">few months ago</abbr></p>
Note: the "format" property above is incorrect. Format would refer more the physical characteristics of an item, rather than its type or genre (e.g. "article", "book", etc.). I'd rather have the main class for the li be "article" in this context, than the fairly meaningless "citation." Of course, one could have both, which would be fine too. -- bruce
Note: Could we use ROLE from hCard to identify editors, translators, authors, etc?
Comments : singpolyma 08:03, 16 Jun 2006 (PDT) : keywords should be rel-tag, and probably also XOXO (the same way the citation list is)
Suggestion du format épouvantail de Mike
In the interests of starting debate and having something concrete to fix, I suggest the following structure for a format. It is probably very incomplete and I claim no microformat expertise. I'm just trying to follow existing patterns. Comments and ridicule are both solicited. -Mike
En Général
The citation format is based on a set of fields common to many bibliographic data formats, which are often implied by standard citation display styles but not explicitly marked up in practice on the web.
Schéma
The citation schema consists of the following:
- cite
- title: required, text (class = fn)
- subtitle: optional, text
- authors: optional, use hCard
- publication date: optional
- link(s) to instantiations, optional, url or use rel-enclosure? (class=url)
- UID, optional (for ISBN, DOI - use existing uid class) | permalink
- series (aka volume/issuenum) , optional (not as sure how to handle these - suggestions?)
- pages: startpage & endpage, optional, text
- venue, optional (hCard)
- publisher, optional (hCard)
- container: optional (nested hCite)
- abstract, optional (blockquote + class="abstract" ?)
- notes, optional (blockquote + class="notes" ?)
- keywords, optional (rel-tag)
- image, optional (for inclusion inline, unlike the url)
- copyright, optional (rel-license)
- what else am I missing?
- language, optional
Looks good, but I question the use of hCard for names. Due to ambiguity issues, requring hCard would lead to extra markup in order to apply just a name, hence the need for a root element. We should extract the N optimization of hCard like we did with adr, in order to ease this problem. --Ryan Cannon
Perhaps a Retrieved Date or Access Date would be appropriate for citing online resources. For example at http://www.crlt.umich.edu/publinks/facment_biblio.html you see citations like this:
Chief Academic Officers of the Big 12 Universities (2000). Big 12 Faculty Fellowship Program. Retrieved December 20, 2000 from the World Wide Web: http://www.k-state.edu/provost/academic/big12/big12guide.htm.
Exemples
The following are translations into the citation format.
Note: some of these are just placeholders right now. Please feel free to fill them in!
Citer la Communication Privée
- published-date seems a weird fit, but it works...
private communication, Michael Jordan, May 2004
Needs a formatted example.
Citer des Cas Légaux
Needs an example. Here's some info I found about citing law:
I'm not a lawyer, so I'm relying on the published "blue book" standard, at least the only part of it I can get without paying $25. I'd be happy to hear improvements from experts in the field - how do lawyers mark up references to case law in HTML now?
From groklaw.net and eff.org, I find mostly just links to PDFs with the name of the case as the link text. Or just this, from EFF:
<h1>The Betamax Case</h1> <h2>Sony Corp. of America v. Universal City Studios, 464 U.S. 417 (1984)</h2>
From an example at the sample bluepages: http://www.legalbluebook.com/pdfs/bluepages.pdf 5 basic components:
- 1 name of the case (citation title)
- 2 published source in which case may be found (citation containing publication?)
- 3 a parenthetical indicating the court and year of decision (citation venue?)
- 4 other parenthetical information, if any (citation notes?)
- 5 subsequent history of the case, if any (citation notes?)
Here's two examples from the bluebook. Note that there are very strict rules about abbreviations in that source!
Holland v. Donnelly, 216 F. Supp. 2d 227, 230 (S.D.N.Y. 2002), aff'd, 324 F.3d 99 (2d Cir. 2003).
Green v. Georgia, 442 U.S. 95, 97 (1979) (per curiam) (holding that exclusion of relevant evidence at sentencing hearing constitutes denial of due process).
Citer un Livre
needs an example
Citer un article de journal
needs an example
Citer un article de magazine
needs an example
Citer un Brevet
Patents are often just cited by number. Here's a citation that accomplishes the same thing with some extra information:
<cite class="citation"> <a class="fn url" href="http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=/netahtml/search-bool.html&r=3&f=G&l=50&co1=AND&d=ptxt&s1=tevanian&OS=tevanian&RS=tevanian">US Patent #6,704,928</a> <span class="author vcard">Richard Shann</span> <abbr class="dtpublished" title="20000828T0000-0500">August 28, 2000</abbr> <blockquote class="abstract"> An executable program is prepared from a plurality of object code modules, at least one of the object code modules including section data specifying a plurality of code sequences each associated with relocation instructions identifying condition parameters. Only one of the code sequences is selected for inclusion in the executable program, determined by whether the condition for that parameter is satisfied. A linker for preparing the executable program includes a stack, a relocation module for reading the relocations, carrying out the relocation operations and selecting code sequences for inclusion in the executable program in dependence on values taken from the stack, a section data module for holding section data which is subject to the relocation operations, and a program forming module for preparing executable programs. Also disclosed is a method of assembling an object code module such that the assembled object code module includes the conditional code sequences.</blockquote> </cite>
Citer une publication de conférence
Based on the following reference, plus some more information from the ACM site and a little of my own input (the tags)
L. Hochstein, J. Carver, F. Shull, S. Asgari, V. Basili, J. K. Hollingsworth, and M. Zelkowitz, “Hpc programmer productivity: A case study of novice hpc programmers,” in Proceedings of ACM/IEEE Supercomputing Conference, 2005.
<cite class="citation">
<span class="author vcard">Lorin Hochstein</span>,
<span class="author vcard"> Jeff Carver </span>,
<span class="author vcard"> Forrest Shull </span>,
<span class="author vcard"> Sima Asgari</span>,
<span class="author vcard"> Victor Basili</span>,
<span class="author vcard"> Jeffrey K. Hollingsworth</span>, and
<span class="author vcard"> Marv Zelkowitz</span>,
<a class="fn url" href="http://dx.doi.org/10.1109/SC.2005.53">HPC Programmer Productivity: A Case Study of Novice HPC Programmers</a>.
<cite class="container citation">
<a class="fn url" href="">Proceedings of ACM/IEEE Supercomputing Conference</a>
<abbr class="dtpublished" title="20051126T0000-0800">2005</abbr>
</cite>
page <span class="startpage">35</span>
<div class="publisher vcard">
<span class=" fn">IEEE Computer Society
</span>
<div class="adr">
<span class="locality">Washington</span>,
<span class="region">DC</span>
</div>
</div>
<a class="url instantiation" href="http://portal.acm.org/ft_gateway.cfm?id=1105800&type=pdf&coll=portal&dl=ACM&CFID=68330711&CFTOKEN=39187329">PDF of full text from ACM</a>
DOI: <a class="url uid" href="http://dx.doi.org/10.1109/SC.2005.53">10.1109/SC.2005.53</a>
Tags: <a href="http://citeulike.org/tag/productivity" rel="tag">productivity</a>, <a href="http://citeulike.org/tag/hpc" rel="tag">hpc</a>, <a href="http://citeulike.org/tag/performance" rel="tag">performance</a>
<blockquote class="abstract">In developing High-Performance Computing (HPC) software, time to solution is an important metric. This metric is comprised of two main components: the human effort required developing the software, plus the amount of machine time required to execute it. To date, little empirical work has been done to study the first component: the human effort required and the effects of approaches and practices that may be used to reduce it. In this paper, we describe a series of studies that address this problem. We instrumented the development process used in multiple HPC classroom environments. We analyzed data within and across such studies, varying factors such as the parallel programming model used and the application being developed, to understand their impact on the development process.
</blockquote>
</cite>
Citer un site web externe
This is based on a formal citation of a website in the references section of a research paper, but could also be used for in-line links that had added information. Here's the original:
[25] David Stern, "eprint Moderator Model", http://www.library.yale.edu/scilib/modmodexplain.html (version dated Jan 25, 1999)
<cite class="citation">
<a class="fn url" href="http://www.library.yale.edu/scilib/modmodexplain.html">eprint Moderator Model</a>
<span class="author vcard">
<a href="http://pantheon.yale.edu/~dstern/dsbio.html" class="url fn">David Stern</a>
</span>
<abbr class="dtpublished" title="19990125T0000-0500">
Jan 25, 1999
</abbr>
</cite>