|
Serialization: Ontologies vs Datatypes
Gary, Based on the W3C wiki description, that is consistent. 1) Blank nodes must not have an IRI, like Coordinate and CreationInformation instances 2) Blank nodes may apply to more than one IRI (RDF g
Gary, Based on the W3C wiki description, that is consistent. 1) Blank nodes must not have an IRI, like Coordinate and CreationInformation instances 2) Blank nodes may apply to more than one IRI (RDF g
|
By
David Kemp
· #5047
·
|
|
Serialization: Ontologies vs Datatypes
Thanks David for the additional info. I was planning allowing the fields of “data types” as objects in RDF triples in SPDX 3.0. The difference between Elements and “data types” was whether URI types w
Thanks David for the additional info. I was planning allowing the fields of “data types” as objects in RDF triples in SPDX 3.0. The difference between Elements and “data types” was whether URI types w
|
By
Gary O'Neall
· #5046
·
|
|
Serialization: Ontologies vs Datatypes
At the SPDX Serialisation Meeting 2023-03-16: Sean presented a deck of slides that he and Alexios had created to explain concepts relating to JSON-LD and RDF with regard to SPDX. The presentation cove
At the SPDX Serialisation Meeting 2023-03-16: Sean presented a deck of slides that he and Alexios had created to explain concepts relating to JSON-LD and RDF with regard to SPDX. The presentation cove
|
By
David Kemp
· #5045
·
|
|
#spdx Gsoc contribution guidance and suggestion
#spdx
I want to contribute in https://github.com/opensbom-generator/parsers project. I would love to have some suggestions and things I need to mention in my proposal. This project seems very interesting to
I want to contribute in https://github.com/opensbom-generator/parsers project. I would love to have some suggestions and things I need to mention in my proposal. This project seems very interesting to
|
By
Utkarsh Saxena
· #5044
·
Edited
|
|
Handling invalid licenses
Hi Anthony, My suggestion is to report the license as stated in the Declared License property, even though invalid, and use either NOASSERTION (or better yet) the correct license in the Concluded Lice
Hi Anthony, My suggestion is to report the license as stated in the Declared License property, even though invalid, and use either NOASSERTION (or better yet) the correct license in the Concluded Lice
|
By
Gary O'Neall
· #5043
·
|
|
Handling invalid licenses
Anthony: <anthony.p.harrison@...> wrote: Can you share some concrete examples?
Anthony: <anthony.p.harrison@...> wrote: Can you share some concrete examples?
|
By
Philippe Ombredanne
· #5042
·
|
|
Handling invalid licenses
I can only speak to what my understanding of SPDX 2.x is. However, before getting to that, I would ask exactly what you mean by "invalid licenses"? Are these files that have some license text that a t
I can only speak to what my understanding of SPDX 2.x is. However, before getting to that, I would ask exactly what you mean by "invalid licenses"? Are these files that have some license text that a t
|
By
Keith Zantow
· #5041
·
|
|
Handling invalid licenses
Team In generating SBOMs, I am encountering a lot of issues with licence information obtained from either ecosystem meta data or actual source files most do not appear to be using SPDX license identif
Team In generating SBOMs, I am encountering a lot of issues with licence information obtained from either ecosystem meta data or actual source files most do not appear to be using SPDX license identif
|
By
Anthony Harrison
· #5040
·
|
|
SPDX v2.3 JSON schema diagram
Norio, Thanks for your response. I refer you to the SPDX V2.3 spec for externalRef SECURITY https://spdx.github.io/spdx-spec/v2.3/package-information/#721-external-refe rence-field and https://spdx.gi
Norio, Thanks for your response. I refer you to the SPDX V2.3 spec for externalRef SECURITY https://spdx.github.io/spdx-spec/v2.3/package-information/#721-external-refe rence-field and https://spdx.gi
|
By
Dick Brooks
· #5039
·
|
|
SPDX v2.3 JSON schema diagram
Hello Dick, Thank you for pointing out. I added the figure of externalDocumentRefs. https://qiita.com/nori0428/items/b1892da6bd30ed6efff4#externaldocumentrefs And as far as I've checked the current sc
Hello Dick, Thank you for pointing out. I added the figure of externalDocumentRefs. https://qiita.com/nori0428/items/b1892da6bd30ed6efff4#externaldocumentrefs And as far as I've checked the current sc
|
By
Norio Kobota
· #5038
·
|
|
Released - Re: New Python tools pre-release
Hi all, we just released v0.7.1 of the tools-python! Best, Meret
Hi all, we just released v0.7.1 of the tools-python! Best, Meret
|
By
meret.behrens@...
· #5037
·
|
|
Event: SPDX tech team meeting - Tuesday, March 14, 2023
#cal-reminder
Reminder: SPDX tech team meeting When: Tuesday, March 14, 2023 11:00am to 12:30pm (UTC-05:00) America/Chicago Where: https://zoom.us/j/663426859 Organizer: Kate Stewart kstewart@... Vi
Reminder: SPDX tech team meeting When: Tuesday, March 14, 2023 11:00am to 12:30pm (UTC-05:00) America/Chicago Where: https://zoom.us/j/663426859 Organizer: Kate Stewart kstewart@... Vi
|
By
...
· #5036
·
|
|
FW: CISA SBOM update
FYI: Update an update today from Allan Friedman re: CISA SBOM activities – see email below. NOTE from Allan: As a reminder, CISA facilitates these open discussions, but the participants shape the agen
FYI: Update an update today from Allan Friedman re: CISA SBOM activities – see email below. NOTE from Allan: As a reminder, CISA facilitates these open discussions, but the participants shape the agen
|
By
Dick Brooks
· #5035
·
|
|
SPDX v2.3 JSON schema diagram
Norio, This is excellent work, thank you. I did not see the externalRefs SECURITY advisory object in the model, see Appendix K for examples; https://spdx.github.io/spdx-spec/v2.3/how-to-use/#k19-linki
Norio, This is excellent work, thank you. I did not see the externalRefs SECURITY advisory object in the model, see Appendix K for examples; https://spdx.github.io/spdx-spec/v2.3/how-to-use/#k19-linki
|
By
Dick Brooks
· #5034
·
|
|
SPDX v2.3 JSON schema diagram
Dear SPDX tech communities, Thank you for providing a lot of useful documents about SPDX! We, OpenChain Japan SBOM-sg members, illustrated the v2.3 JSON schema a little easier to see. https://qiita.co
Dear SPDX tech communities, Thank you for providing a lot of useful documents about SPDX! We, OpenChain Japan SBOM-sg members, illustrated the v2.3 JSON schema a little easier to see. https://qiita.co
|
By
Norio Kobota
· #5033
·
|
|
Serialization subteam: Toy Example
Serialization subteam members: Alexios contributed a toy example JSON file for Issue #89, which illustrates both the correspondence and the difference between any Set class defined in a logical model
Serialization subteam members: Alexios contributed a toy example JSON file for Issue #89, which illustrates both the correspondence and the difference between any Set class defined in a logical model
|
By
David Kemp
· #5032
·
|
|
OpenVEX lively discussion underway on GitHub OpenSSF
https://github.com/ossf/wg-vulnerability-disclosures/issues/125 This video leaves me questioning where Microsoft stands on OpenVEX. Art Manion’s, description of the CISA process is worth listening to:
https://github.com/ossf/wg-vulnerability-disclosures/issues/125 This video leaves me questioning where Microsoft stands on OpenVEX. Art Manion’s, description of the CISA process is worth listening to:
|
By
Dick Brooks
· #5031
·
|
|
FYI: Cross pollination with the CISA ICT_SCRM Task Force SW Assurance work stream
I think Alexios’ example table is a good approach.. I created a Google Sheets copy of his table below and added the CycloneDX related properties. Feel free to update the table. Here’s the link: https:
I think Alexios’ example table is a good approach.. I created a Google Sheets copy of his table below and added the CycloneDX related properties. Feel free to update the table. Here’s the link: https:
|
By
Gary O'Neall
· #5030
·
|
|
FYI: Cross pollination with the CISA ICT_SCRM Task Force SW Assurance work stream
We didn’t have time to go over this topic on the call, so no updates on the table below. I can provide some input, however, from the cdx2spdx tool which interprets the CycloneDX fields. CDX Supplier m
We didn’t have time to go over this topic on the call, so no updates on the table below. I can provide some input, however, from the cdx2spdx tool which interprets the CycloneDX fields. CDX Supplier m
|
By
Gary O'Neall
· #5029
·
|
|
Collaborating with SPDX in GSoC 2023!
Hi guys, I am Banula Kumarage. I am interested in contributing to the "SPDX License Submission Online Tool - increase functionality" through GSOC 2023. I have given a brief intro about myself in the g
Hi guys, I am Banula Kumarage. I am interested in contributing to the "SPDX License Submission Online Tool - increase functionality" through GSOC 2023. I have given a brief intro about myself in the g
|
By
Banula Kumarage
· #5028
·
|