From 0a12af892f8fa45ee3601b89a65f15adc02f52e9 Mon Sep 17 00:00:00 2001
From: Rem Collier <rem.collier@ucd.ie>
Date: Tue, 16 Dec 2025 09:49:19 +0000
Subject: [PATCH 1/2] added first text

---
 .../Interoperability/Reports/report-interoperability.html   | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/TaskForces/Interoperability/Reports/report-interoperability.html b/TaskForces/Interoperability/Reports/report-interoperability.html
index c7dd3b7..dcdc4fd 100644
--- a/TaskForces/Interoperability/Reports/report-interoperability.html
+++ b/TaskForces/Interoperability/Reports/report-interoperability.html
@@ -572,7 +572,7 @@ <h3>Architectural Constraints</h3>
 
           <!-- <p class="def"><strong>Principle 2 (Single entry point)</strong>: Given a single entry URL into a Hypermedia MAS, agents should be able to discover the rest of the system and the means to participate in it by following hyperlinks.</p> -->
 
-          <p class="def"><strong>Principle 2 (Single entry point)</strong>: A Hypermedia MAS should expose one or more entry URLs from which the rest of the system and the means to participate in it can be discovered through hyperlinks.</p>
+          <p id="principle2" class="def"><strong>Principle 2 (Single entry point)</strong>: A Hypermedia MAS should expose one or more entry URLs from which the rest of the system and the means to participate in it can be discovered through hyperlinks.</p>
 
           <p>The core idea behind this second principle is to maximize the usage of hypermedia in order to minimize coupling within the MAS, which promotes <i>Discoverability</i> and <i>Evolvability</i>. This principle draws directly on the <i>Hypermedia As The Engine of Application State (HATEOAS)</i> constraint in REST [[FIELDING00]].</p>
 
@@ -829,7 +829,9 @@ <h3>Discussion</h3>
     </section>
     <section>
       <h2>Discovery</h2>
-
+      <a href="#principle2">Principle 2 (Single entry point)</a> states that a Hypermedia MAS should expose one or more entry URLs from which the rest of
+      the system and the means to participate in it can be discovered through hyperlinks. The principle method for achieving this
+      is the creation of discovery services.
       <section data-dfn-for="Foo">
         <h3>Relevant Standards and Initiatives</h3>
 

From 5068f89b103c1f400ec2299e9168560819ec80da Mon Sep 17 00:00:00 2001
From: Rem Collier <rem.collier@ucd.ie>
Date: Tue, 16 Dec 2025 10:11:55 +0000
Subject: [PATCH 2/2] little bit more

---
 .../Reports/report-interoperability.html          | 15 +++++++++++----
 1 file changed, 11 insertions(+), 4 deletions(-)

diff --git a/TaskForces/Interoperability/Reports/report-interoperability.html b/TaskForces/Interoperability/Reports/report-interoperability.html
index dcdc4fd..c9d5682 100644
--- a/TaskForces/Interoperability/Reports/report-interoperability.html
+++ b/TaskForces/Interoperability/Reports/report-interoperability.html
@@ -781,7 +781,7 @@ <h3>Discussion</h3>
       </section>
     </section>
     <section>
-      <h2>Profiles</h2>
+      <h2 id="profiles">Profiles</id=h2>
       
       <aside class="issue">
           <p>We need to describe non-information resources that we interact with in a Web-based MAS: agents, tools, etc.</p>
@@ -829,9 +829,16 @@ <h3>Discussion</h3>
     </section>
     <section>
       <h2>Discovery</h2>
-      <a href="#principle2">Principle 2 (Single entry point)</a> states that a Hypermedia MAS should expose one or more entry URLs from which the rest of
-      the system and the means to participate in it can be discovered through hyperlinks. The principle method for achieving this
-      is the creation of discovery services.
+      <p>
+        <a href="#principle2">Principle 2 (Single entry point)</a> states that a Hypermedia MAS should expose one or more entry URLs
+        from which the rest of the system and the means to participate in it can be discovered through hyperlinks. Discovery may occur
+        either through ad-hoc exploration of the the Hypermedia Space by link following or through the provision of dedicated resources
+        hosted at well known IRIs. On a local network mDNS based discovery mechanisms may also be used.
+      </p>
+      <p>
+        Discovery mechanisms use a shared representation to advertise the existence of a resource, typically in the form of a 
+        <a href="#profiles">Profile</a>.
+      </p>
       <section data-dfn-for="Foo">
         <h3>Relevant Standards and Initiatives</h3>