Software Heritage and software identification

force11 / force11-sciwg

FORCE11 Software Citation Implementation Working Group

https://www.force11.org/group/software-citation-implementation-working-group

BSD 3-Clause "New" or "Revised" License

56 stars 18 forks source link

Software Heritage and software identification #70

Closed danielskatz closed 5 years ago

danielskatz commented 5 years ago

Based on discussion in Section 3.1 and 3.5 of A&P google doc

In 3.1.4, there is an example of identification of software in software heritage: https://archive.softwareheritage.org/swh:1:rev:81c66c0db5c381dacc0841a4c16e0b3876b15b89;origin=https://github.com/applicationskeleton/Skeleton/
In a comment, another way to identify this same software is https://identifiers.org/swh:1:rev:81c66c0db5c381dacc0841a4c16e0b3876b15b89
Which, if either, should we recommend?

moranegg commented 5 years ago

I would recommend the first one as the by default url for the swh-id and add it is possible to resolve the identifier with different resolvers (which is also possible with N2t).

I believe that the comment was about the usage of an identifier instead of a url.

So I will distinguish between the swh-id -swh:1:rev:81c66c0db5c381dacc0841a4c16e0b3876b15b89;origin=https://github.com/applicationskeleton/Skeleton/ and the permalinks available with different resolvers

danielskatz commented 5 years ago

I think we've moved this discussion into the document, and perhaps finished it there, so I'm going to close this issue