Correcting the port-range constraints to properly implement the intent for the defined constraints.

Committer Notes

Current port-range constraints are generating warnings that port-range start or end must be defined even when they are.

All Submissions:

• Have you selected the correct base branch per Contributing guidance?
• Have you set "Allow edits and access to secrets by maintainers"?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you squashed any non-relevant commits and commit messages? [instructions]
• Do all automated CI/CD checks pass?

By submitting a pull request, you are agreeing to provide this contribution under the CC0 1.0 Universal public domain dedication.

(For reviewers: The wiki has guidance on code review and overall issue review for completeness.)

Changes to Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
  The following schematron file can be used. If deemed necessary, it can be uploaded to the repo. Example sip file can also be uploaded to oscal-content repo.

<?xml version="1.0" encoding="UTF-8"?>
<sch:schema xmlns:sch="http://purl.oclc.org/dsdl/schematron" queryBinding="xslt2"
  xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
  xmlns:sqf="http://www.schematron-quickfix.com/validator/process"> 
  <sch:ns prefix="o" uri="http://csrc.nist.gov/ns/oscal/1.0"/>
     
  <sch:pattern id="proposed">      
     <!-- Schema constrains to non-negative integer so we do not do that here. -->
     <sch:rule context="o:port-range">
        <sch:assert test="exists(@start)" id="start-port-does-not-exist">id port-range-has-start</sch:assert>
        <sch:assert test="exists(@end)" id="end-port-does-not-exist">id port-range-has-end</sch:assert>
        <sch:assert test="not(@start > @end)" id="start-is-before-end">id port-range-end-date-is-before-start-date</sch:assert>
     </sch:rule>         
  </sch:pattern>
 
</sch:schema>

• Have you included examples of how to use your new feature(s)?
• Have you updated all OSCAL website and readme documentation affected by the changes you made? Changes to the OSCAL website can be made in the docs/content directory of your branch.