From 9ce413d449331383f419a71fa41ed5a5e95dbdbc Mon Sep 17 00:00:00 2001 From: Ege Korkan Date: Sun, 28 Apr 2024 01:28:41 +0200 Subject: [PATCH 1/2] fix Eclipse Thingweb links --- index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index 35268db..f431cb6 100644 --- a/index.html +++ b/index.html @@ -186,8 +186,8 @@ The APIs defined in this document deliberately follow the [[[WOT-TD]]] specification closely. It is possible to implement more abstract APIs on top of them, or implementing directly the WoT network facing interface (i.e. the WoT Interface).

- This specification is implemented at least by the Eclipse Thingweb - project also known as node-wot, which is considered the reference open source implementation at the moment. Check its source code, including examples. + This specification is implemented at least by the Eclipse Thingweb + project also known as node-wot, which is considered the reference open source implementation at the moment. Check its source code, including examples.

From 6334fc0a14f821cb439549fd49b31639ec6da651 Mon Sep 17 00:00:00 2001 From: Ege Korkan Date: Mon, 29 Apr 2024 15:28:48 +0200 Subject: [PATCH 2/2] fix further links --- index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index f431cb6..34dba19 100644 --- a/index.html +++ b/index.html @@ -4273,8 +4273,8 @@

API design rationale

some challenges, this specification takes another approach that exposes software objects to represent the Thing metadata as data property and the WoT interactions as methods. One implementation - is node-wot - in the Eclipse ThingWeb project, + is node-wot + in the Eclipse ThingWeb project, which is the current reference implementation of the API specified in this document.