When I created the translator, CFF was only defined for those two resource types. Has that since changed? I'm just skeptical of exporting something that's not at all covered by the format spec.

Thanks @adam3smith for the reply (and for the original contributions in this space)! I believe what you mention is true. A bit more background: my feeling is that both the software being worked on as well as the references which were used to build the software (whether inspiration, methods, data, software, etc) are important to outline within the CITATION.cff. Otherwise it might look from a glance that the software was purely self-inspired by those making direct contributions to it.

Specifically this could be important in reference to software which may not yet have a journal article or other resource tied to it where these references and acknowledgements might traditionally be mentioned. To this effect, this is an effort of openly acknowledging the resources used to create software as it is developed.

When I use CITATION.cff in this way I often implement items under the references key to define these (which roughly has sub-keys/values that align to the convention of top-level keys for the CITATION.cff format).

do you have an example of a CFF file like that? I understand the idea to cite references and IIRC even looked at that, but CFF doesn't seem particularly well suited for that purpose (though I may have missed something).

Thanks @adam3smith , sure thing, here's an example of CITATION.cff file demonstrating what I mentioned.

... CFF doesn't seem particularly well suited for that purpose (though I may have missed something).

Would you suggest any alternatives that are better suited from a software-based perspective? I might have missed something as well; I arrived at the the format of the shared example out of a necessity to follow best known practice today while balancing integration with other formats and services and acknowledging related works + authors. Just the same, I can accept that it might be a bad way of doing things, so I'd value your input here if you have thoughts.

Hi @adam3smith , circling back around to this, would you mind if I expanded upon your original work in CFF.js with a new CFF translator, perhaps labeled as something like CFF-references to assist with what I've described in this issue?

I ask this both from seeking your input as well as respecting licensing permission (the translators repo itself doesn't include overarching LICENSING and the CFF.js file mentions a copyright belonging to you).

I don't know if we'll take it into Zotero -- since Zotero doesn't create hierarchical item types, this is conceptually quite messy -- but you're absolutely welcome to do this -- my copyright on the translator is followed by an AGPL license (which almost all translators carry).