search

HyperAgents / hmas

An ontology to describe Hypermedia Multi-Agent Systems, interactions, and organizations.
https://purl.org/hmas/
2 stars 0 forks source link

range of `:contains` #9

Closed maximelefrancois86 closed 2 years ago

maximelefrancois86 commented 2 years ago

https://github.com/HyperAgents/ns.hyperagents.org/blob/ac90ef8fd96c8fabc8f0c1f0ecf92956723b65df/src/core.ttl#L106-L109

Core meeting 2021-11-29: "the object of :contains can be agents, artifacts, and workspaces"

DrLeturc commented 2 years ago

If everything is rdf:resource, then everything can be contained in a workspace. Should a workspace contain a :Platform ? Does that make any sense ? (why not.) Or should we consider a super class that groups only :Workspace :Agent and :Artifact to restrict :contains ?

What are the pros and cons ?

I think a :Workspace may contain different MAS (i.e. :Platform), a :Workspace may contain :Artifact and :Agents, a :Workspace may contain :SubWorkspaces.

andreiciortea commented 2 years ago

Here :Workspace is meant as an environment abstraction and is inspired by the Agents & Artifacts meta-model (part of the JaCaMo meta-model). In JaCaMo, a workspace can contain agents, artifacts, and since CArtAgO 3.0 it can also contain sub-workspaces (i.e., other workspaces). We can find similar concepts in other MAS platforms, e.g. "containers" in JADE that can only contain agents. Such logical containers typically contain abstractions used to design and program MAS.

A :Workspace typically provides agents with an abstract logical view of some part of their MAS, e.g. what other agents and artifacts situated are in that workspace. We might decide later that other abstractions are needed, e.g. perhaps the work that @oboissier started with Adnane around situated artificial institutions could bring some new concepts. Still, these would be abstractions used to model MAS. At the moment, the main abstractions we use to model MAS and that can be contained in a workspace are agents, artifacts, and workspaces. Organizations (or more precisely organizational entities) are currently also reified through artifacts contained in some workspace.

@DrLeturc side-note: we also make a distinction between MAS and :Platform, e.g. a MAS could be running across multiple platforms. However, there could be an artifact in some workspace that provides agents with affordances to interact with the underlying platform.

For now, I will leave this issue open but I will add the range for :contains that we agreed upon in the Nov 29 meeting.

FabienGandon commented 2 years ago

I would suggest to close that issue indicating the decision on the range of hmas:contains, noting the link to issue #20 for the notion of hmas:MASPlatform and dispatching other questions to other issues if needed to keep each issue focused e.g. an issue on the need for a class hmas:MAS