PUBLIC MARKS from decembre with tags coins & metadonnée

Principalement, l’OpenURL est fait pour permettre d’accéder rapidement à une ressource rencontrée quelque part sur Internet : un lien OpenURL tient compte du résolveur auquel vous êtes (institutionnellement) rattaché et vous propose * un lien vers l’article en ligne, s’il s’agit d’une ressource en ligne * un lien vers la notice dans le catalogue de votre bibliothèque, s’il s’agit d’un document papier. Pourquoi ? D’abord pour le principe. A partir du moment où nous mettons en ligne des métadonnées, il est normal de les fournir dans un format à peu près standard, permettant de les réexploiter. Et ceci indépendamment des usages que, moi-même, je pourrais imaginer : Donc si une bibliothèque de médecine dispose d’un résolveur OpenURL, elle peut indiquer notre catalogue à ses étudiants : ils font une recherche et rebondissent ensuite vers leur propre BU, grâce au plugin LibX que celle-ci aura pris soin de leur proposer.

The URI microformat takes advantage of OpenURL and existing link resolver solution.It defines a convention of plugging URI metadata in HTML page. If it is adopted and widely used,now a microformat-aware application (be a greasemonkey script, or a web service) can grab the identifier and point to your local OpenURL resolver, you immediately get the copy from local library. It is very similar to COINS, but it's much simpler and cleaner, anyone can understand and use it, and its aplication can be beyond traditional research library. e.g. in a public library, you can use amazon as catalog and immediately check if it's available in local collection. COinS provides a great number of additional capabilities that URI microformat can't support. Since COinS can't be dismissed for this reason, it doesn't make sense to me to create yet another standard that does the same thing with so little savings.I will grant that the COinS is less intuitive.....

test Libx pour bobigny....

To embed citation metadata into html in such a way that processing agents can discover, process and make use of the metadata. Since an important use of this metadata will be to allow processing agents to make OpenURL hyperlinks for users in libraries (latent OpenURL), the method must allow the metadata to be placed any where in HTML that a link might appear. In the absence of some metadata-aware agent, the embedded metadata must be invisible to the user and innocuous with respect to HTML markup. To meet these requirements, the span element was selected. The NISO OpenURL ContextObject is selected as the specific metadata package. The resulting specification is named "ContextObject in SPAN" or COinS for short. A COinS Generator site is available - See : COinS Processors Alf Eaton's Greasemonkey script for processing COinSVirginia Tech's