DM: need to simplify osc_action
Task 1
After CCB discussion 2022.04.14:
- the actor and duration exist for all
action
types, so it should not be a field of osc_action - the events should not be action parameters. If they exist, they also come from the Language
- osc_action must be associated to osc_actor (currently it is un-associated action!)
- We will keep osc_action as general parent so that an DM extension can put general parameters there, if this is ever needed
- also, provides good organization for overall structure of DM
- We could leave the "duration" parameter in the uml diagram
- Must re-write the "osc_actions parent action" section to reflect these changes
- must update standard.osc
Task 2
Must make action_for_movable_object
the base class for all motion-related actions (action_for_vehicle and action_for_person)
This includes the osc_action
parent classy UML, but also the individual action UMLs (which currently inherit directly from osc_action
)