Skip to content
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

227 motivating scenario discovery of behavior specifications for sending messages #228

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

Conversation

danaivach
Copy link
Contributor

This manufacturing scenario motivates the use of concepts defined by the hMAS ontology for the discovery of behavior specifications for sending messages to agents.

See the scenario folder, and the FIPA ontology for further details.

Closes #227

danaivach and others added 21 commits January 17, 2024 12:47
…tions-for-sending-messages' of github.com:HyperAgents/ns.hyperagents.org into 227-motivating-scenario-discovery-of-behavior-specifications-for-sending-messages
…ior-specifications/README.md to domains/manufacturing-environments/discover-messaging-behavior-specificationsREADME.md
…-specificationsREADME.md to domains/manufacturing-environments/discover-messaging-behavior-specifications/README.md
…tions-for-sending-messages' of github.com:HyperAgents/ns.hyperagents.org into 227-motivating-scenario-discovery-of-behavior-specifications-for-sending-messages
Copy link
Contributor

@NicoRobertIn NicoRobertIn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems that everything is okay

Maybe a squashed commit is relevant since 23 commits have been made

Copy link
Contributor

@maximelefrancois86 maximelefrancois86 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, with the minor edits you just did during the heartbeat meeting

Copy link
Contributor

@andreiciortea andreiciortea left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @danaivach!

@danaivach
Copy link
Contributor Author

@NicoRobertIn how do you suggest resolving the conflicts?

@NicoRobertIn
Copy link
Contributor

The conflict is just on the test reports, which is not that concerning

The report should regenerate itself as soon as the test action triggers on main

Just make sure that the squash merge does not contains [skip actions] in the commit message so that it triggers

If you want a choice just give priority to the report version that is the most recent (the test date should appear in the reports)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Motivating Scenario] Discovery of behavior specifications for sending messages
4 participants