Skip to content

[TF-Interop-Discovery] Please do not merge #110

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

Open
remcollier wants to merge 2 commits into
base: main
Choose a base branch
from
Open

[TF-Interop-Discovery] Please do not merge #110

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0a12af8
added first text
remcollier Dec 16, 2025
5068f89
little bit more
remcollier Dec 16, 2025
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
15 changes: 12 additions & 3 deletions TaskForces/Interoperability/Reports/report-interoperability.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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>

Expand Down Expand Up @@ -781,7 +781,7 @@ <h3>Discussion</h3>
</section>
</section>
<section>
<h2>Profiles</h2>
<h2 id="profiles">Profiles</id=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>
Expand Down Expand Up @@ -829,7 +829,16 @@ <h3>Discussion</h3>
</section>
<section>
<h2>Discovery</h2>

<p>
<a href="#principle2">Principle 2 (Single entry point)</a> 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>
<p>
Discovery mechanisms use a shared representation to advertise the existence of a resource, typically in the form of a
<a href="#profiles">Profile</a>.
</p>
<section data-dfn-for="Foo">
<h3>Relevant Standards and Initiatives</h3>

Expand Down