-
Notifications
You must be signed in to change notification settings - Fork 60
operations: draft for export control classification #1102
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
base: profile-operations
Are you sure you want to change the base?
operations: draft for export control classification #1102
Conversation
|
I marked this pull request again as draft since there is still a discussion happening in the Operations workgroup on how to best represent the data. |
| ## Metadata | ||
|
|
||
| - name: ExportControlClassificationAssessment | ||
| - SubclassOf: /Core/Element |
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.
| - SubclassOf: /Core/Element | |
| - SubclassOf: /Core/Action |
|
|
||
| ## Description | ||
|
|
||
| Weight to express relevance in de minimis consideration. |
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.
Operations meeting 25-09-26: A better description is needed to clarify use and context.
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.
Definition of the weight (e.g. specification, type,...) should be in the Assessment.
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.
needs to be consistent for all classifications in one assessmentResult.
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.
No blockers from my side.
model/Operations/Classes/ExportControlClassificationAssessment.md
Outdated
Show resolved
Hide resolved
|
rebase to current 'develop' state planned before merge |
46ada0f to
c721835
Compare
ed12e58 to
8094d37
Compare
Signed-off-by: Ummo Schwarting <uschwarting@deloitte.de>
Co-authored-by: stevenc-stb <steven@smarttalkbeacon.com> Signed-off-by: umm0 <uschwarting@deloitte.de>
Co-authored-by: stevenc-stb <steven@smarttalkbeacon.com> Signed-off-by: umm0 <uschwarting@deloitte.de>
Signed-off-by: Ummo Schwarting <uschwarting@deloitte.de>
c721835 to
dce63a2
Compare
Signed-off-by: Ummo Schwarting <uschwarting@deloitte.de>
Signed-off-by: Ummo Schwarting <uschwarting@deloitte.de>
Signed-off-by: Ummo Schwarting <uschwarting@deloitte.de>
Signed-off-by: Ummo Schwarting <uschwarting@deloitte.de>
…implementations Signed-off-by: Ummo Schwarting <uschwarting@deloitte.de>
|
I rebased the profile operations branch and the source for this pull request onto 'develop'. I suggest merging the pull request as it is now to have the profile-operations branch updated to the current discussion state. Your opinion? Edit:I added the suggestions from the discussion here to a separate branch so they are kept: https://github.com/umm0/spdx-3-model/pull/1/files Best, |
Signed-off-by: Ummo Schwarting <uschwarting@deloitte.de>
Draft pull request to discuss export control classification