You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the future, PLANVIZ will be the one that manages the verbosity of the activity name, where it will default to :display-name with args (see #55 )
Optionally, PLANVIZ (based on a user setting) can display the verbose version (intended to be used by a developer working on her plant implementation).
Let’s pick a simple layout for this verbose string.
If we have a plant-part, we must also have a plant-id defined for the activity. However, it is possible to have an activity with a plant-id, without a plant-part. Also, we’ll always have an interface if we have a plant-id. Finally, I suppose we can have an interface without a plant-id.
However, there are some default values that we may or may not want to make explicit at the Pamela TPN-generation level: The default value of plant-id is “plant”, and the default value of interface is “RMQ”.
So the possible combinations are: <activity> <plant-part> <plant-id> <interface> <activity> <plant-id> <interface>
Since there is a natural concept hierarchy here, let’s keep the delimiters simple, and use email and DNS conventions (“@" and “.” delimiters). This gives us: <activity>@<plant-part>.<plant-id>.<interface> (e.g., "rotate-wheel(200)@left-front-wheel.vehicle1.RMQ”) <activity>@<plant-id>.<interface> (e.g., “move-to(2,3)@vehicle1.RMQ”)
The text was updated successfully, but these errors were encountered:
In the future, PLANVIZ will be the one that manages the verbosity of the activity name, where it will default to :display-name with args (see #55 )
Optionally, PLANVIZ (based on a user setting) can display the verbose version (intended to be used by a developer working on her plant implementation).
Let’s pick a simple layout for this verbose string.
If we have a plant-part, we must also have a plant-id defined for the activity. However, it is possible to have an activity with a plant-id, without a plant-part. Also, we’ll always have an interface if we have a plant-id. Finally, I suppose we can have an interface without a plant-id.
However, there are some default values that we may or may not want to make explicit at the Pamela TPN-generation level: The default value of plant-id is “plant”, and the default value of interface is “RMQ”.
So the possible combinations are:
<activity> <plant-part> <plant-id> <interface>
<activity> <plant-id> <interface>
Since there is a natural concept hierarchy here, let’s keep the delimiters simple, and use email and DNS conventions (“@" and “.” delimiters). This gives us:
<activity>@<plant-part>.<plant-id>.<interface>
(e.g.,"rotate-wheel(200)@left-front-wheel.vehicle1.RMQ”
)<activity>@<plant-id>.<interface>
(e.g.,“move-to(2,3)@vehicle1.RMQ”
)The text was updated successfully, but these errors were encountered: