Home → News 2020 November
 
 
News 2020 November
   
 

01.November.2020

15:51 and 28:41 UTC+1
Investigations::Multimedia, AI and KM

*** Work in progress - better structure and wording, links missing ***
United States Department of Defense (DoD), Xslent, and Big Kahuna Technologies
The project, which was initially titled Network Aware Business Data Management System (NABDMS), later renamed to Global Information Architecture (GIA), and is now titled Global Information Network Architecture (GINA), is a giant fraud by responsible persons of the United States Department of Defence (USDoD) and the United States Armed Forces, specifically the United States Navy and the United States Army, connected federal entities, and contractors of the department, the armed forces, and other entities, specifically the two highly dubious and suspicious companies Xslent, which developed the GINA, and Big Kahuna Technologies, which succeeded Xslent as contractor and is holding the non-existent rights for the illegal and void patents related to GINA and filed by persons related to the company Xslent and continuing the process of stealing our orignal and unique works of art titled Analyse und Entwurf eines Betriebssystems nach evolutionären und genetischen Aspekten==Analysis and Design of an Operating System according to Evolutionary and Genetic Aspects, also called as Evolutionary operating system and Evoos, and Ontologic System, also called as OS, and created by C.S..

We quote the only relevant patent application filed by 5 fraudulent persons related to the company Xslent on the 30th of June 2006:
The present invention provides' a Global Information Architecture (GIA) to create an object-oriented, software-based modeling environment for the modeling of various data sources and allowing queries and transactions across those sources. The modeling environment is described in itself. Introspection is achieved since the model is described in the model, and early validation that the infrastructure is correct is established in that the infrastructure must execute against itself. [...] [Note that it was designated as a network-based Global Information Architecture (GIA), but not a Global Information Network Architecture (GINA), and has introspective respectively reflective capabiities.]
The present invention relates to information technology and particularly to an architecture, system, and technique for modeling network-based environments comprised of multiple information sources and presenting, such as a single information resource.
[...]
The United States Department of Defense (DoD) recognized this problem and envisioned a Global Information Grid (GIG) as a solution. The objective of the GIG is to provide a distributed, redundant, fault-tolerant network-based environment that allows authorized information consumers to manage all of theinformation to Which they have access; a system that is ubiquitous, open, secure, and agile. Such a vision implies a fundamental shift in information management, communication, co-existence, integrity, and assurance. Once realized, the GIG vision would provide authorized users with a seamless, secure, and interconnected information environment, meeting the needs of all users, regardless of the location of the information source or the user.
An approach to creating a GIG generally requires (1) the creation of a directory that represents and objectifies all of the information on that organization's netWorks, (2) the creation of a set of access rules for each information user, either explicitly or by role, that describes the level of access each user has for each information resource, and (3) an information appliance that Would provide appropriate access to each user for each information resource. There have been a number of attempts, e. g., virtual databases and summary databases built using ETL (Extraction, Transformation, and Loading) tools, to create environments that meet these criteria. However for very large organizations these requirements are not sufficient. Large organizations require a GIG with the additional capabilities listed below:
1. Multi-Organizational Access [...]
2. Information Resource Relationship Management [...]
3. Multiple Organization and User-Specific Views [...]
4. Human and Computer-User Support [...]
5. Operation Over the Public Internet [...]
6. Support for Rapid Change [...]
[...]

The present invention overcomes these and other deficiencies of the prior art by providing a Global Information Architecture (GIA) for managing and uniting complex, diverse, and distributed components of a Global Information Grid based on two architecture principles. The first is that GIA manages "information objects," i.e., objects that do not have algorithmically intense or very specific operations, through collections of configured components. [...] These types of objects have the useful characteristics of being both capable of supporting a very large subset of the overall software requirements for highly network-centric information environments, and being able to be implemented as a collection of relatively simple, reusable objects, which is a technique that is used by GIA.
In traditional object-oriented development, object behavior, e. g., services, methods, attributes, etc., is defined by a "class," where all objects of a particular class have the same behavior. Any changes to behavior are implemented by programming a new class. However, GIA takes a different approach: rather than adapting behavior by creating or changing classes, it uses multi-purpose classes that are designed to implement behavior through collections of configurable, multi-purpose components. GIA's implementation of information objects through these collections of configured components enables complete configurability.
The second is that GIA is built as a GIA application. Making GIA a GIA application, coupled with the implications of the first principle, results in significant advantages in addressing the six (6) additional capabilities identified above. Since GIA manages information objects, and GIA is a GIA application, GIA has an information object representation of information objects. GIA enables this information object representation of information objects by providing a component for all ofthe characteristics of an information object: services, properties, and relationships. The services and properties of information objects can be directly associated with components through information objects. A new model was created to express the relationships between information objects as information objects: Vector-Relational Data Modeling (VRDM). VRDM expresses a relationship from one information object to another information object as an information object by specifying the relationship, the characteristics ofthat relationship, and the use of that relationship by the first information object. VRDM represents all three of these constructs as information objects Whose relationships, in turn, are expressed through VRDM as information objects in their own right. This build up of VRDM using VRDM is an example of one of the characteristics of GIA: the iterative process of assembling primitive constructs that are then used to configure larger constructs and then larger constructs until GIA is completely assembled. GIA's use of this iterative process to create complexity from a few concepts allows for a very high level of configurability, much higher than using a more traditional, programmed approach.
In another embodiment of the invention, a method for creating Wrapper objects that expose and implement an information object interface comprises the steps of: [...] The method may further comprise the steps of: acting on at least one event, defining an association between the at least one event and the at least one service, and executing the association when the event is raised. The component definitions include information required for executing the desired behavior. The method may further comprise the steps of: defining a service reflexively as another information object including definitions of component services as component information objects, Which are implemented by invoking the component services in response to an invocation of the information object.
[...]
In another embodiment of the invention, a method of implementing factories for objects comprises the steps of: defining an information object for a named set ofobjects to be created that includes an object class, associating a factory to the information object, creating a factory with a creation object method that uses a name, invoking the creation object method, accessing the information object by the name, and creating an object using the class specified in the named information object.
In another embodiment of the invention, a method of creating an extensible collection of factories comprises the steps of: defining an information object for factories, creating a factory-of-factories, and creating a set of factories per the information object for factories.

In another embodiment of the invention, a method of creating a universal information object management environment comprises the steps of: defining information objects for information objects, information sources, each type of component of an information object, defining instances of each of these information objects that collectively represent the characteristics of each of these information objects and factories for creating each ofthese information objects, and creating an object to incrementally build the universal information object management environment by building each type of information object from the description of each type of information object using the corresponding instances. The method may further comprise the step of accessing another instance of a universal information obj ect management environment as collections of information sources. The method may further comprise the steps of: de?ning a mapping of syntax of a non-conforming universal information object management environment to syntax of the universal information object management environment, accessing the universal information object management environment in response to requests made by the non-conforming universal information object management environment.
[...]
In another embodiment ofthe invention, a method of defining applications comprises the steps of: defining applications as information objects that represent collections of user-interfaces, defining systems as information objects that represent collections of applications, and assembling applications and systems per the defined applications and defined systems.
In another embodiment of the invention, a method of describing access a user has to a first information object comprises the steps of: defining a user as a user information object, defining a vector between the user and the first information object, defining a vector between the user and components of the first information object, and assembling a second information object defined on the first information object by assembling only the components specified by the vector, which in turn act on the components of the first information object.
[...]
In another embodiment of the invention, a method for creating a global information architecture comprises the steps of: creating a first information object, Wherein the first information object is configured by metadata and capable of defining other information objects; and executing the first information object. The metadata may describe services of the configured information object, the properties of the configured information object, and/or the relationship of the configured information object With a second information object. The method may further comprise the step of creating a second information object, wherein the second information object is configured with metadata and at least partially defined by the first information object. The content ofthe first information object can be exposed. The first information object may also interoperate with any network available information source.
The present invention provides a GIA that is capable of managing data agnostic to source, type, and network, and each instance of GIA can access data from other instances of GIA as though it was its own, thus making collection universal and ubiquitous. GIA is a robust, comprehensive, and highly efficient, environment for integration, aggregation, and federation of disparate technologies from both a logical and physical perspective. Inherent in this environment is the ability to securely acquire, aggregate, process, control, and deliver large sets of data, in a short time frame, to facilitate interoperability and the deployment of customized, event specific, experiences to end-users.
[...]
[...] the present invention is applicable to any information infrastructure, particularly those in which dynamically changing conditions require a flexible information management environment.
[...]
The present invention enables a "Global Information Architecture" (GIA) for managing a Global Information Grid (GIG). A Global Information Grid refers generally to a distributed environment for collecting, transforming, and presenting information to users, both human and machine. [...]
[...]
A central concept in GIA is that objects can be referenced in multiple "WorldSpaces" and these are inherently hierarchical. A user's (including non-human users) view of information data sources are controlled by her WorldSpace, a structure that uses the attributes she has that makes her unique to identify the appearance and behavior that an object in GIA would present to her. These attributes can include (among others) her usemame, roles, language, locale, and organization. Hence, WorldSpace allows constraint of objects and its services that are available to a user. This view is itself described via Vector Relational Data Modeling (VRDM) through vectors and is wholly configurable, unlike most traditional information systems whose ability to lock down data access is fixed. Since WorldSpace constraints are described in the language of VRDM itself, this description can be changed completely with metadata, allowing for new and unique implementations of WorldSpace without coding. This is achieved by making the User the starting point for any traversal to objects of interest. The vectors (which are configurable) used for this traversal then constrain what objects a user can see and/or change.
In addition to managing any type of data agnostic to type or form, the GIA is able to access that information anywhere on the network. It is also able to understand that information in a context that includes the relationships between instances of information, both explicit and implicit. Moreover, the GIA supports a spectrum of actions on information objects, e.g., the collecting, transforming, and presenting mentioned above, but also updating, deleting, validating, starting, etc. [...]
[...]
Solving the GIG management problem cost-effectively virtually requires that the GIA be configurable. However, the configuration requirements needed to support the GIG are deeper than in a typical software model: not only must there be a model where object components can be configured, but object relationships and services must also be configurable. Moreover, a conventional multi-level security (MLS) approach may be insuficient as different collections of information consumers can have different models.
To meet that demand, the GIA implements, among other things, two new types of software models: a configurable, bootable, reflexive information object model ("GIA Information Model") and a model that can create and run information model configurations ("GIA Execution Model"). "Reflexive" means that the system is self-describing, i.e. a system that describes other systems is reflexive if it is an example of the type of systems it describes. The approach used by the GIA execution model is to wrap all acquired instances of network available information in a software object with a standard interface that exposes the same collection of methods, and provides for access to components of the information through named properties. The GIA Information Model is a coherent information model and is a configuration, i.e., it exists in metadata, and is reflexive because the GIA Information Model can be represented in the GIA Information Model. As the GIA Information Model is bootable, the GIA Execution Model actually loads the first components which represent the primitive concepts of the model into active memory and then uses them to bring in the rest of the GIA Information Model description to create the GIA information Model. [Bingo!!! The whole section shows that our Evoos has been taken as source of inspiration and blueprint (see the section Comment below for a detailed explanation), because both new types of software models, called here GIA Information Model and GIA Execution Model, are essential parts of our Evoos, and the booting process is described in the chapter 8.2.3 Prinzip eines Virus==Principle of a Virus of The Proposal.]
The DssManager 110 exposes a simple, SQL-like Data Access Layer (DAL) 120 interface [...], which is suitable for both object-oriented and database-oriented applications to use. [...]
[...]
[...] GIA supplies its own interface environment, its Task Oriented-User Interface (TOUI) 130 to meet non-specialized needs for visualization and management of GIG data. GIA's TOUI is a configurable, browser-based data representation environment that makes meeting that organizational need "easy." [...] GIA's TOUI includes the ability to display information objects geographically through a Global Information System (GIS) display.
GIA's TOUI 130 operates directly on the base DAL 120. [...]
[...]
This layered structure is part of what enables GIA to be a configured environment, i.e., it enables the programming that is required to change or enhance GIA to be expressed as configurations of "object metadata," i.e., metadata that describes the behavior of an object, i.e., services, properties, and vectors (relationships), not as actual coding.
The foundation of configurability is fundamental to the GIA architecture and the "information object" methodology that GIA embodies. An information object is an instance of information that exposes the standard information object interface used by GIA; it gets this interface by being wrapped in a GIA information object wrapper, which is the collection of components that are assembled to wrap an instance of network-available information so that it functions as an information object. To create new information objects in GIA, one creates a configuration that specifies the information object's components, services, and location, rather than doing programming. Then, using the configuration as a set of instructions, GIA creates and assembles a series of objects, using the layer managers described above, that collectively function as the required information object. [...] GIA assembles its information model according to a specification 250 that describes the components and their relationships.
GIA incorporates novel and important variations on the standard object-oriented development factory pattern. (The factory pattern is a design construct used in object-oriented development where an object is created whose function is to create new objects.) First, the DssManager actually functions as a Factory-of-Factories. Second, the DssManager uses object metadata expressed as information objects to define the actual objects that get created as factories, and then again to define the objects that are created by the factories. [...]
[...]
GIA is fundamentally different: it successfully accomplishes complete user-interface-to-data-store configurability. GIA successfully accomplishes a complete, user-interface to-data-store, objects-through-component configurability as a result of two strategic architectural decisions (as mentioned above) that were imposed on GIA design, and five concepts that came out of those decisions:
(1) Architecture Decision: GIA Manages Information Objects
[...]
(2) Architectural Decision: GIA is a GIA Application
This decision ended up being fortuitous: the approach is far more fundamental to the success of GIA as an environment for managing information objects through configuration than was originally anticipated. By forcing GIA to be a GIA application a large number of problems were identified early on that had to be solved by creating new structures for managing information objects. Of importance was the identification of an information object representation of information objects. This problem led to the following two concepts:
(3) Concept: Information Objects as Components of Information Objects
In order for GIA to be a GIA application, then an information object has to have a representation as information objects. Hence, a component version of all of the characteristics of an information object must be present: services, properties, and relationships. It is possible to represent information services and properties by specifying a name, set of characteristics, and an implementing object only. However, expressing relationships as information objects required the following concept:
(4) Concept: Vector-Relational Data Modeling (VRDM)
There are three different requirements to expressing information object relationships as information objects: the relationship, the characteristic of the relationship, and the use of the relationship by the information objects. VRDM provides all three of those constructs as information objects. This capability is fundamental: to successfully componentized services, properties, and relationships, the relationship between information objects and their services, properties and relationships is expressed through configuration.
(5) Concept: Layered Information Component Objects Assemblies
Since the configuration of a GIA object is an information object, each component ofthe information object has to be an assembly of the corresponding components. [...]
(6) Concept: Information Access Through Information Objects (WorldSpace)
Once one has the structure described in (1)-(5) above, a new possibility exists for managing multi-level access control: the components available to a user simply become vectors between the user and the component objects that make up the information objects accessible by the user.
(7) Concept: VRDM-Based Information Object Assembly
In order to have all of these concepts come together, the information objects that manage the components are assembled per the vectors that define the relationships between those components.
[...]
FIG. 3 illustrates an information object structure 300 according to an embodiment ofthe invention. The layering of the DSS structure 200 is also reflected in the layering of the information object 300. In effect, the layers in the DSS 200 are used to assemble a layered information object 300 that encapsulates all of the components required to represent the information object in the way that is desired for the user for which the information object is being assembled. This compartmentalization of capabilities produces the required result: a configured information object that manages the universal information object space that is the DSS 200.
The information object structure 300 employs a consistent interface, IContent interface 305, for all ofthe layered assemblies. [...]
[...]
This layering of IContent interfaces 305, 315, 325, and 335 is one of the techniques that allow GIA to work. The actual structure of an information object can be the full set of layers described above, or simply an InformationContent object 340. Without this layered approach, the first concept identified as number 3 above would not be possible.
[...]
[...] In addition, the inclusion of a full Event model, where Events can trigger other services, allows for both synchronous and asynchronous processing of events. [...]
[...]
Moreover, because GIA is designed as a GIA application, these definitions themselves are information objects.
[...]
An important consequence of this assembly of an information object from component objects is not obvious: the assembled information object functions as an executable implementation of that information object's specification ("configuration"). In effect, the information object represents the executable object described by the configuration, not a specification that is then interpreted by some other (large) "information object program," the traditional approach. In a very real way the DSS 200 executes the specification 250 - no traditional programming is required.
The use of a common interface for all of the structures is another important aspect of the invention: by using that approach the same sets of configurations can be used to represent information sources, information objects, and user specific information objects. This commonality makes the implementation of the DAL 120, and the adaptation of the DAL 120, achievable, unlike the conventional situation where every information object has its own interface.
[...]
FIG. 5 illustrates a bootstrap operation 500 according to an embodiment of the invention. (Bootstrap is the process of starting up a complex system by initially starting up a simple system that then starts up the more complex system by following a procedure that is intelligible to the simpler system.) Bootstrapping a reflexive architecture is particularly challenging: one has to be able to start up the simple system with very few concepts if the system is to be truly reflexive.
[...]
Again, GIA accomplishes full configurability because the objects that represent GIA are themselves configured information objects. This reflexive, self-describing characteristic of GIA enables GIA as the engine that creates objects that represent executable expressions of information object specifications described in object metadata.
[...]
Alternatively, an RFIDContentServer could be created that listens to a Radio Frequency Identification (RFID) Server to track and report the location of physical assets.
[...]
Applications are built by creating forms [(Task Oriented-User Interface] (TOUI)[)] around objects that participate in a common set of functionality. Of necessity, the first two applications were (1) the application that supports the entry of metadata of the basic GIA Objects (XType, Element, etc.), and (2) the application that supports the creation of a simple TOUI (Forms, Windows, and Fields), that enabled application (1).
[...]
1. A method for creating universal information object management environment as an executable environment description, the method comprising the steps of:
creating descriptions of information sources, associated information objects, object characteristics, and relation ships among the information sources, information objects, and object characteristics, where the descriptions are fully functionally described by the descriptions of the information sources, associated information objects, object characteristics, and their relationships;
creating universal components that represent information objects, types of sources, types of characteristics, and types of relationships, which collectively represent the services and behavior of the environment, whose configurations are defined by associated descriptions, including descriptions of associated information objects, object characteristics, and their relationships; and
assembling at runtime instances of information objects defined on information sources by collecting universal components with associated objects, object characteristics, and relationships that represent their behavior and configuration within the network of their described relationships."

Comment:
The authors have taken our Evoos as source of inspiration and blueprint, and even implemented, or better said, copied essential parts of our Evoos, specifically our two new software models called by them GIA Information Model and GIA Execution Model (specification-based or gene-based an hence configurable as a reflective system (model), bootable, reflective and hence reflexive, executable, flexible, component-based information processing system of systems (model), including the concept of factory-of-factories and based on software development patterns) and the so-called Resource-Oriented Computing (ROC) paradigm, which has copied virtually the same original and unique expression and related characteristic properties of our Evoos.
software development patterns with components and reflexive system teaches the basic invention behind GIA, but with bootable, executable system in addition we have our Evoos
As the titles of The Proposal and our Evoos already make clear, it is a reflective Evolutionary Computing (includes Genetic Programming (GP)) concept, architecture, model, and system. Therefore, Evoos is an Evoos application and its services, properties and relationships are expressed through configuration used for assembling.

The works of art and the personal expressions have been described in The Proposal, The Prototype, and on related websites using specific presentations for the purposes of discussion only. It will be readily apparent to one of ordinary skill in the art, however, that the personal expressions and principles of the works of art can be performed and reproduced in other ways. Therefore, the works of art should not be regarded as being limited in scope to the specific presentations and discussions disclosed, but instead as being fully commensurate in scope with our rights. See the

  • chapter 2.2.1 Komponenten eines Betriebssystems==Components of an Operating System of The Proposal: all points
  • chapter 2.6 Negative Eigenschaften von Betriebssystemen== Negative Properties of Operating Systems of The Proposal: handling of "komplexe Software==complex software" and providing "geforderte Flexibilität==required or demanded flexibility"
  • chapter 2.7 Neue Anforderungen an Betriebssysteme aus der Sicht der Software-Technologie==New Demands on Operating Systems from the Perspective of Software Technology of The Proposal: all points
  • chapter 3.2 Funktionsweise eines Gehirns==Functioning of a Brain of The Proposal:
    "[...] Eine einfache Synthese des Gehirns unterscheidet zwischen dem A-Gehirn und dem B-Gehirn. Die Neuronen des A-Gehirns stehen in Kontakt mit der äusseren Umgebung und den internen Organen und erhalten so Informationen. Die Neuronen des B-Gehirns stehen nur in Kontakt mit Neuronen des A-Gehirns. Das B-Gehirn wird über die Neuronen des A-Gehirns informiert und kann dieses kontrollieren. Diese Kontrolle kann nicht nur bestimmte Bereiche, sondern auch die Gesamtheit des A-Gehirns betreffen. In diesem Modell repräsentiert das A-Gehirn das gewöhnliche Gehirn und das B-Gehirn das Bewusstsein (siehe [Min, 1988]). [...] Das Modell eines festverbundenen Netzwerks ist nach diesen Erkenntnissen nicht mehr haltbar (siehe [Chevallier]).==A simple synthesis of the brain differentiates between the A-brain and the B-brain. The neurons of the A-brain are in contact with the external environment and the internal organs and thus receive information. The neurons of the B-brain are only in contact with neurons of the A-brain. The B-brain is informed about the neurons of the A-brain and can control it. This control can affect not only certain areas, but also the entire A-brain. In this model, the A-brain represents the ordinary brain and the B-brain represents consciousness (see [Min, 1988]). [...] The model of a fixed network is no longer tenable according to these findings (see [Chevallier])."
  • chapter 7 Ziel der vorgeschlagenen Diplomarbeit==Objective of the proposed diploma thesis respectively The Proposal:
    "In der vorgeschlagenen Diplomarbeit soll ein Betriebssystems nach evolutionären und genetischen Aspekten modelliert werden. Während der Erstellung der Spezifikation und des Entwurfs sollen unter anderem die Integration von Methoden des evolutionären Rechnens und des künstlichen Lebens Beachtung finden.==In the proposed diploma thesis, an operating system is to be modelled according to evolutionary and genetic aspects. During the preparation of the specification and the design, the integration of methods of evolutionary computing and artificial life shall be considered."
  • chapter 8.2.2 Virtuelle Zellteilung==Virtual Cell Division of The Proposal:
    "Im Gegensatz zu der ersten Variante liegt der Fokus auf einer bereits vorhandenen "virtuellen Zelle", die eine "virtuelle DNA" enthält. Die "virtueller DNA" repräsentiert eine Struktur, die zum Beispiel Informationen über zwei Baupläne enthält. Der eine Teil enthält die Bauanleitung für die "virtuelle Zellteilung" und der andere Teil die Atome eines logischen Modells für den m -Kernel eines logischen Betriebssystems. Beide Bauplane sind ineinander verschränkt. Eine einfache Funktion sorgt für die Reproduktion der Zellen bis erneut eine "kritische virtuelle Masse" entstanden ist. Die einfache Funktion entschlüsselt dabei eigentlich nur die in der "virtuellen DNA" enthaltenen Informationen und baut dadurch neue Strukturen im Arbeitsspeicher auf.
    Da in dieser Variante bereits die Atome eines ganzen Kalküls reproduziert werden, ist in dieser "kritischen virtuellen Masse" auch eine qualitativ bewertbare Funktionalität enthalten.==In contrast to the first variant, the focus is on an already existing "virtual cell", which contains a "virtual DNA". The "virtual DNA" represents a structure that contains, for example, information about two building plans. One part contains the blueprint for the "virtual cell division" and the other part contains the atoms of a logical model for the m-kernel of a logical operating system. Both blueprints are interlocked. A simple function takes care of the reproduction of the cells until a "critical virtual mass" is created again. The simple function actually decodes only the information contained in the "virtual DNA" and thereby builds new structures in the working memory.
    Since in this variant the atoms of an entire calculation are already reproduced, this "critical virtual mass" also contains a qualitatively assessable functionality."
  • chapter 8.2.3 Prinzip eines Virus==Principle of a Virus of The Proposal:
    "Diese Variante erfordert ein bereits aktives Computer-System als Umgebung in der die Entwicklung einer "virtuellen Zelle" bis zu seiner Metamorphose zur virtuellen logischen Maschine geschützt wird. Dieses Vorgehen erlaubt die Benutzung bereits vorhandener Resourcen, also auch bereits vorhandener Betriebssystemdienste. Die Variante wird durch folgende mathematische Aussage gestützt: Wenn ein berechenbares reflektives System möglich ist, sichert die Theorie der Berechenbarkeit, dass das System von einem turing-äquivalenten System "bootstrapped" werden kann. Dazu ist ein geeigneter Evaluator nötig (siehe [Ban, 1999]). Das eigentliche Problem verschiebt sich somit auf die Beantwortung der Frage, wie ein logisches Modell eines Evaluators zu gestalten ist.==This variant requires an already active computer system as an environment in which the development of a "virtual cell" is protected until its metamorphosis into a virtual logical machine. This procedure allows the use of already existing resources, thus also already existing operating system services. The variant is supported by the following mathematical statement: If a computable reflective system is possible, the theory of computability ensures that the system can be "bootstrapped" by a turing equivalent system. Therefore a suitable evaluator is necessary (see [Ban, 1999]). The actual problem is thus shifted to the answer of the question how to design a logical model of an evaluator."
  • chapter 7 Künstliche Embryologie==Artificial Embryology of The Prototype.

    No matter what the steps of the claimed method are, but one cannot patent the creating act of C.S. in general and the cybernetic self-portrating act of C.S. in particular in relation to our Evoos or any entity when utilizing our Evoos, whereby we have shown with sufficient depth and detail that they merely reflect some of the foundations of our Evoos and therefore must be an editing of the original and unique, personal expression presented and discussed with our work of art titled Evoos and created by C.S. more than 6 years before its patent application was filed. Therefore, we consider the foundations of that patent (application) as plagiarism and therefore as infringement of the copyright of C.S. and eventually the patent issued on the basis of this patent application as void.
    In addition, that GINA looks merely like a known combination of basic software development patterns, such as factory, controller, wrapper, meta, and so on, utilized in object-oriented development and publicated several years before.
    In addition, we have here something like a triple store system, which is an older system based on two items or objects and a relation between them, which is a third item or object, and an executable XML. And we also have here the so-called Resource-Oriented Computing (ROC) paradigm also based on our Evoos. Missing was our kernel-less, reflective, and kernel-less reflective triple stores, substrates, fabrics, or computing environments, our Resource Description Framework (RDF) substrate, fabric, or computing environment publicated by an incompetent plagiarist (see the Investigations::Multimedia, AI and KM of the ...), our Web Ontology Language (OWL) substrate, fabric, or computing environment, and our Ontologic paradigm or simply Ontologics, which for example does it without the ballast of XML and in this way leads us back to Evoos and our OS is based on our Evoos. The latter closes any gap and legal loophole for fraudulent entities, that want to continue with the attempt of stealing our AWs and further IPs.
    See also the language PROGRES described in the documents titled "Introduction to PROGRES, an Attribute Graph Grammar Based Specification Language" and "PROGRES, A Visual Language and Environment for PROgramming with Graph REwriting Systems", which does it even more foundationally.

    Using multi-purpose classes that are designed to implement behavior through collections of configurable, multi-purpose components is considered a very bad system design, because it is difficult or even impossible to make any changes of it due to changed requirements, even and specifically in the case of GIA. Guess why the Object-Oriented (OO 1) and OO programming paradigms have emerged. In case of our Evoos and OS we also have for example a reflective, ontology-based, Ontology-Oriented (OO 2), Ontologic(-Oriented) (OO 3), cognitive system, and the automatic programming, Genetic Programming (GP), and Ontologic Programming (OP) paradigms utilized for the implementation of for example new classes.
    Furthermore, as can be seen with the movements in the field of mSOA initiated with our Evoos and the field of DevOps with a continues development process the common approach of what is called here prior art is still prefered by very well known programmers and system experts.

    But what we would like to know is how the authors want to

  • validate GIA against itself and if they really managed it, specifically how much information is required to describe GIA itself as a configurable, bootable, reflexive, and executable information model,
  • change GIA itself,
  • automate GIA itself, and
  • manage complexity, which is not reduced by GIA.

    It seems to be that the authors have fallen prey to the triple store system illusion in relation to the first and third questions, and are copying also our OS in relation to the second question (see also the quotes of an online encyclopedia below).
    Somehow, we also have the impression, that they did not know at all what they have truly stolen with our Evoos.

    We quote the homepage of the website of the company Xslent:
    "The primary focus of XSLENT LLC was the development of The Global Information Network Architecture (G.I.N.A.) under Cooperative Research and Development Agreement (CRADA) with the US Navy at the Naval Postgraduate School (NPS) in Monterey CA.
    Through this relationship, GINA has been deployed throughout the Dept of Defense for a spectrum of systems which require rapid configuration, processing, and presentation of data from multiple, non integrated, systems.
    The most notable deployments were with
    [•]NPS Coalition Operating Area Surveillance and Targeting System (COASTS) program exercises.
    [•]Integrated Base Operations Center (IBOC) for the US Army Combined Arms Center at Ft Leavenworth KS Garrison.
    [•]Rapid Ordering System (ROS) for US Army Corps of Engineers (USACE)
    In 2008, the GINA Technology was assigned to Big Kahuna Technologies LLC where it is currently being developed under CRADA with the US Army Corps of Engineers Engineering Research and Development Center."

    Comment:
    "In 2008 [...] where it is currently being developed" says all.
    See also the quotes of an online encyclopedia below, that clearify the timeline of related activities.

    We quote the homepage of the website of the company Big Kahuna Technologies:
    "Big Kahuna Vision",
    "[...] enables the bridging of the symbolic and the connectionist representations of the world through causal-dynamic executable-models. Contextual, causal, behavioral, and adaptive models described using our VRDM methods uniquely make possible the "computational plasticity" required for digital machines to infer, adapt, and control other systems based on the changing context of their operational environment"
    "For a machine to learn it must have the ability to calculate across concepts and relationships within the context of the moment and then adapt itself to those changes -- that is uniquely possible with the GINA technology"
    "Contextual adaptation of a system requires the ability to process the changing data associated with entities in the context of relationships that exist between entities and between the conceptual models that define them",
    "Throughout human history there have been those that were believed to have the ability to speak with God, the gods, or the spirits of the earth. In Hawaiian culture the Kahuna (keeper of the secrets) was seen as one who was capable of understanding the relationships between the spirits of the world, the gods, and humans. Every interaction between people, systems, and things creates new relationships. It is the mission of Big Kahuna Technologies to explore and develop new types of systems that provide the understanding of objects and events from the causal dynamics that exist in the relationships between things, and make accessible to both man and machine the meaning of what things are, what they might have been, and what they could be."

    Comment:
    There was no ontologics, no spirit, no metaphysical being, and so on at all, but just only a variant of an environment for executable ObjRel models.
    In fact, everything related to our OS and presented by that company has been stolen from us. This proves what the true goal and purpose of those two companies truly are and why we call them highly dubious fake companies. It is just one of the common patterns of fraud conducted by federal authorities.
    See also the quotes of an online encyclopedia below, that clearify the evolution.

    We quote an online encyclopedia about the subject GINA in the first version publicated on the 7th of June 2009:
    "The concept for the Global Information Network Architecture (GINA) evolved from a realization that the current technologies provided an unprecedented opportunity to create a useful GIG that could transform the possibilities for Net-Centric Operations. The Global Information Network Architecture (GINA) Team was created in 2004 to address this possibility. Originally developed under Cooperative Research and Development Agreement with The US Naval Postgraduate School (NPS) in Monterey CA, the projects initial title was Network Aware Business Data Management System (NABDMS). From early 2005 to late 2007 NPS jointly developed and tested the first generation of the Global Information Network Architecture (GINA). NABDMS received its DITSCAP Certification as an "Architecture" in July 2005.

    Technology
    Vector Relational Data Modeling (VRDM)... Modeling Models
    First... What IS Modeling?
    The dictionary defines modeling as, "The representation, often mathematical, of a process, concept, or operation of a system."
    While software modeling languages, such as Unified Modeling Language (UML) or Object Role Modeling (ORM), attempt to provide an iconic representation to articulate the structure or architecture of an application, they are not executable and have limited applicability beyond the software design environment.
    [...]
    GINA, at a high level, is a model for modeling. Designed to facilitate a principle of development where relationships between objects can be objectified and wielded as objects in their own right, GINA itself is an executable model configured using VRDM.
    VRDM is a core concept that is embodied by GINA. GINA could be looked at as an environment that turns collected data into a multi-dimensional object environment with each object being connected to other objects through vectors. This environment makes many of the information-centric tasks that a user might want to perform far easier than any other approach.
    A key concept of VRDM is that relationships among information objects should themselves be defined as information objects, and be fully configurable.
    Taking relationships and implementing them as GINA objects enables GINA to take configurations and assemble models that can perform most, if not all of the work done by typical hard-coded information applications, such as most enterprise systems, integrations, and information sharing systems.
    As a result of VRDM, it is possible to specify an application through describing the required components as a series of objects and their relationships, or vectors. VRDM enables disparate data, from disparate sources to be invoked and configured to relate in a "System of Systems" model called a specification. The behavior of a specification can be the much same as a contemporary application. The difference, however, is that with VRDM, there is no programming. GINA is a true CBOM for Object Modeling, where the models are themselves executable.
    Critical to this approach is the concept of Reflexivity, i.e., the GINA model is described as a GINA model, that permits deep configurability. When one is using the interactive development environment used to create GINA applications, one is using a GINA application. More importantly, GINA assembles GINA applications according to a GINA model for GINA applications. Deeper still, the GINA model is itself an example of a GINA model. This deep configurability is the key to GINA's power as interoperability and multi-level security ("MLS") engine.
    As a combination of hardware and software-based components, which meets the requirements of a true GIG, GINA is configured as a universal virtual network of data of any type from any source in any location on collected physical networks. GINA is a product of several key concepts which collectively enable it to represent a complete, configurable interoperability environment. These key concepts are embodied in a series of layers and components which collectively allow GINA to perform the types of functions and provide the type of services it needs to be a fully functional interoperability environment.

    Core VRDM Concepts
    Descriptive Programming
    Just as Assembler made machine language programming faster and more accurate, and descriptive languages for specifying procedures ("4GL"s like SQL) made procedural programming faster and more accurate, GINA's VRDM brings a new level of speed and accuracy to object-oriented programming.
    In the long run GINA's encapsulation of the management of network-available data may be more important that even its speed and accuracy for large organizations.

    Component Objects
    With VRDM, Data Agnostic Objects can be created to represent common relationships called Mechanisms. These Mechanisms can be reused and combined with others, new and existing, to create systems and subsystems. This facilitates rapid deployment and non-programmatic implementation.

    Complexity
    Just as everything in the world is assembled from remarkably few elements, arbitrarily complex systems can be assembled from relatively few objects. The key in both cases is that objects have to be designed for interaction and assembly. GINA is designed in that way. Fundamentally, at the bottom level are very few objects, e.g., objects, or XTypes in VRDM, and relationships between XTypes, or Vectors in VRDM. These objects are the primitives on which the VRDM object management model is based. In turn, instances of these primitives are assembled into the basic building blocks of VRDM: fully defined objects representing XTypes and Vectors, as well as constraints and simple entities. These can then be assembled to fully describe the GINA environment, and to allow the administrator to create the data objects to support a Task Oriented User Interface (TOUI), or a specific application.

    WorldSpace
    A central concept in GINA is that objects can be referenced in multiple WorldSpaces, depending on how a user gets to that object. A WorldSpace determines the applicability of an object's vectors, e.g. attributes and relationships, when assembled for a particular event or usage. WorldSpaces are inherently hierarchical: as one more tightly defines the WorldSpace associated with an event or usage, the more tightly one must define, and the more granularly one needs to specify associated behaviors.

    HyperPlanes
    If we look back at the concepts associated with GINA, we could say that an object exists in a 3 dimensional data object space. Its location in that space is defined by its order of complexity, its usage and related components, and the user and WorldSpace in which it is being accessed. At any given time the behavior of a system is dictated by all of its objects locations in this 3-dimensional object-space. However, this behavior is not the same for every user, and is influenced by the characteristics of that user that effectively define hyperplanes in this object space. Thus, the appropriate object model is only summarized in three dimensions, with multiple user-based dimensions of behavior effectively being summarized on this graphic. In effect, at any given time an object exists as a point in 7+ dimensional object behavior space. Remarkably, GINA not only models this space effectively, but does so in an environment where most specifications are created through configuration, not programming.

    Directory Sub System (DSS)
    GINA is implemented through a software-based, multi-layer, configurable data object management environment. Just as the entirety of GINA can be viewed as a series of well-structured layers, the data object management environment is also structured and layered, with multiple layers of the object management environment corresponding to each of the top three layers in the overall GINA. [...]

    Task Oriented User Interface (TOUI)
    Another model that has been built in GINA is called the Task-Oriented User Interface, or "TOUI". The current mainstream approach to user interfaces ("UIs") involves a process where a developer "paints", or in some other way creates a mark-up of the UI, and then defines the binding of components of that the UI to the underlying application using some standardized approach. The TOUI model takes a different approach: a UI is assembled at the time of request from components according to a set of vectors that take into the account model states and the user during the assembly process. As a result, the UI no longer represents the application that uses information, but rather becomes the external expression of the information model that represents the application. Moreover, because the definition of the UI is done as a set of metadata-defined GINA components, the expression of those components can be done in any environment that has sufficiently strong semantics for representing applications, whether that is Java, .NET, Python, or even a 3-D visualization environment[,] interfaces, etc."

    Comment:
    Note the date of publication 2009, which strengthens our allegations (see also the comment to the second quote of an online encyclopedia about the subject GINA below).
    Also note once again that a bootable, executable, reflective, flexible, component-based, and specification-based or gene-based system is our Evoos.
    Component objects are used in relation to Computer-Aided Software Engineering (CASE) tools for Visual Programming Languages (VPLs) and Rapid Application Development (RAD) for example.
    WorldSpace or worldview is a concept of Computer-Aided Design (CAD) applications since the early 1990s or even before. But they are different from n-dimensional data spaces.
    There was only the multi-layer logical structuring mechanism, but no hyperplane, which was said due to our n-dimensional OS based on the hypergraph. Note that "a layer is a logical structuring mechanism for the elements that make up [a] software solution, while a tier is a physical structuring mechanism for [a related] system infrastructure".
    The concept of TOUI is not new (see for example the documents titled "Oggetto: An Object Oriented Database Layered on a Triple Store", "Desktop Objects Directly Manipulating Data and Metadata" (Oggetto Desktop), and "Interactive Database Objects - Moggetto" (Oggetto with MOG editable widgets)).
    Also note the 3-D visualization.

    We quote an online encyclopedia about the subject GINA in the actual version publicated on the 22nd of October 2019:
    "Global Information Network Architecture (GINA) is a software framework that bridges the symbolic and the connectionist representations of the world through executable conceptual models. Declarative contextual, causal, behavioral, and adaptive models for computational inferencing, analysis, and control can run and adapt based on the changing context of data-in-motion. This patented software technology enables the processing and the orchestration of context and causality for counterfactual analysis, decision support, and learning machines - addressing key roadblocks in the continued evolution of current AI, interoperability, and system-of-systems solutions.
    Vector Relational Data Modeling (VRDM) is an object-based modeling language that differs significantly from traditional object-oriented software descriptions. A key goal of VRDM is to enable the definition of executable models. This means that the modeling constructs need to be capable of fully specifying the runtime structure of an application. One way VRDM achieves this is by introducing the notion of a Vector, which allows the participants in object relationships to be determined dynamically, as the model executes. This and the other core object-based constructs that make up the VRDM modeling language are combined through configuration, and not coding, to make possible software applications that are executable models and that are interpreted dynamically, just-in-time, just-in-context, and just-in-state.
    The computational model underlying the GINA software was designed to facilitate a new type of Global Information Grid (GIG) for US security and defense Net-Centric Operations. In 2004, The GINA research and development team was convened under a cooperative research and development agreement (CRADA) between the U.S. Naval Postgraduate School (NPS) in Monterey, California and XSLENT LLC. XSLENT LLC contributed the patented executable component based modeling environment technology with NPS providing leadership and implementation sponsorship. The project was called Network Aware Business Data Management System (NABDMS). In late 2008, the United States Army Corps of Engineers (USACE) and the Engineer Research and Development Center (ERDC) began a second phase of the project under CRADA with Big Kahuna Technologies LLC, the current IP holders for the GINA technology. The GINA environment has been implemented to become a High Level Architecture (HLA) for System Fusion Networks (SFN) as an interoperable and multi-level security ("MLS") engine.[1] because it uses Vector Relational Data Modelling (VRDM), a configurable, component based object model (CBOM) for managing data. GINA combines development, control and application. A third phase of the technology's evolution and implementations in support of US national security is underway with a CRADA with the Joint Staff of the Department of Defense for high-priority needs related to integration, system orchestration, sensor fusion, network convergence, cybersecurity, and numerous AI focused initiatives.

    GINA Technology Applications

  • Command and Control (C2)
  • C4ISR
  • Counterfactual analytics
  • Multi-level attribute-based network security
  • Non-compiled executable enterprise solutions
  • Cloud based digital artifact management (cloud library for documents, video, code, etc.)
  • Active Cyber Defense/Offense applications
  • Inference and Computational Learning
  • Transfer learning (models that exhibit this quality across different domain applications)

    References
    1 [...] "The Global Information Network Architecture (GINA) Technology Framework." Naval Postgraduate School, Monterey CA."]

    Comment:
    The given reference is a hyperlink that eventually leads to the domain ginaos.org, which seems to be an os or even an OS.
    Note that the

  • first version (2004 to 2007) is based on our Evoos respectively that executable component-based modeling environment is an edited and extended variant of our Evoos with the configuration or specification as virtual gene or virtual DNA for configuration, the GIA and objects as virtual nerve cells or neurons, and vectors as virtual dendrites, and compositions as virtual brains, and is very similar to the so-called ROC also based on our Evoos, as we already mentioned above, and also developed at the same time around the years 2004 to 2005,
  • second version (late 2008 to , and
  • third version is based on our OS,
  • none of our AWs are patentable, but copyrighted,

    obviously.
    Now, we also have the explanation for our impression that the GIG changed after the publication of our OS.

    We quote the document titled "Researchers, commanders partner on potential networking revolution" and publicated on the 31st of October of 2012:
    "[...] potential networking revolution [...] "
    "[...] "system of systems modeling environment," a digital landscape wherein multiple applications, users and components are able to interact and behave through specified configuration as linked multi-dimensional systems"
    "[...] rescue helicopters area able to "speak" to fixed-winged aircraft; that decision makers in tactical operations centers are able to look through the helmet-cameras of rescuers on the ground; and that rescuers are able to share information, intelligence and information feeds from a host of disparate technologies and agencies",
    "It brings together unrelated programs, components and data streams in a single architecture allowing for unprecedented levels of interconnectivity and cooperation",
    "[...] technology represents both information and relationships among information as objects that may be repurposed to new configurations of systems and system behavior",
    "[...] environment is 'agnostic' ... It takes components, programs and technologies and represents them within itself in a manner that is universal within the GINA environment, allowing for previously unseen levels of interoperability",
    "[...] describe a platform that would encompass a Global Information Grid (GIG) composed of users, the components that they use, and data. Every user, and every component (cell phone, tablet, computer, even traffic cameras) that is modeled in to GINA becomes a multi-dimensional object in cyberspace",
    "[...] emergent capabilities that arise from all of the related components within the executable GINA model are greater than the sum of their individual parts, whether they are new or legacy data systems or sources",
    "[...] different systems is that they speak different languages ... GINA does not require the end systems to be modified to talk to them, GINA is built to understand all of the various data inputs or 'anguages' and then creates links and relationships,"",
    "As technology continues to evolve so rapidly towards ever-greater complexity, so does the programming that makes it work",
    "[...] configured system of systems architecture, not only exposes stove-piped systems in a common, easily understood way, but also uses a universal descriptive metaphor to wire their interactions in a manner that is not only obvious to the user and the developer, but also executable by the computer",
    "GINA universe",
    "[...] incorporates aspects of cryptology into network capability",
    "[...] other initiatives where GINA is a central aspect of the architecture, including interagency emergency response collaboration within Silicon Valley, and an intelligence and information data fusion effort with federal, state and local authorities",
    "[...] allows for the interoperability of unrelated systems and advanced decision matrix databases critical to the kind of operations simulated in the Soaring Angel exercise",
    "[...] simulating timely responses to encounters with insurgents",
    "[...] massive mission critical database, with the ability to access information must faster than separate stove-piped systems",
    "Techniques such as game theory can be incorporated into GINA models in order to establish a Nash Equilibrium, or optimal course of action, for everything from enemy actions to mission success and morale",
    "[...] make sense, of unique data streams",
    "[...] enhances the cognitive toolset for the decision maker",
    "[...] enables cognitive enhancement", and
    "[...] models can also be built within GINA to answer cognitive questions about weapons systems or approaches to specific problems within the GINA environment".

    Comment:
    Around the year 2005 and again around the year 2011, they found out what we have truly created with our Evoos and our OS.
    Note the use of all the explanations and the new interpretations of the GINA related to multi-dimensionality, cyberspace, universe, cognition, and Question Answering (QA), to continue with stealing the original and unique, personal expressions of our Evoos and OS, as it is proven by a comparison with the content of the patent application quoted above.

    We quote the document titled "Better Visibility for Border Security " and publicated on the 1st of February 2013:
    "[...] system of systems that draws in information from many stovepiped sources regardless of their coding or programming",
    "[...] hybrid methodology that leverages model-based architecture and component-based development",
    "System Interoperability for Enabling Smart Mobile System Services in Network Decision Support Systems",
    "[...] facilitates extremely rapid development of information, analytical/computational modeling and decision-support systems using model-driven architecture in concert with executable component-based structures that circumvent the need for code generation",
    "[...] creating a semantic model of behavior which in turn permits maximum flexibility to accommodate technology and mission changes over the course of development",
    "[...] reflexive, executable, component-based, platform agnostic, model-driven architecture, which provides data and information required by the requisite services for smart mobile systems",
    "[...] assist with issues such as camera and ground-sensor management",
    "[...] allows users to homogenize and create semantic models of all the information",
    "Real-time models increase the situational awareness [...]", and
    "[...] new information technology that can change the end game for large systems that have all failed to date".

    Comment:
    A brain works also in this way by drawing in signals from many sources regardless of their structuring or functioning, and a brain-like system, specifically our Evoos, has the ability to draw in information from many sources regardless of their coding or programming.
    A brain works also in this way by always working, executing, thinking, and modelling.

    We quote the document titled "A dream for GINA: new intelligence technology is being incorporated into warfighting, homeland security, and emergency management missions" and publicated in September or October 2012:
    "[...] gain precise situational awareness, rather than accessing huge chunks of intelligence and manually analyzing it [...]", and
    "[...] mapping predictive organizational behavior [...]".

    Comment:
    There were no gain in situational awareness and no predictive whatsoever in GIA and GINA at all.

    We quote the document titled "Army researchers demonstrate next-generation information integration platform" and publicated on the 25th of September 2019:
    "[...] sensor systems integration to support command and control, or C2, common operating picture technologies needed for decision support",
    "[...] individual component of a broader ARL technology package aimed at facilitating both C2 systems interoperability and processing of Internet of Things data at the network edge -- and applied toward ingest and processing of data from a collection of commercial IoT sensors operating under a set of use cases, including perimeter monitoring of installations and vehicle tracking",
    "Data from the IoT sensors was transmitted using long-range wide area network",
    "GINA software was installed and run on a virtual machine hosted on an ARL server",
    "Once ingested and processed by GINA, IoT data derived from the LoRaWAN gateway would be forwarded to the RaptorX common operating picture software for review by the staff located remotely at Fort Hamilton, New York -- communications between the mobile TOC and Fort Hamilton were facilitated through LTE-based connectivity",
    "GINA's core capabilities for networking, data integration and system interoperability using commercial IoT sensor technologies assembled and tested in-house and sensor data generated by other sensing technologies brought to the event by collaborating groups [Our OntoCore (OC) software component is a capability-based system for everything.]",
    "[...] able to relay successfully the LoRaWAN-based data to RaptorX, a military geographic information system designed to support visualization of real-time sensor feeds to support real-time review of the IoT",
    "[...] creators of the GINA technology",
    "[...] unique technology",
    "[...] extensible integration and interoperability, as well as unique capabilities for contextual, causal and behavioral analytics represents a game-changer as we seek to advance joint efforts to integrate and leverage new Artificial Intelligence technologies to solve our future 'hard problems'",
    "[...] unique methodology for integration, orchestration, and cognitive model-execution for decision support models", and
    "[...] data analytics extensions, as well as integration of multiple heterogeneous data streams through simulated tactical scenarios".

    Comment:
    The field of Cyber-Physical System (CPS) and Networked Embedded System (NES) were no topics and focus at all, and only some few rudimentary connections to the field of Ubiquitous Computing (UbiC) and Internet of Things (IoT) (RFID) existed.
    The fields of Business Intelligence (BI), Visualization, and Analytics (BIVA), and Data Science and Analytics (DSA) were also no topics and focus at all.

    All these features of GINA listed above did not exist before the publicaton of our OS to give some few but already sufficient examples.
    We also have shown that GINA is only

  • a utilization of the foundations of our Evoos for business processes and web services and
  • online information "technology [that] was designed to facilitate integration of diverse systems through a collection of intuitive web-based user interfaces, which works with Data Access Layers (DALs) such as for example SOAP Web Services and ODBC interfaces".

    Some missing items and fields not covered by stolen art, which were also listed in relation to the other cases of investigations (see also the Clarification or Investigations::Multimedia, AI and KM of the 10th of October 2020):

  • {correct ?! only modeling of business processes and information systems and database management systems} no Service-Oriented technologies (SOx),
  • no graph-based processing in particular and hypergraph-based approach in general,
  • no SoftBionics (SB), specifically cognitive architecture and particularly brain-like operating system or operating environment,
  • no intelligent architecture as the successor of the integrated executable architecture, which is tried to steal since around 2011 (see the quotes above),
  • no Semantic (World Wide) Web (SWWW),
  • no Grid, Cloud, Edge, and Fog Computing,
  • no blackboard systems,
  • no Mediated Reality (MR), specifically AR, VR, and MR,
  • no Caliber/Calibre and New Reality (NR),
  • no validated and verified computing,
  • no blockchain-based and no Distributed Ledger Technology (DLT),
  • no TOGAF, DoDaf, and NAF,
  • no wearable computing,
  • no Data Science and Analytics (DSA), including
    • statistical learning and analysis,
    • data mining,
    • Big Data Fusion (BDF),
    • Big Data Processing (BDP), and
    • Big Data Analytics (BDA),
  • no this, no that, nix, nada, nothing.

    But only

  • Object-Oriented (OO 1) and ontology-based paradigms, and the combination of both to Ontology-Oriented (OO 2) paradigm,
  • model-based architecture,
  • component-based development,
  • business processes,
  • web services,
  • SOx and Semantic SOx,
  • utility computing and grid computing of the first generation,
  • and so on.

    But

  • reflective,
  • operating system-level (including virtualization),
  • cognitive (including parts of for example Semantic SOx and Cognitive Grid),
  • foundations of SDN-NFV-VNF-CNF, mSOA, network slicing,
  • and so on

    already come from our Evoos and one can see now how they tried to steal it.

    It is about the Global Information Grid (GIG), the LandWarNet (LWN) respectively the Future Combat Systems (FCS) Brigade Combat Team (BCT) Network, and the Systems Of Systems Common Operating Environment (SOSCOE), which was merely another vision besides CALO and PAL based on spying out our research and development activities at that time.
    But we also found out very quickly that they had no clue what to do ("Between 1995 and 2009, $32 billion was expended on programs such as this [FCS], with little to show for it.") and in case they knew what to do then they had no clue how to do it (document titled "Global Information Grid (GIG) Overarching Policy" and publicated 2002).
    We also noted that they could not get around our Evoos.
    We also saw directly, that the operational foundation, Mediated Reality (MedR) (e.g. AR, VR, and MR), and much of SB were missing with everything including Internet, WWW, SOx, Ubiquitous Computing (UbiC) (e.g. IoT), grid computing, SWWW, GIG, and so much more. The simple solution is the OS based on Evoos.
    Also interesting is the fact, that some patents were filed in June 2006, but then nothing happened until around November 2009, and again around the years 2011 and 2019. Obviously, we gave them nothing more to steal.

    Keep in mind that our brain-like Evolutionary operating system (Evoos) is from December 1999 and

  • Object-Relational (OR) DataBase Management Systems (ORDBMSs),
  • executable models for (reflective) (object-oriented) (concurrent) programming, (kernel-less) language systems, (reflective) real-time systems, and distributed environments even with linguistic symbiosis (see the documents titled "Representing and Executing Real-time Systems" and "Executable Specifications for Concurrent Programming" and listed in the section Formal Modeling of the webpage Links to Software of the websites of OntoLinux, as well as the document "RbCl: A Reflective Object-Oriented Concurrent Language without Run-time Kernel" and listed in the section Exotic Operating System of the same webpage),
  • executable extensions of software modeling languages, such as the Unified Modeling Language (UML) called correspondingly executable UML (xUML) (see the book titled "Executable UML: A Foundation for Model-Driven Architecture" and publicated in the year 2002 and also the document titled "AUML - Agent-based Unified Modeling Language" and listed in the section Formal Modeling of the webpage Links to Software of the websites of OntoLinux),
  • eXtensible Markup Language (XML) processing engines and Virtual Machines (VMs),
  • Multi-Agent Systems (MASs),
  • Polygon(al)-Data[bank] Model (see the patent numbered WO9715015A2, titled "Information system and process for storing data therein", and listed in the section Semantic File/Storage System of the webpage Links to Software of the websites of OntoLinux),
  • faceted and integrated information systems (see for example ARchitektur integrierter InformationsSysteme==ARchitecture of integrated Information Systems (ARIS), which even emerged once again in relation to the The Open Group Architecture Framework (TOGAF), Department of Defense Architecture Framework (DoDAF), and North Atlantic Treaty Organization (NATO) Architecture Framework (NAF) due to our OS),
  • ontology-based systems for data mediation and integration (see the documents of the project titled Mediation of Information using XML (MIX) and listed in the section Symbolic Artificial Intelligence (AI 1) of the webpage Literature of the website of OntoLinux and keep in mind that RDF and OWL are XMLs and the topic is exhaustively researched and developed),
  • Operations Management (OM), including Business Process Management (BPM) and Workflow Management (WfM) systems,
  • Product Lifecycle Management (PLM), including Systems Engineering (SE) and Computer-Aided technologies (CAx), including Computer-Aided Software Engineering (CASE) tools, and
  • Problem Solving Environments (PSEs),

    existed all before GINA. See the webpages Overview and Links to Software of the website of OntoLinux for the referenced fields and most of the referenced works.
    This means, that

  • our OS is not based on GINA at all and
  • all patents related to GINA seem to be void.

    Furthermore, since the October 2006 the fake companies Xslent and Big Kahuna Technologies together with the U.S.DoD are trying to reinterpret that NABDBMS and GIA as GINA by taking our Ontologic System (OS) and in this way our Evoos as source of inspiration and blueprint once again. This constitutes multiple infringements of the rights of C.S. and our corporation, specifically the infringement of our copyright for the original and unique expressions of our Evoos and our OS, that are addressed verses to GINA.
    In fact, there was not much.

    The situation is the same like in the cases of for example

  • Cognitive Grid (see the Website review of the 23rd of August 2017, and the Clarification and the Investigations::Multimedia, AI and KM of the 22nd, 23rd, 24th, and 28th of August 2017),
  • operating system-level virtualization or containerization (see Clarification of the ... and Investigations:: ... of the ...),
  • Service-Oriented technologies
    • microService-Oriented Architecture (mSOA) (see the Clarification of the ... and Investigations:: ... of the ...),
    • Service-Oriented Programming (e.g. SORCER) (see the Clarification of the ... and Investigations:: ... of the ...),
    • Service-Oriented Infrastructure (SOI) (see the Clarification or Investigations::Multimedia, AI and KM of the 10th of October 2020),
    • service orchestration (see the Clarification of the ... and Investigations:: ... of the ...),
  • Resource-Oriented Computing (ROC) paradigm (see the Clarification of the ... and Investigations:: ... of the ...),
  • Software-Defined technologies (SDx) (see the Clarification of the 14th of August 2020 and the issue SOPR #297 of the 14th of August 2020 (same day))
    • Software-Defined Networking (SDN), SD-WAN, ...,
    • Network Function Virtualization (NFV) and Virtualized Network Function (VNF),
    • Cloud-native Network Function (CNF),
    • Software-Defined Infrastructure (SDI),
  • Grid, Cloud, Edge, and Fog Computing (GCEFC) (see the Clarification of the January 2020,
  • 5G Next Generation (5G NG) (see the Clarification of the 20th of August 2020 and Investigations:: ... of the ...),
  • Free and Open Source Software (FOSS) projects (see the Clarification of the ... and Investigations:: ... of the ...),
  • DoDAF, NAF, ... (see the Clarification of the ... and Investigations:: ... of the ...),
  • and so on.

    One can also make the observation that at the same time or in the same periode of time, and without any Teaching, Suggestion, and Motivation (TSM) a NABDMS and an XML processing engine, and also the fields of SOx and grid computing have suddenly become such totally different computing and networking paradigms, technologies (including systems), and environments with GIA and ROC, and also mSOA and SOProgramming, containerization, service orchestration, and cloud computing, which all have the related foundational and characteristic properties of our Evoos. This shows that they all have a common source of inspiration and denominator, as described by others and us with a black hole, but have the foundational and characteristic properties of our Evoos in common respectively taken as blueprint.
    The same holds for the projects GIG (envisioned on the 22nd of September 1999), GIG Enterprise Services (ES), and FCS (document titled "FCS White Paper: Systems Overview" and publicated in April 2008) and also the operational framework NetOps (document titled "Joint Concept of Operations (CONOPS) for Global Information Grid (GIG) NetOps Version 3" and dated 4th of August 2006) and the architecture framework DoDAF, which have suddenly become GIG Enterprise Management (GEM), GIG Net Assurance (GNA), and GIG Content Management (GCM) (document titled "NetOps for the Global Information Grid (GIG)" and dated 19th of December 2008), and also GIG 2.0, Joint Enterprise Defense Infrastructure (JEDI), as well as DoDAF 2.0 based on our OS.
    By the way: The NetOps for GIG is dated December 2008 and the GINA was referenced on a webpage of an online encyclopedia about the subject NetOps in December 2009, which matches our observations, impressions, allegations, and claims documented herein, specifically in relation to the company Big Kahuna Technologies.

    Eventually, no sufficient prior art has been presented in relation to the

  • single fields and technologies, and
  • integration of these single fields and technologies,

    but significant evidence, which

  • shows that our ArtWorks (AWs) and further Intellectual Properties (IPs), specifically our Evoos and our OS, have been taken as sources of inspiration and blueprints multiple times, which again provides the causal links to our AWs and further IPs, and
  • proves their originality and uniqueness.

    One can even see how the responsible entities have tried to present a system, that would not infringe our rights, by presenting nothing related to an operating system, virtual machine, and so on, and only used the term reflexive but not the term reflective.
    But the

  • property of being reflexive is included in the property of being reflective in the context of the fields of logics and mathematics, and has been used as synonym for being reflective in the context of the field of software, and
  • copyright does not know mercy in a case, that shows significant and substantial evidence that a work has been taken as source of inspiration and blueprint in whole or in even the smallest part and without creating a new original and unique expression, and in this way proves a causal link to the original and unique expression of the prior art.

    In the last 10 months, we

  • found out that much more entities have stolen our Evoos and our research and development work for our OS, which is the successor of our Evoos, in whole or in part in the years 2000 to 2006, and the same and other entities are trying to take those stolen intellectual properties to steal our OS in whole or in part since the end of October 2006 (see once again the referenced Clarifications and Investigations above), and
  • realized that our Evoos is much more profound for many technologies and fields, including
    • computing and networking in general, and
    • operating system (os or OpS), Information System (IS), what is wrongly called Grid, Cloud, Edge, and Fog Computing (GCEFC), and so on in particular.

    If a federal entity wants to perform and reproduce our OS, including our Evoos and our Ontoscope, then it has to sign our out-of-court agreement, which demands to

  • clearly acknowledge that our OS is the original and unique work of art, but nothing else, such as for example GIA and GINA,
  • remove all infringing matter or handover every IP, such as for example the patents related to GIA and GINA, and
  • establish joint ventures with our Society for Ontological Performance and Reproduction (SOPR) and other business units of our corporation exclusively, but not with another entity, such as for example software manufacturers and service providers.


    03.November.2020

    Ontonics Further steps

    We have designed another variant of one of our electric energy storage devices, which might be more advantageous in practice than other variants.


    04.November.2020

    Ontonics Further steps

    We have developed another variant of one of our electric energy storage devices, which is highly interesting and elegant, might be more advantageous in practice than other variants, and has the potential to become a standard in related fields.


    06.November.2020

    Ontonics Further steps

    We have improved a subsystem to make an overall system (much) more effective.


    09.November.2020

    Ontonics Further steps

    We do have to apologize for inflicting some confusion, when we made the statement in the issue Ontonics Superstructure #23 of the 19th of October 2020 that "fusion energy [...] will be added when it is ready in 5 years", because it also reflects the running gag in this technological field that the realization of fusion-based power generation is always said to be only 5 years away.
    But in fact, we wanted to say that our fusion-based technologies and their various utilizations will be ready for the market introduction in 5 years, because they are already here since more than 3 years, as our latest review confirmed once again, which also confirmed their effectivity, including cost effectiveness, efficiency, safety, and scalabiltiy.

    Due to this state of maturity we also founded our new Society for Fusion Utilization and Generation (SFUG) (see the related issue SFUG #1 of today below).
    Entities, specifically governments and industrial companies, have to

  • sign our out-of-court agreement and further legally binding agreements and contracts included in our set of rules,
  • become members and licensees of at least one of our societies for controlling and managing the performance and reproduction of the ArtWorks (AWs) and further Intellectual Properties (IPs) included in the oeuvre of C.S. and the legal scope of our corporation, and
  • comply with the core regulations of the Articles of Association (AoA) and the Terms of Services (ToS) with the License Model (LM), that are common to all of our societies

    to be eligible for legal utilization of any AWs and further IPs included in the oeuvre of C.S. and the legal scope of our corporation.

    Also note, that we

  • have made some of the technologies of our societies
    • Superunicorns™ of our OntoLab Vision Funds™ and
    • Superbolts™ of our Blitz Funds™

    set up and managed by our HighTech Office Ontonics, and

  • will begin with the introduction of our electric energy storage technologies and the related infrastructure as a test. If an entity fails this test, then it is out in relation to the
    • utilization of our fusion-based technologies in particular and
    • performance and reproduction of the oeuvre of C.S. in general.

    Society for Fusion Utilization and Generation (SFUG) #1

    We are pleased to announce the start of our collecting and managing society titled Society for Fusion Utilization and Generation (SFUG) for handling the the work of art series fusion power and the included artworks based on fusion, as well as controlling and managing their performance and reproduction as fusion-based technologies, goods, and services.

    Ontonics Superstructure #24

    Our Weather Control System (WCS) is a

  • highly integrated solution, which is composed of several single solutions, but also
  • single solution of a larger overall integrated solution itself, which is also utilized for our climate change reversal.

    Further single solutions are the

  • integration of the WCS with our Hover Transport System (see the issue Ontonics Superstructure #13 of the 5th of August 2017) of our
    • Hoverland and
    • Hovercity,

    and

  • structure or network of larger WC stations as basic elements, which were discussed and shown in the issue Ontonics Superstructure #23 of the 19th of October 2020.

    In the last past, we already focused on another single solution as well, which is also some kind of a grid, structure, or network comprising WC stations as basic elements, but pursues several different goals and accordingly has different related properties and functionalities and also smaller dimensions.

    For sure, when realizing our Weather Control System (WCS), then the urgency and the efficiency are main factors to be considered, but also the locations, the economics, and the many other aspects, which are external to these activities.
    At this planning stage, we had to focus on details of this smaller single solution related to its

  • properties and functionalities,
  • integration in said larger overall integrated solution, and
  • designs of the single WC stations to match the local environments, because we do not want something like for example that wind mill asparagus, which disfigures the environment (see how ugly such a wind farm looks like for example on Maui and Big Island in Hawaii or at various places in California, both U.S.America) and annoys the immediate neighbourhood and natural environment with the rotating drop shadow and the permanent subliminal noise.

    Like with other parts of our WCS, we estimated that each WC station costs around 2 million U.S. Dollar without the other parts and the first deployment should comprise 10000 WC stations of this type as initial contingent for a total of 20 billion U.S. Dollar, and increase the number to 100000 stations for a total of 200 billion U.S. Dollar.

    Style of Speed Further steps

    We reviewed our propulsion systems based on our real fusion reactor, specifically our highly performant and efficient real

  • fusion propulsion systems, including
    • fusion rocket engines, incuding
      • conventional rocket engines,
      • air-augmented rocket engines, and
      • air-breathing rocket engines,

      and

    • fusion-electric propulsion systems,

    and

  • Fusion-Based Combined Cycle (FBCC) propulsion systems, combining our
    • fusion rocket engines,
    • plasma jets,
    • plasma propulsion engines, and
    • ion drives.

    The question is now if we already install one of these fusion-based propulsion systems in our first spaceship in addition to our Hover technologies for Vertical Take-Off and Landing (VTOL) capability or not. Why not? :D


    10.November.2020

    Ontonics Further steps

    We looked at a different variant of a component, which is utilized for one of our technologies or even might be a different basic variant of it and seems to provide a superior performance for specific areas of application in comparison to what is respectively was before state of the art.
    We also worked on the improvement of systems based on this technology and this component, which showed to be more crucial and complex.


    13.November.2020


    15.November.2020


    16.November.2020

    Ontonics Superstructure #25

    In the following, we give a summary about the layers or spaces and their altitude classifications of our Superstructure:

  • solar system platform stations
  • 180 km and above: space satellites and platform stations with geocentric orbit
    • above 35786 km: High Earth Orbit (HEO) satellites and platform stations
    • 35786 km: Geosynchronous Orbit (GEO) satellites and platform stations
    • 2000 km to 35786 km: Medium Earth Orbit (MEO) satellites and platform stations
    • 450 to 2000 km: Low Earth Orbit (LEO) satellites and platform stations
    • 180 to 450 km: Very Low Earth Orbit (VLEO) satellites and platform stations
  • 17 to 180 km: atmospheric satellites and platform stations
    • 40 to 180 km: High-Altitude Pseudo-Satellites or High-Altitude Platform Stations (HAPSs)
    • 17 over 22 to 40 km: Hover Stations and Medium -Altitude Pseudo-Satellites or Medium-Altitude Platform Stations (MAPSs)
  • 0 over 1 to 5 km: land and see surface platform stations and Hover Stations
    • 0 to 5000 m: Hover Stations and Low-Altitude Pseudo-Satellites or Low-Altitude Platform Stations (LAPSs)
    • 0 to 1000 m: Weather Control (WC) base stations
  • below 0 m: undersea platform stations

    Obviously, our Superstructure is a computer-, network-, data-, information-, and leader-centric and -enabled technology with a Network Operations (NetOps) operational framework, which provides Situational Awareness (SA), and Command and Control (C2), Communication, and Computer and Intelligence (C4I), and also as a Service (aaS) capability models and operational models, and many other properties, functionalities, and benefits. The latter shows once again that its foundation is our Ontologic System (OS) (see also the section Legal matter [Infrastructure] of the issue SOPR #300 of the 10th of September 2020).

    We also made some calculations related to the grid, structure, or network of Weather Control (WC) stations, which are of the smaller type and are arranged in a grid of

  • squares with an edge length of 10 kilometers or an area of 100 square kilometers, or
  • hexagons with an edge length of 10 kilometers or an area of 259.8 square kilometers.

    If the grid, structure, or network is arranged in squares, then one requires around

  • 98000 stations to cover the entire land surface of the USA (9833520 km²) and
  • 102000 stations to cover the entire land surface of the European continent (10180000 km²).

    In this case we would need 200000 stations of this type and not the 100000 stations, as estimated before.
    In this relation, we also have to note that in some areas such a dense arrangement is not needed (e.g. high mountain ranges), while in some other areas a denser arrangement is needed (e.g. urban areas).

    If the grid, structure, or network is arranged in hexagons, then one requires around

  • 37850 in case of the U.S.A. and
  • 39184 in case of the European continent.

    In this case we would have more than 20000 stations of the estimated 100000 stations left for areas, which need a higher density, and also a match with our OntoGlobe and OntoEarth software components (see the OntoLix and OntoLinux Website update of the 21st of August 2017 and also the issues Ontonics Superstructure #13 of the 7th of August 2017 and #16 of the 15th of August 2017 referenced therein).

    Furthermore, other parts of our 3D infrastructure Superstructure should be able to compensate reduced features and functionalities in areas with a thinner arrangement or for other local reasons.

    Join the bright side of the force. Become a member of our societies, associations, and team of winners.


    17.November.2020

    Ontonics Further steps

    In case that antitrust actions of the company Facebook, we would like to express our interest for the takeover of it subsidiary Instagram and make our usual takeover bid about

  • its market capitalization on the 1st of January 2015 plus
  • 10 years of the annual profit the company made in the year 2019,

    with

  • 33.3% payed in cash after the payment of the overall damage compensations, admission fees, and outstanding royalties of the company Facebook and
  • 66.7% offset with the overall damage compensations, admission fees, and outstanding royalties of the company Facebook. :)

    Though the companies Twitter and Snapchat are first in the queue of potential takeovers.

    In case of the aerospace company The Boeing Company we got no clear signal and for sure no definite commitment in relation to a (potential) takeover of it by a business division of our corporation, but instead we got the impression of a negative attitude on the part of its management.
    To make the situation crystal clear: Boeing

  • has been ditched and dumped in the last years by its former management,
  • is worth 1 U.S. Dollar plus 10 years of the annual profit it made before the scandal with its airliner model 737 Max happened,
  • has to be rescued by a very expensive rebuilding, and
  • will not avoid to use our ArtWorks (AWs) and further Intellectual Properties (IPs), and become a member of our related societies, but
  • shows a certain lack of understanding for this situation by its management.

    Due to these reasons we have developed highly interesting and effective alternatives, which means we have the options to

  • clean up that mess and restore Boeing, or
  • build up something new, which might be less expensive and more effective.


    18.November.2020

    21:34, 22:19 and 23:55 UTC+1
    Ontonics Further steps

    After several state and federal governments have set due dates, from when the sale of automobiles without an electrified propulsion system is banned and also excluded any innovations in other Clean and Green™ systems in this way, it should be no magic to predict that the number of electric and hybrid cars will increase correspondingly.
    But a situation is emerging in the U.S.America, U.K., member states of the European Union, and other countries, in which electromobility is doomed to fail without hightech, because

  • sufficiently many recharging points and sufficiently dimensioned power grid infrastructures are not yet existing and
  • improvements of this situation will not happen as much as required, specifically not on the basis of truly renewable energy sources.

    We anticipated and solved this problem with our new electric energy storage technologies as well, for example with our related

  • infrastructure
  • technologies, including battery exchange or swapping systems, platforms, and services, and
  • open and internationally standardized battery form factors,

    whose use is essential for

  • performing and reproducing our original and unique works of art created by C.S. and
  • having success in the field of electromobility.

    But we also anticipated and solved another huge known problem with all ordinary batteries. We quote a related report: "How long does the battery last?
    Once again, this depends on how you look after it.
    Most electric car batteries are lithium-based, just like the battery in your mobile phone Ontoscope. Like your phone Ontoscope battery, the one in your car will degrade over time. What that means is it won't hold the charge for so long and the range will reduce."
    This means that after 4 years the range will inevitably reduce and after 10 years such batteries are electric waste or electroscrap.
    Indeed, some magic has been announced in relation to a battery configuration, that lasts 1 million miles by one battery manufacturer and two automobile manufacturers, but this more durable battery configuration lacks increased capacity, or being precise specific energy with around 260 to 360 Wh/kg and has to prove its quantities and qualities in practice at first.
    But with our electric energy storage technology there is neither such a degradation nor a problem with waste and recycling at all.


    20.November.2020

    19:36 and 19:42 UTC+1
    Ontonics Further steps

    In relation to one of our technologies we have created a foundational concept and a related conceptual model, but not a design.
    We also made several improvements to this concept and its conceptual model (see for example the Further steps of the 22nd of August 2015 and 22nd of November 2017). But only by happenstance we made a step concering this improvement today that resulted not only in one of the potential designs of this technology, but also in a highly elegant foundational design and various variants of it.
    Even better, we are also working on scaling up and down our technology. Specifically the downsizing is particularly interesting and fascinating, because it would allow relatively small versions, which experts, who all still have problems with the basics of this technology, consider such a realization impossible.

    We also added another component to the conceptual model, but this might exclude another component and therefore would result in a new conceptually model.
    Despite that we might have 2 different working designs and sysetes, which taken alone are both revolutionary, it would be even more advantageous, if both components could be integrated in one thing.

    While writing this message, we also made two improvements to two other technologies, which should increase their efficiency and performance.

    We love it to observe when things begin to move, run, improve, and evolve.


    21.November.2020

    King Smiley Further steps

    Out of interest, we have looked at the Santa Maria degli Angeli complex on the 15th of November 2020 and today. As we said before, the inclusion of the church and the second cloister is obvious, as is the case with some of the other buildings. But a look at its floor plan shows that the first and thrid cloisters, virtually the whole second connecting building between the first and third cloisters, the end section of a first connecting building in the proximity of the rotonda, and the building between the second cloister and the rotonda are not included.
    But we would like to get the whole building complex even if we would have to construct a new building complex at another location as replacement for the current users or tenants, for example the university.


    24.November.2020

    OntoLab Further steps

    What a success once again: Our OntoLab is now the undeniable #1 research laboratory worldwide without copying and stealing like the rest.

    The first seven OntoLab derivates have been founded with an Institute for Artificial Intelligence and Fundamental Interactions at the Massachusetts Institue of Technology, Massachusetts, U.S.America, and with 6 other institutes as part of an effort and with the support of the National Science Foundation and the U.S.American Department of Agriculture.

    Today we got undeniable evidences proving that our original and unique Caliber/Calibre included in our Ontologic System (OS) and connected to the fields of

  • Algorithmic Information Theory (AIT),
  • conventional and quantum computing, and also
  • SoftBionics (SB)

    (see also our Evolutionary operating system (Evoos) described in The Proposal and included in our (OS)), as well as our original and unique

  • Bridge from Natural Intelligence to Artificial Intelligence

    is becoming or already has become the accepted Theory of Everything (ToE).

    We have nothing less expected otherwise.

    By the way:

  • There is much or even much too much that humans do not understand.
  • Our OS with the Caliber/Calibre is neither new (more than 16 years old) nor a field (in contrast to Ontonics), but a work of art and has to be called by our titles and designations, and referenced properly.
  • See also the issue SOPR #307 of the 24th of November 2020 (today) about the introduction of our new Theory of Everything System (ToES) of the exclusive infrastructure of our Society for Ontological Performance and Reproduction (SOPR).

    05:00, 14:55, 17:38, and 18:37 UTC+2
    SOPR #307

    *** Sketching mode ***
    Topics

    This issue is a summary of aufgearbeiteter notes publicated in the last days and some more information related to the following topics:

  • Legal matter [Antitrust]
  • Legal matter [Blacklist]
  • Legal matter [Licensing of further Intellectual Properties (IPs)]
  • Digital rights [Data protection and data security] (13th of November 2020)
  • Infrastructure
  • IDentity and Access Management System (IDAMS)
  • Electronic Government [Digital citizen account]
  • Electronic Government [Digital election]
  • Social and Societal System (SSS)
  • OFinS [Currencies] (Bitcoin and Co. are illegal (18th of November 2020))
  • Theory of Everything System (ToES)

    Legal matter [Antitrust]
    Any change of an antitrust law give us the right and opportunity to renegotiate the terms and conditions of the related legal matter, specifically

  • the out-of-court agreement with the damage compensations of C.S. and our corporation, and
  • the Articles of Association (AoA) and the Terms of Services (ToS) with the License Model (LM) of our Society for Ontological Performance and Reproduction (SOPR).

    Legal matter [Blacklist]
    We noticed that contracts of companies include a non-compete clause, which lists restricted parties with which a business partner is not allowed to do business.
    In fact, we thought about such a list and put every entity on it, that performs and reproduces our AWs and further IPs, but refuses to sign our out-of-court agreement and become a member and licensee of our SOPR. But we we have discarded this possibility, because we thought such an action would be illegal, specifically for a large company or another entity with a certain market power.

    Legal matter [Licensing of further Intellectual Properties (IPs)]
    {This is a temporary section for the readers interested in this matter.}
    In the issue #306 of the 26th of October 2020 we are short of finishing this topic. Important to note are the

  • addition of the aspect of shift of rights for AWs and further IPs,
  • alignment of the regulations in regard to this shift of rights,
  • finishing regulations
  • ...

    Digital rights [Data protection and data security]
    We would like to give the recommendations to

  • not scrutinize or question cryptography and
  • not demand a master key

    in case of data protection or privacy, and data security, because it is already sufficiently simple for law enforcement to get access.

    We would also like to make the suggestions
    as more personal the information as more increased legal requirements and regulations
    as more often request for personal information as more increased legal requirements

    {please note only ideation here}
    As always said, we use both centralized and decentralized approaches, concepts, and solutions.
    data have been collected, are being collected, and will be collect
    keep the data storages separated
    on the individual device respectively Ontoscope and cybernetical extension, extended brain of a user

    We will look on the solutions of the countries Danish, Finish, and other countries, the ontologies, and the data models, and provide a general solution as part of the related subsystems and platforms, applications, and services of the infrastructure of our SOPR.

    Infrastructure
    Obviously, our Ontologic System is also a computer-, network-, data-, information-, and leader-centric and -enabled technology with a Network Operations (NetOps) operational framework, which provides Situational Awareness (SA), and Command and Control (C2), Communication, and Computer and Intelligence (C4I), and also as a Service (aaS) capability models and operational models, and many other properties, functionalities, and benefits (see the section Legal matter [Infrastructure] of the issue SOPR #300 of the 10th of September 2020 and also issue Ontonics Superstructure #25 of the 16th of November 2020).
    For non-experts we would like to give the explanation that we have built at least the Global Information Grid (GIG) 2.0 and 3.0, which include the LandWarNet (LWN) respectively the Future Combat Systems (FCS) network and its successor the Brigade Combot Team (BCT) Modernization program as the combination of what is on top and inside of the GIG's inner cylinder, of the United States Department of Defence (USDoD) and the United States Armed Forces, specifically the United States Navy and the United States Army, as part of our Ontologic System.
    But more importantly to note is the point that we adapted the military goals, uses, and benefits for the civil goals, uses, and benefits.

    The FCS BCT integrated network is structured in the 5 layers

  • sensors (C2 Constellation, platforms and effectors (Forcenet)),
  • applications (command) (business applications, etc.),
  • services (System-of-Systems Common Operating Environment (SoSCOE)),
  • transport (telecommunications) (infrastructure), and
  • standards

    and is able to process, secure, and exchange information via the GIG across all echelons, which in case of our OS are the 6 rings and related ID spaces and universes of the management hypergraph structure of our ON, OW, and OV.

    We also added

  • SoftBionics (SB), including
    • AI,
    • ML,
    • CV,
    • CAS,
    • etc.,
  • ontologies
  • Evolutionary operating system (Evoos),
  • validated and verified, including
    • smart contract technique,
    • blockchain technique, and ,
    • Distributed Ledger Technology (DLT),
    • etc.,
  • frameworks, including for example
    • operational SoftBionic NetOps,
    • developmental SoftBionic DevOps,
    • transportational SoftBionic Service Operations (ServOps),
    • etc.,
  • etc.

    with our Ontologic System (OS) and our Ontoscope (Os), and also our further Intellectual Properties (IPs).
    Correspondingly, the infrastructure of our SOPR includes related facilities, subysystems and platforms, goods, and services, such as for example the

  • IDentity and Access Management System (IDAMS),
  • Collaboration and Communication System (Co²S or CoCoS) infrastructure (e.g. 5G Next Generation (5G NG), related parts of ON, OW, and OV respectively Ontologic Computing (OC), also wrongly know as (awka) Grid, Cloud, Edge, Fog Computing (GCEFC)),
  • Superstructure,
  • Traffic Management System (TMS), Next Generation Transportation System (NextGen), and Unmanned System Traffic Management (UTM) System (UTMS) for land, air, water, and space, such as for example
    • Air Traffic Management (ATM) System (ATMS),
    • Air Traffic Control (ATC) System (ATCS),
    • Airline Operational Control (AOC) System (AOCS),
    • L-band Digital Aeronautical Communications System (LDACS),
    • Unmanned Aircraft System (UAS) Traffic Management (UTM) System (UTMS),
  • and much more.

    IDentity and Access Management System (IDAMS)
    In the last days, one of the 26 member airlines of the Star Alliance global airline alliance has introduced the IDentity and Access Management System (IDAMS) with biometric functionalities like for example biometric authentication as a form of identification and access control of the alliance, which is called Star Alliance Biometrics.

    For data protection reasons, the IDAMS of Star Alliance is separated from the IDAMS of the federal border control and it is not intended to connect both systems. But the IDAMS of Star Alliance will also be used for security checks at airports, among other things, and these are mandatory by law.
    The latter also shows that the airlines and airports are conducting federal tasks in a public environment.

    If an entity wants to operate an own public IDentity and Access Management System (IDAMS), then it has to do this on its own premises with an own network (e.g. Virtual Private Network (VPN)) respectively with on-premises software, but without an external Grid, Cloud, Edge, and Fog Computing (GCEFC) provider or other service provider, specifically without off-premises software. Otherwise, the use of our IDAMS of our Society for Ontological Performance and Reproduction (SOPR) is mandatory.
    The latter does not mean that IDAMSubsystems are connected.

    Furthermore, if our Ontologic System Components (OSC) and Ontoscope Components (OsC), and Ontologic Applications and Ontologic Services (OAOS) are performed and reproduced, then the

  • unrestricted access to raw signals and data for our SOPR, and
  • exclusive trade of raw signals and data, informations, knowledge, models, and algorithms on the Marketplace for Everything (MfE) of our SOPR,

    are mandatory.

    Electronic Government [Digital citizen account]
    The subject matter was also discussed in the section Digital rights [Blanket data retention] of the issue #305 of the 18th of October 2020
    We looked at various services of public authorities, that are connected with a digital citizen account, such as for example the

  • digital pension account==digitales Vorsorgekonto
  • ELectronic Consideration Verification procedure, also ELectronic Income CErtificate (ELICE) procedure==ELektronisches EntgeltNAchweis-Verfahren, auch ELektronischer EinkommensNAchweis (ELENA)
    With the ELICE procedure (original term JobCard) in F.R.Germany, the income certificate or proof of income was originally to be provided electronically using a chip card and electronic signature from 2012. In 2014, the Federal Employment Agency introduced the less extensive successor system Accepting Certificates from employers Electronically==Bescheinigungen von Arbeitgebern Elektronisch Annehmen (BEA). Furthermore, the final report for the Optimized Reporting procedure in the social Security==Optimierte Meldeverfahren in der sozialen Sicherung (OMS) was also presented
  • Accepting Certificates from employers Electronically==Bescheinigungen von Arbeitgebern Elektronisch Annehmen (BEA)
  • Optimized Reporting procedure in the social Security==Optimierte Meldeverfahren in der sozialen Sicherung (OMS)
  • Electronic Wage Tax Deduction Features==Elektronische LohnSteuerAbzugsMerkmale (ELStAM), also electronic wage tax card
  • digital election

    problematic are the

  • data storage or retention,
  • profiling and
  • abuse by the basis of such systems, platforms, applications, and services. For example, PIIs or personal data were retrieved illegally from a computer of the police in a larger police department.

    Essential for all these problems of data protection or privacy, and data security is always the right to access. Therefore, multilevel, military-graded IDentity and Access Management System (IDAMS) with biometric functionalities like for example biometric authentication as a form of identification and access control for all personnel with rights for data access.

    Electronic Government [Digital election]
    Another field where the digitalization shows substantial solutions, benefits, and advantages for societies, but also foundational problems, deficits, and disadvantages is the conduction of elections.
    Nothing is more urgent in a modern society than making sure elections work, because everything else a government can do depends on that.

    Some general requirements to provide election results everyone can trust in:

  • use of proven and effective approaches, methods, and technologies, including our OS with validation and verification, smart contract and blockchain techniques, our Distributed Ledger Technology (DLT), the IDAMS of our SOPR, and so on outdating paper-based poll books, ballots, and ballot-marking devices
  • standardized voter and election ontologies
  • standardized voter databases,
  • automatic voter registration: If an eligible citizen has an interaction with a government agency, she or he has registered unless she or he has declined, and the records are sent digitally to the registrar.
  • exchange voter data so the records of people who move or die can easily be updated. The National Institute of Standards and Technology has been developing a common data format that would allow registrars in one state to exchange information with those in another state, greatly increasing the integrity of the rolls.
  • easier for states to share data to both reach out to unregistered voters and to keep track of people who move or die so they are not wrongly kept on voter rolls.
  • digital poll books for reducing problematic record-keeping at the polling place and providing quick vote. Electronic or paper poll books are used to check if a voter is registered to vote at a particular location. nationwide use of standardized, secured electronic poll books, {?with a paper backup copy}
  • national standard for their certification and security
  • national standards for handling of email-in ballots {?mail-in ballots}
  • correct counting

    adoption of these standards for registration, data exchange, maintenance

  • keep voters from being incorrectly purged from the rolls
  • remove suspicions of voter fraud
  • easier registration,
  • cleaner, more up-to-date voter rolls
  • maintenance to ensure ineligible voters do not remain on the books and purges of voter rolls are no form of voter suppression anymore
  • sufficient number of voting booths everywhere so nobody has to wait in line for too long
  • easier voting,
  • faster voting,
  • lessen suspicions of fraud and instances of disenfranchisement,
  • faster counting by reducing the need for provisional ballots when a registration is disputed
  • {?optical scanners, which use easy-to-mark paper ballots} that can be processed by the machines for speed or for checking, and easy to audit and do recounts, people can look at them if necessary after the election.
  • {?standard for upgrade of the remaining paper-based ballot-marking devices and replace all electronic-only devices} validation and verification Even with a system that's expected to work well, we need to know that it has worked well. Like any other equipment, paper-based optical-scan counting machines can fail and human error can add to this. That is why risk-limiting audits should be conducted after each election after the counting is complete, but before the result is certified. In such audits, all ballots can be examined and compared with the already reported results. Well-established SoftBionic methods (AI, ML, CV, etc.) allow to spot potential problems, be it errors with machines, human error, manipulation. This helps citizens feel confident that the reported result is what they would get if all ballots were correctly counted. Risk-limiting audits should be a standard final step before certifying elections.

    Social and Societal System (SSS)
    A provider of a social media and short messaging platform proposed that companies should provide a

  • unambigious explanation of their content moderation decisions,
  • straightforward appeals procedure, and
  • ability for consumers to choose the algorithms that serve up social media content.

    We find the proposal quite interesting. While the first two points should be a matter of course for sincere service providers, the third point would even allow a user to select an algorithm for a social media platform individually on the basis of our OS, with its Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV), and in a way similar like it is already done with the so-called cookies of websites.
    Luckily, our SOPR has already prepared everything that is needed with its regulations concerning the

  • digital rights and digital properties of its members and licensees, specifically raw signals and data, informations, knowledge, models, and algorithms,
  • service moderation and brokerage,
  • Society 5.0 Social and Societal System (SSS), and
  • trade of these digital properties on its Marketplace for Everything (MfE).

    By the way, trading raw signals and data, informations, knowledge, models, and algorithms on the MfE is exclusive due to the societal compromise for opening our OS and allowing and licensing the performance and reprodcution of certain parts of our OS, including the foundational hardware and software components, applications, and services, to the worldwide public.

    Theory of Everything System (ToES)
    We added a new subsystem based on our original and unique Caliber/Calibre which

  • is included in our Ontologic System (OS),
  • connected to fields of
    • Algorithmic Information Theory (AIT),
    • classical or conventional computing and quantum computing, and also
    • SoftBionics (SB)

      (see also our Evolutionary operating system (Evoos) described in The Proposal and included in our OS) as well as our original and unique

    • Bridge from Natural Intelligence to Artificial Intelligence

    is becoming or already has become the accepted Theory of Everything (ToE).

    Like with for example digital maps and Mediated Reality (MedR) environments based on our Ontologic System (OS) and our Ontoscope (Os), our new Theory of Everything System (ToES) is the place of authority where related technologies, goods, and services, as well as models and algorithms have to be hooked in and galvanized. Everything else is considered an infringement of our copyright excluively managed and exploited by our SOPR.


    25.November.2020

    Ontonics Further steps

    Due to our many outstanding creations and achievements, we have just forgotten to inform our fans and readers that we had achieved just another breakthrough in a relation to a technology while cleaning up our archive. How can one be so forgetful? :D
    Howsoever, this developmental step

  • allows the elimination of impairments and the construction of fundamently different solutions on the one hand and
  • increases our already significant lead in the related field even much further on the other hand.


    27.November.2020

    Ontonics Further steps

    We developed two variants of a technology and a third variant, which is the integration of the first two ones. The results should be improvements of the initial variant of the related technology.


    29.November.2020

    Ontonics Further steps

    We developed another way of utilization of a technology, which should have some advantages in comparisons to similar technologies utilized in the same way.

    Even more important to note is our further development of these technologies and some related technologies and also our improvements of them to a complete system, which has the potential to start the next revolution of us.


    30.November.2020

    07:20, 09:02, and 21:21 UTC+1
    Ontonics Further steps

    To get a first and very reduced impression about

  • what others and we are talking about and doing, and
  • how ambitious the overall digital plan of the governments truly is by adding a second structure for data governance and much more

    see for example the graphics

  • (Machine to Machine) M2M World of Connected Services - The Internet of Things 2009,
  • Internet of Things Landscape 2018,
  • (Big) Data and AI Landscape 2019,
  • (Financial Technology) FinTech Ecosystem and Financial Technology landscapes,
  • Sales Technology Landscape 2013, and
  • Connected Car landscape.
  •    
     
    © or ® or both
    Christian Stroetmann GmbH
    Disclaimer