Skip to content

Commit

Permalink
Pushing generated website pages [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
@actions-user
david-waltermire-nist authored and actions-user committed May 9, 2022
1 parent 131415e commit 0ffca66
Show file tree
Hide file tree
Showing 38 changed files with 1,600 additions and 688 deletions.
58 changes: 35 additions & 23 deletions docs/content/reference/latest/assessment-plan/json-definitions.md
View file

Large diffs are not rendered by default.

20 changes: 10 additions & 10 deletions docs/content/reference/latest/assessment-plan/json-reference.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -763,7 +763,7 @@ The following is the JSON format reference for this [model](/concepts/layer/asse
<p>The value <b>may be locally defined</b>, or the following:</p>
<ul>

<li><strong>https://www.doi.org/</strong>: A Digital Object Identifier (DOI); use is preferred, since this allows for retrieval
<li><strong>http://www.doi.org/</strong>: A Digital Object Identifier (DOI); use is preferred, since this allows for retrieval
of a full bibliographic record.</li>
</ul>
</div>
Expand Down Expand Up @@ -1617,7 +1617,7 @@ The following is the JSON format reference for this [model](/concepts/layer/asse
<details class="constraints" open="open">
<summary>Constraint (1)</summary>
<div class="constraint">
<p><span class="usa-tag">matches</span>: a target (value) must match the regular expression '[A-Z](2)'.</p>
<p><span class="usa-tag">matches</span>: a target (value) must match the regular expression '[A-Z]{2}'.</p>
</div>
</details>
</div>
Expand Down Expand Up @@ -2154,7 +2154,7 @@ The following is the JSON format reference for this [model](/concepts/layer/asse
<p>The value <b>may be locally defined</b>, or the following:</p>
<ul>

<li><strong>https://orcid.org/</strong>: The identifier is Open Researcher and Contributor ID (ORCID).</li>
<li><strong>http://orcid.org/</strong>: The identifier is Open Researcher and Contributor ID (ORCID).</li>
</ul>
</div>
</details>
Expand Down Expand Up @@ -2646,7 +2646,7 @@ The following is the JSON format reference for this [model](/concepts/layer/asse
<details class="constraints" open="open">
<summary>Constraint (1)</summary>
<div class="constraint">
<p><span class="usa-tag">matches</span>: a target (value) must match the regular expression '[A-Z](2)'.</p>
<p><span class="usa-tag">matches</span>: a target (value) must match the regular expression '[A-Z]{2}'.</p>
</div>
</details>
</div>
Expand Down Expand Up @@ -6778,7 +6778,7 @@ The following is the JSON format reference for this [model](/concepts/layer/asse

<li><strong>objective</strong>: **(deprecated)** Use 'assessment-objective' instead.</li>

<li><strong>assessment</strong>: **(deprecated)** Use 'assessment-method' instead</li>
<li><strong>assessment</strong>: **(deprecated)** Use 'assessment-method' instead.</li>

<li><strong>assessment-objective</strong>: The part defines an assessment objective.</li>

Expand Down Expand Up @@ -7149,7 +7149,7 @@ The following is the JSON format reference for this [model](/concepts/layer/asse
<code>ns</code> is provided, the name is expected to be in the "OSCAL" namespace.</p>
<p>To ensure a <code>ns</code> is unique to an organization and naming conflicts are avoided, a URI containing a
DNS or other globally defined organization name should be used. For example, if FedRAMP
and DoD both extend OSCAL, FedRAMP will use the <code>ns</code> "https://fedramp.gov", while DoD will use the <code>ns</code> "https://defense.gov" for any organization specific <code>name</code>. </p>
and DoD both extend OSCAL, FedRAMP will use the <code>ns</code> <code>http://fedramp.gov/ns/oscal</code>, while DoD might use the <code>ns</code> <code>https://defense.gov</code> for any organization specific <code>name</code>.</p>
<p>Tools that process OSCAL content are not required to interpret unrecognized OSCAL
extensions; however, OSCAL compliant tools should not modify or remove unrecognized
extensions, unless there is a compelling reason to do so, such as data sensitivity.</p>
Expand Down Expand Up @@ -7460,7 +7460,7 @@ The following is the JSON format reference for this [model](/concepts/layer/asse
<code>ns</code> is provided, the name is expected to be in the "OSCAL" namespace.</p>
<p>To ensure a <code>ns</code> is unique to an organization and naming conflicts are avoided, a URI containing a
DNS or other globally defined organization name should be used. For example, if FedRAMP
and DoD both extend OSCAL, FedRAMP will use the <code>ns</code> "https://fedramp.gov", while DoD will use the <code>ns</code> "https://defense.gov" for any organization specific <code>name</code>. </p>
and DoD both extend OSCAL, FedRAMP will use the <code>ns</code> <code>http://fedramp.gov/ns/oscal</code>, while DoD might use the <code>ns</code> <code>https://defense.gov</code> for any organization specific <code>name</code>.</p>
<p>Tools that process OSCAL content are not required to interpret unrecognized OSCAL
extensions; however, OSCAL compliant tools should not modify or remove unrecognized
extensions, unless there is a compelling reason to do so, such as data sensitivity.</p>
Expand Down Expand Up @@ -11690,7 +11690,7 @@ The following is the JSON format reference for this [model](/concepts/layer/asse
<code>ns</code> is provided, the name is expected to be in the "OSCAL" namespace.</p>
<p>To ensure a <code>ns</code> is unique to an organization and naming conflicts are avoided, a URI containing a
DNS or other globally defined organization name should be used. For example, if FedRAMP
and DoD both extend OSCAL, FedRAMP will use the <code>ns</code> "https://fedramp.gov", while DoD will use the <code>ns</code> "https://defense.gov" for any organization specific <code>name</code>.</p>
and DoD both extend OSCAL, FedRAMP will use the <code>ns</code> <code>http://fedramp.gov/ns/oscal</code>, while DoD might use the <code>ns</code> <code>https://defense.gov</code> for any organization specific <code>name</code>.</p>
<p>Tools that process OSCAL content are not required to interpret unrecognized OSCAL
extensions; however, OSCAL compliant tools should not modify or remove unrecognized
extensions, unless there is a compelling reason to do so, such as data sensitivity.</p>
Expand Down Expand Up @@ -12028,7 +12028,7 @@ The following is the JSON format reference for this [model](/concepts/layer/asse
<code>ns</code> is provided, the name is expected to be in the "OSCAL" namespace.</p>
<p>To ensure a <code>ns</code> is unique to an organization and naming conflicts are avoided, a URI containing a
DNS or other globally defined organization name should be used. For example, if FedRAMP
and DoD both extend OSCAL, FedRAMP will use the <code>ns</code> "https://fedramp.gov", while DoD will use the <code>ns</code> "https://defense.gov" for any organization specific <code>name</code>.</p>
and DoD both extend OSCAL, FedRAMP will use the <code>ns</code> <code>http://fedramp.gov/ns/oscal</code>, while DoD might use the <code>ns</code> <code>https://defense.gov</code> for any organization specific <code>name</code>.</p>
<p>Tools that process OSCAL content are not required to interpret unrecognized OSCAL
extensions; however, OSCAL compliant tools should not modify or remove unrecognized
extensions, unless there is a compelling reason to do so, such as data sensitivity.</p>
Expand Down Expand Up @@ -21185,7 +21185,7 @@ The following is the JSON format reference for this [model](/concepts/layer/asse
<p>The value <b>may be locally defined</b>, or the following:</p>
<ul>

<li><strong>https://www.doi.org/</strong>: A Digital Object Identifier (DOI); use is preferred, since this allows for retrieval
<li><strong>http://www.doi.org/</strong>: A Digital Object Identifier (DOI); use is preferred, since this allows for retrieval
of a full bibliographic record.</li>
</ul>
</div>
Expand Down
Loading

0 comments on commit 0ffca66

Please sign in to comment.