From 15cf0e116a59470fdf2bc82430136c3ad9119ee5 Mon Sep 17 00:00:00 2001 From: Andrei Ciortea Date: Mon, 1 Dec 2025 11:43:48 +0100 Subject: [PATCH 1/3] interop: Draft intro to Section 4 (Identification) --- .../Reports/report-interoperability.html | 28 +++++++++++++++---- 1 file changed, 23 insertions(+), 5 deletions(-) diff --git a/TaskForces/Interoperability/Reports/report-interoperability.html b/TaskForces/Interoperability/Reports/report-interoperability.html index f213ca8..2ddfa64 100644 --- a/TaskForces/Interoperability/Reports/report-interoperability.html +++ b/TaskForces/Interoperability/Reports/report-interoperability.html @@ -554,9 +554,11 @@

Architectural Constraints

The principles are adapted from — and discussed in detail in — [[CIORTEA19]]. Their theoretical underpinning is the REST architectural style [[FIELDING00]], but they extend beyond REST to address requirements specific to agents, such as Resource Monitoring (see also [[KHARE04]][[FIELDING17]]).

-

Principle 1 (Uniform resource space): All entities in a Hypermedia MAS, and the relations among them, should be represented in a uniform, resource-oriented manner consistent with the Web architecture.

+

Principle 1 (Uniform resource space): All entities in a Hypermedia MAS, and the relations among them, should be represented in a uniform, resource-oriented manner consistent with the Web architecture.

-

The core idea behind this first principle is to project the observable state of a Web-based MAS into a uniform, distributed hypermedia environment (cf. [[[#mas-web-application-layer]]]). This promotes Scalability by enabling the seamless distribution across the Web: agents can use hyperlinks to discover and interact with other entities within and across Hypermedia MAS. It also supports Interoperability, Extensibility, and Evolvability through uniform hypermedia views of heterogeneous components.

+

The core idea behind this first principle is to project the state of a Web-based MAS into a uniform, resource-oriented, and distributed hypermedia environment (cf. [[[#mas-web-application-layer]]]). Resources in this environment may include not only documents (or information resources) — such as agent cards, FOAF profiles, or WoT Thing Description Documents — but also processes (e.g., agents, tools, services), real-world objects (e.g., devices), or abstract concepts (e.g., ontological terms). We refer to this broader category of entities as non-information resources [[COOLURIS]].

+ +

Having a uniform, resource-oriented representation provides consistent access to all these entities and enables linking and reuse across systems. This principle promotes Scalability by enabling seamless distribution across the Web: agents can use hyperlinks to discover and interact with other entities within and across Hypermedia MAS. It also supports Interoperability, Extensibility, and Evolvability through uniform hypermedia views of heterogeneous components.

The trade-off is decreased efficiency: components must translate between their internal data representations and the uniform representations exposed via their interfaces, which are necessarily less optimized for the specific needs of individual components.

@@ -568,7 +570,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.

-

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]].

+

The core idea is to maximize the usage of hypermedia in order to minimize coupling within the MAS, which promotes Discoverability and Evolvability — allowing agents to join and navigate the system dynamically with minimal prior configuration. This principle draws directly on the Hypermedia As The Engine of Application State (HATEOAS) constraint in REST [[FIELDING00]].

@@ -576,7 +578,7 @@

Architectural Constraints

Principle 3 (Observability): A Hypermedia MAS should enable agents to selectively monitor and receive updates about relevant resources and events in their virtual environments using Web standards.

- This principle enables Situatedness and Resource Monitoring, and improves the Scalability of the overall Hypemedia MAS: selective perception allows agents to focus only on those parts of the distributed hypermedia environment that are relevant to their current tasks, enabling them to handle larger environments while reducing the load on the underlying hypermedia infrastructure.

+

This principle enables Situatedness and Resource Monitoring, and improves the Scalability of the overall Hypemedia MAS: selective perception allows agents to focus only on those parts of the distributed hypermedia environment that are relevant to their current tasks, enabling them to handle larger environments while reducing the load on the underlying hypermedia infrastructure.