wendellpiez
commented
2 years ago This Issue should be refactored and split out, or just closed. For example, authoring CSS would be part of an OSCAL framework for an XML IDE such as oXygen. That or other use cases could motivate Issues; without a specific use case this Issue is difficult to address (and such CSS as it describes does exist, in different forms).
User Story:
As an OSCAL user or developer, I wish to hand-edit a profile, only to discover the delivered OSCAL CSS doesn't fully support it. Also, the CSS that is there, could probably be improved somewhat, with respect both to browser display of OSCAL data (XML+CSS), or editing in CSS-capable XML authoring tools.
Goals:
Better CSS for better / cleaner presentation of and interaction with OSCAL data in browsers and tools that support CSS. It will be "better" both from an aesthetic/usability point of view, and perhaps in its organization of resources and libraries. Ideally, there will be documentation and guidance on how to use it.
Dependencies:
Acceptance Criteria
CSS is easy to find and use with OSCAL XML, and its functional coverage can be considered adequate to an estimated 80% of use cases for it (or more). In particular, profiles calling SP800-53 catalog data are supported. (Note: the CSS will be applied to the profile itself, not to the result of executing or resolving the profile.)