From 4384d44ed91788f62d52427a8d3ac5cf615ffccf Mon Sep 17 00:00:00 2001 From: Julien Perrochet Date: Thu, 12 Sep 2024 12:59:03 +0200 Subject: [PATCH] comments --- .../astm/utm/dss/fragments/sub/implicit_correct.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/implicit_correct.md b/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/implicit_correct.md index e470e33218..6c322888df 100644 --- a/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/implicit_correct.md +++ b/monitoring/uss_qualifier/scenarios/astm/utm/dss/fragments/sub/implicit_correct.md @@ -4,7 +4,5 @@ This test step fragment validates the time-bounds of an implicit subscription ## 🛑 Implicit subscription has correct temporal parameters check -If the implicit subscription time boundaries do not match the OIR's, either one, or both, of the following are possible: - -The DSS is in violation of **[astm.f3548.v21.DSS0005,1](../../../../../../requirements/astm/f3548/v21.md)**, as the implicit subscription does not cover the OIR's time boundaries; -Entities that should have been cleaned up earlier are still present in the DSS, and this scenario cannot proceed. +If the implicit subscription time boundaries do not cover the OIR's, +the DSS is in violation of **[astm.f3548.v21.DSS0005,1](../../../../../../requirements/astm/f3548/v21.md)**.