Skip to content
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

Accepted SPEC should have DOI #159

Open
pllim opened this issue Sep 28, 2022 · 6 comments
Open

Accepted SPEC should have DOI #159

pllim opened this issue Sep 28, 2022 · 6 comments

Comments

@pllim
Copy link
Contributor

pllim commented Sep 28, 2022

You probably will do it but just in case...

@stefanv
Copy link
Member

stefanv commented Sep 28, 2022

Do DOIs refer to a specific version of a document, or just to a URL in general? If the latter, should be feasible.

@pllim
Copy link
Contributor Author

pllim commented Sep 28, 2022

I think whatever works for you is fine. Though if the SPEC is going to be hard to change after being finalized and each subsequent edit is significant in itself, a separate DOI per version might be better. But otherwise, general is easier to maintain?

@stefanv
Copy link
Member

stefanv commented Sep 28, 2022

Yes, the reason I am asking is because SPECs are defined to be living documents, so the idea is that they will evolve over time. The history will be in github, of course.

What is the advantage of having a DOI, other than a shorter URL?

@pllim
Copy link
Contributor Author

pllim commented Sep 29, 2022

I was thinking more like Zenodo for citation. Is that appropriate here? https://zenodo.org/

@stefanv
Copy link
Member

stefanv commented Sep 29, 2022

@jarrodmillman may be better positioned to answer that question.

@MridulS
Copy link
Member

MridulS commented Sep 29, 2022

Zenodo can indeed give out "living" DOIs, it has a base link which redirects to the latest version of a document/artifact.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants