-
-
Notifications
You must be signed in to change notification settings - Fork 68
[WIP] v1.7 #511
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
Draft
jkowalleck
wants to merge
125
commits into
master
Choose a base branch
from
1.7-dev
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
[WIP] v1.7 #511
Conversation
This file contains hidden or 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: Jan Kowalleck <[email protected]>
Signed-off-by: Jan Kowalleck <[email protected]>
) Signed-off-by: Dmitry Volk <[email protected]>
Signed-off-by: Dmitry Volk <[email protected]>
…but a name. Signed-off-by: Dmitry Volk <[email protected]>
Signed-off-by: Jan Kowalleck <[email protected]>
Signed-off-by: Jan Kowalleck <[email protected]>
Signed-off-by: Jan Kowalleck <[email protected]>
Signed-off-by: Jan Kowalleck <[email protected]>
Signed-off-by: Jan Kowalleck <[email protected]>
Signed-off-by: Jan Kowalleck <[email protected]>
Signed-off-by: Jan Kowalleck <[email protected]>
1. enabled test runner for schema 1.7 1. copied all test cases from 1.6 to 1.7 1. renamed the files from `*.1.6.*` to `*.1.7.*` 1. migrated the test cases from schema 1.6 to schema 1.7 see the diff/delta of each individual commit for details java tests are expected to fail, as long as #256 is not done
Signed-off-by: Jan Kowalleck <[email protected]>
We often only need the latest docs, while developing a new version. Therefore, the latest version's docs are generated first.
Signed-off-by: Jan Kowalleck <[email protected]>
Signed-off-by: Jan Kowalleck <[email protected]>
Signed-off-by: Jan Kowalleck <[email protected]>
Signed-off-by: Jan Kowalleck <[email protected]>
Signed-off-by: Jan Kowalleck <[email protected]>
Signed-off-by: Jan Kowalleck <[email protected]>
…on (fixes #595) Signed-off-by: anthonyharrison <[email protected]>
# Conflicts: # schema/bom-1.7.proto # schema/bom-1.7.schema.json # schema/bom-1.7.xsd
…on (fixes #595) Signed-off-by: anthonyharrison <[email protected]>
With this property external references can be annotated with additional metadata in a machine-readable format. Signed-off-by: Christoph Steiger <[email protected]>
As discussed in ticket #321, this PR adds the following abilities: - mark components as **external** > Determine whether this component is external. > An external component is one that is not part of an assembly, but is expected to be provided by the environment, regardless of the component's `@scope`. This setting can be useful for distinguishing which components are bundled with the product and which can be relied upon to be present in the deployment environment. > This may be set to `true` for runtime components only. For `/metadata/component`, it must be set to `false`. - external components may have **version-ranges** instead of a specific version > For an external component, this specifies the accepted version range. > The value must adhere to the Package URL Version Range syntax (vers), as defined at <https://github.com/package-url/purl-spec/blob/master/VERSION-RANGE-SPEC.rst>. > May only be used if `.isExternal` is set to `true`. > Must be used exclusively, either 'version' or 'versionRange', but not both. fixes #321 ---- > [!NOTE] > this one supersedes #326 <-- read there for more background and previous discussions implementing with `components`, because the objects referenced/required are actually used at runtime and therefore are considered a "component". Sketch/proposal for #321 - [x] sketch JSON schema - properties and assert - test cases - [x] sketch XML schema - elements & attributes. no asserts - this would require XSD1.1 which is not broadly implemented, yet. - test cases - [x] sketch ProtoBuff schema - fields - test cases ---- > [!NOTE] > ALL FEEDBACK IS WELCOME! Yes, everything. > but some might not be resolved in this very PR, but in the authoritative guides. See #586 (comment)
…est case Signed-off-by: Steve Springett <[email protected]>
Signed-off-by: Steve Springett <[email protected]>
Signed-off-by: Steve Springett <[email protected]>
Signed-off-by: Steve Springett <[email protected]>
Signed-off-by: Steve Springett <[email protected]>
Signed-off-by: Jan Kowalleck <[email protected]>
…censing, etc (#599) As discussed via #549, this PR adds new structures to allow documenting the licensing and "properties" of SPDX expressions As discussed via #554, this PR adds new structures to allow documenting the license texts for SPDX expressions' individual parts. ---- TODO - [x] agree on data models & finalize examples - [x] write the schemata - [x] write the spec - [x] write a proper summary for this PR ---- - fixes #554 - fixes #549
Implements patent support. Closes #596
Signed-off-by: Jan Kowalleck <[email protected]>
Signed-off-by: Jan Kowalleck <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
Note
WORK IN PROGRESS
see progress: https://github.com/CycloneDX/specification/milestone/8
Fixed
ComponentData
sub-elements (#600 via #601)Deprecated
Changed
Added
Support for external components with version-ranges (#321 via #586)
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)
Support for representing patent information (#596 via #597)
Support for properties on external-references (#608 via #610)
... TBC ...
Documentation
Test data
ComponentType
"runtime" #233