Closed andrecastro0o closed 4 months ago
using https://citation-file-format.github.io/cff-initializer-javascript/ to generate citation.cff
the use of
type: software
has to do with the only 2 available values for available type
type: enum (software or dataset)`
https://github.com/citation-file-format/citation-file-format/issues/430#issuecomment-1517691065 argues that:
Also, this is generally a decision of setting cut-off points, i.e., it depends on the resolution of the argument if something is software (including, e.g., build instructions, documentation, metadata files), or if everything is a complex object (e.g., are constants really software or data, etc.). For your use cases, I lean towards arguing that documentation is part of the object, whereas OERs usually aren't mainly software, even if they are implemented using software. For this argumentation, CFF is a valid format for documentation, but not for OERs.
At this level of granularity, I am happy to settle for software
as opposed to dataset
. Also because there's a tiny software component. And an ontology can might be understood as software.
@SArndt-TIB
I tried to create a DOI via zenodo github integration but was limited to the repos under my own github namespace. TIBonto repos are not there, of course :)
Hence I didnt create a DOI for the repo, but I am not too bothered about it.
If you fancy getting a DOI minted for this repo , cool, but I wouldn't spend more than 15min trying to achieve it
See: