Software Citation Principles¶
Smith, A. M., Katz, D. S., & Niemeyer, K. E. (2016). Software Citation Principles. PeerJ Computer Science, 2.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Persistent Identifier
- The publication-identifier infrastructure ported to research-software citation once software was recognized as a citable output, the structural move being to make the resolver responsible for the moving target.
This sourceExtends persistent-identifier/resolver infrastructure to research software as a citable, moving-target output.
Supported in partVerified against the publisher's abstract
Supplies the principle that software should be cited as a research output, but says nothing about porting publication-identifier infrastructure or a resolver owning a moving target.
“Based on a review of existing community practices, the goal of the working group was to produce a consolidated set of citation principles that may encourage broad adoption of a consistent policy for software citation across disciplines and venues.”
- The publication-identifier infrastructure ported to research-software citation once software was recognized as a citable output, the structural move being to make the resolver responsible for the moving target.
Verification¶
Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Read against the text for 1 of 1 citation: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:1c88d84a95fe · see in the full table