-
Notifications
You must be signed in to change notification settings - Fork 181
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 imported-from
relation to links in SSP
#1023
Comments
The second case of |
This issue is derived from the following scenario (schematically represented below):
|
This adds the new `/link/@rel` value of `imported-from` in the following locations: - `/system-security-plan/system implementation/component/link` - `/system-security-plan/Control implementation/implemented requirements/link`
This adds the new `link/@rel` value of `imported-from` in the following locations in the `system-security-plan`: - `system-implementation/component/link` - `control-implementation/implemented-requirements/link`
This adds the new `link/@rel` value of `imported-from` in the following locations in the `system-security-plan`: - `system-implementation/component/link` - `control-implementation/implemented-requirements/link`
Talked with @david-waltermire-nist and team during weekly status meeting. We are going to break out the #756 dependency be implicit, not explicit, and removed from the deps section of the user story. I will update that issue accordingly to circle back and update the docs or code in the PR attached to that issue and circle back on this once merged. |
Co-authored-by: David Waltermire <[email protected]>
Co-authored-by: David Waltermire <[email protected]>
Co-authored-by: David Waltermire <[email protected]>
Co-authored-by: David Waltermire <[email protected]>
Co-authored-by: David Waltermire <[email protected]>
Co-authored-by: David Waltermire <[email protected]>
Co-authored-by: David Waltermire <[email protected]> Signed-off-by: Alexander Stein <[email protected]>
Co-authored-by: David Waltermire <[email protected]> Signed-off-by: Alexander Stein <[email protected]>
Co-authored-by: David Waltermire <[email protected]> Signed-off-by: Alexander Stein <[email protected]>
Co-authored-by: David Waltermire <[email protected]> Signed-off-by: Alexander Stein <[email protected]>
Co-authored-by: David Waltermire <[email protected]> Signed-off-by: Alexander Stein <[email protected]>
Co-authored-by: David Waltermire <[email protected]> Signed-off-by: Alexander Stein <[email protected]>
Co-authored-by: David Waltermire <[email protected]> Signed-off-by: Alexander Stein <[email protected]>
Co-authored-by: David Waltermire <[email protected]> Signed-off-by: Alexander Stein <[email protected]>
Co-authored-by: David Waltermire <[email protected]> Signed-off-by: Alexander Stein <[email protected]>
Co-authored-by: David Waltermire <[email protected]> Signed-off-by: Alexander Stein <[email protected]>
Co-authored-by: David Waltermire <[email protected]> Signed-off-by: Alexander Stein <[email protected]>
Co-authored-by: David Waltermire <[email protected]> Signed-off-by: Alexander Stein <[email protected]>
Co-authored-by: David Waltermire <[email protected]> Signed-off-by: Alexander Stein <[email protected]>
Co-authored-by: David Waltermire <[email protected]> Signed-off-by: Alexander Stein <[email protected]>
Co-authored-by: David Waltermire <[email protected]> Signed-off-by: Alexander Stein <[email protected]>
User Story:
To better document how components, capabilities, and controls all relate to one another. Additional pre-defined relation types would be useful. Although the Link assembly allows for arbitrary values some of the time, pre-defined acceptable values would provide users and tool developers better ability to make more universally compatible documents.
Adding additional values to the following Links would simplify importing and referencing source information for objects within the SSP
Goals:
Add
imported-from
as a accepted value in the ssp -> system implementation -> component -> link stanza. This relation is intended to represent the UUID and/or href back to the Component Definition that defined that component.Add
imported-from
as a accepted value in the ssp -> Control implementation -> implemented requirements -> by-component -> link stanza. This relation is intended to represent the UUID and/or href back to the Component Definition that defined that control narrative.Dependencies:
Enhancing 'link' to indicate internal targets in a 'resource' #756 is completed, as linking to thecomponent-definition/@uuid
and its originalcomponent/@uuid
within need to be addressed at the same time with two different fields or a complex syntax in the one field that is not very ergonomic,@link
at this time doesn't support that currently.Acceptance Criteria
{The items above are general acceptance criteria for all User Stories. Please describe anything else that must be completed for this issue to be considered resolved.}
The text was updated successfully, but these errors were encountered: