forked from usnistgov/OSCAL
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Requirement Tagging - Profile Resolution Specification (usnistgov#1089)
* Tagged Requirements (updated .rnc), Added Draft Status, several small fixes in modify section * Applying AJ's fixes, other various small fixes - pending larger automated formating * Intro purpose rewrite. Editorial fixes from comments. Small edits to "Processing" page on site. Co-authored-by: Alexander Stein <alexander.stein@nist.gov> Co-authored-by: Stephen Banghart <stephen.banghart@outlook.com>
- Loading branch information
Showing
4 changed files
with
292 additions
and
338 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,10 +1,18 @@ | ||
--- | ||
title: Processing Specification | ||
title: Processing Specifications | ||
weight: 50 | ||
description: Standardized processes to be applied to OSCAL data | ||
aliases: | ||
- /documentation/specification/ | ||
- /documentation/processing/ | ||
suppresstopiclist: true | ||
--- | ||
|
||
OSCAL data is intended to be processed in many ways for many different purposes. The specifications here describe normative processes, in the sense that all OSCAL processors that perform these operations should produce the same outputs from the same inputs under the same configuration. However, users and developers should find many ways to take advantage of data encoded in OSCAL, even beyond what is considered here. | ||
|
||
**Please note that these specifications are currently a work in progress and are subject to change.** If you have any feedback or comments, please create an issue at the [NIST OSCAL Github Repository](https://github.com/usnistgov/OSCAL) | ||
|
||
|
||
# Profile Resolution Specification | ||
|
||
The [Profile Resolution Specification](profile-resolution/) provides the standardized process for transforming an OSCAL Profile into an OSCAL Catalog. This specification is current a work in progress and is subject to change. |
Oops, something went wrong.