[TF-Interop-Discovery] Please do not merge

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>
 
@@ -746,7 +746,7 @@ <h3>Agentic AI</h3>
       </section>
     </section>
     <section data-dfn-for="Foo">
-      <h2>Identification</h2>
+      <h2 id="identity">Identification</h2>
 
         <aside class="issue">
           <p>We need to identify agents, tools, protocols, and other entities in a Web-based MAS in a uniform way and independent of context. Additional requirements may be relevant depending on the degree of openness, e.g. see the <a href="https://www.w3.org/TR/did-1.0/#design-goals">requirements identified by the DID WG</a>.</p>
@@ -781,7 +781,7 @@ <h3>Discussion</h3>
       </section>
     </section>
     <section>
-      <h2>Profiles</h2>
+      <h2 id="profiles">Profiles</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,12 +829,48 @@ <h3>Discussion</h3>
     </section>
     <section>
       <h2>Discovery</h2>
-
+      <p>
+        The role of discovery is to enable Web agents to provide mechanisms to support the retrieval of other Web Agent or Tool 
+        <a href="#identify">identities</a> at runtime either directly or indirectly through intermediary <a href="#profiles">profiles</a>
+        that include the identity of the Web Agent or Tool.
+      </p>
+      <aside class="issue">
+        <p><A href="https://www.w3.org/TR/wot-discovery">WoT Discovery Standard</A> specifies two phases for Discovery: Introduction and Exploration.
+          Introduction is the discovery of a URL that describes an Agent/Tool. Exploration is the consumption of the resource associated with that
+          URL which may be an identity or profile. My concern is that Exploration is really use of the identifier/profile which is described in
+          the relevant section.
+        </p>
+      </aside>
+      <p>
+        The need for discovery is based on <a href="#principle2">Principle 2 (Single entry point)</a> which 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>
+      <aside class="issue">
+        <p>
+          Approaches considered in WoT Discovery: Direct, Well-Known Uniform Resource Identifier [RFC8615], DNS-based Service Discovery, DIDs?
+        </p>
+      </aside>
       <section data-dfn-for="Foo">
         <h3>Relevant Standards and Initiatives</h3>
-
+        A number of standards and initiatives exist that address Web Agent or Tool discovery. The following sections focus on agents and tools.
         <section data-dfn-for="Foo">
           <h3>Agent Discovery</h3>
+            <h3>FIPA</h3>
+            <p>
+              The section on <a href="#identify">Identification</a> includes a brief introduction to the
+              <a hef="https://web.archive.org/web/20250321030044/http://www.fipa.org/repository/index.html">FIPA Standards</a>. The 
+              topic of  agent discovery is mentioned in two of the standards: the <a href="https://web.archive.org/web/20250814070600/http://www.fipa.org/specs/fipa00001/SC00001L.html">FIPA Abstract Architecture Specification (FIPA00001)</a>
+              and the <a href="https://web.archive.org/web/20230528171843/http://fipa.org/specs/fipa00023/SC00023K.html">FIPA Agent Management Specification (FIPA00023)</a>.
+              The first of these standards defines an abstract architecture for agent platforms (the runtime infrastructure on which
+              agents are deployed) based on: agents and services. Services are intended to provide the infrastructure supports necessary 
+              to deploy agents. This includes the Agent Directory Service, a support service that agents can register with and which 
+              they can use to find other agents they wish to interact with. The second standard introduces the mandatory Agent Management
+              Service (AMS) that is the authority for the creation of FIPA Agent Identifiers and is also an implementation of the Agent
+              Directory Service.
+            </p>
+          </section>
 
         </section>
         <section data-dfn-for="Foo">