-
Notifications
You must be signed in to change notification settings - Fork 183
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
Updated FedRAMP Baselines #546
Conversation
docs/content/contribute/devlunch.md
Outdated
@@ -3,9 +3,17 @@ title: Lunch with the Devs | |||
description: Contact Us | |||
--- | |||
|
|||
{{% usa-intro %}}To increase communication with the OSCAL community, the NIST OSCAL team is hosting a one-hour teleconference every two weeks starting on Thursday, December 5th 2019 @ noon EST.{{% /usa-intro %}} | |||
{{% usa-intro %}}To increase communication with the OSCAL community, the NIST OSCAL team is hosting a one-hour teleconference every two weeks starting on Thursday, December 5th 2019 @ noon EST.{{% /usa-intro %}}Global |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change probably doesn't belong in this PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed. We need to do a better job of keeping PRs more focused on a single set of related changes.
@brianrufgsa Can you rebase this against master? To do this you can run the command:
|
<define-flag as-type="NCName" name="position"> | ||
<formal-name>Position</formal-name> | ||
<description>Where to add the new content with respect to the targeted element (beside it or inside it)</description> | ||
<allowed-values><!-- TODO: define these --> | ||
<enum value="before"/> | ||
<enum value="after"/> | ||
<enum value="starting"/> | ||
<enum value="ending"/> | ||
</allowed-values> | ||
</define-flag> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@brianrufgsa Can you explain this change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@david-waltermire-nist I did all that, and when I prepared the pull request it only showed my eight files. I am not sure what is happening. It was only supposed to be the four FedRAMP baselines and resolved profiles.
<xsl:apply-templates mode="#current" select="*[@key=('title')]"/> | ||
<xsl:apply-templates mode="#current" select="*[@key=('param', 'parameters')]"/> | ||
<xsl:apply-templates mode="#current" select="*[@key=('prop', 'properties')]"/> | ||
<xsl:apply-templates mode="#current" select="*[@key=('annotation', 'annotations')]"/> | ||
<xsl:apply-templates mode="#current" select="*[@key=('link', 'links')]"/> | ||
<xsl:apply-templates mode="#current" select="*[@key=('part', 'parts')]"/> | ||
<xsl:apply-templates mode="#current" select="*[@key=('control', 'controls')]"/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@brianrufgsa You shouldn't commit any changes against files in the xml, json, or content directories, since these files are generated by the CI/CD. Can you revert these files?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR makes changes to the /content, /xml, and /json directories which are maintained by the CI/CD. These file changes need to be reverted. The PR should also be rebased against master.
Committer Notes
Updated FedRAMP baselines as OSCAL profiles and resolved profiles.
These use the revised profile schema with the new alter/add/@id-ref syntax
All Submissions:
Changes to Core Features: