From 4bc50208973a41e7fe52acd0cc6abfd755f83b46 Mon Sep 17 00:00:00 2001
From: Michael Lagally <31951801+mlagally@users.noreply.github.com>
Date: Thu, 18 Feb 2021 15:54:20 +0100
Subject: [PATCH 1/4] Reference device

---
 index.html | 30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)

diff --git a/index.html b/index.html
index 772ecf8..71fb76e 100644
--- a/index.html
+++ b/index.html
@@ -593,6 +593,36 @@ <h3 id="profile-description-methodology">Methodology</h3>
                 -->
       </p>
     </section>
+	  
+    <section id="reference-devices">
+      <h2>Reference Device Classes</h2>	  
+	<p>
+	Since a profile is to be supported by a wide variety of devices, lower 
+	bound for device characteristics and capabilities have to be selected.
+	Small embedded devices have very limited RAM and Flash storage among other limitations 
+	(e.g. clock speed, power consumption) which make complex processing unfeasible.
+	</p>
+	<p>
+	<section>
+	<h3 id="use-case">Use Case</a>
+	<p>
+	As the baseline use case we select the capability to process a full TD without additional external components.
+	A device in the <em>producer</em> role generates a TD and allows consumers to use telemetry and control of device actions.
+	In the <em>consumer</em> role a device is extracting pieces of information from a single TD to 
+	control or read telemetry data from some other device.
+	</p>
+	<p>These devices are simple consumers/producers that just are required to consume a SINGLE TD.
+	The characteristics of a minimum device which can run a TCP / HTTP stack + process JSON payloads to consume and expose TDs
+	were identified with several model assumptions and by inspecting some real workd devices.
+		
+	<p>
+	Additionally all TDs that were used during the PlugFests showed that 95% of TDs were around 8KB in size.
+	</p>	
+	<p>
+	A maximum size of a TD of 16 KB leaves enough headroom and can be still handled on embedded devices with 64-128KB of RAM.
+	</p>
+    </section>
+	     
   </section>
 
 

From aca9083b54b5e3b885a3ff0b914f8d529ec6e431 Mon Sep 17 00:00:00 2001
From: Michael Lagally <31951801+mlagally@users.noreply.github.com>
Date: Thu, 18 Feb 2021 15:57:56 +0100
Subject: [PATCH 2/4] Update index.html

---
 index.html | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/index.html b/index.html
index 71fb76e..23f076a 100644
--- a/index.html
+++ b/index.html
@@ -595,7 +595,7 @@ <h3 id="profile-description-methodology">Methodology</h3>
     </section>
 	  
     <section id="reference-devices">
-      <h2>Reference Device Classes</h2>	  
+      <h2>Reference Device</h2>	  
 	<p>
 	Since a profile is to be supported by a wide variety of devices, lower 
 	bound for device characteristics and capabilities have to be selected.
@@ -612,8 +612,11 @@ <h3 id="use-case">Use Case</a>
 	control or read telemetry data from some other device.
 	</p>
 	<p>These devices are simple consumers/producers that just are required to consume a SINGLE TD.
+	</p>
+	<section>
+	<h3 id="core-device">Embedded Reference Device</a>
 	The characteristics of a minimum device which can run a TCP / HTTP stack + process JSON payloads to consume and expose TDs
-	were identified with several model assumptions and by inspecting some real workd devices.
+	were identified with several model assumptions and by inspecting some real world devices.
 		
 	<p>
 	Additionally all TDs that were used during the PlugFests showed that 95% of TDs were around 8KB in size.
@@ -621,6 +624,7 @@ <h3 id="use-case">Use Case</a>
 	<p>
 	A maximum size of a TD of 16 KB leaves enough headroom and can be still handled on embedded devices with 64-128KB of RAM.
 	</p>
+       </section>
     </section>
 	     
   </section>

From 9f13b1f5a0c246fd953a6e7ce6b7e86ddbc29718 Mon Sep 17 00:00:00 2001
From: Michael Lagally <31951801+mlagally@users.noreply.github.com>
Date: Thu, 18 Feb 2021 15:59:20 +0100
Subject: [PATCH 3/4] Update index.html

---
 index.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.html b/index.html
index 23f076a..dfdddbd 100644
--- a/index.html
+++ b/index.html
@@ -604,7 +604,7 @@ <h2>Reference Device</h2>
 	</p>
 	<p>
 	<section>
-	<h3 id="use-case">Use Case</a>
+	<h3 id="use-case">Use Case</h3>
 	<p>
 	As the baseline use case we select the capability to process a full TD without additional external components.
 	A device in the <em>producer</em> role generates a TD and allows consumers to use telemetry and control of device actions.
@@ -614,7 +614,7 @@ <h3 id="use-case">Use Case</a>
 	<p>These devices are simple consumers/producers that just are required to consume a SINGLE TD.
 	</p>
 	<section>
-	<h3 id="core-device">Embedded Reference Device</a>
+	<h3 id="core-device">Embedded Reference Device</h3>
 	The characteristics of a minimum device which can run a TCP / HTTP stack + process JSON payloads to consume and expose TDs
 	were identified with several model assumptions and by inspecting some real world devices.
 		

From e5c999c00d47c4df5ab49e5b26fc761bc3ececf8 Mon Sep 17 00:00:00 2001
From: Michael Lagally <31951801+mlagally@users.noreply.github.com>
Date: Thu, 18 Feb 2021 16:02:38 +0100
Subject: [PATCH 4/4] Update index.html

---
 index.html | 1 +
 1 file changed, 1 insertion(+)

diff --git a/index.html b/index.html
index dfdddbd..916532e 100644
--- a/index.html
+++ b/index.html
@@ -613,6 +613,7 @@ <h3 id="use-case">Use Case</h3>
 	</p>
 	<p>These devices are simple consumers/producers that just are required to consume a SINGLE TD.
 	</p>
+	</section>
 	<section>
 	<h3 id="core-device">Embedded Reference Device</h3>
 	The characteristics of a minimum device which can run a TCP / HTTP stack + process JSON payloads to consume and expose TDs