#shwid — Public Fediverse posts

@wobweger @steffi_ge Hi, that's pretty cool!
I still see that journals ask for your #ResearchSoftware to be deposited in a generic repository with a DOI. Ugh. I can understand that this ensures long term archival, which might not be guaranteed on the git*.com where people can even nuke their repository.
How can we convince journals that citing #SHWID is superior to citing ZIP dumps with DOIs ?

@wobweger @steffi_ge Hi, that's pretty cool!
I still see that journals ask for your #ResearchSoftware to be deposited in a generic repository with a DOI. Ugh. I can understand that this ensures long term archival, which might not be guaranteed on the git*.com where people can even nuke their repository.
How can we convince journals that citing #SHWID is superior to citing ZIP dumps with DOIs ?

@wobweger @steffi_ge Hi, that's pretty cool!
I still see that journals ask for your #ResearchSoftware to be deposited in a generic repository with a DOI. Ugh. I can understand that this ensures long term archival, which might not be guaranteed on the git*.com where people can even nuke their repository.
How can we convince journals that citing #SHWID is superior to citing ZIP dumps with DOIs ?

@wobweger @steffi_ge Hi, that's pretty cool!
I still see that journals ask for your #ResearchSoftware to be deposited in a generic repository with a DOI. Ugh. I can understand that this ensures long term archival, which might not be guaranteed on the git*.com where people can even nuke their repository.
How can we convince journals that citing #SHWID is superior to citing ZIP dumps with DOIs ?

@wobweger @steffi_ge Hi, that's pretty cool!
I still see that journals ask for your #ResearchSoftware to be deposited in a generic repository with a DOI. Ugh. I can understand that this ensures long term archival, which might not be guaranteed on the git*.com where people can even nuke their repository.
How can we convince journals that citing #SHWID is superior to citing ZIP dumps with DOIs ?

SWHIDs (SoftWare Hash IDentifiers ) are persistent identifiers #PIDs for software source code artifacts such as source code files, source trees, commits, and other objects typically found in version control systems.

📣Great news: The #SHWID now meets the #ISO standard.

Congratulations 🙌 @swheritage

#OpenScience #ResearchSoftwar #FAIR #FAIR4RS #RDM #OpenInfrastructure #PIDecosystem @PIDNetworkDE

SWHIDs (SoftWare Hash IDentifiers ) are persistent identifiers #PIDs for software source code artifacts such as source code files, source trees, commits, and other objects typically found in version control systems.

📣Great news: The #SHWID now meets the #ISO standard.

Congratulations 🙌 @swheritage

#OpenScience #ResearchSoftwar #FAIR #FAIR4RS #RDM #OpenInfrastructure #PIDecosystem @PIDNetworkDE

SWHIDs (SoftWare Hash IDentifiers ) are persistent identifiers #PIDs for software source code artifacts such as source code files, source trees, commits, and other objects typically found in version control systems.

📣Great news: The #SHWID now meets the #ISO standard.

Congratulations 🙌 @swheritage

#OpenScience #ResearchSoftwar #FAIR #FAIR4RS #RDM #OpenInfrastructure #PIDecosystem @PIDNetworkDE

SWHIDs (SoftWare Hash IDentifiers ) are persistent identifiers #PIDs for software source code artifacts such as source code files, source trees, commits, and other objects typically found in version control systems.

📣Great news: The #SHWID now meets the #ISO standard.

Congratulations 🙌 @swheritage

#OpenScience #ResearchSoftwar #FAIR #FAIR4RS #RDM #OpenInfrastructure #PIDecosystem @PIDNetworkDE

SWHIDs (SoftWare Hash IDentifiers ) are persistent identifiers #PIDs for software source code artifacts such as source code files, source trees, commits, and other objects typically found in version control systems.

📣Great news: The #SHWID now meets the #ISO standard.

Congratulations 🙌 @swheritage

#OpenScience #ResearchSoftwar #FAIR #FAIR4RS #RDM #OpenInfrastructure #PIDecosystem @PIDNetworkDE