search

usnistgov / oscal-tools

Tools for the OSCAL project
https://pages.nist.gov/oscal-tools/
34 stars 17 forks source link

Describe associated documents #30

Open danielnaab opened 2 years ago

danielnaab commented 2 years ago

Given an OSCAL document, I would like to understand the extent of all referenced external documents, so I may create tooling to abstract filesystem and network I/O on top of SaxonJS.

This could take different forms, but one may be XSLT that produces a representation of a filesystem.

wendellpiez commented 2 years ago

@danielnaab IIRC we have in mind some kind of 'tracer' that could traverse an import tree or other set of relations between files, correct? This is interesting. There are also complementary kinds of 'survey' tools I can envision. For example, given any set of OSCAL files (perhaps detected dynamically in a file system), draw a map showing where they reference one another, or call outside the set. That too could take the form of a representation of a filesystem, with your single-document networks always a subset of the larger net of nets. Thoughts?

danielnaab commented 2 years ago

@wendellpiez fyi, if I recall, this issue was driven by the goal outlined here: https://github.com/18F/fedramp-automation/blob/develop/src/validations/docs/adr/0009-multi-document-rules.md We might revisit the need to create a manifest as the ASAP projects gets going again, but your description of a tracer's output sounds consistent with what we'd need to provide input to SaxonJS. cc @MarkXLIX @garygapinski