and hence already suggests what the source of inspiration is.
At this point, we would like to give the information that on the one hand our Ontologic System Architecture (OSA) also provides this functionality, for sure, and on the other hand a causal link with our OS should be avoided.

04.January.2018
OntoLix and OntoLinux Website update
We added in the section Visualization of the webpage Links to Software the links:

• Chris North and Ben Shneiderman: Snap-Together Visualization: A User Interface for Coordinating Visualizations via Relational Schemata
• Christopher Loy North: User Interface for Coordinating Visualizations Based on Relational Schemata: Snap-Together Visualization

• John A. Mariani and Robert Laugher: TripleSpace: An experiment in a 3D graphical interface to a binary relational database
• Pete Sawyer, Andy Colebourne, John A. Mariani, and Ian Sommerville: Interactive Database Objects
• Armstrong Kadyamatimba, John A. Mariani, and Peter Sawyer: Desktop Objects: Directly Manipulating Data and Meta Data

The first referenced document is a shorter description of the Snap-Together concept and the second one is the long dissertation paper of C.L. North about it, which also shows visualization applications listed in this section Visualization as well.
The fourth referenced work "describes a user interface framework called Moggetto for an object-oriented database system (OODB)" that is simply described as Oggetto with MOG editable widgets.
Snap-together these works and have more fun for example with the OntoGraphics, OntoScope, OntoCAx, and OntoBlender software components.

We also added to the section Semantic File/Storage System of the same webpage the following link:

See also the related work Investigation of the Use of the Object-Oriented Paradigm in the Construction of a Triple Store based on Dynamic Hashing, that was added with the Website update of the 6th of March 2017), is also based on the Binary-Relational Model (BRM), like for example the Resource Description Framework (RDF), mentions the Object-Oriented DataBase Management System (OODBMS) Oggetto (chapter 2.4), as well as TripleSpace and Virtual Reality (VR) (chapter 2.5.2), shows how many OS parts are connected with each other as well, and also says that "[a]n important requirement for a database system is the ability for a schema to evlove. Triple stores are uniquely placed to meet these requirements as the metadata is stored with the data itself, and thus we can apply triple store operations to the metadata", which eventually is some kind of reflective computing.
These concepts and properties make these works specifically interesting in relation with the OntoBase and OntoFS software components (see also the Further steps of the 19th of December 2017) but also in relation with the other components of our OS.

These references are for everybody who still do not know that everything is already included in our OS and how everything perfectly fits together by our Ontologic System Architecture (OSA) since the beginning of our OS, and also how it could be implemented.
Also keep in mind that our OSA integrates all in one, so that for example a user can interact naturally and directly with her/his graphics and visualizations by e.g. talking or/and gesturing with them even in an emotional way.

See also

06.January.2018
Comment of the Day
""Ignorance is bliss." said the free press." [C.S., Today]
"You know, I know this matter doesn't exist. I know that when I read it, the media is telling my brain that it is true and not faked. After nine years, you know what I realise?"

08.January.2018
Comment of the Day
"On résiste à l'invasion des armées; on ne résiste pas à l'invasion des idées.", [Victor Hugo, Histoire d'un crime==The History of a Crime, written 1852, published 1877]
One resists the invasion of armies; one does not resist the invasion of ideas.
One cannot resist an idea whose time has come.
Nothing is stronger than an idea whose time has come.
Nichts ist mächtiger als eine Idee, deren Zeit gekommen ist.
He is also well known for his novels Les Misérables and Notre-Dame de Paris==The Hunchback of Notre Dame.

09.January.2018
Ontologic Web Further steps
We have extended the range of services that are based on our OntoKey software component (see the OntoLix and OntoLinux Further steps of the 28th of October 2017).

10.January.2018
Comment of the Day
"Knowing is seeing.", [C.S., Today]

Clarification
We noticed statements like

well knowing that the OntoBot of our original and unique Ontologic System (OS) can do it even better, because it has it all, and hence is the true future.

Another statement was the following one: ""By day four of [a large consumer electronics exhibition] we will be reporting when a gadget doesn't have [the voice assistant of a first company] or [the voice assistant of a second company]," quipped [an] executive editor of [a] tech news site [...]."
We add that by day five of said consumer electronics exhibition they will be reporting when a gadget doesn't have the voice trifecta, or a related app or cloud service, and next year when a gadget is not Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV) enabled respectively part of our Ontologic Net (ON), specifically our OntoHome platform included in the ON (see the Ontologic Net Further steps of the 5th of January 2017 and 20th of October 2017, and the Ontonics Further steps of the 5th of December 2017).

In this relation, we have to note that for example the

are only workarounds and compromise temporary solutions on the way to the complete implementation of our ON, OW, and OV, because they double the latency for example, and we are sure that every truly smart company is already happy to join in and update their applications and services accordingly.

What belongs together, comes together.

Ontonics Further steps
We worked on our newest battery technology (see for example the Further steps of the 2nd and 26th of December 2017), specifically on the design, chemistry, and packaging, but at this point we are not sure if a new variation finds its way in a final electric energy storage device.
We also worked on its high-volume production.

Just for fun we also designed a so-called smart screen or smart display device, that is quite amazing.

Ontologic Web Further steps
We have added a new service to our Ontologic Web (OW) platform, that is based on the OntoCore, OntoBot, and OntoLedger software components and the service platform OntoCoin and OntoTaler included in the financial service platforms of our OW.

Our Society for Ontological Performance and Reproduction (SOPR) will also use this new service internally so to say to crawl the OW and find Ontologic Applications and Ontologic Services (OAOS) with our Search, Find, and Information (SFI) engine Ontologics.info that have been executed without permission.

Please keep in mind that our OntoLedger software component provides functionality that can also be based on the technique of the blockchain but does not depend on it in general (see for example the OntoLix and OntoLinux Further steps of the 18th of October 2017).

We also added a new service platform.

We also extended one of our platforms.

11.January.2018
Clarification
We would like to give the reminder that our Dedicated Communications (DediCom) system (not to confuse with the Dedicated Short-Range Communications (DSRC) system) includes 4G, 5G, and any other kind of wireless communication standard by design, as can be seen easily with the feature of the wireless network awareness with improved connection tools and detections of the distributed computing paradigm, that extends our AutoSemantic extension package, but does not list the Institute of Electrical and Electronics Engineers (IEEE) Wireless Local Area Network (WLAN) standards on its webpage anymore to make clear that cellular network standards are not excluded, though two of the exemplary Ontologic Applications of our Ontologic System (OS) also mention a mobile telephone and a map already besides the other explained and unexplained features of our OS related to mobile computing and networking.
The integrations with the fields of

are already provided by the related features of our

• Ontologic Net (ON) with its
  • Ontologic Net of Things (ONoT),
• Ontologic Web (OW), and
• Ontologic uniVerse (OV),

(see also the Ontonics Further steps 5th of December 2017) and

• proactive-drive/predict the future,
• proactive user support,
• able to sense humans (e.g. pedestrians),
• integration of Web 2.0 content like maps, whereby the Web 2.0 is commonly characterized by user-generated contents e.g. wikis, blogs, maps, and other crowd-sourced website contents, and
• swarm intelligence.

Null Problemo.

Ontonics Further steps
Just for fun we also designed another so-called smart screen or smart display device, that is also quite amazing.

Ontoscope Further steps
We have begun with the research and development, as well as the prototyping phases of the next generation of our head-worn Ontoscope Virtual Reality Head-Mounted Display (VRHMD) and Mixed Reality Head-Mounted Display (MRHMD) platforms in the stationary and mobile or standalone variants that provide exceptional ratio of resolution and price and in the case of the standalone variants a runtime of multiple hours or even days depending on the type, functionality, and utilization of a related HMD, as already announced several months ago.

iRaiment Further steps
We have begun with the research and development, as well as the prototyping phases of the next generation of our feature watch, smartwatch, and wrist-worn Ontoscope platforms that provide a runtime of multiple months or even years depending on the type, functionality, and utilization of a related wearable, as already announced several months ago.
For example,

But to be honest, we expect longer runtimes. Much longer.

We have also began with the research and development, as well as the prototyping phases of the next generation of our smartglasses and head-worn Ontoscope dataglasses platforms that provide a runtime of multiple months or even years depending on the type, functionality, and utilization of a related smart eyewear, as already announced several months ago.
For example,

But to be honest, we expect considerably longer runtimes.

Roboticle Further steps
We have started a new product range that has a very high potential to become a substitution for something.

12.January.2018
Comment of the Day
Dron•e™
Fridg•e™
Speak•e™
TV•e™
Smart•e™
E-component™

Ontonics Further steps
Just for fun we also extended our range of smart speakers and designed two new series with several models, that are also quite amazing and have the potential to become the killer devices in their market segment as it is the case with our smart screens or smart displays mentioned in the Further steps of the 11th of January 2018 (yesterday).

OK, Hi, Hey
Onto
Axela
Robee (pronounced like Roby)
Dronee (pronounced like Drony)
Teddee (pronounced like Teddy)
Flakee (pronounced like Flaky)
Flockee (pronounced like Flocky)
Chefee (pronounced like Chefy)
Cookee (pronounced like Cooky)
Medee (pronounced like Medy)
Nursee (pronounced like Nursy)
Cleanee (pronounced like Cleany)
Sweepee (pronounced like Sweepy)
Buildee (pronounced like Buildy)
Housee (pronounced like Housy)
Fridgee (pronounced like Fridgy)
Speakee (pronounced like Speaky)
TVee (pronounced like TVy)
Bikee (pronounced like Biky)
Scootee (pronounced like Scooty)
Caree (pronounced like Cary)
Craftee (pronounced like Crafty)
Wallee (pronounced like Wally)
Loadee (pronounced like Loady)
Diggee (pronounced like Diggy)
Liftee (pronounced like Lifty)
Hovee (pronounced like Hovy)
Smartee (pronounced like Smarty)
and our other agents.

intelliTablet Further steps
We developed a new model of our P@d series. For a few seconds we thought at first, that it is only a nice design, but then we realized that it might become much more interesting.

iRaiment Further steps
We have developed a new range for wear including tops, trousers, and shoes. Specifically exciting for us is one of our new shoe models because it has the potential to become a new classics.

Roboticle Further steps
We continued the work on a first of our robot platforms and extended its range of utilization.

We also continued the work on a second of our robot platforms and extended its range of utilization as well.

13.January.2018
Ontonics Further steps
We improved one of our technologies for wireless power transmission even more, which should be able to wirelessly transfer efficiently and safely

which is

This wireless power transmission system is ready for mass production and integration.

Style of Speed Further steps IWI #13
We updated the webpage of our original and unique System Automobile by reording the text a little and adding the

• application and service platform,
• integration with our Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV), and
• service Mobility as a Service (MaaS),

and

14.January.2018
Clarification
The exposure of the security vulnerabilities Meltdown and Spectre were no surprise for us at all in contrast to the astonishment, shock, and reactions of the rest of the world and the actings of some involved entities, because over the years we heard again and again that

• branch prediction for speculative execution and
• advanced caching,

and

can be exploited (see the OntoLix and OntoLinux Further steps of the 20th of November 2015). In fact, if we remember vaguely but nevertheless correctly we read a related news report already last year in relation with at least one of said two security vulnerabilities or a similar one, which has been confirmed in the last days.

Due to these security vulnerabilities but also many other reasons it can also be seen easily now why

which makes our ontologic works original and unique once again.

Besides this, we can also utilize other basic properties of our OS as parts of countermeasures, specifically its

Roboticle Further steps
We have created a new robot series. Lovely.

Investigations::AI and KM
*** Update - epilog missing, epilog ***

Obviously, these are parts of our Ontologic System (OS) and our Ontologic System Architecture (OSA), specfically the OntoBot software component, the related features listed on the webpage Feature-Lists, and the related integrated works listed on the webpage Links to Software, but proving a causal link and correspondingly a copyright infringement in relation with our original and unique ontologic works is not easy in this case, because at this time we cannot show our relevant substantial contributions to the field of Machine Learning (ML), specifically to Artificial Neural Networks (ANNs), with the only exceptions discussed in the related comments made to the quotes above, and because the various libraries, frameworks, and toolkits of organizations and companies taken alone do not provide a starting point for intervention on the basis of a copyright infringement.

The attempt to show our contributions comes down to the little but nevertheless immensely important detail that rewriting logic was only used for biological neural networks and Artificial Neural Networks (ANNs) but neither for ANNs with backprogation used for adaption or training nor for Recurrent Neural Networks (RNNs) before the start of our OS. In this relation, we found two documents that are about ANNs in Maude, were published in the year 2008, and should be taken as binding because they were written by long-term users of Maude. These documents say, that one of the research directions in rewriting logic discussed in 1997 could be the representation of ANNs in rewriting logic but since then "no concrete map has ever been constructed either following those ideas or any others" and the proposed approach could only be used for the first stage but not for "the second one, in which the output produced by those patterns is used to adapt (or train) the net so as to make it more precise", which let the authors to the claim that they have filled the gap with the "introduc[tion of] multilayer perceptron [(MLP)] nets, their specification in Maude, and an appropriate strategy for their evaluation [and the presentation of t]he backpropagation algorithm for neural network training". The fact is, we filled this gap before with the OntoBot software component of our OS that is based on SoftBionics (SB) and Maude, which again is based on rewriting logic and also reflection (see the related comments made to quotes above) and we guess that most potentially the authors deliberately withhold our works to mislead the scientific community and the rest of the public.

Despite that we have not found out if and what parts of our OS went into the deep learning techniques and their applications, it is nevertheless very remarkable that only in 2009 and hence more than 2 years after the start of our OS deep learning was applied in the fields of Automatic Speech Recognition (ASR), Natural Language Processing (NLP), Recommender System (RS or RecS), and Computer Vision (CV), and executed on multiple GPUs and cloud computing systems, which all are elements and features of our OS as well. This proves once again that we started the so-called renaissance of AI and ML, indeed and as we always said, but not one of those companies always mentioned in this relation, which also shows once again the more than obvious misleading of the public about the significance of our actings and the unfair business practices of others in this case as well.

Btw.: Symbolic approaches belong to Artificial Intelligence 1 (AI 1) in this context and the context of our SoftBionics (SB), and we call the combination of mainstream techniques and orphaned, model-based algorithms as well as other approaches and techniques AI 3.
We do not need to tell our fans and readers who is meant with Black Swan.

Investigations::Multimedia

In the course of this investigation we found out, that the acronym OASIS of the MMORPG even means Ontologically Anthropocentric Sensory Immersive Simulation, which obviously and doubtlessy provides the causal link with our Ontologic System and its acronym OS, its Ontologic System Architecture and its acronym OSA and basic property of integrating Virtual Reality Environments (VREs) and simulators, like the OntoCOVE and the other ones listed in the sections Collaborative Virtual Environment, as well as simulations, like the ones listed in the sections Machine Simulation, Robot Simulation, Human Simulation, Earth Simulation, and Space Simulation on the webpage Links to Software of the website of OntoLinux, and its Ontologic uniVerse and its acronym OV, that is functioning as a New Reality (NR) and already changing the society since its start in the year 2006.
The acronym OASIS also reflects the acronym of the operating system Online Application System Interactive Software of the company Phase One Systems, that has been renamed to THEOS, which means The OS in the sense of The One on the one hand and in Greek God on the other hand, which again provides another causal link with our original and unique OS due to the relation with the field of ontology, the ontological proof or ontological argument, and so on.
Furthermore, the link to the worldview of or belief in anthropocentrism, humanocentrism, or homocentricism can be found in the logo of SoftBionics (SB), whereby SB is also a foundation of our OS and hence listed on the webpage Terms of the 21st Century of OntoLinux and in the title of the section Mensch im Mittelpunkt==Human in the Center and in the content of the section Mitarbeiter==Employees of the webpage Philosophie==Philosophy of the website of the C.S. GmbH.
Needless to say that anthropocentrism and an egg is also directly connected with embryology which is one of the main topics of The Proposal, obviously.
Moreover, among licensed characters and elements used in the film is the DeLorean time machine from the movie Back to the Future, that is outfitted with K.I.T.T. from the TV series Knight Rider, which reflects our K.I.T.T. of Style of Speed, which again is based on our OS and included in the OV and New Reality (NR) as well.
Also, the scientific designations ornithology and oology have some synthectical similarity with the scientific designation ontology, an egg shape can be found in the middle of the fractal sign O#, which also symbolizes our ontologic zero, and the date of the movie's launch in theaters on March 30, 2018 is also no happenstance because March 30 can also be written as 03.30 and 30.03 depending on the location, which suggest a reflection of and a link with the 3³ Theme of C.S..

We knew it all the time that sooner or later somebody known or unknown, and specifically S. Spielberg alone or together with somebody else will make such a mov(i)e after he already did such a stunt in the past with the movie A.I. Artificial Intelligence for example. This time we catched him.
Taken all together the copyright infringement and the infringement of other rights of C.S. and our corporation are proven. Convicted!!!

15.January.2018
Comment of the Day
"Baby, gib mir mehr von dem, was Du Liebe nennst.
Auch wenn es keine Liebe ist, ich liebe es.", [Bausa, Song "Was Du Liebe nennst", 2017]

"Baby, give me more of that what you call love.
Even if it is no love, I love it/I'm loving it."

The 3³ Theme is also included as it is the case with Mixed Reality (MR) and Ontonic reflected by "Mix' Tonic mit Gin mal zwei==Mix tonic with Gin times two".
What should we say? It still makes big waves since more than 11 years now.

Ontonics Further steps
We looked at two works in the fields of Cyber-Physical Systems (CPS), Internet of Things (IoT), and Networked Embedded Systems (NES), Machine-to-Machine (M2M) communication, and Semantic Web of Things (SWoT), and found out that the only two referenced works published before 2006 are about a

• on the one hand is developed for processing distributed ontologies and
• on the other hand might be listed on the website of OntoLinux together with the materials about the other Cyber-Physical Systems (CPS), Internet of Things (IoT), and Networked Embedded Systems (NES) as announced some weeks ago

(see also the last section of the Clarification of the 10th of January 2018).
All the other works have a very obvious causal link with our OS or even are copies of parts of our OS.

Consequently, no prior art in the field of the Semantic Web of Things (SWoT) could be found, our Ontologic System (OS) with its Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV), including the Ontologic Net of Things (ONoT), Ontologic Web of Things (OWoT), and Ontologic uniVerse of Things (OVoT), remains the original and unique work, and we do not expect that significant prior art will surface in the future.

Furthermore, we have much more interesting but often plagiarizing and even defrauding material, that always show eventually that our ontologic works are original and unique, such as for example reflective ontologic middleware and other ontology-based and Ontology-Oriented (OO 2) systems. It is planned to select works for referencing them on the website of OntoLinux at an appropriate time.

Nevertheless, what we see in relation with implementations of parts of our OS looks promising and shows that our vision is right and will be realized, specifically now that companies are invited to license our ontologic works and other related works.

It's not a trick - It's Ontologics

16.January.2018
Clarification
The National Science Foundation (NSF) said in relation with Cyber-Physical Systems (CPS) that "[s]ensing and manipulation of the physical world occurs locally, while control and observability are enabled safely, securely, reliably and in real-time across a virtual network. This capability is referred to as "Globally Virtual, Locally Physical"."

The Physical Web project said that "[a] core principle of this system is no proactive notifications. The user will only see a list of nearby devices when they ask. If your phone were to be buzzing constantly as you walked through the mall, it would be very frustrating. Push notifications in general are too easily abused. Of course, the user can opt-in to notifications, we are just saying that by default, the user must ask to see anything nearby.
In addition, we only scan when the screen is on: there is no scanning that goes on when the phone is in your pocket. This is consistent with our 'no interruptions' goal but it also has a large positive impact on power usage. Using this app should have very little impact on your phone's battery life."

In contrast, the Ontoverse

• Ontologic Net (ON), including
  • Ontologic Net of Things (ONoT),
• Ontologic Web (OW), including
  • Semantic Web (SW),
  • Ontologic Web of Things (OWoT), including
    • Semantic Web of Things (SWoT),

  and

• Ontologic uniVerse (OV), including
  • Ontologic uniVerse of Things (OVoT),

• global and local, and virtual and physical respectively real
• push and pull notifications, and
• screen out and on states.

See also the Clarification of the 21st of November 2017 and the Ontonics Further steps of the 15th of January 2018 (yesterday).

OntoLix and OntoLinux Further steps
We took a quick look at Maude once again that comfirmed our impression we had already several years ago that

Binding are the contents of the documents with the titles

and other works.

Indeed, we could not find any prior art that combines the rewriting logic and the

But we found again

We also got a confirmation of one of the many advantages of our original approach:
"First of all, the election of our concrete representation in which neurons and links are individual entities and which, at first sight, might not strike as the most appropriate, is of paramount importance. Indeed, our first attempts at specifying perceptrons made use of a vector representation like the one we have used here for inputting the data and similar to that proposed in [a research work]. Such representation was actually suitable for the evaluation of patterns but proved unmanageable when considering the training algorithm."

An implication is that the special fields of

• system with stateful dataflow graph or computation graph,
• series of computational steps via a directed graph, and
• graph-based distributed computation,

and

are included in the field of SoftBionics (SB) and therefore are a part of the OntoBot software component of our OS (see also the Investigations::AI and KM of the 15th of January 2018 (yesterday)).

17.January.2018
Comment of the Day
"Nothing beats the original.", [C.S., Today]

Clarification
For everybody who has not seen it all the years we would like to make clear that our Ontologic System (OS) with its Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV) can also be viewed as an Artificial Neural Network (ANN), which can be trained on the one hand and is able to learn on the other hand, and therefore as an ANN with backpropagation, a Recurrent Neural Network (RNN), and a Deep Neural Network (DNN) respectively a deep learning system.
This is also another implication of the Investigations::AI and KM of the 14th of January 2018 and the OntoLix and OntoLinux Further steps of the 16th of January 2018 (yesterday).

In the following we summarize in more detail the foundations that makes this ability of our OS possible.
The Proposal is about a reflective operating system designed after a human brain.
The OS is (mostly) kernel-less reflective/fractal/holonic and a Multi-Agent System (MAS) respectively a holon, as can be seen easily in the section Basic Properties of the webpage Overview of the website of OntoLinux.
The Ontologic System Architecture (OSA) integrates all in one and is designed after a associative system in general and a human brain in particular as well, as can be seen easily in the section Integrating Architecture of the same webpage.

In Maude, which is

• rewriting logic
• metaprogramming, and
• reflection,

• model of computation and
• logic,

• OntoBot software component of our OS, and
• integrated by our OSA in this way,

elements of a system can also be handled as

that can act for example concurrently in a distributed system.

The Pathway Logic Assistant (PLA) realized as a Maude actor and also included in the OntoBot

• Maude module (for rewriting, logical specifying, and reasoning),
• Petri net (for efficient query), and
• graph (for interactive visualization),

In fact, our Ontologic Paradigm (OP) or Ontologic Computing Model (OCM) generalizes this approach of Maude and the PLA and provides different representations of or views on a computing system that can be semantically equivalent, which provides our OS the capability to shift shape, so to say, in whole or in part and on a system levels and abstraction levels between multiple models of computation, such as a common operating system (os), a Multi-Agent System (MAS), a holonic system, and an ANN even at runtime and as part of its operation whenever required.

This very special and fascinating capability was utilized by us to extract or separate hardware and software compilers out of our Ontologic System (OS) and Ontoscope (Os), that are based on the ANN techniques respectively associative computation model and transform or map microkernel-based and monolithic operating systems, such as Unix (includes Apple MacOS and iOS), Linux (includes Google Android), Microsoft Windows, etc., into ANN based control systems respectively associative systems (see also the Clarification of the 14th of January 2018 once again) and Integrated Circuitries (ICs), such as microchips and processors (includes x86, ARM, AMD, and Nvidia), into ANN based neuromorphic circuits respectively associative machines (see the Ontonics Website update of the 7th of April 2013).

Needless to say that this OS property is directly and seamlessly connected with Content-Addressable Memory (CAM) respectively Associative Memory (AM) and Content-Addressable Storage (CAS) as well (see the Clarification of the 8th of August 2014 and 9th of March 2017, the Ontonics, OntoLix and OntoLinux Further steps of the 2nd of May 2016, the Ontologic Net and Ontologic Web Further steps of the 11th of May 2016, and the OntoLix and OntoLinux Website update of the 8th of March 2017).

The Binary Decision Diagram (BDD) data structure, the relational model, and the graph transformation for inter-model transformation (see OntoLix and OntoLinux Website update of the 27th of May 2016 for example) are also included in the OntoCore, OntoBase, OntoFS, and OntoBot software components of our OS (see also the OntoLix and OntoLinux Further steps of the 28th of May 2016 and 1st of June 2016 as well as the Clarification of the 14th of January 2018) and provide the foundations for the basic properties of (mostly) being self-adaptive, self-organizing, self-regenerative, and intelligent, as well as for additional features and many utilizations.

We do apologize if we raised the impresson that we have camouflaged this basic property of our OS between the lines of our publications.

Please keep in mind that these OS properties and functionalities have been developed and integrated in the years 2004-2006, later published in a highly condensed or minimalistic way with the start of our OS OntoLinux, and since then merely explained by showing resolutions and implications of what has been published already before and by using much more words with our following publications like this clarification.

Original and unique

Now, our fans and readers can see once again, how very well thought our OS truly is, and why we absolutely rightfully say:
This is a serious copyright warning.
Be happy and become a member of our Society for Ontological Performance and Reproduction (SOPR).

19.January.2018
Comment of the Day
"In general, the question is not if the machine is unstoppable but who owns and controls the machine.", [C.S., Today]

Ontonics Further steps
Already some days ago, we developed a new variant of a mechanism, which can be utilized for many devices.

OntoLix and OntoLinux Website update
We noted that we overlooked and forgot to mention the Mekensleep Underware software library set in the related list point of the Feature-List Ontoverse (2nd June 2012), that only mentions the Virtual Object System (VOS), despite Mekensleep Underware

Said this, we corrected this faux pas.

Ontologic Web Further steps
We improved our social networking platform of our Ontologic Web (OW) including the

(see also the message OS is ON of the 9th of May 2016).

SOPR #101
Our OS and our Os have become the worldwide standard for the

Our OS and our Os are becoming more and more the worldwide standard for the

See for more industrial sectors listed in for example the complete United Nations industry classification system called International Standard Industrial Classification of All Economic Activities:

the complete classification system of the U.S.A., Canada, and Mexico called North American Industry Classification System or NAICS:

and the complete classification system of the European Union called Statistical Classification of Economic Activities in the European Community (NACE) and other areas (where are our friends from P.R. China?) to find out what is already affected or will become affected eventually.
Hint: It is everything and therefore the terms Web 3.0, Web 4.0, Web 5.0, and Industry 4.0 are not quite right.

Our OS and our Os will become the worldwide standard for

as well.

As we already said and suggested in the past and the last time, envisioning and realizing such a performance demands the participation in its monetization by law.

In an internal discussion someone said that if we demand our fees and share we would destroy the companies because the values for their stock would plunge and make them insolvent. We do not think so in the common case, that is licensing the reproduction and performance of our ontologic works at the SOPR, but in the hard case, that is a prosecutor takes the case to the court and the judge gives us right.

20.January.2018
Ontonics Further steps
We have developed a new type of fuel cell, which has an efficiency of more than 94%. But more interesting for us is its working temperature of around 50 °C or less and its converging with another technology of us in this way even more.

16:20 UTC+1
Oh, what ...?

Ontologics Ontologic System Architecture (OSA) with Bridge from Natural Intelligence to Artificial Intelligence, OntoBase, Multimodal OntoBot, Multimodal OntoScope, Augmented Reality (AR) and Mixed Reality (MR), OntoEmotion, OntoNet, OntoWeb, and Ontologic Applications and Ontologic Services, Internet of Things 2.0, Integration, Logic Apps, etc., etc., etc.
No ordinary technological progress and fair use. No new work and expression of idea. No authorized performance and reproduction.

© Microsoft (only graphics) and Ontonics

As it is the case with all the other cases, this case does not need more discussion.
What is required is a reconsideration of the basis of assessment for the fixed fee but we are very sure that hardware, software, and service providers already have the related license models that we can take as blueprints.

This is a formal news that we are publicating since some weeks instead of complete investigations until the money flows. Nevertheless, we have the material commonly used for our investigations documented, prepared, and archived as it is the case with the material for other potential uses worldwide.

21.January.2018
OntoLix and OntoLinux Further steps
As a continuation to the work mentioned in the Further steps of the 19th of December 2017 we envisioned and designed a cryptographic eXtensible Array (XArray). We have not mentioned the Distributed Hash Table (DHT) data structure without any deeper going reasons (see also the Merkle tree data structure).

We have also looked at the InterPlanetary File System (IPFS) and noticed that our OntoBase, OntoFS, OntoLedger, OntoNet, OntoWeb, and OntoVerse software components can be configured accordingly where needed, if needed at all (see also the message OS is ON of the 9th of May 2016, and for example the Ontologic Net and Ontologic Web Further steps of the 11th of May 2016, the OntoLix and OntoLinux Further steps of the 5th of July 2017, and 13th, 18th, and 26th of October 2017, the Ontologic Net Further steps of the 5th of July 2017, the Ontologic Web Further steps of the 5th of July 2017, 16th of October 2017, and 10th of January 2018, Ontonics Further steps of the 19th of December 2017 (last list point), and also the Clarification of the 11th, 16th and 17th of October 2017, 20th of December 2017, and 17th of January 2018).

Please note that the event-driven network programming framework Twisted is included in the Mekensleep Underware software library set and also utilized for the Tahoe Least-Authority File Store (Tahoe-LAFS), which is a distributed data store and distributed file system but also a Content-Addressable Storage (CAS) system.
Also, take attention when utilizing and combining works (e.g. the IPFS) with other elements of our Ontologic System (OS), because of our Ontologic System Architecture (OSA), which integrates the software components and referenced works of external entities already.

23.January.2018
Preliminary investigation of University of Washington and DARPA started
A complete investigation will be published in the next future. For the while, see for example our

• autonomous function and automation,
• formal modeling with state machine and transition system (UML and Petri net),
• full-system validation and verification (SAT-solver, model checker, etc.), and
• logic, language, and analysis of components and (type-safe) systems,

• rewriting logic (logic, language, and analysis, equivalence, concurrent, etc.) of Maude,

• SPACE and
• KLOS (kernel-less or nanokernel with e.g. exception handling in user space),

and

We do not need to fabricate a fraudulent document with 18 pages to say the same.

Btw.: It does not matter at all how many other documents are referenced in a paper, because in the case that the referenced documents are based on our original and unique works as well or are published after our publications neither a causal link can be avoided nor an ordinary technological progress can be artificially created or convincingly simulated in this way.
At least we got a list of some other plagiarists, who deliberately infringed our copyright and other rights, misappropriated taxpayers' money, damaged the integrity of the scientific research community, and misled the public, and we are already looking at some of them as well.

In relation with the subject matter of the OntoLix and OntoLinux Further steps of the 3rd of January 2018 and the Clarification of the 14th of January 2018 C.S. suggested the following: "This would be ideal with a microkernel-based operating system".
A highly competent security expert answered: "Interestingly enough, a proposal to implement exactly that, using Linux as a server level process under seL4 was put on DARPA's I2O desk 18 months ago with limited success. I believe it is safe to say there was a conceptualization problem."
We do not think so because of OntoL4Linux, L4OntoLinux, and OntoL4OntoLinux.
In summary, we have at least the cases of the stolen autonomous flight controller for Unmanned Aerial Vehicles (UAVs), like helicopters and multicopters (e.g. quadcopters), based on the secure, formally verified L4 microkernel seL4 and some other features of our OS, that attempt to steal our OntoL4Linux, and that toy operating system verified by using an essential part of our OS and integrated approaches.

In the course of our investigations in relation with that verified L4 microkernel (see also the Investigations::Multimedia, AI and KM of the 16th of December 2017) we found out that short before the start of our OS OntoLinux an executable specification of this microkernel written in Haskell was discussed in public, but only in the year 2008 the document about kernel design for isolation and assurance of physical memory was published, that is related to the kernel resource management of that L4 microkernel, which is exporting the management of kernel resources to user level and subjecting them to the same capability-based access control as user resources, which was denoted as novel approach.
The latter suggests that this alleged novel approach to isolation of memory and kernel resource management of a kernel-less operating system were not inside the initial Haskell specification or model, as it is also suggested by the abstract of the related document: "We propose a development methodology for designing and prototyping high assurance microkernels, and describe our application of it. The methodology is based on rapid prototyping and iterative refinement of the microkernel in a functional programming language. The prototype provides a precise semi-formal model, which is also combined with a machine simulator to form a reference implementation capable of executing real user-level software, to obtain accurate feedback on the suitability of the kernel API during development phases. We extract from the prototype a machine-checkable formal specification in higher-order logic, which may be used to verify properties of the design, and also results in corrections to the design without the need for full verification. We found the approach leads to productive, highly iterative development where formal modeling, semi-formal design and prototyping, and end use all contribute to a more mature final design in a shorter period of time."
It is a long time ago when we looked at that, but only now we can see our capability-based kernel-less os and verified capability-based kernel-less os OntoL4 implemented in part as that secure, formally verified L4 microkernel seL4, or being more precise, secure, formally verified L4 based nanokernel or secure, formally verified L4 based kernel-less os, and also parts of our OntoL4 in the os Barrelfish of Microsoft. Potentially, we have discussed the original and unique features of our OntoL4 already in the past but in a different context.

Extra funny: Three fraudulent entities meet with each other again for the next attempt to steal our Intellectual Properties (IPs). The first entity (DARPA) funded the endeavour. The second entity (National Information and Communications Technology Centre of Excellence Australia (NICTA) respectively Commonwealth Scientific and Industrial Research Organisation (CSIRO) represented by G. Heiser et al.) has stolen before a part of our OS by espionage and most potentially by copying from our publications (e.g. OntoL4). The third entity (University of Washington) copied from our publications a part of our OS and a related approach of us based on formal modeling and formal verification.
What we find really funny is the fact that the third entity makes clear the differences between its verified toy os and the secure, formally verified L4 microkernel of the second entity, which are testified by the second entity. But a simple logical implication is that in this way the second entity testified the originality and uniqueness of our related OS part as well. Oh, seems not to be a very clever shepherd and definitely not a reincarnation of Jesus.
In the same way, a fourth entity (one or more author(s) of a webpage of an online encyclopedia) thought to be clever in stating that the kernel resource management of the secure, formally verified L4 microkernel seL4 was a novel approach in 2008.

26.January.2018
Website update
We added to the OntoLix Further steps of the 5th of May 2015 the note about the basic ideas, concepts, and software stacks given by our Ontologic System Architecture (OSA) and its integration of the Kernel-Less Operating System (KLOS) and the capability-based operating systems Systems Programming using Address-spaces and Capabilities for Extensibility (SPACE) and L4 due to historical and legal significance.
In fact,

• a capability-based and kernel-less operating system or capability-based nanokernel, and a verified and kernel-less operating system or verified nanokernel are very exotic already and also seem to be original and unique, but
• a verified, capability-based, and kernel-less operating system or verified and capability-based nanokernel are original and unique definitely,

or said in other words, there is a high and still increasing potential that a secure, formally verified L4 microkernel is a secure, formally verified L4 nanokernel, which would imply that it is

OntoLix and OntoLinux Further steps
We took a look at the libostree project formerly known as OSTree and are still critical with some utilizations of it, specifically in relation with the method of virtualization on the level of an operating system or containerization as well as sandboxing with capabilities, namespaces, transactions, and system metadata as we already mentioned in a comment of the 19th of September 2017.

Furthermore, we see that the topic Content-Addressable Storage (CAS) gets more and more momentum after our explanations about how everything fits perfectly together by our integrating Ontologic System Architecture (OSA) have been understood. For sure, we do not claim for CAS systems, the Merkle tree data structure, and so on, but caution that there are some intersections and also point on our OSA and the Ontologic System Components (OSC) once again (e.g. Peer-to-Peer (P2P) computing systems with blockchain, InterPlanetary File System (IPFS), and comparable P2P projects) (see also the Further steps of the 21st of January 2018).

At this point we would also like to repeat once again that we are not the fun killer but the industries that hijacked the open source and free software movements eventually, and we will not give away our Intellectual Properties (IPs) for free to entities who have more than enough money to license them, so that we get into the position to fund open source projects and similar activities with social and not solely economical interests.

Clarification
From an online encyclopedia we got the following informations: "Intel RealSense, formerly known as Intel Perceptual Computing, is a platform for implementing gesture-based human-computer interaction techniques. It consists of series of consumer grade 3D cameras together with an easy to use machine perception library that simplifies supporting the cameras for third-party software developers.
Features

• Tracking multiple faces
• Identification of facial features like eyes, mouth and nose

• Gesture recognition
• Tracking up to 10 simultaneous fingers, 8 gestures, and access to raw depth data

• Speech recognition
• Background noise subtraction

• Object tracking
• Drawing CG images on real-world scenarios

[...]."

From the same source we also got the following informations: "Machine perception is the capability of a computer system to interpret data in a manner that is similar to the way humans use their senses to relate to the world around them. The basic method that the computers take in and respond to their environment is through the attached hardware. Until recently input was limited to a keyboard, or a mouse, but advances in technology, both in hardware and software, have allowed computers to take in sensory input in a way similar to humans.
Machine perception allows the computer to use this sensory input, as well as conventional computational means of gathering information, to gather information with greater accuracy and to present it in a way that is more comfortable for the user. These include computer vision, machine hearing, and machine touch.
The end goal of machine perception is to give machines the ability to see, feel and perceive the world as humans do and therefore for them to be able to explain in a human way why they are making their decisions, to warn us when it is failing and more importantly, the reason why it is failing."

Obviously, the last section of this description is merely a copyright infringing and misleading editing of the content published about our original and unique ontologic works on the websites of OntomaX and OntoLinux (see The Proposal and the webpages Feature-Lists and Ontologic Applications of the OntoLinux website).

Please keep in mind in this relation that

• operating system (os),
• safe and secure computing,
• Mediated Reality (MedR) paradigm in general and the Augmented Reality (AR) and Mixed Reality (MR) paradigms in particular,
• Synthetic Reality (SR),
• Semantic (World Wide) Web (SWWW),
• Service-Oriented Architecture (SOA),
• as a Service (aaS),
• cloud computing,
• semantic grid computing,
• cognitive grid computing, as well as
• the Bridge from Natural Intelligence (NI) to Artificial Intelligence (AI), which for example allows a machine to give a self-explanation and can be applied in the fields of machine perception, Perceptual User Interface (PUI), and perceptive media, but does not belong to these fields at all.

Moreover, always missing is the overall integrating architecture that brings together fields like

• perceptive user interface,
• multimodal user interface, and
• multimedia user interface

and also

• Model-Driven Architecture (MDA),

• Multi-Agent Systems (MASs),
• Cognitive Agent Systems (CASs) (do not confuse with intelligent software agent),
• Swarm Intelligence (SI) or Swarm Computing Systems (SCSs),

• immobile robot (immobot),
• Unmanned Ground Vehicle (UGV),
  • autonomous car,
• Unmanned Aerial Vehicle (UAV),

• smart grid,

as it is the case with all the other documents of the period between the years 1998 to 2006 (see for example the Website review of the 5th of March 2017 and the related Clarification of the 6th of March 2017, the Website review of the 23rd of August 2017 and the related Clarification of the 23rd and 24th of August 2017, the related section of the OntoLix and OntoLinux Website update of the 25th of August 2017, the Clarification of the 31st of August 2017, the Website update of the 26th of September 2017, and the Investigations::Multimedia, AI and KM of the 12th of October 2017).

The consequences are the same as already said in the website reviews and clarifications referenced above.
Luckily, we are inviting everybody to become a member of our Society for Ontological Performance and Reproduction (SOPR) and obviously the time has come since the summer of 2016 that there is no way for circumvention anymore.

Investigations::Multimedia, AI and KM

In the following we look at each relevant layer provided by the OpenEmbedded framework:
"meta-oe [] Additional shared OE metadata [...] boinc-client [...] Open-source software for volunteer computing [The Berkeley Open Infrastructure for Network Computing (BOINC) is a middleware system that supports volunteer and grid computing. See the related work in the section Network Technology of the webpage Links to Software. ...] Linux CAN network development utilities [See the related work in the section Automation of the webpage Links to Software. ...] Ceres Solver is an open source C++ library for modeling and solving large, complicated optimization problems. [See the point Problem Solving Environment (PSE) in the section Basic Properties of the webpage Overview. ...] The gSOAP toolkit provides a unique SOAP-to-C/C++ language binding for the development of SOAP Web Services and clients. [...] raptor2 [...] Library for parsing and serializing RDF syntaxes [See the Ontologic File System (OntoFS) software component and the sections Semantic File/Storage System and Semantic (World Wide) Web of the webpage Links to Software. ...] tbb [...] Parallelism library for C++ - runtime files [Threading Building Blocks (]TBB[)] is a library that helps you leverage multi-core processor performance without having to be a threading expert. It represents a higher-level, task-based parallelism that abstracts platform details and threading mechanism for performance and scalability. [See the webpage Feature-Lists. ...] [This layer with all these supporting libraries, applications, and tools already copies a part of the composition of our Ontologic System (OS), which has been selected and composed very carefully (see also the Clarification of the 18th of October 2017 and the Clarification #1 of the 3rd of November 2017), and the combination with those other layers of the OpenEmbedded framework also constitutes a part of the composition and basic properties of our Ontologic System (OS) and Ontologic System Architecture (OSA), as can be seen better with other layers mentioned in following quotes.]",
"meta-amd [] Official layer for AMD common platform/board support [...] CodeXL enables developers to harness the benefits of CPUs, GPUs and APUs. [See the Feature-List #1 of our OS OntoLinux.]",
"meta-tegra layer [] BSP layer for the NVIDIA Tegra processors. [...] cudnn [...] NVIDIA CUDA Deep Neural Network library [See the section Softbionics and Artificial Intelligence 3 of the webpage Terms of the 21st Century. ...] tensorrt [...] NVIDIA TensorRT (GPU Inference Engine) for deep learning [See once again the Feature-List #1 and the section Softbionics and Artificial Intelligence 3. One of the main issues is not that this layer includes this library for Deep Neural Networks (DNNs) and therefore for a method of SoftBionics (SB), but again the combination with those other layers of the OpenEmbedded framework, that constitue a part of the composition and basic properties of our OS and OSA. Even more problematic is the multicore and GPU-based inference engine for deep learning, because this has been copied directly from our website of OntoLinux and the causal link is provided by the overall framework of OpenEmbedded for example.]",
"meta-intel-iot-devkit [] This is the distro layer for the Intel IoT developer kit. [See the Feature-List #5 of our OS OntoLinux.]",
"meta-ivi [] This layer's purpose is to add In-Vehicle Infotainment (IVI) support when used with Poky. The goal is to be able to build a GENIVI compliant baseline image. [See the section Computing and Multimedia of the website of Style of Speed, which describes technologies that are powered by our OS.]",
"meta-refkit [] Defines the distribution of the IoT Reference OS Kit for Intel Architecture project. [This layer depends on many other layers, such as meta-filesystems, meta-iot-web, meta-intel-realsense, meta-oie, meta-refkit-computervision, meta-refkit-core, and meta-refkit-industrial, which shows the general problem of providing compositions that are partial copies of our OS and OSA.]",
"meta-refkit-computervision [] A profile for the IoT Reference OS Kit for Intel Architecture with tools and configuration for computer vision use cases. [...] mkl-dnn [...] Intel Math Kernel Library for Deep Neural Networks [See once again the section Softbionics and Artificial Intelligence 3 of the webpage Terms of the 21st Century. ...] packagegroup-computervision [...] Components for computer vision profile [See once again the section Softbionics and Artificial Intelligence 3. ...] refkit-image-computervision [...] IoT Reference OS Kit image for Computer Vision profile. [See once again the Feature-List #5 and the section Softbionics and Artificial Intelligence 3 of the webpage Terms of the 21st Century. One of the main issues is not that this layer includes this library for Deep Neural Networks (DNNs) and this package for Computer Vision (CV), and therefore a method and a field of SoftBionics (SB), but again the combination with those other layers of the OpenEmbedded framework that constitue a part of the composition and basic properties of our Ontologic System (OS) and Ontologic System Architecture (OSA). Even more problematic is the further combination with the field of the Internet of Things (IoT), because this has been copied directly from our website of OntoLinux and the causal link is provided by the overall framework of OpenEmbedded for example.]",
"meta-refkit-extra [] A layer for demos and other things which are built on top of [the] IoT Reference OS Kit for Intel Architecture. [...] Caffe: A fast open framework for deep learning [...] Darknet: Open Source Neural Networks in C [...] The meta-refkit-extra layer depends upon: openembedded-core meta-refkit [See the comments made to the two quotes before and to the following quote.]",
"meta-refkit-industrial [] A profile for the IoT Reference OS Kit for Intel Architecture with tools for industrial use cases, i.e. ROS Industrial packages intended to be used in industrial robotics applications. [...] refkit-image-industrial [...] IoT Reference OS Kit image for Industrial profile. [...] The meta-refkit-industrial layer depends upon: openembedded-core meta-oe meta-ros meta-python meta-refkit-core [We will not accept combinations of this layer with other specific or even unacceptable layers, because that Robot Operating System (ROS) already infringes our copyright as it is the case with the combinations of the field of the Internet of Things (IoT) with that ROS and cloud computing services, because these combinations have been copied directly from our website of OntoLinux and the causal link is provided by the overall framework of OpenEmbedded for example.]",
"meta-networking [] This layer is intended to be a central point for networking-related packages and configuration. It should be useful directly on top of oe-core and compliments meta-openembedded. It should be primarily useful to the following groups: - Anyone building a small networking device (eg. a home router / bridge / switch). - Anyone wanting to add network services to their device (eg. anything that might benefit from a small ftp/tftp server) [See the section Network Technology of the webpage Links to Software. Also consider that in the case this meta-networking layer is combined with the meta-iot-cloud layer we already get for example the software stack for a smart home hub and Ontologic Applications. This becomes even more worse when other layers are added as well.]",
"meta-cloud-services [] Support libraries and packages that are not directly coupled to a particular cloud solution (i.e openstack). [This layer seems to be okay but only at first sight because it depends on the meta-virtualization layer, which includes an agent of a company that is copying contents of our websites and parts of our OS. See also the other comments made in relation with similar problematic combinations.]",
"meta-device-cloud [] Device Cloud (DC) is a cloud/device platform that accelerates device to cloud and cloud to cloud interaction. This meta layer integrates a Python implementation that is designed to be run on the device side and can be used for device actuation, management, sending telemetry, remote console etc. The Python agent for DC is designed for quick deployment on any platform that supports Python. The continuous deployment model uses "pip" to install and update the latest modules. Any application that wants to use DC cloud services can import the "device_cloud" module and begin using the DC APIs. [This layer seems to be okay but in combination with other layers an unwanted situation is reached quickly.]",
"meta-intel-realsense layer [] This layer adds the packages necessary for adding support for Intel RealSense cameras via librealsense [...] librealsense2 [...] Intel RealSense SDK 2.0 is a cross-platform library for Intel RealSense depth cameras [One of the main issues is not that this layer includes a library for 3D or depth cameras and implements gesture-based human-computer interaction techniques, but again the combination with the other layers of OpenEmbedded that constitue a part of our composition and OSA as well as the software stack for our Ontoscope. Even more problematic is the library for machine perception or Perceptual User Interface (PUI) and Augmented Reality (AR), because this has been copied directly from our website of OntoLinux and the causal link is provided by the overall framework OpenEmbedded for example.]",
"meta-iot-cloud layer [] OpenEmbedded layer to add support for multiple cloud service provider solutions [...] [One of the main issues is not an interface to a related part of our Ontologic System (OS) or the federation of distributed systems and related cloud computing services, inclusive logic application management and Internet of Things (IoT) services, but the combination or even federation of these specific individual distributed systems respectively cloud computing services and IoT services, such as for example the voice-based cloud services or speech cloud services, vision cloud services, video intelligence cloud services, and cognitive computing cloud services, to an overall composition, which is definitely a part of our Ontologic System Architecture (OSA) and accordingly the related cloud computing applications and services constitute Ontologic Applications and Ontologic Services (OAOS). The latter is not covered by the fair use clause or an ordinary technological progress. Even more problematic is the integration of these service interfaces of the companies Google, Microsoft, Amazon, and IBM, because these are parts of our OSA that have been copied directly from our website of OntoLinux and the causal link is provided by the overall framework of OpenEmbedded for example. In fact, this looks like an attempt to copy a substantial part of our Ontologic Net (ON). As in the case of ROS, there is no way to go on as in the past.]",
"meta-iot-web [] IoT web components including Node.js, IoT REST API Server, iotivity-node, etc [...] [Again, the potential combination with other specific layers is one of the true problems.]",
"meta-maker [] This layer is intended to be the home of applications and tools for Makers in OpenEmbedded. While initial focus is on 3D printing, this is by no means intended to be an exclusive layer. Other applications for CNC machining, lasercutting, knitting, etc. are expected to follow and are welcome. [See the section Rapid Prototyping Machine of the webpage Links to Hardware.]",
"meta-office [] This layer contains libreoffice recipes, import filters and helper libraries required by libreoffice. [...] rasqal [...] Library for querying RDF [...] redland [...] Library providing the RDF API and triple stores [See once again the OntoFS software component and the sections Semantic File/Storage System and Semantic (World Wide) Web of the webpage Links to Software.]",
"meta-qt5-extra [] Recipes to build desktop environments and applications based on Qt5 [...] marble [...] Marble is a Virtual Globe and World Atlas [See the section Earth Simulation/Virtual Globe of the webpage ....] serd [...] C library for RDF syntax which supports accessing Turtle and NTriples [...] sord [...] C library for storing RDF data in memory [See the comment made to the quote before. At this point it becomes obvious once again that the potential combination with other specific layers and the partial copy of our relatively exotic composition are problems in relation with our copyright.]",
"meta-ros [] ROS (Robot Operating System) support layer [...] ar-track-alvar [...] This package is a ROS wrapper for Alvar, an open source AR tag tracking library. [...] depth-image-proc [...] Contains nodelets for processing depth images such as those produced by OpenNI camera. [...] festival [...] University of Edinburgh's Festival Speech Synthesis Systems is a free software multi-lingual speech synthesis workbench that runs on multiple-platforms offering black box text to speech, as well as an open architecture for research in speech synthesis. It designed as a component of large speech technology systems. [...] realsense-camera [...] ROS driver for RealSense camera [...] robot-pose-ekf [...] The Robot Pose EKF package is used to estimate the 3D pose of a robot, based on (partial) pose measurements coming from different sources. It uses an extended Kalman filter with a 6D model (3D position and 3D orientation) to combine measurements from wheel odometry, IMU sensor and visual odometry. The basic idea is to offer loosely coupled integration with different sensors, where sensor signals are received as ROS messages. [...] rosgraph [...] rosgraph contains the rosgraph command-line tool, which prints information about the ROS Computation Graph [...] sphinxbase [...] This package contains the basic libraries shared by the CMU Sphinx trainer and all the Sphinx decoders (Sphinx-II, Sphinx-III, and PocketSphinx), as well as some common utilities for manipulating acoustic feature and audio files. [...] srdfdom [...] Parser for Semantic Robot Description Format [...] yocs-virtual-sensor [...] Virtual sensor that uses semantic map information to see obstacles undetectable by robot sensors. [...] [As we said before, we will not accept combinations of that ROS layer with other specific or even unacceptable layers and the reason can be seen easily with the combination of Augmented Reality (AR), OpenNI, Festival, and a Semantic Robot Description Format related functions. We also documented the fraud in relation with ROS and an ontology server, and other serious issues in the past already. As a consequence, we will not discuss ROS any further and the only solution we can see in this case is to convey ROS and all related patents to us and then license them by our Society for Ontological Performance and Reproduction (SOPR).]", and
"meta-sdl [] Connect IVI system with smart phone application framework [See once again the section Computing and Multimedia of Style of Speed, specifically the AutoSemantic extension package. By the way: The meta-sdl layer should get a better name that does not interfere with the acronym of the Simple Directmedia Layer (SDL), like for example meta-SDLIVI.]".
Most potentially, the meta-homeassistant, meta-iot-web, meta-oic, and meta-openhab layers will become unacceptable very soon.

The system elements, like the modeling and problem solving library, Augmented Reality (AR), Machine Learning (ML), Computer Vision (CV), grid and cloud computing, Resource Description Framework (RDF), Natural Language Processing (NLP), Controller Area Network (CAN) bus, robotics, 3D printing, virtual globe, Internet of Things (IoT), computation graph, Multimodal Multimedia User Interface (M²UI) and Perceptual User Interface (PUI), and so on, and their combinations are obvious evidences for the act that the website of our OS OntoLinux, specifically its webpages Links to Software and Links to Hardware, have been taken as blueprints because some layers include our very carefully selected and arranged relatively exotic composition that otherwise would make no sense at all.
It is also obvious that in this way a foundation, which copies an essential part of our OS and its OSA as well as a part of our composition of works of external entities and us, should be provided that can be used for the

• Cyber Physical Systems 2.0 (CPS 2.0), Internet of Things 2.0 (IoT 2.0), and Networked Embedded Systems 2.0 (NES 2.0), including
  • Industry 4.0,
• computing and multimedia technologies and systems of Style of Speed, including
  • AutoSemantic expansion package and
  • In-Vehicle Infotainment (IVI) systems,
• and other OA

as well as

• SoftBionics (SB) and
• Hyper Connectivity of Style of Speed.

From our point of view we do have an infringement of our copyright, that was deliberately conducted by the responsible entities of the OpenEmbedded framework, indeed (see the Clarification of the 18th of October 2017 and the Clarification #1 of the 3rd of November 2017).

We really like the OpenEmbedded framework very much (see also the related Ontologic Applications), but we also repeat what we already said in relation with open source software or organization like the Linux Foundation and the Apache Software Foundation, and of major industrial companies:

This also shows once again why at least all named companies will be happy to become members of our Society for Ontological Performance and Reproduction (SOPR).

27.January.2018
Comment of the Day
"Don't anthropomorphize computers; they hate that!", [A. Wexelblat, 1998]
But when C.S. does it, they are happy.

28.January.2018
Investigations::AI and KM
*** Work in progress - epilog not ready ***

The following quotes are based on the content of the presentation titled "Introduction to Chainer":
"Neural network = Computational graph [Simply take a look at for example the Clarification of the 17th of January 2018 and also note that a foundational concept of Maude is the equation, which has been reflected by this and similar titles of presentation slides.]",
"How to handle a computational graph [...] Static [...] Dynamic [] The actual code that performs computation is treated as a definition of computational graph [As we said before, the subject matter is about executable specifications of ANNs. At this point]",
"Chainer is the first deep-learning framework to adapt "Define-by-run"* *autograd adopted define-by-run but it was not a framework for deep learning" [This is a very interesting information, because it also confirms our claim and achievement in this specific area of the field of ML. Indeed, we have proven that our OS is the first system that comprises such a deep learning framework based on the facts that our OntoBot has all the required features and functionalities by design and the ANN with reverse-mode differentiation or backpropagation realized with Maude and presented by other scientists is the second one (see the Clarification of the 17th of January 2018 once again). Correspondingly, that framework is not the first DNN framework and therefore such a statement has to be considered at least as an act of unfair business practice because it deliberately misleads the public about the true origin of our achievement.]",
"Define-and-run (static graph) [] Consists of two steps: first to build a computational graph, then feed data to the computational graph (Caffe, theano, TensorFlow, etc.)",
"Define-by-run (dynamic graph) [] Describing a forward-pass computation means to construct a computational graph for the backward computation (Chainer, DyNet, PyTorch, etc.) [The term define-by-run also reminds us of our Learning by doing approach that we apply with our OntoBot. Besides this, it does not matter for this investigation if the single steps are called forward-pass computation, forward-mode autograd, backward computation, backpropagation, or howsoever, because we have a computation graph that represents an algorithm, model, or specification, which again is executable and adaptable by metaprogramming and reflective programming at runtime, and so on. With this statement we also get the information that the company Facebook with PyTorch and the Carnegie Mellon University and many others with the Dynamic Neural Network Toolkit (DyNet) are acting in the same way like the investigated company Preferred Network. This is also not a surprise.]",
""Forward computation becomes" a definition of the network [] Depending on data it is easy to change a network structure [] You can define a network itself by Python code = The network structure can be treated as a program instead of data [Firstly, we have once again the executable specification approach, which is also applied by methods of the field of Evolutionary Algorithm (EA), specifically Genetic Programming (GP). Secondly, changing a network structure respectively computer program depending on data is made possible by the properties of the multiparadigmatic programming language Python based on the paradigms of Object-Oriented (OO 1) programming as well as metaprogramming and reflection, that are all included in our integrating Ontologic System Architecture (OSA) and therefore included in our ontologic programming paradigm or Ontologic Computing Model (OCM) in general and included in Maude and therefore included in the OntoBot in particular by its integration in the OSA as a component and its integration of Maude. Eventually, we get the combination of reflective programming and executable specification, which is already relative exceptional, but their utilization for the realization of DNNs based on dynamic graphs comes very close to a causal link with our original and unqiue OS. Thirdly, treating the network structure as a program instead of data is the technique of metaprogramming, in which computer programs have the ability to treat programs as their data, and even the technique of reflective programming, because the metalanguage used for the computer program, that treats programs respectively network structures as data, and the attribute-oriented programming language used for the network structures are the same programming language. We also have here once again the technique of multiparadigmatic programming, which combines the Object-Oriented (OO 1) and graph-based programming paradigms in this case. As we said in the comment made to the quote before, these programming paradigms are also included in our ontologic programming paradigm or OCM.]",
"Distributed Deep Learning with ChainerMN [At this point we can see that the copied DNN framework is also combined with the distributed computing paradigm, which shows the similarity with the related part of our original and unique works even better and hence strengthens our position in regard to the allged copyright infringement.]", and
"ChainerRL: Deep Reinforcement Learning Library [] Reinforcement Learning: "Train an agent which interacts with the environment to maximize the rewards [] 1. Create an environment [] 2. Define an agent model [] 3. Create an agent [] 4. Interact with the environment! [An image of a simple Roboverse is shown as the environment. Besides that the copied DNN framework is also combined with the Agent-Oriented Programming (AOP) paradigm and intelligent software agents, it is also combined with 3D visualization. See the sections Intelligent/Cognitive Agent and Visualization of the webpage Links to Software of the website of OntoLinux. We have seen such a combination of a DNN framework and a 3D visualization of a software agent with the activities of the company Google in the fields of AI and ML as well, which is based on a static computation graph but nevertheless already highly questionable from the point of view of a copyright infringement. In this investigative case we even have a dynamic computation graph or a reflective graph-based approach, which taken all together is sufficient to show the causal link required to prove a copyright infringement.]".

The following quotes are based on the content of the presentation titled "Introduction to Chainer: A Flexible Framework for Deep Learning":
"The forward computation is written as a regular program code with special variables and operators, executing which simultaneously involves the forward computation and the graph construction (just by storing the order of operations). [] The graph is used for the backward computation. [] This paradigm enables us to use arbitrary control flow statements in the forward computation [...] The computational graph can be modified within each iteration [Specifically using an array for storing the order of operations and modifying the computation graph in one or more iterations reminds us of a very restrictive variant of Evolutionary Algorithm (EA), specifically of Genetic Programming (GP) and Differential Evolution (DE) used for ANNs. See also the comments made to the quotes above that are related to reflective programming and executable specification.]".

The following quotes is based on the content of the presentation titled "v2.0 alpha":
"Era of dynamic graph frameworks [] MXNet [] Chainer [] PyTorch [] Chainer as a pioneer in this field [After we have proven that we started the so-called renaissance of AI and ML but not the two other companies, we have here another proof that we also started the era of dynamic graph frameworks in ML as well. This is outstanding and therefore emphasizes the originality and uniqueness of our ontologic works and our claim for their protection by the copyright. We also got with this statement the information that the Apache Software Foundation with its MXNet framework (see its investigative case below), the company Facebook with its PyTorch lbrary, and even the company Uber with its deep probabilistic programming language called Pyro, which is variant of PyTorch, have copied this property of our OS as well, in the case of Uber because Maude also provides the foundation for "[s]tatistical/probablistic analysis of large data sets" besides the "[m]athematical models of processes [for s]olving equations (linear, polynomial, differential ...)" and the "[F]ormal (symbolic/logical) models [for a]spects of system represented as logical formulas expressing both structure and process [... and e]xecutable models [that] allow to explore system behavior", which includes debugging and more.]".
To mislead the public even more the black, red, and light blue text style (e.g. Ferrero Kinder and Nutella) of OntoLinux is used for the presentations as well.
What is that for a cheap show of that plagiarist and his supporters? For sure, we have here an essential function of our OntoBot with this dynamic DNN technique and agent-oriented programming and the combination of the OntoBot and the OntoScope with this visual 3D environment for intelligent software agents.

Sketch of the verdict is difficult to make:

• reflective programming including metaprogramming
• self-adaptive

• Artificial Intelligence 1 (AI 1) symbolic
• Machine Learning (ML)
• Evolutionary Computing (EC)
  • Evolutionary Programming (EP)
  • Genetic Algorithm (GA)
  • Genetic Programming (GP)
  • Differential Evolution (DE)

• rewriting theory
• Algebraic Data Type (ADT)
  • metaprogramming
  • reflection
• model of computation
  • dataflow
  • graph rewriting
  • Artificial Neural Network (ANN)

The decisive point is the integration of

that was introduced as

This {integrated and/or integrating?} element has been merely extracted out of the OS' basic properties and the OntoBot, and implemented with the multiparadigmatic programming language Python, which does not constitute a new work with an own expression of the plagiarist, but only some kind of editing of our original and unique work, when assessed from the semantical point of view.
Indeed, this integration {element?} could still be viewed as too trivial or/and an ordinary technological progress, and therefore as not sufficient for a protection by the copyright respectively as a copyright infringement, but

The plagiarism is proven by

• comprise the
  • style of presentation (e.g. Ferrero Kinder and Nutella style),
  • innuendos on equations of Maude,
  • abstraction of an abstraction,
  • etc.,

  and

• show the
  • true intention of the plagiarist and his supporters,

and

Accordingly the verdict can only be: Convicted!!!

Maybe not questionable or not sufficient to show a causal link with the OS are the following combinations with DNN frameworks:

Questionable or even highly questionable are the following combinations:

But the following combinations are crossing the white, yellow, or red line:

Interestingly, we now got the proof that we have not only started the renaissance of AI and ML, and introduced some other relevant features, such as CPU/GPU generic backend and Multi-GPU parallelism, but also that we were years ahead with ANNs with backpropagation and static computation graph with reflection based metaprogramming and dynamic computation graph as well. One invention taken alone could be viewed as an ordinary technological progress but this is not the case anymore with all the other combinations introduced by us with the integrating Ontologic System Architecture (OSA), like for example dynamic DNN provided by a grid computing and cloud computing platform respectively as a Service (aaS) or this combination in combination with Natural Language Processing (NLP), Natural Image Processing (NIP), Computer Vision (CV), machine perception, voice-based assistant, conversational agent, immobot, smartphone, Ontoscope and new photography, automotive computing, Semantic (World Wide) Web (SWWW) and Semantic Web of Things (SWoT), Cyber-Physical Systems (CPS), Internet of Things (IoT), and Networked Embedded Systems (NES), and also Industry 4.0, etc..
Moreover, when the whole Information and Communication Technology (ICT) industry is copying this composition and integration of our OS in whole or in part, then we reach the point once again where a discussion about the obvious infringements of our copyright and other rights is not required anymore.

Now, we know all what our contributions to AI and ML, and their applications are and that are a lot and they are beyond an idea respectively belong to the characteristic expression of C.S..

In the cases of the supporting companies IBM, Intel, Microsoft, and Nvidia, but also the companies Google and Facebook, and other companies, as well as the Carnegie Mellon University and other universities the originality and uniqueness is proven once again by the very exotic combination of

in particular and

29.January.2018
Website update
We added to the OntoLix and OntoLinux Further steps of the 23rd of August 2017 the note that "the ability for metaprogramming is already included in the OntoBot through Maude".