/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

Software Heritage and software identification #70

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 3.1 and 3.5 of A&P google doc

@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 8, 2018

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

This comment has been minimized.

Sign in to view
Copy link
Collaborator

danielskatz commented Feb 7, 2019

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

@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