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

Annex A: Fix typo: SpecVerion, interoperabiility #923

Merged
merged 3 commits into from
May 3, 2024
Merged

Annex A: Fix typo: SpecVerion, interoperabiility #923

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c85548b
Fix typo: SpecVerion, interoperabiility
bact Apr 21, 2024
35afdfb
Merge branch 'development/v3.0.1' into fix-typo-diffs-from-previous-e…
bact Apr 23, 2024
6fa7a79
Merge branch 'development/v3.0.1' into fix-typo-diffs-from-previous-e…
bact Apr 30, 2024
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
36 changes: 15 additions & 21 deletions docs/annexes/diffs-from-previous-editions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -211,7 +211,6 @@ The completeness property would be constructed based on the following:

Relationship migration is being worked out in the relationships spreadsheet. Once completed, the following table will reflect the translation for relationship types from SPDX 2.3 to SPDX 3.0:


| SPDX 2.3 Relationship Type | SPDX 3.0 Relationship Type | Swap to and from? | LifecycleScopeType |
|----------------------------|----------------------------|-------------------|--------------------|
| AMENDS | amendedBy | Y | |
Expand Down Expand Up @@ -285,10 +284,9 @@ Changing the snippetFromFile from a property to a relationship [to be filled in]

### SpecVersion


#### Description of Change

The type of SpecVerion is changed from a simple string without constraints to a SemVer string which must follow the [Semantic Versioning format](https://semver.org/).
The type of SpecVersion is changed from a simple string without constraints to a SemVer string which must follow the [Semantic Versioning format](https://semver.org/).

This adds a constraint where a patch version is required. Previous usage of the SpecVersiononly included the major and minor version.

Expand Down Expand Up @@ -330,7 +328,7 @@ example

Not used

#### Range / Where Used
#### Range / Where Used

LicenseException

Expand All @@ -344,13 +342,11 @@ This field has not been used.

licenseInfoInFiles


#### Tag/Value Name

LicenseInfoInFiles


#### Range / Where Used
#### Range / Where Used

Package

Expand All @@ -368,7 +364,7 @@ filesAnalyzed

FilesAnalyzed

#### Range / Where Used
#### Range / Where Used

Package

Expand Down Expand Up @@ -396,7 +392,7 @@ ReleaseDate

releaseTime

#### Range / Where Used
#### Range / Where Used

Package

Expand All @@ -418,7 +414,7 @@ BuildDate

buildTime

#### Range / Where Used
#### Range / Where Used

Package

Expand All @@ -440,7 +436,7 @@ ValidUntilDate

validUntilTime

#### Range / Where Used
#### Range / Where Used

Package

Expand All @@ -462,7 +458,7 @@ ExternalDocumentRef

import

#### Range / Where Used
#### Range / Where Used

SpdxDocument (Creation Information)

Expand All @@ -486,7 +482,7 @@ FileChecksum, PackageChecksum

verifiedUsing property and Hash class

#### Range / Where Used
#### Range / Where Used

Package, File

Expand All @@ -508,7 +504,7 @@ N/A - parsed from a string following the Checksum: keyword.

hashAlgorithm

#### Range / Where Used
#### Range / Where Used

Package, File

Expand All @@ -530,7 +526,7 @@ PackageName, FileName

name

#### Range / Where Used
#### Range / Where Used

Package, File

Expand Down Expand Up @@ -576,7 +572,7 @@ PackageHomePage

homePage

#### Range / Where Used
#### Range / Where Used

#### Rationale

Expand Down Expand Up @@ -636,7 +632,6 @@ Custom Additions have been added in SPDX 3.0 which operate in a similar manner t

### License Exception


#### SPDX 2.3 Model Name

LicenseException
Expand Down Expand Up @@ -789,17 +784,17 @@ Note that additional purposes can be added using the additionalPurpose property.

## Serialization Formats

SPDX 3.0 implements a JSON-LD format which has consistent class and property names with the model.
SPDX 3.0 implements a JSON-LD format which has consistent class and property names with the model.

See the SPDX 3.0 JSON Schema for the format specifics.

The Tag/Value, YAML, RDF/XML and Spreadsheet formats are not supported.

Additional serialization formats are being considered for the SPDX 3.1 release.

# A.2 Differences between V2.3 and V2.2.2 <a name="A.2"></a>
# A.2 Differences between V2.3 and V2.2.2 <a name="A.2"></a>

V2.3 has added new fields to improve the ability to capture security related information and to improve interoperabiility with other SBOM formats.
V2.3 has added new fields to improve the ability to capture security related information and to improve interoperability with other SBOM formats.

Key changes include:

Expand Down Expand Up @@ -880,7 +875,6 @@ SPDX Lite | Appendix VIII | Annex H/G* |
SPDX File Tags | Appendix IX | Annex I/H* | Annex H
Differences from Earlier SPDX Versions | N/A | Annex J/I* | Annex I


*_This edition featured inconsistent lettering._

# A.5 Differences from V2.2 and V2.1 <a name="A.5"></a>
Expand Down
Loading