From 1eb57894f9880c6d5a2102f26010336784082f08 Mon Sep 17 00:00:00 2001
From: Ingo Friese <ingo.friese@telekom.de>
Date: Mon, 7 Apr 2025 09:35:22 +0000
Subject: [PATCH] ref check

---
 TS-0041-oneM2M-SensorThings_interworking.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/TS-0041-oneM2M-SensorThings_interworking.md b/TS-0041-oneM2M-SensorThings_interworking.md
index dd32f1f..0e7b94c 100644
--- a/TS-0041-oneM2M-SensorThings_interworking.md
+++ b/TS-0041-oneM2M-SensorThings_interworking.md
@@ -73,7 +73,6 @@ The following referenced documents are not necessary for the application of the
 - Use the **EX** style, add the letter "i" (for informative) before the number (which shall be in square brackets) and separate this from the title with a tab (you may use sequence fields for automatically numbering references).
 
 - <a name="#_ref_i.1">[i.1]</a>    oneM2M Drafting Rules (http://www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf)
-    
 
 
 # 3 Definition of terms, symbols and abbreviations
@@ -134,7 +133,7 @@ For the purposes of the present document, the [following] abbreviations [given i
 
 # 4 Conventions
 
-The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in this document are to be interpreted as described in the oneM2M Drafting Rules [\[i.1\]](#_ref_i.1).
+The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in this document are to be interpreted as described in the oneM2M Drafting Rules <a href="#_ref_i.1">[i.1]</a>.
 
 
 # 5 Introduction to OGC SensorThings API
-- 
GitLab