OSCAL reference documentation - empty Constraints

[iMichaela]

Describe the bug

In the OSCAL reference documentation, there are empty Constraints with statements reading:
> Constraints that may apply to the data value of this element (in context):
which expand to nothing, leaving the statement incomplete.

Who is the bug affecting?

What is affected by this bug?

When does this occur?

How do we replicate the issue?

Go to any 'reference' page and use browser search to find the statements listed above.

If applicable, add screenshots to help explain your problem.}

Expected behavior (i.e. solution)

Other Comments

[david-waltermire]

@iMichaela I did an XPath search of the metaschemas using //(*:constraints|*:constraint)[not(*)][not(normalize-space())]. I found 3 instances, which might be causing this, but its hard to tell without more specifics.

Can you provide a few specific examples of where you are seeing this?

[iMichaela]

@david-waltermire-nist There are multiple instances of this error on each reference page for the XML formats (see bottom of the image below).

assessment results model: 16 instances (the first one is under addr-line - see above)
poa&m: 15 instances
assessment plan: 14
component definition model: 12
ssp: 19
profile model: 14
control model: 13

[wendellpiez]

@david-waltermire-nist is probably correct as to the upstream cause. However the data anomaly should be tolerated (and not produce the empty stub). Removing placeholders from the data then becomes an option.

Let's see to it this is corrected with usnistgov/metaschema-xslt#17.

[wendellpiez]

Provision to prevent the unwanted output for 'stub' content has been made in PR usnistgov/metaschema/#135.

[david-waltermire]

The reference documentation on the website has been completely revamped. This new documentation will be released with OSCAL 1.0.0. This issue was addressed by PR #948.