Skip to content

[Interop TF Report] Architectural considerations #92

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

[Interop TF Report] Architectural considerations #92

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 33 additions & 7 deletions TaskForces/Interoperability/Reports/report-interoperability.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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>

Expand Down Expand Up @@ -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>
Expand Down