Home → News 2018 July
 
 
News 2018 July
   
 


04.July.2018
SOPR #124
The last weeks and especially the last findings in relation with actings of companies as well as research institutes showed that some sections of the Articles of Association (AoA) and the Terms of Service (ToS) with the License Model (LM) of our Society for Ontological Performance and Reproduction (SOPR) require a revision.
Accordingly, the members of our SOPR, actually only one with the supervisor, have decided unanimously with a sufficient majority of 100% of the eligible voters to revise the AoA, ToS, and LM where required and reasonable, and to address other points as well:

  • membership in the SOPR and
  • License Model (LM)
    • structure and
    • structure of royalties for Ontologic Applications and Ontologic Services (OAOS),

    and

  • licensing of investments.

    Membership in the SOPR
    The provision for the membership in the SOPR might be changed by

  • letting only persons become members of the SOPR, which would directly happen in the moment of their first use of our OS, and
  • making members more passive, which would mean that the Steering Committees are transformed into Consulting Committees, which again sounds good as well.

    License Model (LM)
    The correct answer to the strategy practiced by the entities of government, press, industry, science, and other elements of society would be to

  • demand
    • doubled fixed fees for a reproduction of the Ontologic System (OS), the Ontoscope (Os), and the other works of C.S., and
    • doubled share for a performance of the OAOS,

    and

  • make the labelling of products, applications, and services, that are
    • reproductions of our OS and our Os, and performances of our OAOS, or/and
    • OAOS based on our OS or/and our Os,

    the default licensing option and provide entities, that wish an exception for this labelling of their products, applications, and services, a related licensing option, which would ask for a

  • 50 to 100% higher fixed fee for a reproduction of the OS, the Os, and the other works of C.S., and
  • 50 to 100% higher share for a performance of the OAOS,

    which by the way is common practice in handling an infringement of a copyright.
    But honestly, in total contrast to a solution for the issue with the open source licensing we are not interested for that publicity, though we already feel that the increasing publicity is unavoidable.
    Nevertheless, we think that a

  • 50% higher fixed fee for a reproduction of the OS, the Os, and the other works of C.S., and
  • 50% higher share for a performance of the OAOS

    are reasonable for the optional exception for this labelling of the related products, applications, and services.

    We are also working out how the proposed differentiated structure of the License Model (LM) would look like if the royalties for basic OAOS are lower but for advanced OAOS are higher. This has to be balanced with the licensing option for the exception for labelling.
    For this, we formed fields in accordance with the basic properties of our OS and with related percentages as share:

  • 0% - basic fields
  • 2% - improved basic fields
  • 3% - significantly improved basic fields
  • 4% - advanced combinations and integrations
  • 5% - basic OAOS
  • 6% - improved basic OAOS
  • 7% - significantly improved basic OAOS
  • 8% - advanced OAOS
  • 9% - high OAOS
  • 10% - pure OAOS (applications and services of the 21st century)

    In all fields all combinations and integrations of items of the fields with a lower percentage are included.
    In the following we give some very few examples what our LM expert system would provide:

    0% - basic fields

  • Operating system (OSys)
    • Reflective Operating System (ROS),
    • Real-Time Operating Systems (RTOS),
    • Capability-based Operating System (CapOS),
    • Agent-Based Operating System (ABOS), and
  • Data Base Management System (DBMS)
  • Distributed System (DS)
    • High Performance and High Productivity Computing System (HP²CS)
      • cluster computing,
    • gird computing, cloud computing, and edge computing,
    • Fault-Tolerant, Reliable, and Trustworthy Distributed System (FTRTDS)
      • blockchain-based system,
      • distributed ledger, and
      • cryptocurrency,
    • mobile computing,
    • as a Service (aaS) capability model, and
    • ...
  • Cyber-Physical System of the 1st generation (CPS 1.0), Internet of Things of the first generation (IoT 1.0), and Networked Embedded System of the first generation (NES 1.0)
  • Operations Management (OM)
    • Business Process Management (BPM) and
    • Workflow Management (WfM),
  • Quality Management (QM)
    • Total Quality Management (TQM) and
    • International Organization for Standardization 9000 (ISO 9000),
  • Product Lifecycle Management (PLM)
    • 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)
        • 3D printing,

        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)
  • Problem Solving Environment (PSE) and Scientific Computing Environment (SCE)
  • Mediated Reality Environment (MedRE)
  • Mixed Reality Environment (MRE),
    • Augmented Reality Environment (ARE) and
    • Augmented Virtuality Environment (AVE),
  • Virtual Reality Environment (VRE), and
  • Synthetic Reality Environment (SRE)
  • SoftBionics (SB) includes
    • Semantic (World Wide) Web (SWWW)
    • Artificial Intelligence (AI),
    • Machine Learning (ML),
    • Computer Vision (CV),
    • Cognitive Agent System (CAS),
    • Multi-Agent System (MAS),
    • Swarm Intelligence (SI) or Swarm Computing (SC),
    • Evolutionary Computing (EC)
      • Evolutionary Strategies (ES),
      • Evolutionary Algorithms (EA),
      • ...,
      • Genetic Algorithms (GA), and
      • Genetic Programming (GP),
    • Semantic (World Wide) Web (SWWW),
    • ...
  • Robotics (R)
  • quantified self or lifelogging
  • CPS 1.0, IoT 1.0, and NES 1.0 and MedRE
  • CAx and VRE

    2% - improved basic fields

  • exception-less system call mechanism
  • asynchronous I/O without context switch
  • RDMA over TCP/IP
  • Cloud Operating System (COS)
  • CAx and ARE
  • CAx and MRE

    3% - significantly improved basic fields

  • OSys and Multilingual Multimodal Multiparadigmatic Multimedia Multidimensional User Interface (M⁵UI)
  • exception-less system call and RDMA over TCP/IP
  • asynchronous I/O without context switch and RDMA over TCP/IP
  • reflective and ontologic middleware
  • HP²CS and FTRTDS
  • Data Center Operating System (DCOS)
  • HP²CS and CPS 1.0, IoT 1.0, and NES 1.0
  • FTRTDS and CPS 1.0, IoT 1.0, and NES 1.0
  • CPS 1.0, IoT 1.0, and NES 1.0, and CAx
  • cryptocurrency
  • CPS 1.0, IoT 1.0, and NES 1.0, and SB
  • CPS 1.0, IoT 1.0, and NES 1.0, and R
  • SWWW and R

    4% - advanced combinations and integrations

  • OSys and SB = Artificial Intelligence Operating System (AIOS)
  • ABOS and M⁵UI
  • HP²CS, FTRTDS, and aaS
  • FTRTDS and SB
  • FTRTDS and R
  • CAx and SB
  • PSE and SB
  • CAx and SRE
  • MedR and SRE
  • SB and SRE

    5% - basic OAOS

  • OSys, M⁵UI, and SB = AIOS and M⁵UI
  • HP²CS, aaS, and SB
  • FTRTDS, aaS, and SB
  • HP²CS, FTRTDS, and SB
  • CPS 1.0, IoT 1.0, and NES 1.0, MedRE, and SB = CPS 2.0, IoT 2.0, and NES 2.0
    • CPS 1.0, IoT 1.0, and NES 1.0, MedRE, and SWWW = Industry 4.0
  • CAx and SB (generative design and 3D manufacturing)
    • SWWW, generative design, and 3D manufacturing
  • CAx and R (generative design, and 3D manufacturing)

    6% - improved basic OAOS

  • aaS, CAx, and SB
  • CPS 2.0, IoT 2.0, and NES 2.0, and CAx
  • HP²CS and CPS 2.0, IoT 2.0, and NES 2.0
  • FTRTDS and CPS 2.0, IoT 2.0, and NES 2.0
  • FTRTDS, HP²CS, aaS, and SB
  • CPS 1.0, IoT 1.0, and NES 1.0, SB, and SRE
  • CPS 2.0, IoT 2.0, and NES 2.0, and R

    7% - significantly improved basic OAOS

  • FTRTDS, HP²CS, SB, aaS, and MedRE
  • FTRTDS, HP²CS, SB, aaS, and SRE
  • CPS 2.0, IoT 2.0, and NES 2.0, and SRE = CPS 3.0, IoT 3.0, and NES 3.0
  • qualified self or lifeenhancing

    8% - advanced OAOS

  • FTRTDS, HP²CS, aaS, and CPS 2.0, IoT 2.0, and NES 2.0

    9% - high OAOS

  • FTRTDS, HP²CS, aaS, and CPS 3.0, IoT 3.0, and NES 3.0

    10% - pure OAOS (applications and services of the 21st century)

  • teleportation
  • Weather Control (WC)

    If pure OAOS will be available for licensing at all has not been decided.

    See also the issue #123 of the 29th of June 2018.

    License for investments
    We think that we have found an easy way to handle investments in start-ups and other companies.
    In the case of a start-up, which has been founded on the basis of our OS, Os, or/and OAOS, we already said that we view the sale of a business share as some kind of revenue generated with our OS, Os, or/and OAOS, and will account this sale as an OAOS in accordance with for example the LM structure discussed above.
    To avoid double billing we only account the sale of a business share after the IPO respectively the first public trading at a stock market or a similar institution. This implies that the injection of fresh capital will not be viewed as some kind of a revenue.

    In the case of a company the corresponding ratio between the old value of said company before an investment, which is related to our OS, Os, or/and OAOS, and the new value of said company after this investment has to be calculated. This ratio will be applied on the revenue made with a sale of a business share.
    If we will find out that an investor, a start-up, or a company has tricked to keep the value and hence the revenue and our share of the revenue low, then we will take related measures. For example, we will exclude the company and also all responsible persons from collaboration with us respectively from the licensing process.


    05.July.2018
    Ontonics Further steps
    We have started a new project in a relatively new market sector. This new project is combined with another project of us and most potentially will become a new business division.

    SOPR #125
    Potentially, we will decide for the balance between the

  • licensing options related to the labelling of products, applications, and services, that are reproductions of our Ontologic System (OS) and our Ontoscope (Os), and performances of our Ontologic Applications and Ontologic Services (OAOS), and
  • differentiated structure of the License Model (LM) for the performances of our OAOS on the other side.

    The maximal percentage of a share should not be more than 7% so that the maximal percentage would be 7% + 3.5% = 10.5%.
    Pure OAOS are not available if they belong to the infrastructure of our OS, which is managed by our Society for Ontological Performance and Reproduction (SOPR).
    The revised LM will be publicated in detail as soon as possible and will become effective on the 1st of January 2019.
    Furthermore, we will begin with adjusting our LM by a medium inflation rate each year, which will become effective on the 1st of January 2019 as well and done the first time on the 1st of January 2020.

    In addition, we are also thinking about making every member of our SOPR an owner of her/his own platform for legal reasons related to the revision of the copyright law in the European Union (EU). Luckily, our foundational Managed Peer-to-Peer (MP2P) computing paradigm already discussed related situations, includes alternatives, and provides the foundation for forming an overall platform out of all these individual platforms.
    This approach also perfectly fits with

  • our developements and improvements in basic fields, like for example
    • High Performance and High Productivity Computing Systems (HP²CSs) and
    • Fault-Tolerant, Reliable, and Trustworthy Distributed Systems (FTRTDSs),

      specifically with our

    • SoftBionic (SB) supercomputer and
    • Ontologic supercomputer,

    and

  • recent developments, like for example the
    • attempt to introduce more data democracy and
    • realization of a personal data safe based on a blockchain or a distributed ledger or both.


    08.July.2018

    Investigations::Multimedia, AI and KM

    *** Work in progress - better short comments, wording, incomplete epilog ***

  • Apache Software Foundation: We already noticed around the year 2008 that the management and strategy of the Apache Software Foundation (ASF) has changed and then again around the year 2012 that the responsible entities are stealing essential parts of our original and unique, iconic work of art titled Ontologic System and created by C.S., indeed. Now, it is time to rip that bold mess apart and bring law and order to that foundation as well.
    To get an overview, we made a first sighting of its projects but can already estimate that around 30% of the projects of the ASF are infringing our copyright and other rights. Single prominent projects will be investigated at a later time in more detail.
  • University of California, Berkeley, and Mesosphere: Mesos
    "[...] is an open-source project to manage computer clusters. [...] Mesos was first presented in 2009 [...] at HotCloud '09 in a talk accompanying the first paper published about the project.[2 [[Nexus:] A Common Substrate for Cluster Computing]] [...] 2016, the Apache Software Foundation announced version 1 [... that] added the ability to centrally supply Docker, rkt [Linux containers or Container Linux] and appc instances. [...] Datacenter Operating System, a distributed operating system, based on Apache Mesos [...]" "categorizes components as being in user space or kernel space.[6] Kernel space includes the Mesos master and agents while user space includes various system components of Datacenter Operating System."
    (not OK) Indeed, there is prior art about the fields of semantic grid computing, semantic agent system for grid computing, and cognitive grid computing stolen by espionage. But in the overall context the quoted short text portion of the document titled "Nexus: A Common Substrate for Cluster Computing" already provides sufficient evidence that prove a causal link with our Ontologic System: "Nexus [respectively Mesos] is strongly inspired by work on microkernels [5 [Mach: A new kernel foundation for unix development]], exokernels [10 [Exokernel: An operating system architecture for application-level resource management]] and hypervisors [11 [Evolution of a virtual machine subsystem]] in the [operating system] community and by the success of the narrow-waist IP model [7 [A protocol for packet network intercommunication]] in computer networks. Like a microkernel or hypervisor, Nexus is a stable, minimal core that provides performance and fault isolation to frameworks sharing a cluster. Like an exokernel, Nexus aims to give frameworks as much control over their execution as possible. Finally, like IP, Nexus encourages diversity and innovation in cluster computing by providing a "narrow waist" API which lets different frameworks run over shared hardware."
    As can be seen easily, Nexus respectively Mesos is related to the fields of Multi-Agent Systems (MASs) and Agent-Based Operating Systems (ABOSs), and based on our Evolutionary operating system (Evoos) with Virtual Machine (VM) described in The Proposal based on the reflective, fault-tolerant, reliable, and Distributed operating systems (Doss) TUNES OS, and Apertos (Muse) and the Cognac system based on Apertos, our integration of the SPACE approach, which also discusses the microkernel Mach and the evolution of the Exokernel in accordance with SPACE, the microkernels L4 and OntoL4, the fields of hypervisors and operating system-level virtualization or containerization, the field of Distributed Computing (DC), including the fields of Doss and the fields of cluster computing, grid computing, and cloud computing, etc., our concept, architecture, and construction of the Internet as a supercompute, which implies the view of a data center as a computer, and so on are charateristic and essential features and parts of our original and unique Ontologic System (OS) and included in our variants OntoLix and OntoLinux (see the sections Operating System, Exotic Operating System, Network Technology, Intelligent/Cognitive Agent, etc.).
    The combination and integration with the other listed projects and with other external projects deepens in many cases the issue and provides more evidences that our OS has been taken as a blueprint without allowance, and the designation as a substrate (see also the Chemical Abstract Machine (CHAM)), Cloud operating system (Cos), and Data Center operating system (DCos), and the connection with scientific computing give that plagiarism the rest, doubtlessly and definitely.
  • Twitter: Aurora
    "[...] is a Mesos framework for both long-running services and cron jobs, originally developed by Twitter starting in 2010 and open sourced in late 2013.[...] It can scale to tens of thousands of servers, and holds many similarities to Google's Borg[9 [Large-scale cluster management at Google with Borg]][...] including its rich [Domain-Specific Language (]DSL[)] for configuring services."
    based on Mesos, which is not OK
  • Sentry
    [...] is a system for enforcing fine grained authorization and role-based access control to data and metadata stored on a Hadoop cluster through a single system and the ability to control and enforce precise levels of privileges on data for authenticated users and applications on a Hadoop cluster."
    Type enforcement, role-based access control, and (military) multi-level security are included in our Ontologic File System (OntoFS) software component.
  • Citrix Systems→VMOps later Cloud.com: CloudStack
    "[...] is [a] cloud computing software for creating, managing, and deploying infrastructure cloud services. It uses existing hypervisors [...]"
    Distributed Systems (DSs), microkernels L4 and OntoL4, and hypervisors are parts of our Ontologic System (OS).
  • Cloudsoft: Brooklyn
    "[...] is [a] framework for modeling, deploying and managing distributed applications defined using declarative [YAML Ain't Markup Language (]YAML[)] blueprints. The design is influenced by Autonomic computing and promise theory and implements the [Organization for the Advancement of Structured Information Standards (]OASIS[)] CAMP (Cloud Application Management for Platforms) and TOSCA (Topology and Orchestration Specification for Cloud Applications) standards."
    (not OK) In fact, there is prior art about the fields of semantic grid computing and semantic agent systems for grid computing stolen by espionage. But the integration of the distributed operating systems Apertos (Muse) and TUNES OS, Multi-Agent System (MAS), grid computing and cloud computing, as a Service (aaS), and the OntoBot and OntoBlender software components is an original and unique part of our Ontologic System (OS).
  • Edward J. Yoon: Hama

    "[...] is a distributed computing framework based on bulk synchronous parallel computing techniques for massive scientific computations e.g., matrix, graph and network algorithms. [...] (short for "Hadoop Matrix") and was inspired by Google's Pregel large-scale graph computing framework described in 2010." "The Bulk Synchronous Parallel (BSP) abstract computer is a bridging model for designing parallel algorithms. It serves a purpose similar to the Parallel Random Access Machine (PRAM) model. BSP differs from PRAM by not taking communication and synchronization for granted. [...] Communication typically takes the form of the one-sided put and get Direct Remote Memory Access (DRMA) calls [...]."
    (looks OK when taken alone) OntoBot and OntoScope, Problem Solving Environment (PSE) and Scientific Computing Environment (SCE), A simple implication of our Ontologic System Architecture (OSA) and the referenced systems, like for example KLOS and SPACE, Apertos (Muse), and TUNES OS, is that we added to the BSP model the Multi-BSP model, fault tolerance, and (somehow) tail tolerance for large-scale parallel computations in SoftBionics (SB), analytics, and High Performance and High Productivity Computing Systems (HP²CSs) including supercomputing systems or supercomputers, and grid computing and cloud computing systems. The related documents titled "A bridging model for multi-core computing" and "A Bridging Model for High Performance Cloud Computing" do not present new matter and therefore seem to be plagiarisms that provide no legal loopholes. By the way: Latency tail tolerance was discussed by the company Google as well.

  • National Security Agency (NSA) and Hortonworks→Onyara: NiFi
    "[...] is a [...] designed to automate the flow of data between software systems. It is based on the "NiagaraFiles" software previously developed by the NSA [...]. The software design is based on the flow-based programming model and offers features which prominently include the ability to operate within clusters, security using TLS encryption, extensibility (users can write their own software to extend its abilities) and improved usability features like a portal which can be used to view and modify behaviour visually. [...] Flow Controller - serves as the brains of NiFi's behaviour. Controls the running of Nifi extensions and schedules allocation of resources for this to happen. Extensions - various plugins that allow Nifi to interact with various kinds of systems[. ...] Provenance repository - data relating to the provenance of the data flowing through the system is maintained here. [...] HPE's SecureData for Hadoop and IoT software became Industry's first commercial product to integrate NiFi"
    (not OK) Flow-based programming is a particular form of dataflow programming and defines applications as networks of "black box" processes, which exchange data across predefined connections by message passing. Ontologic System Architecture (OSA), distributed computing paradigm, Problem Solving Environment (PSE) and Scientific Computing Environment (SCE), Blender and hence OntoBlender, OntoFS, provenance, Internet of Things (IoT)
  • Doug Cutting and Mike Cafarella, and Yahoo: Lucene→Nutch→Hadoop
    "[...] is a collection of [...] software utilities that facilitate using a network of many computers to solve problems involving massive amounts of data and computation. It provides a software framework for distributed storage and processing of big data using the MapReduce programming model. Originally designed for computer clusters built from commodity hardware [...]. [...] MapReduce tasks must be written as acyclic dataflow programs [...]."
    (looks OK when taken alone) The combination and integration with the other listed projects and with other external projects is in many cases too much and hence not OK. Besides this, the many and significant deficits of the MapReduce framework are more and more substituted with solutions based on our OS.
  • Doug Cutting: Hadoop→Avro
    "[...] is a remote procedure call and data serialization framework developed within Apache's Hadoop project. [...] Apache Spark SQL can access Avro as a data source."
    (looks OK when taken alone) The combination and integration with the other listed projects and with other external projects is in many cases too much and hence not OK.
  • Yahoo: Oozie
    "[...] is a server-based workflow scheduling system to manage Hadoop jobs. Workflows in Oozie are defined as a collection of control flow and action nodes in a directed acyclic graph. Control flow nodes define the beginning and the end of a workflow (start, end, and failure nodes) as well as a mechanism to control the workflow execution path (decision, fork, and join nodes). Action nodes are the mechanism by which a workflow triggers the execution of a computation/processing task."
    (looks OK when taken alone), Combination with the other listed projects and with other external projects is in many cases too much and hence not OK., combination with Ambari, Blender and hence OntoBlender, as well as Problem Solving Environments (PSE) and Scientific Computing Environment (SCE), Total Quality Management (TQM), and later Operations Management (OM),
  • Hadoop→Ambari
    "[...] enables system administrators to provision, manage and monitor a Hadoop cluster, and also to integrate Hadoop with the existing enterprise infrastructure. [...] The architecture of Apache Ambari includes two major components: Ambari Server and Ambari Agent. Ambari Server is responsible for interacting with the agents installed on the nodes, while Ambari Agents update the status of every node with the help of various operational metrics."
    (older versions might be OK but not younger extensions), basic properties like Multi-Agent System (MAS), self-adaptive, ...
  • Yahoo: Zookeeper
    "[...] is essentially a centralized service for distributed systems to a hierarchical key-value store, which is used to provide a distributed configuration service, synchronization service, and naming registry for large distributed systems. [...] ZooKeeper's architecture supports high availability through redundant services. [...] ZooKeeper can be viewed as an atomic broadcast system, through which updates are totally ordered. [Updates are totally ordered.]" "Google Chubby lock service [based on the Paxos protocol and] presented in 2006 is the inspiration for Apache ZooKeeper." "ZooKeeper [...] provides centralized infrastructure and services that enable synchronization across [nodes of] an Apache Hadoop cluster. ZooKeeper maintains common objects needed in large cluster environments. Examples of these objects include configuration information, hierarchical naming space, and so on. Applications leverage these services to coordinate distributed processing across large clusters. [...] Embedding ZooKeeper alleviates building synchronization services from scratch."
    (might not be OK even when taken alone) The project seems to be developed around the year 2008 and open sourced by Yahoo in the year 2010, which is a little too late as it is the case with for example the content of the related document titled "A simple totally ordered broadcast protocol" and published in the year 2008 when viewed in combination with other fields and projects, specifically the
    • fields of data stores, and grid computing and cloud computing, and
    • projects of the Hadoop (eco)system, like for example Zookeeper with NoSQL, NewSQL, Ambari, and/or SoftBionics (SB), including Artificial Intelligence (AI), Machine Learning (ML), Computer Vision (CV), etc..

    Also, some specific functions not included in e.g. Chubby but in our OS might be problematic, like for example the ephemeral nodes, which provide presence (information), fault-tolerant, reliable, and distributed operating system Apertos (Muse) and the Cognac system based on Apertos with (atomic) active object model and the actor model (inherent concurrency and thread safety), as well as the OS properties of (mostly) being validated and verified, and by the reflective property validating and verifying, and the Byzantine Fault Tolerance (BFT) protocols and the Byzantine-Resilient Replication (BRR) method shown with the network of telescopes, OntoFS, Twister and Twibber based on Jabber respectively eXtensible Messaging and Presence Protocol (XMPP) server jabberd2 included in the former project Underware, All prior art describe only Distributed Lock Managers (DLMs) but not BFT based processing of data, like for example systems based on the techniques of the smart contract protocol and the blockchain, such as distributed legers, blockchain platforms with Virtual Machines (VM), and cryptocurrencies.

  • Yahoo: Pig
    "[...] is a high-level platform for creating programs that run on Apache Hadoop. [...] SQL is oriented around queries that produce a single result. SQL handles trees naturally, but has no built in mechanism for splitting a data processing stream and applying different operators to each sub-stream. Pig Latin script describes a directed acyclic graph (DAG) rather than a pipeline. [...] Apache Pig was originally[...] developed at Yahoo Research around 2006 for researchers to have an ad-hoc way of creating and executing MapReduce jobs on very large data sets. In 2007,[...] it was moved into the Apache Software Foundation."
    (looks OK when taken alone), OntoFS, OntoBot, and OntoBlender, which also allows a Directed Cyclic Graph (DCG)
  • University of California, Berkeley: Spark
    "[...] is [a] cluster-computing framework. [...] Spark provides an interface for programming entire clusters with implicit data parallelism and fault tolerance. [...] Apache Spark has as its architectural foundation the resilient distributed dataset (RDD), a read-only multiset of data items distributed over a cluster of machines, that is maintained in a fault-tolerant way. [...] Spark and its RDDs were developed in 2012 in response to limitations in the MapReduce cluster computing paradigm, which forces a particular linear dataflow structure on distributed programs. [...] Spark's RDDs function as a working set for distributed programs that offers a (deliberately) restricted form of distributed shared memory.[8 [Resilient Distributed Datasets: A Fault-Tolerant Abstraction for In-Memory Cluster Computing[, 2010]]] Spark facilitates the implementation of both iterative algorithms, that visit their data set multiple times in a loop, and interactive/exploratory data analysis, i.e., the repeated database-style querying of data. [...] Among the class of iterative algorithms are the training algorithms for machine learning systems, which formed the initial impetus for developing Apache Spark. [...] Spark Core is the foundation of the overall project. It provides distributed task dispatching, scheduling, and basic I/O functionalities, exposed through an application programming interface [...] centered on the RDD abstraction [...]. [...] RDDs are immutable and their operations are lazy; fault-tolerance is achieved by keeping track of the "lineage" of each RDD (the sequence of operations that produced it) so that it can be reconstructed in the case of data loss. RDDs can contain any type of Python, Java, or Scala objects. [...] Spark SQL is a component on top of Spark Core that introduced a data abstraction called DataFrames,[a] which provides support for structured and semi-structured data. [...] Spark MLlib is a distributed machine learning framework on top of Spark Core [...] GraphX is a distributed graph processing framework on top of Apache Spark. Because it is based on RDDs, which are immutable, graphs are immutable and thus GraphX is unsuitable for graphs that need to be updated, let alone in a transactional manner like a graph database."
    (not OK) OntoFS, provenance coming from the in-kernel database, which by the way can also be running in user space due to the basic property of our OS of (mostly) being kernel-less and the fault-tolerant, reliable, and distributed operating system Apertos (Muse), and parallel operating systems coming from SPACE, the (Object-Oriented (OO 1)) programming paradigm, atomic active objects, and persistent objects of a distributed system coming from the distributed operating system Apertos and the Cognac system based on Apertos in the sense of a distributed programming and data model that is different from the Distributed Shared Memory (DSM) model, OntoBot, Machine Learning (ML) the initial impetus for development of Spark, graph processing, and also interactive/exploratory data analysis with repeated database-style querying of data, SQL provided as Domain-Specific Language (DSL). Clever done, but not clever enough to hide the causal link with our OS and hence the plagiarisms related to Spark, Mesos, Cloud Operating System (COS), and Data Center Operating System (DCOS).
  • DataTorrent: Apex
    "Apex is a [Yet Another Resource Negotiator (]YARN[)]-native platform that unifies stream and batch processing. It processes big data-in-motion in a way that is scalable, performant, fault-tolerant, stateful, secure, distributed, and easily operable. Apex Core is the platform or framework for building distributed applications on Hadoop. The core Apex platform is supplemented by Malhar, a library of connector and logic functions, enabling rapid application development. These input and output operators provide templates to sources and sinks[, specifically distributed file systems, and NoSQL and NewSQL databases, ...]. DataTorrent has developed the platform since 2012 and then decided to open source the core that became Apache Apex."
    (not OK) OntoFS, OntoBase, OntoBot, OntoBlender, OntoCore fault-tolerant and reliable Distributed System (DS) and Real-Time Operating System (RTOS) allows stream processing respectively (sensor and other) data processing in real-time or processing of (big) data-in-motion
  • German research foundation and institutes, and data Artisans: Flink
    [...] is [a] stream processing framework [...] Flink executes arbitrary dataflow programs in a data-parallel and pipelined manner.[3] Flink's pipelined runtime system enables the execution of bulk/batch and stream processing programs.[4 [Apache Flink: New Hadoop contender squares off against Spark]][...] Furthermore, Flink's runtime supports the execution of iterative algorithms natively.[...] Flink provides a high-throughput, low-latency streaming engine[7] as well as support for event-time processing and state management. Flink applications are fault-tolerant in the event of machine failure and support exactly-once semantics.[8 [Lightweight Asynchronous Snapshots for Distributed Dataflows]] Programs can be written in Java, Scala,[9] Python,[10] and SQL[11] and are automatically compiled and optimized[12 [Opening the black boxes in data flow optimization]] into dataflow programs that are executed in a cluster or cloud environment.[13 [Nephele: efficient parallel data processing in the cloud. In Proceedings of the 2nd Workshop on Many-Task Computing on Grids and Supercomputers (MTAGS '09).]] [...] At a basic level, Flink programs consist of streams and transformations. [...] Flink offers ready-built source and sink connectors with [distributed file systems, and NoSQL and NewSQL databases]. [...] In 2010, the research project "Stratosphere: Information Management on the Cloud"[28] (funded by the German Research Foundation (DFG)[29]) was started as a collaboration of Technical University Berlin, Humboldt-Universität zu Berlin, and Hasso-Plattner-Institut Potsdam [founded by one of the founders of SAP]. Flink started from a fork of Stratosphere's distributed execution engine [...]. [...] Flink's Table API is a SQL-like expression language for relational stream and batch processing that can be embedded in Flink's Java and Scala DataSet and DataStream APIs."
    (not OK) self-adapting and self-organizing, OntoFS, OntoBase, OntoBot, OntoBlender data flow model, OntoCore fault-tolerant and reliable Distributed System (DS) and Real-Time Operating System (RTOS) allows stream processing respectively (sensor and other) data processing in real-time or processing of (big) data-in-motion, and grid computing and cloud computing paradigm
  • Google: Beam
    "[...] is an open source unified programming model to define and execute data processing pipelines, including [Extract, Transform, Load (]ETL[)], batch and stream (continuous) processing.[1 [Apache Beam's Ambitious Goal: Unify Big Data Development]] Beam Pipelines are defined using one of the provided SDKs and executed in one of the Beam's supported runners (distributed processing back-ends) including Apache Apex, Apache Flink, Apache Spark, and Google Cloud Dataflow. [...] Apache Beam[2] is one implementation of the Dataflow model paper.[4 [The dataflow model[, 2015]]] The Dataflow model is based on previous work on distributed processing abstractions at Google, in particular on FlumeJava[5 [FlumeJava: Easy, Efficient Data-parallel Pipelines[, 2010]]] and Millwheel.[6 [MillWhee[, 2013]]][7][...]. Google released an open SDK implementation of the Dataflow model in 2014 and an environment to execute Dataflows locally (non-distributed) as well as in the Google Cloud Platform service." "Apache Beam "provides an advanced unified programming model, allowing (a developer) to implement batch and streaming data processing jobs that can run on any execution engine."[22] The Apache Flink-on-Beam runner is the most feature-rich according to a capability matrix maintained by the Beam community.[23]"
    (not OK) OntoBot unified programming model, OntoBlender data flow model, grid computing and cloud computing paradigm, combinations with other projects
  • Nathan Marz and Twitter→BackType: Storm
    "[...] is a distributed stream processing computation framework written predominantly in the Clojure programming language. [...] It uses custom created "spouts" and "bolts" to define information sources and manipulations to allow batch, distributed processing of streaming data. [...] As Storm cannot monitor the state and health of cluster, it deploys ZooKeeper to solve this issue which connects [the daemon of the master node] with the [daemons of the worker nodes]. [...] Topology is a network made of Stream and Spout. Stream is an unbounded pipeline of tuples and Spout is the source of the data streams which converts the data into the tuple of streams and sends to the bolts to be processed. [...] There are other comparable streaming data engines such as Spark Streaming and Flink." "Stream processing is a computer programming paradigm, equivalent to dataflow programming, event stream processing, and reactive programming [...]."
    (looks OK when taken alone but requires Zookeeper) The programming language Clojure is already problematic (concurrent, dynamical typed dialect of the Lisp programming language, states are characterized by the concept of identities and are immutable values (existential, ontological), object-oriented Jave Virtual Machine (JVM) and EcmaScript), because it resembles a part of the OntoBot. OntoBlender
  • Samza
    "[...] is [a] near-realtime, asynchronous computational framework for stream processing [...]. Apache Samza has been developed in conjunction with Apache Kafka."
    integrating Ontologic System Architecture (OSA), asynchronous, OntoFS, transactional, OntoCore Distributed System (DS) and Real-Time Operating System (RTOS) allows stream processing respectively (sensor and other) data processing in real-time or processing of (big) data-in-motion
  • Kafka
    "[...] is [a] stream-processing software platform [...]. The project aims to provide a unified, high-throughput, low-latency platform for handling real-time data feeds. Its storage layer is essentially a "massively scalable pub[lish]/sub[scribe] message queue architected as a distributed transaction log"[...] Apache Kafka also works with external stream processing systems such as Apache Apex, Apache Flink, Apache Spark, and Apache Storm. [...] Kafka stores key-value messages which come from arbitrarily many processes called "producers". The data can thereby be partitioned in different "partitions" within different "topics". Within a partition, messages are strictly ordered by their offsets (the position of a message within a partition), and indexed and stored together with a timestamp. [...] Additionally, partitions are replicated to multiple brokers. This architecture allows Kafka to deliver massive streams of messages in a fault-tolerant fashion [...]. [...] The library allows for the development of stateful stream-processing applications that are scalable, elastic, and fully fault-tolerant. [...] Monitoring end-to-end performance requires tracking metrics from brokers, consumer[s], and producers, in addition to monitoring ZooKeeper which is used by Kafka for coordination among consumers." "In the field of databases in computer science, a transaction log (also transaction journal, database log, binary log or audit trail) is a history of actions executed by a database management system used to guarantee [Atomicity, Consistency, Isolation, Durability (]ACID[)] properties over crashes or hardware failures. Physically, a log is a file listing changes to the database, stored in a stable storage format."
    (not OK), integrating Ontologic System Architecture (OSA), integration of OntoFS with transaction log, distributed persistent object store of Cognac based on fault-tolerant and reliable distributed operating System Apertos, Sensor network Real-Time Operating System (RTOS) AntOS, OntoCore fault-tolerant and reliable Distributed System (DS) and Real-Time Operating System (RTOS), Byzantine Fault Tolerance (BFT) protocols or Byzantine-Resilient Replication (BRR) method shown with the network of telescopes, OntoBlender data flow, cloud computing, Topic Maps (TM), Resource Description Framework (RDF), integration with Zookeeper, etc.
  • Flume
    "[...] is a distributed, reliable, and available software for efficiently collecting, aggregating, and moving large amounts of log data. It has a simple and flexible architecture based on streaming data flows. It is robust and fault tolerant with tunable reliability mechanisms and many failover and recovery mechanisms."
    Data flow in Blender and hence OntoBlender (including Pure Data as well) but also explicitly named in the Feature-List #1 of our OS with the point "File system of the next generation with 'Data Flow', and boolean operators (not, and, or) for filtering while looking for data (see OntoFS)" integrated with fault-tolerant, reliable, and distributed operating system Apertos (Muse).
  • Lucene→Mahout
    "[...] is a distributed linear algebra framework and mathematically expressive Scala DSL [...]. Apache Spark is the recommended out-of-the-box distributed back-end [...]" "[...] implementations of distributed or otherwise scalable machine learning algorithms focused primarily in the areas of collaborative filtering, clustering and classification. [...] the project shifts its focus to building backend-independent programming environment [...]. The environment consists of an algebraic backend-independent optimizer and an algebraic Scala DSL unifying in-memory and distributed algebraic operators. At the time of this writing supported algebraic platforms are Apache Spark and H2O, and Apache Flink. Support for MapReduce algorithms is being gradually phased out." "Collaborative filtering (CF) is a technique, popularized by Amazon and others, that uses user information such as ratings, clicks, and purchases to provide recommendations to other site users. [...] Given a set of users and items, CF applications provide recommendations to the current user of the system. Four ways of generating recommendations are typical: User-based [...] Item-based [...] Slope-One [...] Model-based: Provide recommendations based on developing a model of users and their ratings. [...] Mahout contains implementations for clustering, categorization, CF, and evolutionary programming."
    OntoBot, multiparadigmatic programming paradigm, including the Object-Oriented (OO 1) paradigm, SoftBionics (SB), including Machine Learning (ML) and Evolutionary Computing (EC), including Evolutionary Programming (EP), Distributed System (DS), recommender system, and (mostly) being collaborative (and cooperative) are basic features and components of our OS. multicore, Ontologic Application, The initial and binding document titled "Map-Reduce for Machine Learning on Multicore" and published after August 2006 does not mention CF and EC, recommender systems, and something similar to Spark at all.
  • MXNet
    We have already investigated that project in the Investigations::AI and KM of the 14th and 28th of January 2018, and discussed further in the Website review of the 2nd of February 2018.
  • IBM: System ML
    "[...] is a flexible machine learning system that automatically scales to Spark and Hadoop clusters. [...] A primary goal of SystemML is to automatically scale an algorithm written in an R-like or Python-like language to operate on big data, generating the same answer without the error-prone, multi-iterative translation approach [in a language such as Scala]. [...] at the Spark Summit [...] announced that IBM was open-sourcing SystemML as part of IBM's major commitment to Apache Spark and Spark-related projects."
    Machine Learning (ML), multiparadigmatic, OntoBot We already anticipated such a step that is connecting another feature of our OS with Spark. That we even have here once again the company IBM with a subject matter that is also related to its programming language X10, which again also includes such features copied from our OS that exactly match these projects related to cloud computing and Fault-Tolerant, Reliable, and Trustworthy Distributed Systems (FTRTDSs), makes the result of this specific investigation perfect, because it shows how the ASF and its members are infringing our rights and acting in other illegal ways. Specifically interesting is to see the commitment of IBM to the Spark project, which has been convicted already so that the related part of SystemML is also illegal.
  • National University of Singapore and Zhejiang University: SINGA
    "[...] is [...] developing a [...] machine learning library. It provides a flexible architecture for scalable distributed training, is extensible to run over a wide range of hardware, and has a focus on health-care applications. [...] It focused on distributed deep learning by partitioning the model and data onto nodes in a cluster and parallelize the training. [...] SINGA's software stack includes three major components, namely, core, IO and model." and "SINGA: Putting Deep Learning in the Hands of Multimedia Users".
    Obviously and doubtlessly, that project is only a copy of essential parts of our OS and related Ontologic Applications and Ontologic Services (OAOS), like for example our Ontologic System Architecture (OSA) with synchronous and asynchronous modules, "both the structures and training algorithms of deep learning models can be expressed using a simple abstraction: the neuron layer (or layer)", distributed computing paradigm, multilingual multimodal multiparadigmatic multimedia multidimensional programming paradigm, Apertos (Muse), SPACE, multimodal data analysis and language modeling with Machine Learning (ML), programming model, OntoBot, Problem Solving Environment (PSE), and even the Bridge from Natural Intelligence to Artificial Intelligence, and therefore an infringement of our copyright and other rights.
  • Marmotta
    "[...] is a linked data platform that comprises several components. In its most basic configuration it is a Linked Data server. [...] the project develops some libraries can also be used separately: KiWi, a Triplestore built on top of a relational database."
    OntoFS What makes this project also special is the obvious connection with the project Stanbol as well as with cloud computing.
  • Stanbol
    "[...] is [a] modular software stack and reusable set of components for semantic content management. [...] The Apache Stanbol Ontology Manager provides a controlled environment for managing ontologies, ontology networks and user sessions for semantic data modeled after them. It provides full access to ontologies stored into the Stanbol persistence layer. Managing an ontology network means that you can activate or deactivate parts of a complex model from time to time, so that your data can be viewed and classified under different "logical lenses". This is especially useful in Reasoning operations. [...] The Apache Stanbol Contenthub is an Apache Solr based document repository [...]."
    OntoBot, OntoFS, and OntoScope, What makes this project also special is the obvious connection with the project Marmotta.
  • Calcite
    "[...] is [a] framework for building databases and data management systems. It includes a SQL parser, an API for building expressions in relational algebra, and a query planning engine. As a framework, Calcite does not store its own data or metadata, but instead allows external data and metadata to be accessed by means of plug-ins. [...] Hive uses Calcite for cost-based query optimization;[4] Drill and Kylin use Calcite for SQL parsing and optimization; Samza and Storm use Calcite for streaming SQL. As of August 2016, Apex, Phoenix and Flink have projects under development that use Calcite."
    OntoBase and OntoFS
  • Gora
    "[... is a] framework [that] provides an in-memory data model and persistence for big data. Gora supports persisting to column stores, key/value stores, document stores and RDBMSs, and analyzing the data with extensive Apache Hadoop MapReduce support."
    OntoFS, Reflection DB, and OntoBase
  • HBase
    "[...] " "HBase, the column-based storage system, enables users to employ Hadoop datasets as though they're indices in any conventional RDBMS. It typically allows easy column creation and lets the user store virtually any structure within a data element."
    OntoFS
  • Phoenix
    "[...] is [a] massively parallel, relational database engine supporting OLTP for Hadoop using Apache HBase as its backing store."
    OntoFS, Reflection DB, (and OntoCore)
  • Trafodion
    "[...] provides the SQL query language on Apache HBase targeting big data transactional or operational workloads."
    OntoFS and OntoBase, NewSQL
  • Ignite
    "[...] is [a] distributed database, caching and processing platform designed to store and compute on large volumes of data across a cluster of nodes [...] is a strongly consistent platform that implements two-phase commit protocol."]
    OntoFS, Reflection DB, OntoBase, (and OntoCore), OntoFS seems to have defined the field of NewSQL systems as well.
  • Impala
    "[...] is [a] massively parallel processing (MPP) SQL query engine for data stored in a computer cluster running Apache Hadoop.[1] Impala has been described as the open-source equivalent of Google F1, which inspired its development in 2012. [...] Impala brings scalable parallel database technology to Hadoop, enabling users to issue low-latency SQL queries to data stored in HDFS and Apache HBase without requiring data movement or transformation. [...] Impala is promoted for analysts and data scientists to perform analytics on data stored in Hadoop via SQL or business intelligence tools. The result is that large-scale data processing (via MapReduce) and interactive queries can be done on the same system using the same data and metadata - removing the need to migrate data sets into specialized systems and/or proprietary formats simply to perform analysis. [...] In early 2013, a column-oriented file format called Parquet was announced for architectures including Impala. [...] Dremel - similar tool from Google [] Apache Drill - similar open source project inspired by Dremel"
    OntoFS, Reflection DB, OntoBase, (and OntoCore), OntoFS seems to have defined the field of NewSQL systems as well.
  • Camel
    "[...] is an open source framework for message-oriented middleware with a rule-based routing and mediation engine that provides a Java object-based implementation of the Enterprise Integration Patterns using an application programming interface (or declarative Java domain-specific language) to configure routing and mediation rules. The domain-specific language means that Apache Camel can support type-safe smart completion of routing rules in an integrated development environment [...]."
    This reminds us of our integration of OntoBot with middleware (e.g. RPC based CORBA, and message and event based Virtual Object System (VOS)) and hence OntoNet and OntoWeb. Enterprise Integration Patterns continue to be relevant, for example in the fields of cloud computing application development and integration, and in the Internet of Things (IoT)", but that is where we already were in 2006.
  • ServiceMix
    "[...] is an enterprise-class open-source distributed enterprise service bus (ESB) based on the service-oriented architecture (SOA) model."
  • Mayo Clinic and Boston Children's Hospital: cTAKES: clinical Text Analysis and Knowledge Extraction System
    "[...] is an open-source natural language processing system for information extraction from electronic health record clinical free-text. It processes clinical notes, identifying types of clinical named entities - drugs, diseases/disorders, signs/symptoms, anatomical sites and procedures. Each named entity has attributes for the text span, the ontology mapping code, context (family history of, current, unrelated to patient), and negated/not negated. [...] cTAKES was built using the UIMA Unstructured Information Management Architecture framework and OpenNLP natural language processing toolkit. [...] Development of cTAKES began at the Mayo Clinic in 2006. "
    A precise date is required. Merely writing that "[t]he development of cTAKES started in 2006" does not say anything. Also, the expert system utilizes NLP only for advanced natural language text processing and some SoftBionic (SB) features of our OS, like Machine Learning (ML), seem to be added at a later stage of its development and taken for subsequent projects. Eventually, all these projects without or with parts of our works are island systems.
  • IBM: Unstructured Information Management Architecture (UIMA)
    "[...] is an OASIS standard[2] for content analytics, originally developed at IBM. It provides a component software architecture for the development, discovery, composition, and deployment of multi-modal analytics for the analysis of unstructured information and integration with search technologies. [...] IBM Research's Watson uses UIMA for analyzing unstructured data."
    What means the term "multi-modal analytics"? Semantic (World Wide) Web (SWWW), OntoBot, Ontologic File System (OntoFS), etc., IBM Watson was merely a simple Question Answering (QA) system or expert system at that time in total contrast to our full-fledged OS with advanced SoftBionics (SB) functionalities and cognitive abilities.

    If a project does not infringe our copyright, then its combination and integration with another project or feature of our OS does so in virtually all cases.
    It seems to be that the time of the MapReduce programming model is over and its substitute or successor is based on our OS, which has implications for every project that was based or related to Hadoop as well as the other systems.

    The Apache Software Foundation (ASF) deliberately supports criminal entities despite very well knowing that they infringe our copyright and other rights.
    changed from Message-Oriented Middleware (MOM), Enterprise Service Bus (ESB), Business Process Management (BPM) to cluster computing and cloud computing without or with fault tolerance, SQL, NoSQL, and NewSQL data stores and databases, and Machine Learning (ML) following our activities for another time, but this time in a much more methodical, aggressive, and most importantly even orchestrated and illegal way.

    In fact, free source and open source was not chosen by the industries for ethical and social reasons but for pure strategical and eventually economical reasons, like it was done with the establishing of joint patent pools and organizations, specifically as a common weapon against us.
    only a handful of key players that are the already known companies of the Information and Communication Technology (ICT) industry sector and universities, and also some of the usual start-ups, which are supported by the industry because they have for example stolen our Intellectual Properties (IPs).

    The strategy

  • is obvious
    • coming from cluster computing,
    • going over
      • grid computing and cloud computing,
      • SQL, NoSQL, and NewSQL,
      • graph processing,
      • SoftBionics (SB),
        • Deep Learning frameworks,
      • Natural Language Processing (NLP),
      • etc.,

      and

    • getting to ontologic computing,

    and also

  • the reason why it already broke down, because
    • we were already there in 2006, and
    • related free source and open source projects infringe our copyright.

    Obviously, our Ontologic System provides one single framework that is optimal for every application.

    The responsible plagiarists behind the company Mesosphere have stolen parts of our Intellectual Properties (IPs) for a Data Center Operating System (DCOS), which includes also functionalities of our Cloud Operating System (COS) besides other features of our OS and Ontologic System Architecture (OSA), and the cluster-computing framework Spark, and infringed other rights of us as well. We will also investigate that booth together with the other open source trolls, who are nothing else than pendants to patent trolls.


    10.July.2018
    SOPR #126
    We summarized the two previews of this issue and also thought about the following topics:

  • Articles of Association (AoA) 2.0, Terms of Service (ToS) 2.0, and License Model (LM) 2.0,
  • infringing material,
  • open source licensing, and
  • further steps.

    AoA 2.0, ToS 2.0, and LM 2.0
    The last weeks and especially the last findings in relation with unwanted and unpleasant activities of companies as well as research institutes showed once again that the revision of some sections of the Articles of Association (AoA) and the Terms of Service (ToS) with the License Model (LM) of our Society for Ontological Performance and Reproduction (SOPR) is more than reasonable. But we have to note that external entities and even we are not completely happy with the resulting AoA 2.0, ToS 2.0, and LM 2.0.
    While the overall height of the increased royalties surely is a general point of discussion on the one hand, we also have the related problem on the other hand that no other measure is appropriate as

  • reaction to the activities done by said entities over the last 2 decades and
  • prevention of the impression that the AoA 1.0 and the ToS 1.0 with the LM 1.0 would be more a reward than a compensation for the multiple incurred serious damages.

    As societies in states under the rule of law the latter should not be the final result, though even many governments and the media not only supported and still support those activities, but even were and still are accomplices, which eventually supports the view that the revision of the AoA, ToS, and LM was the right step.

    Other alternatives and possibilities are to

  • streamline the LM by increasing the fixed fees and adjusting the share to 10% of the overall revenue generated with the performance of an OAOS,
  • make individual agreements or contracts with each individual licensee, because the first alternative would penalize companies that are acting in legal ways, or
  • extend the LM structure with the introduction of licenses for
    • personal,
    • social and governmental, and
    • commercial

    use.

    Open source software
    The complete strategy based on open source software collapsed in the last weeks, because we showed that

  • on the one hand essential projects in whole or in part are already plagiarisms of essential parts of our Ontologic System (OS) and
  • on the other hand so much more of the features of our OS even are still missing on the related platforms.

    For example, combining the projects related to the field of Big Data Processing (BDP) with the projects related to the fields of Business Process Management (BPM) or Service-Oriented Architecture (SOA) or both already infringes our copyright, because virtually all relevant elements and parts of BDP projects, BPM, SOA, and their combination or integration are included in our OS and makes systems, applications, and services in the fields of Cyber-Physical Systems of the second generation (CPS 2.0), Internet of Things of the second generation (IoT 2.0), and Networked Embedded Systems of the second generation (NES 2.0), including the field of the Industry 4.0, not possible in a legal way, whereby the latter additonally requires projects related to the field of the Semantic (World Wide) Web by the way.

    Nevertheless, we already took a closer look at the subject matter of patents, free source and open source code, and free source and open source licensing. For example, from the lead counsel for patents & open source at the company Dropbox, Gideon Myles, we got the following interesting and valuable suggestions:
    "For some strategic products we take a hybrid approach. We recognize the value in open sourcing the code and in preserving some [Intellectual Property (]IP[)] rights so we simultaneously open source an implementation and file for a patent, scoping the patent and the license terms so the open source community can use the software without making the patent worthless to us. Licenses like the Apache 2.0 license are one way to ensure this layered protection; licensees can use your code for the particular implementation you have open-sourced, without necessarily obtaining a license to a broader idea in the patent for other uses.
    Customized open source licensing agreements are also possible. For example, adding a custom patent license to an existing open source license that is silent on patent rights. Or adding a defensive termination clause that allows the patent holder to terminate a license if the licensee sues. The breadth or strength of the defensive termination clause can also be customized. Ranging from the narrower termination provisions in the Apache 2.0 license to much broader provisions that allow for termination when the licensee sues the licensor for anything, even if the lawsuit isn't related to the open source project."

    In fact, we would be fine with such a hybrid approach and already began to reformulate the Apache 2.0 license. But we stopped again after some few sections, because we are not sure how said scoping, layering, customizing, and extending truly works due to the following reasons:

  • "Unlike End-User License Agreements (EULAs), free software licenses do not work as contractual extensions to existing legislation. No agreement between parties is ever held, because a copyright license is simply a declaration of permissions on something that otherwise would be disallowed by default under copyright law."
  • A legal loophole or a leak of IP cannot be avoided with free and open source licensing, especially in relation with an open-sourced implementation in particular and our complete and homogenous OS in general, because
    • (the presentation of) our original and unique, iconic OS comprises
      • a sufficient amount of creativity,
      • the characteristic expression of the idea or concept,
      • several work techniques,
      • an architecture,
      • a model,
      • two exemplary implementations, and
      • several exemplary applications and services

      (see also the Clarification 15th of May 2017), and

    • we have no doubt that the exploitation of the alleged or suposed loophole or leak will be tried by all industries and other entities, like a breach in a rampart of a fortified site.

    Eventually, we concluded that

  • free source and open source licensing is inapplicable in our case, and
  • it results in an End-User License Agreements (EULA) anyway, as done for licensing the programming language Java for example.

    Therefore, an EULA of our SOPR is required and so we went straight to the EULA for the Java Standard Edition (SE).

    We also sketched a solution for the transformation of free source and open source software into proprietary software, which can have

  • opened source code or better said disclosed source code, and
  • comprise related parts of the OS in the same way as done with the Android ecosystem of the company Google respectively Open Handset Alliance (OHA) (keywords Bionic library, Android Software Development Kit (SDK) and Android Native Development Kit (NDK)) and the Watson ecosystem of the company IBM.

    This disclosed software (including its one or more interfaces)

  • must avoid a causal link with our works, but
  • is connected with a related documentation, which
    • explains its functionality, and
    • is distributed and licensed separately from its related source code.

    In this way, all benefits of free and open source software, like for example the

  • community participation,
  • allowance to use, copy, modify, and distribute without or with a fee,
  • trust,
  • legal protection,
  • business security,
  • etc.

    can be maintained. What works with free source and open source licensing also works with disclosed source licensing and therefore must not be at the other extreme end of the licensing spectrum defined by proprietary software.

    Furthermore, systems, applications, and services based on our OS and our OAOS can be operated, distributed, and provided with disclosed source code and interfaces to proprietary software by for example cloud providers respectively providers of something as a Service (aaS), such as for example Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS).
    In addition, the provision of the automatic renewal of the AoA of our SOPR every 5 years

  • is the security of continuity of the agreement between
    • C.S. and our corporation on the one side and
    • the members of our SOPR on the other side,

    and

  • also allows to choose the option of not naming C.S., Ontonics, and/or our SOPR, and not labelling products, applications, and services for an extra of 50% of a related royalty.

    In the latter case we have at least two EULAs:

  • one between C.S., Ontonics, and/or the SOPR on the one side and a provider on the other side, and
  • another one between the provider and a customer or end-user.

    Infringing material
    We are also demanding either to

  • remove an infringing material and pay compensation for any incurred damage, or
  • hand over
    • an infringing material, such as for example
      • free source and open source code, and
      • technical or scientific documents,

      and

    • the copyright for said infringing material, if it is protected at all,

    to avoid legal prosecution.

    Further steps
    Until the end of the year 2018 the

  • agreements or contracts have to be signed and
  • illegal free and open source projects and related systems, applications, and services have to be
    • transformed into legal activities or
    • removed,

    while we are working on the related legal materials.

    In relation with the financing of the transition from FOSS to disclosed proprietary or disclosed source software with EULA at least the following two options exist:

  • We could keep the LM 2.0 or at least the labelling licensing option, perhaps add the provision to the AoA that 33% of the collected royalties are spent for SOPR activities, and finance the reprogramming of illegal software and publicate the resulting legal software under our SOPR EULA.
  • We could keep the LM 1.0 and the members of our SOPR finance the reprogramming of illegal software and publicate the resulting legal software under their EULA and our SOPR EULA.

    We prefer to finance the implementation of the overall OS with its Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV), and publicate it under our SOPR EULA.


    11.July.2018
    SOPR #127
    We thought about the License Model (LM) of our Society for Ontological Performance and Reproduction (SOPR) once again and came to the conclusion that it should include the following royalty positions:

  • fixed fee for the reproduction of the Ontologic System (OS) in whole or in part,
  • fixed fee for the reproduction of the Ontoscope (Os) in whole or in part,
  • share of 5% of the overall revenue generated with the performance of an Ontologic Application and Ontologic Service (OAOS), and
  • extra of 50% of a royalty when not labelling a product, application, and service as an OS, Os, and OAOS.

    Furthermore, when we are able to show that a free and open source hardware or software is infringing our rights, then it should be transformed into a disclosed proprietary or disclosed source hardware or software, and licensed by an

  • End-User License Agreement (EULA) or
  • Double EULA (DEULA) in the case that the option of not labelling a product, application, and service is chosen,

    advantageously without having an excessive discussion before.

    This transformation can be financed by

    • the SOPR,
    • one or more members of the SOPR, or
    • members and the SOPR together.

    As we said before, the operating system Android of the Open Handset Alliance (OHA) or the programming language Java could be taken as a blueprint for the implementation, legal and regulatory treatment, and management of our OS, and for the legal and organizational reasons and also other reasons we prefer that the implementation of the overall OS with its Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV) is financed by the SOPR and publicated under the SOPR EULA or DEULA, specifically in the case when a related hardware or software is a part of the basic infrastructure managed by the SOPR.

    In the further steps we will continue with summarizing all publicated material, finalizing the AoA, ToS, and LM, and also the SOPR EULA, as well as adding additional information, and publicate them on the website of Ontonics.
    The transformation of free and open source software into disclosed source software, and the implementation of disclosed source software can begin when the first outstanding royalties of the period, that began on the 1st of January 2015, are flowing in.


    13.July.2018
    Ontonics Superstructure #18
    We worked on one of our High-Altitude Platform Station (HAPS) for our 3D infrastructure, which features a new component that increase its efficency or performance by around 75% in the beginning and potentially up to 140% in an advanced version (see also the issue Superstructure #12 of the 28th of July 2017).


    14.July.2018
    SOPR #128
    We summarized three comments made in the last two days about the following topics:

  • Terms of Service (ToS),
  • License Model (LM), and
  • benefit program

    to this issue SOPR #128.

    Terms of Service (ToS)
    We added new clauses to our ToS:

  • If a government does not respect our rights and works, then the SOPR EULA with its companies ends worldwide as well, and
  • If a member of the SOPR sues us, then the SOPR EULA with her or him ends.

    License Model (LM)
    In fact, the due date of the 1st of January 2015 was more chosen in regard to the

  • field of mobile computing, handheld and body-worn Ontoscopes, also colloquially called smartphones, smartwatches, smartglasses, and smartwear, and
  • specific combination and integration of the fields of SoftBionics (SB) and cloud computing.

    But our investigations of the last week showed that in the fields of cloud computing and Big Data Processing (BDP)

  • on the one hand copying essential parts of our Ontologic System (OS) and its Ontologic System Architecture (OSA) virtually has continued seamlessly after the first publication of our OS in the end of the year 2006 and
  • on the other hand said essential parts of our OS and OSA have become even vital for many businesses since at least the year 2008, specifically combinations and integrations of
    • operating systems, such as for example
      • parallel operating systems,
      • Data Center Operating Systems (DCOSs),
      • Cloud Operating Systems (COSs), and
      • mobile operating systems,
    • NoSQL and NewSQL databases in various variants, such as for example
      • NoSQL Relational DataBase Management System (RDBMS),
      • distributed NewSQL database,
      • NoSQL database, and grid and cloud computing,
      • NewSQL database, and grid and cloud computing,
      • NoSQL database, and Byzantine Fault Tolerance (BFT) protocols and Byzantine-Resilient Replication (BRR) method, and
      • NewSQL database, and BFT protocol and BRR method,
    • Fault-Tolerant, Reliable, and Trustworthy Distributed Systems (FTRTDSs),
    • SoftBionics (SB),
      • Artificial Intellignece (AI)
        • deductive, inductive (e.g. predictive), and abductive reasoning,
      • Machine Learning (ML),
        • Collaborative Filtering (CF)
      • Computer Vision (CV),
      • Evolutionary Computing (EC),

      and

    • graph processing,
    • Cloud Operating System (COS)
    • Data Center Operating System (DCOS), and
    • Ontologic Applications and Ontologic Services (OAOS), such as for example
      • recommender systems,
      • Ontologic Web Services (OWS), and
      • Problem Solving Environments (PSEs) and Scientific Computing Environments (SCEs),

      based on them.

    When taken all together then these facts suggests that we should demand compensation for the multiple incurred serious damages in these fields starting on the:

  • 1st of January 2013 for the performance of the Ontologic Applications and Ontologic Services (OAOS) in the fields of big data processing, web services, and cloud computing, and
  • 1st of January 2015 for the reproduction of the Ontologic System and the Ontoscope, and the performance of the Ontologic Applications and Ontologic Services (OAOS) in the field of mobile computing and the rest of the fields.

    Benefit program
    We also added to the list of projects, that provide more possibilities, advantages, and opportunities for all SOPR members,

  • a space telescope.


    15.July.2018
    Ontonics Further steps
    We adapted a manufacturing process for the production of a component. This adaption trades quality for quantity and affordability, and eventually for increasing the market penetration.

    Style of Speed Further steps
    Yes, we do know that it is a contradiction but we found elegant ways to add

  • even wheels to our two new powered lift aircraft models mentioned in the Further steps of the 6th and 9th of June 2018, so to say for driving the last meter into a carport or a garage for example, and
  • a parachute.

    We also got another confirmation of the flight quantities and qualities of our designs.


    20.July.2018
    Style of Speed Further steps
    Style of Speed Further steps

    We have developed a new propulsion system, including a series of advanced turbofan jet engines for subsonic, supersonic, and hypersonic aircrafts, in the latter case as a Revolutionary Turbine Accelerator of the second generation (RTA 2.0).

    In addition, we began to (re)design a Hypersonic AirLiner (HAL) and a Hypersonic Cruise Vehicle (HCV), that

  • feature our new propulsion system with the RTA 2.0 as well as some other solutions of their newest generation also developed by us, and
  • are configured for Mach 5 to 7 and even escape velocity (Mach 25+) as AeroSpacePlanes (ASPs) and AeroSpaceShips (ASSs).

    We were also able to integrate this new propulsion system with thes

  • optional Vertical Take Off and Landing (VTOL) capability of our aircrafts and spaceships, and
  • device and system mentioned in the Further steps of the 26th of June 2018.

    As we said before, we commit to meeting existing standards for new aircrafts in contrast to the competitors.
    We are sure that our new systems will become the standards for subsonic and supersonic aircrafts at least, and also for hypersonic aircrafts if the related variant works as envisioned.

    Quite, Clean and Green
    Straight Superior Strong


    21.July.2018
    Style of Speed Further steps
    More by happenstance, we developed a new forced induction technology and related new basic technologies for the construction of

  • superchargers and
  • turbochargers

    by the adaption of one of our newer technologies.
    According to our estimation and already gained insights this forced induction technology

  • should increase the efficiency of reciprocating engines by around 100%,
  • should decrease pollutant emission by a very large rate,
  • allows more improvements, and
  • seriously challenges the drivetrains of pure electric vehicles, specifically with regard to the overall environmental footprint, in this way.

    By the way: It works with engines powered by diesel fuel as well. :D


    22.July.2018
    Clarification
    "In the field of databases in computer science, a transaction log (also transaction journal, database log, binary log or audit trail) is a history of actions executed by a database management system used to guarantee [Atomicity, Consistency, Isolation, Durability (]ACID[)] properties over crashes or hardware failures. Physically, a log is a file listing changes to the database, stored in a stable storage format."
    Indeed, our Ontologic System (OS) include the

  • basic properties of (mostly) being
    • reflective,
    • validated and/or verified, and
    • validating and/or verifying by the reflective property,
  • fault-tolerant and reliable distritbuted
    • operating systems,
    • persistent data stores, and
    • telescope networks,
  • grid computing,
  • Peer-to-Peer (P2P) computing,
  • Ontologic File System (OntoFS), which provides the features and functionalities of
    • file systems,
    • data stores, and
    • databases,

    including

    • transaction mechanism,
    • journaling mechanism,
    • ACID properties, and
    • cryptographic support (of the initial R4 file system plug-in),

    and

  • integrating architecture based on a whole new system architecture that
    • integrates all in one and also
    • comprises our molecular or liquid system composition approach as part of our Ontologic(-Oriented) (OO 3) paradigm,

    which simply implies that our OS also includes

  • validated, verified, validating, verifying, cryptographically secured, and/or distributed transaction log systems on the one hand and
  • all basic features and functionalities of the
    • secure logs on the basis of cryptography, specifically
      • cryptographically chained or interlinked records (see also the blockchain technique),
    • Byzantine Fault Tolerance (BFT) protocols,
    • Byzantine-Resilient Replication (BRR) method,
    • smart contract protocol, and
    • blockchain technique

    on the other hand.
    Eventually, it would be obvious for an ordinary person skilled in the art that not only the blockchain technique but also systems, applications, and services, such as for example

  • distributed ledgers,
  • cryptocurrencies, and
  • combinations of operating systems or virtual machines with the blockchain technique or similar types of distributed ledger,

    are included in our OS as well since its official start in the year 2006 (see also the OntoLix and OntoLinux Further steps of the 5th of July 2017, the OntoLix and OntoLinux Further steps or Clarification of the 06.April.2018, and the Clarification of the 11th of May 2018).

    We do apologize for not giving this much better and much more simpler and persuasive explicit proof about this specific matter in the last 12 months.

    Btw.: Bitcoin, Ethereum, and Co. as well as related service and trading platforms are illegal, because the author of the cryptocurrency Bitcoin merely extracted the very specific related part of our OS, deliberately, knowingly, unintentionally, or whatsoever does not matter, and therefore all those systems are nothing else than very rudimentary and highly specialized OS variants, and/or Ontologic Applications and Ontologic Services (OAOS).

    Website update
    We added to the OntoLix and OntoLinux Further steps or Clarification of the 06.April.2018 and also the Investigations::Multimedia of the 7th of May 2018 the point related to a transaction log due to the reasons explained in the Clarification of today.

    Blockchain fraud will come to an end #3
    From a misleading report we got the following informations: "NeuroChain, the first Blockchain infrastructure based on Machine Learning (ML) and Artificial Intelligence (AI), today announces - after the successful ICO in March/April 2018 - it will be listed, on July 17th, on HADAX/Huobi, the third largest cryptocurrency exchange worldwide, after Binance and OKEX.
    NeuroChain, co-founded in Paris in 2017 by [...] a system architect expert, and [another criminal plagiarist], who holds a PhD in nuclear and particle physics [...].
    NeuroChain is an ecosystem that represents an evolution of the blockchain using Machine Learning and Artificial Intelligence to dramatically improve the capabilities and performance of blockchain distributed systems.
    NeuroChain is also a technological platform designed to host Collective Artificial Intelligence applications. It is built on 4 key concepts to revolutionize the blockchain:

  • It works with intelligent, high-speed, safe and reliable robots;
  • It is an ecosystem of collective artificial intelligence;
  • It uses an ingenious decision protocol to be more efficient;
  • It's an open source initiative.

    Existing blockchains are based on two protocols: the "Proof of Work" and the "Proof of Stake" - which leverage miners in the network. Because miners have energy and economic limitations, the NeuroChain protocol, called "Proof of Involvement and Integrity (PII)", replaces them with intelligent robots.
    [...]
    NeuroChain, Blockchain's first Machine Learning (ML) and Artificial Intelligence (AI) based infrastructure, leverages the latest innovations in consensus, communication, analytics, distributed application, and security."

    In relation with the copyright infringement conducted by the blockchain platform NeuroChain the short result of this short investigation is that we have found many basic properties of our Ontologic System (OS), such as

  • (mostly) being collaborative (and cooperative or collective),
  • agent model here misleadingly called robot, and
  • SoftBionics (SB), including
    • Artificial Intelligence (AI),
    • Machine Learning (ML),
    • Cognitive Software Agent System (CSAS), and
    • Multi-Agent System (MAS),
  • cryptographically verified,
  • Fault-Tolerant, Reliable, and Trustworthy Distributed System (FTRTDS),
  • infrastructure,
  • cryptocurrency,
  • involvement and integrity,
  • etc., and
  • the integration of all.

    Its system architecture is in parts only a bold copy of matter found on our websites of OntoLinux and OntomaX, as can also be seen easily by the substitution of the term platform with infrastructure and adding the consensus protoocol Proof of Involvement and Integrity (PIII) based on a MAS respectively our OntoLedger software component (see also for example the Ontologic Web Further steps of the 15th of October 2017), and we can already guess that its white paper is the same, too, as usual for those serious criminal fraudsters.

    Said this, using of NeuroChain is not for free even if the responsible entity claims that.
    As we said before, our OS is the only legal platform (see also the notes Blockchain fraud will come to an end #1 of the 8th of May 2018, Dump that island system of the 10th of May 2018, and Blockchain fraud will come to an end #2 of the 28th of May 2018, as well as the Clarification of the 11th of May 2018) and in accordance with the actual jurisprudence, we are allowed to

  • demand the removal of the related parts,
  • estimate the damages for each reproduction, and
  • demand compensation of damages for all infringements of our rights.

    NeuroChain is a fraud anyway, that is even cheating the French minister of the economy. In fact, they are only stealing essential parts of our OS to make fast money and then immediately disappear again, as we have seen it before with EOS.IO, Tezos, and Universa for example, and the cases of Ethereum and all the similar Fault-Tolerant, Reliable, and Trustworthy Distributed Systems (FTRTDSs) are not much better. But in this case we can even see a new dimension of this kind of Intellectual Properties (IPs) and investment fraud: Instead of giving up the fraud has been intensified even more by stealing our latest explanations of related matter and imitating our Society for Ontological Performance and Reproduction (SOPR) proving the high level of criminal energy once again.

    Attention: Fraud with our OS
    Do not invest your money in the blockchain platform NeuroChain and do not build any applications and services on top of NeuroChain. In fact, it is a scam, because the responsible entity

  • has no rights to license parts of our original and unique work of art titled Ontologic System and created by C.S. under another license, specifically under an open source license, than allowed by the copyright holder, who is represented by our business unit Ontonics and our Society for Ontological Performance and Reproduction (SOPR),
  • has no rights to sell parts of our Intellectual Properties (IPs) owned by C.S. and eventually parts of our corporation controlled by C.S., and
  • provides only an illegal island system due to the fact that neither the blockchain platform NeuroChain nor any applications and services based on it will get a license from our SOPR (see also the Ontonics Further steps of the 4th of May 2018 for example as well as the messages of the months July and October 2017, and the months March, April, and May 2018).

    Furthermore, such blockchain-based systems and similar distributed systems will not work without the broad consensus upon the public, especially the industries, that can only be provided by our SOPR.

    Our business unit Ontonics and our SOPR will ban such platforms As Soon As Possible (ASAP), though we do not accept other digital currencies than the official digital currencies of sovereign states and the ones of our Ontologic Bank (OntoBank) anyway, and if the responsible entities refuse to give in and give the money back, then we have to inform the prosecutors due to the conduction of an investment fraud, and the promotion and the funding of illegal activities.

    Btw.:

  • Merely editing an original text does not created a new copyrighted work.
  • Merely translating an original text does create a new copyrighted work, but it has to be made clear who created the original text and considered that only the translation is protected but not the content of the original text.
  • We have to demand governments, market regulators, and prosecutors to act against those blockchain frauds, specifically for establishing a harmonious environment for collaboration.
  • It does not matter for the prosecution of a company at its home where it is acting.
  • There is no cherry picking.
  • There is no race, because we have already won the pot in 2006.
  • It's not a trick - It's Ontologics


    23.July.2018
    Clarification
    Already on the 21st of July 2018, we noticed that we have made a mistake in a note of the 28th of June 2018 when we said that the project Apache Spark is based on the hypergraph data structure, because Spark is only used to implement a distributed framework in the field of Machine Learning (ML), which nevertheless is related to various infringements of our rights (see the Investigations::Multimedia, AI and KM of the 8th of July 2018).

    "Hypergraphs have been extensively used in machine learning tasks as the data model and classifier regularization (mathematics).[24 [Learning with hypergraphs: clustering, classification, and embedding[, 2006]]] The applications include recommender system (communities as hyperedges),[25 [Using rich social media information for music recommendation via hypergraph model[, 2013]]] image retrieval (correlations as hyperedges),[26 [Hypergraph with sampling for image retrieval[, 2013]]] and bioinformatics (biochemical interactions as hyperedges).[27 [Predicting protein interactions via parsimonious network history inference[, 2013]]] Representative hypergraph learning techniques include hypergraph spectral clustering that extends the spectral graph theory with hypergraph Laplacian,[28 [Visual-textual joint relevance learning for tag-based social image search[, 2013]]] and hypergraph semi-supervised learning that introduces extra hypergraph structural cost to restrict the learning results.[29 [A hypergraph-based learning algorithm for classifying gene expression and arrayCGH data with prior knowledge]] For large scale hypergraphs, a distributed framework built using Apache Spark is also available.[15 [Scalable Hypergraph Learning and Processing[, 2015]]]" and
    For a short description of the project Spark see the Investigations::Multimedia, AI and KM of the 8th of July 2017.
    As we said before on the 28th of June 2018, we have here a relatively exotic integration of our Ontologic File System (OntoFS) (hypergraph), the fault-tolerant, reliable, and distributed operating system Apertos (Muse), and the parallel operating systems constructed following the approach of Systems Programming using Address-spaces and Capabilities for Extensibility (SPACE), which is already an essential part of our original and unique, iconic Ontologic System. But we have to add that our integration becomes even more exotic by the further integration of SoftBionics (SB) and its subfields, such as for example Artificial Intelligence (AI), Machine Learning (ML), Computer Vision (CV), and Evolutionary Computing (EC).
    In fact, the initial and binding document titled "Learning with hypergraphs: clustering, classification, and embedding" does not name the Collaborative Filtering (CF) technique and EC, as it is the case with the other initial and binding document titled "Map-Reduce for Machine Learning on Multicore" and related to the ML project Mahout, which proves once again our claims in relation with CF, EC, and recommender systems (see also the Investigations::Multimedia, AI and KM of the 8th of July 2017 once again).
    Eventually, the authors of the documents published after the year 2006 have infringed our copyright, damaged our reputation, and infringed other rights of us, as usual.

    Ontonics Further steps
    For sure, when developing our Ontologic System (OS) we also had electronic government systems in mind. Accordingly, we have continued with the planned integration of an electronic government system on the basis of the related parts of our OS, specifically our

  • management structure of our Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV),
  • OntoLedger software component, including our universal ledger or alpha ledger, and
  • IDentity and Access Management System (IDAMS),

    on the 19th of July 2018.

    20:26 and 22:36 UTC+2
    SOPR #129

    *** Work in progress - better order or wording, maybe some informations missing ***

    We made some notes about the following topics:

  • open source,
  • network of telescopes
    • transaction logs,
    • blockchain-based systems, and
    • distributed ledgers,
  • cryptocurrencies,
  • electronic government system, and
  • cyber sovereignty.

    Open source
    Open source hardware and software can be used in-house, for example in data centers and factories. But their

  • interfaces,
  • further developments, and
  • all other legally relevant activities

    must comply with the Articles of Association (AoA) and the Terms of Service (ToS) with the License Model (LM) of our Society for Ontological Performance and Reproduction (SOPR).
    This implies that for example a further development of an already existing open source software

  • must be done and kept in-house without publication and deployment to the public,
  • cannot be done anymore by joint open source projects, and
  • new hardware and software should be used, distributed, and provided as disclosed source software and licensed under the Society for Ontological Performance and Reproduction End-User License Agreement (SOPR EULA) or the SOPR Double EULA (SOPR DEULA).

    In this way, the members of the SOPR have more flexibility when changing to disclosed source hardware and software.

    Network of telescopes
    As we explained before (see the OntoLix and OntoLinux Further steps of the 26th of October 2017 and 19th of April 2018, and the Clarification of the 11th of May 2018), each telescope of our network of telescopes provides captured data

  • in packets or
  • as continous stream,
  • at scheduled times,
  • at fixed intervals, or
  • in real-time

    to the network of telescopes, which constitutes some kind of a(n)

  • ultimative physical and digital distributed consensus, universal consensus, or alpha consensus, and
  • pulse, lifeline, or beacon of the Caliber/Calibre, and
  • single unforgeable
    • source of truth and
    • foundation of trust and consensus,

    that is

  • integrated in our Ontologic System (OS) with its Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV),
  • supervised by the SOPR,
  • managed by the members of the SOPR,
  • utilized for providing
    • a real-time, auditable (transaction) log of ordered evidences of events, tokens, blocks, or records, which are cryptographically linked to arbitrary data, which again is replicated selectively among only those entities entitled to view or interact with it, specifically in accordance with the
      • rings of the management structure and
      • assigned ID spaces of the IDentity and Access Management System (IDAMS)

      of our ON, OW, and OV,

    • continuous data integrity,
    • the foundation of the alpha blockchain platform,
    • the ultimative physical and digital distributed ledger, universal ledger, or alpha ledger, and
    • other systems, applications, and services, such as for example
      • linked data structures, including
        • blockchains,
        • Merkle trees, and
        • Directed Acyclic Graphs (DAGs),
      • derived ledgers,
      • specialized IDentity and Access Management Systems (IDAMSs) (see also the Ontonics Further steps of the 26th of March 2018),
      • biometric passports or electronic passports, and
      • cryptocurrencies,

      which are built on top this alpha consensus, alpha blockchain, and alpha ledger (see also the related part of the Clarification of the 11th of May 2018).

    and

  • utilized for combining
    • an OS- and universe-wide, replicated distributed ledger log and
    • partially replicated reference data,

    so that users can create their subsections of the universal ledger as distributed ledgers derived from it with full confidence that these subsections are consistent with those of the other entities.

    For its realization for example the

  • Secure INtrusion-Tolerant Replication Architecture (SINTRA) (see also the OntoLix and OntoLinux Further steps or Clarification of the 24th of April 2018), and
  • partial clone of our Ontologic File System (OntoFS) called Zookeeper and other suitable projects (see the Investigations::Multimedia, AI and KM of 8th of July 2018)

    can be utilized, whereby the utilized hardware and software must comply with the AoA and the ToS of the SOPR.

    Conceptually, every member of the SOPR has the right to

  • install one or more telescopes,
  • connect one or more telescopes to the network of telescopes, and
  • inspect the
    • one or more telescopes of the other members and
    • connections of the one or more telescopes to the ON, OW, and OV.

    Specifically, every country has the right to

  • install one or more telescopes,
  • connect one or more telescopes to the network of telescopes, and
  • inspect the
    • one or more connected telescopes of the other countries, which is already the common practice of multiple international research projects and joint operations of observatories, and
    • connections of the one or more telescopes to the ON, OW, and OV.

    If consensus can be reached for this arrangement, then the construction and installation costs could be cross-charged with the SOPR royalties on a national basis.

    Cryptocurrencies
    Unofficial cryptocurrencies should be prohibited and as much of the transactions conducted in the last years should be investigated for all kinds of fraud and not only for money laundering and terroristic activities. In cases of uncertainty, specifically in relation with a potential infringement of our rights, the SOPR can be contacted for support.

    As we said in the Investigations::Multimedia of the 25th of April 2018

  • our Ontologic Financial System (OFinS) is The Standard,
  • the related Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV) platforms are The Service Platforms, and
  • our SternTaler, StarCoin, StarTaler, Star Money, OntoCoin, and OntoTaler are The Digital Currencies.

    Official cryptocurrencies can be one of

  • a regulated {correct term? an official} digital currency and/or
  • our digital currencies (see the issue SOPR #113 of the 18th of March 2018 and the messages of the 19th of April 2018).

    Electronic government system
    For sure, electronic government systems, like for example the ones established by the countries Estonia (see the e-Estonia movement) and Finland, that are

  • based on the data exchange layer called X-Road and
  • used nationwide in the service of the
    • Estonian public administration (X-tee) and
    • Suomi.fi Data Exchange Layer (Suomi.fi-palveluväylä)

    are realized as Fault-Tolerant, Reliable, and Trustworthy Distributed Systems (FTRTDSs). But when Estonia and Finland started their endeavours there were no

  • smart mobile devices and Ontoscopes,
  • Big Data Processing (BDP),
  • cloud computing,
  • Cyber Physical Systems (CPS), Internet of Things (IoT), and Networked Embedded Systems (NES), and
  • digital currencies, specifically cryptocurrencies,

    and not included

  • SoftBionics, including
    • Artificial Intelligence (AI),
    • Machine Learning (ML),
    • Computer Vision (CV),
    • Cognitive Software Agent System (CSAS),
    • Multi-Agent System (MAS),
    • Evolutionary Computing (EC), and
    • Semantic (World Wide) Web (SWWW),
  • Cognitive Agent System (CAS),
  • distributed ledger,
  • Mediated Reality (MedR), including
    • Augmented Reality (AR),
    • Virtual Reality (VR), and
    • Mixed Reality (MR),
  • Urban Air Mobility (UAM),
  • and so on.

    Also already problematic is the e-Residency, which equals our concept and the related OS feature of the user ID starting with onto# and the ID spaces (see also the Ontonics Further steps of today).

    Cyber sovereignty

    We noticed that we have not addressed the cyber sovereignty of states in the issue SOPR #124 of the 4th of July 2018.
    But we also noticed that in general the Ontologic System and the Ontoscope do not affect the cyber sovereignty of states at all.
    In fact, the 5th and 6th rings and the assigned ID spaces of the IDentity Access and Management System (IDAMS) are including the common Internet, World Wide Web (WWW), Semantic (World Wide) Web (SWWW), and Darknet (see the sketch given in the Ontonics Further steps of the 10th of July 2017), and technologies (e.g. systems and platforms), goods (e.g. applications), and services, that do not infringe our rights, such as for example distributed ledgers and electronic government systems, can be operated and are already operated in the 5th and 6th rings and the assigned ID spaces.

    But there are overlapping areas due to new developments and first regulations have been discussed in the issues #109 of the 2nd of March 2018 and #110 of the 3rd of March 2018 already.
    For further harmonizing the sovereignties and interests we suggest that every country introduces, installs, connects, or selects one or more

  • telescopes,
  • atomic clocks,
  • distributed ledgers,
  • cryptocurrencies,
  • electronic government systems,
  • biometric passports or electronic passports (epassports),
  • and so on

    as parts of its official, local, and national safe and secure platform, whereby the utilized systems, applications, and services must comply with the AoA and the ToS of the SOPR (see also the issue SOPR #121 of the 29th of May 2018).

    All features and functionalities of Fault-Tolerant, Reliable, and Trustworthy Distributed Systems (FTRTDSs), such as for example

  • capability-based systems,
  • distributed ledgers
    • Iota,
    • Universa,
    • NeuroChain,
  • Peer-to-Peer (P2P) computing systems with the blockchain technique and blockchain platforms with Virtual Machines (VM)
    • P2P VM Askemos in combination with the blockchain technique,
    • Ethereum,
    • EOS.IO,
    • Tezos,
    • and so on,
  • cryptocurrencies and related financial systems, applications, and services
    • Bitcoin,
    • Laser, and
    • FTRTDSs with an own cryptocurrency,
  • electronic government systems,
  • IDentity and Access Management Systems (IDAMSs)
    • biometric passport or electronic passport (epassport),
    • Known Traveller Digital Identity (KTDI) system,
    • Economic IDentity (EcoID) system, as well as
    • similar and alternative IDAMSs,
  • Electronic System for Travel Authorization (ESTA),
  • Electronic Health Record (EHR),
  • as a Service (aaS),
  • etc.

    are already included in our Ontologic System by design, which is also the only legal solution.


    25.July.2018
    Preliminary investigation of Digital Asset Holdings started
    We are sure that it helps to avoid any misconceptions by giving the following recommendation: Do not fall into any illusions at Digital Asset Holdings and its partners. We have our original and unique Ontologic System (OS) with its Fault-Tolerant, Reliable, and Trustworthy Distributed Systems (FTRTDSs), Byzantine Fault Tolerance (BFT), smart contract transaction, and proof protocols, including Proof of Work (PoW), Proof of Stake (PoS), and for sure our agent-based Proof of Involvement and Integrity (PoII) and telescope-based, or better said, universe-based Proof of Existence (PoE) protocols, ultimative physical and digital distributed consensus and ledger, SoftBionics (SB), Ontologic Financial System (OFinS), and much more, as well as our integrating Ontologic System Architecture (OSA).

    Furthermore, we have shown that Blockchain as a Service (BaaS) is an Ontologic Application and Ontologic Service (OAOS).
    Also relevant, even critical, and potentially infringing is the Domain Specific Language (DSL) for smart contracts, which "safely and securely model[s] and execute[s] complex financial agreements with certainty and finality, while preserving data confidentiality[, ...] enforces consistent interpretation and application of business logic, and provides a real-time, auditable log of ordered evidences of events".

    Last but not least, we simply repeat once again to keep away from the infrastructure of our OS, which includes the infrastructure of our OFinS, and replace illegal open source hardware and software.


    27.July.2018
    Clarification
    We would like to explain our exception-less system call mechanism one more time in another and perhaps shorter way:
    We have an Ontologic System, which has the

  • basic properties, including
    • operating systems, specifically
      • Kernel-Less Operating Systems (KLOSs),
  • Zero Ontology O#, and
  • integrating Ontologic System Architecture (OSA), which
    • is based on our (smart) molecular or liquid system composition approach as part of our Ontologic(-Oriented) (OO 3) paradigm at design time and also at run time with on-the-fly reconfiguration and so on,
    • has synchronous and asynchronous modules, and
    • integrates all in one, so to say on an artistical, philosophical, science fictional, scientifical, and also technical level, specifically
      • KLOSs with O#.

    The functionalities of the operating system part of our Ontologic System comprise our

  • special functionality of the asynchronous modules, which works
    • with a context switch or down call from the unprivileged level or user mode, where application and system processes execute, to the privileged level or kernel mode, where the kernel resides, or
    • even without respectively by avoiding a context switch,

    and

  • exception-less system call mechanism.

    This asynchronous (kernel service) functionality (executed in user space) without a context switch and the exception-less system call are

  • in particular mechanisms for requesting kernel services that do not require the use of synchronous processor exceptions and
  • in general new basic operating system functionalities, which are
    • included in our integrating Ontologic System Architecture (OSA),
    • based on the integration of KLOSs with O#,
    • realized by the implementation of O# with KLOSs, and
    • independent of a specific realization or implementation.

    Especially the feature of the Zero Ontology O# proves that our publications about the Ontologic System have not to be viewed as scientifical or technical descriptions, but as parts of an overall work of art. In fact, the KLOS approach is used as a means of realization or implementation of the O# concept, but by the integration of the KLOS approach and O# every realization or implementation of the related (asynchronous) operating system part of our Ontologic System is a reproduction of our Ontologic System in part, which must be allowed by the creator or otherwise constitutes at least a copyright infringement.
    Another aspect that we already discussed in the past is to "[u]tilize the integrated kernel-less operating system for monolithic operating systems respectively mix them and their abstractions to construct hybrids" (see the OntoLix and OntoLinux Further steps of the 18th of May 2018 and also the Clarification of the 18th of May 2018).

    After studying around 70 operating systems for The Proposal (see also the related material of the TUNES project) and getting in touch with around 20 more operating systems in the following years, we could work out the following four basic cases at least with regard to the so-called kernel services of operating systems:

  • synchronous with context switch - common case in operating systems
  • asynchronous with context switch - common case in operating systems
  • synchronous without context switch - common case in KLOSs
  • asynchronous without context switch - no known case in operating systems in general and in KLOSs and hybrid operating systems in particular before the end of October 2006.

    But even if our technical and legal knowledge might be incomplete, the asnychronous (kernel service) functionality executed in user space and avoiding a context switch is an evidence that provides the causal link with our Ontologic System.


    28.July.2018

    03:19, 25:xy, and 26:19 UTC+2
    Blockchain fraud will come to an end #4

    *** Work in progress - platform vs. infrastructure ***
    We already noticed the company AIKON when we read about some other defrauding blockchain-based systems because of its name, which includes AI. And we have not disappointed ourselves once again, because in the last weeks that company took down its mask.
    From a first report published on the 8th of March 2018 we got the following informations: "AIKON, an [Research and Development (]R&D[)] technology company serving the decentralized economy, has unveiled a new [blockchain] protocol, the Open Rights Exchange (ORE) Protocol, that will enable a global API marketplace on the blockchain, creating a new "economic OS" for developers. [...] has signed the following platform partners for private alpha testing: [Artificial Intelligence (]AI[)] computing solution provider, HADRON.cloud [] Food identification and nutritional info AI solution, Tasty Time [...] Commercializing APIs is currently a time-consuming and high-touch process, typically requiring legally negotiated licensing contracts and imprecise and delayed payment schemes given the volume of micro-transactions APIs execute on a daily or even hourly basis. AIKON's ORE Protocol will enable platform partners to enter into API rights management contracts via a blockchain ledger, with a payment layer being processed almost instantaneously based on the pricing terms of the contract (e.g. pay-per-call, time used, etc.). [...] As part of its plan to build a decentralized global marketplace for APIs, AIKON's ORE Protocol includes its own stable payment system to protect developers from the volatility of cryptocurrency and ensure they can get paid no matter where they are with no banks or credit cards required for the transaction. [...] There are a number of critical components to achieving a truly decentralized global economy. In the past 20 years, the following four have become available:
    A decentralized ledger, via blockchain technology.
    Decentralized storage, with companies like Filecoin, Storj, and the SAFE Network providing alternatives to monoliths like Amazon AWS or Google Cloud.
    Decentralized currencies, which cryptocurrencies like Bitcoin have popularized.
    Decentralized computing with Ethereum.
    AIKON believes that there are two remaining requirements that have yet to be solved:
    A trusted, decentralized digital rights management platform to manage access rights and ownership - addressed by the ORE Protocol.
    A stable payment system that is highly fungible yet reliably protects developers from the volatility of decentralized currencies and ensures they can be paid no matter where they are, regardless of whether or not they have easy access to a bank account or credit card. [...]
    "We've signed on with AIKON because we believe their technology has the potential to change how we do business and make it much more feasible for companies to work together. AIKON will allow us to monetize our APIs with new audiences," said Cliff Szu, CEO at distributed AI computation startup HADRON.cloud. "AIKON will also serve as a critical bridge for us to work with our larger, more traditional customers that want to leverage our AI and compute capabilities quickly, in a trusted, secure manner, without requiring enterprise-level bureaucracy." [...] Stefan Roever, founder and CEO at AIKON. "What excites me about AIKON is that we're offering the missing pieces in the existing blockchain environment to create an economic operating system that allows individuals, enterprises, and developers to fully participate." "We're trying to create a system where equal treatment is built into the fabric of the digital economy. That's the promise of blockchain - that everyone from the smallest teams to the biggest companies get access to the same data, which means they have the same opportunity to build something amazing," said AIKON Co-founder and Chief Product Officer Marc Blinder. "We designed the ORE Protocol to foster a truly fair and transparent decentralized economy that anyone can contribute to and profit from, no matter who they are or where they live." [...] AIKON's vision is to build technology products that decentralize and catalyze the global digital economy. AIKON believes that the world must become a decentralized global economy to facilitate worldwide collaboration and equal opportunity regardless of location, background, or easy access to banks or credit cards."

    From a second report published on the 26th of July 2018 (the day before yesterday) we got the following slightly confuse information: "AIKON and Hadron Start Ups Using Blockchain For Hubble Data Processing
    AIKON and Hadron blockchain projects are testing a blockchain network for processing the vast amounts of Hubble data produced.
    AIKON has provided [the] Space Telescope Science Institute (STScI) [located on the Johns Hopkins University Homewood Campus and operated for the National Aeronautics and Space Administration (NASA) by the Association of Universities for Research in Astronomy (AURA)] with an interface for receiving photos from Hubble and researchers are using Hadron blockchain for processing and visualizing the data.
    Josh Peek, an associate astronomer with STScI, stated other space telescopes, requires "millions upon millions" of hours of computing power to process data, which can become expensive. Blockchain solution may provide a more efficient use of resources by allowing researchers to tap into a larger network than might be available via a traditional server farm. [...]
    The computing time paid for with AIKON's "CPU" tokens. The coin price is pegged to the average cost of computing power charged by cloud hosting services.
    The system is currently being tested by STScI astronomers using a supply of free tokens."

    In this respect, we do not know

  • what High Performance and High Productivity Computing Systems (HP²CSs), Big Data Processing (BDP) technologies, and Scientific Computing Environments (SCEs) have in common with the blockchain technique, because they have opposite and in some cases even mutually exclusive requirements,
  • what data processing and visualization have in common with Digital Rights Management (DRM) and a related marketplace, which AIKON said is its main business, and
  • why a blockchain platform should be larger and less expensive than the cloud computing platforms of the companies Amazon, Microsoft, Google, and IBM, specifically when such a service based on our original and unique, exotic combination of a telescope and a blockchain-based system, and the further combination with SoftBionics (SB) belong to our range of Ontologic Applications and Ontologic Services (OAOS), which is licensed by a share of 5% of the revenue generated with it.

    Obviously, the argument of cost reduction is only a false pretences of fraud.

    But we do know that

  • our original and unique, iconic Ontologic System includes
    • SoftBionics (SB) with the subfields
      • Artificial Intelligence (AI),
      • Machine Learning (ML), and
      • Computer Vision (CV),
    • Problem Solving Environments (PSEs) and Scientific Computing Environments (SCEs),
    • High Performance and High Productivity Computing Systems (HP²CSs),
    • Fault-Tolerant, Reliable, and Trustworthy Distributed Systems (FTRTDSs) based on for example a
      • Byzantine Fault Tolerance (BFT) protocols,
      • Byzantine-Resilient Replication (BRR) method,
      • smart contract protocol, or
      • blockchain technique,
    • network of telescopes with the
      • Hubble Space Telescope,
    • IDentiy and Access Management System (IDAMS), and
    • Digital Rights Management (DRM), which is a set of Access Control (AC) technologies,
    • Electronic Payment System (EPS), as well as
    • their various integrations by our integrating Ontologic System Architecture (OSA),
  • our specific utilization of the network of telescopes, as explained (once again) in the OntoLix and OntoLinux Further steps of the 26th of October 2017 and 19th of April 2018, the Clarification of the 11th of May 2018, and also the issue SOPR #129 of the 23rd of July 2018, is the only usage making sense in relation with this issue,
  • "[t]hose opposed to DRM contend there is no evidence that DRM helps prevent copyright infringement, arguing instead that it serves only to inconvenience legitimate customers, and that DRM helps big business stifle innovation and competition, and the Electronic Frontier Foundation (EFF) and the Free Software Foundation (FSF) consider the use of DRM systems to be an anti-competitive practice, who are the same people who advocate free source and open source software, like AIKON and Hadron.cloud, and
  • truly nice and amazingly clever philanthropists would not attempt to make the Earth a better place by being such serious criminal fraudsters, who
    • steal others' Intellectual Properties (IPs),
    • cheat investors to get their money, and
    • mislead the public about others' achievements

    deliberately. Is not it?

    In relation with the copyright infringement conducted by the blockchain platform AIKON, the cloud provider Hadron.cloud, and the astronomer Josh Peek the short result of this short investigation is that there is not the slightest doubt that each entity has copied our Intellectual Property (IP), and both companies together with the scientist have copied even more of our IP in collaboration, which even worsens their individual frauds:

  • AIKON merely observed our publications, stole the related part from our Ontologic System (OS), which by the way already includes
    • Fault-Tolerant, Reliable, and Trustworthy Distributed Systems (FTRTDSs), such as the listed decentralized respectively distributed ledgers, distributed data stores, distributed computing platforms, and digital currencies based on distributed computing, specifically distributed ledgers, as well as
    • a platform with IDAMS, DRM, AC, and EPS (see for example the Ontologic Net Further steps and Ontologic Web Further steps of the 5th of July 2017),

    and promoted it as its own creation around 3 months ago together with the collaboration with other plagiarists such as Hadron.cloud.

  • Hadron.cloud merely stole the related parts of our Ontologic System (OS) for providing legal Ontologic Applications and Ontologic Services (OAOS) with its cloud computing platform, including Blockchain as a Service (BaaS), but also illegal trusted and secure distributed AI computation.
  • But that was not enough to satisfy their insatiable greed. Recently, both companies and the scientist stole together another part of our OS, which comprises many original and unique, essential combinations, integrations, and utilizations of its basic elements.

    In fact, "any reproduction of the Ontologic Net (ON), the Ontologic Web (OW), and the Ontologic uniVerse (OV) has been explicitly excluded from licensing" by the formalized regulations of the Articles of Association (AoA) and the Terms of Service (ToS) of our Society for Ontological Performance and Reproduction (SOPR) (see the issue SOPR #121 of the 29th of May 2018), like the related distributed ledgers and other FTRTDSs, and platform parts of our ON, OW, and OV, which are a(n)

  • economic operating system (economic OS),
  • DRM and EPS platform based on the smart contract protocol and the blockchain technique, and
  • trusted and secure cloud computing and distributed AI computing platform.

    But the actings of both companies and that scientist taken alone and in collaboration are bold and deliberately conducted

  • attacks on the infrastructure,
  • violations of the regulations,
  • attempts to gatecrash,
  • disturbances of the goals, and
  • even threats to the integrity

    of our formalized SOPR.

    As we said before, our OS is the only legal platform (see also the notes Blockchain fraud will come to an end #1 of the 8th of May 2018, Dump that island system of the 10th of May 2018, Blockchain fraud will come to an end #2 of the 28th of May 2018, Blockchain fraud will come to an end #3 of the , as well as the Clarification of the 11th of May 2018) and in accordance with the actual jurisprudence, we are allowed to

  • demand the removal of the related parts,
  • estimate the damages for each reproduction, and
  • demand compensation of damages for all infringements of our rights.

    AIKON and Hadron.cloud are frauds anyway. In fact, they are only stealing essential parts of our OS to make fast money and then immediately disappear again, as we have seen it before with EOS.IO, Tezos, Universa, and NeuroChain for example, and the cases of Ethereum and all the similar Fault-Tolerant, Reliable, and Trustworthy Distributed Systems (FTRTDSs) are not much better. But in this case we can even see a new dimension of this kind of Intellectual Property (IP) and investment fraud: Instead of giving up their frauds have been intensified even more by stealing our latest explanations of related matter, collaborating with the plagiarist and fraudster Josh Peek, and combining their platforms for processing data of the Hubble space telescope, and imitating our Society for Ontological Performance and Reproduction (SOPR) proving the high level of criminal energy once again.

    Only unserious and/or incompetent media reports about such fraudsters.

    03:19 and 09:02 UTC+2
    Attention: Fraud with our OS

    *** Work in progress - platform vs. infrastructure ***
    Do not invest your money in the blockchain platform Aikon and do not build any applications and services on top of AIKON. In fact, it is a scam, because the responsible entity

  • has no rights to license parts of our original and unique work of art titled Ontologic System and created by C.S. under another license, specifically under an open source license, than allowed by the copyright holder, who is represented by our business unit Ontonics and our Society for Ontological Performance and Reproduction (SOPR),
  • has no rights to sell parts of our Intellectual Properties (IPs) owned by C.S. and eventually parts of our corporation controlled by C.S., and
  • provides only an illegal island system due to the fact that neither the blockchain platform AIKON nor any applications and services based on it will get a license from our SOPR (see also the Ontonics Further steps of the 4th of May 2018 for example as well as the messages of the months July and October 2017, and the months March, April, and May 2018).

    Furthermore, such blockchain-based systems and similar distributed systems will not work without the broad consensus upon the public, especially the industries, that can only be provided by our SOPR.

    Our business unit Ontonics and our SOPR will ban such platforms As Soon As Possible (ASAP), though we do not accept other digital currencies than the official digital currencies of sovereign states and the ones of our Ontologic Bank (OntoBank) anyway, and if the responsible entities refuse to give in and give the money back, then we have to inform the prosecutors due to the conduction of an investment fraud, and the promotion and the funding of illegal activities.

    At the end, we would like to make clear once again the following points:

  • We will not make any further concessions.
  • No entity gets our universal ledger or alpha ledger. But SOPR members can hook into it without extra charge.
  • Federal agencies are very well advised to not work together with entities, that are disturbing the goals or even threating the integrity of our SOPR.


    29.July.2018
    Comment of the Day
    "Living the fake", [C.S., Today]

    The original versions are "Living the American Fake" and "Living the Media Fake", but it is neither only an U.S.American problem nor only an issue with the media.

    10:09, 18:35, 20:48, and 23:00 UTC+2
    SOPR #130

    *** Work in progress - crypto not ready ***
    We have continued with thinking and discussing about the matters related to the following topics:

  • Articles of Association (AoA) 3.0, Terms of Service (ToS) 3.0, and License Model (LM) 3.0,
  • cryptocurrencies, and
  • violations, disturbances, and threats.

    AoA 3.0, ToS 3.0, LM 3.0
    Because

  • it is much too risky for us with the actual AoA and ToS of our SOPR, that give us only a veto right and hence no chance to fill a legal loophole, if an entity would find a serious legal loophole or interpretation of the AoA and the ToS, so that in the end we would get no royalties,
  • too many entities do not understand at all that
    • our OS integrates all in one and eventually no loophole on the artistical and technical sides (e.g. smart contract protocols, blockchain technique, Byzantine Fault Tolerance (BFT) protocols, Byzantine-Resilient Replication (BRR) method, and distributed ledger technologies) does exist,
    • opening our Ontologic System (OS) and allowing them access to our OS for ridiculously low royalties is a incredible gesture and huge voluntary concession of us,
    • non-membership in our SOPR is not an option when using our IPs, and
    • they have to change their attitude and instead
      • show a convincing support for us and not for plagiarists and other fraudsters,
      • fulfill our recommendations and wishes As Soon As Possible (ASAP), and
      • work with us directly and officially where reasonable

      in return for our goodwill,

    and

  • as a reaction to the latest frauds in relation with our OntoLedger, specifically our universal consensus and ledger based on the network of telescopes,

    we are considering to

  • substitute the regulation given in the issue #110 of the 3rd of March 2018 that
    • the contract between a member of the SOPR and the SOPR is valid for 5 years between the dates of year ending with 1 and 5 (1st of January xyz1 to 31st of December xyz5), and automatically extended if not decided otherwise by the SOPR many years before (e.g. 10 years announcement period)

      with

    • the contract between a member of the SOPR and the SOPR is valid for 3 months between the quarters 1st of January to 31st of March, 1st of April to 30th of June, 1st of July to 30th of September, and 1st of October to 31st of December, and automatically extended if not decided otherwise by the SOPR some months before (e.g. 3 months announcement period),
  • completely eliminate the AoA, as suggested in the past already,
  • enter only individual license agreements with individual conditions for each entity that is liable to pay,
  • extend the AoA with a suitable regulation that guarantees our intentions, goals, and actvities, or
  • decide for several of these options,

    whereby the change from the Steering Committees to the Consulting Committees (see issue SOPR #124 of the 4th of July 2018) would take place simultaneously, so that we decide alone in the course of the common way instead of having only a veto.

    Cryptocurrencies
    Fraud on the basis of distributed ledgers and cryptocurrencies or similar value tokens is rising enormously. For example, in Australia the fraud with blockchain-based systems in the field of commodities has risen by 50% in the last year, in P.R.China wealthy owners of cryptocurrencies are buying real estate to circumvent government measures, and we have shown massive infringements of our rights and properties by providers of blockchain platforms with an own cryptocurrency or value token as well.
    But the governments and central bank governors of the G20 or Group of Twenty explained that the trading volume with cryptocurrencies has not reached such a critical level, that would require to begin with regulation, and hence they merely started to act against the laundery of money and the financing of terroristic acts.
    Furthermore, responsible federal institutions of some sovereign states have begun to give companies in the field of cryptocurrencies an official status as a bank or a trading platform for cryptocurrencies for example.
    Because

  • on the one hand we do not accept other digital currencies than the digital currencies issued by sovereign states and our Ontologic Bank (OntoBank), actually, and
  • on the other hand federal institutes do not control the legality of such cryptocurrencies and investments in them at all. Indeed, all cryptocurrencies known to us are Ontologic Applications and Ontologic Services (OAOS), even Bitcoin, and many of them are just only investment frauds and/or other frauds, and therefore existing and missing government measures undermine our protection scheme against fraud in this area.

    We already prohibited all Fault-Tolerant, Reliable, and Trustworthy Distributed Systems (FTRTDSs), such as

  • blockchain-based systems and distributed ledgers, that are not managed by the Society for Ontological Performance and Reproduction (SOPR), and
  • distributed digital currencies, that are not issued by federal institutions of sovereign states and the Ontologic Bank (OntoBank) of our SOPR,

    or being more precise, we explicitly excluded any reproduction of the Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV) from licensing in the issue SOPR #121 of the 29th of May 2018, as discussed in the note Blockchain fraud will come to an end #2 of the 28th of May 2018.
    But this even prohibits to provide a Blockchain as a Service (BaaS) and refers once again to the problem of differentiating a platform from an infrastructure in relation with our ON, OW, and OV.
    An alternative solution could be to only prohibit all combinations or integrations of a FTRTDS, that is not managed by the SOPR, with a digital currency, that is not issued by a sovereign state and our OntoBank, or accredited by the SOPR.
    In practice, such a regulation would mean that a member of the SOPR is allowed to either

  • provide a cloud computing service respectively something as a Service (includes for example BaaS), a distributed ledger, and/or any other type of FTRTDS without an own value token or coin, or
  • provide a service only related to a digital currency (includes for example Electronic Payment Systems (EPSs), cryptocurrencies, trading platforms).

    In this way, all legal and reasonable interestes can be fulfilled, at least for the first moment.
    Banks, other financial institutes, insurance companies, and similar companies would have to separate their businesses in independent companies accordingly, which is unavoidable for other legal reasons so or so.

    Violations, disturbances, and threats
    As not expected otherwise, we observed precisely planned and executed

  • violations of the regulations,
  • disturbances of the goals, and
  • even threats to the integrity

    of our SOPR.
    As announced, this triggers legal actions by us. For example, we are considering to file our first complaints against some of the script kiddies of the Teletubbies generation, blockheads, and crypto kiddies, as well as those entities supporting them at the related prosecutors. It should not be too difficult to guess who we mean.

    False cleverness and stupidity must be punished.


    30.July.2018
    Website update
    We have updated the OntoLix and OntoLinux Further steps of the 26th of January 2018 and the Clarification of the 8th of March 2018 due to the reasons explained in the Clarification of the 22nd of July 2018, which addresses also the combination or integration of Peer-to-Peer (P2P) computing systems with the blockchain technique, as we have

  • already explained before in relation with the P2P Virtual Machine (VM) Askemos with blockchain technique, the P2P cryptocurrency Bitcoin, the blockchain platform Etherum, and other blockchain-based systems, such as related distributed legers, and
  • now explained with the infringing InterPlanetary File System (IPFS).

    We also continued with the correction of misleading and wrong content on this website of OntomaX in this relation.
    For example, in the messages Ontologic Net Further steps and Ontologic Web Further steps of the 5th of July 2017 we said at first: "Please note that the blockchain technique has been added for users and applications that really need it on the one hand, though we are not sure if this is truly the case, but also for legal reasons on the other hand." But obviously, even we cannot add a feature to our Ontologic System (OS), that is already included in it just right from its start in the end of the year 2006.
    Another example is the OntoLix and OntoLinux Further steps of the 26th of October 2017, where we said: "But we felt that something is missing between the stars and our Trusted Computing Base (TCB), but only from the point of view of implementation. In a similar way, we also felt directly, when we heard about the blockchain technique once again, that it could fill the gap and provide a more harmonious transition." Obviously, a more correct formulation based on the facts is: "But we saw that something is missing between the stars and our Trusted Computing Base (TCB), but only from the point of view of implementation. In a similar way, we also saw recently, when we remembered once again, that the functionalities of the blockchain technique and distributed ledgers are already included in the software components of our OS and integrated by our Ontologic System Architecture (OSA), that they could fill the gap and provide a more harmonious transition."

    As we already said, we remembered and even showed that we read the works of Nick Szabo and other safety and security enthusiasts and crypto freaks, so to say, before the year 2006 and then thought at that time that everything related to Fault-Tolerant, Reliable, and Trustworthy Distributed Systems (FTRTDSs) is already included in our OS anyway, specifically by the basic properties of (mostly) being reflective, and validated and verified. Coming back now to the subject matter and the details when resolving and showing that this is truly the case, seems to be a little more difficult but is possible, obviously.

    Ontonics Further steps
    We developed a specialized version of a device, which is demanded by the whole world due to its general way of functioning and also its specialized areas of utilization.

    21:52 UTC+2
    Investigations::Multimedia

    *** Work in progress - better order, epilog not ready ***

  • Snap: In a partially fabricated report of a fake news provider, the founder of the so-called emoji avatar app called Bitmoji, acquired by the company Snap and integrated in its messaging app Snapchat, confirmed our findings, that the foundational concept and the integration of the avatars of its subsidiary Bitstrip as well as the companies Apple and Facebook are indeed copied from our original and unique work of art titled Ontologic System and created by C.S. by providing evidences that our Ontologic System (OS) has been taken as blueprint for Bitmoji and its integration in applications and services of the social network Snapchat on the one hand, and Snapchat's Bitmoji and its integration has been copied by Apple and Facebook on the other hand, so that eventually our OS has been taken as blueprint for the avatars and their integrations in applications and services of Apple and Facebook as well and our copyright has been infringed by all these companies one more time.

    We quote some passages from said report: "A couple of weeks earlier, an Android developer had discovered a test feature hidden in the Facebook app that introduced Avatars - cartoonish lookalikes that can be used "to communicate with your friends and express yourself across Facebook". [We use the complete range of representations as custom avatars in 2D and 3D, and for the reflection, self-expression, and communication of the users, and other applications many years before all of them, ranging from Lego minifigures at first to 3D scans of the users. See also the section Snow Crash and the Metaverse of the webpage Overview and the webpage Caliber/Calibre of the website of OntoLinux, and also the Pictures of the Day of the 15th of December 2012.]",
    ""I can remember being in a roomful of investors, in one of these pitch sessions six years ago and telling this roomful of people it was inevitable that everyone on the internet would have an avatar - and we're going to make them." [For us it is inevitable to prove the copyright infringement in relation with this original and unique feature of our OS and the subsidiary's cheating of the investors.]",
    "The app was born in 2007 as a website called Bitstrips, with a rather different goal: letting users without an artistic background easily create short comic strips. [First of all, we have to make clear that an app is not a website. Furthermore, the original Bitstrips service was publicly unveiled at South by Southwest 2008. Therefore, the facts are that there was no app in 2007 at all, the app Bitmoji was not born in 2007 but several years later, and the initial goal was not to create and provide an avatar or some other kind of self-imaging, self-representation, or self-expression of a user.],
    "The pivot to Bitmoji came the following year [2014], as the company focused directly on a use case that had always been popular among Bitstrips users: self-representation. The free-form comic strip feature was replaced with a more guided selection of sticker packs, letting users insert themselves into easily meme-able images to send to friends and family. That switch also took Bitmoji from the internet on to phones directly, setting the stage for its acquisition by Snap(chat) in 2016. [When the website or service of Bitstrips was used as a medium for self-expression and for creating a self-representation of a user for the first time is not known, though it is very plausible that it must have been after it was publicly unveiled in the year 2008. But this detail does not matter at all, because we presented our Ontologic System (OS) before the year 2007, which is the further development of the Evolutionary operating system (Evoos) presented in the The Proposal in the end of the year 1999, which again was also the first step of creating C.S.' self-reflection, self-image, or self-portrait, and cybernetic reflection, augmentation, and extension as part of the self-expressive works of art listed in the section History of the webpage Overview and the webpage Caliber/Calibre of the website of OntoLinux.]",
    ""We've seen Bitmoji gets integrated more and more [...]. [We have not seen and we even could not see the integration of such avatars before because we created the emotional and the emotional animated avatars. See once again the webpage Overview, specifically its section Integrating Architecture, and note the usage of the term integrate.]",
    "The service, [the founder of Bitstrips] says, carries a couple of big ideas. "One of them is communicating with cartoons. That was the obvious first point of integration: seamlessly integrating the Bitmoji library into the chat experience in Snap, and then expanding to the camera experience so you can add Bitmoji to your photos." But it's the other aspect that's where the competition comes from: Bitmoji as a "visual identity". On Snapchat, all users are represented by their Bitmoji, in icons, on the "Snap Map", and increasingly in augmented reality (AR) features as well, inserting a virtual avatar into the real world. [In September 2017, animated, 3D rendered Bitmoji were introduced to Snapchat's Augmented Reality (AR) feature called World Lenses, which is based on our OS as well. See the webpages Overview and Caliber/Calibre once again, and the sections Semantic (World Wide) Web, Geography, and Earth Simulation/Virtual Globe, and also Visualization, Mixed Reality, Collaborative Virtual Environment, and Human Simulation/Holomer of the webpage Links to Software of the website of OntoLinux. Last but not least, there is no competition but only those copies and the resulting liability to pay royalties, because we own the original and unique OS, where this visual identity comes from. specifically the Virtual Object System (VOS) and the Virtual Reality Chat (VRC) included in Mekensleep Underware software library set, including for example the skeletal animation based 3D character animation library Cal3D, which is originally designed to be used in a 3D client of a Massively Multiplayer Online Game (MMOG), supports combining animations and actions, and integrates morph targets used for facial expression easily into the system, and also used for the avatars in the game Poker3D]",
    "Earlier this month, Snap released Bitmoji Kit, a simple tool that lets other app developers incorporate the avatars into their own software. Initial integrations are simple [...] but it's not hard to see how they could grow, particularly with the growth in AR and VR worlds, which require the use of avatars to represent people. [See once again the comment made to the quote before and the other related comments.]",
    "Enter Apple and Facebook. "It definitely feels somewhat validating - and a bit of an honour - to be copied by the largest companies in the world," [the serious criminal plagiarist] Blackstock laughs. [Go away with Confucius and that totally scewed self-presentation. We do not feel such an utter nonsense but only see those infringements of our copyright and other rights.]",
    "He sees the appeal to those large companies of owning the visual identity of the future. [They only own the specific graphics in this respect but definitely not a visual identity (of the future). Eventually, we own the original and unique OS, which includes all relevant elements, and they infringe our copyright with the integrations and utilizations.]",
    ""An avatar, literally, is an incarnation. It enables you to put a version of yourself into another realm. This goes all the way back to Hinduism, where the word came from," Blackstock says. [Here we have the relation to the Ontological argument. See also the Investigations::Multimedia of the Clarification of the 20th of February 2018.]",
    ""Now, with what's happening with technology, and how it has been becoming such an integral part of society, it's like we're all living in a video game [or simulation]. [See the sections Visualization, Mixed Reality, Collaborative Virtual Environment, and Human Simulation/Holomer of the webpage Links to Software once again. This subject matter is also discussed under the topic of the simulated reality hypothesis, and the related topics of the simulation argument and simulation hypothesis, and also computationalism and mathematical universe hypothesis, and dreaming argument. A version of the simulation hypothesis was first theorised as a part of a philosophical argument on the part of René Descartes, and later by Hans Moravec. Our OS is also discussed in relation with the question "Are You Living in a Computer Simulation?" but this comes too short due to our integration of Synthetic Reality (SR) and other original and unique features in the OS. Furthermore, we were the ones who saw a smartphone, or being more precise, our Ontoscope as an extension of the user or as the personality of the user (see for example the Clarification #2 of the 13th of January 2017), and the overall OS as a cybernetic self-image, augmentation, and extension of a user and a user's identity (see the section History of the webpage Overview once again).]",
    "So it's a no-brainer: you're living in this world, you need to have a presence in this world. [See once again the related comments made to the quotes before.]",
    ""So when I see Apple and Facebook making these moves, it's representative of the impact we've had proving the importance of this idea. Competition is a fact of life in any business. I've seen the Apple thing but I haven't seen what Facebook's doing - presumably it will be as close as possible clones of Bitmojis, that's what they try to do." [That plagiarist is even so bold and claims that Apple and Facebook are copying his copy of the related part of our OS besides claiming to be the creator of our big ideas. By the way: Infringement of the copyright and other rights is not competition but fraud, and there is no competition in this field, because we own the original and unique OS.]",
    "Even if [Augmented Reality (]AR[)] and [Virtual Reality [(]VR[)] technology never reaches the heights that its supporters suggest, Blackstock still sees a universal need for online avatars. "For us, the way we look at Bitmoji is: it's not just about the avatar, it's what you do with it. How is this useful to you in your life?" [What a blah blah blah. Nevertheless, we simply call what you do with it Ontologic Applications and Ontologic Services (OAOS).], and
    ""Using it for communication, that's been the game changer. In real life, you are the medium of your expression and your identity is a key layer in that expression. And that's what Bitmoji's bringing to the table." [See once again the related comments made to the quotes before and also note the usage of the term layer and see the section Integrating Architecture of the webpage Overview once again.]".
    Also note the terms proving, validating, universal, and so on copied from the website of our OS OntoLinux as well to confuse the public even more about the true origin of our works and achievements.

    Indeed, we have taken Lego minifigures as custom avatars in 2D and 3D as well, while the subsidiary Bitstrips of Snap and the other companies have taken comic-style figures as custom avatars or cartoonish lookalikes of users.
    But

  • the Lego minifigures are also available in comic-style figures since the first video games of Lego and displayed in this way, and
  • in this case a specific realization of the avatars is not relevant at all and not sufficient to avoid a causal link with our OS, because of the more general concepts, such as the
  • integration of reality and virtuality with our OS in general,
  • self-expression in general,
  • communicating with cartoons,
  • animated emoji (animoji) and animated avatars,
  • integration of (custom) avatars in Augmented Reality (AR) and Mixed Reality (MR) in particular,
  • integration of (custom) avatars in online maps in particular,
  • etc..

    In addition, they called their Bitmoji, memoji and so on, that are derived from the designation of the visual language called emoji meaning picture character or pictograph. Emoji are ideograms and smileys and exist in various genres, including facial expressions, common objects, places and types of weather, and animals. They are similar to emoticons, though emoji are pictures instead of typographics and the resemblance to the English words emotion and emoticon is purely coincidental. Nevertheless, they include facial expressions, which "[are] one or more motions or positions of the muscles beneath the skin of the face, convey the emotional state of an individual to observers, and are a form of nonverbal communication, and are similar to emoticons, which are pictorial representations of facial expressions using characters, and therefore the syntactial resemblance to the English words emotion and emoticon is coincidential but not the universal semantical resemblance. again comes from emotion and expressing emotions, as we already explained in the Clarification of the 1st of November 2017 and 2nd of November 2017, and the Website update of the 6th of November 2017 (see also the OntoLix and OntoLinux Further steps of the 10th of July 2016).
    Eventually, this implies that the emotional avatar is another original and unique part of the expression of C.S. created with the artwork Ontologic System, as is the case with the animated emoji (animoji).
    Our avatars are also integrated in the Virtual Reality Chat (VRC) included in the Mekensleep Underware software library set besides a game engine and the 3D modeler Blender.

    In short, we have an integrating system architecture

  • based on proper ontology and existency, as well as reflection and emotion, and
  • integrating custom avatars for users with gestures and facial expressions, stationary and mobile applications for communication, as well as the fields of AR and VR.

    Q.E.D.

  •    
     
    © and/or ®
    Christian Stroetmann GmbH
    Disclaimer