[Closes #119] Add manufacturing scenario for discovery of behavior specifications #136
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Replaced: Behavior -> Behavior Execution Behavioral Specification -> Behavior Specification has Form -> Form signifies -> Signification of Behaviors Updated: Behavior Execution, Action Execution, Behavior Specification, Action Specification, Form, Input, Schema Removed: has Action
update scenario description and competency questions to cover discovery of behavior specifications and behavior parametrization
What are the behavior specifications that a given signifier signifies?
Q2: What are the action specifications that a given signifier signifies?
Q3: What are the forms that describe how to execute a given specified action?
Q4: What is the input that is expected by a given specified action?
Q5: What are the schemas of a given expected input?
Classes: BehaviorExecution, ActionExecution, BehaviorSpecification, ActionSpecification, Input Properties: signifies, hasForm, expectsInput, hasSchema
gnardin
approved these changes
Sep 21, 2023
| :signifies a owl:ObjectProperty ; | ||
| rdfs:isDefinedBy :interaction ; | ||
| rdfs:domain :Signifier ; | ||
| rdfs:range sh:NodeShape ; |
There was a problem hiding this comment.
Please check with the Web Semantic experts if it is Okay to have sh:NodeShape as rdfs:range.
There was a problem hiding this comment.
Addressed in a past commit based on #136 (comment).
| - a form describing an HTTP request, | ||
| - a form describing a request based on the Constrained Application Protocol (CoAP). | ||
|
|
||
| The agent discovers the signifier, that is exposed in the profile of the robotic arm artifact. Based on the signified information, the agent moves the gripper by providing an [`onto:GripperJoint`](https://ci.mines-stetienne.fr/kg/ontology#GripperJoint) as input, and sends an HTTP request based on one of the forms. |
There was a problem hiding this comment.
I would say that reformulating the sentence as suggest in item 3 is enough. I do not see the need to make the changes proposed in items 1 and 2.
FabienGandon
approved these changes
Sep 22, 2023
DrLeturc
approved these changes
Sep 25, 2023
andreiciortea
approved these changes
Sep 29, 2023
FabienGandon
deleted the
scenario-manufacturing-discover-behavior-specs
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This manufacturing scenario motivates concepts defined by the hMAS ontology for the discovery of behavior specifications.
See the scenario folder for further details.