Skip to content
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 support for network and data flow diagrams #273

Merged
merged 1 commit into from
Feb 24, 2022

Conversation

kylelaker
Copy link
Contributor

This mimics the existing behavior for Authorization Boundaries

Closes: #222
Closes: #223

This mimics the existing behavior for Authorization Boundaries

Closes: #222
Closes: #223
@kylelaker
Copy link
Contributor Author

image

@kylelaker
Copy link
Contributor Author

Because of some formatting changes, the diff for this may be slightly better if the "ignore whitespace" option is applied.

kylelaker added a commit that referenced this pull request Feb 24, 2022
While working on the implementation for #273 it was unclear to me
whether the specification permits diagrams to be referenced directly by
URI or not so I split this out into its own pull request.

The specification specifically states:

> The value of the href can be an internet resource, or a local reference
> using a fragment e.g. #fragment that points to a back-matter resource in
> the same document.
>
> If a local reference using a fragment is used, this will be indicated by
> a fragment "#" followed by an identifier which references an identified
> resource in the document's back-matter or another object that is within
> the scope of the containing OSCAL document.
>
> If an internet resource is used, the href value will be an absolute or
> relative URI pointing to the location of the referenced resource. A
> relative URI will be resolved relative to the location of the document
> containing the link.

This, to me, implied that we should be permitting absolute and relative
links via a URI to internet resources.

To implement this, a "wrapper"-ish function has been created for what
used to be a pure Back Matter lookup function. It handles the logic to
determine whether the link is internal (needs to be looked up in Back
Matter) or an internet resource (is a URI).

There are some incidental changes to code and tests due to the changing
of imports and addition of exported `test-data`.
@zclarkEDC zclarkEDC merged commit 8926cb7 into develop Feb 24, 2022
@kylelaker kylelaker deleted the feature/add-network-data-diagrams branch February 24, 2022 17:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Display SSP Network Architecture Display SSP Data Flow
3 participants