Skip to content

Add missing profile specifications to ProfileIdentifierType#1226

Open
goneall wants to merge 4 commits intodevelopfrom
add-operations-profile
Open

Add missing profile specifications to ProfileIdentifierType#1226
goneall wants to merge 4 commits intodevelopfrom
add-operations-profile

Conversation

@goneall
Copy link
Member

@goneall goneall commented Feb 26, 2026

Adds operational, functional safety and service profiles

Signed-off-by: Gary O'Neall <gary@sourceauditor.com>
@goneall goneall requested review from bact and zvr February 26, 2026 22:32
Copy link
Collaborator

@bact bact left a comment

Choose a reason for hiding this comment

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

LGTM. Do we like to add "functionalSafety and "service" here as well?

@bact bact added this to the 3.1-rc2 milestone Feb 26, 2026
@bact bact added Profile:Core Core profile and related matters Profile:Operations Operations profile and related matters labels Feb 26, 2026
Signed-off-by: Gary O'Neall <gary@sourceauditor.com>
@goneall goneall changed the title Add operations profile specification to ProfileIdentifierType Add missing profile specifications to ProfileIdentifierType Feb 27, 2026
@goneall
Copy link
Member Author

goneall commented Feb 27, 2026

LGTM. Do we like to add "functionalSafety and "service" here as well?

Good catch - I'll add those to the same PR

Signed-off-by: Gary O'Neall <gary@sourceauditor.com>
Signed-off-by: Arthit Suriyawongkul <arthit@gmail.com>
@bact
Copy link
Collaborator

bact commented Feb 27, 2026

I just noticed that we have some inconsistencies between the model and the spec.

In the model, we have 3 licensing profiles:

  1. Licensing
  2. SimpleLicensing
  3. ExpandedLicensing

In ProfileIdentifierType, we have 2 licensing profiles:

  1. "simpleLicensing"
  2. "expandedLicensing"

In the Conformance chapter of the spec, we have 1 licensing profile:

  1. Licensing profile

The spec probably treat all *Licensing profiles as one.

Should we add the "licensing" entry to ProfileIdentifierType as well? To make it match the model.

Note that Licensing profile is different from almost all other profiles. It contains only profile information and contains no model part (there are no classes/properties/vocabularies in Licensing profile) -- all classes and properties used in Licensing profile conformance are from Core, Software, and SimpleLicensing profiles. Another profile that also contains no model part is the Lite profile.

@bact
Copy link
Collaborator

bact commented Feb 27, 2026

@goneall We can merge this PR as it is and manage the "licensing" entry in ProfileIdentifierType question in another PR.

Since it is about licensing, would like to hear from @swinslow too.

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

Labels

Profile:Core Core profile and related matters Profile:Operations Operations profile and related matters

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants