-
Notifications
You must be signed in to change notification settings - Fork 0
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.
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
What can Platforms host ? #8
Comments
Good question but I just wanted to note that ranges or domains are not compulsory in case we don't have an exact constraint here. |
Does it make any sense to host an artifact ? [TO DO : we need to define and clarify :contains / :hosts / :hasWorkspace ?] |
There is ":hostsWorkspace a owl:ObjectProperty ; [TO DO : what is the relation between a :Workspace and a :Platform ?] |
A distinction is made between :containsAgent and :containsArtifact. What about a :containsSubWorkspace? Do we really need to explicit :containsX ? |
one radical option would be to have only one relation (eg. contains) instead of multiple (eg hosts, containsArtifact, etc.) and to use typing: :aPlatform hmas:contains :aW1523, a:Machine4 . :aW1523 hmas:contains :Agent6 . |
In order to see if we really need the hmas:host property, I propose to consider the following question, the answer will decide if we need it : Can a platform not host an agent that is contained in its workspace? If the answer is "yes", then we need it. Another similar question is : |
Okay let's try something. Let's consider that I'm in the officeWorkspace. What can we conclude ? I'm contained in the officeWorkspace, but I cannot be hosted by the platform since I'm a guest and I do not have any login. Does that make any sense to say that I'm not contained in the Platform ? The definition of hmas:host property --> domain = Platforms, range = Workspaces U Agents (or range = Resources as it is actually the case). The actual definition lets possible to consider that an artifact may be hosted by a platform too ? |
This relates to the discussion in Issue #6. As @FabienGandon suggested above, for now, I would not impose constraints on the range of On
So this goes along the lines of the example given by @DrLeturc. In the end, I think the final distinction between I've updated the definitions for |
in #6 Andrei wrote:
So should we also say that a platform can host other platforms ? +1 for this |
@maximelefrancois86 : i think yes, it should. |
Pull Request #31 introduces the |
How much of this discussion goes away if we focus on |
What is the range of
:hosts
?https://github.com/HyperAgents/ns.hyperagents.org/blob/ac90ef8fd96c8fabc8f0c1f0ecf92956723b65df/src/core.ttl#L163-L166
Is it only
:Artifact
and:Agent
?The text was updated successfully, but these errors were encountered: