From b6f1973f15d28896e09cf7b9e47cd80dd89e4898 Mon Sep 17 00:00:00 2001 From: Wendell Piez Date: Mon, 25 Jul 2022 11:52:00 -0400 Subject: [PATCH] Profile Resolution Spec clarification: validation of imported catalogs and profiles (#1380) Addresses #1312 --- .../profile-resolution/profile-resolution-specml.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/specifications/profile-resolution/profile-resolution-specml.xml b/src/specifications/profile-resolution/profile-resolution-specml.xml index 5fcffde022..cc97b90112 100644 --- a/src/specifications/profile-resolution/profile-resolution-specml.xml +++ b/src/specifications/profile-resolution/profile-resolution-specml.xml @@ -303,7 +303,7 @@ profile: -

If the object fetched cannot be found or is not a valid OSCAL object, the tool MUST cease processing and provide an error.

+

If the object fetched cannot be found, or does not parse as an OSCAL catalog or profile, the tool MUST cease processing and provide an error.

-

Under this directive, colliding controls will result in invalid results, as they will both appear in the results with the same ID. Accordingly, this setting may be useful in ensuring integrity of references to controls as given in the profile: if any included control is called only once, clashing controls will not be produced and validation will succeed.

+

Under this directive, colliding controls will result in invalid results, as they will both appear in the results with the same ID. Accordingly, this setting may be useful in ensuring integrity of references to controls as given in the profile: if any included control is called only once, clashing controls will not be produced, disambiguating the result and avoiding validation errors.