Skip to content

Update 0.Introduction.md #41

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Oct 23, 2023
Merged

Update 0.Introduction.md #41

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions Chapters/0.Introduction.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,15 +12,15 @@ chain, developer communities need tools to cope with the increasing complexity.

A key building block for addressing this issue is a system of *intrinsic*
identifiers that allows to precisely pinpoint the exact version of any software
artefact, at all levels of granularity, *without relying* on any central registry
artifact, at all levels of granularity, *without relying* on any central registry
or naming authority.

With this specification, the SWHID working group makes such a system of
intrinsic identifiers, originally developed for the Software Heritage
universal source code archive, available to all stakeholder.
universal source code archive, available to all stakeholders.

For the sake of clarity, we will use examples drawn directly from the Software
Heritage archive, but notice that systems for persistent archival of software
artefacts, as well as resolution of SWHIDs are out of the scope of this
artifacts, as well as resolution of SWHIDs are out of the scope of this
specification, and the SWHID specification does not require in any way the
use of Software Heritage.