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.

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

Fix Software Example 14 title (typo as "Example 1") #107

Merged
merged 1 commit into from
Jan 10, 2025
Merged
Changes from all commits
Commits
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
9 changes: 4 additions & 5 deletions software/example14/README.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Example 1
# Example 14

## Description

Expand All @@ -7,16 +7,16 @@ An [existing (original) SPDX document](content/examplemaven-0.0.1.spdx.json) is
## Comments

In addition to any modifications made to the original SPDX document, the following changes are made to the resultant enriched SPDX document:

- Create a new `documentNamespace` - this is required since the enriched document does not contain exactly the same SPDX metadata
- Update the `created` timestamp to the time this document was generated
- Add a tool to the creators for the enrichment tool
- Create an `AMENDS` relationship from the enriched document to the original document
- Add an `externalDocumentRef` for the original document - this is necessary to create the relationship and provides a checksum for verifying the integrity of the original document


Below is a diff for the above-mentioned changes:

```
```diff
6c6
< "documentNamespace": "http://spdx.org/documents/examplemaven-0.0.1",
---
Expand Down Expand Up @@ -46,5 +46,4 @@ Below is a diff for the above-mentioned changes:
> "relationshipType": "AMENDS",
> "comment": "The original document and been enriched by the Parlay application"
> },

```
```
Loading