Skip to content

Conversation

@mjherzog
Copy link
Member

@mjherzog mjherzog commented Nov 20, 2025

This is a rewrite of the draft from:

@mjherzog
Copy link
Member Author

@jkowalleck Pushed changes resolving your comments - thanks for the review.

Copy link
Member

@pombredanne pombredanne left a comment

Choose a reason for hiding this comment

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

Here are some partial comments.

Copy link
Member

@pombredanne pombredanne left a comment

Choose a reason for hiding this comment

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

Here is second set of reviews! 👍

- The proposed change for validation messages allows multiple messages from a
single test case.
- There is no message returned for a successful validation.
- We will need to clearly define the difference between an info message and a
Copy link
Member

Choose a reason for hiding this comment

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

Makes sense.

>*Error message discussion*
The current PURL specification documentation does not contain guidance
Copy link
Member

Choose a reason for hiding this comment

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

OK, but then we should at least link to existing implementations

There is also an important perspective from [PR 747](https://github.com/package-url/purl-spec/pull/747)
regarding the expected use of PURL test messages by PURL tools.

*"I don't think it is necessary or beneficial for PURL to specify error
Copy link
Member

Choose a reason for hiding this comment

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

100% agree

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants