-
Notifications
You must be signed in to change notification settings - Fork 140
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
Add OMG History chapter #1053
Merged
Merged
Add OMG History chapter #1053
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Arthit Suriyawongkul <[email protected]>
kestewart
reviewed
Aug 11, 2024
Signed-off-by: Arthit Suriyawongkul <[email protected]>
@bobmartin3000 This one is replacing #1008 |
Using https://spdx.github.io/spdx-spec/v3.0.1/rdf/schema.json Signed-off-by: Arthit Suriyawongkul <[email protected]>
We can drop the last couple lines from this - the ones with the urls. Meant to mention that today.
Bob
Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: Arthit Suriyawongkul ***@***.***>
Sent: Sunday, August 11, 2024 7:38:56 PM
To: spdx/spdx-spec ***@***.***>
Cc: Robert A Martin ***@***.***>; Mention ***@***.***>
Subject: [EXT] Re: [spdx/spdx-spec] Add OMG History chapter (PR #1053)
@bact commented on this pull request. In docs/omg-history. md: > +candidate 2 of SPDX 3. 0 in February of 2024. This release candidate will give +tool creators and those who maintain the support libraries for working with +SPDX time to start
@bact commented on this pull request.
________________________________
In docs/omg-history.md<#1053 (comment)>:
+candidate 2 of SPDX 3.0 in February of 2024. This release candidate will give
+tool creators and those who maintain the support libraries for working with
+SPDX time to start revising their projects in advance of the final version of
+the specification. For those not following the inner workings, debates, and
+discussion of the combined 3T-SBOM and SPDX 3.0 working group for the last 3
+years there will be a dramatic change in the SPDX model as it goes from SPDX
+2.3 to SPDX 3.0, as shown by looking at Figure 16’s left-side (SPDX 2.3 model)
+compared to its right-side (SPDX 3.0), shifting the SPDX name from Software
+Package Data Exchange to System Package Data Exchange and the scope of items it
+can convey in a bill of materials.
+
+![Figure 16 – SPDX 2.3 Model compared to the SPDX 3.0 Model](images/spdx23-spdx30-comparison.png "Figure 16 – SPDX 2.3 Model compared to the SPDX 3.0 Model")
+**Figure 16 – SPDX 2.3 Model compared to the SPDX 3.0 Model**
+
+The SPDX 3.0.1 model is available at:
+[https://github.com/spdx/spdx-3-model](https://github.com/spdx/spdx-3-model)
@goneall<https://github.com/goneall> for v3.0 it is at https://spdx.github.io/spdx-spec/v3.0/model/schema.json
But the new spec-parser will publish v3.0.1 one at https://spdx.github.io/spdx-spec/v3.0.1/rdf/schema.json
See @zvr<https://github.com/zvr> comment here: #1046 (comment)<#1046 (comment)>
—
Reply to this email directly, view it on GitHub<#1053 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AUYBD7BIASN3UPR5PIOXCMLZQ7YZBAVCNFSM6AAAAABMLCUUDKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDEMZRHEYTEOJRGQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Remove links to SPDX resources Signed-off-by: Arthit Suriyawongkul <[email protected]>
As @bobmartin3000 suggested, I removed that last three lines with URLs. The schema and ontology URLs will be included in the Serialization chapter by the JSON-LD context PR #1059 |
kestewart
approved these changes
Aug 12, 2024
goneall
approved these changes
Aug 12, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(Replacing #1008 - with approvals there)
This PR will only add the content but not include it to the navigation bar. That will be handle by PR #1055