Track tasks and feature requests
Join 40 million developers who use GitHub issues to help identify, assign, and keep track of the features and bug fixes your projects need.
Sign up for free See pricing for teams and enterprisesLeverage links with the "cite-as" relation type #58
Comments
This comment has been minimized.
This comment has been minimized.
|
Note that other Signposting patterns can also be leveraged by the citeas.org service. Links with the "describedby" relation type provided by the landing page URI lead to bibliographic information about the artifact the landing page is about. Using the same landing page as above, the complete HTTP Link header is as follows: The bibliographic information that is linked to is - in this case - obviously also available from the DOI API. But that requires the client to have out-of-bound knowledge about that API. With the above "describedby" links, a client can just follow its nose to the metadata. |
RFC8574 defines the "cite-as" link relation type that can, among others, be used to point from a landing page URI to the URI that should be used for citation purposes. A major motivation for defining the relation type was that research found that a very significant number of resources that have a DOI are not cited by means of their DOI but rather by means of their landing page URI [1].
A link with the "cite-as" relation type would typically be provided in the HTTP Link header of the landing page. For example, using the landing page https://easy.dans.knaw.nl/ui/datasets/id/easy-dataset:61891 for a dataset in the DANS EASY collection:
The "cite-as" approach is part of the broader Signposting effort aimed at clarifying common landing page patterns to machines by using utterly simple REST/HATEOAS techniques. Early Signposting adopters typically implement "cite-as" with priority. As such:
[1] Van de Sompel, H., Klein, M., and Shawn, J. (2016) Persistent URIs Must Be Used To Be Persistent. Poster at WWW 2016; arXiv preprint at http://arxiv.org/1602.09102