-
Notifications
You must be signed in to change notification settings - Fork 46
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.
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
SPDX 2->3 conversion of ExternalPackageReferences #81
Comments
The following SPDX 2 external package ref types don't seem to have an SPDX 3 counterpart:
How would they be sorted into identifier vs reference? |
I would suggest - reference. |
This needs to be handled, but not considered a blocker for 3.0-rc |
Kate and I discussed this. We probably should handle these in RC2 since it will impact the vocabulary. |
@maxhbr - with @armintaenzertng being out, would you mind adding a pull request to add the missing external reference types? |
I opened #484 to address the issue of missing ExternalRefTypes. However, the initial question of this issue still stands, namely what to do with the |
I'm thinking we should change the type of ExternalRefTypes to be |
Partial fix for issue #81 Signed-off-by: Gary O'Neall <[email protected]>
Partial fix for issue #81 Signed-off-by: Gary O'Neall <[email protected]>
This was resolved with PR #487 |
This is part of #74:
Edit: updated after I understood that ExternalPackageReference will be split into two new properties. Some references will convert to ExternalIdentifier, others to ExternalReference. See the migration documentation for a conversion guideline.
There remain two problems when the
category
isOTHER
:type
can be String-valued. Should this then be converted to SPDX3ExternalIdentifierType.other
orExternalReferenceType.other
?locator
can be an arbitrary String (without spaces) in SPDX2, but the SPDX3ExternalReference.locator
must be a URI.ExternalIdentifier.identifier
would be a String, but can we be sure that the SPDX2 reference of categoryOTHER
is actually an identifier?The text was updated successfully, but these errors were encountered: