Re: [jats-list] Re: Software citations

[Alf Eaton <eaton.alf@xxxxxxxxx>]

That's a decent workaround, thanks Bruce. It could also be argued that
any <edition> element in a citation with @publication-type="software"
contains the version information, by default (unless there's some
other meaning of "edition" that could be appropriate for software).

Alf

On 13 March 2014 12:13, Bruce Rosenblum <bruce@xxxxxxxxx> wrote:
> Rather than add more elements to element-citation, you might try using the
> edition element with specific-use to indicate "software-version" I don't
> think that approach would be considered "tag abuse"
>
> Bruce
>
>
> At 08:06 AM 3/13/2014, Alf Eaton wrote:
>>
>> I did find
>> <https://www.ncbi.nlm.nih.gov/pmc/pmcdoc/tagging-guidelines/citations/v3/programs.html>,
>> but it looks like the recommendations haven't been updated for about
>> 10 years, as it only covers "Computer Programs on CD-ROM, DTD [sic],
>> or Disk".
>>
>> The most suitable example there puts the version and OS information in
>> "<edition>PC 1.1a version</edition>", which seems like a reasonable
>> compromise.
>>
>> Perhaps it's time to add a <version> element to <element-citation>,
>> which may refer to a specfic version number (or branch name, commit
>> hash, etc) of the software and have an optional xlink:href with a URL
>> for that release?
>>
>> Alf
>>
>> On 13 March 2014 11:53, Alf Eaton <eaton.alf@xxxxxxxxx> wrote:
>> > Does anyone have any examples of software citations marked up with
>> > <element-citation>? I've been looking around the JATS document for
>> > citations[1], and can't find any mention of software (though there are
>> > examples for "web", "online" and "database" citations).
>> >
>> > In particular, I'm looking to mark up a citation of this software:
>> > http://www.cgl.ucsf.edu/home/sparky/
>> >
>> > Ideally, it would be possible to use the URL plus their recommended
>> > citation string:
>> >
>> > T. D. Goddard and D. G. Kneller, SPARKY 3,
>> > University of California, San Francisco
>> >
>> > and additionally mark up the version and operating system of the
>> > software that was used.
>> >
>> > As there aren't fields in <element-citation> for a version number or
>> > an operating system, do people just use the standard citation fields
>> > and then rely on versions, OS, etc being described in the methods
>> > section?
>> >
>> > Also of relevance is Mozilla Science Lab's "Code as a research object"
>> > project[2], which encourages authors to archive versioned releases of
>> > their software, and provide DOIs of those archives for others to cite.
>> >
>> > Thanks,
>> > Alf
>> >
>> >
>> > [1] http://jatspan.org/niso/publishing-1.1d1/#p=tagging-references
>> > [2] http://mozillascience.org/code-as-a-research-object-a-new-project/
>
>
> -------------------------------------------------------------------
> This email message and any attachments are confidential. If you are not the
> intended recipient, please immediately reply to the sender or call
> 617-932-1932 and delete the message from your email system. Thank you.
> -------------------------------------------------------------------
> Bruce D. Rosenblum
> Inera Inc.
> 19 Flett Road
> Belmont, MA 02478
> 617-932-1932 (office)
> bruce@xxxxxxxxx