| 1 |
Each attribute of each object has an owner: the owner is the federate responsible for updating that attribute
-
Called "owner-computes rule"! Any object must be updated by a particular federate
|
| 2 |
Different attributes of the same object may have different owners. One federate is updating an aircraft's position; another federate, subscribing to the position, is updating icing
|
| 3 |
"Privilege to delete" an object is an attribute owned by some federate
|
| 4 |
Ownership can change: responsibility for updating an attribute can pass from one federate to another. E.g., an aircraft modeled in an aggregate simulation could transfer ownership of the position attribute to a cockpit
|
| 5 |
Ownership exchange may be pushed or pulled
|
