Co-Simulation Master/Slave Terminology in DCP

[maarme]

As discussed I am raising this topic as an issue. For political correctness reasons the co-simulation community should part with the master/slave terminology as it is associated with slavery as a dark part of human history and use alternative terms like master/minion or orchestrator/unit etc. This topic was recently raised in multiple paper reviews for good reasons. The DCP standard documentation should also avoid the terminology and use something innocuous that does not potentially hurt the standard reputation and that also can be cited without issues.

[martinkrammer]

Summary/Alternative terms:

For "Master":

• master
• orchestrator
• primary
• leader
• agency
• hive
• conductor
• captain
• schemer
• guide

Slave:

• minion
• unit
• secondary
• follower
• replica
• operative
• node
• worker
• replica
• drone
• handler
• steward
• emissary
• doer
• mason
• coordinator
• conscript

[martinkrammer]

Alternatively, the terms master/slave may remain in the specification, and a preamble could be added to the specification.

[martinkrammer]

Another proposal:

• "Node0" and numbering
• Unit
• controller/agent (could be misleading, use case related. agent is supposed to work on its own)
• importer (terminology in FMI3 - probably not suitable for DCP)
• manager

Most neutral ones:

• primary/secondary
• follower
• conductor/unit
• director

[martinkrammer]

"DCP slave" -> "DCP Unit". Seems straightforward, in-line with FMI. "DCP Master" -> "DCP director", "DCP manager"