From e1a7894b3b866c825a3e1697c47e6beae5cc0e52 Mon Sep 17 00:00:00 2001
From: Martin van der Plas <martinvanderplas@gmail.com>
Date: Tue, 26 Nov 2024 14:05:24 +0100
Subject: [PATCH] API Version-header en SemVer

verbetering van de how to test in relatie tot
https://github.com/Geonovum/KP-APIs/issues/626
https://github.com/Geonovum/KP-APIs/issues/627
---
 DesignRules.md | 13 +++----------
 1 file changed, 3 insertions(+), 10 deletions(-)

diff --git a/DesignRules.md b/DesignRules.md
index 5de84a0..60d6f88 100644
--- a/DesignRules.md
+++ b/DesignRules.md
@@ -621,12 +621,8 @@ Changes in APIs are inevitable. APIs should therefore always be versioned, facil
       </dd>
       <dt>How to test</dt>
       <dd>
-         <ul>
-            <li> Step 1: The API MUST meet the prerequisets to be tested. These include that an OAS file (openapi.json) is publicly available, parsable, all $refs are resolvable and paths are defined.</li>
-            <li> Step 2: In the open api specification the info and version object MUST be available.</li>
-            <li> Step 3: The version MUST comply with Semantic Versioning.</li>
-         </ul>
-      </dd> 
+         The "API-Version" response header MUST comply with Semantic Versioning.
+      </dd>
    </dl>
 </div>
 
@@ -653,10 +649,7 @@ Changes in APIs are inevitable. APIs should therefore always be versioned, facil
       </dd>
       <dt>How to test</dt>
       <dd>
-         <ul>
-            <li> Step 1: A request to the base url MUST give a response and include the header "API-Version".</li>
-            <li> Step 2: The value of the header "API-Version" MUST have a valid Semantic Versioning number.</li>
-         </ul>
+         A response MUST include the header "API-Version".
       </dd>
    </dl>
 </div>