The Articles of Association (AoA) and the Terms of Service (ToS) with the License Model (LM) of our Society for Ontological Performance and Reproduction (SOPR) are drafted in such a way that as much as possible or even all of the items spied out, stolen, or copied from us in the last 2 decades will be repatriated, such as for example:

• Autonomic Computing (AC),
• Service ORiented Computing EnviRonment (SORCER), and
• Resource-Oriented Computing (ROC) (e.g. NetKernel),

• Service-Oriented Computing of the first generation (SOC 1.0) (e.g. SORCER) and
• Service-Oriented Computing of the second generation (SOC 2.0) (Service-Oriented Computing of the first generation (SOC 1.0) with Semantic (World Wide) Web (SWWW) standards and technologies, or Semantic Service-Oriented Computing (SSOC), or Service-Oriented Architecture of the first generation (SOA 1.0) with Autonomic Computing (AC) and Semantic (World Wide) Web (SWWW) standards and technologies, or Semantic Service-Oriented Architecture (SSOA) with Autonomic Computing (AC)),

• Industrial Internet of Things (IIoT) and
• Industry 4.0 (including ontologies as well),

In this relation, we also learned over the years that

• multi-cloud,
• dynamic federation,
• service meshing,
• marketplace of applications or app store,
• marketplace of services,
• ...
• continuous integration,
• continuous delivery, and
• continuous deployment,
• DevOps,
• ...

and

Self-evidently, if we cannot prove that an item has been spied out, stolen, or copied from us, then the spied out, stolen, or copied item can be used by entities legally. But there are big ifs and buts.

Once again, we are not regulating or even prohibiting any

as long they are based on prior art or do not show a causal link with our original and unique works of art, but when an entity wants to reproduce or perform our works of art, then we highly appreciate team spirit and team play following our credo "All or nothing at all".

In relation to Ontologic Applications and Ontologic Services (OAOS) and their meshing or combination and integration we have at least four definitions:

We also have three types of meshing or combination and integration of functionalities:

• non-OAOS with non-OAOS not in OS - no limitation and
• non-OAOS with non-OAOS in OS - exclusive SOPR infrastructure,

This covers elegantly the issues with the operating system-level virtualization or containerization, patent portfolios, and so on.

We are afraid to say, but there is virtually no multi-cloud of companioned competitors, as some companies suggested in the last past, because there are not much non-OAOS not in OS and therefore beyond our clear-cut delimitation respectively outside of our umbrella.

As we said in the past:

03.February.2019
Ontonics Further steps
We developed three new materials that together with the new material mentioned in the Further steps #1 of today respectively the 1st of February 2019 constitute a new type of material.

Recently, we also got the knowledge that several materials including all new materials can also be produced by another special technique.

04.February.2019
Website update
We separated the image shown in the Clarification of the 23rd of April 2008 as the Picture of the Day and added the additional informations.

Investigations::Multimedia, AI and KM, Robotics

In relation to the latter, we quote some passages of an online encyclopedia: "Producer David Ellison explains that the title Terminator Genisys "[is] in reference to genesis, which is in reference to the singularity and the man-machine hybrid that John Connor ends up being."[6 [Woerner, Meredith (July 3, 2015). "Why was 'Terminator Genisys' spelled with a 'Y'?"]
[...]
The T-3000 is [...] given the mission to assist Cyberdyne Systems as the company's architect in developing a new operating system named Genisys [...].
[...] T-3000 [...] being made of machine-phase matter (essentially, programmable matter) [...].
It is capable of shapeshifting at much more rapid speed than the mimetic polyalloy Terminators, though it is still limited by complexity or mass; [...].
[...]
Unlike previous Terminators, the T-3000 transforms and regenerates in layers, beginning with its bone structure, then muscle tissue, skin and clothing.
[...]
These aspects, combined with the access the cyborg has to its original human host's memories in addition retaining his or her personality, behavioral traits, and some levels of emotions, the T-3000 can easily convince even those well-versed in tactics used by Terminators that it is actually a human, essentially a machine that thinks like them (see Turing test). [...] It appears to retain the ability to infect others and create more T-3000s [...]. The transformation, which is described as replacing its victim's body on the cellular level, cannot be reversed." and
"The T-5000 [...] has the ability to 'convert' a living organism into a nanorobotic T-3000 Terminator at the cellular level. The new T-3000 Terminator keeps the appearance of its original organic form and retains its host's memories and behavioral characteristics (see posthuman/technological singularity)."

Terminator Genisys is based on our Ontologic System. We leave it to our fans and readers to find the places of the original content on our websites, specifically the websites of OntomaX and OntoLinux. Hint: Begin with the webpages Overview, Caliber/Calibre, and Terms of the 21st Century of the website of our Ontologic System OntoLinux and also the issue SOPR #157 and the OntoLix and OntoLinux Further steps of the 23rd of December 2018.

Quite fascinating, is not it? But now integrate Tron and Terminator for example to get a better impression and understanding of our Ontologic System and Ontoscope.

Eventually, also this plagiarism proves once again that

[...] more undeniable evidences are provided that show once again that our iconic masterpieces of art titled Ontologic System and Ontoscope.
Very interestingly, we do not only see

• Caliber/Calibre,
• New Reality (NR), and
• Ontologic uniVerse (OV), as well as
• OntoBot and OntoScope components

but also get

• said original and unque elements of our Ontologic System and
• the narrative, speculative, not scientific and technical, literary arts, specifically scientific fantasy or science fiction,

that we presented with our Ontologic System as well.

Also interesting to note that the name of the one production company also reflects aspects of C.S.' works. "Annapura [...] is the goddess of food and nourishment in Hinduism [... and] is an avatar (form) of Parvati, the wife of Shiva."
"Parvati or Gauri "is the Hindu goddess of fertility, love, beauty, [purity, energy, creative power,] marriage, children, and devotion; as well as of divine strength and power.[...] She is the Jaganmata (mother of the universe). Known by many other names, she is the gentle and nurturing aspect of the Supreme Hindu goddess Adi Parashakti and one of the central deities of the Goddess-oriented Shakta sect. She is the Mother goddess in Hinduism,[...] and has many attributes and aspects. [...] Along with Lakshmi and Saraswati, she forms the trinity of Hindu goddesses (Tridevi)." "Parvati is the wife of the Hindu god Shiva - the protector, the destroyer (of evil) and regenerator of the universe and all life."

05.February.2019

08:09, 16:18, and 19:33 UTC+1
SOPR #166

*** Work in progress - not sure if sufficient and better wording ***
We would like to discuss a master plan and related further steps. But the problem is that everytime we did this before some entities thought to be clever (not really) and tried to steal something.

Master plan and further steps

• universal ledger (see also the issue SOPR #157 and the OntoLix and OntoLinux Further steps of 23rd of December 2018),
• IDentity and Access Management System (IDAMS), and
• Ontologic Financial System (OFinS),

  followed by the

• Communication and Collaboration (CoCo) system,
• social networking platform,
• societal system without anonymity and monetizing of user data,
• marketplace for everything system, and
• societal marketplace platform with anonymity and without monetizing of personal data

of the SOPR infrastructure (see also the issue #159 of the 31st of December 2018).
The rings and assigned ID spaces of the IDAMS must work together with the namespaces of the individual Intersup nodes, and also the overall ON, OW, and OV.
As far as we can remember and see, virtually everything exists but must be adapted, configured, and integrated as individual core components and as parts of the overall OS. This is a little more difficult and a little less complex.
But very crucial points are the locations of the servers, the governance of these systems, and the vetting of entities. In fact, the latter is a huge problem, as others and we already said and as first failures in some countries already showed, because it does not work as secure as required, as not expected otherwise. We have some first national and international solutions and are working on more solutions, but can already say that getting and keeping an ID is a longer lasting and continuing process.

• systems of the fields of
  • Service-Oriented technologies (SOx),
  • New Reality (NR), including
    • Augmented Reality (AR),
    • Virtual Reality (VR),
    • Mixed Reality (MR),
    • etc.,
  • Cyber-Physical Systems (CPS), Internet of Things (IoT), and Networked Embedded Systems (NES), including
    • Industrial Internet of Things (IIoT) and
    • Industry 4.0,
  • Ubiquitous Computing or Pervasive Computing systems,
  • robotics,
  • mobility technologies, goods, and services,
• Communication and Collaboration (CoCo) systems,
• multi-cloud computing systems, dynamic federation systems, and service meshing systems, as well as
• individual systems, platforms, applications, and services,

so to say as prototype systems or development systems. In this respect, we would like to recall that the Intersup is the interconnected supercomputer and should be operated as for example a (parallel computing) cluster, but not as a grid computing or cloud computing system or similar networking system anymore, which are merely "providing [...] access to distributed, heterogeneous and dynamic [...] computational facilities, applications, visualisation, data and experimental facilities, integrated and accessible as a single resource over the Internet", but are not the Internet itself respectively the Intersup and Ontologic Net (ON). Indeed, the visions of the Grid and the Cloud are already old stuff and their realisation is based on our vision provided with our Evolutionary operating system (Evoos) described in The Proposal and our Ontologic System (OS).

06.February.2019
Comment of the Day
"We are the Singularity.", [C.S., Today]

But we are not the synthetic intelligence Skynet respectively new operating system named Genisys, which takes the form of a cyborg in the movie Terminator Genisys, which is the fifth part of the Terminator saga.
In this respect, we also would like to note that in the image titled "Evidence" also shown on the webpage Caliber/Calibre the figure in the center represents

in respect of

09:00 UTC+1
SOPR #167

*** Work in progress - link to former SOPR issue missing ***
In the past {when and where in which issue?}, we already said that some technologies and related products and services are not licensable. The following is a list of them:

• mind transfer or uploading in general, and
• on the basis of Distributed Systems (DSs) (for example Peer-to-Peer (P2P) and cloud computing platforms) in particular,

• physical worlds or dimensions between
  • microscopic world (for example Quantum Mechanics (QM) and quantum computing) and
  • macroscopic world (for example universum and network of telescopes),

  and

• New Reality (NR) (see for example the Tron saga and the movies titled "Abre Los Ojos==Open Your Eyes" and "Vanilla Sky") between / of

• human and machine DNA bonding,
• changeling, shapeshifter, and transformer,
• self-reconfiguring robotics,
• self-replicating robotics, and
• parionics,

The list might be extended with more list points or examples or both.

The reasons for this exclusivity are the

If an entity touches any of these technologies for economic reasons beyond scientific fantasy or science-fiction, which still is a subject to licensing, then membership in our SOPR will be rejected or withdrawn.
There will be many related economic opportunities but also order.

09.February.2019
Roboticle Further steps

We developed a control system for Unmanned Aerical Vehicles (UAVs) that comprises a receiver, which

• take over control of a UAV,
• request and check information about a UAV like for example its identity, ownership, flight permit, and flight path,
• check if a UAV has all mandatory systems on board and is operated near a special area
• and so on,

Moreover, this control system can be extended with one or more other secure embedded systems, that

11.February.2019

06:43 UTC+1
Original Ontologic Applications!?

Since quite some time we are looking at multimodal, augmented reality translators respectively the integration of Computer Vision (CV), translation, and Augmented Reality (TranslatAR).
Unsurprisingly, we found one system of the University of California at Santa Barbara, U.S.A., and also systems of the company Microsoft and at least a third entity if we remember correctly.

Also unsurprisingly, we found other Ontologic Applications (OAs) like for example a handheld user-perspective augmented reality magic lens, specifically on the basis of stereo matching, MobileKinetic, and Image-Based Rendering (IBR) and other OAs based on for example MobileKinetic and other features of our Ontoscope.

If we cannot find convincing prior art, then such OAs will be added to the related webpage, as announced, for sure unsurprisingly as well.

11:00 and 19:27 UTC+1
Clarification

*** Work in progress - result of review of SSW missing ***
We reviewed some documents related to the fields of

as well as

Until now, we have not found (persuasive) prior art in these fields with

that is described by plagiarists with statements like for example

While the first statements are made in relation to our reflective ontology-based middleware, the second statements say there is no specific middleware anymore, which shows one of the many characteristics of our Ontologic System (OS) as well. In fact, it depends on the view on and use of our OS and hence both views are right, as we also explained in relation to monolithic and microkernel-based operating systems.

Exactly the same can be said for exactly the same reasons about the related

in these fields with

that is described by plagiarists with statements like for example

whereby the terms software operating system and monolithic microkernel are utter nonsense.

Continuing in this way, the whole system stack can be viewed, dissolved, restructured, and used, that is described by plagiarists with statements like for example

The latter was also said in relation to our effective connection, merging, integration, and unification of the real world and the virtual world as our New Reality (NR) based on the fields of

• Industrial Internet of Things (IIoT) and
• Industry 4.0,

and our integration of these fields and the fields of

• Augmented Reality (AR),
• Virtual Reality (VR),

as

• Semantic Mixed Reality (SMR),
  • Semantic Augmented Reality (SAR) and
  • Semantic Virutal Reality (SVR),

At this point, it should be understood that we took the programming language Java as an inspiration but thought through it down to the foundations of its existence.
An intermediate step was to extend Linda-based systems, which originate from parallel computing and include tuple spaces like for example JavaSpaces, with SWWW standards and technologies to semantic tuple spaces or sTuples, and triple spaces, and further with logics and cybernetics as the foundations, specifically the fields of

and also the

Another step was to replace the Java Runtime Environment (JRE) or Java Virtual Machine (JVM) with all kinds of abstract machines, VMs, Virtual Virtual Machines (VVMs), hypervisors, and so on.
Also, arbitrary frameworks like for example the infrastructure technology or service platform Jini based on JavaSpaces are realized.
A concurrent step was to integrate the results with the fields listed before.
Eventually, these steps resulted in the creation of our

In the course of this review, we remembered that we have done most of the very complex work related to the Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV) already including the first steps of integrating the

14.February.2019

16:10 and 19:15 UTC+1
Further steps or Website Review

We are continuing the review of prior art and in this way improved even more our knowledge about and view on the technical but also the legal matters.

In this regard, we are also reviewing the Clarification of the 16th of October 2018 and 11th of February 2019 related to the fields of the

• Semantic Internet of Things (SIoT) including
  • Semantic Sensor Net (SSN),

and

• Semantic Web of Things (SWoT) including
  • Semantic Sensor Web (SSW)

because the white line cannot be drawn as easily as we thought due to the reasons that

• Semantic Sensor Network ontology and
• at least one more ontology related to Geographic Information Systems (GISs), the Semantic (World Wide) Web (SWWW), and potentially our Caliber/Calibre, New Reality (NR), and Ontologic uniVerse (OV),

and

• publications of said relevant elements and
• presentation of our OS, which already includes said very basic elements by design.

For better understanding, we are preparing a special Investigations::Multimedia, AI and KM with the missing investigative cases related to WoT, SSN, and SSW.

In addition, we already are at the point where we move further from

so that the related prior art does not matter so much anymore but their integration in accordance with our OS. In fact, we have now something totally new: OS is ON.

Nevertheless, we want to close the white lines in relation to technical and legal matters as early as possible, so that any nonsense like for example the blockchain-based systems, the so-called Distributed Web or Decentralized Web (DWeb), the FuturICT project related to the former two technologies, or other attempts to circumvent or even steal our OS in whole or in part, is down and out as well.

We would also like to remind governments that we

• citizens of other states and also
• users of our OS, inhabitants of our Ontologic uniVerse (OV), and members of our Society for Ontological Performance and Reproduction (SOPR),

as discussed in relation to our SOPR and regulated by the Articles of Association (AoA) and the Terms of Service (ToS) of our SOPR,

• found dependencies of our SOPR in virtually all countries and
• pay taxes in accordance with the local laws.

Roboticle Further steps
In the last two days, we have added a new model of a newer type of robot to our product range, which

Astonishingly, a design concept could be realized in this way, which before was thought to be too visonary.

15.February.2019

20:47 and 23:09 UTC+1
Further steps or Website Review

Our intuition was right but our memory was a little confused by the nonsenses publicated by plagiarists, though we were already wondering since October 2018 and eventually started the review yesterday.
For sure, an essential part of the Semantic Web of Things (SWoT) was presented by for example the company Fujitsu (Laboratories of America) with its Task Computing paradigm in the years 2003 and 2004. See its documents titled "Semantic Web and Ubiquitous Computing - Task Computing as an Example -" and "Task Computing - the Semantic Web meets Pervasive Computing -", which will be added to the webpage Links to Software of the website of OntoLinux.
But we noticed that many fields like sensor networks and other solutions were missing and hence our review and update of our website is continuing.
Indeed, a first detailed look on the prior art related to an ontology mentioned in the Website review of the 14th of February 2019 supports our view that it

:)
Other points are the

• Internet of Things (IoT) and Web of Things (WoT) and
• Semantic Internet of Things (SNoT) and Semantic Web of Things (SWoT),

and

At this point we would to give the reminder that it was one of the many beginnings, that became very rapidly so complex theirselves that a solution was required for the integration and management of the whole overall system itself, which become something totally new, which again had to be cognitive, specifically reflective, and our Evolutionary operating system (Evoos) respectively C.S.' first cybernetic self-reflection, self-image (cyber selfie), or self-portrait was the perfect match for the start.

Ontonics Further steps
For our various business divisions, that are creating the next disruptive transportation and mobility revolutions, we continued with the plan for a headquarter in the state New York, U.S.A., comprising a headquarter in the state New Jersey as an alternative option.
In relation to New York City, we found the

persuasive and conclusive because exceeding our ideas and being in absolute harmony with our ideals.
Our initial investment is intended to be around 25 bn U.S. Dollar and has the realistic potential to be increased tenfold through investments in our endeavour and related businesses by other entities and us.

Think bigger.
The Bigger Apple.

For sure, we have not forgotten our friends in the P.R.China, Russia, and the many other areas on planet Earth.
We also noticed some interest of the state Israel in relation to the Middle East gigahub of our World Wide Hover Association (WWHA) Transcontinental Network respectively Silk Skyway planned in a neighbouring country.
But we can only go ahead after the agreement with our Society for Ontological Performance and Reproduction (SOPR) is signed and all of the Intellectual Properties (IPs) of C.S. are given back. :)

17.February.2019

21:38 UTC+1
Further steps

We are investigating one more time if software, like for example Nexus or Mesos, and Istio, is already crossing the white line respectively if we can close the white lines as early as possible in the related fields as well.
Specifically problematic are in relation to the

• operating system-level virtualization or containerization,
• grid computing and cloud computing, and
• the integration of both, which is already standard with cloud computing platforms.

Indeed, we are working on a clear-cut for the

18.February.2019

05:05 and 18:30 UTC+1
Ontologic Net Further steps #1

We reviewed works related to the so-called Future Internet, specifically the field of Information-Centric Networking (ICN).

So far, we have the following (very) bold and even (serious) (criminal) (partial) plagiarisms that infringe our copyright and other rights in relation to our original and unique, iconic Ontologic System (OS):

All of them have taken our OS as blueprint but none of them got it right and provide legal certainty, and what they got right is an evidence that shows a causal link with our OS.
We do not expect that the situation with most or even all of the other related projects and technologies will be better.
If we remember correctly then we already announced a special Investigations::Multimedia. The result of this investigation will be interesting because we will also show something in relation to the 3 plagiarisms SCN, NFN, and Resource-Oriented Computing (ROC), as well as logic programming, functional programming, reflective programming, and also Service-Oriented technologies (SOx).
So much once again about the scientific landscape on the one hand and our OS on the other hand.

So far, we have the following situation:

So far, we have the following take-aways as well:

• lower layers or better said lower areas of the overall system structure or better said overall system space including the operating system and the networking system,
• overall system including its self-containment, closure and openness, self-emergence, and self-organization,
• view as a logical or mathematical system and an ontological system,
• view as a wide area (parallel computing) cluster or the Interconnected supercomputer (Intersup),
• Service-Oriented technologies (SOx),
• SoftBionics (SB) including the Semantic (World Wide) Web,
• Semantic Service-Oriented technologies (SSOx),
• and so on

have all been overlooked.

In the course of this review, we also got the impression that we have not explained the related part of our OS, specifically our Ontologic Net (ON), sufficiently, properly, and convincingly enough. So we will remedy this deficit as well.

Btw.: There exist so much intellectual material that it can be seen since quite some time that there must be some kind of an unbelievably massive black hole or singularity that attracts most of the technical matter, which for sure is C.S. with our OS and other works, and not a small light but the light. OS is ON.

05:05 and 18:30 UTC+1
Ontologic Net Further steps #2

*** Work in progress ***
We worked on some details of our Ontologic Net (ON) related to the

In this respect and in relation to the fields of Named Data Networking (NDN) and Named Function Networking (NFN), we ask the following question: What came first: the data or the function? The answer is easy: it is undecidable. But when applying an ontologic approach based on existency we can find the perfect starting point (see The Proposal, The Prototype, More Notes, and the related documents on the webpage Literature).
We begin with the reality, and views, philosophies, and theories about it (e.g. Descarte, Kant, and Co., Einstein and Co., and others), the universe with times and spaces (e.g. suns and planets), the planet Earth with causalities or events and places, places with networks, networks with data centers and computer clusters, data centers and computer clusters with computers, computers with processors, processors with cores, cores with transistors, transistors with electrons, electrons with quantum particles, and so on.
A network of transistors forms a core of a chip, a network of chip cores forms a processor, a network of processors forms a computer, a network of computers forms a data center or a computer cluster, a network of data centers or computer clusters forms an Intersup, and so on.
We continue with the virtuality in the same way with knowledge, informations, data, functions, bits, and so on.
Our OS also has the mirroring, reflective, fractal, and other basic properties and the Caliber/Calibre, which merges, integrates, and unifies the real world and the virtual world.

If we want to Keep It Simple and Stupid (KISS), then we

• logics and an empty domain or empty set,
• mathematics and a zero or empty set, and
• ontologics with an ontologic zero, correspondingly.

Oh, here is our Zero Ontology or Null Ontology already and we can compare the OS with a number system or better said a group in mathematical terms or even more better said something that goes beyond the rational or deterministical in Turing words.
Puff Pang Kaboom (see the image titled "Evidence"). OS is ON. And the game is to keep the system under control, the train on the tracks, the AI in rational times and spaces, causalities, and so on. The best way for doing so is to believe in love, find harmony, and adapt following the evolution.

As we already explained in the past, the very foundational concept of our OS does exist and it works in such a way. But as in the case of XML for example it does not make sense in practice to begin with symbol grounding, let everything self-organize and self-emerge, and resolve and evaluate everything again and again even when using caching techniques. Therefore, we use as means for

19.February.2019

11:56 UTC+1
Preliminary result

*** Work in progress - better wording ***
Our view in relation to the Semantic Sensor Net (SSN), which should not be confused with a sensor network, in which sensors are interconnected or connected to a network by using wired or wireless connections, and the Semantic Sensor Network ontology is supported by the facts that the

• lists sensor networks in the chapter Future Enabling Technologies as part of an underlay network and
• discusses them as part of a new societal infrastructure and societal systems in relation to our New Reality (NR), Ontologic Reality (OR), and Ontologic uniVerse (OV), and what is wrongly called Semantic Reality (SR or SemR) and also related to a societal infrastructure and societal systems, specifically social networking platforms, by plagiarists.

This means

• companies,
• members of the Open Geospatial Consortium (OGC),
• proponents and participants of the
  • Distributed Web or Decentralized Web (DWeb) also included in our OS,
  • participants of the FuturICT project and
  • other projects,

and

and therefore belong to our OS, which is the white line that we drew correctly in October 2018 in the fields of

• Cyber-Phiysical Systems (CPS), Internet of Things (IoT), and Networked Embedded Systems (NES) (see Semantic Internet of Things (SIoT), CPS 2.0, IoT 2.0, and NES 2.0, and Ubiquitous Computing of the second generation (UbiC 2.0)),
• SSN, and
• SWoT.

20.February.2019

OntoLix and OntoLinux Further steps

*** Work in progress - order and wording, SDN and NFV inclduded in OS ***
Network Functions Virtualization (NFV) and Deep Packet Inspection (DPI) are complementing the Software-Defined Networking (SDN) functions and can be integrated and utilized with the Ontologic System Components (OSC) of our Ontologic System (OS) in the same way like the SDN technology if required (see the OntoLix and OntoLinux Further steps of the 10th of November 2017).
In this way, we are able to run different network layer protocols and form different virtual networks (see also the Website update of today).

We would also like to recall that we also have the

See also the OntoLix and OntoLinux Further steps of the 10th of November 2017 and the Ontologic Net Further steps of the 18th of February 2019 and today.
Also keep in mind that our OS comprises our Ontologic(-Oriented) (OO 3) paradigm with its molecular or liquid system composition approach based on our integration of for example the Chemical Abstract Machine (CHAM), which applies for the OntoNet, OntoWeb, and OntoVerse components as well.

17:05 UTC+1
OntoLix and OntoLinux Website update

*** Work in progress - missing links to documents ***
We added to the section Network Technology of the webpage Links to Software the following links:

The Virtual Service Grid corresponds to and fits together with basic properties and essential parts of the works of others referenced on the webpage Links to Software and our Ontologic System (OS), as can be seen easily with the following quote: "A large array of wide-area application technologies for distributed high-performance computing including scientific problem-solving environments [...], computational Grids [...], and peer-to-peer environments [...] are emerging."

Note that the Wide Area Network (WAN) part of the Albatross system is still based on the Internet Protocol (IP) suite and the Java Remote Method Invocation (RMI), but we already improved both with for example our

• High Performance and High Productivity Computing (HP²C) technologies (see the Clarification of the 4th of June 2018) and
• exception-less system call mechanism and its kernel-less asynchronous variant (see for example the Investigations::Multimedia of the 15th of May 2018), and also
• integration of
  • blackboard systems or blackboard architecture, including
    • systems of loosely-coupled applications and services,
    • tuple spaces,
    • Linda like systems,
    • space-based systems or Space-Based Architecture (SBA), and
    • agent-based systems, like space-based agent systems,

    and

  • other distributed shared object systems (e.g. X10).

"Given that the number of data names is unbounded, can one keep the size of name-based NDN forwarding information base (FIB) under control?"
Another solution to keep the routing table size under control is to introduce a layer of indirection: one can reach addresses that are not on the global forwarding table by mapping them to addresses that are on the table. This is the main idea behind the Map-and-Encap [13] proposal, [...].
SNAMP enables the network to forward all interest packets towards the closest data even when not all data name prefixes are present in the global routing table.
See also the Further steps and the Ontologic Net Further steps of today.

06:37, 23:26, 24:26, and 25:53 UTC+1
Ontologic Net Further steps

*** Work in progress - better order and wording ***
We are continuing with looking at the solutions presented by others in relation to the future but already dead Internet and for sure our Ontologic System (OS) and copies of it (see the Further steps of the 18th of February 2019).

The first point is multiparadigmatic and multilingual programming.

• query language for declarative networks (distributed Datalog or Network Datalog (NDlog)),

As the Named Function Networking (NFN) plagiarsts said, "[a] name can thus interchangeably represent a mapping to an information object, a function capable of processing information objects, or an expression that combines the two (and involving multiple names)."
And further: "Like in the case of removing locality-of-storage aspects from data names, NFN removes locality-of-execution: instead of inferring from a user request the location for the computation and expecting from the routing substrate to reinforce its reachability, the NFN network discovers or appoints alternative places for hosting computations." But this is cluster computing and space-based computing. Is not it?

But NFN is in large parts a plagiarism of essential elements of our OS, which we will show in all details in an already announced investigation. The remaining question is if the complete NFN is already included in our OS or if NFN is merely utilizing said essential elements of our OS.
The last missing piece is included in the integration of the OntoBot and OntoNet components. "In the general topic of in-network programmability, in the past, Active Networking (AN) research [...] envisioned users able to load programs [23 [Softnet - An approach to high level packet communication], 19] in a network data path that supports programming primitives [...], or programming language frameworks, eg. [9 [PLAN: A Packet Language for Active Networks], 17 [Implementation of an Active Network]]. A modern re-incarnation of parts of the AN vision is found today in the objectives of Software Define Networking [15 [OpenFlow: [...]]]. Unlike AN and [Software-Defined Networking (]SDN[)], however, NFN's primary focus is not on explicitly programming a data path, but rather letting the network compose a data path that satisfies the needs of a high level user program, thus the main decision making lies with the network."
Obviously, our OS includes the networking and also Topic Maps (TMs) and hence hypergraphs.
OntoBot includes the

and therefore is also distributed and also includes

OntoNet includes

OntoBot and OntoNet are integrated, so that they can automatically and autonomically program or compose or both a data path or orchestrate services to do so as required. This works multilingual and not only with FP, intelligently, cognitive, and like NFN and beyond.
Virtually the same holds for similar plagiarisms, specifically of our OntoNet component, which we will shown in all details in said announced investigation as well. :)

The second point is ontology.
As we already said before for example in the OntoLix and OntoLinux Website update of the 13th of February 2018 "[w]e do not follow specific ideologies about how a computing system has to be designed and implemented, apply fixed system behaviours and schemes, and have gears and springs [...]."
We simply take an ontology and then do

The third point is SoftBionics (SB).
We simply take Artificial Intelligence (AI), Semantic (World Wide) Web standards and technologies, etc. and then do Semantic Net or even better Ontologic Net (ON).

In analogy to Ontologic Computing (OC) we call it Ontologic Networking (ON), which corresponds nicely with our OntoNet (ON) component and our Ontologic Net (ON).
As the NFN plagiarsts said "[Adoption of indirect semantics and NDN] contributes to a perception and use of the network as a data repository, a global database of some sort, or in its simplest form as a (semantic) memory." And now we take a look at our OS once again and see that we have a brain abstracted with the OntoBase and OntoFS components with Resource Description Framework (RDF) and Web Ontology Language (OWL) (local and global semantic data store or database), Associative Memory (tuple space and Content-Addreassable Storage (CAS)), OntoBot (cognitive computing), an overall dynamic ontology or ontologic, etc..

Remember in this relation, that the

• data and
• code respectively functions and methods,

• validated,
• verified,
• specification-carrying, so that even Application Programming Interfaces (APIs) are not needed at all, which corresponds to and fits together with our molecular or liquid system composition approach based on our integration of for example the CHemical Abstract Machine (CHAM) perfectly, and
• proof-carrying, so that the users and the OS itself can build on trust or blindly trust wherever needed and advantageous,

allow so many other improvements and utilizations, and do a little magic.
We must also take a look in our archive to see if more relevant prior work exists.

For sure, we do have a (hierarchical) Peer-to-Peer (P2P) global service discovery system and a middleware based on tuple spaces (e.g. semantic tuple spaces and triple spaces), ontologies, and reflection, that are integrated with the other Ontologic System Components (OSC), specifically the OntoNet component, by our integrating Ontologic System Architecture (OSA), which integrates all in one, including the SWWW middleware and the ontologic network, since the start of our OS in 2006 (see also Virtual Object System (VOS), the plagiarisms SCN and Convergence, and other plagiarisms related to the OntoNet component).
Just take our Service-Oriented Virtual Object System (SOVOS), SCN partially based on SOVOS, and Convergence based on our OS, add Semantic (WWW) Web standards and technologies, and replace the standard middleware with a knowledge-based, ontology-based, Semantic Service-Oriented Computing (SSOC), or Semantic Service-Oriented Architecture (SSOA) middleware (e.g. Web Service Execution Environment (WMSX) and reflective triple spaces) also used with the OntoWeb and OntoVerse components and the Ontologic Web and Ontologic uniVerse following the self-similarity or fractal and holonic basic properties of our OS and its OSA. In fact, it is quite simple, elegant, and perfect.

But we were already there in 2006 and therefore made the lookup services (name, directory, and discovery services), routing service, composition service, and other services scaling-proof by substituting the protocol and algorithm of networks and distributed systems based on for example Distribute Hash Tables (DHTs), like for example the Chord lookup algorithm, with the Chord# lookup algorithm (see the OntoLix and OntoLinux Website update of the 13th of February 2018).
What we are trying to do is to find further improvements for example in relation to

The result should already be what it is truly wanted for the next century or longer.
Indeed,

• exception-less system call mechanism and its kernel-less asynchronous variant, and
• substitution of DHT-based lookup algortihms with the Chord# lookup algorithm,

Oh, always ahead. :)

But

We take care on these aspects as well for example by integrating the advantages of the other architectures and systems, if not already included in our OS by design, which is what we are doing and explaining here.

At the end, we would like to recall two statements in this relation:

Indeed, others had similar ideas with metacomputing, worldwide distributed computing, and grid computing, but none of them were able to realize it, develop it further, or even create something totally new in contrast to us.

Of course, we are worth all that trust and money. :)

Btw.: We demand the company Cisco Systems to remove the infringing open source NFN matter immediately.
The same holds for SCN and all the other plagiarisms made in Swiss, and Convergence with CONET, and all the other plagiarisms made in Italy.

21.February.2019
Comment of the Day
"The first one, who shoots, is the second one, who looses."
"Der Erste, der schießt, ist der Zweite, der verliert."

14:00 and 22:30 UTC+1
Clarification

*** Work in progress - layers vs. areas vs. spaces vs. scopes ***
We noticed a misconception and even a confusion within the field of Information-Centric Networking (ICN) and in relation to our Ontologic System, specifically our Ontologic Networking, OntoNet component, and Ontologic Net respectively we forgot to explain how our OS works in this relation.
The Internet is about the "where", which has become a source of many problems, while the so-called Future Internet is about the "what", which should solve these problems of the Internet by removing locality-of-storage and locality-of-execution, as said in relation to the ICN technologies Named Data Networking (NDN) and Named Function Networking (NFN), but it is said in relation to the ICN system Convergence that "a content-centric network (CONET) [...] should allow controlling where in the network contents or links to contents will be stored, e.g. in a given geographical or administrative domain." Somehow the various views are contradictory.

Despite that the

our OS is based on ontologies, so that its ON, OW, and OV are able to handle everything including the "when", "where", "who", "what", "why", "how", and so on.
All layers or spaces of the architecture, including the link and the physical layers or areas, of both wireline and wireless technologies, are considered with an integrated approach, that includes data and information, time or event, space or address, entities, objects, causalities or reasons, and every other aspect.
We have ontologies, specifically for times and events, spaces and places, topics and themes, and ontologics, which can be used as scopes on the overall dynamic ontology and overall ontologic respectively OS.

We also noticed that the proposed network architectures focus on only

• tuple spaces,
• Linda like systems, and
• agent-based systems and space-based agent systems,

and

But again we have ontologies for computer networks and distributed systems, and our OS does them all.

As a side effect, the OS alone and together with the users being inside the OS can solve problems, like for example the naming, routing, securing, localizing, caching, and so on with a snap.

Zooko's Triangle says we can only have two of the three following properties of a naming scheme:
"Zooko's Triangle identifies possible tradeoffs among three desirable properties of a naming scheme of a network protocol. Zooko's Triangle states that names can enjoy simultaneously at most two of the following characteristics:

For instance,

Because security is a must we have to choose between decentralization and memorability."
Do we really? No, we must not, but let the OS do one or more of them to have it all.
For security we have the basic properties of (mostly) being

which (mostly) overcome Zooko by the trust in and magic or spirit of our belief system OS.
This works also with other properties of a system (see the CAP Theorem or Brewer's Theorem and the PACELC theorem based on the CAP Theorem).
We can reduce most of the issues until only special cases remain, which are irrelevant in practice and can be written in stones, hardcoded, etc., or simply dismissed.

In fact, these points have also been overlooked.

23.February.2019
Clarification
*** Review - last section and prior art related to smart ***
We found an interesting and entertaining report about the Java Jini system, which is based on the Linda model or coordination language respectively tuple space model called JavaSpaces, and somehow got the idea to say something more about the relation of Jini and tuple spaces with our Ontologic System.

In the following, we quote said report titled "More than just another pretty name" and publicated in the year 1998: "Sun's Jini opens up a new world of distributed computer systems [...]
Objects in the Jini system do not have to be centrally managed and instead, are matched by a sort of electronic bulletin board that lists the objects' attributes, according to the company. Sun's chief scientist, John Gage, likes to call Jini "the singles bar" model of computing since the process mimics people looking for partners in the real world.
Sun believes Jini could be used as a foundation for connecting large numbers of machines into distributed systems that are self-monitoring and able to move and replicate data automatically. If Jini achieves its second wish of redefining the computer, users of any device from a smartcard upward could be freed from concerns about the location of data and where computations are performed. The operating system as we know it today could quietly retire. Sun co-founder and chief Jini architect Bill Joy admits this distributed systems dream will take "a quantum leap in thinking."
But there is more. If Jini enables objects to communicate like people, why not use it to migrate real-world transactions and interactions into software on the network? The long-term future for Jini could be as a building block for networked markets and software "mirror worlds" of the one we know today, some observers say.
[...]
But behind such blue-sky visions lies a fledgling technology that many within Sun still do not understand. [...] As a result, when Jini surfaced last month, a host of Sun executives were at a loss as to exactly what the technology is and how to explain it.
[...]
Asked about Jini at Sun's earnings announcement two days after news of Jini broke, Chief Operating Officer Ed Zander looked to his boss, Chairman and CEO Scott McNealy for help. "Scott and I are trying to flip a coin here and see who's smarter on this," Zander confessed. McNealy, however was not much help, simply summing up the work as "exciting and compelling."
Even Jini's name is still in question. The name was originally taken from a program Joy wrote to generate all words that start with "J" (for Java) that can be pronounced in English. "Jini" sounded good to Joy and sounded like the magical spirits in the ancient tales "Arabian Nights' Entertainments," a Sun official says. Sun is now trying to decide what that name means. Is it Java Intelligent Network Infrastructure? Java Information Network Infrastructure? Or, Jini Is Not Initials?
[...]
And if Jini can indeed be used to connect appliances around the home and tools at the office, Sun hopes the architecture can scale up to the level where the tasks of thousands or even millions of users and devices are managed by Java objects zipping around the network without the central control of an operating system.
[Microsoft] Windows, and all major operating systems - [Sun Microsystems] Solaris included - manage all of a system's resources - memory, storage, processor - under one roof: a PC or workstation. The operating system loads data and programs, handles all input/output operations and manages memory, keeping track of where data and programs are stored. The key point is that all of these components are in one location and managed by one "boss."
The Jini vision is to take all of those pieces and toss them out across a network. Java objects could travel the network and carry out the same communication between components that today is handled by an operating system.
"This is the next level in the evolution of [computer] systems," says Gage. "Today people think about a system as being in one place, right here but it is a very simple step to imagine you break it up - cut the computer up into all its little operating pieces[, which could be viewed as so-called microservices, though microservices are message-based]."

In this relation, we also quote the document titled "A Tuple-Space based Middleware for Collaborative Tangible User Interfaces", which is based on the related features and basic properties of our Ontologic System (OS) and was publicated in the year 2009, and therefore is considered as a partial plagiarism of our OS: "Motivated by earlier approaches for ubiquitous interaction infrastructures [18 [Support for multitasking and background awareness using interactive peripheral displays]] and orchestration of mobile pervasive computing platforms [20 [Pervasive games in a mote-enabled virtual world using tuple space middleware]], we have chosen the LINDA tuple-space-concept [4 [Linda in context]] as a foundation for our coordination framework. LINDA is a means to coordinate processes solely via data contained in a 'tuple space' [6 [The Semantics of a Parallel Language based on a Shared Data space]]. A tuple space can be interpreted as a virtual blackboard, which is used by several processes for communication and/or interaction. The participating processes do not communicate via messages and do not share variables. Rather, they produce data structures, called 'tuples', and place them into the tuple space for access by other processes [3 [A Knowledge-Based Framework for Deploying Surveillance Problem Solvers]]. This access is realized using three basic operations:

Linda thus can be understood as a producer-consumer algorithm, which is solely orchestrated using data structures [3] [(compare with the publish-read or publish-subscribe algorithm)].
Consequently, when designing our framework, we took a data-centric perspective. Coordination between input devices, output devices and orchestration among them is founded solely on the data collected and processed."

Honestly, we also have not understood how Jini works for some few days at that time, but in contrast to others we were so fascinated about everything related to the Java technology that we catched fire in relation to Jini instantly and even developed the whole Java technology further eventually.
As some results of our own research and development in the OntoLab, we have integrated

• systems of loosely-coupled applications and services,
• tuple spaces,
• Linda like systems, like for example the CHemical Abstract Machine (CHAM), and
• agent-based systems and space-based agent systems,

but also our

and combined and integrated the result with the operating systems, Runtime Environments (REs) or Virtual Machines (VMs), networking systems, data stores, User Interfaces (UIs), including Graphic User Interfaces (GUIs), Tangible User Interfaces (TUIs), and Multimodal User Interfaces (MUIs), and everything else.
Suddenly, we got something totally new beyond Java, Jini, and mirror worlds, that we called Ontologics and Ontologic System (OS).

00:01, 04:27, 06:14, and 16:30 UTC+1
Ontologic Net Further steps
Further steps

*** Work in progress - order, wording, microservices vs. actoragents, etc. ***
We are reviewing and ordering the many interesting Information-Centric Networking (ICN) materials inclusive the plagiarisms.

(wide area) (parallel computing) cluster or cluster computing

Semantic (World Wide) Web (SWWW) standards and technologies include

One reason why we have not explicitly mentioned SOC and SOA in relation to our OS is that we have them included in our OS through SWWW anyway.
SOA applications are WS and "The most credited technology that deals with service oriented computing is Web Services [...]."

We added reflection and integrated the SWWW with operating system and networking system for example. This is sufficient to show the originality and uniqueness of our OS in this relation as well, specifically in relation to (reflective) tuple space-based, knowledge-based, and ontology-based middleware.

But we also have realities and therefore we also considered the solutions developed in the field of Distributed Virtual Environment (DVE) or Networked Virtual Environment (NVE) and its subfield of Massively Multiuser Virtual Environment (MMVE), including the field of Massively Multiplayer Online Game (MMOG) (see also the Virtual Object System (VOS)), which are often related to the fields of

and also

or simply said with everything we also want in addition to contents and services.
These fields also

• aspects of the Virtual Environments (VEs) reflect aspects of the
  • Real Environments (REs) on the one hand and
  • Wide Area technologies (WAx) on the other hand.

The latter property is exploited with for example our

In the case of lookup services, including name, directory, and discovery services, as well as routing and forwarding services, etc. for Distributed Systems (DSs) based on for example Peer-to-Peer (P2P) computing, grid computing, and tuple space computing we have the already described

• hashing

and with

• parallelization,
• unlimited-state-per-node topology,
• reactive routing state or cache management, and
• support for scalable
  • multi-attribute range queries,
  • relational queries, and
  • SPARQL Protocol and RDF Query Language (SPARQL) queries,

• caching,
• prefetching,
• load balancing,
• partitioning in structured superpeers or supernodes, super-supernodes, and so on (see also map-and-encap approach for controlling the size of state-per-node topology, and scaling and replication of VSG and DVEs, zoned federation of DVEs, and O(logk n) scheme of Chord# extension),
• utilizing reactive and proactive actions on the basis of
  • background communication with multicasting and broadcasting, and
  • SoftBionic (SB) function
    • epidemic hoarding,

  or

• adding an additional computer.

Background communication overhead is no problem with the huge bandwidth available.
As another improvement we reuse the collected data about the network whenever advantageous.
There also exists at least one interesting lock service for Distributed Systems (DSs) that can be integrated in an advantageous way as well.

In relation to the Tapestry location and routing architecture the statement is made that the tasks of

must be integrated. But we already have

• systems of loosely-coupled applications and services,
• tuple spaces,
• Linda like systems, and
• space-based systems

and

with the integration of the CHemical Abstract Machine (CHAM) as well as

so that

are so to say microservices and even smart or intelligent microservices {actoragents of a space-based agent system} in our OS or better said ontologic services, too, which provides the required flexibility and makes our OS future-proof.
The basic properties and the integrating OSA allow the reduction of complexity and the release of synergies between the many applications and services of the different layers or areas and their improvements and optimizations.

Eventually, we end up with a wide area (parallel computing) cluster in general and the Interconnected supercomputer (Intersup) in particular {softbionic High-Performance Computing (HPC) respectively Ontologic Net} and {infrastructure} components of OS are operated as such and not as the Internet, the World Wide Web (WWW), and the Semantic (World Wide) Web (SWWW) anymore (see also the Comment of the Day #2 of the 21st of November 2012).

The OS can be viewed as a fractal that becomes what a human, a cyborg, or a machine wants to by using another fractal which is an instantiated ontologic and works as an (ontologic) scope or (onto)scope.

This raises the question where to begin with an ontologic or a related (onto)scope in the fractal. Algorithmic Information Theory (AIT) asks for minimal solution. Our Evolutionary operating system (Evoos) gives 3 starting variants. Eventually, it does not matter where to start but how, which let to the transformation of existing matter into our OS.
The fractal and geometric basic properties (structure, topology, and geometry) of the OS are important.

The Ontoscope constitutes a hardware realization for a more general ontologic or related (onto)scope in the fractal OS.

We said that our Ontologic System Architecture (OSA) has a special layered structure, because conceptually the OSA is tier-less and layers only exist as ontologic areas respectively (ontologic or onto)scopes in the moment the related part of the fractal OS is "touched", examined, or "unlocked" by a human, a cyborg, or a machine like the information about time or when, and space or where of an electron, as we explained many years ago already. This is done with our multidimensional, multiparadigmatic, multilingual, multimodal, multimedia programming, Ontologic Programming (OP) for Ontologiic Computing (OC) and Ontlogic Networking (ON).
Once again the questions are where to start and how minimal is the starting set. The OS starts with the fractal represented by the Zero Ontology or Null Ontology O#, which is initialized with a Kernel-Less Operating System (KLOS) but could also start with for example a complete system already existing (see The Proposal) or an arrangement or structure, topology, and geometry of hardware elements that has the function of a KLOS.

• [Network address translation (]NAT[)] traversal: NDN does away with addresses, public or private, so NAT is unnecessary.
• Address management: address assignment and management is no longer required in local networks. no IP addressing layer"

OntoNet

Others have

and correspondingly we have also

but what we are missing is something like

in correspondence with the multimodal properties. For example, when we use optical switches, fibers, and networks then we could use an image or video coming from an imager directly as resource identifier.
In the same way, we are also missing the multilingual and multiparadigmatic properties, though this has been added to ICN by us already and therefore NDN and NFN were not selected and hence CCN was not selected but are included in our Ontologic Computing (OC) and Ontologic Networking (ON) paradigms.
But in for example the ... Further steps of the ... we said that we use (hyper)graphs for ... and therefore

and a named graph is an instantiated ontologic, so to say, which is ontology-based data and ontology-based code {issue with graphs relevant?}, which again has to be resolved, rewritten, or computed for forwarding, getting a desired item, etc.. It could be compared with the unification of the plagiarisms NetKernel without XML and NFN. So let us call it NON like NONsense. :D

But the OntoNet, OntoWeb, and OntoVerse components are different and work in a different way on the basis of our Ontologic Computing (OC) and Ontologic Networking (ON) paradigms. Once again, the fractal and geometric basic properties (structure, topology, and geometry) of the OS are important.

no triple-based or triple space computing, but tuple space computing, such as for example ontology(-based) space computing, OWLSpace computing, or OntoSpaces, because Resource Description Framework (RDF) and also Web Ontology Language (OWL) and Topic Map (TM) as well as (hyper)graph rewriting
languages can be mixed with other languages, programming paradigms can be mixed with other programming paradigms, models can be mixed with other models, and computing paradigms can be mixed with other computing paradigms (e.g. Client-Server (CS), Peer-to-Peer (P2P), grid, tuple space, and triple space computing) by agent or manager respectively ontology (see also the related explanation given yesterday, and also Java JXTA in relation to P2P computing and also Open Agent Architecture (OAA) in relation to Service-Oriented technologies (SOx), blackboard systems, and Natural Language Processing (NLP))
persistently publish-read and publish-subscribe systems (e.g. Publish-Subscribe Internet Technologies (PURSUIT), content-centric, publish-subscribe service model, and ontology-based publish-subscribe system)

In the course of this review, we also got the impression that we have not explained the related part of our OS, specifically our OntoNet, OntoWeb, and OntoVerse components, sufficiently, properly, and convincingly enough. So we will remedy this deficit as well.
Subsequently, we will select an exemplary configuration for name service and routing, etc., that we will take as starting point for the infrastructure of our SOPR and our ON, OW, and OV platforms.

Instead of running in circles we will show more SWWW standards and technologies, applications, and services to explain the OC better with real world examples in the next days.

What should we say? Ontologics!

24.February.2019
Style of Speed Further steps
We developed three new variants of the system mentioned in the Further steps of the 27th and 28th of January 2019, which allow

of our related conventional Vertical Take-Off and Landing (VTOL) aircrafts.
The variants are based on the integration of a component, that we had already adapted for or integrated in a different way with the first variant of the system.
While the second variant is more focused on the performance level and substitutes a main component of the first variant completely, the third variant is also focused on the improvement of the energy efficiency of said main component.

17:39 UTC+1
Preliminary investigation of Linux Foundation finished/finalized

*** Work in progress ***
We already said it between the lines in the Clarification of the 23rd of February 2019 (yesterday). The disputed new functionality in the libaio library of the Linux kernel is based on a Distributed Shared Memory (DSM), tuple space, or Linda like system respectively the blackboard architecture, or Linda architectural model or coordination language.

We also mentioned in the past that the CHemical Abstract Machine (CHAM) has very similar concepts and the same degree of parallelism like the tuple space architectural model of Linda according to its developers.

Eventually, the responsible Linux kernel developers have not only copied our integration of the Kernel-Less Operating System (KLOS) and the Systems Programming using Address-spaces and Capabilities for Extensibility (SPACE) approach, but the integration of KLOS, SPACE, and CHAM in relation to the

• avoiding the cost of a ring transition, specifically a vertical system call trap respectively a context switch from the unprivileged level or user mode, where application and system processes execute, to the privileged level or kernel mode, where the kernel resides, and
• providing an exception-less system call mechanism without or with its kernel-less asynchronous variant.

Correspondingly, we have not only an infringement of our moral rights and personal rights, because C.S. was not named as original author of this new, original and unique, and very significant operating system functionality and essential element of our original and unique, iconic work of art titled Ontologic System and created by C.S., but a verbatim direct copyright infringment in relation to the latter.

Because we reject Free and Open Source Software (FOSS) licenses for protecting our Ontologic System, we also reject being listed in the copyright noticed of the related part of the libaio library and demand once again to stop that copyright infringement immediately by removing the infringing material.

Btw.: The same holds for all similar solutions including the FlexSC, VirtuOS, and virtio library of the Linux kernel.
Using this functionality with other

• cluster computing,
• Peer-to-Peer (P2P) computing, and
• gird computing,
• cloud computing, and edge computing, as well as
• mobile computing

will only deepen this infringement.

25.February.2019

21:47and 22:39 UTC+1
OntoLix and OntoLinux Further steps

A quick look on the Secure NAmespace MaPping (SNAMP) technique showed its similarity in the way scaling and replication is done with for example the Virtual Service Grid (VSG) architecture and Distributed Virtual Environment (DVE) architectures, that are included in our Ontologic System (OS) by design since 2006, as well as the other functionalities of our Ontologic Networking (ON) paradigm (see the Ontologic Net Further steps of the 20th of February 2019 and Further steps of the 23rd of February 2019).

But we were not satisfied with the one-dimensional or linear naming scheme of the Virtual Object System (VOS) (e.g. .../3D/object/point or .../place/www/ontologics/index.html), which by the way was later also applied in the fields of

and therefore we chose a (hyper)graph-based naming scheme when developing our OS, which we call

With our OntoNet, OntoWeb, and OntoVerse components, including for example the

we have everything required for realizing our Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV), as well as all the other related, known and unknown properties and functionalities of our OS also developed by us.

Even better, we have a backward compatibility, so that the

• Information-Centric Networking (ICN), specifically the works done in the fields of
  • NDN and
  • NFN,

can be used and reused in constructive and advantageous ways, such as for example in routers that perform routing computation, packet forwarding, and data caching all based on addresses, names, graphs, and much more.

By the way, if someone is looking for a term in relation to prefix and graph we suggest pregix or pregrix. :D

So, this is looking quite well already. Is not it?
Wow, our OS is learning to walk and fly.

27.February.2019
Ontonics Superstructure #20
We were looking for the location of the Eastern European gigahub of our World Wide Hover Association (WWHA) Transcontinental Network respectively Silk Skyway. The candidates were the following cities and urban areas around them:

Eventually, the advantages of the city Moscow for a gigabub location were undeniable and decisive.

We are also looking at

Our Silk Skyway becomes an infrastructure for the benefit of all, that

Ontonics Space Elevator #13
We took a look at a space tower once again and got the idea to adapt a juvenile technology and a new technology for our completely new type of space elevator, whch is constructed in a completely different way than our other space elevators and correspondingly called Space Elevator 4 (SE4).
What makes the SE4 so outstanding is its

28.February.2019

00:15 UTC+1
SOPR #168

*** Proof-reading ***
As announced, we will say something more about the topics

Legal matter
If an entity is using matter related to our Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV), as well as Ontologic Computing (OC) and Ontologic Networking (ON), then we understand this as the firm commitment to the Articles of Association (AoA) and the Terms of Service (ToS) with the License Model (LM) of our SOPR.
We will not accept any nonsens such as the usual attempts to circumvent our OS by cheap tricks, technologies, or collaborations anymore.

Infrastructure
In the last days we were able to

in better ways.
Now, we can define and delineate the infrastructure of our

in better ways as well.
We hope that there was never a doubt that our SOPR will operate and therefore manage simply said the infrastructure for Ontologic Computing (OC) and Ontologic Networking (ON) or even more simply said at least the

• lookup service
  • graph service including name service,
  • directory service, and
  • discover service,
• routing,
• forwarding,
• caching,

For sure, in doing so we work together with the competent, quantified, and qualified members of our SOPR, as made clear in the past already (see for example the issue #166 of the 5th of February 2019).
Correspondingly, the ON, OW, and OV comprise dedicated subnetworks, subgrids, and other subsystems for foundational domains and ontologies, and their related technologies including platforms, products including applications, and services.

13 prominent examples are our

Please keep in mind that our OS with its integrating Ontologic System Architecture (OSA)

and therefore

Master plan
We will not give too much details about the master plan, because the evil never sleeps.
Every country, region, city, and entity gets a

depending on the density of population and demand for computing power and networking performance.
Every Virtual Service Grid (VSG) is reflected in a real service grid as an ontologic service in the Ontologic uniVerse (OV) so to say.
Then we can slowly begin with the bigger things and the magic things.