Jump to content

COinS

Unchecked
From Wikipedia

ContextObjects in Spans, commonly aabreviated COinS, is the 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 the copy of the book in one's own library.[1]

History

[edit]

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 the "link resolver". The OpenURL framework was later standardized as ANSI/NISO Z39.88 in 2004.[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 the 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-Arie[5] and the working paper by Chudnov and Jeremy Frumkin.[citation needed] Discussion of the latter on the GPS-PCS mailing list[6] resulted in the 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 http://ocoins.info/, which includes specific guides to implement COinS for journal articles and books and the COinS generator.

Summary of the data model

[edit]

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 the couple of simple fields. However the guidelines are not required part of COinS, so the standard does not provide the strict metadata model like Dublin Core or the Bibliographic Ontology.

Use in web sites

[edit]

The following web sites make use of COinS:

Server-side applications

[edit]

Several server-side applications embed COinS:

Client tools

[edit]

Client tools which can use COinS include:

See also

[edit]

References

[edit]
  1. ↑ Daniel Chudnov: COinS for the Link Trail. In: Library Journal. 2006年7月, S. 8–10.
  2. ↑ ANSI/NISO Z39.88 - The OpenURL Framework for Context-Sensitive Services. 2004. ISBN 978-1-880124-61-1.
  3. ↑ "Autodiscovery and embedding metadata". gcs-pcs-list. 20 December 2004. Retrieved 20 March 2011.
  4. ↑ "sample inline openurl". gcs-pcs-list. 6 January 2005. Retrieved 20 March 2011.
  5. ↑ Herbert Van de Sompel, Beit-Arie, Oren: Generalizing the OpenURL Framework beyond References to Scholarly Works - The Bison-Futé Model. In: D-Lib. 7, Nr. 7/8, July/August 2001, ISSN 1082-9873. Script error: No such module "Vorlage:Handle"..
  6. ↑ "GCS-PCS mailing list". Groups.google.com. Retrieved 7 June 2010.
  7. ↑ "Latent OpenURLs in HTML for Resource Autodiscovery, Localization and Personalization". Retrieved 20 March 2011. Unknown parameter |coauthors= ignored (help)
  8. ↑ Apps, Ann (16 April 2003). "Z39.88-2004 KEV Implementation Guidelines". Retrieved 20 March 2011.
  9. ↑ 9.0 9.1 "Mendeley Web now supports COinS". 6 August 2009. Retrieved 6 August 2009.
  10. ↑ Peter Binkley's plugin, described further in this post, can be used to refer to external sources within the WordPress post
  11. ↑ ScholarPress Coins plugin generates self-referential COinS for each WordPress post
  12. ↑ John Miedema's plugin creates COinS for books referenced in WordPress posts
[edit]

guided tour test

Retrieved from "https://test2.wikipedia.org/wiki/COinS"