Skip to content
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

docs(schema): clarify purls must not contain versions #317

Closed
wants to merge 1 commit into from
Closed

docs(schema): clarify purls must not contain versions #317

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
3 changes: 2 additions & 1 deletion docs/schema.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -668,7 +668,8 @@ within its ecosystem. The two fields must both be present, because the
The `purl` field is a string following the
[Package URL specification](https://github.com/package-url/purl-spec) that
identifies the package, without the `@version` component.
This field is optional but recommended.
This field is optional but recommended. It *must not* contain a `version`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is already made explicit on line 670?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Huh. Couldn't see it for the trees at the time :-(

component.

Different ecosystems can define the same names; they identify different
packages. For example, these denote different libraries with different sets of
Expand Down
Loading