From f8c1e6d8cf0fb48b3eab9652daec89caea171da9 Mon Sep 17 00:00:00 2001
From: Andrei Ciortea <andrei.ciortea@gmail.com>
Date: Fri, 29 Aug 2025 08:47:06 +0200
Subject: [PATCH] Interop report: Add structure for architectural
 considerations

---
 .../Reports/report-interoperability.html      | 40 +++++++++++++++----
 1 file changed, 33 insertions(+), 7 deletions(-)

diff --git a/TaskForces/Interoperability/Reports/report-interoperability.html b/TaskForces/Interoperability/Reports/report-interoperability.html
index 694eba4..3c07bd5 100644
--- a/TaskForces/Interoperability/Reports/report-interoperability.html
+++ b/TaskForces/Interoperability/Reports/report-interoperability.html
@@ -281,6 +281,39 @@ <h3>Conceptual Dimensions for Web-based Multi-Agent Systems</h3>
         Throughout this report, we use these four conceptual dimensions to organize the discussion and emerging technologies.
 
       </section>
+      <section data-dfn-for="Foo">
+        <h3>Architectural Considerations</h3>
+      
+        <aside class="issue">
+          <p>Different approaches choose different distribution styles, e.g. MCP uses an RPC-style of distribution. This section discusses these different styles with reference to the Web architecture. The discussion could go into many directions, what emerged in our meetings is a need to look deeper than the agent level of abstraction. What seems important is to identify alignments and misalignments with the Web architecture.</p>
+        </aside>
+
+        <section>
+          <h3>Design Goals [Non-functional Requirements]</h3>
+
+          <aside class="issue">
+            <p>MAS are a class of systems known for NFPs such as <strong>flexibility/adaptability</strong>, <strong>openness</strong>, <strong>robustness</strong>, and <strong>scalability</strong> [Weyns, 2010]. The Web is a distributed hypermedia system specifcally designed to meet a well-defined set of NFPs, among which <strong>scalability</strong>, <strong>heterogeneity</strong>, <strong>evolvability</strong>, and <strong>extensibility</strong> [Fielding and Taylor, 2002; Taylor et al, 2010]. Inhereting the properties of the Web in Web-based MAS is desirable, which means we need to design MAS that are aligned with the Web Arch [[HMAS]].</p>
+          </aside>
+
+        </section>
+
+        <section data-dfn-for="Foo">
+          <h3>Architectural Patterns for Web-based MAS</h3>
+
+          <aside class="issue">
+            <p>Components, connectors, and data view of Web-based MAS. See also Weyns' architectural patterns for situated MAS [Weyns, 2010] and the work on hMAS [Ciortea et al, 2018].</p>
+          </aside>
+
+        </section>
+
+        <section data-dfn-for="Foo">
+          <h3>Considerations</h3>
+
+          <aside class="issue">
+            <p>The main considerations we draw from the above. The focus is on alignment with the design of the Web.</p>
+          </aside>
+        </section>
+      </section>
       <section data-dfn-for="Foo">
         <h3>State of Web-based Multi-Agent Systems</h3>
 
@@ -435,13 +468,6 @@ <h3>Agentic AI</h3>
         </section>
 
       </section>
-      <section data-dfn-for="Foo">
-        <h3>Architectural Considerations</h3>
-      
-        <aside class="issue">
-          <p>Different approaches choose different distribution styles, e.g. MCP uses an RPC-style of distribution. This section discusses these different styles with reference to the Web architecture. The discussion could go into many directions, what emerged in our meetings is a need to look deeper than the agent level of abstraction. What seems important is to identify alignments and misalignments with the Web architecture.</p>
-        </aside>
-      </section>
     </section>
     <section data-dfn-for="Foo">
       <h2>Identification</h2>