-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Field suggestion: latest CRAN release #18
Comments
we could use the crandb API https://github.com/metacran/crandb to get it, not sure if you can do an external API request though in the codemetar workflow? |
@cboettig there is no "latest version at provider" term right? I tend to think this field would be a layer added for our registry after codemeta.json creation 🤔 |
right. EDIT just to expand on this, technically a codemeta.json file is an annotation of a single instance (i.e. single version) of software. (just like a DOI points to a single version of a paper or dataset). to have consistent semantics, I think you would technically want a separate file asserting the provenance relationships between different versions. not sure if PROV has any notion of "latest", in general it seems like a dubious proposition to record in data file, at least without a timestamp associated with that assertion. |
nowadays one could add that using |
Updated comment above about why this doesn't exist. Good point about I think we can close this? |
codemetar
/CodeMeta do not have that, there is a provider term but it'll only indicate whether the package is on CRAN/BioConductor.Would it be interesting to know the version and date associated with the latest CRAN release using metacran?
The text was updated successfully, but these errors were encountered: