/force11-sciwg

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

"published" language #66

Closed
danielskatz opened this Issue Oct 4, 2018 · 2 comments

Comments

Assignees
No one assigned
Labels
A&P doc discussion
Projects
None yet
Milestone
No milestone
2 participants
@danielskatz @moranegg
@danielskatz
Copy link
Collaborator

danielskatz commented Oct 4, 2018

Based on discussion in Section 2 of A&P google doc

  • In the software citation principles paper, we used "published" to mean than an author had submitted the software to an archival repository along with metadata, and that the repository had issued an identifier. There is some confusion about this term. Is there a better term?
  • We also need to make clear that made public is not the same as "published"

@danielskatz danielskatz added the A&P doc discussion label Oct 4, 2018

@moranegg

This comment has been minimized.

Sign in to view
Copy link
Contributor

moranegg commented Oct 10, 2018

"Published software" should be equivalent to "published article" in the research domain.
An article that is public but not published does not have the same stature than one published with a complete set of metadata and which will result with a standard citation.

That's why software made available online, in my opinion, is not "published software", but it doesn't mean it shouldn't be cited.

I would reserve the term published software to software that was published by a journal or software that was deposited in an archive (like Zenodo, HAL, etc.).
@danielskatz

This comment has been minimized.

Sign in to view
Copy link
Collaborator

danielskatz commented Feb 7, 2019

I think this has been resolved in the document, and I'm closing this issue to avoid having duplicate discussions in 2 places - if you think this is still a problem in the document, please add a comment or make a suggestion there.

@danielskatz danielskatz closed this Feb 7, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment