There is a newer version of this record available.

Other Open Access

Citation File Format (CFF)

Druskat, Stephan

DataCite XML Export

<?xml version='1.0' encoding='utf-8'?>
<resource xmlns:xsi="" xmlns="" xsi:schemaLocation="">
  <identifier identifierType="DOI">10.5281/zenodo.1003150</identifier>
      <creatorName>Druskat, Stephan</creatorName>
      <nameIdentifier nameIdentifierScheme="ORCID" schemeURI="">0000-0003-4925-7248</nameIdentifier>
      <affiliation>Humboldt-Universität zu Berlin, Department of German Studies and Linguistics, Berlin, Germany</affiliation>
    <title>Citation File Format (CFF)</title>
    <subject>citation file format, CFF, citation files, software citation, format, YAML, software sustainability, research software</subject>
    <date dateType="Issued">2017-10-06</date>
  <resourceType resourceTypeGeneral="Text">Other</resourceType>
    <alternateIdentifier alternateIdentifierType="url"></alternateIdentifier>
    <relatedIdentifier relatedIdentifierType="URL" relationType="IsSupplementTo"></relatedIdentifier>
    <relatedIdentifier relatedIdentifierType="DOI" relationType="IsVersionOf">10.5281/zenodo.1003149</relatedIdentifier>
    <rights rightsURI="">Creative Commons Attribution Share Alike 4.0 International</rights>
    <rights rightsURI="info:eu-repo/semantics/openAccess">Open Access</rights>
    <description descriptionType="Abstract">&lt;p&gt;The &lt;strong&gt;Citation File Format&lt;/strong&gt; (&lt;strong&gt;CFF&lt;/strong&gt;) is a human- and machine-readable format for &lt;em&gt;CITATION&lt;/em&gt; files. These files provide citation metadata for (research and scientific) software. The format aims to support all use cases for software citation described in [1]. CFF is serialized in YAML 1.2, and is therefore Unicode-based and cross-language (in terms of both natural language scripts and programming languages). This specification, together with the Unicode standard for characters, aims to provide all the information necessary to understand CFF, and to use (i.e., write) and re-use (i.e., read, validate, convert from) it. These specifications are maintained openly at;/p&gt;


&lt;p&gt;[1] A. M. Smith, D. S. Katz, K. E. Niemeyer, and FORCE11 Software Citation Working Group, &amp;ldquo;Software citation principles,&amp;rdquo;&lt;em&gt; PeerJ Computer Science&lt;/em&gt;, vol. 2, p. e86, Sep. 2016 [Online]. Available:;/p&gt;</description>
    <description descriptionType="Other">{"references": ["A. M. Smith, D. S. Katz, K. E. Niemeyer, and FORCE11 Software Citation Working Group, \"Software citation principles,\" PeerJ Computer Science, vol. 2, p. e86, Sep. 2016 [Online]. Available:", "S. Druskat, \"Track 2 Lightning Talk: Should CITATION files be standardized?\" in Proceedings of the Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE5.1), 2017 [Online]. Available:", "R. Wilson, \"Encouraging citation of software - introducing CITATION files.\" 2013 [Online]. Available:", "O. Ben-Kiki, C. Evans, and I. d\u00f6t Net, \"YAML Ain't Markup Language (YAML) Version 1.2. 3rd Edition, Patched at 2009-10-01.\" 2009 [Online]. Available:", "J.-M. Hufflen, \"Names in bibtex and mlBibTeX,\" TUGboat, vol. 27, no. 2, pp. 243\u2013253, Nov. 2006 [Online]. Available:"]}</description>
All versions This version
Views 896111
Downloads 47754
Data volume 63.0 MB7.1 MB
Unique views 73987
Unique downloads 38348


Cite as