Holotomial
Analysis

                                                                         Contact
Hands on
2D-mapping		 Slides
Stacking		 Eyes
Pairing		 Spherical
Time-space		 3D-Dynamic
Perspectives
Section 2         Foreword        *Holotomy        Scenology        Configuration        Scenography
 

2.5

 ----- Scenography
 

A scenography is nothing special but putting scenarios in a written format.

  

Like for the configurations, it is also a large diversity of written formats. We choose a conventional codification for when a scenario or a schema needs to be handled by a machine or liaised with numbers and tables formats.

By this convention, we designate actors and objects by [q], actions by [p] and time-periods by [t].

A complete action may be represented by [q] x [p] x [t] where the sign "x" means "combined with".

The adjacent figure illustrates that this convention is enough to comply with most of the existing programming syntaxes.

We mention also here that we will later use the symbols [1] and [i] respectively for real and imaginary, [u] and [v] respectively for uncertainty and void and that the symbol [ ] has the generic meaning of space or collection.

  

< previous page

related parallelisms

next section >

  
 
 
 


Parallelisms : Programming language

Programming language

We underline a manner to maintain a compatibility between procedures written from and as holotomies with the usage of current programming languages like in OOP (Object Oriented Programming), MultiAgent Programming and SOA (Services Oriented Architecture) applications.

Care must be taken that our above denominations may eventually designate both single objects-actors or collections of - with not necessity to specify.

Interesting is to notice that a similar type of language can be utilized for both machines and human being executed programs.

We do not have any particular requirements on the syntax that may remain on the ownership of those  languages. We only mention that we may more naturally comply with MultiAgent programming than with OOP languages because those later languages make extensive usages of inheritances that we have conventionally rejected.