Home → News 2020 July
 
 
News 2020 July
   
 

02.July.2020

21:11 UTC+2
SOPR #292

*** Work in progress - maybe ready for Proof-reading mode ***
Topics:

  • Legal matter [joint ventures]
  • License Model [research] or Digital rights [signals and data properties]

    Legal matter [joint ventures]
    In the issue SOPR #291 of the 30th of June 2020 we already discussed potential measures to protect the neutrality and independence of our Society for Ontological Performance and Reproduction (SOPR).
    Today, we would like to inform the public that we decided for the expansion of the clause in the Articles of Association (AoA) and the Terms of Services (ToS) of our SOPR, that regulates the establishment of joint ventures between ... by including companies, in which a state participates and for which rules exist concerning the

  • voting rights and restrictions on voting rights, in particular
    • blocking minority,
  • purchase and sale of company shares,
  • prevention of a takeover of said company, or
  • any other legal option and regulation, which grants said state a veto right in all important decisions taken by said company.

    License Model [research]
    At first, we would like to note that one can see how closely connected the fields of grid computing and cloud computing are and therefore have been brought together by us as the so-called field of Grid, Cloud, Edge, and Fog Computing (GCEFC), which again is included in our field of Ontologic Computing (OC) and hence in our Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV).

    Proponents of the so-called National Cloud Computing initiative in the U.S.America say that "[scientists] need to get scientific research on the public cloud" and propose that "[t]he research cloud would use the [grid and] cloud [computing data centers] of the tech companies. Academic scientists would be government-subsidized customers of the tech giants, perhaps at rates below those charged to their business customers."
    Similar considerations and suggestions are made by the member states of the European Union (EU) and the European Commission (EC).

    The following clauses included in the AoA and the ToS of our SOPR are sufficient to handle such initiatives and similar cases:

  • Our SOPR is political neutral and independent.
  • All or nothing at all, which prevents all attempts to exploit our compromise for opening our OS for everybody as a legal loophole.
  • The unrestricted access to raw signals and data for our SOPR has to be granted. which prevents any attempt to exploit our compromise for opening our ontological system to all as a legal loophole
    Marketplace for Everyhting (MfE) of the infrastructure of our SOPR is the common place of trading for members and licensees of our SOPR, where owners of raw signals and data, informations, knowledge, models, algorithms, and so, can offer their digital properties to any entities, including national research institutes, and under any terms and conditions, that are legal in a jurisdiction, which we highly recommend to our members and licensees.
  • Services have to be registered with service interfaces (e.g. Application Programming Interfaces (APIs)) at our SOPR.
  • The establishment of joint ventures between federal and public institutes (e.g. universities) and our SOPR is required.
  • An exemption for the establishment of a joint venture is only possible in a very special and reasonable case essential to national security, but not in a case essential to ordinary economic competitiveness or protectionism.
  • In the issue #... of the ... we already addressed this and said that we will estimate the correct rates.
  • The License Model (LM) comprises licensee classes for federal and public authorities and institutes without and with Information and Communication Technology (ICT).

    We find the argument of national security submitted in this case a little thin. In fact, the related regulation of an exemption in the AoA and the ToS was meant for only the military in case an establishment of a joint venture between a federal authority and our SOPR, Ontonics, or a business unit of our corporation is not possible due to laws concening national security.
    But we also understand and find it reasonable that there is an interest of nations to keep the treasure trove of signals and data as an economical advantage, due to the opinion that signals and data are the oil of the 21st century.

    {not decided; ICT faculties and so on of federal and public research institutes and universities are basically another type of ICT sector} We expand the licensee class for non-ICT with ICT by adding federal and public authorities and institutes with ICT.


    12.July.2020

    Ontonics Further steps

    We have developed a new device and two variants of it by adapting a well-known device to test in real-time whether a person has a viral respiratory disease.
    This would make alternative measurements possible in case a drug is not available or long-term immunity is not achievable.


    17.July.2020


    18.July.2020


    20.July.2020

    OntoLix and OntoLinux Further steps

    We looked at the possibilities of utilizing specific networking standards and protocols related to our Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV).

    We also worked on the implementation of a basic functionality of our Ontologic System (OS), which is responsible for increasing its performance on various levels.


    23.July.2020

    Clarification

    Our success story continues and there is no end in sight.
    "Online collaboration platforms and related tools have become as important to us as smartphones Ontoscopes and computers," said a professor at the Sloan School of Management at the Massachusetts Institute of Technology in the U.S.A..
    And what is one of the basic properties of our Ontologic System (OS)? Yes, indeed, (mostly) being collaborative, besides for example the other properties listed in for example the message Ontoscope Further steps of the 17th of March 2020.

    Once again, we got the proof that our OS is visionary, beyond state of the art, and more human than human, and therefore copyrighted in whole or in part.


    25.July.2020

    Ontonics Further steps

    We continued the work on the new device mentioned in the Further steps of the 12th of July 2020.

    The estimated result based on comparable applied approaches:

  • detection rate: around 95%
  • detection time: around 30 seconds

    in case of an infection with the Severe Acute Respiratory Syndrome CoronaVirus 2 (SARS-CoV-2).
    We have the opinion that our solution is much better than

  • testing in the common way with turnaround times of 5, 9, 12, or 15 days on the one hand and
  • merely measuring the temperature in the same time on the other hand.

    Is not it?

    Interested governments, companies, and other entities can, or better said, should contact us As Soon As Possible (ASAP) Or Even Better Immediately (OEBI).
    By the way: Did we mention in the Further steps of the 24th of March 2020 that we also developed something else?


    26.July.2020

    02:51, 17:56, and 20:06 UTC+2
    SOPR #293

    *** Work in progress - last chapters not ready, some contents might be removed ***
    Topics

    This issue is about various topics with one focus laid on legal and joint matters:

  • Legal matter
  • Legal matter [joint ventures]
  • Digital rights
  • License Model (LM)
  • P.R.China [Discounts]
  • Interoperability
  • Healthcare 4.0
  • Tourism
  • Transition process [Takeovers]

    Legal matter
    Freedom demands rules, that apply for everybody.

    The issue of how the old Internet and the old World Wide Web (WWW) were regulated or regulated themselves was one of the most important issues imaginable. But entities have created a crisis of trust of knowing what is true and what is not true, which led to the very sad situation that the opportunity offered by the Internet and the WWW got into a worrying and alarming degree of trouble.
    With the creation of our Ontologic System (OS) with its

  • Ontologic Net (ON), which is the successor of the Internet,
  • Ontologic Web (OW), which is the successor of the World Wide Web (WWW), and
  • Ontologic uniVerse (OV), which is something totally new

    we want to pull this incredibly valuable thing off.
    One important activity is providing and guaranteeing openess, interoperability, and equality in the whole OS for all members and licensees of our Society for Ontological Performance and Reproduction (SOPR) (see the sections Interoperability and Social and Societal System (SSS) below).

    In this context, we would like to make our monthly recall for newbies or unteachable ones and tell or remind them that our SOPR is the neutral hub of all activities in the

  • legal scope of our digital rights, digital interest, digital property, or digital estate,
  • legal scope of our Ontologic System (OS),
  • domain of our New Reality (NR) respectively
  • sovereign space of our OntoVerse (OV), also known as OntoLand (OL),

    but not the rock in the way.
    Nevetheless, we will react in appropriate and reasonable ways, if an entity attempts to circumvent our SOPR.

    Accordingly, producers and providers of technologies, goods, and services have to sign the Articles of Association (AoA) and the Terms of Services (ToS) with the License Model (LM) of our SOPR, where it is clearly said that Ontologic Applications and Ontologic Services (OAOS), which include every applications and services

  • exectuted on a device, a vehicle, or any other hardware based on our Ontologic System Components (OSC) or our Ontoscope Components (OsC), or
  • operated or utilized in our OS with its ON, OW, and OV,

    have to be stopped from working and removed, if their producers and providers refuse to comply with the AoA and the ToS of our SOPR.

    They pledged to work with federal and state authorities to agree shared jurisdiction over the land.
    "The Nations and the state are committed to implementing a framework of shared jurisdiction that will preserve sovereign interests and rights to self-government while affirming jurisdictional understandings, procedures, laws, and regulations that support the public safety, the economy, and the private property rights," the statement said.

    At the end, we would like to give our friends in the U.S.A., the P.R.China, the European Union, the Russian Federation, and every other country and grouping of states on planet Earth the friendly note, that nobody can

  • get out of this matter and
  • gamble in this respect

    anymore, neither do we, because we have that priced in our revised License Model (LM) and there is still significant room for improvements of our Fair, Reasonable, And Non-Discriminatory, As well as Customary (FRANDAC) terms and conditions.

    Therefore, if such interferences are not stopped immediately, then we will take back the related parts of our AWs and further IPs without paying the costs, or said in other words, the interferers and troublemakers have to pay these costs as well.

    Legal matter [joint ventures]
    The regulation concerning the establishment of joint ventures between companies with state participation and C.S.Owned Enterprises (CSOEs) is not a loophole in the sense of that a participation of a state is done for reaching joint venture status besides influence, because the

  • engagement of a CSOE in a joint venture can be 0 to 100%, and
  • exclusivity of the
    • OS with its ON, OW, and OV,
    • management structure of our ON, OW, and OV,
    • (OSystem) core executed in the 1st layer and related ID spaces and universes of the management structure of our ON, OW, and OV,
    • infrastructure of our SOPR, and
    • Ontologic Economic System (OES)

      with their subsystems and platforms, and

    • power of control and management concerning the OS with its ON, OW, and OV, the management structure, and the infrastructure by our SOPR

      remain,

    and

  • joint ventures are at the edge of said exclusive parts respectively said scope of power of control and management by SOPR.

    Digital rights
    Once again, the discussion is about the federal request for

  • access to fixed inventory data such as name, address, and date of birth, but also the IP addresses used, and
  • data retention for 6 months.

    License Model (LM)
    We were thinking about

  • introducing the License Model (LM) with the 7, 17, 27 proposal for the
    • banned companies and
    • member states of the G20 and the wealthier or richer member states of the EU,

    or

  • making a reset of all disputs and withdrawal of granted discounts due to the
    • latest revision of our License Model (LM) with the 7, 12, 17 proposal,
    • regulation concerning the unrestricted access to raw signals and data, and also
    • other regulations, as well as terms and conditions of our SOPR.

    Eventually, we decided for making the reset and beginning again with the known procedures of our SOPR.

    P.R.China [Discounts]
    We are also doing an audit to decide if we have to withdraw 2, 3, or 4 discounts granted for the People's Republic of China, because the country

  • is not a democracy,
  • does not allow freedom of speech,
  • has infringed our rights related to our Artworks (AWs) and further Intellectual Properties (IPs), and
  • does not fulfill other requirements in order to be eligible for certain discounts by our SOPR.

    Interoperability
    Similar to the important network neutrality for Internet Service Providers (ISPs) we have some kind of OS neutrality and SOPR neutrality for all Ontologic Service Providers (OSPs). In addition, we have social, societal, political, legal, and technological demands and developments. All cannot be provided, guaranteed, and protected by members and licensees of our SOPR with their proprietary parts of our OS, but by our SOPR.

    Generally, Cloud Service Providers (CSPs or CloudSPs) of so-called public clouds, like for example Amazon Web Services (AWS), IBM Cloud, Oracle Cloud Infrastructure, Microsoft Azure, Google Cloud, and Alibaba Cloud, own and operate the infrastructure at their data center and provide access to their facilities generally via the Internet. In addition, some providers have already begun to offer direct connect services on dedicated private network (fiber) connections {is this truly possible?} and in this way to realize their own subON or even illegal OS clone:

  • AWS Direct Connect,
  • Oracle FastConnect,
  • Microsoft Azure ExpressRoute, and
  • Google Cloud Interconnect.

    Such connections require customers to purchase or lease a private connection to a peering point offered by the cloud provider.
    (Advanced) Direct Connect ((A)DC) has a Peer-to-Peer (P2P) file sharing (and chat) protocol. ((A)DC) clients connect to a central hub and can download files directly from one another.
    The increases of this development is a

  • private link, which provides private access to services hosted on a proprietary cloud computing platform, keeping the customer's data on the proprietary network of a CloudSP through private connectivity from a virtual network to a Platform as a Service (PaaS) without the public Internet,
  • virtual network or private network in the proprietary cloud network, which provides connectivity of private infrastructure on-premises networks to proprietary cloud or network of a CloudSP through site-to-site Virtual Private Networks (VPNs), and
  • virtual Wide Area Network (WAN) in the proprietary cloud network, which provides unified, global connectivity and security.

    As we already explained in the past, CloudSPs are now where we already are all the time with the

  • hybridyzation (legacy or on-premise, private, and public deployment),
  • multiplication,
  • integration, and
  • hyperconvergence

    of for example

  • High Performance and High Productivity Computing (HP²C),
  • Peer-to-Peer Computing (P2PC), and
  • Grid, Cloud, Edge, and Fog Computing (GCEFC)

    as part of our ON, OW, and OV.

    Obviously, the basic properties of the underlying old Internet and old World Wide Web (WWW) are already changing with our ON, OW, and OV, and their new features on the basis of

  • Network Function Virtualization (NFV) (see also our Evolutionary operating system (Evoos) included in our OS with its integrating Ontologic System Architecture (OSA)),
  • Software-Defined Networking (SDN) (see once again our Evoos and OSA),
  • Scalable Distributed Tuplespace (SDT),
  • Space-Based Architecture (SBA),
  • Non-Deterministic Networking (NonDetNet or NDetNet) and Deterministic Networking (DetNet) based on Audio Video Bridging (AVB)/Time-Sensitive Networking (TSN), and SDN, and therefore to a very large extent on our OS (see its basic properties) with its ON for Integrated Services (IntServ) and Differentiated Services (DiffServ),
  • Wide Area Network (WAN) High Performance and High Productivity Computing (HP²C),
  • mobile computing,
  • Virtual Object System (VOS),
  • Information-Centric Networking (ICN),
  • Content-Centric Networking (CCN),
  • etc.

    (see the related Clarifications and Further steps of the {dates missing} ... January 2020).

    But we do much more with our

  • OS with its ON, OW, and OV,
  • management structure of our ON, OW, and OV,
  • infrastructure of our SOPR, and
  • Ontologic Economic System (OES)

    with their subsystems and platforms, including for example

  • Universal Ledger (UL), including the only legal Distributed Ledger Technology (DLT),
  • High Performance and High Productivity Computing (HP²C),
  • IDentity Access and Management System (IDAMS),
  • Collaboration and Communication System (Co²S),
  • and so on.

    In many cases we address technologies, goods, and services related to Microsoft Azure as examples, which are not supporting openess and interoperabiltiy, though in most of the cases or even all of them we found the services by other CloudSPs as well. We are not opening our OS only to support and see that large companies are building up restricted, closed, or proprietary systems, goods, and services, which in most of the cases would even reward them for stealing our ArtWorks (AWs) and further Intellectual Properties (IPs) before. Obviously, that is totally ridiculous.
    The proprietary cloud network between the data centers of the companies Microsoft and Oracle has been discussed in relation to the infrastructure of our SOPR in the issues #... of the ... and #... of the ... {links missing}.
    The directory service or name service called Active Directory (AD) of the company Microsoft has been discussed in relation to our ON, OW and OV, and also IDAMS in the issue SOPR #290 of the 24h of June 2020.

    Matter, which is related to

  • hybridyzation, multiplication, integration, and hyperconvergence,
  • os-level virtualization or containerization, and also
  • network-level virtualization and network function virtualization,

    is considered to be highly problematic due to the not discussible demands for

  • legality and legal certainty,
  • openness and interoperability, as well as
  • freedom of choice, innovation, and competition

    pro bono publico==for the public good and all other entites concerned.

  • (Advanced) Direct Connect ((A)DC) due to the reason that it is not Platform as a Service (PaaS), as designated, but Infrastructure as a Service (IaaS) or just infrastructure of SOPR
    • Amazon Web Services (AWS) Direct Connect,
    • Microsoft Azure ExpressRoute,
    • Oracle FastConnect, and
    • Google Cloud Interconnect,
  • {telcos have that as well, but not all the software; demands can be fulfilled when services, inclusive containers and their APIs, are registered at SOPR} proprietary cloud network due to the reason that it is infrastructure of our SOPR
  • virtual network or private network in the proprietary cloud network due to the reason that it is infrastructure of SOPR
  • {traffic remains on the proprietary cloud network of the CloudSP, with no public old Internet access, which implies no public ON} Azure Private Link due to the reason that it is IaaS or just infrastructure of SOPR
  • Azure Stack consistent hybrid cloud respectively Azure-based private cloud due to the reason that it is Infrastructure as a Service (IaaS) or just infrastructure of our SOPR
    • Azure Stack Hub is cloud-native intergrated system,
    • Azure Stack HCI is HyperConverged Infrastructure (HCI) operating system, and
    • Azure Stack Edge is cloud-managed edge-computing appliance with hardware-accelerated SoftBioncs (SB) based on Azure
  • Amazon Web Services (AWS) Outposts due to the reason that it is Infrastructure as a Service (IaaS) or just infrastructure of our SOPR
    • VMware Cloud on AWS
    • AWS native

  • IDAMS
  • Spatial Anchors for Mediated Reality (MedR), including Augmented Reality (AR), Augmented Virtuality (AV), Virtual Reality (VR), and Mixed Reality (MR), is PaaS or IaaS of SOPR

  • Free and Open Source Software (FOSS) due to the reason that it is Evoos, OS, IaaS, or just infrastructure of SOPR
    • many or even most projects of the Linux Foundation
      • some parts of the operating system (os) Linux related to basic os concepts and functionalities,
      • Cloud Native Computing Foundation (CNCF),
      • Open Container Initiative (OCI) standards for os-level virtualization or containerization due to the reason that it is Evoos included in OS,
      • Open Network Operating System (ONOS),
      • Open Network Automation Platform (ONAP),
      • Distributed Ledger Technology (DLT) Hyperledger,
      • projects in the field of Internet of Things (IoT),
      • and so on,
    • many projects of the Apache Software Foundation (ASF)
      • Azure Databricks is collaborative Apache Spark and
      • Apache ARIA based on Cloudify based on Topology and Orchestration Specification for Cloud Applications (TOSCA),
    • some projects of the Open Connectivity Foundation (OCF)
      • IoTivity and
      • AllJoyn,
    • some standards of the Organization for the Advancement of Structured Information Standards (OASIS)
      • Topology and Orchestration Specification for Cloud Applications (TOSCA) and
      • Cloud Application Management for Platforms (CAMP),
    • several as a Service (aaS) capability models of the company Microsoft
      • Azure IoT based on AllJoyn and IoTivity,
      • Azure Container Registry based on OCI and supporting Azure Kubernetes Service, Azure Red Hat OpenShift, and Singularity (also illegal)
      • Azure Kubernetes Service (AKS),
      • Azure Red Hat OpenShift is an on-premises PaaS built around Docker containers orchestrated and managed by Kubernetes on a foundation of Red Hat Linux,
      • Azure Service Fabric powers core infrastructure as well as other services, orchestrates containers and microservices on proven reliable, and self-healing or self-regenerative platform,
      • Azure Blockchain based on Ethereum and Hyperledger Fabric,
    • etc.

    Matter that is problematic due to overlaps with the infrastructure of our SOPR:

  • Identity & Access Management due to ON, OW, and OV, and IDAMS
    • Azure Active Directory,
    • Azure Active Directory Domain Serivces, and
    • Multi-Factor Authentication
  • Azure DNS (acronym for Domain Name Service) due to ON, OW, and OV
  • Azure Digital Twins due to the reason that public digital twins and spatial anchors are PaaS or IaaS of SOPR
  • Azure API for FHIR (acronym for Fast Healthcare Interoperability Resources) due to Healthcare 4.0
  • Connected Health due to Healthcare 4.0
  • Connected Vehicle due to the reason that the Hyperconnectivity cloud computing suite of Style of Speed is SOPR

    Terms that are not acceptable:

  • Logic Apps due to confusion with Ontologic App(lication)s and also wrong, because here only for workflow, but not for anything related to Logic Programming (LP)

    Social and Societal System (SSS)
    social network and societal network platforms versus social media
    There is confusion about the very nature of the field of interaction networking, including social networking and societal networking, and providing the basis for social media.

    Social networks are not the uncontrolled press and social media are not the uncontrolled common media.
    Companies, like for example Twitter, Snap, and Reddit, are not viewed by European courts as social networking platforms.

    While social networking and societal networking platforms enable the connection of entities, social media platforms enable also the publication and sharing of content between the entities connected by the networking platforms.
    Moderation is an essential activity of a platform to keep entities connected.
    In this regard it is important to note that while interaction networking platforms do not create and present own contents, they nevertheless develop and utilize algorithms to manage the way of networking, connecting, and moderating, and therefore also the way of developing, controlling, and moderating the public opinions.

    Demands of activists

  • civil rights,
  • anonymity,
  • advance equality and fight discrimination, while also safeguarding free expression,
  • elevating free expression, which must apply to everyone and does not privilege certain voices over less powerful voices by
    • demanding that everyone has to abide by the same rules, and
    • preventing or avoiding a hierarchy of speech.

    Demands for activities and a system (e.g. algorithms), which actually

  • does moderation,
  • catches real-time misinformation, and
  • enables participation in the activities of a platform (e.g. management).

    In general, any liberation only leads to an attack on the power of control and eventually to a situation, where another clique becomes the gatekeeper and arbiter of truth respectively narrator and moderator of alternative truths and fake news.

    The last point of the demands and activities surely comes from the press, which has

  • proven the general insight noted before by claiming the control over the public opinion, but also
  • lost influence, control, and power, because social networking overcomes exactly this deficiency.

    But social networking does not overcome the deficits inherent in the field of interaction networking, because it has proven the general insight noted before.

    Healthcare 4.0
    An Electronic Health Record (EHR) or Electronic Patient Record (EPR) is also subject to the regulation that we have unrestricted access to raw signals and data.

    Healthcare 4.0 is

  • organizing the medical appointments, which is ideally integrated with a societal networking platform.
  • collecting and analyzing data to improve the
    • health management in general and
    • diagnostics in particular.

    The digital speech assistant Doctor Algorithm replaces the first consultation with the family doctor or primary care physician, if they receive enough data.
    Many users are willing to enter their personal data in online search engines when it comes to the (self-)analysis of disease symptoms.

    The ride sharing company shares personal data in the U.S.A., but also with at least 29 countries, including Australia.
    Also interesting is the detail that the Healthcare 4.0 service was quitly introduced without asking us and that it was quitly used by 29 countries.

    Obviously, part of our Healthcare 4.0 subsystem and platform of the exclusive infrastructure of our SOPR based on our OS and our user data.

    Our Healthcare 4.0 is the neutral hub where raw signals and data, informations, and interfaces to models and algorithms go in and out.
    Therefore, such service portals have to be handed over to our SOPR as well, like all virus apps and other warning apps of countries or companies.

    Tourism
    We have already started with collecting informations about the various technologies (e.g. systems and platforms), goods (e.g. applications, devices, and vehicles), and services utilized in the field of tourism in recent months for the reasons of legal matter, technological support, and royalty accounting.

    In general, we have here systems of the fields of multimedia and CPS, IoT, and NES.

    Transition process [Takeovers]

    In contrast to some governments we adhere to contracts and other legally binding agreements.
    Therefore, our HighTech Office Ontonics adheres to our takeover bids and declares them as still being effective as long as we get the takeover procedures done by the transition process, comprising damage compensations, admission fees, outstanding royalties, etc..


    28.July.2020

    Clarification

    Do you remember?

  • "The buzzword du jour in service-oriented architectures [(SOA)] is ESB. Enterprise service buses are the preferred tools for integrating systems with heterogeneous data interchange interfaces and based on a wide array of technologies, from [the programming language COmmon Business-Oriented Language (]COBOL[)] to [Common Object Request Broker Architecture (]CORBA[)] to [Java Enterprise Edition (]JEE[)].", [1st of January 2007]
    :D

  • An online encyclopedia: "Heroku is a cloud platform as a service (PaaS) supporting several programming languages. One of the first cloud platforms, Heroku has been in development since June 2007, when it supported only the Ruby programming language, but now supports Java, Node.js, Scala, Clojure, Python, PHP, and Go.[...] For this reason, Heroku is said to be a polyglot platform as it has features for a developer to build, run and scale applications in a similar manner across most languages."
  • "PaaS' days as a stand-alone tech may be numbered as the cloud layer gets absorbed by IaaS platforms from AWS and others. [...] PaaS has never truly lived up to its early billing as the future of cloud computing. [...]
    To understand what led us here, let's go back to 2008 for a moment. The National Institute of Standards and Technology [(NIST)] was forming the way we defined the types of cloud. IaaS was for workloads traditionally found in the data center, such as storage and compute platforms; SaaS was for static business processes presented as over-the-internet applications; and between the two there was PaaS. [...]
    It's also worth remembering that Microsoft and Google's initial forays into cloud were focused on PaaS but both quickly moved to IaaS and have kept their focus there since. Meanwhile, AWS, which began with IaaS, later added PaaS [...]. [...]
    Moreover, the lines between IaaS and PaaS have blurred to near invisibility as AWS, Microsoft and Google continue to add features and functionality that fill the gaps between the two cloud computing [as a Service (aaS) capability] models, particularly around app development.", [16th of July 2019]
    Honestly, we stopped between 2008 and 2016 to learn and follow what was marketed as cloud computing and only thought about it: "What a nonsense. They will all end up coming to our OS anyway." And indeed, the Cloud Service Providers (CSPs) did all the moves of hybridyzation, multiplication, integration, and hyperconvergence as well, while blurring the lines between IaaS and PaaS.
    Today, we do know and also have proven by showing a vast amount of evidence that they were at our OS all the time.

    There is also significant evidence that we created the field of translyse, including the field or category of translytical database, with our OS as well.
    Simply said, translytical is transactional, operational, and analytical (near-)real-time signals and data, information, and model handling within a flat stack layer respectively a convergend or even a hyperconvergend system.
    Therefore, a translytical platform is not just a database with an in-memory and a little Business Intelligence (BI) functionality, but a part of our Ontologic System Components (OSC), specifically the OntoCore (OC or OCore) and OntoBase (OB or OBase) components with their integration but also combination on the basis of microService-Oriented Architecture (mSOA) respectively what we as the original creator called liquid computing and Ontologic Computing (OC or OntoC).

    Eventually, we made

  • SoftBionics (SB) (including AI, ML, CV, CAS, etc.),
  • operating system-level Virtualization (oslV) or containerization,
  • Network Function Virtualization (NFV),
  • Software-Defined Networking (SDN),
  • Software-Oriented technologies (SOx) and Everything as a Service (EaaS),
  • utility, grid, cloud, edge, and fog computing, and also as a Service (aaS),
  • mobile computing,
  • Cyber-Physical System (CPS), Internet of Things (IoT), and Networked Embedded System (NES),
  • Collaboration and Communication (Co²) (see also the note of the 23rd of July 2020),
  • self-driving vehicles,
  • and so on

    the outstanding successes and chapters of our success story after they failed, and also added much more new things, which were not conceived, created, or realized at all.
    And because we knew that the whole world will be on fire due to our OS, we made it a work of art, which taken alone as an act of creation already guarantees its copyright protection one more time besides the OS itself seen as a further expression.

  •    
     
    © or ® or both
    Christian Stroetmann GmbH
    Disclaimer