"Section/Sub-Section headings of the Software Description paper";"Mapping from the available EML and DOAP metadata elements; a few other elements have been added to provide a better mapping to the data paper structure, with formatting guidelines" ;"Derived from the ‘name’ element. This must be extended to a concise description of the software tool and its implementation, e.g.: “BioDiv, a web-based tool for calculation of biodiversity indexes”. Format: This is a centred sentence without full stop (.) at the end." <Authors>;"Derived from the ‘developer’, ‘maintainer’ and eventually ‘helper’, ‘tester’, and ‘documenter’. From these elements, combinations of ‘first name’ and ‘last name’ are derived, separated by commas (,). Corresponding affiliations of the authors are denoted with numbers (1, 2, 3,...) in superscript at the end of each last name. If two or more authors share same affiliation, it will be denoted by use of the same superscript number. Format: centred." <Affiliations>;"Derived from the ‘developer’, ‘maintainer’ and ‘helper’. From these elements, combinations of ‘Organisation Name’, ‘Address’, ‘Postal Code’,‘City’, and ‘Country’ will constitute the affiliation." "<Corresponding authors>";"Derived from any of the ‘developer’, ‘maintainer’, ‘helper’, ‘tester’, and‘documenter’ elements. From these elements ‘first name’, ‘last name’ and ‘email’ are derived. Email addresses are written in parentheses (). In case of more than one corresponding author, these are separated by commas.Format: indented from both sides." "<Received, Revised, Accepted, and Published dates>";"These will be inserted manually by the Publisher of the data paper to indicate the dates of original manuscript submission, revised manuscript submission, acceptance of manuscript and publishing of the manuscript as data paper in the journal." <Citation>;"This will be inserted manually by the Publisher of the data paper. It will be a combination of Authors, Year of data paper publication (in parentheses), Title, Journal Name, Volume, Issue number (in parentheses), and DOI of the data paper in both native and resolvable HTTP format." <Abstract>;"Derived from the ‘short description’ element. Format: indented from both sides." <Keywords>;"Keywords should reflect most important features of the tool and areas of implementation, and should be separated by commas (,)." <Introduction>;"Free text." "<Project Description>";"Derived from ‘description’ element; if applicable, it should also include sub-elements such as ‘title’ of the project, ‘personnel’ involved in the project, ‘funding’ sources’, and other appropriate information." "<Web Location (URIs)>";"Derived from the elements ‘homepage’, ‘wiki’, ‘download page’, ‘download mirror’, ‘bug database’, ‘mailing list’, ‘blog’, ‘vendor’" "<Technical specification>";"Derived from the elements ‘platform’, ‘programming language’,‘operational system’ (if OS-specific), ‘language’ , ‘service endpoint’" <Repository>;"Derived from the elements ‘repository type’ (CVS, SVN, Arch, BK),‘repository browse uri’ (CVS, SVN, BK), ‘repository location’) SVN, BK,Arch), ‘repository module’ (CVS, Arch), ‘repository anonymous root’(CVS)" <License>;"Derived from the ‘license’ element" <Implementation>;"Derived from ‘Implements specification’ and ‘audience’ elements; please remember that this section is of primary interest to end users, and should be written in detail, if possible including use cases, citations and links." "<Additional Information>";"Any kind of helpful additional information may be included." <Acknowledgement>;"Lists all acknowledgments at the authors' discretion." <References>;"Includes literature references and web links cited in the text."