Home → News 2017 August
 
 
News 2017 August
   
 

03.August.2017
Comment of the Day
Hover speed™

Clarification
As a sequel to the Clarifications of the 21st of April 2017 and 23rd of May 2017 we continue with our clarifications and explanations in relation with he foundational problems of passenger drones, Personal Aerial Vehicles (PAVs), and so on, which are also called flying cars and flying taxis.

A basic multicopter has no blade pitch and does not accelerate all the time, so that passengers either are lying at taking off, landing, and hovering, or are hanging in the seat belts (if they have some at all) in forward flight at cruise speed.
Adding a blade pitch to at least two or four rotors of a multicopter makes it much more complex than a helicopter, obviously.

Furthermore, the claims "no noise==kein Krach" and "quite rotors==leise Rotoren" constitute an unfair business practice, specifically illegal marketing, if the noise is around 65 dB(A) at 75 m or most potentially louder. Imagine 4, 8, 12, 18, or more rotors with each of them being as loud as or even louder than a large electric rotary riding lawn mower and in concert even more than "twice as loud as one single [rotor]".
In addition, noise reduction of helicopters has improved very much in recent years (see also the Further steps of the 23rd of May 2017).

Hybrid systems are suggested to be an option for increasing the flight range. But in this way all the complexity and safety problems are added again that are said to be reduced by the simple multicopter concept as one of its main advantage.

Ontonics Hoverland #3
We worked a little on our US Hover Association (USHA) Trans-American Network (see also the Clarification and the Original vs. Inspiration of the 13th of August 2013 and the issue Superstructure #8 of the 14th of May 2017).
Needless to say, our Hoverpods, Hoverbusses, Hovertrains, and VTOL airplanes are not bind to train stations, airports, and even the infrastructure of our Raylev Transport System and therefore can also be used wherever needed.

US Hover Association Trans-American Network
© US High Speed Rail Association

$19 billion per year in new businesses - 150,000 jobs
At least and this is only the beginning.

Style of Speed Further steps
We are pleased to give more information about our Hoverorb, Hoverpod, and Hoverbus platforms (see for example the Further steps of the 17th of March 2017 and the Original vs. Inspiration of the 5th of May 2017 and 8th of June 2017):

  • cruise speed: increased once again (see specification given in the Further steps of the 27th of March 2017 and 26th of April 2017) in contrast to 50-70 km/h/31-43 mph for some minutes
  • maximal speed: increased once again (see specification given in the Further steps of the 27th of March 2017 and 26th of April 2017) in contrast to 100 km/h/62 mph for some few minutes
  • endurance: increased once again (fascinating; see specification given in the Further steps of the 27th of March 2017) in contrast to 27 min at a cruise speed of 50 km/h/31 mph
  • range: increased once again (see specification given in the Further steps of the 27th of March 2017) in contrast to 27 km/17 mi at a cruise speed of 70 km/h/43 mph
  • noise: 0-40 dB(A) at 1 m (noiseless to very quite; stillness to whispering) in contrast to 60dB(A) at 1 m (normal conversation) and > 65 dB(A) at 75 m of a multicopter (very loud and annoying)
  • efficiency: >> 12 g/W = 19.67 lb/hp in contrast to other types of aircraft (see the Further steps of the 24th of June 2017)
  • safety: anti-gravity device (see also the issue Ontonics Hovercity #2 of the 5th of February 2017) in contrast to a mulitcopter with full aircraft emergency parachute (see also the Clarification of the 23rd of May 2017)
  • area of operation: like airplane
  • operating temperature: like airplane
  • emission: very low overall environmental footprint (1-10% carbon dioxide (CO2) and nitrogen oxides (NOx)) in contrast to pure electric aircraft
  • and much more.

    Please keep in mind that essential concepts and technologies used for the construction of our Hoverorb, Hoverpod, and Hoverbus platforms are protected by international copyrights and worldwide patents.

    In addition, we have adapted one of our modules to substitute a component of a specific type of aircraft. In this way, we save much development time and accelerate the obtainment of the Certificate of Airworthiness (CofA) once again (see also the Further steps of the 17th of May 2017).

    We predict the future by inventing it™.


    04.August.2017
    Website update
    The Picture of the Day of the 21st of May 2017 has become an Original.

    In the issue Ontonics Hoverland #3 of yesterday we said at first "Where we are going, we do not need rails." but removed the statement later due to our Hovertrain™ platform and Raylev™ Transport System. Correspondingly, we added the missing links to the Clarification and Original vs. Inspiration of the 13th of August 2013.
    We also updated the map a little by bringing back the icon for VTOL aircrafts, correcting Hoverspeed with Hovertrain and Pod with Hoverbus, and adding Hoverpod.

    Interim injunction to ban Daimler operating systems and services required
    We made a very rough estimation about the damage that has been inflicted in the last 3 years and is sharply increasing by the activities of the vehicle manufacturer Daimler, specifically by its marque Mercedes-Benz, other marques of Daimler, and other companies based on the following facts:

  • A scientific report costs around 35 to 60 U.S. Dollar. The work related with our multimedia work of art titled Ontologic System Architecture (OSA) was at least three times higher and more complex, which makes it at least three times more worth respectively 105 to 180 U.S. Dollar, but the work could be estimated very well to be ten times higher and more complex, though its real value is not evaluable which makes it priceless.
  • An application based on the related components of for example the Mercedes-Benz multimedia platform is essentially an Ontologic Application and hence includes also intellectual properties worth at least around 5 to 10 U.S. Dollar.
  • A (web or network) service (including online advertisement and cloud computing service) based on our OSA and in combination with the feature identity management or identity and access management system, access control system, and user account control enhancement of our Ontologic System (OS) is essentially a part of our OS and hence includes also intellectual properties worth at least around 35 to 50 U.S. Dollar or even 1 to 5% of the profit gained with such an Ontologic System Service.
  • A (web or network) service (including online advertisement and cloud computing service) based on our OSA is essentially an Ontologic Application and includes also intellectual properties worth at least 5 to 10% of the profit gained with such an Ontologic Service.
    At least a licence for every single server instance is required, which can be a virtual machine constituting a virtual server, a processor, an embedded system, a server blade, etc. depending on the case of application.
  • A device based on our multimedia work of art titled Ontoscope is in the same range as the (Ontologic) applications and the OSA depending on the amount of elements or rate of similarity. We have already estimated the value which is around 10 to 15 U.S. Dollar for simple components, over 50 U.S. Dollar for more advanced modules, up to 150 to 200 U.S. Dollar or even more for a complete Ontoscope, though its value is not really evaluable and therefore makes it priceless.
  • A product based on our OSA, e.g. a cyberphysical product or a patented item, is basically a part of an Ontoscope.

    For sure, we have to consider the effect of spreading our works so much in a short time by the company Daimler, but obviously this would have happened as well when handled in a legal way by Daimler, and it also blocked the development of our corporation so that we are unable to distribute it, obviously as well. The latter has to be prized in again with other issues.

    Furthermore, the

  • extremely high level of personal and economical damages,
  • lack of public awareness in respect of the true origin of these original and unique multimedia works of art, and also
  • continuation of all misleading, damaging, and fraudulent activities

    require an interim injunction as soon as possible to ban the

  • distribution and use of all plagiarizing parts of Daimler's operating systems and multimedia systems based on our Ontologic System,
  • provisioning of all services based on our Ontologic System Architecture, as well as
  • sale of devices including parts of our Ontoscope.

    Clarification
    Sadly to say, we have to recall and emphasize once again that our

  • OntoLab, The Lab of Visions, is engaged with the generation of visions,
  • multimedia art project titled "Reality as the Media" also comprises the
    • transformation of visions, fantasy and fiction into reality, as can also be seen with our OntoLab, and
    • implementation of such transformations and realizations even in unforeseeable and unexpected ways to surprise the public and also provoke sudden changes of direction of the public, as can be observed with the jumps on the bandwagons and attempts of free riding by the industries,

    and

  • Hovercity and Hoverland with all of their stationary and mobile software systems and applications as well as hardware devices and vehicles are based on and integrated with our Ontologic System (OS) and its Ontologic uniVerse (OV) as part of our OntoLab and Reality as the Media projects.

    See the

  • Comment of the Day of the 27th of July 2017,
  • Clarification of the 12th of May 2017,
  • Original and Clarification of the 21st of May 2017,
  • Original vs. Inspiration of the 5th of May 2017,
  • Original vs. Inspiration of the 8th of May 2017,
  • Original vs. Inspiration of the 10th of May 2017,
  • Original vs. Inspiration of the 8th of June 2017,
  • Original of the 17th of June 2017, and
  • Original vs. Inspiration of the 25th of June 2017.

    Ontonics Hoverland #4
    Our Hoverland gets air emergency medical services and rescue services, also called air ambulance services, or air paramedic services, with the new Hoverdrone™ Ambulance, Hoverpod™ Ambulance, or simply Hover Ambulance™ (see also the issue Hovercity #12 of the 30th of July 2017), which conducts air transportation to move patients to and from hospital deserts, healthcare facilities, and accident scenes with our Ambulance Hoverpod™ of Style of Speed and Roboticle (see the Style of Speed Further steps of the 30th of July 2017). Personnel provide comprehensive prehospital, emergency, and critical care to all types of patients during (aero)medical evacuation or rescue operations aboard the Ambulance Hoverpods.


    05.August.2017
    Comment of the Day
    Hoverplane™

    Ontonics Hovercity #14
    Some critics said that realizing a transport system solely on aerial vehicles will not work, because in bad weather conditions they cannot fly. Indeed, this is a problem, which also applies for all ground based transport systems (e.g. storm and heavy rain and snow) and even underground transport systems (e.g. flooding).

    We are pleased to reveal the information that we have already combined our Hover Transport System based on for example the Hoverorb, Hoverpod, Hoverbus, Hovertrain, and Hoverplane platforms of Style of Speed with the Weather Control System (WCS) 1.0 of our 3D infrastructure Superstructure (see the issue Superstructure #13 of today).

    In fact, the Weather Control System (WCS) will already be in place at most villiages and cities with the installation of the Ontologic Net (ON), Ontologic (OW), and Ontologic uniVerse (OV), and other systems of our Hovercity.

    Join the bright side of the force. Become a member of our Hovercity Association and Hover Association.

    Ontonics Hoverland #5
    Some critics said that realizing a transport system solely on aerial vehicles will not work, because in bad weather conditions they cannot fly. Indeed, this is a problem, which also applies for all ground based transport systems and even underground transport systems (e.g. flooding).

    We are pleased to reveal the information that we have already combined our Hover Transport System based on for example the Hoverorb, Hoverpod, Hoverbus, Hovertrain, and Hoverplane platforms of Style of Speed with the Weather Control System (WCS) 1.0 of our 3D infrastructure Superstructure (see the issue Superstructure #13 of today).

    In fact, the Weather Control System (WCS) will already be in place at most urban areas with the installation of the Ontologic Net (ON), Ontologic (OW), and Ontologic uniVerse (OV), and other systems of our Hoverland.

    Join the bright side of the force. Become a member of our Hoverland Association, Hover Association, and Silk Skyway Association.

    Ontonics Superstructure #13
    We have integrated our Weather Control System (WCS) 1.0 (see the issue #10 of the 10th of July 2017 and the Ontonics Further steps of the 10th, 11th, and 14th of July 2017) with the Hover Transport Systems of our Hovercity and our Hoverland (see the related issues Hovercity #14 and Hoverland #5 of today).

    Join the bright side of the force. Become a member of our Superstructure Association, Hover Association, and Silk Skyway Association.


    06.August.2017
    Ontonics Further steps
    We combined two technologies of us to solve a foundational problem with one of these technologies in a quite unorthodox way.

    Ontonics Hoverland #6
    We worked a little on our EU Hover Association (EUHA) Trans-European Network (see also the Clarification and the Original vs. Inspiration of the 13th of August 2013, the issues Superstructure #8 of the 14th of May 2017 and Superstructure #13 of the 5th August 2017, and the issue Hoverland #3 of the 3rd August 2017).
    Needless to say, our Hoverpods, Hoverbusses, Hovertrains, and VTOL airplanes are not bind to train stations, airports, and even the infrastructure of our Raylev Transport System and therefore can also be used wherever needed.

    EU Hover Association (EUHA) Trans-European Network
    © Trans-European Transport Network

    The map shows the so-called core network corridors and represents only a sketch of our EUHA network that is missing straight links and additional links between countries, regions, cities, and villiages.

    22.5 billion euro per year in new businesses - 210,000 jobs
    At least and this is only the beginning.


    07.August.2017
    Original vs. Inspiration
    1. row: Popular Mechanics August 1964, cover picture, Major de Seversky's ion-propelled aircraft
    2. row: Fantastic future ionocraft

    Major de Seversky's Ion-Propelled Aircraft
    Fantastic future Ionocraft
    © Hearst Communications→Popular Mechanics and :(

    When we saw de Seversky's ionocraft the first time several years ago, we were fascinated and had to conclude that others have developed the technology already. But on a closer look it came out that an ionocraft is not practical because of its foundational properties (see also the Ontonics Further steps 24th of June 2017).

    Ontonics Superstructure #14
    We would like to show an initial sketch of our World Wide Hover Association (WWHA) Transcontinental Network respectively Silk Skyway presented in the issue #8 of the 14th of May 2017.

    World Wide Hover Association (WWHA) Transcontinental Network respectively our Silk Skyway
    © :(

    The map shows the so-called core network corridors and represents only a sketch of our Silk Skyway that is missing straight links and additional links between, continents, countries, regions, cities, and villiages.
    The US Hover Association (USHA) Trans-American Network was presented in the issue Hoverland #3 of the 3rd of August 2017 and the EU Hover Association (EUHA) Trans-European Network was presented in the issue Hoverland #6 of the 6th of August 2017. The other continental networks will be presented at appropriate times.

    125 billion euro per year in new businesses - 1,250,000 jobs
    At least and this is only the beginning.

    We are also thinking about a map projection for our OntoGlobe as the starting point for our global

  • Silk Skyway, Highway in the Sky, and Autobahn in the Sky (see for example the issue Ontonics Hovercity #1 of the 3rd of February 2017) traffic network, as well as
  • Weather Control System (WCS) grid, and even
  • Ontologic uniVerse (OV) including our OntoEarth and OntoSpace

    that is projected into 2D and 3D in any appropriate way (e.g. cubes). Preferable would be a conformal map projection (e.g. Mercator projection) and an area preserving projection.
    Obviously, this would make the shown transport network routes some kind of main streets, as known from U.S.American cities for example, or even obsolete (see also the Ontonics Further steps of the 19th of April 2017).
    Grid? Tron? No, much better: Ontologic uniVerse. :D

    Investigations::Multimedia

  • Apple: From a report about potential new features of the next smartphone model of the company Apple we got the following informations: "[...] face recognition feature will be part of the new “BiometricKit” system [...] [Biometrics refers to metrics related to one or more human characteristics. Biometrics authentication is used in computer science as a form of identification and access control. But the feature identity management or identity and access management system, access control system, and user account control enhancement of our Ontologic System (OS) is essentially a part of our OS. In addition, because a human characteristic is individual and unique a biometric system has something in common with user reflection.]", "Computational photography is the next stage in camera development - where advanced algorithms take the input of one or more physical camera lens and use it to create an image that looks better than what could be achieved with a raw, unprocessed image. [...] Apple's iPhone 7 Plus combines photos from the two cameras with different focal lengths on the back to create a lossless zoom as well as using depth information to artificially create out-of-focus background or bokeh effects for portrait shots. [A non-expert has recognized that the smartphone of the company Apple has two cameras and also a depth sensing functionality, so that we got some kind of a stereoscopic camera and two different types of 3D cameras. This is a part of our Ontoscope.]", "[...] SmartCam system, which will likely tune camera settings based on the scene it detects. [...] Some of the scenes mentioned include [...] “point light source”. [Obviously, the word smart in the term SmartCam means some kind of Artificial Intelligence (AI) or Machine Learning (ML) functionality to recognize a scene to be captured and the scene called point light source is once again an evidence for a 3D camera. These are also essential parts of our Ontoscope. See also our MobileKinetic technology.]", "Augmented reality photography", "References to a depth-sensing front-facing camera were found, likely part of the sensing system used for face recognition, which will enable new camera effects and tricks, including something called “ARFaceAnchor”. [Another company] and many other programs, including the camera apps of [just another company] smartphones, have long provided masks and other augmented-reality features that can be applied to faces. It appears Apple will ship a system that recognises the face in a selfie and can apply AR effects. Further digging also revealed a series of lines of code that appear to reference expression detection, tracking the position and shape of the mouth, among other things. Alternatively they could reference AR modifications that can be applied to faces, such as big lips or massive comedy eyes. [We have not analyzed if augmented reality photography has been copied from our Ontologic System and Ontoscope or is an older functionality. But the combination of the field of augmented reality photography and a smartphone is a part of our Ontoscope. The functionality of expression detection and so on seems to be related with some kind of Artificial Intelligence (AI) or Machine Learning (ML) functionality as well. In this relation, see the Clarification #2 of the 13th of January 2016 for example.]".
    It does not appear but is already proven that on the one hand Apple has stolen our intellectual properties in relation with the original and unique multimedia works of art titled Ontologic System and Ontoscope, and created by C.S., and on the other hand our Ontoscope is definitely not the result of an ordinary technological progress like e.g. an MP3 player.

    Btw.: We are considering to take the Apple iPhone, the Goolge Pixel, the Samsung Galaxy, and other mobile devices out of the shops worldwide together with prosecutors.


    08.August.2017
    Ontonics Hovercity #15
    We are pleased to reveal the information that we have already combined our Hover Transport System based on for example the Hoverorb, Hoverpod, and Hoverplane platforms of Style of Speed and the Hoverbee and Spray Pigeon drone platforms of Roboticle with our Earth Life Sciences project Agriculture NG™(see also the issue Superstructure #15 and Roboticle Further steps of today).

    Ontonics Hoverland #7
    We are pleased to reveal the information that we have already combined our Hover Transport System based on for example the Hoverorb, Hoverpod, and Hoverplane platforms of Style of Speed, and the Hoverbee and Spray Pigeon Unmanned Aerial Vehicle (UAV) models of Roboticle with our Earth Life Sciences project Agriculture NG™ (see also the issue Superstructure #15 and Roboticle Further steps of today).

    Ontonics Superstructure #15
    We have integrated our Earth Life Sciences project Agriculture NG™ with our Weather Control System (WCS), our World Wide Hover Association (WWHA) Transcontinental Network respectively Silk Skyway, the Hover Transport Systems of our Hoverland and our Hovercity, and more drone models/platforms of Roboticle (see the issues #8 of the 14th of May 2017 and #14 of the 7th of August 2017, and also issue #13 of the 5th of August 2017 and the related issues Hoverland #7 and Hovercity #15 of today).

    Roboticle Further steps
    For sure, with so to say the first buzzing of our Hoverbee (see also the Further steps of the 26th of June 2015, 30th and 31st of May 2017, and 31st of July 2017) we could begin to utilize them for Swarm-Engineering.
    One prominent application is the Earth Life Sciences project Agriculture NG™ of Ontonics, that could also be described as the farming of the next generation, where we use our Hovebee to distribute substances, like for example pesticides, insecticides, decontaminating substances, pollen, and suchlike, as we do with our Spray Pigeon and the Hoverorb, Hoverpod, and Hoverplane platforms of Style of Speed.


    09.August.2017
    Comment of the Day
    Hover hub™
    Hover fly™

    Roboticle Further steps
    We have designed a new model of our Hoverbee series and a model of our new Hoverfly series. Masterpieces.

    We have designed two models of a new Hoverdrone series (see also the Ontonics Further steps of the 21st of February 2017). Masterpieces, too.

    We have also designed three models of a new Hoverdrone series. Masterpieces, third.

    Investigations::Multimedia, AI and KM

  • Google: From time to time we find some more evidences for the many infringements of our rights conducted by the company Google. The latest evidence found by us is related with a router utilized at home. We quote from the product's website: "The new Google Wifi system provides a different way to improve your wireless network. It replaces your existing router, and it's a system of points that you place around the home to put an end to dead zones while delivering fast connectivity to every room and every device. It's simple to control, and features built-in Network Assist technology that keeps your network fast and secure - with no work required from you. Plus, you can manage both OnHub and Google Wifi with a single, easy-to-use companion app. [The network assist technology is a functionality of our Ontologic System (OS), as can be seen on the webpage Ontologic Applications and the section Network Technology of the webpage Links to Software of the website of our OS OntoLinux.]", "Find the fastest channel [-] OnHub automatically switches channels to maintain the best Wi-Fi signal strength and avoid congestion, without interrupting what you're doing. That gives you the fastest possible speed for your devices. [The functionalities of the Software-Defined Radio (SDR) and the Smart Antenna (SA) or Intelligent Antenna (IA) are also provided with our OS and our Wireless Supercomputer (WiSer) technology (see the OntoLix and OntoLinux Further steps of the 13th and 19th of July 2015, and the Ontonics Further steps of the 18th of August 2015).]", "A self-improving system. [-] From the moment you activate it, OnHub automatically starts learning and improving itself so you'll always have optimal Wi-Fi performance. Plus, it stays current with the latest changes in device software or security, making it compatible with new devices. [At this point the illegal strategy of the company Google implodes once again, because self-improving is a reflective cognitive ability and learning is a cognitive ability, that both are essential features of our OS, as can be easily seen with The Proposal. Therefore, these features are connected with the other features, such as the network assist technology, as part of the composition of our Ontologic System Architecture (OSA). In addition, the aspect of security is directly connected with the operating system and network functionalities listed and referenced on the website of the OS software components, in the sections Operating System and Network Technology of the webpage Links to Software, and also on the webpage of the Ontologic Applications.]", "Continuously improving [-] OnHub regularly updates its software with the newest features, so it never stops working well. [On the first look this sounds legal, but with the proven causal link with our orignal and unique works it is illegal, because this points to the reflective ability and to the comment made to the quote before once again.]", "Enhanced security [-] OnHub's software includes advanced and always-evolving security features that update automatically to help protect your network, your data, and all your devices. [On the first look this also sounds legal, but with the proven causal link it is illegal as well, because this points to the features of the OS software components related with operating systems and to the comments made to the quotes before once again.]", "[...] we've been busy delivering on our promise [...] [speech act stealing]", "Features you'll love. [Compare this slogan with the logos of OntoLinux.]", "While most routers only have two antennas, OnHub from [another company] comes equipped with 13. They're set in a unique circular pattern [...] [This is another evidence for Google's obsession with everything we do, because here we have an original and unique feature of our Wireless Supercomputer (WiSer) technology (see the Ontonics Further steps of the 13th of July 2014).]", "["If this then that" or "if then else"]-Enabled [-] OnHub is the first router that supports ["If this then that" or "if then else"], which lets you create simple commands to automate basic tasks and devices in your home. Design your own "Recipes" to automatically modify lighting, smartphones, [... programmable, self-learning, sensor-driven, Wi-Fi-enabled] thermostats, [digital media players], and hundreds of other devices and services that use ["If this then that" or "if then else"]. [Doubtlessly, this is logic programming and with the proven causal link with our orignal and unique works we have here a part of our ontologic respectively multilingual multimodal multiparadigmatic multidimensional multimedia rule-based and inference engine of the OntoBot software component for advanced "If This Then That Or Else" (ITTTOE or IT³OE) respectively "If Then Else" (ITE) control and actions based on conditional statements or expressions (see also the Bridge from Natural Intelligence (NI) to Artificial Intelligence (AI). Together with the features of learning, self-improving, continously improving, and network assistance, we have enough evidences that provide the causal link with our OS, and consequently the next infringements of our copyright and other rights.]", and "Automatic band steering [Again, we have here a functionality of the Software-Defined Radio (SDR) and the Smart Antenna (SA) or Intelligent Antenna (IA) that is provided with our OS and our Wireless Supercomputer (WiSer) technology.]".
    But these infringements of laws are not all, because we also have the next clear evidence that Google is illegally abusing its market power on the one hand and on the other hand has even strengthened its obsession at that time, and so to say the nice side effect that Google even did it once again in such an obvious way that a prosecutor and a market regulator even do not need to make any investigations anymore and a judge even does not need to think about the subject matter anymore for finding the one and only judgement: Convicted and To be broken up!!!
    It is also sufficient legal matter to put the founders and the former and actual managers of Google into jail.


    10.August.2017
    Ontonics Further steps
    Save your time, save your breath, save your money
    OK, OK, OK, we shut up and take your money for our Hoverdrone, Hoverboard, and Hoverpod coming soon.
    And do not forget our Swoop.
    And do not forget our clean diesel fuel and clean gasoline.
    And do not forget our ...
    And do not forget our OOO models of Ontoscope and intelliTablet as well as our Homebench, Flexbench, and Gamebench are also short before their releases (see all messages of the 11th of July 2014).

    Style of Speed Further steps
    The revolution continues with our piloted, platooning, and autonomous Hovertruck™ and Hovertrain™ platforms:

  • We can deliver much faster than any ground-based transport system.
  • We can deliver to the same cost or even less expensive due to straight flight paths.
  • We can deliver much safer without having any traffic in our Highway in the Sky™.

    Furthermore, we concluded that our business model of our Quickcharger, Quickflasher and Superflasher, as well as Splash and Dash Service Stations, that is based on a fuel, which is unbelievably low in price and was mentioned in the Further steps of the 17th of July 2017 for the first time, is even much more profitable, so that we are thinking about reducing the prize for our clean diesel fuel and clean gasoline that in the end will cost between 20 and 33% per liter or gallon of the actual price depending on various conditions (see the Further steps of the 27th and 28th of July 2017).
    Yes indeed, our fuels are cleaner and cheaper than the power out of the plug. :D

    Join the bright side of the force. Become a customer or even an investor of Style of Speed.

    Investigations::Multimedia, AI and KM
    *** Work in progress - better wording, some more explanations and OS links ***

  • Motorola Solutions: The company Motorola Solutions collaborated with a company, which acts in the field of Artificial Intelligence (AI) and Machine Learning (ML), specifically in the field of Artificial Neural Network (ANN) and neuromorphic computing, to create smart cameras.
    From a first report we got the following informations: "Public safety agencies today face an increasing demand to capture, store, properly manage and share video evidence. [This sounds like contents of the webpage about our OntoLogger software component of our Ontologic Systems (OSs) OntoLix and OntoLinux, which in the context of the technique of lifelogging respectively the lifelog paradigm only summarizes the related features of our Ontologic System (OS) and Ontoscope, which again are included in their general concepts (see for example The Proposal about the Evolutionary operating system (Evoos).]".
    From a second report we got the following informations: "[The other company]'s patent-pending technology uses "at the edge" learning capabilities, which allows for a body camera to "learn" to identify a person or object of interest. This process is known as incremental learning and reduces the risk of "catastrophic forgetting," which occurs when a neural network forgets its previous training. Incremental learning also enables enhanced accuracy and latency for real-time public safety applications of AI, according to the company. "[The other company]'s technology enables AI applications to learn at the edge after their deployment," [a technical director of Motorola Solutions] says. "This can unlock new applications for public safety users. In the case of a missing child, imagine if the parent showed the child's photo to a nearby police officer on patrol. The officer's body-worn camera sees the photo, the AI engine 'learns' what the child looks like and deploys an engine to the body-worn cameras of nearby officers, quickly creating a team searching for the child. [Obviously, we have here essential features of our Evolutionary operating system (Evoos) descirbed in The Proposal and our OS, as well as essential parts of our Ontoscope.]".
    From a third report we got the following information about the functionality of the system: "[The company] has created patent-pending facial recognition software capable of working on very small computers, allowing it to be used on wearable devices. The cameras will use artificial intelligence to automatically scan hundreds of faces in a crowd, notifying authorities when they come across a known target. [The company]'s founder [...] said the software works in a similar way to the mammalian brain, allowing it [to] learn faster than traditional search technology. The technology is composed of a group of specialised processors which form different parts of a 'mini brain'. And the new technology is capable of machine learning, meaning the more faces that it encounters, the faster it comes at detection. [See the The Proposal, the section Softbionics and Artificial Intelligence 3 of the webpage Terms of the 21st Century and the section Integrated Circuit/Chip of the webpageLinks to Hardware of the website ofOntoLinux.]".
    We are very sure that the pending patent of that company includes essential features and parts of our OS and our Ontoscope. If the inventors have hold back informations about our OS or/and our Ontoscope in the Information Disclosure Statement (IDS), then this constitutes an illegal patent application, which invalidates that patent in the same way, as it is the case with all the other patents based on our original and unique multimedia works of art.
    Obviously, the Ontologic System (OS) and the Ontoscope are based on the Evolutionary operating system (Evoos) described in The Proposal, which is based on the fields of operating systems, including Real-Time Operating Systems (RTOSs), and cognitive computing, which again proves that our works are the original and unique works in relation with this plagiarism.
    We also explained in the Investigations::Multimedia of the 18th of December 2009 that the working of the Ontologic File System (OntoFS) software component resembles (a part of) the working of a (human) brain by giving the following explanation: "[...] this implies that a user or even a machine itself by reflection only has to do with a data storage system of a machine (e.g. computer) or its own data storage system what nature does with a brain: Connecting, disconnecting and caring connections between nodes in an appropriate way, which is done in ontological and geometrical/spatial ways. Said that, with the OntoLinux™ approach we really haven't shown only how artificial intelligence can be implemented, but also how natural and in general intelligence is achieved." (see the The Proposal once again and also the Investigations::AI and Knowledge management, and Robotics of the 24th of September 2010).
    See also the OntoBot software component and the section Operating System of the webpage Links to Software of the website of OntoLinux.
    We also explained that our OS and Ontoscope can operate independently of another computer around 2009(?).

    The AI technology seems to be related with the SyNAPSE project of the Defense Advanced Research Projects Agency (DARPA), which we discussed several times in the past (see the Clarifications of the 16th of July 2014 and 8th of August 2014, and the Ontonics Further steps of the 10th of August 2014 and the Ontoscope Further steps of the 20th of September 2014 and 14th of April 2017).

    See the Clarification of the 11th of March 2008 and the comment to the Picture of the Day #1 of the 16th of May 2011, the comment to the Original of the 13th of November 2009, the Investigation of the 28th of February 2010 (keyword neural net), the Investigations::Multimedia and Robotics of the 7th of September 2010, and the cases of the company International Business Machines in the Investigations::AI and Knowledge management, Multimedia and Robotics of the 19th of August 2011 and 10th of August 2014, and the Investigations::AI and Knowledge management, and Robotics of the 24th of September 2010 and 19th of October 2012 (which was also copied by Motorola Solutions and its partner).

    Ontonics Website update of the 16th of July 2010, and the Ontonics Further step of the 7th of September 2010
    See the section Integrated Circuit/Chip of the webpage Links to Hardware of the website of OntoLinux.

    See the point 4. of the Investigations::AI and Knowledge management, Multimedia and Robotics of the 21st of May 2011.

    For sure, the combination of a (digital) camera with AI for object recognition is not new and potentially also has originated in the fields of computer vision and robotics, and potentially is utilized together with lifelogging as well (see also the OntoLogger software component for Ontologic LifeLogging). But the abstraction of e.g. a mobile device, such as a smartcamera, a smartwatch, a smartphone, and a smarttablet, as a robot head, a cyborg head, and a self-portrait with the Ontoscope is an original and unique act, that makes the Ontosope a (multimedia) work of art and there is absolutely no doubt that the Ontoscope is related with the 3D camera series Ontoscope of the company Cornu.
    Furthermore, the causal link with our original and unique works is given with the touchscreen display of the body-worn camera, its connection with distributed computing and cloud computing, specifically "cloud-based data storage" and "digital evidence management", Softbionics and Artificial Intelligence 3 (includes Artificial Intelligence (AI) and Machine Learning (ML)), cognitive computing, neural net software and hardware, and the misleading marketing slogans "Innovative 3-in-1 solution" and "Unified. Simplyfied. Smart." of Motorola Solutions, which prove that our Ontologic System and Ontoscope have been taken as blueprint in a top-down approach, which again constitutes a copyright infringement and other infringements of our rights. Said this, Motorola Solutions and its partners have lost the game already around 10 years ago. Convicted!!!

    We have not analyzed the research papers of one of the founders of the other company, but our first impression is not the best respectively the main author seems to be a fraudster.

    Last but not least, take a look at the Question of the Day of the 9th of August 2014.

    Btw.: Since this month we use the abbrevation KM for Knowledge Management.
    Please do not report about such criminal plagiarisms and activities anymore.
    Bitte nicht mehr über solche kriminellen Plagiate und Aktivitäten berichten.


    11.August.2017
    Ontonics Further steps
    We found a technique and technology for a long-term problem and selected the first products. It would be really great if the technique would work in a satisfactory manner.
    In addition, we also connected the technique and technology with one of our services.

    Style of Speed Further steps
    We thought that it was time to throw our hat in the ring as well in relation with the movement that displays common automobiles as landspeeders.
    In fact, the image of Steve McQueen's 917 hovercar respectively landspeeder is related with the 91x series based on our Speeder system platform (see the Further steps of the 11th of May 2017 and 28th of July 2017).

    Steve McQueen's 917 Hovercar respectively Landspeeder
    © :( and Style of Speed


    13.August.2017
    Ontonics Further steps
    We worked on one of our fusion reactors and designed it in a large size for a power plant, a medium size for a vehicle (no, we have not said Model T), and a micro size for a mobile device.

    Roboticle Further steps
    We worked on one of our drone models with anti-gravity device and were short before showing a first image of the first design of its first generation (see the Further steps of the 31st of July 2017. But then we got from an(other) expert gave the information that one component is not as durable as required by us to make our fans and customers happy. Luckily, we did not need to go back to the drawing board but could take one of our other technologies out of the stock that we use for a smiliar drone model (see also the Further steps of the 9th of August 2017).
    Nevertheless, we keep the first drone model in our product range, because either we take an improved variant of the component or do not improve it as a lower budget option.


    14.August.2017
    Comment of the Day
    Hover power™
    Hover power unit™

    Clarification
    We consider the following statement as a copyright infringement and a reputation infringement as part of an act of unfair business practices: "Don't use drones to carry your goods! Turn your goods into drones!" as we do in the case of the stolen concept of the other original and unique multimedia work of art titled Lighter Than Air Walker and also created by C.S..

    Ontonics Further steps
    In relation with a specific application of one of our techologies we encountered a problem. After thinking about it we found a first solution, which is relatively trivial. But we are also thinking about another possibility to improve this technology, which led to a second solution of said problem and also to said improvement.

    Roboticle Further steps
    We continued the work on one of our Hoverdrone models (see for example the Further steps of the 17th of April 2017 and 13th of August 2017 (yesterday)).
    The image shows our first design of a very basic Hoverdrone™ respectively Quadrovector™ or Quadvector™ with anti-gravity devices (4 Hover Power™ Units (HPUs) as tiles), and 32-bit flight controller but without battery and wiring.
    Its dimension is around 70 mm × 70 mm/2.76 in × 2.76 in and its weight should be around 30 g/0.066 lb as shown, like a typical palm-sized micro quadcopter without battery. With carbon fiber as base material we should be able to decrease the weight to 20 g/0.044 lb (see also the Further steps of the 25th of March 2015).
    Roboticle Hoverdrone Quadvector with Anti-gravity Devices
    © :), wiseGeek, and Roboticle

    Camera modules for imaging and First-Person View (FPV) piloting are also available. For FPV piloting we highly recommend our Ontoscope VRontier™ high-tech Head-Mounted Displays (HMDs).

    Obviously, we do not talk about fairy tales on the one hand but on the other hand we also do not give any informations about the working of our anti-gravity device and repulsorlift engine technologies with this image. Honestly, we even do not know

  • if the Hoverdrone works at all,
  • if the Hoverdrone works as intended,
  • how high its performance is (see the Ontonics Further steps of the 24th of June 2017),
  • what the physical limitations of the utilized technologies are,
  • what the practical limitations of the utilized technologies are,
  • which configuration is preferable, or
  • if we have totally over-engineered once again.

    Said in other words, the status of this work seems to be more experimental development but could be production ready already.

    Please keep in mind: Original and unique work of art, copyrighted, patented, patent pending, or/and patent queuing.

    Said that, all copycats, kleptomanics, and criminal entities should spend their time with paying their open bills and writing one or more license applications for our various intellectual properties, because otherwise serious problems may arise.


    15.August.2017
    Ontonics Superstructure #16
    We worked on the traffic control system and the related positioning system and navigation system of our 3D traffic network of our 3D infrastructure, which includes the World Wide Hover Association (WWHA) Transcontinental Network respectively Silk Skyway (see the issues #8 of the 14th of May 2017, #10 of the 10th of July 2017, and #14 of the 7th of August 2017), US Hover Association (USHA) Trans-American Network (see the issue Hoverland #3 of the 3rd of August 2017), and EU Hover Association (EUHA) Trans-European Network (see the issue Hoverland #6 of the 6th of August 2017).

    In relation with the traffic control system we harmonized the 2D maps of our traffic network with the 3D space of the vertical and horizontal passages, aisles, or skyways proposed in the issue #10 of the 10th of July 2017 and decided that the space above seas, lakes, rivers, forests, deserts, mountains, and all other areas that virtually are no whereabouts of humans become the first Highways in the Sky and Autobahns in the Sky.
    Furthermore, we worked on the traffic regulations in accordance with common rules of navigation and federal regulations for road, water, and air traffic. For example, a vehicle that comes from the right side or/and above has always priority/right of way.
    These arrangements or provisions can be taken by the Federal Aviation Administration (FAA) and other federal aviation authorities as foundations to harmonize their air traffic management systems with our traffic management system.

    In relation with the positioning system we harmonized our 3D traffic network with the rest of our Ontologic System (OS) (see for example the Ontonics, OntoLix and OntoLinux Further steps of the 2nd of May 2016) and services (see for example the issue Ontonics Hovercity #1 of the 3rd of February 2017).
    At this point, we remembered that many years ago we had the same problem in relation with various applications, such as weather forecasting and later weather control for example, and made the decision to keep it as flexible as possible and as precise as required for a specific application. That said,

  • arbitrary dimensions (e.g. 2D, 3D, 4D, and nD),
  • resolutions (e.g. discretization methods of numerical methods such as Finite Element Method (FEM), Finite Volume Method (FVM), Computational Fluid Dynamics (CFD), Smoothed Particle Hydrodynamics (SPH), etc. used for Computer-Aided technologies (CAx)),
  • mapping projections (e.g. variable Tissot indicatrix or ellipse of distortion), and
  • other features

    are handled by our Ontologic System (OS) and its

  • OntoGlobe with the OntoEarth and OntoSpace, and
  • OntoNet,
  • OntoWeb, and
  • OntoVerse,

    which are installed on the related stationary and mobile devices and systems.

    In relation with the navigation system we worked on an automatic routing functionality for our 3D traffic network that

  • is based on others' and our positioning systems,
  • implements our traffic control with their traffic regulations, and
  • avoids crossings and congestions of our various piloted and unmanned aircrafts and spacecrafts.


    16.August.2017
    Roboticle Further steps
    We continued the work on one of our Hoverdrone models (see for example the Further steps of the 17th of April 2017, and 13th and 14th of August 2017).
    The image shows the first design of a very basic Hoverdrone™ respectively Quadrovector™ or Quadvector™ with a camera module for imaging and First-Person View (FPV) piloting.
    Roboticle Hoverdrone Quadvector with Anti-gravity Devices and Camera for Imaging and First-Person View (FPV) Piloting
    © :), wiseGeek, :(, and Roboticle


    17.August.2017
    Comment of the Day
    I'm flyin' it™
    Flying can™
    Instant dropdown™
    Instant flyin™
    Hover tile™
    Hover plate™

    Roboticle Further steps
    We would like to show the first prototypes of our new type of our unforeseeable and unexpected, personal, original and unique Flying Can™ concept and platform, in this case our Flying Soda Can™ and Hover Cola™.
    Needless to say, the Flying Can™ will be available in many different dimensions and designs on the one hand and on the other hand will be used for our

  • Mail/Carrier/Message Pigeon 3.0 developed by Ontonics and the OntoLab,
  • delivery drone service, as well as
  • other new logistics services provided for external entities (see also the Further steps of the 15th of February 2015 and 10th of May 2017, and the Ontologic Web Further steps of the 5th of May 2017, and 10th of May 2017).

    Even better, our small Hoverdrone shown in the Further steps of the 14th and 16th of August 2017 lifts at least around 320-360 g/ 0.71-0.79 lb if required, and our Flying Cans have a negative weight (the magic words are anti-gravity device and repulsorlift engine) and in this way are able to fulfill all legal requirements easily even when transporting higher volumes such as Hover Beer™.

    Roboticle Flying Can Prototype
    © :(

    We are also pleased to announce the related delivery drone service called Instant Dropdown™ or Instant Flyin™, which is the successor of the retrograde pickup services and suchalike.

    We also continued the work on one of our Hoverdrone models (see for example the Further steps of the 17th of April 2017, and 13th and 14th of August 2017).
    The image shows the first design of a very basic Lego® Hoverdrone™ respectively Quadrovector™ or Quadvector™ with anti-gravity devices (4 Hover Power™ Units (HPUs) as dishes), and 32-bit flight controller but without battery and wiring.
    Roboticle Lego Hoverdrone Quadvector with Anti-gravity Devices
    © :) and :(

    I'm flyin' it™

    Style of Speed Further steps
    In the last week, we have begun to

  • transform our motorbikes into speeder bikes and swoops, aka. hoverbikes, and
  • develop the next generation of our speeders.

    Let us describe the results in the following way: Amazing.


    18.August.2017
    Comment of the Day
    The future is on™

    Ontonics Further steps
    We developed a high-performance flight controller, that has the potential to become the standard in nano and micro Unmanned Aerial Vehicles (UAV)

    We also integrated one of our technologies with another technology. But we are not sure if this makes sense from the economical point of view on the one hand and if we have invented it already on the other hand (looking into our stocks).

    Roboticle Further steps
    While working on our Hoverdrone models shown in the last days, we suddenly had the first design of a very basic nano quadrovector, nano quadvector, or mesivector (Please see the Clarification of the 26th of March 2015 for the nomenclature designations used by us in the field of Unmanned Aerial Vehicles (UAVs)).
    Below we list some specification data for the first generation:

  • general:
    • weight: 10 g or 0,022 lb
    • dimension: 25 mm × 25 mm
  • image sensor: Ontoscope
  • microcontroller: OntoLab top secret
  • software: Ontologic System
  • Vmax: top secret
  • range: 1.75 km or 1.09 mi
  • endurance: 55 min
  • flying qualities: better than mini quadrocopter.

    The dimension of a nano quadvector depends on the sizes of the Hover Power Units (HPUs), electronic components, and energy storage devices that are utilized for its construction, but the manufacturing of HPUs with customized sizes and shapes is possible (see for example the Further steps of the 17th of August 2017 (yesterday)).
    The mesicopter with its 15 mm wide rotors shown in the left image of the Further steps of the 8th of July 2016 and the HPU tiles shown in the images of the Further steps of the 14th and 16th of August 2017 have also a dimension of ca. 25 mm × 25 mm.

    The range and the endurance of this nano quadvector model are

  • the ½ of the range and the endurance of a micro helicopter based Personal Reconnaissance System (PRS) optimized with one of our energy storage devices (see the issue Ontonics Super Warrier #7 and the Further steps of the 13th of September 2016),
  • 1.75 × higher than the range and the endurance of a micro helicopter based PRS with a common lithium-ion battery, which provides a range of 1 km and an endurance of 30 min, and
  • 18 × higher than the range and the endurance of a micro quadrocopter with a common lithium-ion battery and a camera module for First-Person View (FPV) piloting.

    Before we could understand our new Hoverdrone design we also got new models for our Swiss Army Drone and U.S. Army Drone series (see the Further steps of the 19th of September 2016, 17th of April 2017, and 16th of July 2017).

    C.S. made a second sketch of the design of a smaller Swiss Army Drone.
    Roboticle Swiss Army Drone Hoverdrone Quadvector with Anti-gravity Devices
    © :(, Roboticle, and C.S.

    Honestly, this rapid development is a little mindblowing even for us.

    Authorities and agencies can give in their requirement specifications and place their orders.
    It is always better to fly with us. :D


    19.August.2017
    Original
    Ceci N'est Pas un Drone==This is Not a Drone (Yesterday and Today)
    This is Not a Drone
    © C.S.

    This flying, floating, or hovering chip, processor, or Central Processing Unit (CPU), or Hover Power Unit (HPU) of the multimedia works of art series titled Hoverinium, Pervasive Hovering, and Hovering Computing, and created by C.S. is original and unique, unforeseeable and unexpected, and best of all, definitely even is not the result of an ordinary technological progress. And if somebody is still not convinced about its special protection, then we would like to mention OS and Ontoscope, and also Hoverscope, etc. as well.
    See also the Original and the Clarification of the 21st of May 2017, the Original and the related comment of the 17th of June 2017, and also René Magritte.

    Btw.: We would like to suggest to call it la drone et une drone.


    20.August.2017
    Ontonics Further steps
    We have adapted a technology of an old system for one of our device. In fact, we already worked on this adaption but have not realized it in the specific way as we did today.

    Ontonics Super Warrior #15
    We developed another Personal Reconnaissance System (PRS) based on a new paper plane-sized Unmanned Aerial Vehicle (UAV) with anti-gravity devices (see also the Roboticle Further steps of today).

    Roboticle Further steps
    For sure, we utilize our Hoverwing and Hover Power Unit (HPU) technologies and other anti-gravity devices for the construction of small planes as well.
    Since the 14th of August 2017 we developed three basic models, that are based on different ways of construction and have the dimensions of a palm-sized micro UAV, a mini UAV, and a paper plane-sized UAV, and a basic module that will give children of all ages a smile in their face and professionals high-performance tools (see for example the Ontonics Super Warrior #15 of today).

    Below we list some specification data for the first generation of the paper plane-sized UAV:

  • general:
    • weight: 45 g or 0,099 lb
    • dimension: 280 mm × 150 mm
  • image sensor: Ontoscope
  • microcontroller: OntoLab top secret
  • software: Ontologic System
  • Vmax: top secret
  • range: 40 km or 24.85 mi
  • endurance: 220 min
  • flying qualities: better than mini aircraft.


    21.August.2017
    Ontonics Further steps
    We have developed another variant of a technology.

    Ontonics Super Warrior #16
    As part of the third revolution in warfare, we composited the latest generation of our platform for managing autonomous weaponry, which is based on SoftBionics (SB), including Artificial Intelligence (AI), Machine Learning (ML), and Evolutionary Computing (EC), for operating our long range negotiation tool (see the Roboticle Further steps of the 14th of January 2017) and our new negotiation tool of our Super Warrior platform (see the issue #14 of the 9th of July 2017).

    It is always better to collaborate with us and join our highly effective team.
    Authorities and agencies can give in their requirement specifications and place their orders.

    Btw.: As long as serious criminals are lying and stealing our intellectual properties we are not interested in discussing their incompetent nonsense at all.
    In fact, all those fraudsters are the true problem, the Box of Pandora each and every day doing bad things, but not machines, robots, AI, ML, and EC, and so on, as we said in the past already.
    "We do not have long to act." Wrong, they are already too late, they still have not understood what we are saying, they still are refusing to stop their nasty actings, and we do not wait for them anymore since the start of the Super Warrior project with its issue #1 on the 3rd of November 2015. Instead, we are putting everything that companies like for example Google, Microsoft, Amazon, International Business Machines, Qualcomm, Intel, Motorola, Tesla, and Co. as well as Samsung and many others have stolen, are stealing, and will steal from us in the fields of SB into any of our robots inclusive our negotiation tools as needed.
    The right alternative is that they license our Ontologic System, Ontoscope, and all the other nice, original and unique things of us, so that we remain neutral and keep such capabilities out of specific machines or, if this is not possible, handle them in appropriate ways.
    Hopefully, they have understood at least these simple rules of the game. :)

    OntoLix and OntoLinux Website update
    For further realizing our OntoGlobe and related systems, applications, and services we added to the section Earth Simulation/Virtual Globe of the webpage Links to Software the project:

  • Los Alamos National Laboratory (LANS) and University Corporation for Atmospheric Research (UCAR): Model for Prediction Across Scales (MPAS)

    See also the webpage Overview, the OntoCAx and OntoBlender software components, and the issues Ontonics Superstructure #14 of the 7th of August 2017 and Superstructure #16 of the 15th of August 2017.

    One of the most interesting points is that "[t]he defining features of MPAS are the unstructured Voronoi meshes and C-grid discretization used as the basis for many of the model components. The unstructured Voronoi meshes, formally Spherical Centriodal Voronoi Tesselations (SCVTs), allow for both quasi-uniform discretization of the sphere and local refinement. [... a] model takes advantage of the SCVT-dual mesh, which is a triangular Delaunay tessellation appropriate for use with Finite-Element-based discretizations." This was exactly one of our thoughts around the year 2000 or so.

    Even better, we wanted to add the technique of Voronoi diagram for other applications as well, such as

  • mesh networking, specifically Wireless Ad hoc NETwork (WANET) and its applications of Mobile Ad hoc NETwork (MANET) and Vehicular Ad hoc NETwork (VANET),
  • operating Collaborative Virtual Environment (CVE) and Massively Multiuser Virtual Environment (MMVE), including Massively Multiplayer Online Game (MMOG),
  • Swarm-Engineering,
  • simulation of rigid-body and molecular dynamics,
  • simulation of discrete-time process, and
  • all its many other applications (see for example the issue OntoLab On-Line #2 and the Roboticle Further steps of the 30th of March 2015).

    See also the OntoCOVE, OntoNet, OntoWeb, and OntoVerse software components.

    Said this, we also added to the section Network Technology of the same webpage the project:

  • National Central University, Taiwan, Department of Computer Science and Information Engineering, Academia Sinica, Institute of Information Science and Institute of Physics, Tamkang University, Department of Computer Science and Information Engineering, Université Paris, Laboratoire d'informatique de Paris 6 (LIP6), and University of Hong Kong, Department of Computer Science, VAST development team and contributors, sponsors, and community: [Voronoi-based Overlay Network (]VON[)]-based Application-layer [Spatial Publish Subscribe (]SPS[)] with Topology-awareness (VAST)

    "VAST is a light-weight network library that supports Spatial Publish Subscribe (SPS) so that virtual worlds such as MMOGs [...] can be built more scalably.
    Existing virtual worlds rely on static resource provisioning and partitioning that are expensive to deploy and have inherent scalability limits. VAST intends to provide an [...] alternative that is scalable, affordable, and easily deployable.
    VAST will have these properties due to a peer-to-peer (P2P) design, so that resource nodes can be added or removed any time, and dynamic load balancing is possible. VAST relies on a Voronoi-based Overlay Network (VON), which performs neighbor discovery and spatial queries in bounded amount of time (i.e., the query time does not increase as more nodes join the system). Additionally, VAST uses VSO to perform load balancing, and VoroCast to distribute messages via forwarding."

    "[The authors] present VAST, a generic P2P overlay that provides spatial publish/subscribe (SPS) services with layers to support different VE requirements. The overlay accommodates both regular and super-peers, and evolves based on the state of the application.
    VAST takes into account the physical topology (i.e., network distance) between peers and the heterogeneity in peer resources so that requirements of different kinds of VEs are met in a practical, flexible, and efficient manner. Our analysis and simulations show that the adoption of super-peers provide a unique design space where both the required bandwidth at the server, and the average latencies among clients, can be effectively reduced, such that even a crowded virtual world region can be hosted under residential ADSL environment."
    VAST fits nicely with the Virtual Object System (VOS).

    Due to nasty foul plays and even criminal activities we substituted in the section Collaborative Virtual Environment the link:

  • University of Illinois, College of Engineering and School of Art & Design: Electronic Visualization Laboratory (EVL)

    with the correct link:

  • * ** National Science Foundation, Advanced Research Projects Agency, U.S. Department of Energy, and contributors,

    added the document:

  • Visual Proceedings, The Art and Interdiscplinary Programs of SIGGRAPH 94, VROOM,

    and marked the link with a * and **, because some contributors are under investigations or have already been convicted of infringing our copyright.

    In general, the markers * and ** will be removed if all infringing material has been removed from the World Wide Web and any other place, and our original and unique multimedia works of art have been referenced.

    As can be seen once again, our Ontologic System (OS) is thoroughly thought out and hence is so much more, specifically much more original and unique, unforeseeable and unexpected.


    22.August.2017
    Investigations::Multimedia, AI and KM
    *** Work in progresss - complete sentences and links; some links might be missing ***

  • University of Illinois: We found (two or) three projects respectively plagiarisms on the website of the Electronic Visualization Laboratory of the College of Engineering and School of Art & Design of the University of Illinois that show that some scientists, their advisers, and their funders have not referenced
  • the original and unique multimedia work of art titled Ontologic System created by C.S. and
  • to some extent the other original and unique multimedia work of art titled Ontoscope also created by C.S.,

    and instead either used

  • uncommon wording or
  • even had not tried at all to blurr their traces

    to mislead the public deliberately.
    At least one project even proves that we have not only common plagiarists, who infringed our copyright, but criminals, whose goal is not to just create a scientific paper by copying parts of our Ontologic System (OS) but to create a fake timeline for damaging the reputation of C.S. and our company as much as possible and deleting our existence.

    Because this case is relatively huge we have broken this investigations down into two parts:

  • The first part is about a project focused on essential parts of the OntoBot, OntoScope, and Ontologic File System (OntoFS) software components.
  • The second part is about an older project, that indeed is prior art on the one hand but on the other hand is presented in a suspicious way, and about a project that on the one hand seems to have been started before we publicated our OS in the end of October 2006 but on the other hand was misused to steal essential parts of our OS and our Ontoscope hardware component by extending it with a third part to mislead the public and manipulate the timeline as well.

    Nevertheless, in all cases the authors and their advisors were too incompetent, so that we were able to convict them not only for infringing our copyright but also for conducting infringements of our right that go beyond a simple fraud, were realized in a group, and were done with the goal to gain personal and economical advantages, which renders them as serious crimes.

    In this first part of this investigation we have read several publications, including a webpage, scientific papers, and posters, quoted the relevant sections of them, and gave related comments and links to our original sources.
    Webpage with a short summary authored by Yiwen Sun, Jason Leigh (Director, EVL), Andrew Johnson (Associate Professor, CS / EVL), Barbara Di Eugenio (Associate Professor, CS), and Luc Renambot (Research Assistant Professor, CS / EVL): "[The application] is a semi-automated visual analytic system that is guided by a conversational user interface to allow users to verbally describe and then manipulate what they want to see. Natural language processing and machine learning methods are used to translate the imprecise sentences into explicit expressions, and then a heuristic graph generation algorithm is applied to create a suitable visualization".

    First paper authored by the plagiarists Yiwen Sun, Jason Leigh, Andrew Johnson, and Sangyoon Lee: "[The application]: A Semi-automated Model for Translating Natural Language Queries into Meaningful Visualizations [We have an automated model/executeable model, such as an agent (executable UML) or the related part of our OntoBot, Natural Language Processing (NLP), meaning/semantics, as well as Visualization.]", "[The application], an attempt at a semi-automated visual analytic model that is guided by a conversational user interface to allow users to verbally describe and then manipulate what they want to see. We use natural language processing and machine learning methods to translate the imprecise sentences into explicit expressions, and then apply a heuristic graph generation algorithm to create a suitable visualization. [See the sections Natural Language Processing, Intelligent/Cognitive Interface, and Visualization, as well as the OntoBot and OntoScope software components.]", "The goal is to provide a streamlined experience to nonexpert users, allowing them to focus on using the visualizations effectively to generate new findings. [See the point Problem Solving Environment (PSE) listed on the webpage Overview and the related sections of the webpage Links to Software of the website of OntoLinux.]", "[...] a 2007 National Science Foundationworkshop report on "Enabling Science Discoveries through Visual Exploration" noted that "there is a strong desire for conversational interfaces that facilitate a more natural means of interacting with science." [See again PSE and the related sections in the Links to Software.]", "[...] spoken dialog [...] [See section Natural Language Processing once again.]", "This inspired us to adopt a conversational interface in the semi-automated visual analytic model. [As we show here, the inspiration was our Ontologic System OntoLinux, obviously and definitely. See also the project Visualytics (Visual Analytics) of the Innovation-Pipeline of Ontonics.]", "In this paper, we propose a two-step process to translate a user's verbal description to a representative visualization: first, parse the imprecise queries into explicit commands using natural language processing and machine learning methods; then, determine an appropriate type of visualization based on the commands and data properties automatically. [Obviously, OntoBot and OntoScope software components. See also the Feature-Lists and the section Softbionics and Artificial Intelligence 3 of the webpage Terms of the 21st Century.]", "In this initial work we limit the types of visualizations that can be generated to standard 2D graphs and plots. However in the future we fully intend to extend this to accommodate complex visual representations such as those commonly used in scientific visualization (such as volumetric or streamline visualizations). [See OntoScope software component section Visualization of the Links to Software.]", "The primary contributions of this research include: 1) the incorporation of a conversational interface and natural language parser to allow for natural language input rather than grammar based commands; 2) the development of an algorithm to automatically generate graphs based on the classification of visual analytic tasks; 3) the development of a Simplified Visualization Language (SimVL) as an intermediate expression for a user's specification, which is precise, and easy to convert in a representative graph. [Point 1 is Natural Language Processing again. Point 2 is something like graph grammars and PROgramming with Graph REwriting Systems (PROGRES). Point 3 intermediate expression is related with OS feature of "natural language and image processing, and logics". See also the comment in the OntoLix and OntoLinxu Website update of the 23rd of April 2016 and 12th of May 2016, as well as the Investigations::AI and Knowledge management of the 10th of June 2016 and 27th of December 2016 (keyword SVG).]", "[...] VisQL specification language [...] [See also PROGRES once again, that is listed in the section Multiparadigmatic Computing of the Links to Software.]", "[...] demonstrated a semantic model for automatic transfer function editing in volume rendering applications [...] [See OntoBot and section Visualization]", "Another interesting approach [...] simplifies the creation of customized visualization applications with a pipeline. Once the pipeline is constructed, the application can be generated automatically. [See the OntoScope software component which is based on the OntoBot and the general pipelines of Graphics Processing Units (GPUs) and related 3D graphics libraries.]", "A number of speech-based interfaces have been developed that help users to access information using a conversational paradigm. [...] worldwide weather forecast information over the phone using spoken dialog [...] travel planning, health information access [...] [See section Natural Language Processing once again to find for example the dialogue management in the Mercury flight reservation system used for travel planning.]", "[... A Multi-Modal Natural Language Interface to an Information Visualization Environment] was the first to integrate a natural language interface into an existing information visualization system. [The] work takes the natural language question, determines the appropriate database query, and presents the results to the user. [Important to note here is the point that we with our OS have generalized the whole task and this prior work completely, including visualization and visual analytics (see also the Clarification of the 26th of July 2017). Therefore, the plagiarists have only copied our general approach in parts. In addition, presenting prior art, that is also included in our OS, does not mean that it is allowed to use our OS as a blueprint and it also changes the situation in relation to an ordinary technological progress respectively a fair use of our works, as we discussed in the Clarification #1 of the 21st of July 2017. At this point we always mention the Pictures of the Day of the 25th of July 2013 and the related comment with the judgement of Judge Birss.]", "Though the idea of using a conversational interface to craft visualizations is not new, our work addresses a growing trend toward in this area, as witnessed in the recent work of Wolfram Research. [We have convicted that company of infringing our copyright already in the past. What we see here is that the publics is deliberately misled about the true origin of all those plagiarisms.]", "[...] input parser will interpret the sentence as a request for a relationship graph [...] This interpretation is expressed as SimVL commands and entered into the graph generator [...] Properties of various various graph types [Suddenly, we have a relationship, a graph, graph types, and so on. In fact, here we are at graph grammars for graph generation, PROGRES, and eventually our OntoBot.]", "The reasoner uses this information to determine that the most appropriate visualization will be a scatter plot. [Bingo!!! OntoBot and OntoScope. At this point we could stop the investigation already, but we will provide as much as possible evidences.]", "The essential parts of our framework are two steps: input parser and graph reasoner. [Obviously, it is the OntoBot. See also section Multiparadigmatic Computing once again.]", "The translation of user's imprecise specification is based on a natural language parser imbued with machine learning algorithms that are able to make reasoned decisions automatically. [OntoBot, Feature-Lists and the section Softbionics and Artificial Intelligence 3]", "[...] apply a supervised learning method in this space to predict the class of the task [...] [See Softbionics and Artificial Intelligence 3 and webpage Ontologic Applications.]", "[...] nine-dimensional space [...] [Compare with the designatio n-Dimensional OS (nDOS) of OntoLinux.]", "[...] decision tree learning method to classify the query [...] [See OntoBot and Softbionics and Artificial Intelligence 3 or more precisely Machine Learning (ML).]", "[...] the graph reasoner works as a smart agent carrying out a similar reasoning process autonomously. The rules of reasoning can be divided into three categories [...] [OntoBot and section Intelligent/Cognitive Agent of the webpage Links to Software. We also have the 3³ Theme of C.S. here.]", "[...] - Find [...] - Find [...] - Find [...]", "[...] conversational interface [...] a more active feedback from the system will be needed, for example suggesting related queries as well as associated results to help the user find their solution. [See Natural Language Processing and Ontologic Applications.] ", "[...] Metadata is needed for providing context to parsing [...] One solution might be usingWordNet[16] to find Synset for each attribute. [WordNet is linked in the seciton Natural Language Processing.]", "Another field needed in the metadata will be the Units of the data. [We already use ontologies for domain knowledge, which have been introduce to solve such metadata problems.]", "We integrated natural language processing and automated graph generation algorithm to make the implicit sentence semantics explicit in the final representation. [Let us correct this statement and say they have stolen our intergration of natural language processing and automated graph generation algorithm to make the implicit sentence semantics explicit in the final representation.]", and "Future directions in this research will include more active reaction from the system, such as suggestion of related queries in response to unclassified questions [...] [Suggestions is another word for recommendations in the context, which leads us to OAs.]".
    Eventually, it is a part of our OS and an Ontologic Application.

    Second paper authored by the criminal plagiarists Yiwen Sun, Jason Leigh, Andrew Johnson, and Barbara Di Eugenio: "[...] [...]", "Even a decade ago this would have seemed far-fetched, but today we are seeing renewed interest in the use of natural language as an interface to computing. [Yes indeed, and the proven reason for this renewed interest is the publication of our Ontologic System in the end of October 2006, as will become easily apparent with this investigation even for non-experts.]", "Siri, the intelligent personal assistant on iPhone 4S [...] [We have proven several times that a small company and the company Apple have stolen the combination of this Intelligent Personal Assistant (IPA) with a mobile device from the webpage of our OS. In fact, it is listed in the section Intelligent/Cognitive Interface of the webpage Links to Software as PAL - Personalized Assistant that Learns and CALO - Cognitive Agent that Learns and Organizes.]", "The field of natural language processing has made great strides in the last decades, with a variety of models that are able to understand the meaning of sentences in recommender systems, educational technology and health applications. [See the webpage Ontologic Applications, the sections Natural Language Processing, and the educational and health project in the Innovation-Pipeline of Ontonics.]", "This inspired us to consider the use of a conversational interface for the automatic generation of visualizations. [This is definitely not the case, because we have here a plagiarism of our OS OntoLinux.]", "Note however that in this work we are not simply translating explicit visualization commands [...] Instead the expectation is that our approach will enable a user to ask deeper questions about data [...] without having to follow or memorize a strict grammar or command structure, as has been in the past. [Guess what we did more than 5 years before them?]", "While the initial prototype produces information visualizations, we will also explain and show through a case study how the approach is conceptually extensible to scientific visualizations as well. [See OntoBot and OntoScope software components and section Visualization of the webpage Links to Software]", "[...] Mackinlay's APT system [Automating the Design of Graphical Presentations of Relational Information] [We have discussed many times the relational foundations of our OS. See the OntoFS software component for example.]", "[...] composition algebra to describe various graphical encoding and developed expressiveness and effectiveness criteria to ensure meaningful design [...] [This sounds a little like quality management.]", "[...] [Interactive graphic design using automatic presentation knowledge] extended the concepts of APT [...]", "[...] automatically create visual discourses - a series of animated visual illustrations for explaining complex information to users. His work was extended [...] which used an AI planning-based approach to automatically design and create such discourses [...] [At this point it becomes already obvious that our development process has been recapitulated only and documented in a way that should mislead the public about the true origin of our works. Once again, the existence of prior art and to repeat its combination in a way as we did before with the composition of our Ontologic System Architecture (OSA) does not avoid a causal link with our original and unique multimedia works of art titled OS. See the judgement of Judge Birss once again.]", "In recent years, related approaches have targeted specific application domains, rather than proposed a more general methodology. [Obviously, this is also wrong, because we always said that our ontologic paradigm does this generalization to the maximal extend that resulted even in the Zero Ontology or Null Ontology represented even by a fractal sign O#.]", "[...] [Mapping Communicative Goals into Conceptual Tasks to Generate Graphics in Discourse. Knowledge-Based Systems], a system that automatically summarizes transportation schedules as text and graphs. In this system, they proposed a set of rules to map communicative goals to low-level operational tasks [...]", "[...] [From Web Data to Visualization via Ontology Mapping] proposed an approach for automatic generation of visualizations via ontology mapping and applied the approach to web data for music. The web data was first mapped to domain ontology, and then projected to visual representation ontology, which was finally depicted as a specific visualization using external visualization toolkits. The mapping between domain and visual representation ontologies was represented by semantic bridging ontologies, which were defined from expert knowledge. By comparison, our approach uses a more flexible metalearning algorithm to automatically translate language into visualization intentions. [Bingo!!! Furthermore, we have here parts of the feature of the Bridge from NI to AI, which is already as much flexbile as possible, as it has been explained by us with RDF triple stores and OWL data stores in relation with our OntoFS software component and with other OS features.]", "The key criticism cited was that problem-solving and recall competed with speech articulation and interpretation in their use of working memory. However, Dennett [Consciousness Explained] argues that problem solving is in fact enhanced when more areas of the brain are engaged such as when you are speaking and hearing your own words (i.e. thinking a problem out loud). [Bingo!!! Here we have Problem Solving Environment (PSE) listed on the webpage Overview and the sections Intelligent/Cognitive Agent, Intelligent/Cognitive Interface, and so on, as well as reflection and The Proposal.]", "Language interfaces in a variety of settings, from educational technology to health care, have been shown to improve the user's experience and performance [The Integrality of Speech in Multimodal Interfaces, Multi-modal presentation of medical histories, Knowledge co-construction and initiative in peer learning interactions, Persuading users through counseling dialogue with a conversational agent]. [And here the criminal authors aggressively and deliberately mislead the public about the Multimodal User Interface (MUI) and the conversational OntoBot of our OS. See also the sections Natural Language Processing, Intelligent/Cognitive Agent, and Intelligent/Cognitive Interface.]", "Technically, the considerable renewed interest in the use of speech and natural language as an interface to computing is due in large part to significant computing power and new powerful statistical models that are brought to improve speech recognition and natural language interpretation. Google's director of research Peter Norvig, believes that being able to converse with computers is “the future”. Natural Language Processing, the processing of language beyond the recognition of words in speech, also made great strides in the last decade, with a variety of models that are used to understand the meaning of sentences, as shown by successes such as that of IBM Watson which defeated the two best human champions in Jeopardy! and Wolfram Alpha - a knowledge engine developed by Wolfram Research that is capable of responding to natural language based questions with computed answers and relevant visualizations instead of a list of web pages as a traditional search engine provides. Additionally, a number of speech-based computational models have been developed that help users to access information using a conversational paradigm. [Here the criminals deliberately list all those entities that we have convicted of stealing our intellectual properties related with the OS. This has been done to deliberately mislead the public and goes beyond a common infringement of copyright.]", "Recent work in the information visualization community has applied various design principles to the automatic generation of visualizations though none had used natural language nor approached scientific visualizations. Articulate attempts to combine these advanced techniques together in exploring how to automatically translate natural, and potentially ill-defined, conversational language into meaningful visualizations of data in a generalizable way [...] [And this only adds more evidence for the crime investigated and documented here. It is absolutely clear that this is a serious criminal lie because the authors do know our OS OntoLinux from which they have stolen essential parts of the presented application.]", "[...] the approach involves: extracting syntactic and semantic information from a verbal query; applying a supervised learning algorithm to automatically translate the user's intention into explicit commands; and finally, determining an appropriate type of visualization based on the translated commands and properties of the meta-data [...]", "The Input Translator takes natural language queries spoken by the user and translates them into a set of commands that follows a precise grammar, which we call SimVL (Simplified Visualization Language) - analogous to small subset of Wilkinson's Grammar of Graphics [...]. [OntoBot with rewrite rules and PROgramming with Graph REwriting Systems (PROGRES), and OntoScope.]", "[...] meta-data properties are gathered such as data units and semantic relations, which provide a brief context for interpreting the data. To obtain the semantic relations, we use WordNet [...], a lexical database that groups English words into sets of cognitive synonyms (synsets) and expresses various semantic relations between these synsets. [Obviously, this has been stolen from the webpage of our OS OntoLinux as well, as can be seen with the sections Semantic (World Wide) Web, Natural Language Processing, and Intelligent/Cognitive Agent.]", "The keywords in each dictionary are selected according to empirical knowledge and domain vocabulary. [Domain vocabulary leads to ontologies.]", "[...] shallow linguistic features were found that might help the classification of the query, for example clause type, query contains a comparative or superlative adjective or adverb, query contains a cardinal number, and query contains a quantifier. [Somehow we have the impression that this statement is about the basic properties of (mostly) being shallow- and deep-inferencing listed on the webpage Overview.]", "Three widely used supervised learning algorithms were considered for this classification job: Decision Tree, Bayesian Network and Support Vector Machine. Each model generated by one machine-learning algorithm can be regarded as an expert." [See the sections Pure Rationality and Softbionics and Artificial Intelligence 3 of the webpage Terms of the 21st Century.]", "It is more reliable to take into account the opinions of several experts rather than relying on only one judgment. Therefore, we combined a decision tree inducer, a Bayesian network learner, and a support vector machine to form a meta-learner, which takes the majority votes from the three basic classifiers. [Obviously, this is what our OntoBot does with the agent systems, reasoners, and so on listed on the webpage Links to Software, as also explained in Ontologica, Ontologico, Ontologics of the 21st of May 2016. In addition, we have here the sections Pure Rationality and Softbionics and Artificial Intelligence 3 of the webpage Terms of the 21st Century once again. By the way, we have here also a reference to the 3³ Theme of C.S. and the movie "Minority Report", which we also discussed in relation with our OS in the past (see for example the OntoLinux Further steps of the 28th of March 2012. Therefore, we have the next evidence for the infringements of our rights by the criminal authors.]", "The algorithm employed to select candidates for suggestion is based on a context-aware meta-classifier. [This is the OntoBot software component, sections Intelligent/Cognitive Agent and Intelligent/Cognitive Interface, and Ontologic Applications.]", "[...] formal grammar [...] [This is a reference to the section Formal Modeling of the webpage Links to Software somehow.]", "The Visualization Executer [...] works as an agent carrying out a similar reasoning process. [OntoBot and section Intelligent/Cognitive Agent]", "Speech recognition is achieved using the Sphinx toolkit [...] [In the meantime, they even changed form the Windows system to the speech recognition toolkit that we have listed in the section Natural Language Processing of the webpage Links to Software.]", "The first step in the expansion of [the plagiarism] towards [... an] application is to understand their usage scenario. [Obviously, this is common software engineering, specifically the phase to create the requirement specification. This leads us to the section Formal Modeling of the webpage Links to Software. Again, we can see with this point how detailed the plagiarism and aggressive the stealing is realized.]", "[...] 3D visualization [...] Finally, in the Visualization Executer, adaptions are made in the graph reasoning algorithm to accommodate 3D views. In the current prototype, VTK (the Visualization Toolkit) [...] was employed to visualize scalar data. [Bingo!!! Here we have the OntoBot and OntoScope software components as well as the section Visualization of the webpage Links to Software once again, which proves the deliberately conducted criminal looting of our intellectual properties.] ", "Since the framework of [the illegal plagiarism] is composed of distinct modules, each of them handles a single process such as data processing, language parsing, or graph generation; it is very flexible to be applied to different domain science by adjusting certain modules in the framework. [Modular architecture]", "Another direction in this research is to provide a textual or verbal explanation to the user on how and why the resulting visualization was derived by the system. When answering the user's questions, which may include requests for information about how to visualize the data and requests for clarification on what the visualization represents, Articulate needs access to its own knowledge about the implementation of the current visualization, such as the mapping from data attribute to visual primitives. [Bingo!!! This is the next undeniable evidence of the serious criminal acting of those entities. Non-expert might not see it directly, but here we have the reflective feature of our OS and also the Bridge from NI to AI that we introduced, so that the system can provide for example this kind of rationality==explanation about its actions to a user.]", "In terms of interaction modality, enabling gesture input as a complementary interface to voice input is a promising area to investigate. With devices such as a multi-touch screen and optical trackers [...], it will be relatively easy to extend [the plagiarism]'s framework with the gesture interaction. [Bingo!!! Here we have the evidence that our Multilingual Multimodal Multiparadigmatic Multidimensional Multimedia User Interface (M⁵UI) has been stolen as well. The related doctoral thesis should be revoked.]", "Unlike traditional visualization tool, this approach brings together natural language processing, machine learning and visualization techniques, to enable the interaction with speech [...] [Once again we have to make very clear that this approach is a part of our original and unique multimedia work of art titled Ontologic System and created by C.S..]", "[...] three-fold [...]", "[...] the introduction of a meta-learning algorithm to automatically interpret a user's intent based on linguistic features. We devised a multi-dimensional feature space to represent both syntactic and semantic characteristics of a verbal query. [The next evidence is given with the term multi-dimensional because this reflects our Multilingual Multimodal Multiparadigmatic Multidimensional Multimedia User Interface (M⁵UI) and copies our statement that OntoLinux is also an n-dimensional Operating System (nDOS).]", and "[...] direction for the future investigation of the automatic generation of data visualization in a natural interaction environment. [And at the end, we get a forecast of more stealing with this reflection of our the Bridge from NI to AI and other features based on Natural User Interfaces (NUIs).]".
    That is only shameless and disgusting.

    A first poster created by the plagiarists Jillian Aurisano, Abhinav Kumarn, Alberto Gonzalez, Khairi Reda, Jason Leigh, Barbara DiEugenion, and Andrew Johnson: "[...] ... [...]", "[...] visual data exploration involves repeated cycles of visualization construction and interaction, as well as reasoning across many visualizations generated over the course of an exploratory session. A 'conversational interface', which maintains a dialog with the user through natural language and gestures, could support these complex tasks. [In comparison to the two other documents investigated before, we can see once again that the looting of our intellectual properties related with the OS has been intensified once again. The simple speech interface has become a conversational interface or dialogue management system with a Multimodal User Interface (MUI).]", "Natural Language[,] Gesture[,] Window Management [We also can see as another addition with a window management, which is also included in the OntoBot software component, which in its initial version is based on the programming language Pop-11 and comprises the interface between Pop-11 and the X Window System (RCLIB) respectively Wayland included in the OntoGraphics software component. This also comprises User Interface (UI) functions like zoom and pan.]", and "Data Analysis Scenario [Shown is a diagram that is called in a future poster a knowledge base.]".

    The third paper written by the criminal plagiarists Abhinav Kumar, Jillian Aurisano, Barbara Di Eugenio, Andrew Johnson, Alberto Gonzalez, and Jason Leigh: "Towards a Dialogue System that Supports Rich Visualizations of Data", "[...] support fullfledged dialogue between a user and a system that transforms the user queries into visualizations. So far, we have collected a corpus where users explore data via visualizations; we have annotated the corpus for user intentions; and we have developed the core NL-to-visualization pipeline. [Again, we see an advancement into the direction of our OS.]", "Creation and collaboration: Engaging new audiences for information visualization. [See for example the Ontologic Collaborative Virtual Environment (OntoCOVE) software component.]", "[...] a fullfledged conversational interface that will automatically generate visualizations [...] [See the combination of our OntoBot and OntoScope software components and the sections Natural Language Processing and Visualization of the webpage Links to Software of the website of OntoLinux.]", "[...] much work is devoted to multimodal interaction with visual representations [...], but not to automatically generating those visual representations. [We all do know that this is wrong, because our OS with its OntoBot and OntoScope software components does it as well.]", "When [an application] the closest to our work, cannot resolve an ambiguity in an NL query, it presents the user with selection widgets to solve it. However, only one visualization is presented to the user at a given time, and previous context is lost. [The authors] compares [the application] to IBM Watson Analytics, that allows users to interact with data via structured language queries, but does not support dialogic interaction either. [Have our fans and readers noticed what is going on here? The plagiarists a sneaking around our OS like a snake in the grass.]", "[...] a collaborative large-display middlewear, to drive the display wall [...] [As we mentioned before, one feature of special interest is the Ontologic Collaborative Virtual Environment (OntoCOVE) software component.]", "The pipeline in Figure 2 illustrates how [the application] processes a spoken utterance, first by translating it into a logical form and then into a visualization specification to be processed by the Visualization Executor (VE). For create/modify visualization requests, an intermediate SQL query is also generated. [The looting continues with an SQL database. We mentioned in a comment to a quote above already the relational foundation of our OntoFS, which by surprise (not really) has in one varinat SQLight as one of its basic software library. Also notice the use of the acronym VE which prepares the stealing of a further feature of our OS.]", "We begin by parsing the utterance we obtain from the [...] Speech API into three Natural Language Processing structures. [An] Natural Language Processing [...] is used to obtain PropBank [...] semantic role labels (SRLs), which are then mapped to Verbnet [...] and Wordnet using SemLink [...] The final formulation is the conjunction [of several clauses]. [Semantic role labelling, sometimes also called shallow semantic parsing, is a task in natural language processing. It is related with the basic properties of (mostly) being shallow- and deep-inferencing listed on the webpage Overview.]", "If the classifier assigns to an utterance the window management type, a logical form along the lines described above will be generated [...] keyword extraction is used to determine whether the window management instruction relates to closing, opening, or repositioning; [As we mentioned in a comment to an investigated poster before, window management is also stolen. But this is not the end of the looting.]", "If the utterance is classified as a request to create or modify visualizations, the logical form is used to produce an SQL query. SQL was partly chosen because the crime data we obtained from the City of Chicago is stored in a relational database. [We do not buy that explanation but claim that the crime data has been selected specifically for this and other reasons.]", "We distinguish between filter and aggregate based on types stored in the KO, a small domain-dependent knowledge ontology. The system is re-configurable for different domains by updating the KO. [SuperBingo!!! This is again an evidence for the conducted crime that non-experts understand very easily.]", "[...] the VE uses Vega[: A Visualization Grammar] [...] [Once again we are at graph grammars and suchalike.]", "Annotation. We are focusing on referring expressions (see below), and on the taxonomy of abstract visualization tasks [...]. This taxonomy, which includes why a task is performed, [...] [Here we have the Pure Rationality once again.]", and "Dialogue Manager / Referring Expressions. We are developing a Dialogue Manager (DM) and a Visualization Planner (VP) that will be in a continuous feedback loop. [...]".

    A second poster created by the plagiarists Jillian Aurisano, Abhinav Kumarn, Alberto Gonzalez, Jason Leigh, Barbara DiEugenion, and Andrew Johnson: "Toward a Conversational Interface for Visual Data Exploration", "A 'conversational interface' which maintains a dialog with the user through natural language and gestures, could allow users to engage in repeated cycles of visualization generation and modification, asking questions directly through speech. [As we mentioned before the system becomes more and more the same as the related part of our OS.]", "Architecture [-] WebSpeech API [-] Natural language to vis pipeline [-] parsing and processing [-] logical form [-] question type classifier [-] knowledge base [-] history manager [-] sql and visualization specification generation [-] window management specification [The plagiarism has also a temporal component as another addition.]", "Visualizations were executed using [library].js, which leverages principals from grammar of graphics. Results are displayed in a multi-windowed, web-based environment. [Another looting is happening by this web-based service, which points into the direction of the Semantic (World Wide) Web. We also mentioned before that the criminals are trying to loot as much as possible in a systematic way respectively following a more comprehensive plan.]", and "Resolving references to on-screen visualizations and objects through speech and gesture [This is our Multilingual Multimodal Multiparadigmatic Multidimensional Multimedia User Interface (M⁵UI) of the OntoScope component.]".
    For the record: Convicted!!!

    The positive aspects, if they can be designated in this way at all, are the following:

  • The plagiarists are experts in the fields of visualization and Virtual Reality (VR), and advanced applications in these fields (see for example the document SIGGRAPH '94, VROOM listed in the section Collaborative Virtual Environment) and clearly say all the years that they are not aware about our Ontologic System (OS). Because we have proven that our OS exists since around 11 years the logical implication can only be that we are first.
  • Interestingly, we listed the VROOM exhibition because it is about Virtual Reality (VR), but the publications do not mention VR or Virtual Environment (VE) at all. This implies that the experts in this field have not found prior art that can be defraudingly exploited for creating the fake timeline in this direction despite this would fit much better with the competences of them.
  • In addition, the plagiarists have found some related works but clearly say all the time that these works have deficits that their plagiarism has not. A logical implication of the first point is that our OS has not these deficits.
  • Moreover, because of the second and third points the logical implication can only be that our OS is original and unique, and also was unforeseeable and unexpected at its time of publication even for the highly skilled experts.

    Last but not least, we think that this shameless and disgusting attack on the goodwill of the whole scientific community and the reputation of us is a case for the prosecutor.

    In general, we do not know what is going on in the broken brains of such entities, that we are observing in politics, sciences, and industries, but such an audacity and criminal energy makes one speechless once again.


    23.August.2017
    Website review
    We might have a little problem: We found a very suspicious paper that somehow seems to be relevant in relation with some parts of our copyright claims, because it mentions semantic web, grid computing, semantic grid, multi-agent system, conversational agent, and even cognitive agent and cognitive grid. Either we have forgotten the paper or found it only today, or something else happened.

    Important to note is that our way of argumentation does not completely implode but we might adjust some statments a little. In addition, everytime we might have such a setback the scope and limits of our claims sharpen. Also keep the judgement of Judge Birss in mind respectively if a causal link with our original and unique works is not avoided then we still have a copyright infringement.

    For sure, we do apologize for any mistakes that may have happened, but would also like to mention that: You can't make an omelette without breaking eggs.
    Nevertheless, we have to conduct a second review of related clarifications and investigations, which we will do together with the first review announced on the 5th of March 2017.

    Clarification
    In relation with the document about the cognitive grid with conversational agent (see the Website review of today) we would like to make some statements. So far we have found in that document the methods and fields of

  • introspection,
  • Artificial Intelligence (AI),
  • meta-reasoning (e.g. Belief-Desire-Intention (BDI) agent architecture), and
  • cognitive computing (e.g. State operator and result (Soar)),
  • learning,
  • Problem Solving Environment (PSE),
  • planning and proactivity,
  • spoken dialog system (e.g. conversational agent), and
  • self-explanatory

    all in relation with semantic grid computing and therefore potentially only a part of our Ontologic Net and Ontologic Web, but we have found:

  • no reflective computing,
  • no trust and verification,
  • no operating system including network component,
  • no virtual machine,
  • no capability-based operating system kernel,
  • no agent-based operating system and multi-agent operating system (see Agent-Based Operating System (ABOS) referenced in the section Exotic Operating System of the webpage Links to Software of the website of OntoLinux),
  • no ontology-based agent-based system, and ontology-oriented agent system and semantic agent system (see Nuin and Ontologies in Agent Architectures referenced in the section Intelligent/Cognitive Agent, and UML-Based Ontology Modeling for Software Agents referenced in the section Formal Modeling of the webpage Links to Software),
  • no agent-based dialog system,
  • no computing with words, images, and other modalities,
  • no smart contract,
  • no Internet of Things (IoT),
  • no Cyber-Physical Systems (CPS),
  • no Virtual Object System (VOS),
  • no Content-Addressable Memory (CAM), Content-Addressable Storage (CAS), and Content-Addressable Network (CAN),
  • no Information-Centric Networking (ICN) and Content-Centric Networking (CCN),
  • no Multimodal User Interface (MUI) respectively Multimodal Dialogue Management System (MDMS) but only keyboard, mouse, voice,
  • no viusalization, sound, multimedia, AR, VR, MR,
  • no Business Process Management (BPM), Workflow Management (WfM), Quality Management (QM), Product Lifecycle Management (PLM), Computer-Aided technologies (CAx),
  • no portable devices respectively only robots, and
  • no Ontologic uniVerse (OV).

    Furthermore, questions like

  • conversational agent for grid management vs. conversational grid vs. conversational agent system executed on the grid,
  • semantic grid agent vs. semantic agent grid,
  • Multi-Agent Systems (MASs) in the semantic (world wide) web vs. ontology-based agent-based system vs. ontology-oriented agent system and semantic agent system
  • etc.

    have to be discussed and answered, and The Proposal have to be considered as well, the latter leads us straight to the Pictures of the Day of the 25th of July 2013 and the related comment with the judgement of Judge Birss.
    At this point, we can already say that in the already upcoming system landscape the cognitive grid is an isolated layer or tier between the operating system, server, and application layers or tiers, and eventually an unconnected island that cannot be inhabited or even accessed by mobile devices (see also the comment OS too large to steal of the 15th of May 2016).

    OntoLix and OntoLinux Website update
    In the Further steps of the 5th of July 2017 we said that "a smart contract can be formulated in any language in general" and listed some specific languages as examples, which we also already used in the fields of Product Lifecycle Management (PLM) and Computer Aided Engineering (CAE).
    In this context, we would like to add that

  • on the one hand PLM comprises
    • Systems Engineering (SE),
    • Product and Portfolio Management (PPM),
    • Computer-Aided technologies (CAx),
      • Computer-Aided Design (CAD),
      • Computer-Aided Industrial Design (CAID),
      • Computer Aided Engineering (CAE), and also
      • Computer-Aided Software Engineering (CASE), and
      • Computer-Aided Manufacturing (CAM), as well as
      • Computer-Aided Production Engineering (CAPE) or Computer-Aided Production Planning (CAPP/CAP), and
      • Computer-Aided Quality (CAQ) Assurance,
    • Product Data Management (PDM),
    • Manufacturing Process Management (MPM),
    • Collaborative Product Development (CPD), and
    • Maintenance, Repair and Operations Management (MRO)

    and
  • on the other hand our Ontologic System Architecture (OSA) integrates all in one

    (see the webpage Overview). Said this, it should be obvious that we also utilize the languages listed in the Further steps of the 5th of July 2017 and the approach of the smart contract in the same way if required or/and useful in all the other fields listed above as we already did with domain-specific languages, ontologies, and controlled vocabularies in general and with for example the OntoCAx software component in particular.

    Accordingly, we

  • added these fields and also the new fields of Operations Management (OM), Business Process Management (BPM), and Workflow Management (WfM) to the related points on the webpage Overview,
  • also substituted the point Total Quality Management (TQM) with Quality Management (QM), and sorted the existing point TQM and the new point International Organization for Standardization 9000 (ISO 9000) into it, and
  • expanded the point Mediated Reality Environments (MedREs) by adding the point Augmented Virtuality Environment (AVE), made it the upper class, and sorted the existing points Augmented Reality Environment (ARE), Virtual Reality Enviornment (VRE), and Mixed Reality Environment (MRE) into it.

    The reason why we listed TQM at first is very simple to understand: It is related with the United States Department of Defense and sounds better.

    OntoLix and OntoLinux Further steps
    We took a quick look at the multiparadigm, metaprogramming language Racket, which was formerly known as PLT Scheme, is related with Lisp, and utilized for creating domain-specific languages for example, and thought once again about

  • extending the SimAgent Toolkit of our OntoBot with such a programming language, though the ability for metaprogramming is already included in the OntoBot through Maude, and
  • combining domain-specific languages with ontologies for creating ontology-specific languages respectively ontologic languages

    as part of our ontology-oriented automatic multilingual multimodal multiparadigmatic multimedia multidimensional programming respectively Ontologic Programming (OP) paradigm (take the one that most fit your taste).

    Furthermore, we realized the integration of the Workflow Management System (WfMS) with the OntoBlender software component in accordance with our Ontologic System Architecture (OSA) and simulated the execution of basic functionalities of our Ontologic System (OS) that are representative for the whole OS.

    We also improved the presentation of the spoken dialogue management system respectively spoken dialog multi-agent system and its vast range of ontology-based, executable vocabularies in the OntoBlender and applied it on the OntoBlender itself.
    In the next development steps we will realize the

  • mutual integrations of the
    • Business Process Management (BPM) ,
    • Workflow Management (WfM),
    • Product Lifecycle Management (PLM) in some first parts, and
    • Quality Management (QM)
    and
  • further integration of their integrations with the OntoBlender.

    It is like playing with a building kit for young and old children.

    Moreover, we also realized how an optimization of the OntoBase and OntoFS software components can be implemented by exploiting the functionality of the OntoBot in accordance with our OSA.
    The result meets our expectations, which is that our data stores are at least 3 magnitude faster.
    As a consequence we can realize many advanced Ontologic Applications at all (see also the fields listed in the section Basic Properties of the webpage Overview) and we can realize many of them even locally on the many types of our Ontoscopes for example.

    iRaiment Further steps
    We have created two new smartbands.

    Investigations::Multimedia, AI and KM
    *** Proof-reading - some parts might be removed ***

  • University of Illinois: This is the second part of this investigation that we have begun yesterday.

    At first, we have taken a look on an older project that arose our interest for various reasons: "Reading and Assembling Contextual and Holistic Big Mechanisms", "The [...] system extracts (i.e., reads and assembles) causal mechanisms from research abstracts and papers. [From another source we also got the informations that the first stage is to read literature and convert it into formal representations. This means that the system is related with Natural Language Processing and Artificial Intelligence (AI).]", "The fundamental research proposed has three guiding principles. The mechanisms extracted must: (a) be runnable, i.e., they must predict the data; (b) model current uncertainty of causal relations being active given context information; and (c) be holistic, that is, they explain multiple layers of abstraction, ranging from cellular to organism phenotypes. Thus, running our model produces quantifiable probabilities for the modeled variables [...] [What we find suspicious in this case is the combination of the terms predict, model, causal relations, and holistic, as well as multiple layers of abstraction, ranging from cellular to organism phenotypes, which suggests metalevels, and also the connection to the fields of developmental biology, bioinformatics, systems biology, and quality management, and therefore to The Proposal. From another source we also got the informations that the second stage is to integrate the knowledge given by the formal representations of the first stage into computational models and the third stage is to produce experimentally testable explanations and predictions. This points to our OntoBot software component and our OAs already.]", "The [...] system will provide a platform for communicating explanation with novel visualization tools for the extracted mechanisms. [Here we have a part of our OntoScope software component and the section Visualization of the webpage Links to Software of the website of OntoLinux.]", and "We will evaluate our approach in the domain of cancer biology, by extracting signaling pathways, but our work is largely domain independent. [At this point we have cancer biology, which was listed on the webpage Links to Organizations of the website of OntoLinux (see the Websiste update of the 18th of July 2016) and signaling pathways, which reminds us of the pathway logic included in the OntoBot software component. In addition, the system is domain independent, which points to our ontologic paradigm.]".
    Somehow, that system is odd and the

  • the density of same combined concepts as well as functionalities of our OntoBot and OntoScope software components and Ontologic Applications, and the same marketing of our OS on the one hand and
  • the knowledge that we have here even two already convicted institutes

    are at least clear indicators that a continued observation of the system's development is appropriated and required. It seems to be that the Defense Advanced Research Projects Agency (DARPA) together with the University of Illinois and other entities are stealing an essential part of our Ontologic System, which is not the first time. Indeed, what is proposed as Big Mechanism is just only a large part of our Ontologic System.

    In this relation, we give the warning that we have already sighted other entities taking part in that plagiarism, so that the legal situation might not be secured as it is the case with the so-called Industry 4.0 approach (see the Clarification Industry 4.0 Special #1 and Investigations::Multimedia, AI and KM of the 22nd o f February 2017 and the Clarification Industry 4.0 Special #2 of the 24th of February 2017).

    We have also read the first 25 pages of a thesis of a second project, that has been extended in a suspicious way that reminds us of the original and unique multimedia works of art titled Ontologic System and Ontoscope, and created by C.S..

    A first webpage with a short summary authored by Robert V. Kenyon and Xun Luo: "Personal Augmented Computing Environment (PACE) focuses upon the research challenges affecting the development of applications for personal mobile devices, specifically personalized visualization and scalable human-computer interaction. [First of all, its name is a reaction on our Personal Automatic Virtual Environment (PAVE) project in the Innovation-Pipeline of Ontonics. Furthermore, it is focused on Virtual Environments (VEs) and the aspect of mobile devices has been added to the initial research goal.]", "The initial goal of PACE was to determine the effects of different visual factors on the correct size perception of virtual objects in an immersive virtual environment (VE). A set of controlled experiments were designed and conducted in EVL's virtual reality system, the CAVE. [As we said in the comment to the quote before. We guess the aspect of mobile devices has been added after the start of Ontologic Systems (OSs) OntoLix and OntoLinux in October 2016.]", "An effective process to collect a user's hand sample images for posture profile building was proposed and implemented. The novelty of the proposed process is that it takes advantage of the synergies between mobile device and infrastructure, and uses proactive measures instead of post-processing techniques to improve sample image quality. [First of all, the synergies between mobile device and infrastructure are not new, as can be seen with Augmented Reality (AR) and process migration, which both are features of our OS (see also the Feature-Lists). The point with proactive measures is related with Ontologic Applications but provide no persuasive causal link with our Ontologic System, as it is the case with quality that can be found in the webpage Overview.]", "[...] vision-based hand detection and recognition system using computer clusters [...] [At this point we halten fest the aspect of distributed computing.]", "[...] hand tracker/controller [...] was implemented and integrated as the interface device for a large-scale tiled display instrument [...] [Do not be confused, because the mobile device is not the hand tracker.]", and "[...] PACE also introduces a prototype personal VE: a reach-and-grasp training environment [...] [Bingo!!! Here we have the missing causal link with our Personal Automatic Virtual Environment (PAVE) and also to our Ontologic System as well as to mobile devices.]".
    What has to be said as well is the point that the webpage tells as project duration "August 16, 2005 - May 1, 2008" but the other quoted publications are from 2008 only. We guess that only the preliminary and early work of a "reach-and-grasp training environment for in-home rehabilitation of stroke survivors" is from the time before our OS was known.

    A second webpage with a summary of the project authored by Xun Luo: "Virtual reality (VR) is a technology which allows a user to interact with a computer-simulated virtual environment (VE). Since its inception it has created an impact in many fields, but has not yet gained wide acceptance to be used in a personal context. At the same time, personal mobile devices (MDs) have evolved tremendously during recent years. The deployment of MDs is becoming pervasive [...] [Once again we have a reference to our Personal Automatic Virtual Environment (PAVE) and also to our Ontologic System as well as to mobile devices. Also interestingly is the term computer-simulated virtual environment that was said to have something with simulation in the text. In fact, you do not simulate a VE but generated a VE that simulates reality or/and virtuality.]", "[...] improvements in the infrastructures supporting wireless inter-device connectivity and collaboration [...] [See the Feature-Lists and the OntoCOVE software component of our OS.]", "[...] to make the key elements of a VE, i.e. visualization and interaction, work as smoothly for MD-based systems as for desktop-based systems, three research challenges need to be addressed [...] [This is an essential feature of our OS, as can be seen with the OntoScope and OntoCOVE software components. In fact, nobody understood why we were so crazy at that time to add a Virtual Reality Environment (VRE) to mobile devices such as smartphones and tablet computers for example.]", "How to effectively allow a user to collect his / her own biometrical data to build personalized profiles? [Honestly, we do not know what the relations to the initial research goal and VE are. Somehow the relations are so edgy.]", "How to efficiently make use of the processing resources in the infrastructure for the compute-heavy tasks for a individual user, such as intelligent human computer interaction? [This also sounds like features of our OS as can be seen with the Feature-Lists and the section Intelligent/Cognitive Interface of the webpage Links to Software of the website of OntoLinux.]", "First, to understand the visual factors that make VE more like the real world, a set of controlled experiments are designed and conducted in a CAVE system. [As we said, from CAVE to MD is too unique for us that we are sure that it was copied from our OS. In the investigation of the related thesis below more similarities can be seen, which leads to a suspicious density that suggests a copyright infringement.]", "Being conducted by no other researchers before, this study helps us to better understand the role of size constancy in VE performance. [This is interesting but we do not know what "the effects of different visual factors on the correct size perception of virtual objects in an immersive virtual environment (VE)" has in common with an MD and a hand tracker.]", "While most hand posture recognizers' performance are very sensitive to hand sample image quality and require them to be taken under strictly controlled laboratory setting, by employing the process proposed and implemented by this work, the mobile device user can collect hand sample images by themselves with relative ease [...] [We are not sure but user interfaces for common personal computers based on a webcam were already available at that time. Also important to note is the point that we had already mentioned on the webpage of the Ontologic Applications the "simplifing the interface to complex applications by allowing the user to interact with them through common language, gesture, and sense" in direct relation to a mobile phone and a Personal Digital Assistant (PDA), which proves the originality and uniqueness of our OS. In fact, the hand tracker/controller becomes a gesture control in the thesis investigated below.]", "The third contribution of this work is a set of scalable computing techniques to speed up the tasks of a vision-based hand detection and recognition using computer clusters. [So once again, what has the MD lost in this research project? And the killer question is the following: Why is that vision-based hand detection and recognition system based on a high-performance computing system not utilized for the hand posture recognizer as well instead of the MD system, when the hand tracker/controller respectively vision-based hand detection and recognition, that is based on the hand sample images collected with the MD, is utilized in a VE such as a CAVE or a large scale tiled display instrument? It makes no sense at all to use the MD in this way.]", "[...] a sample application, a hand tracker/controller [...] is implemented and integrated with a large scale tiled display instrument as a human computer interaction device. [See the comment to the quote before.]", and "This work also introduces one preliminary and early work for personal VE: a reach-and-grasp training environment for in-home rehabilitation of stroke survivors. This pilot study achieved certain results and were successful to some extent. [On a similar webpage of the author we also got the additonal information that "[b]y analyzing the methods and outcome of this study, as well as working closely with domain experts, important lessons are learned with insightful ideas, which strongly motivated the need for the final approaches." So there is a pilot study with an initial approach and final approaches. This would explain the suspicious project duration dates mentioned above.]".

    In the following we quote the first 25 pages of the thesis of Xun Luo: "On the interaction side, the VE should be able to be interacted with using the modalities a user interacts in the real world, to blend itself into the user's daily life seamlessly. This means that a VE system should maximize itself in sensing the presence and status of the user [Bingo!!! Said in other worlds the VE is a reflective application based on our Caliber/Calibre and the OntoCOVE software component based on the OntoScope software component with its Multimodal Multiparadigmatic Multidimensional Multimedia User Interface (M⁵UI).]", "[...] interaction and computation components of the VR system should satisfy the size, price and power consumption requirements for portable use [...] [The combination of a Virtual Reality (VR) system with a portable device or mobile device is always an evidence for a copyright infringement in relation with our Ontologic System.]", "Because of the potential business opportunities, integration of networked environments and location-based applications has now drawn the attention of wearable system vendors. Location-based VE provides computer generated visual and audio content based on the location context of the user, thus calling for more seamless registration between the virtual world and the real world. [See the point augmented, mediated, virtual, and mixed reality environments in the webpage Overview.]", "[...] new geographical information systems that allow people to see a location using street map, satellite view, “hybrid” view that integrates the former two, and even 3D view of the panoramic camera images of the streets have been offered by major web service companies [...] [The older of the two prominent geographical information systems was launched on the 25th of May 2007.]", "The practical needs for networked VE applications also make the needs for wearable displays to increase. Compare to the immersive HMDs in traditional VEs, augmented displays suit this purpose better because the real world and VE can be optically blended to facilitate a user's experience. [Here we have again Augmented Reality (AR).]", "[...] mobile phones, personal digital assistants (PDAs) [...]", "Also, nearly all these devices exhibit the common trends towards more powerful processing units, standardized and interoperable application platforms, and natural human computer interfaces. [We are not sure where the author got the point about the natural human computer interfaces from because at the end of the year 2007 mobile devices had no natural human computer interfaces.]", "As a consequence, most applications only run on proprietary systems and universal deployment among various mobile devices is not common. [This gives us another indicator when the scientific work was done. A Linux kernel based operating system is not mentioned by the author.]", "The main human-computer interfaces on mobile device phones today are QWERTY style keyboards and touch screens. There are also devices that make use of inertial sensing [...] and touch-based gestures [...] [Remember that this was 1 year after we started the OntoLinux webpage.]", "[...] Utility Computing or more contemporary, Software as a Service and Infrastructure as a Service [...] [Utility computing is a synonym for grid computing.]", "Being different from traditional personal computers' two-dimensional visual interfaces, three-dimensional (3D) user interface is one of the most important hallmarks of VEs and should be well implemented for personal use.", "Scenario 2: A driver uses a portable GPS mounted on the car to navigate routes while driving. Using a VE, the GPS displays all the buildings along the road as 3D models. The GPS also communicate with other GPS devices in the nearby vehicles and display these vehicles in 3D models on the screen. [This sounds very familiar.]", "The Need for Natural Interaction for VR Tracking [See the webpage of the Ontologic Applications.]", "To make a VE ready for personal and mobile use, tracking module should ideally be tetherless, and able to track in 3D space. At the same time, current user interfaces are not fully suited for human-centered VEs. [See the OntoScope and OntoCOVE software components and the webpage of the Ontologic Applications once again.]", "In fact, the limitations of current human-computer interfaces hinder expansion of the VEs to serve individual uses. [See the comment to the quote before.]", "The ideal exchange between mobile devices and computer systems in the infrastructure should be both application data as well as user profiles. Mobile devices should be able to transfer its user profile to the infrastructure in a nearly transparent and online way that minimizes the user's awareness. At the same time, accesses to the infrastructure processing power, including discovery of the computation resource in the infrastructures, initialization of collaboration sessions, as well as quality-of-service control should all be automated and effectively managed. [This reminds us somehow of the basic properties listed on the webpage Overview, the Feature-List #1, the OntoCOVE software component, and the section Network Technology of the webpage Links to Software of the website of OntoLinux.]", "An English-speaking traveler is having a business trip in Tokyo and walked into a Japanese sushi bar. Unfortunately, all the menus and store signs in the sushi bar are in Japanese and the traveler cannot read them at all. Luckily, powerful computer system has been deployed in the sushi bar, and available for customer access through wireless link. So the traveler use his mobile device to take continuous video stream of Japanese menus and store signs and offloads the computer-vision based processing to the computer system in the sushi bar. The traveler's mobile device already stored his native language (English) and dietary preferences as personal profiles. Such information personalizes the image processing process. When the processed result is rendered to the user, menus and store signs are translated into English and with a “recommendation” ranking displayed next to each of them. [Bingo!!! We call such an application an Ontologic Application.]", "[...] to investigate scalable computing techniques to facilitate the synergy between mobile devices and infrastructure computer systems to implement a highperformance hand posture based tracker and controller [...] [This is also an Ontologic Application.]", "[...] The VR system that is chosen to conduct the control experiments is the CAVE Automatic Virtual Environment (CAVE) [...] [Do not confuse with our Personal Automatic Virtual Environment (PAVE).]", "[...] mobile device based VR systems [...]", "Making the users' hand capable of tracking and controlling objects in the VE will greatly facilitate the wide deployment of such systems, and push them closer towards portability and mobility. [This proves again that our OS is original and unique and was unforeseeable and unexpected at this time.]", "Hand images are to be captured, processed, and mapped to 2D coordinates as well as control commands at the rate of VR frame update. A set of hand postures are defined as symbol for control commands and when they are performed by the VE user, corresponding commands are issued to the VE.] [We are wondering if the company Microsoft has infringed our copyright in this specific field as well, because its motion sensing input device was first announced in the year 2009.]", "To investigate solutions that effectively create the synergy between the mobile device and computer systems in the infrastructure, this work aims at designing and implementing a prototypical paradigm that use the computation clusters in the infrastructure to boost the computation tasks performed by the hand tracker [...] [Where is the synergy?]", "[...] Finger Mouse, which is a freehand pointing alternative to the ubiquitous mouse. In this system, the user merely performs a pointing gesture above the keyboard. A down-looking camera is trained on the keyboard. [gesture]", "[...] algorithms to generate virtual representations, avatars, of dynamic real objects at interactive rates. Further, he presented algorithms to allow virtual objects to interact with and respond to the real-object avatars. That allowed dynamic real objects, such as the user, tools, and parts, to be visually and physically incorporated into the VE. The system uses image-based object reconstruction and a volume-querying mechanism to detect collisions and to determine plausible collision responses between virtual objects and the real-time avatars. [Mixed Reality (MR)]", "[...] real-time gesture recognition [...] contains a wireless camera [...] acoustic sensor and accelerometers [...] [real-time and gesture]", "[...] user carries a wearable computer, wear HMD and use hand as the sole input for HCI [...] Video captured from wearable camera are streamed to a desktop system (Dual-Processor Pentium III) via wireless LAN for all processing and the results are sent back to the user. At the same time a video combiner feeds the captured video back to the HMD to create augmented reality. [...] The wearable computer is used as a video terminal only. [distributed computing and Augmented Reality (AR)]", "[...] hand tracking, in a real-time manner [...] assigned gesture recognition to application [...] counts on a wearable laptop system rather than scalable computing resources to fulfill all the computation tasks, include hand detection, tracking and recognition [...]", and "[...] VR face tracker using neural network based techniques [...] techniques. By using dual mounted cameras and active IR illumination, the tracker is capable to detect and track human faces in 3D space [VR, Multimodal Multiparadigmatic Multidimensional Multimedia User Interface (M⁵UI) of OntoScope software component, and Machine Learning (ML)]".


    24.August.2017
    Clarification
    We reviewed our Ontologic System (OS) in relation with the highly suspicious paper mentioned in the Website review and Clarification of the 23rd of August 2017 and also remembered other properties of our OS with its overall integration of all in one as some kind of an ontology-based, Ontology-Oriented (OO 2), and Ontologic(-Oriented) (OO 3) system by the Ontologic System Architecture (OSA), that eventually shows once again on the one hand that there was suddenly a part of our idea once again, for whatever reasons, but on the other hand also no clue how to realize it once again, as it is exactly the case with the subjects discussed in the Website review and Clarifications of the 14th of May 2016, 5th and 6th of May 2017, and what synergies this integration makes possible.
    At this point we also recall the regulatory cycle of the Total Quality Management (TQM) system listed in the webpage Overview of the website of OntoLinux and it does not matter if the cycle is closed by design, an artificial entity (e.g. robot), a plant, or a living entity (e.g. monkey). This could be seen very well with a semantic Workflow Management (WfM) or Business Process Management (BPM) system that is neither applied for workflows related with ontology engineering, specifically the creation of an ontology, nor on itself, specifically in relation with reflective computing and self-improving.

    As consequences, the

  • semantic grid and the cognitive grid are
    • isolated layers or tiers between the operating system and server layers or tiers and the application and client layers or tiers, and
    • even not proper parts of our Ontologic Net (ON) and Ontologic Web (OW), so to say,
  • originality and uniqueness of our OS has been completely re-established again,
  • related parts of the Qualcomm patent and other patents remain void, and
  • white, yellow, or red line only has been adjusted a little but also sharpened once again, and hence devices, applications, and services such as virtual assistants, voice shopping services, smart speakers, and so on based on Artificial Intelligence (AI), Machine Learning (ML), and so on, are not out of the trouble when a causal link with our works is shown.

    Style of Speed Further steps
    We worked on the design of our last wheeled models, so to say as a recreational hobby in the field of oldtimers.

    We also worked on the design of the models of our 91x series based on our Speeder system platform (see the Further steps of the 11th of May 2017, 28th of July 2017, and 11th of August 2017).

    Investigations::Multimedia, AI and KM
    *** Proof-reading mode ***

  • Syapse: In relation with the investigation of the project of the University of Illinoise, that is related with the shameless and serious criminal plagiarism of our original and unique multimedia work of art titled Ontologic System and created by C.S. as the so-called Big Mechanism project or approach of the Defense Advanced Research Projects Agency (DARPA) (see the Investigations::Multimedia, AI and KM of yesterday), we also found many more infringing and illegal informations of the project leaders and other participants, who have stolen parts of our Ontologic System (OS) as well, which let directly to the insight that the Big Mechanism is a part of our OS. One of these criminal participants is the company Syapse that has stolen our original and unique Ontologic System Architecture. We quote from a presented poster: "Syapse [The company name already says all with its allusion to a synapse.]", "A Semantic Computing Platform to Enable Translational and Clinical Omics [The title of the file the poster is stored in already says all, because the system is based on ontologies and our Ontologic Computing (OC) paradigm, as will be proven in the following. By the way: The term omics refers to the fields in biology ending in -omics, such as genomics, proteomics, and metabolomics. Said this, we have here a reference to hospital information systems, which is a field C.S. worked in a very long time, The Proposal, and the section Human Simulation/Holomer of the webpage Links to Software of the website of OntoLinux, and the projects 21st Century Health Care Card and Holomer of the Innovation-Pipeline of Ontonics.]", "A Semantic Data Platform to Enable Translational and Clinical Omics [The title of the poster itself has been changed slightly by substituting the term computing with data.]", "Medicine is rapidly moving from a phenotype-driven to a genotype-driven science [...] [We have here once again a reference to The Proposal and also a link to the OntoBot software component of our OS OntoLinux.]", "[...] 1) evolving biomedical knowledge, 2) longitudinal medical data, and 3) high-volume omics data. Attempts at bridging these data types required for enabling clinical omics has yielded little success. Syapse has built a data platform that enables capture, modeling, and query of all three data types, along with applications and programming interfaces for seamless integration with lab and clinical workflows. [We have here two criminal marketing lies in one sentence. Firstly, that company has bridged the three data types with the presented data platform. Secondly, that company has not built a data platform but simply copied our OSA in a specific variant. Therefore, the first point is a lie, because our attempt worked obviously. And why the term bridging is used in a negative way is also obvious: misleading the public.]", "Using a proprietary, semantic layer based on Resource Description Framework (RDF) and related standards, the Syapse platform enables assembly of a dynamic knowledge base from the user's internally curated knowledge, public biomedical ontologies, or private databases. [We also think that the semantic layer is proprietary, but not owned by that company, because it was taken from our OS. In addition, the dynamic knowledge base points and its assembly points to our Ontologic File System (OntoFS) and OntoBot software components, and the term curated knowledge was copied from our website Ontologics.info, where also the links to ontologies and controlled vocabularies in the form of XML files or other formats can be found.]", "[...] RDF objects [...] [This suggest a relation with the Object-Oriented (OO 1) paradigm.]", "The semantic data platform provides the ability to capture complex data, flexibility of data models to meet evolving requirements [...] [The term complex leads to our Hightech Office Ontonics.]", "[...] Resource Description Framework (RDF) is used for flexible data schema and storage [...] [At first sight this looks harmless. But RDF is used for flexible data schema as well in the sense of metadata is data and our Ontologic Paradigm (OP) utilized for the OntoFS. Furthermore, this point is connected with a triple store that includes controlled vocabularies and semanitic application data in a shown graphic.]", "Data properties can be structured as vocabularies based on public biomedical ontologies. [...] Syapse supports the use of private ontologies and vocabularies within the platform without compromising privacy.", "The SKOS standard is used in representation of imported vocabularies. [See the case of the World Wide Web Consortium (W3C) in the Investigations::AI and Knowledge management of the 7th of September 2012 for example.]", "Challenge: Omics data such as whole-genome sequence is voluminous and unstructured. Semantic computing architecture alone is poorly suited for high-volume, low complexity data. Scalable variant store and federated queries allow integration of omics data with complex clinical information. [This is our OntoBase.]", "Challenge: Different organizations need to capture different sets of processes and source data, while retaining the ability to support evolving requirements. Syapse accommodates disparate and evolving data requirements through the use of configurable ontologies. Configurable ontology is customer-specific, supports migration of legacy data, and can capture a variety of laboratory and clinical processes. [The user-specific configurable ontology This point is connected with a data store designated as "Ontology Files", which in fact stands for Ontologic File System (OntoFS), an "Application Ontology Logic", which in fact stands for Application Ontologic or our OntoBot respectively Ontologic Application, and an "Ontology Layer" of a "Fat Client", which is connected with a "Display Config[uration]" of an "Object Interface", which in fact stands for our OntoScope. Besides the "Scalable Data Store" designated as "Variant Store" and the "Application Data Stores" including the "Ontology Files[ystem]" and the "RDF Triple Store", an "Application DBMS" with "SQL" interface is also shown that reflect our OntoBase and OntoFS. In addition, a "Semantic Object Layer" is shown, which together with the "Object Interface" emphasizes the connection with the Object-Oriented (OO 1) and Ontology-Oriented (OO 2) paradigms. Moreover, a part of that platform is designated as "Web Application Components", which reflects our OSA with its components and Ontologic Applications once again. See also the section Semantic (World Wide) Web to the Links to Software, specifically the document about the Knowledge Bus referenced therein (see also the Clarification of the 14th of May 2016). Eventually, basically, and conceptually, in the context of a semantic, ontology-based, ontology-oriented, and ontology logic-based computing platform this is our original and unique, unforeseeable and unexpected, and hence copyrighted and proprietary Ontologic Computing (OC) paradigm and OSA. Bingo!!!]", "The application presents appropriate functionality automatically by reading the current configuration of the user's ontology. This parameterization of functionality by ontology allows user interfaces, such as the Syapse query builder, to conform automatically to custom data models. [And this point together with the all the time, dynamically, configurable ontology describes nothing else than an essential part of our Ontologic Computing (OC) paradigm, because the system utilizes ontologies for the application, management, interpretation, and presentation of (user) data and (system) functionality.]", "Expressing configurable ontologies in a machine-processable format is necessary for content retrieval and management. Ontologies conform to opensource OWL standards. [The term machine-processable format sounds harmless as well. But in the context we it is related with our Ontologic Computing (OC) paradigm as well. At least such wordings have been deliberately created to mislead the public as much as possible.]", "Semantic queries, supported by the RDF framework for storing data, are highly expressive, return structured results, and are executed immediately in memory. This supports queries, data mining, pattern recognition, and reporting rules on the intersection of clinical, omics, and knowledge base information. Query interface allows non-technical users to interact intuitively with complex data, while Syapse Query Language (SyQL) supports bioinformaticists and software developers in programmatically executing queries. [The most important points in this statement are data mining, pattern recognition, rules, and programmatically executing queries, which is considerably more functionality than the functionality of a data store. In fact, data mining is the process of discovering patterns in large data sets involving methods at the intersection of Machine Learning (ML), statistics, and DataBase Management Systems (DBMSs), pattern recognition is even a branch of Machine Learning (ML), and programmatically executing a query in memory makes the query a program, which could be everything even our OS eventually due to the system properties "Resource Description Framework (RDF) is used for flexible data schema and storage", "Application Ontology Logic", and "Semantic Object Layer" based on our OSA.]", "Challenge: Clinical omics and biomedical knowledge come from many disparate systems, such as electronic medical records, data warehouses, laboratory information systems, and public knowledge bases. Seamless integration of these source data with minimal technical overhead is needed to support users with complex legacy systems. Integration with other current systems, such as analytical pipelines, machines, and EMRs is needed to provide a comprehensive view of relevant information. [The company has also stolen parts of our Ontologic Applications and projects 21st Century Health Care Card and Holomer of the Innovation-Pipeline of Ontonics, whereby the Holomer is also listed in the section Human Simulation/Holomer of the webpage Links to Software.]", "Like the web application user interfaces and functionality, the API also presents appropriate functionality automatically by reading the current configuration of the user's ontology. ETL tools, such as database connectors and parsers, are all parameterized based on the user's ontology as well. Configurable ontology supports mapping and easier migration of legacy data. API conforms to RESTful standards. Syapse additionally provides Python and JavaScript wrappers. [Also the functionality and tools are automatically presented and parameterized based on a current configuration of a user's ontology, which proves once again that not only the data, but also the functionality and the management or operation of the overall system are integrated all in one system (see the webpage Overview of the website of our OS OntoLinux). As we said before, this is our Ontologic Computing (OC) paradigm and our OS stolen by that company. Furthermore, the programming language and the ECMA scripting language were the only two other languages that our OS supported initially.]", "Several major cancer centers are using Syapse to implement a next-generation IT and informatics infrastructure [...] [That was said 8 years after the start of OntoLix and OntoLinux.]", "Biologists and clinicians use the Syapse data platform to implement an omics learning healthcare system. [Our fans and readers might already ask where is more out of the field of Artificial Intelligence (AI). Here is it. Let us wait when there are conversational agents, too]", "Syapse is providing its semantic data platform for the Free the Data! initiative [...] [That is quite bold to give away something for free that one does not own at all.]", "Our novel semantic data platform will enable powerful data mining, visualization, and reporting [...] [This is a reference to our OntoBot and OntoScope, and another evidence for its copyright infringement once again.]", and "Syapse has developed an innovative data management platform that will enable the creation of single-patient multi-omics profiles and clinical decision support via a user-configurable semantic platform, federated data storage architecture, in-memory indexing of large scale omics data, and semantic queries. [And we have created a sketch for our lawyer team.]".
    We have provided evidences that our original and unique Ontologic System Architecture (OSA) has been taken as a blueprint in a top-down approach without aoviding a causal link, which implies various infringements of our rights, specifically of our copyright. For sure: Convicted!!!

    Is not it bold that the DARPA has stolen our OS and is realizing it with such criminal plagiarists like the University of Illinois, the company Syapse, and many other entities?
    The positive aspects, if they can be designated in this way at all, are the following:

  • If these entities have been chosen for the DARPA project, then we can assume that there are not much more others and that there are no others with original works in relation with our OS.
  • Because our OS has been chosen for this DARPA project as well, we got a further evidence of its uniqueness and originality.


    25.August.2017
    OntoLix and OntoLinux Website update
    For rounding up the section Basic Properties of the webpage Overview we added the

  • types of Operating System (OSys) Reflective Operating System (ROS), Real-Time Operating Systems (RTOS), Capability-based Operating System (CapOS), Agent-Based Operating System (ABOS), and Artificial Intelligence Operating System (AIOS),
  • types of Data Base Management System (DBMS) Relational Data Base Management System (RDBMS), NoSQL, Object-Oriented Data Base Management System (OODBMS), Object-Relational Data Base Management System (ORDBMS), and NewSQL, and
  • point Agent System and sorted the Multi-Agent Systems (MASs) and Cognitive Agent Systems (CASs) into it.

    The list of the basic properties might be reduced again to the top points when related webpages or/and content have been added.

    We also added to the section Mixed Reality of the webpage Links to Software the document:

  • Advanced Telecommunications Research Institute International (ATR) Communication Systems Research Laboratories, Paul Milgram, Haruo Takemura, Akira Utsumi, and Fumio Kishino: Augmented Reality: A class of displays on the reality-virtuality continuum

    Somehow, our definition of Mixed Reality (MR) seems to equal their definition of the Reality-Virtuality Continuum (RVC) on the one hand and we have not regarded the definition of Mediated Reality (MedR) of Steve Mann sufficiently in relation with the description of our Ontologic uniVerse (OV) despite we listed MedR on the webpage Overview (see also the Clarification of the 16th of April 2016 and the Website update of 23rd of August 2017).

    In the section Natural Language Processing of the same webpage we added the document:

  • University of Rochester, Department of Computer Science, James F. Allen, Donna K. Byron, Myroslava Dzikovska, George Ferguson, Lucian Galescu, and Amanda Stent: Towards Conversational Human-Computer Interaction

    In this paper The Rochester Interactive Planning System (TRIPS), also called "[a]n intelligent integrated problem-solving assistant", is described, which is "a generic system for practical dialogue together with a framework in which new tasks can be defined relatively easily. Key to this enterprise is the development of an abstract problem-solving model that serves as the underlying structure of the interaction." "This approach models the human-machine interaction after human collaborative problem solving." The "generic system (applicable across a practical domain) is specialized to the particular domain by integrating domain-specific information [...]." "A domain-specific task model provides mappings from the abstract problem solving model to the operations in a particular domain by specifying what things count as objectives, solutions, resources, and situations in this domain and how they can be manipulated." "[An] agent-based framework, where the back-end is viewed as a set of agents providing services [exchanged by a] define[d ...] broker that serves as the link between the dialogue system and the back-end".

    We generalized such combined systems in the

  • first step with the substitution of an abstract problem-solving model as used for e.g. TRIPS with our Ontology-Oriented (OO 2) paradigm by using domain models respectively ontologies, controlled vocabularies, and similar sources of knowledge to provide a coherent OO 2 model for the individual specializations of such a dialog system (see also Agent-based Unified Modeling Language (AUML) and UML-Based Ontology Modeling for Software Agents, Ontologies in Agent Architectures, and Nuin for example) for example),
  • second step with the substitution of the dialog system and its specific problem-solving model with an agent-based dialog system included in the overall Multi-Agent System of our OntoBot (OB) software component of the Ontologic System (OS) in accordance with the first step,
  • third step with the substitution of the service broker with an ontology broker and ontology-based broker included in an overall ontologic broker, and made it ready for the semantic net, semantic web, semantic grid, cognitive net, cognitive web, and cognitive grid in this way as well, which resulted in the related parts of our Ontolgic Web, Ontologic Grid, and Ontologic Net, and
  • fourth step with the integration of the elements of the first and second steps within our Ontologic(-Oriented) (OO 3) and Ontologic Computing (OC) paradigms.

    What the authors have not realized, like the author of the suspicious document mentioned in the Website Review and Clarification of the 23rd and 24th of August 2017 (see also the Website Review 5th of March 2017), for example is the step of the overall connection, overlay, and integration to an all in one system architecture mentioned on the webpage Overview, and the synergetic effects that are the result of the property of being holistic/fractal and also the property of being reflective of our Ontologic System Architecture (OSA). For example, in this case they did not apply the agent-based system for the dialog system as we also noted in the Investigations::AI and KM of the 9th and 10th of May 2017. In other cases, the agent-based system has not been applied on the operating system with its network and other communication functionalities (see Agent-Based Operating System) as it is the case with the semantic agent and the cognitive agent (see The Proposal). In addition, multimodal computing respectively Natural Multimodal Processing (NMP) or Natural Sense Processing (NSP) was also not regarded (see The Proposal once again and also the Clarifications of the 1st of May 2016, 6th of March 2017, and yesterday).

    Style of Speed Further steps
    We would like to show just only the first design prototype of our Magic Carpet.
    Such a type would also work for our public transport system as discussed in the Further steps of the 28th of April 2017.

    Duffy London→Flying Carpet Coffee Table → Style of Speed→Magic Carpet
    © Duffy London

    And yes indeed, our Magic Carpet is available in all pixel combinations and can be used as seat, chair, or coffee table as well.
    This shows nicely the difference once again: The works of C.S. even do have a real shadow and fly.


    26.August.2017
    Comment of the Day
    Hover machine™

    Original #1
    Walt Disney, Star Wars: The Force Awakens (2015)

    Walt Disney Star Wars The Force Awakens
    © Walt Disney

    See also the Original vs. Inspiration of the 10th of May 2017 and 8th of June 2017.

    Be the first and get your tickets for

  • a Star Wars Weekend in Disneyland with flights from and to your home in a TIE Fighter or a Millennium Falcon, and
  • a Star Wars theme park with Swoops, Landspeeders, Airspeeders, TIEs, Millennium Falcons, Super Star Destroyers, and much more.

    Do not say we have not told you.

    Are you a cab driver who is not afraid of flying?
    Then
    Join the Bright Side of the Force.™
    Become a Hoverorb™ or Hoverpod™ pilot.
    Join our Highly Effective Team.™
    Today.

    I'm flyin' it™

    Original #2
    Maximilian Büsser and Friends (MB&F) and Reuge, MusicMachine 3, Twin Mechanical Music Box with dual music cylinders and resonant amplifying base

    MB&F→Reuge→MusicMachine 3 Twin Mechanical Music Box with Dual Music Cylinders
    MB&F and Reuge→MusicMachine 3 Twin Mechanical Music Box with Dual Music Cylinders
    © MB&F

    OntoLix and OntoLinux Website update
    We have corrected and updated the section Enterprise Integration of the OntoCAx software component.

    Roboticle Further stpes
    We are very sorry to say, but our Hoverdrone™ Model T shown as Original #2 today can only play digital music, take images, charge wirelessly on the base, hover around, and perhaps something more.
    The shown images should only give an impression of a prototype of the HoverMachine™ 3 most potentially available at MB&F as well.
    See also our similar Lego model. :D

    I'm flyin' it™

    Style of Speed Further steps
    We worked on the design of the first model of one of our Hoverpod™ series that is more like a Hoverplane.


    27.August.2017
    Ontonics Further steps
    Since some months, we are working on the next generation of a technology of us that is related with two older even more exotic technological concepts that we will realize with said next generation of the technology.
    When coming from a specific problem with a utilization of this technology we looked at another utilization of it and concluded that we are already at a stage of its development that we can solve said problem. The results are unbelievable.

    Style of Speed Further steps
    Let us talk about one of the top themes ... hoverboards, what else?
    In the last days, we worked on the our hoverboard, specifically on its design and working.
    The image below shows a deck of a skateboard that we adapted as the second prototype of our hoverboard.

    Woyt → SoS Hoverboard Prototype
    © Woyt and Style of Speed

    Such a hoverboard works but with a relatively low performance without a Mr. Fusion Home Energy Reactor or an Arc Reactor (see also the Original vs. Inspiration of the 18th of July 2015 and the Ontonics Further steps of the 13th of August 2017) and for other technical reasons, which is also the reason why we are recommending to take our Magic Carpet (see the Further steps of the 25th of August 2017) until the practical deficits have been solved.

    Furthermore, we are addressing three specific problems two of which are shown in the following short video.

  • The first problem is this dipping while stepping on the hoverboard,
  • the second problem is its propulsion, and
  • the third problem is its agility when hovering.

    The second and third problems led to the consideration to develop three different models:

  • The first model only hovers but has no propulsion system and must be pushed like an ordinary skateboard,
  • the second model has also a propulsion system but also the resulting higher energy consumption as mentioned above, and
  • the third model has an advanced design.

    Back to the Future Hoverboard in Action
    © Universal Studios

    While designing the first model of one of our Hoverpod™ series and approaching the final design step by step we found an error with the general approach. For increasing the safety even more to make our Hoverpods bulletproof, so to say, we added wings among other technologies. But wings generate drag when generating lift and we do not need this lift because this kind of lift generation is substituted by our more efficient anti-gravity device and repulsorlift engine technologies. That said, wings and also preferable safe measures to reduce their drag consume energy that would render the whole approach less efficient in the end when compared with an airplane that has only wings.

    Luckily, our OntoLab is already working on a technology for various applications and one of them is the solution of this problem, which we planned to introduce with a future generation of our Hoverpod platform. This will lead to many discussions with the regulators until we will be able to convince them eventually.


    28.August.2017
    OntoLix and OntoLinux Website update
    As some readers might have observed already, we have uploaded a very rudimentary first version of the webpage of our OntoCore (OC) component, as mentioned in the Further steps of the 3rd of January 2017, that is based on the collection of informations about our OntoL4 and OntoS1 microkernels, OntoCore, abstract machine core, and Artificial Intelligence (micro)kernel (AI microkernel) given in the

  • Clarification of the 1st of May 2016,
  • Clarification #1 of the 4th of May 2016,
  • Clarification of the 14th of May 2016,
  • OntoLix and OntoLinux Website update of the 16th of May 2016,
  • OntoLix and OntoLinux Website update of the 27th of May 2016,
  • OntoLix and OntoLinux Further steps of the 28th of May 2016,
  • OntoLix and OntoLinux Website update of the 30th of May 2016,
  • OntoLix and OntoLinux Further steps of the 1st of June 2016,
  • Clarification #1 of the 5th of June 2016,
  • Clarification of the 7th of June 2016,
  • Clarification of the 8th of June 2016,
  • OntoLix and OntoLinux Website update of the 13th of June 2016,
  • Further steps of the 3rd of January 2017,
  • Clarification or the 7th of January 2017,
  • OntoLix and OntoLinux Website update of the 6th of March 2017,
  • OntoLix and OntoLinux Website update of the 8th of March 2017,
  • Ontonics Further steps of the 19th of April 2017,
  • OntoLix and OntoLinux Further steps of the 5th of July 2017, and
  • Investigations::Multimedia, AI and KM of today.

    Needless to say that we will sort the design rationals, OntoL4, OntoS1, and OntoCore properties, connections, and applications in the next step and add some glue text.

    Investigations::Multimedia, AI and KM

  • University Southern California: A member of the Information Sciences Institute of the University of California publicated a highly suspicious document short before the website of OntoLinux was started in the year 2006 (see also the Website review of the 23rd of August 2017 and the Clarification of the 23rd and 24th of August 2017). We announced to say "Thank you" with an investigation of documents written by her well-knowing that we will find at least one evidence of copyright infringement. Since then we read 10 documents and found at least one copyright infringing and reputation damaging work that we quote in the following:
    "This paper describes several challenges facing programmers of future edge computing systems, the complex and diverse multi- and many-core devices that will soon exemplify commodity mainstream systems. [See the project MultiCore Competence in the Innovation-Pipeline of Ontonics]",
    "When programming such complex systems, several new concerns arise, such as computation partitioning across functional units, data movement and synchronization, managing a diversity of programming models for different devices, and reusing existing legacy and library software. [Surprisingly, these are some of the reasons why we developed our Ontologic System (OS). See also the webpage Overview of the website of OntoLinux.]",
    "[...] distributed computing environments [...] [See the related sections of the Links to Software, specifcally the sections Network Technology and Semantic (World Wide) Web of the website of OntoLinux.]",
    "large search spaces of possible solutions and the difficulty of predicting performance on increasingly complex architectures. Cognitive techniques are well-suited for managing systems of such complexity. [See the comment to the quote before.]",
    "We describe how cognitive techniques could provide a fundamentally new programming paradigm for complex heterogeneous systems, where programmers design selfconfiguring applications and the system automates optimization decisions and manages the allocation of heterogeneous resources to codes. [What the authors have not said to deliberately mislead the public is the that this fundamentally new programming paradigm has been developed by us and is part of our Ontology-Oriented (OO 2), Ontologic(-Oriented) (OO 3), and Ontologic Computing paradigms. See also the The Proposal.]",
    "Heterogeneous platforms can accelerate many applications that mix compute-intensive and control-intensive phases of computation, which are best targeted to different processing elements. These applications include large-scale scientific computations, complex simulations of physical phenomena, and visualizations. [See for example the section Visualization and the sections related with simulation of the webpage Links to Software.]",
    "One such example is entity-level simulations, wherein people and other entities are simulated by independent agents, are widely used for training and simulation. [See again the comment made to the quote before and also the webpag CCaliber/Calibre beginning with the section Snow Crash and the Metaverse.]",
    "These entities must determine if they are in the line-of-sight (LOS) of other entities, in particular models of sensor platforms. [See the section Intelligent/Cognitive Agent of the webpage Links to Software.]",
    "To ensure that experiments progress in real time [...] [See the section Operating System and once again the section Intelligent/Cognitive Agent of the webpage Links to Software.]",
    "While heterogeneous systems are promising from a performance and power perspective, additional programming challenges arise, including: (1) partitioning of the application across functional units; (2) managing data movement between functional units; (3) differences in programming models and tools across functional units; and, (4) managing reuse of code developed by others. Further, edge computing applications must be highly optimized for performance and power consumption. Just to put these challenges in perspective, (1), (2) and (4) are also challenges in porting across different homogeneous platforms. In the absence of tool support for this set of challenges, programmers of heterogeneous platforms must explicitly manage these details, which can dominate all other aspects of application programming for heterogeneous systems. The net result is that developing and debugging programs on such systems can be quite tedious, and is only approachable by highly-skilled individuals. [...] [Guess why we developed our OS as well and list the fields of Total Quality Management (TQM), Computer-Aided Software Engineering (CASE), and Problem Solving Environment (PSE) on the webpage Overview of the website of OntoLinux?]",
    "Programmers of distributed applications face similar challenges. [...] Programmers of these distributed applications face a very diverse set of resources and requirements. They also must manage software components developed by others, much like programmers of heterogeneous architectures incorporate software libraries developed by others. [See also the section Exampling Scenarios of the webpage Ontologic Applications.]",
    "[...] cognitive techniques for managing large-scale distributed applications [...] [See the section Basic Properties of the webpage Overview.]",
    "Our key observation is that a systematic and principled approach to developing and executing heterogeneous applications, making use of cognitive techniques, can greatly increase programmer productivity and application performance [...]. We introduce the concept of self-configuring applications, a new paradigm for heterogeneous programming that combines model-based software development and empirically-driven optimization. The role of a programmer with such an approach is to design models for software components that declare explicitly parameters and other aspects that can be optimized and managed by the underlying system. The system, in turn, takes a proactive role in configuring the application by searching through the space of possible configurations guided by information learned from empirical data derived from prior executions. [Obviously, we introduced the concept of self-configuring or self-adaptive applications, a new paradigm for heterogeneous programming that combines model-based software development and empirically-driven optimization, as can be easily proven with a look at The Proposal and the webpages Links to Software, Overview, and Ontologic Applications. Interestingly to note is the point that the plagiarists connected cognitive techniques with self-configuring applications, which leads us to The Proposal once again.]",
    "The role of a programmer with such an approach is to design models for software components that declare explicitly parameters and other aspects that can be optimized and managed by the underlying system. [See again the fields of Total Quality Management (TQM), Computer-Aided Software Engineering (CASE), and Problem Solving Environment (PSE) on the webpage Overview as well as the related sections Formal Modeling and Formal Verification of the webpage Links to Software.]",
    "The system, in turn, takes a proactive role in configuring the application by searching through the space of possible configurations guided by information learned from empirical data derived from prior executions. [See again the webpage Ontologic Applications and the OntoBot software component. At this point we have shown sufficiently many subject matter that proves the causal link and hence the copyright infringement.]",
    "[...] proposes self-configuring applications as a programming paradigm for heterogeneous platforms that incorporates cognitive techniques to represent and manage complex mapping decisions [...] [See the comments to the related quotes before.]",
    "While it might seem beneficial if all of these resources could be programmed using the same universal programming model, this is an unrealistic goal, as it would: (1) compromise the strengths of the existing programming models for their own platforms; (2) make it impossible to incorporate legacy code into edge computing applications; and, (3) fail to be adopted by the community, as there will never be consensus on what is the right universal programming model. [At this point the limit of the competences of the plagiarists can be seen, because our OS solves all three requirements with our ontologic paradigm and the functionalities of our OS components. In fact, this is also a case for cognitive computing and our original paradigm for heterogeneous programming.]",
    "As we move to increasingly heterogeneous platforms of the future, having appropriate architectureindependent programming paradigms becomes of paramount importance. [This is another reason why we developed our Ontology-Oriented (OO 2), Ontologic(-Oriented) (OO 3), and Ontologic Computing paradigms.]",
    "[...] introduce the concept of self-configuring applications, whereby the programmer expresses an application as a high-level workflow comprised of tunable software components that are abstractions of implemented codes. [See the webpage Introduction and again the fields of Total Quality Management (TQM), Computer-Aided Software Engineering (CASE), and Problem Solving Environment (PSE) on the webpage Overview, the related sections Semantic (World Wide) Web and Formal Modeling of the webpage Links to Software, and also the OntoBlender software component.]",
    "The optimization process relies on empirical search to execute and evaluate portions of a collection of equivalent alternative implementations of the workflow for the most suitable implementation. Machine learning, a rich knowledge representation, and an experience base aid in pruning and navigating the search space. [An optimization process based on empirical search can be found by a quick look on The Proposal and the related document More Notes, the document about Evolutionsbionik==Evolutionary Bionics]", and the related section Softbionics and Artificial Intelligence 3 of the webpage Terms of the 21st Century, the thechnique of Machine Learning (ML) can also be found in the section Softbionics and Artificial Intelligence 3, a rich knowledge representation is given with the approaches of ontology and topic map, and other approaches mentioned on the webpage Introduction, and the rest is provided by our OntoBot.]",
    "Workflows represent complex applications as components and their associated data flow.",
    "Component technology has been commonly used for over a decade as a strategy for facilitating code reuse and interoperability. As one notable example, the Common Object Request Broker Architecture (CORBA) facilitates interoperability between two programs, potentially written in different languages and executing on different vendor's platforms. [Needless to say, that CORBA is included in one of the many packages of the Linux distribution Debian. It was also already linked by GNOME with Metisse of the Mekensleep Underware software library set. See also the Virtual Object System (VOS).]",
    "The use of components in edge computing addresses several of the challenges in Section II. From the workflow perspective, it provides a sufficiently coarse-grain boundary for reasoning about application composition and optimization. It provides a unified mechanism for applications that mix legacy code, highly tuned libraries, and new self-configuring components either written by an application developer or generated automatically by a compiler. At the component level, the same programming model is used, regardless of functional unit and data movement protocol. [First of all, we also have structured our OS in components. Furthermore, see the sections Semantic (World Wide) Web and Formal Modeling once again.]",
    "[...] the component models used by workflow systems include three distinct aspects: a functional model, an invocation model and a performance model [...] [The first two models are also included in e.g. the Unified Modeling Language (UML) and the third model can also be realized as an extension in UML.]",
    "The functional model is used to communicate with the programmer at the application level. It also allows the workflow system to reason about the interactions among components in the workflow, and support programmers in workflow creation and validation. [See the sections Semantic (World Wide) Web and Formal Modeling that are connected with the fields of Total Quality Management (TQM), Computer-Aided Software Engineering (CASE), and Problem Solving Environment (PSE) and our OntoBot and OntoBlender once again.]",
    "The minimal component interface must verify the correctness of the invocation model [...] [See the section Basic Properties of the webpage Overview once again to find the OS property of being verified.]",
    "While a workflow instance logically identifies the full application, it does not include execution details such as what hardware resources should be used or where data should be placed. [Because we have a reflective OS with at least one integrated Computer-Aided Software Engineering (CASE) tool, its execution must be available in the CASE tool, which implies that we have a workflow instance logically identifies the full Ontologic Application respectively Ontologic System.]",
    "Compiler optimization typically performs a static analysis of application code and generates a single binary of the code. [...] a static, purely model-based approach [...] Recent work has dealt with the complexity of modern architectures through empirical techniques, where optimization decisions are guided by executing code variants directly to measure and compare performance. [...] compiler technology that can incorporate empirical techniques to tune application code [...] would be highly desirable to dramatically improve programmer productivity. This goal has inspired several compiler efforts that employ empirical optimization to evaluate alternative compiler optimization strategies, leading to much higher performance than the standard compiler approach that relies on static models. [See also the next quotes and their related comments.]",
    "[...] hybrid approach called model-guided empirical optimization combines the complementary strengths of compiler models and heuristics with empirical techniques [...] Using model-guided empirical optimization, the compiler generates a set of experiments to perform a search among possible implementations and optimization parameter values. [...] In the previous discussion, the experiments were the result of compiler algorithms. However, the compiler can also serve as an experiments engine for the application programmer, assisting with evaluating application-level parameters. [Conceputally, this is also the way Evolutionary Computing (EC) works, which is also included in Softbionics and Artificial Intelligence 3 and in this way included in the functionality portfolio of our OntoBot.]",
    "[The authors] envision a compiler that is constructed in a principled way, so that optimizations are well-defined and easily composed. [...] [The authors] propose a compiler based on formal descriptions of optimization behavior that can easily be composed. [...] In conjunction with searching [...] such an approach creates a powerful approach to compiler design that can assist in targeting heterogeneous resources. [We have the reflective OntoBot with the SimAgent Toolkit and OntoBlender with at least one Computer-Aided Software Engineering (CASE) tool, which both are utilized for Ontologic Applications and are based on our Ontology-Oriented (OO 2), Ontologic(-Oriented) (OO 3), and Ontologic Computing paradigms, which again comprise formal descriptions and are composable obviously.]",
    "[...] decisions and the associated search are hard-coded in the compilers or the workflows. [...] Cognitive techniques provide a systematic and principled paradigm to manage these decisions and to automate as many of them as possible. [We were already there as can be seen with the comments to the quotes before.]",
    "Approximate search algorithms explore the space of possible solutions not by exploring partial combinations of decisions and appending new ones but by navigating complete solutions and their variants [Goldberg 02 [The Design of Innovation: Lessons from and for Competent Genetic Algorithm]; Kirkpatrick et al 83 [Optimization by Simulated Annealing, Science]]. Examples include genetic algorithms and simulated annealing. [Both Genetic Algorithm (GA) and Simulating Annealing (SA) are compared with Genetic Programming (GP) in Banzhaf et al 1998 Genetic Programming: An Introduction and "1 Genetic Programming as Machine Learning". See also the section Softbionics and Artificial Intelligence 3 once again.]",
    "The first step will be to articulate and represent declaratively the kinds of decisions [...] By representing declaratively all these decisions, the search for a solution and better yet the search for an optimal (or quasi-optimal) solution can be conducted by using a variety of well-known algorithms and optimization techniques. In addition, declaratively representing these decisions will enable a better understanding of their nature and their interdependencies. This determines the complexity of the search and more importantly it determines what the best algorithm and search strategy is.[Here we are again at our OntoBot.]",
    "Many cognitive techniques are applicable in this context, including uncertainty reasoning, abstraction search, and metareasoning [Gil 06a]. [Clever but not clever enough. In fact, the author created a link to her highly suspicious document mentioned in the introduction of this investigative case to provide a causal chain that she had publicated the idea before us. But that did not work because we cut that causal chain the first time with the start of our OntoLix and OntoLinux and the second time with this investigative case. Besides this, that highly suspicious document is related with the semantic grid and agent-based systems combined to a cognitive grid, which in this context is not connected with the self-configuration of applications for heterogeneous systems at all. Bad luck, but we created so much subject matter and this even earlier in parts that a complete stealing cannot work. See also the Website review of the 23rd of August 2017 and the Clarification of the 23rd and 24th of August 2017, and also the last section of the OntoLix and OntoLinux Website update of the 25th of August 2017 once again.]",
    "Machine (automated) learning is another cognitive technique that will be advantageous to support programming for unforeseen heterogeneous computing architectures and applications. [Here we have again the webpages Introduction and Overview, the section Softbionics and Artificial Intelligence 3, as well as our OntoBot.]",
    "Learning techniques are used routinely to develop intelligent agents that make decisions while learning not to repeat the same mistakes and to improve their performance in tasks they perform routinely. Learning ranges from simply collecting performance metrics and deriving statistical predictive models, to more complex learning where efficient search heuristics are derived by reasoning about the properties of a problem domain. Learning can also improve performance by recognizing common failure conditions and designing mechanisms to anticipate and avoid them. [We would like to point to The Proposal, specifically the chapter 4 Piaget und künstliche Intelligenz==Piaget and artificial intelligence and the OntoBot once again.]",
    "A rich area for cognitive learning techniques is automatically learning local decisions concerning individual optimizations. [Obviously, the authors have understood this part of our Ontologic System.]",
    "[...] machine learning techniques could effectively be used to automate the construction of compiler optimization heuristics [...] [See the chapter 5 Zusammenfassung==Summary of The Proposal. At this point we would like to mention that on the one hand a compiler belongs to an operating system as a basic tool and on the other hand we have described even a 7.16 [7.19] Compiler für DNA and 7.18 [7.21] Compiler für mRNA in A Prototype.]",
    "The decision is also framed as a classification problem for machine learning.",
    "These results demonstrate the effectiveness of learning techniques to select transformations in adaptive compilers. [See again the OntoBot with the SimAgent Toolkit and keep in mind that the reflective property of the OntoBot also applies on the SimAgent so that in the end we have an adaptive compiler and a possibility to transform it included in the OntoBot.],
    "There is a wealth of research on cognitive techniques for human-machine collaboration for complex problem solving for many other domains that could be relevant for this area of research. For example, planning and constraint checking techniques have been demonstrated to assist users in workflow creation [...]. One could imagine programming environments for edge computing where intelligent assistance is used to extract from the programmer crucial application features relevant to performance, combined with automation of exploration and learning of optimization strategies at the compiler level. [See again the webpage Overview to find the fields Cognitive Agent and Computer-Aided Software Engineering (CASE), and also the OS property of being collaborative, as well as the webpage Ontologic Applications to find the intelligent assistance.]", and
    "Programmers will remain at the application level, while the system will take care of execution details and of learning strategies to customize its behavior to the current architecture. [And finally, we have once again the OS property of being reflective, the OntoBot, and the webpage Ontologic Applications, but also the Caliber/Calibre because the system reflects also a user and learns the habits of said user for customization.]".
    So miss smart aleck, this is the first copyright infringement and illegal exploitation of our reputation, as the provided analysis doubtlessly prove.
    Bad luck, this time we were first and that disgusting spying and stealing ends here finally.

    Btw.: The workflow part is called Model-Based Design (MBD), Model-Driven Engineering (MDE), and Model-Driven Architecture (MDA; see e.g. Unified Modeling Language (UML), specifically use case diagrams and activity diagrams intended to model both computational and organizational processes (i.e. workflows), Meta-Object Facility (MOF), XML Metadata Interchange (XMI), and Common Object Request Broker Architecture (CORBA)) supported by Computer-Aided Software Engineering (CASE) tools. See also business logic of a software that comprises workflows that are the ordered tasks of passing documents or data from one entity (a person or a software system) to another, Process Specification Language (PSL) Ontology (includes also the Process Interchange Format (PIF) and used with activity diagrams of UML), and Business Process Modeling (BPM).

    We are continuing with looking for the next evidence.

    Because our fans and readers were so brave in the last days we have begun with creating a litte candy for them on the 23rd of August 2017, proposed as a starter the reading of the OntoLix and OntoLinux Further steps of the 5th of July 2017, the webpages of the Components and Ontologic File System (OntoFS) software component, specifically its section Operating System Security, and the sections Operating System, Exotic Operating System, and Intelligent/Cognitive Agent of the webpage Links to Software, and noted to keep attention with implicitly given facts and related OntoLix and OntoLinux Website updates.
    This investigation is related with our Ontologic Systems OntoLix and OntoLinux and its features of the fields of capability-based system, sandboxing and shielding, cloud computing, (smart) contract creation, reasoning, and so on. We also take this opportunity to show more unforeseeable and unexpected properties of our OS.

  • University of Harvard: A research project of the University of Harvard developed a capability-based operating system extension that is based on a secure shell scripting language. We quote the most important and interesting portions of a related paper:
    "Current security tools make it difficult to apply this principle: they either require significant modifications to applications or do not facilitate reasoning about combining untrustworthy components. [In general, this is not the case with our Ontologic System Architecture (OSA).]",
    "[...] secure shell scripting language. [Secure shell] scripts enable compositional reasoning about security through contracts that limit the effects of script execution, including the effects of programs invoked by the script. [Secure shell scripting] contracts are declarative security policies that act as documentation for consumers of [secure shell] scripts, and are enforced through a combination of language design and sandboxing. [We discussed the issue with the sandbox in web browsers and clearly said that it is a function that belongs into the operating system respectively kernel space. We also have a capability-based microkernel OntoS1 in the OntoCore of our OS. In addition, we have Virtual Machines (VMs), Virtual Virtual Machines (VVMs), Agent-Based Operating Systems (ABOSs), and Multi-Agent Systems (MASs) as well as our OntoBot software component, the feature of "'Full Scripting' of the operating system functions (see e.g. Open Source Poplog and OntoBot)" listed in the Feature-List #1, and much more.]",
    "[Secure shell scripting] offers language abstractions for reasoning about the authority of pieces of software and their composition. Specifically, [secure shell scripting] (1) introduces a capability-based scripting language with language abstractions (such as contracts and wallets) to use capabilities effectively, and (2) implements, on a commodity operating system, capability-based sandboxes that extend the guarantees of the scripting language to binary executables and legacy applications. [We have a capability-based operating system microkernel with our OntoL4 software component, our OntoBot, at least one scripting language, and our OSA, that integrates all in one, which again also comprised in the beginning the set of Linux kernel modifications and user space tools Security-Enhanced Linux (SELinux).]", "Security guarantees of scripts apply transitively to other programs the script may invoke, including arbitrary executables. [This reminds us of the OS basic properties of being validated and verified, and specification- and proof-carrying listed on the webpage Overview of the website of OntoLinux.]",
    "Access control is based on the user on whose behalf the script executes. Thus, a script's authority is ambient (i.e., it derives from the script's execution context) [...], and a script may access any and all resources that the invoking user may access. [Secure shell scripting]'s security is based on capabilities instead of ambient authority. [See the related comment to a quote above.]",
    "Each capability-safe [secure shell] script comes with a contract that is enforced by the language runtime. A capability-safe [secure shell] script can use the capabilities it possesses to access resources using [secure shell scripting]'s built-in functions, if allowed by the contract. [Secure shell] scripts can also invoke arbitrary executables in capability-based sandboxes. A capability-based sandbox is created with a set of capabilities, and enforces a mandatory access control policy that restricts the executable's behavior based on those capabilities and their contracts. [At this point we use the approach of the smart contract, which should be at least validated and verified on the one hand and has not been disclosed with the start of OntoLix (see once again the OntoLix and OntoLinux Further steps of the 5th of July 2017). In summary, we have a validated, verified, capability-based, and smart contract-based operating system kernel OntoL4, with the capability-based, secure shell scripting language SHILL of Harvard and the POSIX extension Capsicum of Cambridge, and apply them as required and reasoned by our OntoCore and OntoBot. By the way: The official start of OntoLix on the 9th of November 2014 is not quite correct because its first official start was together with OntoLinux on the 29th of October 2006(?).]",
    "Of course, the contract that accompanies a script may also be untrustworthy [...] The benefit of [secure shell scripting]'s approach is that it is much easier to inspect and understand the declarative contract than to examine the script itself. [As we said, in our OS smart contracts are at least validated and verified Ontologic Applications.]",
    "[Secure shell scripting]'s trusted computing base includes the operating system kernel and [secure shell scripting] runtime. [Secure shell scripting] does not explicitly defend against malicious scripts or executables that exploit security flaws in the kernel or [secure shell scripting] itself. [At this point the case becomes slowly a copyright infringement, because this points to our OntoL4, OntoS1, OntoCore, and OntoBot software components and together with the other properties of our original secure shell respectively shield language we have the impression to got a causal link with our OS.]",
    "[Secure shell] scripts can only acquire capabilities as arguments provided by the user, or by deriving them from other capabilities (e.g., using a directory capability to acquire a capability for a file in the directory). These restrictions, known as capability safety, lie at the heart of the security of [secure shell] scripts. [See the OS properties of specification- and proof-carrying. At this point it can be learned how elegantly the properties of being validated and verified, and specification- and proof-carrying interact with each other and generate unforeseeable and unexpected synergies. This is also the reason why a well-known company has also stolen this feature of our OS by verifying smart contracts in the same way as the L4 microkernel for example, which showed another time that a verified smart contract is basically and conceptually an Ontologic Application (see once again the OntoLix and OntoLinux Further steps of the 5th of July 2017).]",
    "Conceptually, [secure shell scripting] capabilities correspond to operating system representations of resources, such as file descriptors, and built-in functions such as append and lookup are wrappers for the corresponding system calls.",
    "[...] Design by Contract paradigm [...] [Ladies and Gentlemen, we are very pleased to say: Design by Smart Contract.]",
    "Each function contract has two parts: the precondition and the postcondition. [...] A capability contract with a set of privileges restricts what operations that capability can be used for. [Oh, a rule.]",
    "Moreover, if any of these capabilities comes with a contract, the [Mandatory Access Control (]MAC[)] policy further limits access to the resource according to the capability's contract. This capability-based MAC policy is enforced in addition to the operating system's discretionary access control (DAC) policies [...] [Indeed, this is also similar to the functionality in this part of of our OS, as mentioned above already. Luckily, our OntoCore and OntoBot do this job automatically and intelligently.]",
    "Ambient scripts are used to create capabilities and pass them to functions that capability-safe scripts provide. Consequently, the language of ambient scripts is extremely restricted [...] [At this point, we see the next advantage of our OS because conceptually we do not have this restriction but SoftBionics (SB) and our OntoCore and OntoBot.]",
    "The kernel module implements capability-based sandboxes and provides capability-safe versions of several POSIX system calls. [See for example the POSIX extension Capsicum once again and also the OntoLix and OntoLinux Further steps of the 04.April.2016.]",
    "We implement the [secure shell scripting] language as an extension to Racket [...] Racket's contract mechanism to implement [secure shell scripting] contracts [...] [Racket? See the OntoLix and OntoLinux Further steps of the 23rd of August 2017, look at the SimAgent Toolkit of our OntoBot, see the OntoLix and OntoLinux Further steps of the 5th of July 2017 once again, and watch how the magic of our all in one integrating OSA and our Ontologic Computing paradigm unfolds.]",
    "There is no fundamental obstacle to providing capability support for all resources, though doing so would require additional modifications to the system call interface. For example, we would need to provide a low-level capability for processes, similar to Capsicum's process descriptors. [What should we say? Perhaps Bingo???]", and
    "[Shielding] targets a particular domain (shell scripting) instead of general programming and that it uses contracts to manage capabilities instead of capability-based design patterns [26 [Robust Composition: Towards a Unified Approach to Access Control and Concurrency Control]]. [See the OntoLinux Website update of the 30th of January 2008. Somehow, it is not clear if shielding is sandboxing, as in this case, or the inverse of sandboxing, as in the case of Microsoft (see its case below). Nevertheless, it is obvious that our approach does both respectively all by the capabilities of our OntoBot and our other components.]".
    We do apologize for holding back relevant informations but the evil is listening.
  • Microsoft: The company Microsoft did the same as the University of Harvard and developed also a secure system extension for operating systems, but approached the problem from the other side with the technique of shielded execution, which is said to be the inverse of sandboxing. We quote a related paper that was presented at the same Symposium on Operating Systems Design and Implementation (OSDI) in the year 2014 like the paper of the University of Harvard quoted above:
    "[...] cloud computing infrastructure requires substantial trust [...] [See the section Basic Properties of the webpage Overview and the section Network Technology of the webpage Links to Software of the website of OntoLinux (keep in mind that grid computing, cloud computing, and edge computing are closely related).]",
    "We introduce the notion of shielded execution, which protects the confidentiality and integrity of a program and its data from the platform on which it runs (i.e., the cloud operator's OS, VM and firmware).",
    "Our prototype [...] is the first system to achieve shielded execution of unmodified legacy applications [...] [This is a lie deliberately made to mislead the public because our OS achieves this as well.]",
    "shielded execution [... is e]ssentially the inverse of sandboxing, it protects the confidentiality and integrity of code and data from an untrusted host.",
    "[...] a secure region of address space known as an enclave [...] [We would also like to recall that the reflective operating systems and other operating systems referenced in the section Exotic Operating System of the webpage Links to Software also provide many features that have been reinvented with the presented operating system extension in various ways, such as said secure region of address space for example.]",
    "[...] use an in-enclave library OS [...] [Compare the contents of this quote and the quote before with the protected regions of address spaces of special operating systems, specifically Kernel-Less Operating System (KLOS), Systems Programming using Address-spaces and Capabilities for Extensibility (SPACE), which we have referenced in the section Exotic Operating System in the year 2007, of reflective operating systems, specifically Apertos (Muse) and the Cognac system based on Apertos with its meta space concept, as well as Agent-Based Operating Systems (ABOSs) and Multi-Agent Systems (MASs), which belong to the basic properties of our OS, and of the special operating systems Spring in conjunction with the Exokernel and library Operating System (libOS), which both are very well-known in this field, and so on.]",
    "In contrast to previous protection mechanisms such as process isolation, sandboxing, managed code, etc. which serve to confine an untrusted program and protect the rest of a system from its actions, isolated execution refers to the inverse: protecting specific code from the rest of the system, however large or privileged. [But the foundation of process isolation is at least isolated execution of a process in a secure or protected region of address space. So what is new besides the added properties of our original and unique OS? See also KLOS and SPACE once again.]",
    "[...] the OS can re-enter the enclave, giving it the opportunity to inspect and modify its own state before resuming; [Here we have the technique of introspection and reflection and therefore the OS property of being reflective.]",
    "[...] specifically exclude software-based isolation mechanisms, because besides their vulnerability to simple hardware attacks, we wish to give the cloud provider the unfettered ability to patch and update its privileged software [...] [Important to note at this point are the facts, that this foundational property of its already highly suspicious operating system Singularity is excluded on the one hand and instead features of our Ontologic System (OS) have been added on the other hand. Obviously, that company does not know what to steal from us.]",
    "[...] a system supporting low-overhead sandboxing of [...] applications [...] consists of two core mechanisms, both of which [the shielding system] leverages: the picoprocess, and library OS. The picoprocess is a secure isolation container constructed from a hardware address space, but with no access to traditional OS services or system calls; instead, a narrow ABI of OS primitives is provided, implemented using a security monitor [...] [See the basic properties of our OS, the OntoL4 software component with e.g. its hypervisor functionality, and the section Intelligent/Cognitive Agent of the webpage Links to Software. At this point, our original and unique combination of a mcrokernel, with a reflective operating system, and an operating system with a secure or protected region of process space can be seen and in this way an evidence for a copyright infringement.]",
    "Together, the picoprocess and LibOS enable sandboxing of unmodified [...] applications with comparable security to virtual machines, but substantially lower overheads. [This lower overheads and the resulting increase in performance are exactly the reasons why we have combined microkernels, such as the L4 microkernel, and reflective operating systems, such as Muse and Aperto for example, as the basis for our OntoCore software component and abstract machine. In this way and by other design decisions and Ontologic System (OS) properties, we are able to realize and provide the exotic and advanced OS functionality, such as a cognitive Multi-Agent System Virtual Virtual Machine (MASVVM) for example.]",
    "While [the libOS] aims only to protect the host from an untrusted guest, [the shielding system] shields the execution of the application and LibOS from an untrusted host, thereby enabling mutual distrust between host and guest. [We do not buy it for the reasons given in the comments to the quotes before. Maybe this is the part of our OS that we already thought Microsoft has stolen when we saw that libOS the first time without the shielding system.]",
    "Specific calls require further validation [...] The interface at the enclave boundary must allow the shield to verify the correctness of all operations while also enabling an efficient implementation. [Could it be that we have here the OS basic properties of being validated and verified?]", and
    "The shield is not encrypted, but its integrity will be verified. [See once again the section Basic Properties of the webpage Overview. At this point, the causal link with our original and unique combination of a microkernel, with a verified operating system, a reflective operating system, and an operating system with a secure or protected region of process space becomes obviouse and therefore we have here an evidence for a copyright infringement, because the combination of the system properties of (mostly) being verified, kernel-less, and reflective with at least one secure or protected region of address space is an original and unique part of our OS, as far as we do know.]".
    Obviously, the company Microsoft is continuing its attempt to steal another portion of our operating system and Ontologic System, as it is doing since at least 17 years now. But this time we have proven once again that the gap between the usual operating systems and their usual technological development on the one hand and our original and unique, unforeseeable and unexpected Ontologic System on the other hand has become too large for that disgusting game (see also the comment OS too large to steal of the 15th of May 2016, the OntoLix and OntoLinux Further steps of the 5th of July 2017, and the webpage of the OntoCore software component).
    Do not trust the hardware, too.

    In addition, we see here some kind of collaboration respectively orchestration between the two entities at the Symposium on Operating Systems Design and Implementation (OSDI) in the year 2014. While the company Microsoft presented a part or an edge of a part that approached our OntoCore from the side of our kernel-less, reflective, capability-based, verified OntoCore the University of Harvard presented a complementing part that approached our OS from the side of our kernel-less, reflective, capability-based, verified OntoCore and our OntoBot.
    Nevertheless, both entities have not avoided a causal link with our original and unique multimedia work of art titled Ontologic System and in this way infringed our copyright and other rights by e.g. exploiting our reputation.


    29.August.2017
    Ontonics Further steps
    We continued with the improvement of one of our technologies mentioned in the Further steps of the 14th of August 2017.

    OntoLix and OntoLinux Further steps
    Let us talk about ... no, not hoverboards here but about operating systems and microkernels.
    We reduced the Application Binary Interface (ABI) of operating system primitives even more than others respectively removed them practically mostly and conceptually completely with a kernel-less microkernel, so that a Haven is already the Heaven.
    To show this, we recall the relevant features of operating systems that are referenced in the section Exotic Operating System of the webpage Links to Software with the exceptions of the VirtuOS, Asbestos, and Singularity that we hold back and in one case even do not want to reference for specific reasons. The following text passages can be found in the original materials about these operating systems.

    1. Kernel-Less Operating System (KLOS)
    [In KLOS] each process has its own private address space and virtual memory mapping and functions independent of all other processes in the system.
    This is made possible by the use of a subtle trick involving segmentation and Task State Segments (TSS).

    The [so-called] Event Core is the heart of the KLOS architecture. The amount of processing done in the Event Core is minimal and restricted to transferring control to the unprivileged domain and performing an optional Translation Look-aside Buffer (TLB[; a cache that memory management hardware (MMU) uses to improve virtual address translation speed]) flush. It is important to note that the Event Core is not just another name for the "kernel" as viewed in traditional OSs. Unlike traditional kernels, in KLOS there are no "down-calls" to the Event Core.

    2. Systems Programming using Address-spaces and Capabilities for Extensibility (SPACE)
    Virtualized resources as the fundamental abstraction presented to the application developer are removed. Instead SPACE supports spaces, domains, and portals as structuring mechanisms, which can be used to implement system services in multiple protection domains.
    The key to SPACE is the exploitation of protection domains to structure the operating system in terms of multiple kernels. [At this point, our Ontologic System Architecture (OSA) integrates a Multi-Agent System (MAS), an Agent-Based Operating System (ABOS), and a microkernel.]
    By using the protection domains in processor architectures that support kernel-based systems, it is possible to build an operating system without relying on a central kernel.
    SPACE generalizes the processor architecture by abstracting address spaces, privilege[(d)] modes, and exceptions. These mechanisms are used to construct software using spaces, domains, and portals.
    In SPACE the only abstractions present in the kernel are a generalization of the exception or interrupt handling mechanism. This generalized exception handling mechanism could be implemented in hardware; the result would be a truly "kernel-less" operating system.
    Ultimately, the kernel is the hardware.

    Address spaces correspond to [Auxiliary Memory Unit (]AMU[)] contexts, but instead of two privilege[(d)] modes, SPACE supports an arbitrary number.
    Exceptions are extended in SPACE through three related mechanisms:

  • 1. The first mechanism translates a hardware exception and related information (e.g. processor exception registers) into a generalized exception and parameter pair (X,v).
  • 2. The second mechanism maps generalized exceptions into portals. A portal associates an (X,v) pair with a generalized exception handler.
    Portals also specify the portal type implementation to use for traversing the portal to the exception handler and later returning.
    The ability to traverse a portal is a capability. A cross-domain call is then defined as passing through a portal. A cross-domain (communication) mechanism is used as a generalization of interrupt handling.
  • 3. The third mechanism used to extend exceptions in SPACE allows different implementations of the generalized exception and portal type mechanisms to be associated with each address space.

    This is questioning the use in a practical operating system: elimination of privileged-mode, tagging of memory operations, hardware support for portals/token-chains.
    Hardware protection does not come for free, though its costs are diffuse and difficult to quantify. Costs of hardware protection include maintenance of page tables, soft TLB misses, crossprocessor TLB maintenance, hard paging exceptions, and the additional cache pressure caused by operating system code and data supporting hardware protection. In addition, TLB access is on the critical path of many processor designs and so might affect both processor clock speed and pipeline depth. Hardware protection increases the cost of calls into the kernel and process context switches. On processors with an untagged TLB, such as most current implementations of the x86 architecture, a process context switch requires flushing the TLB, which incurs refill costs.
    (See also 3.1 Fluke Alta.)

    3. Flux µ-kernel environment (Fluke)
    Microkernels Meet Recursive Virtual Machines
    Fluke provides a virtualizable architecture.
    A complete virtual machine interface is provided at each level; efficiency derives from needing to implement only new functionality at each level. This infrastructure allows common operating system functionality, such as process management, demand paging, fault tolerance, and debugging support, to be provided by cleanly modularized, independent, stackable virtual machine monitors, implemented as ordinary user processes.

    3.1 Alta
    Alta provides essentially the same operating system and process model as does Fluke, but executes Java byte code instead of machine language, and uses type safety instead of the MMU to provide protection.
    Software-based protection mechanisms can take several forms, including type-safe languages, annotated code systems, and checkable (or provable) code accompanied by a proof. All of these systems use compile-time, load-time or run-time checks to prevent a program from making illegal memory accesses.

    3.2 Flask
    Flask is a security-enhanced version of the Fluke kernel and operating system, that applies Mandatory Access Control (MAC) to the Fluke microkernel.
    Many of Flask's core design principles have found a modern incarnation in SELinux, which, like TrustedBSD, adds MAC to popular Unix systems, and derived from SELinux in FreeBSD.

    4. VirtuOS
    VirtuOS exploits hardware-based virtualization [(e.g. Xen or another hypervisor)] to isolate and protect vertical slices of existing operating system kernels [(e.g. Linux)] in separate service domains, and to provide full protection of isolated system domains respectively improved isolation of kernel parts or components in virtualized containers [(see e.g. OntoLix based on BSD Unix)]. Each service domain represents a partition of an existing kernel, which implements a subset of that kernel's functionality.
    VirtuOS's user library dispatches system calls directly to service domains using an exception-less system call model [(see Linux kernel with FlexSC; external synchrony (see Xsyncfs))], avoiding the cost of a system call trap in many cases [(compare with 1. kernel-less KLOS without privileged mode or ring transition and with hardware-based virtualized resources, and 2. SPACE without privileged mode but with support of an arbitrary number of them and without virtualized resources but hardware-based (protection for) cross-domain calls)].

    It uses the [Peripheral Component Interconnect (]PCI[)] passthrough and [input-output memory management unit (]IOMMU[)] facilities of hardware-based virtual machine monitors to provide service domains with direct access to physical devices.
    [The hypervisor]'s PCI passthrough mode allows guest domains other than Dom0 direct access to PCI devices, without requiring emulation or paravirtualization. These guests have full ownership of those devices and can access them using unchanged drivers.
    To make PCI passthrough safe, the physical presence of an IOMMU is required. An IOMMU remaps and restricts addresses and interrupts used by memory-mapped I/O devices. It thus protects from faulty devices that may make errant DMA accesses or inject unassigned interrupts. Thus, devices and drivers are isolated so that neither failing devices nor drivers can adversely affect other domains [(replace the IOMMU with contract-based channels (CBCs) and manifest-based programs (MBPs) like in 9. Singularity)].

    Exception-less system calls avoid this overhead. Instead of executing system calls in the context of the current task, a user-level library places system call requests into a buffer that is shared with kernel worker threads that execute the system call on the task's behalf, without requiring a mode switch. Effective exception-less system call handling assumes that kernel worker threads run on different cores from the user threads they serve, or else the required context switch and its associated cost would negate its benefits.
    A key challenge to realizing the potential gains of this model lies in how to synchronize user and kernel threads with each other. Since application code is generally designed to expect a synchronous return from the system call, user-level M:N threading is required, in which a thread can context-switch with low overhead to another thread while a system call is in progress. Alternatively, applications can be rewritten to exploit asynchronous communication, such as for event-driven servers [using libflexsc also based on FlexSC-Threads]. VirtuOS uses the exception-less model for its system call dispatch, but the kernel worker threads execute in a separate virtual machine.
    [Exception-less system calls are also used for an event-driven or event-based server, and the general-purpose distributed memory caching system Memcached.]

    5. Spring
    Sun engineers used non-standard terminology for a number of common components, which makes discussing the system somewhat confusing. For instance, Mach tasks are referred to as domains, ports as doors, and the kernel as the nucleus.

    5.1 Nucleus
    The Spring kernel was divided into two parts: a virtual memory system and the nucleus.
    IPC model with doors between domains and name service.
    The Spring kernel is not multi-threaded and almost immediately hands off the vast majority of requests to the servers, so under this model it is only the servers which, in theory, need to be threaded.

    5.2 InterProcess Communication (IPC)
    One major difference between Mach and Spring was the IPC system. In Mach, the system was arranged as a set of one-way asynchronous pipes (ports) between programs, a concept derived from Unix pipes. In programming, however, the most common method of communications is the procedure call, or call/return, which Mach did not support directly. Call/return semantics could only be supported via additional code in higher-level libraries based on the underlying ports mechanism, thereby adding complexity.

    Spring directly supported call/return semantics in the basic communications system. This resulted in a change of terminology from ports in Mach, to doors in Spring. Doors were known to the kernel only; programs were handed [some kind of] a handle to the door with an identifier which was unique to that program. The system worked similarly to ports for the initial message; messages sent to a door were examined by the nucleus in order to find the target application and translate the door handle, but the nucleus then recorded small amounts of information from the caller in order to be able to return data quickly.

    Additionally, the Mach model was asynchronous - the call would return if and when the server had data. This followed the original Unix model of pipes, which allowed other programs to run if the server was busy. However, for a call/return system this has serious drawbacks, because the task scheduler has to run to select the next program to be serviced. Hopefully this was the server the call was requesting data from, but it this was not guaranteed. Under Spring, IPC is synchronous; control is immediately passed to the server without running the scheduler, improving the round trip time in the common case when the server can immediately return.

    5.3 Subcontracts
    Although not directly related to Spring per se, [...] existing mechanisms for supporting different flavors of calls were not well defined. In order to provide a richer interface, they developed the concepts of subcontracts [(see also 9. Singularity)].

    5.4 Related Work
    The L4 microkernel shares a number of features with Spring's kernel. In particular it also uses a synchronous call/return system for IPC, and has a similar Virtual Machine (VM) model.

    5.5 Interface Definition Language (IDL)
    Spring concentrated on programmability; making the system easier to develop on. The primary addition in this respect was the development of a rich Interface Definition lLanguage (IDL). In addition to functions and their parameters, Spring's interfaces also included information about what errors can be raised and the namespace they belong to. Given a proper language, programs, including operating system servers, could import multiple interfaces and combine them as if they were objects native to that language - notably C++. Some time later the Spring IDL was adopted with minor changes as the [Common Object Request Broker Architecture Interface Definition Language (]CORBA IDL[)].

    6. Pebble (for embedded applications)
    Pebble shares with SPACE the idea of cross-domain communication as a generalization of interrupt handling.

    6.1 Key Ideas
    Minimal supervisor-mode nucleus, responsible for little more than context switches.

  • Most operating system functionality is provided by servers that execute in user mode without special privileges. Safe extensibility: the system is constructed from untrusted components and reconfigured while running.
  • Software components execute in separate protection domains enforced by hardware (MMU).
    Inter-domain communication is performed by portals, which are generated dynamically.
    Portals may manipulate parameters.

    6.2 Hardware vs. Software Protection in
    Component-Based Applications
    Software protection: type safe languages (e.g. Java) or software fault isolation.
    Traditional hardware protection: components run in separate protection domains enforced by MMU.

  • Slow communication encourages co-location of components.
    Pebble approach: hardware protection with efficient communication via specialized portals.
  • Components may be written in any language.
  • The cost of portal call is small enough so that there is no performance reason to co-locate components in a single protection domain.

    6.3 Notes: Design Philosophy
    A small kernel:

  • The kernel is responsible only for switching between protection domains.
  • If something can be run at user level, it is.
  • Pebble kernel is much smaller than contemporary kernels (Unix, Inferno, L4[; An old version of L4 was ment at that time. Microkernels of the actual L4 versions are also very small.])
    Typical Pebble components: CPU scheduler, device drivers (including interrupt handling), VM, file systems.
    Portals:
  • portal code is generated dynamically and performs portal-specific actions.
  • portal code runs in kernel mode and may access or modify private data structures belonging to certain servers (e.g. VM).
  • portal code has no loops and may not be blocked.
  • each protection domain has a private portal table.
    No performance reason to co-locate services (run multiple services in the same protection domain).
  • cross-domain transfers via portals are very efficient.
  • can run untrusted code written in any language (not just type-safe languages such as Java) in a separate protection domain under hardware memory protection without a large performance penalty.

    6.4 Related Work
    Pebble includes a combination of old ideas:

  • Microkernels: Mach and L4.
  • Protection domains and portals: SPACE.
  • Specialized code generation: Synthesis and Synthetix.
  • Efficient parameter passing: [Lightweight Remote Procedure Call (]LRPC[)].
  • Object oriented OS: Spring.
  • Dynamically replaceable components: Kea.
  • User-level implementation of high-level abstractions: Exokernel

    Is it just a combination of L4 and Synthesis?

  • You are absolutely right.

    6.5 Pebble vs. Related O[perating] S[ystem]
    Pebble takes the ideas of Synthesis and Synthetix to the extreme.
    What happens when all system calls and all IPC are customized?
    Pebble has a smaller nucleus than modern kernels like L4, while keeping their performance advantage for specialized system calls and IPC. [(This comparison is based on older implementations of the L4 microkernel and must not hold for the latest implementations of it.)]
    Pebble extends operating system functionality by calling new user-level servers via efficient portals. Other[ operating system]s load code into the kernel or provide a library of low-level abstractions.
    Pebble provides safety by enforcing protection domains with hardware MMU. Other[ operating system]s use special languages, static or dynamic checks for code that is loaded into the kernel.

    7. OntoS1
    OntoS1 is our verified microkernel, which is based on our (verified) OntoL4 microkernel.

    Instead of leveraging hardware based protection to speed up (some of) the context switching, like for example TrustZone (TZ), a verified kernel can be used to run all operating system servers and applications in protected mode respectively without any priviliged mode (see 1. KLOS and 2. SPACE).

    8. Coyotos
    Type safety is another way to enforce operating system security. Coyotos combines capabilities with language-level verification techniques.

    9. Singularity
    Singularity systems incorporate three key architectural features:

  • 1. Software-isolated processes (SIPs; isolation-based processes (IBPs)) for protection of programs and system services provide an environment for program execution protected from external interference.
  • 2. Contract-based channels (CBCs) for communication enable fast, verifiable message-based communication between processes.
  • 3. Manifest-based programs (MBPs) for verification of system properties define the code that runs within software-isolated processes and specify its verifiable behavioral properties.

    [At the same time two collaborating research groups have begun to verify the L4 microkernel as well, because C.S. was acting in these fields for the development of our OS.]

    9.1 Software-Isolated Process (SIP)
    SIPs cannot share writable memory with other SIPs and are isolated by software verification, not hardware protection. In other words, SIPs are closed object spaces.

    SIPs rely on programming language type [(see Exokernel and SPIN)] and memory safety for isolation [(see Exokernel also by means of software protection techniques, like type safe languages and sandboxing)], instead of memory management hardware. Through a combination of static verification and runtime checks, Singularity verifies that user code in a SIP cannot access memory regions outside the SIP. With process isolation provided by software rather than hardware, multiple SIPs can reside in a single physical or virtual address space.
    Richer systems can be built by layering SIPs into multiple address spaces at both user and kernel protection levels. Aiken et al. [1] evaluate the trade-offs between software and hardware isolation [(compare with the meta space concept of Cognac based on Apertos and hardware-based virtualized containers of exception-less VirtuOS)].
    Communication between SIPs incurs low overhead and SIPs are inexpensive to create and destroy, as compared to hardware protected processes (see Table 1). Unlike a hardware protected process, a SIP can be created without creating page tables or flushing TLBs. Context switches between SIPs also have very low overhead as TLBs and virtually addressed caches need not be flushed.
    Protection domains can provide an additional level of hardware-based protection or isolation around SIPs. Each protection domain consists of a distinct virtual address space [(compare with 1. kernel-less KLOS without privileged mode or ring transition and with hardware-based virtualized resources, and 2. SPACE without privileged mode but with support of an arbitrary number of them and without virtualized resources but hardware-based (protection for) cross-domain call)].

    9.2 Contract-Based Channel (CBC)
    A channel is a bidirectional message conduit with exactly two endpoints. A channel endpoint belongs to exactly one thread at a time.
    Communication across a channel is described by a verifiable channel contract. The two ends of a channel are not symmetric in a contract.
    A contract consists of message declarations and a set of named protocol states. Message declarations state the number and types of arguments for each message and an optional message direction. Each state specifies the possible message sequences leading to other states in the state machine [(see communication of agents listed in the section Intelligent/Cognitive Agent and handling of state machines in the Agent-based Unified Modeling Language (AUML) listed in the section Formal Modeling of the webpage Links to Software)].

    9.3 Manifest-Based Program (MBP)
    Every component in Singularity is described by a manifest, including the kernel, device drivers, and user applications.
    A manifest describes an MBP's code resources, its required system resources, its desired capabilities, and its dependencies on other programs.
    It is a machine-checkable, declarative expression of the MBP's expected behavior. The primary purpose of the manifest is to allow static and dynamic verification of properties of the MBP. For example, the manifest of a device driver provides sufficient information to allow installtime verification that the driver will not access hardware used by a previously installed device driver. Additional MBP properties which are verified by Singularity include type and memory safety, absence of privileged-mode instructions, conformance to channel contracts, usage of only declared channel contracts, and correctly versioned ABI usage.
    A basic manifest is insufficient to verify that a MBP is type safe or that it uses only a specific subset of channel contracts. Verification of the safety of compiled code requires additional metadata in MBP binary files.
    To facilitate static verification of as many run-time properties as possible, code for Singularity MBPs is delivered to the system as compiled Microsoft Intermediate Language (MSIL) binaries [(MSIL is a superset of the Common Intermediate Language (CIL) and CPU independent byte code format)].

    When an MBP is invoked, the manifest guides the placement of code into a SIP for execution, the connection of channels between the new SIP and other SIPs, and the granting of access to system resources by the SIP [(see object and agent migration)].

    9.4 Compile-Time Reflection (CTR)
    The core feature of compile-time reflection (CTR) is a high-level construct in Sing#, called a transform, which allows programmers to write inspection and generation code in a pattern matching and template style. The generated code and metadata can be statically verified to ensure it is well-formed, type-safe, and not violate system safety properties. At the same time, a programmer can avoid the complexities of reflection APIs.
    [Interestingly to note are the points that we have the Evolutionary operating system (Evoos) with Run-Time Reflection (RTR) and we use proper reflection or RTR because the OntoBot is based on the SimAgent Toolkit that utilizes on-the-fly compilers. This implies that an agent, specifically a cognitive agent, as part of an operating system or an overall system architecture has not been envisioned by the developers of the Singularity operating system.]

    10. Barrelfish
    Message-based rather than shared-data communication offers tangible benefits: instead of sequentially manipulating shared data structures, which is limited by the latency of remote data access, the ability to pipeline and batch messages encoding remote operations allows a single core to achieve greater throughput and reduces interconnect utilization.

    11. Asbestos
    Asbestos proposes the marriage of previous ideas in systems: the capability-based operating system, the per-process namespace, the virtualizable kernel interface (the logical extension of system call interposition libraries), and decentralized MAC [or Distributed Mandatory Access Control (DMAC)].
    Asbestos uses decentralized, fine-grained mandatory access control (MAC) primitives to solve this problem in a flexible and scalable manner. Subjects on the system, such as processes, I/O channels, and files, are assigned labels, and special privilege is needed to remove a label once applied.
    The Asbestos operating system makes non-discretionary access control mechanisms available to unprivileged users, giving them fine-grained, end-to-end control over the dissemination of information.
    Asbestos provides protection through a new labeling scheme that, unlike schemes in previous operating systems, allows data to be declassified by individual users within categories they control. The categories, called tags, use the same namespace as communication endpoints, making them a kind of generalization of capabilities. As in a capability system, processes can dynamically generate new tags and distribute them independently. Processes can specify temporary label restrictions on sent messages to avoid the unintentional use of privilege.
    Asbestos's new process abstraction, the event process, efficiently supports server processes that must spin off many versions inhabiting distinct security compartments. Event processes impose less overhead on the operating system than forked address spaces, so many thousands of them can coexist without resource strain.

    12. But there is one more thing:
    We removed that remaining hardware generalization of the exception or interrupt handling mechanism, system call trap, hardware MMU and IOMMU, etc. of kernel-less operating systems with the integration of system features like:

  • capability-based (see L4),
  • verified,
  • cross-domain communication (see SPACE and Pebble),
  • hypervisor (see L4 and also VirtuOS),
  • exception-less system call model (see KLOS and Linux kernel with FlexSC and VirtuOS),
  • asynchrony (see Integrating Architecture of our OS and VirtuOS),
  • external synchrony (see Xsyncfs),
  • type safety instead of the MMU (see Fluke Alta and Coyotos),
  • verifiable contract-based channels (CBCs) and manifest-based programs (MBPs) (see Singularity) instead of the IOMMU,
  • message-based system rather than shared-data communication (see Barrelfish) over CBCs for example,
  • and so on

    as a dynamic, flexible way as required, whereby our OntoCore has also the integrated system features of:

  • verified OntoS1,
  • Design by Smart Contract,
  • Ontology-Oriented (OO 2) and Ontologic(-Oriented) (OO 3) instead of the MMU and the IOMMU,
  • Ontology-Oriented (OO 2) and Ontologic(-Oriented) (OO 3) for the CBC and the MBP,
  • and much more.
    Think about it. WOW.

    Are there any questions?


    30.August.2017
    Clarification
    In relation with the OntoLix and OntoLinux Website update of yesterday we would like to add that at this point it can be seen that at least conceptually the OntoCore is not grounded anymore and therefore we can begin to talk about our more than 11 years old plan to view it as the proof for Artificial Consciousness, Teleportation #1 and #2, and many of the other stuff others that are based on our Caliber/Calibre and we listed in the webpage Terms of the 21st Century of the website of OntoLinux. Fascinating.

    Website update 11:20 UTC+2
    We added to the OntoLix and OntoLinux Further steps of yesterday the sections Spring, Singularity, Asbestos, Flask, VirtuOS, and OntoS1 from our internal document, as well as some more points and comments for better understanding and for having everything at one place.

    We have also finalized the first investigative case of the Investigations::Multimedia, AI and KM of the 28th of August 2017, which proves once again that we are the good ones. :)

    OntoLix and OntoLinux Website update
    In relation with the OntoLix and OntoLinux Website of yesterday we forgot to make explicit what the website update is about at all, which is made up today.

    We added to the section Exotic Operating System of the webpage Links to Software the link:

  • Virginia Tech, Ruslan Nikolaev and Godmar Back: VirtuOS - an operating system with kernel virtualization

    At this point it should be obvious that we have decomposed the BSD Unix kernel for OntoLix and the Linux kernel for OntoLinux to realize what we said in the sections 2.7.2 Metamorphose==Metamorphosis and 8.2.3 Prinzip eines Virus==Principle of a Virus of The Proposal and on the webpage Profile: We at OntoLinux, transform operating systems based on Linux into Ontologic Systems.
    This is done in the way as we said in the section Hint of the webpage Project Status: If you are trying to build your own system, develop a strategy for automating as much as possible without stepping out of the whole concept.
    Said this, we have our original and unique Ontologic System and Ontoscope ready since 2006. Period.

    In the section File System of the same webpage we added the link:

  • University of Michigan, Department of Electrical Engineering and Computer Science, Edmund B. Nightingale, Kaushik Veeraraghavan, Peter M. Chen, and Jason Flinn: Rethink the sync [(eXternal synchrony file system (Xsyncfs))]

    I'm lovin' it™


    31.August.2017
    Comment of the Day
    Cognitive system core™
    Cognitive core™
    Cognitive microkernel™
    Cognitive kernel™

    Website update
    We added to the OntoLix and OntoLinux Further steps of 29th of August 2017 the section Coyotos, the information that Flask applies MAC, and some more informations about the basic features of Asbestos for better understanding and for having everything at one place.

    We are also thinking about moving the content of this Further steps to the website of OntoLinux.

    Clarification
    It is long time ago since we worked on The Proposal and The Prototype respectively the Evolutionary operating system (Evoos), and also the foundations of the Ontologic System (OS), which is based on the Evoos and comprises many elements of it. But when thinking about

  • a highly suspicious document mentioned in the Website review of the 23rd of August 2017, discussed in the Clarification of the 23rd and 24th of August 2017, and the last section of the OntoLix and OntoLinux Website update of the 25th of August 2017, and mentioned in the first investigative case of the Investigations::Multimedia, AI and KM of the 28th of August 2017, and also
  • the other investigative cases of said Investigations::Multimedia, AI and KM,

    then we remembered that our Evoos has as features

  • network and other communication functionalities, as listed by the point "die Netzwerkfunktionen==the network functions or features" in the chapter 2.2.1 Komponenten eines Betriebssystems==Components of an Operating System of The Proposal, and as already noted in the OntoLix and OntoLinux Website update of the 25th of August 2017, and also
  • Natural Language Processing (NLP) capability as an evolving and learning cognitive agent, for sure,

    which have already been listed even together in the chapter 5 Zusammenfassung==Summary of The Proposal "das Hören - das Mikrofon, die Netzwerkkarte und das Modem==the hearing - the microphone, the network card and the modem" and "das Sprechen - der Lautsprecher, die Netzwerkkarte und das Modem==the speaking - the loudspeaker, the network card and the modem" on the one hand and on the other hand all have to be regarded when discussing such issues.
    That said, elemental parts of the semantic network, including the semantic grid, and the cognitive network, including the cognitive grid, are already described in The Proposal.
    At this point we also would like to recall that the same holds for the

  • Natural Image Processing (NIP) capability, which is also listed in the chapter 5 Zusammenfassung==Summary "das Sehen - die Videokamera und der Scanner==the seeing - the video camera and the scanner",
  • Natural Multimodal Processing (NMP) or Natural Sense Processing (NSP) capabilities, which are also listed in parts in the in the chapter 5 Zusammenfassung==Summary "das Fühlen - die Tastatur und die Maus==the feeling - the keyboard and the mouse", as well as
  • security, as listed in the chapter 2.2.1 Komponenten eines Betriebssystems==Components of an Operating System "das Sicherheitssystem==the security system" and in the chapter 2.2.2 Dienste eines Betriebssystems==Services of an Operating System "Die zweite Menge dient nicht speziell einem Benutzer, sondern sichert die effiziente Ausführung des Betriebssystems im Mehrbenutzerbetrieb. Sie umfasst die Dienste für die Resourcen-Allokation, die Abrechnung bezüglich benutzter Resourcen und die Ausführung von Sicherheitsmaßnahmen.==The second set does not serve specifically for a user, but secures the efficient execution of the operating system in the multi-user mode. It comprises the services for the resource allocation, the acounting with respect to used resources and the execution of security measures.", which is also relevant for grid computing, cloud computing, and edge computing.

    As can be seen even better now, the combinations of cloud computing with cognitive computing, as well as a smart speaker, an autonomous vehicle, or/and a cyber-physical system, and also the cognitive grid potentially constitute copyright infringements because they are based on essential parts of our original and unique Evoos and OS.

    Besides this, we have found the next copyright infringement of the criminal author and other plagiarists that we will document together with the missing complete investigation of her other paper, that is not so highly suspicious anymore. :)

  •    
     
    © and/or ®
    Christian Stroetmann GmbH
    Disclaimer