From Microformats Wiki
Revision as of 12:09, 6 January 2008 by ChristopheDucamp (talk | contribs) ([fr: sync'd with english version - translation in progress])
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


[copie et traduction du billet de la liste de discussion ; actuellement non formaté et non édité - chantier en cours]


Nous pouvons rapidement avoir des microformats pour les codes ISBNs et ISSNs. La nature très spécifique de la manière dont ces codes sont formatés signifie qu'un assemblement plus en profondeur serait superflu. De tels microformats seraient des composants utiles dasn un bon nombre d'autres microformats actuellement proposés. Agir maintenant assurera qu'une méthode standard pourra s'appliquer dans de tels formats.


Andy Mabbett (traduction Christophe Ducamp


Cette page traite de l'usage des ISBNs ; presque tout cela s'applique également aux ISSNs.


Comment marquer les numéros ISBN, de façon à ce qu'ils puissent être extraits et que le livre ad'hoc soit trouvé dans les catalogues de biblothèques, librairies en ligne, etc., par exemple la façon dont Wikipedia utilise les ISBNs. Au lieu de cela, ce service pourrait être la cible par un agent utilisateur (comme pourrait l'être WorldCat pour les ISSNs). Ceci bénéficierait aux plusieurs milliers d'auteurs, et les millions de clients d'ISBNs et ISSNs.

Comment produire un microformat standard ISBN disponible comme un composant pour d'autres microformats.

Les ISBNs incluent un numéro de résumé et peuvent seulement n'avoir que soit 10 ou 13 chiffres de long. (Les ISSNs sont à 8 chiffres)


There as been previous discussion of marking-up ISBNs (International Standard Book Numbers); for example around the proposed citation microformat.

I (Andy Mabbett) believe, however, that a microformat for ISBN should stand alone, and thus be available for use in any other microformat (for recipes, for example, or for hResume, hAtom, hReview or hListing, as well as citations).


So many websites use ISBN numbers, that we would never have time to examine even 1% - so we could ever be sure that we were dealing with cases in the larger side of an 80-20 divide.

However, there are very few ways in which ISBN numbers can be marked up, in a meaningful and valid sense. Furthermore, the very nature of ISBNs, with rigidly defined formats, and check-sums, means that detecting, validating and parsing ISBNs is relatively easy to describe.

Consider these examples (all found on the aforesaid citations-examples)

        <div class="isbn">0-313-32847-1</div>

        <span id="lblIsbn">0-313-32847-1</span>

        <span class="isbnNumber">0195162471</span> 

(note that "isbnNumber" is a tautology!)

and these other possible methods of marking up those ISBNs:

        <div class="isbn">ISBN 0-313-32847-1</div> 

        <span id="lblIsbn">ISBN: 0-313-32847-1</span> 

        <span class="isbnNumber">the ISBN is 0195162471</span> 

        <span class="isbn">ISBN: 0-95115-320-X</span> 

in each case, the marked-up text includes a valid ISBN (some with permitted, but superfluous, dashes) and, in the latter cases, some other non-numerical characters. All a parser need do is discard the non numerical characters, apart from a possible "X" check-digit (it's interesting to note that no "X" check-digit occurs on citation-examples), and check that the remaining digits validate to the included checksum digit.

If the mark-up has introduced additional digits:

        <span class="isbnNumber">the ISBN of book #42 is 0195162471</span> 

then a parser may simply discard the results as invalid - and thus requiring a more tightly applied element.

Prochaines étapes

Decide whether ISBNs should be used as TYPEs of UIDs, or be a stand-alone microformat.

A test-case implementation should be made available, perhaps in a beta version of Operator.

A test page using class="isbn", which has two with "X" check digits, is available and further examples can be added to it.

Additional examples should be created using UID and mark-up examples that already exist in the wild should be marked-up to see if UID covers all these scenarios.

Voir aussi