Skip to content

Conversation

@prabhu
Copy link
Contributor

@prabhu prabhu commented Aug 23, 2025

None of the frontier models and I can answer the question about whether the version is mandatory or not for composer! I'm assuming it is mandatory. All the tests include version, so reinforces the view that the version is mandatory.

  • Defined Requirements: The name_definition and version_definition are now correctly marked as "required", as they are mandatory components for a valid composer purl.
  • Added Normalization Rules: To enforce the lowercasing requirement, normalization_rules have been added to both the namespace_definition and name_definition.
  • Improved Descriptions: The note for the version_definition has been added to state clearly that the version is a required component.
  • Expanded Examples: An additional example from the reference has been included to provide better coverage.

Signed-off-by: Prabhu Subramanian <[email protected]>
@prabhu prabhu marked this pull request as draft August 24, 2025 20:15
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.

@prabhu Thanks. I feel this may be moot after all based on the comments below? Please check!

},
"version_definition": {
"native_name": "version"
"requirement": "required",
Copy link
Member

Choose a reason for hiding this comment

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

Versions are never required per spec.

"note": "The namespace is the vendor. The namespace is not case sensitive and must be lowercased."
"note": "The namespace is the vendor. The namespace is not case sensitive and must be lowercased.",
"normalization_rules": [
"It is not case sensitive and must be lowercased."
Copy link
Member

Choose a reason for hiding this comment

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

This is redundant with the "case_sensitive" flag IMHO that implies lowercasing?

"note": "The name is not case sensitive and must be lowercased. Private, local packages may have no name. In this case you cannot create a purl for these."
"note": "The name is not case sensitive and must be lowercased. Private, local packages may have no name. In this case you cannot create a purl for these.",
"normalization_rules": [
"It is not case sensitive and must be lowercased."
Copy link
Member

Choose a reason for hiding this comment

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

This is redundant with the "case_sensitive" flag IMHO that implies lowercasing?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants