ContextObjects in Spans, commonly abbreviated COinS, is a method to embed bibliographic metadata in the HTML code of web pages. This allows bibliographic software to publish machine-readable bibliographic items and client reference management software to retrieve bibliographic metadata. The metadata can also be sent to an OpenURL resolver. This allows, for instance, searching for a copy of a book in one's own library.1
In the late 1990s OpenURL was created at Ghent University as framework to provide context-sensitive links. The OpenURL link server implementation called SFX was sold to Ex Libris Group which marketed it to libraries, shaping the idea of a "link resolver". The OpenURL framework was later standardized as ANSI/NISO Z39.88 in 2004 (revised 2010).2 A core part of OpenURL was the concept of "ContextObjects" as metadata to describe referenced resources.
In late 2004 Richard Cameron, the creator of CiteULike, drew attention to the need for a standard way of embedding metadata in HTML pages.3 Daniel Chudnov suggested the use of OpenURL.4 Embedding OpenURL ContextObjects in HTML had been proposed before by Herbert Van de Sompel and Oren Beit-Arie5 and a working paper by Chudnov and Jeremy Frumkin.citation needed Discussion of the latter on the GPS-PCS mailing list6 resulted in a draft specification for embedding OpenURLs in HTML,7 which later became COinS. A ContextObject is embedded in an HTML span element.
The adoption of COinS was pushed by various publications and implementations. The specification can now be found at OCOinS.info, which includes specific guides to implement COinS for journal articles and books.
From OpenURL 1.0 COinS borrows one of its serialization formats ("KEV") and some ContextObject metadata formats included in OpenURL implementation guidelines.8 The ContextObject implementation guidelines of COinS include four publication types (article with several subtypes, book, patent, and generic) and a couple of simple fields. However the guidelines are not required part of COinS, so the standard does not provide a strict metadata model like Dublin Core or the Bibliographic Ontology.
The following web sites make use of COinS:
Several server-side applications embed COinS:
Client tools which can use COinS include:
- Chudnov, Daniel (2006-07-14). "COinS for the Link Trail". Library Journal: 8–10. Archived from the original on 2006-10-22.
- ANSI/NISO Z39.88-2004(R2010) - The OpenURL Framework for Context-Sensitive Services. NISO.org. 2004. ISBN 978-1-880124-61-1.
- "Autodiscovery and embedding metadata". gcs-pcs-list. 2004-12-20. Retrieved 2011-03-20.
- "sample inline openurl". gcs-pcs-list. 2005-01-06. Retrieved 2011-03-20.
- Van de Sompel, Herbert; Beit-Arie, Oren (July–August 2001). "Generalizing the OpenURL Framework beyond References to Scholarly Works - The Bison-Futé Model". D-Lib 7 (7/8). doi:10.1045/july2001-vandesompel. ISSN 1082-9873.
- "GCS-PCS mailing list". Groups.google.com. Retrieved 2010-06-07.
- Hellman, Eric (ed.). "Latent OpenURLs in HTML for Resource Autodiscovery, Localization and Personalization" (draft). OCOinS.info. Retrieved 2011-03-20.
- Apps, Ann (2003-04-16). "Z39.88-2004 KEV Implementation Guidelines". MIMAS, The University of Manchester, UK. Retrieved 2011-03-20.
- Reichelt, Jan (2009-08-05). "Mendeley Web now supports COinS". Retrieved 2013-12-14.
- Binkley, Peter (2005-08-09). "COinS WordPress plugin update". WallAndBinkley.com. Can be used to refer to external sources within a WordPress post.
- Boggs, Jeremy (2009-05-13). "ScholarPress Coins plugin". WordPress.org. Generates self-referential COinS for each WordPress post.
- Miedema, John (2008-06-07). "OpenBook Book Data". WordPress.org. Creates COinS for books referenced in WordPress posts.