From 0a12af892f8fa45ee3601b89a65f15adc02f52e9 Mon Sep 17 00:00:00 2001
From: Rem Collier
Date: Tue, 16 Dec 2025 09:49:19 +0000
Subject: [PATCH 1/4] 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 @@
Architectural Constraints
-
Principle 2 (Single entry point): 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.
+
Principle 2 (Single entry point): 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 core idea behind this second principle is to maximize the usage of hypermedia in order to minimize coupling within the MAS, which promotes Discoverability and Evolvability. This principle draws directly on the Hypermedia As The Engine of Application State (HATEOAS) constraint in REST [[FIELDING00]].
@@ -829,7 +829,9 @@
Discussion
Discovery
-
+ Principle 2 (Single entry point) 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.
Relevant Standards and Initiatives
From 5068f89b103c1f400ec2299e9168560819ec80da Mon Sep 17 00:00:00 2001
From: Rem Collier
Date: Tue, 16 Dec 2025 10:11:55 +0000
Subject: [PATCH 2/4] 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 @@
Discussion
-
Profiles
+
Profiles
Discovery
- Principle 2 (Single entry point) 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.
+
+ Principle 2 (Single entry point) 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.
+
+
+ Discovery mechanisms use a shared representation to advertise the existence of a resource, typically in the form of a
+ Profile.
+
A number of standards and initiatives exist that address Web Agent or Tool discovery. The following sections focus on agents and tools.
Agent Discovery
+
FIPA
+
+ The section on Identification includes a brief introduction to the
+ FIPA Standards. The
+ topic of agent discovery is mentioned in two of the standards: the FIPA Abstract Architecture Specification (FIPA00001)
+ and the FIPA Agent Management Specification (FIPA00023).
+ 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.
+