Jump to: navigation, search

BenWest démarrera ceci en réorganisatn le contenu extrait de



(J'ai retiré les problématiques que j'ai proposées. Sentez-vous libre de les faire renaître à partir de l'archive si vous pensez que cela puisse intéresser quelqu'un d'autre, mais je ne les poursuivrait pas plus en profondeur. --Thomas Breuel)

Convertir les formats de citation

Should a user agent provide retransmission of a citation in a new format? Which ones? A user agent should be capable of reading a citation from a web page, in a given format, and converting it into a second format, for use elsewhere. For a list of such formats, and examples, see Wikipedia, Citation styles. Andy Mabbett 11:05, 30 Mar 2007 (PDT)

Problématiques exceptionnelles

Migrées à partir de citation-brainstorming par [[BenWest 17:30, 8 Apr 2007 (PDT)]] disponible sur

The 3 main points i (Brian) came across so far are: 1) IDENTIFIERS 2) FORMAT TYPES 3) NESTING

1) In hCard/hCalendar there is a UID field. Added with URL it makes for a great unique identifier. There are loads of other identifers besides URL, ISBN, LOC call number, SKU, ISSN, etc. Many of these are unique in their domain, but not globally unique. So how to they get marked-up? Much like the hCard TEL/ADR properties, we can use something like:

<div class="uid"><span class="type">ISBN</span>: <span

This makes the encoding the most extensible... if we start use class="isbn" then it is an enumerated list, with class="type" it is open ended.

2) I keep mis-using "format", format is the medium - hardback, softback. The TYPE (there probably is a better word - container?) is book, article, conference, manifesto, etc. Much like the identifers we can make an enumerated list of values, class="book", class="article", but that boxes us in, whereas something like:
<span class="type">article</span>
leaves things more open.

3) Nesting citation data in a citation. The ability to nest the same microformat inside itself is something that other microformats don't explicitly handle.

The two options are: i) Using class="book"

<div class="hcite">
 <div class="book">
  <span class="fn">Book Title</span>
  <div class="chapter">
     <span class="fn">Chapter Title</span>

This makes things easy to nest and to figure out exactly what is associated with what, but the downside is that we have enumerated lists of values for the class properties.

ii) using the TYPE for book

<div class="hcite">
 <div class="type">book</div>
 <span class="fn">Book Title</span>
 <div class="type">chapter</div>
 <span class="fn">Chapter Title</span>

now the class="fn" is not nested inside the class="book" or class="chapter" so there would have to be some other mechanism to associate the data with the type.

citation-issues-fr was last modified: Thursday, June 28th, 2007