search

HyperAgents / hmas

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

`hmas:Hostable` considered harmful #146

Closed Antoine-Zimmermann closed 1 year ago

Antoine-Zimmermann commented 1 year ago

Knowing that something is hostable isn't really helpful at all. The class hmas:Hostable serves no useful purpose. Being "hostable" is as interesting as being "parentable", being "knowable", being "ownable", being "containable", being "exposable" etc. Agents are defined as being Hostable. People are Agents (arguably, but the ontology does not say so), therefore people can be hosted on MAS platforms. What does it mean for a person to be hosted on a MAS platform?

There isn't any constraint on hmas:Hostable so anything could be hostable. It suffices to say ex:thing hmas:isHostedOn ex:platform and it is hostable.

FabienGandon commented 1 year ago

One of the interests of hmas:Hostable could be in declaring it disjoint or the complement of hmas:NonHostable and using them as respective super classes of hmas:SoftwareAgent and foaf:Person and other classes and as a domain of hmas:isHostedOn and therefore to support some validation of the descriptions.

But we if don't have a need/scenario for this then an alternative would be to remove hmas:Hostable.

andreiciortea commented 1 year ago

@Antoine-Zimmermann @FabienGandon please review the PR for the manufacturing scenario on the discovery of Hypermedia MAS Platforms and their Profiles, which motivates Resource Hosting: https://github.com/HyperAgents/ns.hyperagents.org/pull/130

The scenario could be further extended towards normative aspects with terms of services or API rate limiting policies attached to some Hypermedia MAS platform (cc @gnardin).

@Antoine-Zimmermann Good point on people being hosted. +1 for @FabienGandon's proposal.

Antoine-Zimmermann commented 1 year ago

@andreiciortea In the scenario you mention, I do not see anything about hmas:Hostable.

andreiciortea commented 1 year ago

@Antoine-Zimmermann indeed, I misread your initial message. The scenario motivates hmas:isHostedOn. The class hmas:Hostable was discussed in issues https://github.com/HyperAgents/ns.hyperagents.org/issues/8 and https://github.com/HyperAgents/ns.hyperagents.org/issues/23, and introduced with PR https://github.com/HyperAgents/ns.hyperagents.org/pull/31.

@maximelefrancois86 might have more input on hmas:Hostable

Antoine-Zimmermann commented 1 year ago

The issues that introduced and discussed hmas:Hostable do not really show any use case for it. I stand on my position that this is a bad term that does not provide any useful information.

maximelefrancois86 commented 1 year ago

Originally hmas:isHostedOn could be applied to different kinds of entities: Agents, Artifacts, ... Introducing hmas:Hostable was just an attempt to define a common superclass that could be used as the domain of property hmas:isHostedOn.

If this is not a requirement to always have a domain/range for properties, then we can delete hmas:Hostable.