-
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
add constraints for port connectors #5
Comments
|
All those constraints apply for the trigger connections, too. |
We should enforce a unique name/identifier policy on the ports in the same block. |
Can we take some of the necessary constraints from the NPC 4 paper like Herman suggested? |
Of course! It would be nice if we were able to "reuse" the constraints in other BPC-compliant metamodels (e.g. by M2M transformations). |
@scymtym could you link to the NPC 4 paper here as well for reference? |
The paper can be found here: https://core.ac.uk/display/45288978 |
I will reopen this issue with for constraints on which data connection to be allowed. |
DataConnector
orTriggerConnector
should not connect a port to itself (checking rule)FunctionBlock
DataBlock
SchedulerBlock
FunctionBlock
DataBlock
SchedulerBlock
FunctionBlockContainer
DataBlockContainer
FunctionBlock
SchedulerBlock
FunctionBlock
SchedulerBlock
FunctionBlockContainer
The text was updated successfully, but these errors were encountered: