15. Synchronization revisited

  • Synchronisation – Technical design of synchronization, to a first approximation.

  • In depth treatment of synchronisation – In which we descend into the details of synchronization, using perspectives as our guide.

  • Synchronizing subnetworks due to role filling – When a user fills a context role, suddenly an entire new part of the network may become visible to his peers. This requires a special mechanism in synchronisation.

  • Aspects require refinement of Inverted Queries – We can 'add' contexts and roles as Aspects to quickly build complex structures. However, this introduces a problem for synchronisation.

  • Who authors? – The Perspectives Universe would be static, but for the changes made to it by the end users. All of these changes are tracked and annotated with their author. In this text we discuss how we compute the authoring role.

  • Query Inversion over Model Boundaries – An author may reach out, through a query, to a role type defined in an imported model. Consequently, an inverted query must start at that type - but the author may well have no control over that model.

  • Optimizing Inverted Query Application – In this text we describe an optimization of the functionality that applies inverted queries.

  • Synchronization and Public Resources – Public resources necessitate a refinement of synchronization


1. If no authoring role is provided by the API caller, we take it to be the System User.