-
-
Couldn't load subscription status.
- Fork 74
Add support for representing patent information #597
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
Conversation
Signed-off-by: Steve Springett <[email protected]>
Signed-off-by: steve.springett <[email protected]>
|
@planetlevel would you be able to review this? We have worked with WIPO on providing summary information for patents and patent families and we believe our current support for both of these are correct. Let us know otherwise. However, I'm particularly interested in a review of the patent assertions which allow BOM creators to assert their relationship with the patent (owner, licensing, etc). |
|
Hi Steve,
I spent some time with this, and it looks pretty comprehensive. For all my
experience with patents (IP degree from G'town, drafted several patents for
big companies at a lawfirm, have 7-8 of my own)... I guess my patent
experience has been pretty simple relative to these complex scenarios.
Sorry I thought I could be more help here,
…--Jeff
410-707-1487
On Mon, Mar 10, 2025 at 2:17 PM Steve Springett ***@***.***> wrote:
@planetlevel <https://github.com/planetlevel> would you be able to review
this? We have worked with WIPO on providing summary information for patents
and patent families and we believe our current support for both of these
are correct. Let us know otherwise. However, I'm particularly interested in
a review of the patent assertions which allow BOM creators to assert their
relationship with the patent (owner, licensing, etc).
—
Reply to this email directly, view it on GitHub
<#597 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAUUFTHRYGRI6F6OVTPFO3D2TXQNZAVCNFSM6AAAAABW3U24E6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJRGQ2DMMJQHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
[image: stevespringett]*stevespringett* left a comment
(CycloneDX/specification#597)
<#597 (comment)>
@planetlevel <https://github.com/planetlevel> would you be able to review
this? We have worked with WIPO on providing summary information for patents
and patent families and we believe our current support for both of these
are correct. Let us know otherwise. However, I'm particularly interested in
a review of the patent assertions which allow BOM creators to assert their
relationship with the patent (owner, licensing, etc).
—
Reply to this email directly, view it on GitHub
<#597 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAUUFTHRYGRI6F6OVTPFO3D2TXQNZAVCNFSM6AAAAABW3U24E6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJRGQ2DMMJQHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
…est case Signed-off-by: Steve Springett <[email protected]>
Signed-off-by: Steve Springett <[email protected]>
|
@jkowalleck do you know what's up with the Java checker? It's failing on the valid-standard-1.7 test file, which is not part of this PR, and was never failing previously to my knowledge. Also, the PHP one is not returning any useful information, just a generic error. |
did not look into details of this PR, but is suspect the XSD changes are breaking things unintentionally. |
Signed-off-by: Steve Springett <[email protected]>
|
Ah, that makes sense. Thanks for the guidance. |
Signed-off-by: Steve Springett <[email protected]>
Signed-off-by: Steve Springett <[email protected]>
Signed-off-by: Jan Kowalleck <[email protected]>
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.
did a complete review of all changes.
- the JSON, the XML, and the PB are consistent.
- data models made sense - thanks to the good documentation/annotation
|
RFC notice sent on May 3, 2025
Public RFC period ended May 31, 2025 |
|
this one just was accepted during a Ecma TC54 meeting 👍 |
|
Great news 🚀 , and great result. Thank you ❤️ to all the people involved. |
## Fixed * XML schema: add type for `ComponentData` sub-elements ([#600] via [#601]) * JSON schema: added the correct `deprecated` mark for already deprecated structures (via [a973a6b]) ## Deprecated * Deprecated various fields and structures related to _cryptographic transparency_ - _CBOM_ . (via [#657]) Use the newly added structures and fields for detailing the information instead. ## Changed * Extended the scope of _formulations_. (via [#647]) From now on, _formulations_ may be used to describe how any referencable object within the BOM came together, including components, services, metadata, declarations, or the BOM itself. Before, it was restricted to components and services. ## Added * Support for _external components_ with _version-ranges_ ([#321] via [#586]) * Support for _multiple_ SPDX License Expressions alongside with other licenses ([#454] via [#582]) * Support for _Streebog hashing algorithm_ ([#485] via [#525]) * Support for license expression _details and properties_ ([#549], [#554] via [#599]) * Support for expressing BOM distribution constraints with the _Traffic Light Protocol_ (TLP) in metadata ([#595] via [#604], [#653]) * Support for representing _patent information_ ([#596] via [#597]) * Support for _properties_ on external-references ([#608] via [#610]) * Support for _citations_ ([#630] via [#629]) * Support for detailing _cryptographic transparency_ information - _CBOM_ ([#569] via [#657]) ## Documentation * Elaborated component classification "platform", explicitly expressed that it includes just-in-time compilers and interpreters ([#233] via [#647]) * Removed the term "optional" from the schema where the definition was already unambiguous ([#616], [#649] via [#680]) ## Test data * Add test data for CycloneDX 1.7 implementations in XML, JSON, Protobuf [#233]: #233 [#321]: #321 [#454]: #454 [#485]: #485 [#525]: #525 [#549]: #549 [#554]: #554 [#569]: #569 [#582]: #582 [#586]: #586 [#595]: #595 [#596]: #596 [#597]: #597 [#599]: #599 [#600]: #600 [#601]: #601 [#604]: #604 [#608]: #608 [#610]: #610 [#616]: #616 [#629]: #629 [#630]: #630 [#647]: #647 [#649]: #649 [#653]: #653 [#657]: #657 [#680]: #680 [a973a6b]: a973a6b ---- - fixes #233 - fixes #321 - fixes #454 - fixes #485 - fixes #549 - fixes #554 - fixes #595 - fixes #596 - fixes #600 - fixes #608 - fixes #629 - fixes #616 - fixes #649
Implements patent support. Closes #596
TODO/DONE