in our OntoBot component, specifically in its part related to the

as part of our Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV), as well as our Society for Ontological Performance and Reproduction (SOPR) platform based on them (see also the OntoLix and OntoLinux Further steps of the 26th of September 2018).

Ontologic Web Further steps
We are continuing with the development of the Ontologic Web (OW) platform for advertising and marketing.

14:45, 25:1x, and 26:25 UTC+2
SOPR #142

*** Work in progress - some more information might be needed ***
We have to discuss several topics in this issue, including:

Infrastructure
In the issue #139 of the 4th of September 2018 we recalled once again some foundational regulations in relation with the reproduction and performance of

• platforms,
• systems,

• applications,

and

But there are also entities acting in the field of the infrastructure of the Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV) that

They get either the

(see also the issue #138 of the 28th of August 2018).

Data centers

As part of the infrastructure of our SOPR, we are also thinking about providing

dependent on the amount of collected and processed data.

Data sharing and interoperability

In this relation, we thought about various solutions for handling data and managing interoperability, specifically the

• big data and
• user data

as well as

• would give large and wealthy entities an advantage,
• eventually breach net neutrality,
• is not in the interest of our SOPR, and
• is not practicable at all, because virtually no entity can afford the cost.

• is not in the interest of the large companies and perhaps of other entities as well, and
• does not solve all use cases of the Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV).

• select the service that is the first registered one (FIFO principal) or
• do a fair coin toss as already done with Fault-Tolerant, Reliable, and Trustworthy Distributed Systems (FTRTDSs), specifically distributed time stamping systems and distributed ledgers.

At this point it can be seen that a moderator system works in a different way than a service broker of a Service-Oriented Architecture (SOA) and a mediator of a Semantic Service-Oriented Architecture (SSOA).

The moderator system also

and for sure

also

• multi-core processor architecture,
• virtualization,
• Service-Oriented Architecture (SOA), including the fields of
  • Service Object-Oriented Architectures (SOOAs) and
  • Service Protocol-Oriented Architectures (SPOAs),

  and

• Software as a Service (SaaS), or better said, Everything Anywhere Anytime as a Service (EAAaaS).

"The service consumer-provider relationship is governed by a standardized service contract,[...] which has a business part, a functional part and a technical part." Ideally, this would be done on the basis of the TQM and SLA based QoS management, smart contract protocol, and the SOPR ledger integrated in our OS.

The moderator system of the SOPR

• {correct terms?} belongs to the common reality features and anchors respectively reality reference frames,
• concerns the public (e.g. How many persons have crossed the road X at the location Y in the city Z?),
• is of statistical nature (e.g. How often have end entities verbally instructed a microwave to set the stopwatch?), and
• is not collected by a member of the SOPR (e.g. How many end entities have looked for the terms 'moon cheese' on all service platforms?),

• belongs to a virtual or digital estate of a SOPR member (e.g. End user X searched for 'fish with bicycle' on the service platform Y.).

At this point it can be seen once again that our Ontologic System is so unbelievably superior in comparison to those purely blockchain-based systems and other systems based on the Distributed Ledger Technology (DLT) of the crypto kiddies and the enthusiasts of the so-called Distributed Web or Decentralized Web (DWeb), that were developed in the 1990s and correspondingly lack virtually everything. :)

Also, note that without the regulation and moderation by the SOPR another entity could have done this as part of a proprietary or even closed system, and also:
Our OS always fits.

03.October.2018

Preliminary investigation of Michael Sobolewski started

*** Review - alignment with the matter of the field of Service-Oriented Computing 2 ***
Eventually, Michael Sobolewski has been busted by himself and us with his attempt to apply vodoo magic and some psychological tricks and semantic sleights of hand to make out of a Concurrent Engineering (CE) system

• Object-Oriented (OO 1) programming,
• tuple space model for parallel or distributed computing based on the Associative Memory (AM) paradigm and thought as a form of Distributed Shared Memory (DSM),
• concurrent computing,
• percept calculus knowledge representation scheme,
• Agent-Oriented Programming (AOP),
• Multi-Agent System (MAS), specifically
  • multi-agent knowledge-based environment for Concurrent Engineering (CE) applications viewed as shared Peer-to-Peer (P2P) peers or system components dedicated to users,
  • service provider agent,
  • interactive user agent, and
  • agent-based and rule-based metamodeling framework to simplify deployment of new models with user interfaces,
• Service-Oriented Architecture (SOA), specifically
  • Service Object-Oriented Architecture (SOOA),
• distributed computing
  • Peer-to-Peer (P2P) computing and
  • grid computing
    • service delivery network grid (see also cognitive grid)
      • self-organized service providers allocated to best resources,
      • dynamic Quality of Service (QoS) provisioning grid, and
      • compute resource management grid,
• distributed self-aware Service-Oriented Computing (SOC), where a federation is
  • knowing what it is doing,
  • able to learn from experience and adapt to surprises,
  • able to anticipate different scenarios and predict and plan for novel futures,
  • self-aware or self-inspecting and self-deciding of its behavior,
  • self-describing or self-explaining and self-representing,
  • self-testing and self-debugging within a federation,
  • self-explaining within a federation, and
  • self-managing using federated services,
• Computer-Aided technologies (CAx), but only
  • Computer-Aided Design (CAD) and
  • Computer-Aided Engineering (CAE),
• Product Data Management (PDM),
• Problem Solving Environment (PSE), and
• mobile computing,

and

• Java (OO 1 with Virtual Machine (VM), concurrency, introspection, etc.),
• JavaSpaces based on the Tuple Space (RS) model (service specification providing a distributed object exchange and coordination mechanism for Java objects),
• Jini based on JavaSpaces (federated SOOA with Quality of Service (QoS), etc.),
• Rio based on Jini (dynamic framework for distributed systems with System Level Agreement (SLA), etc.),
• Juxtapose (JXTA) (P2P protocols defined as messages in eXtensible Markup Language (XML)), and
• Java Management Extensions (JMX) (managing and monitoring tools),

an essential part of our original and unique work of art titled Ontologic System based on (the integration of) the fields of

as well as the

• Mandatory Access Control (MAC),
• Role-Based Access Control (RBAC), and
• Type Enforcement (TE),

that he even coined an operating system and gave it the acronym of our business unit Style of Speed (SOS) to confuse the public even more despite that the resulting plagiarism is merely a Runtime Environment (RE) respectively a Virtual Machine (VM).

In fact, M. Sobolewski already came too late in March 2007 with his concurrent Federated Method Invocation (FMI) for metaprogramming and other system features, as well as using the term ontology, so that his whole blah blah blah of the following years is just only a failed attempt to jump the queue and mislead the public.
The following quote is already sufficient to convict that plagiarist: "[...]
A service-oriented architecture [(also called as "[t]he new triple Command pattern architecture")] presented in this paper implements FMI to support metaprogramming.
[...]
6. Sixth generation RPC - Federated Method Invocation (FMI), presented in this paper, allows for network invocations [(some weeks later substituted by "concurrent invocations")] on multiple federating hosts (virtual metacomputer) in the [Service ORiented Computing EnviRonment (]SORCER[)] environment [33].
[...]
A service context, based on the percept conceptualization, is a data structure that describes [a] service provider ontology along with related data. A service ontology is controlled by provider vocabulary that describes objects and the relations between them in a provider's namespace within a specified service domain of interest. A requestor submitting an exertion to a provider has to comply with that ontology.
[...]
Polymorphism lets us encapsulate a request - in FMI an exertion - then establish the signature of operation to call and vary the effect of calling the underlying operation by varying its implementation.
[...]
This approach [based on the triple command software design pattern] allows for the P2P environment [8] via the Servicer interface, extensive modularization of Exertions and Exerters, and extensibility from the triple design pattern so requestors can submit any service-oriented programs (exertions) they want with or without transactional semantics.
[...]
Executing a top-level exertion means a dynamic federation of currently available providers in the network collaboratively process service contexts of all nested exertions.
[...]
When permission is granted, then the operation defined by a signature is invoked by reflection.
[...]
[8] Goel S., Shashishekara, Talya S.S., Sobolewski M., Service-based P2P overlay network for collaborative problem solving, Decision Support Systems, Volume 43, Issue 2, March 2007, pp. 547-568 (2007)"
Before the publication of this quoted document, the explanation related to an ontology was not given. In fact, the related quoted sentences were missing in the first publication of the (same) chapter in 2002, as is the case in later publicaitons.

This other quote related to the already failed attempt to steal the related essential parts of our Ontologic System with that metacomputing system, which "builds on top of FIPER to introduce a metacomputing operating system", gives that kleptomaniac the rest: "[SORCER Operating System (]SOS[)] allows execution of a service-oriented program and by itself is the service-oriented system."
Obviously, he found out after around 5 years

• listed The Proposal and the basic property of our Ontologic System of (mostly) being holonic, reflective, fractal, and
• described it in relation with a MAS as holon,

and

• Service Runtime Environment (SRE), Service Virtual Machine (SVM), or Service Execution Engine (SEE), and
• whole Java technology including Jini and Rio,

a SOA based on SOC and a Semantic SOA (SSOA) based on Semantic SOC.

Additional evidences that provide the causal link with our OS are at least the following points found in the list of research projects but not in the documents: "

In addition, we also found a document, which is related to sensor networks, and quote its summary: "Despite many technology advances, the limited computing power of sensors encumber them from taking part in service-oriented architectures. In recent years, the sensor networking subject has been extensively studied, with the focus on efficient usage of energy in sensors and efficient usage of sensor node processing power. However, providing sensor nodes with the relevant computing power and network sensor management is seldom addressed. With the availability of federated meta-computing environments, sensors can participate in service oriented computing, by exporting sensor probe data with relevant processing as a network service. The framework introduced in this paper allows for building highly scalable and dynamic sensor networks, providing sensors with corresponding federated computing environment. A novel approach using the SORCER metacomputing model to integrate several different sensors and sensor networks into a dynamic service-oriented sensor network is presented."
This proves once again that we have integrated the fields of SOC and Semantic SOC (SSOC) with the field of sensor networks.

What makes us wonder in this relation are the facts, that he has

• he came from the field of Knowledge-Based System (KBS), perceptual data processing, and Natural Language Processing (NLP) on the one hand, and
• the company General Electric also has copied another related work of us in the fields of semantic applications and ontologies on the other hand (see its case in the Investigations::Multimedia, AI and Knowledge management of the 6th of May 2013),

• Content Addressable Network (CAN) Peer-to-Peer (P2P) computing architecture,
• Virtual Object System (VOS), and
• Information-Centric Networking (ICN) architecture, comprising architectures like
  • Content-Centric Networking (CCN),
  • Named Data Networking (NDN), and
  • Data-Oriented Networking,

in total contrast to us and as we did.

We have sighted and archieved 2 websites, 29 papers, and 28 proposals for theses to get a comprehensive overview about the fraudulent activities and the applied tricks, and will present the complete investigation at a later time after we completed the cases of the company IBM, the Apache Foundation, and some other universities. Indeed, we have seen a

Moreover, the National Institute of Standards and Technology (NIST), the Defense Advanced Research Projects Agency (DARPA), and IBM were on board once again with supporting that mess as well.
We note to not rely on the works presented by M. Sobolewski et al. after October 2006 because they do not provide legal certainty.

As we mentioned in relation with other plagiarisms, especially interesting is the observation that the scientist must have recognized that our Ontologic System comprises the features and provides the functionalities of the FIPER as well, because otherwise there would neither exist a

which also implies that the plagiarist has

But at least, another external entity has recognized and comfirmed that our iconic work of art titled Ontologic System and created by C.S. is original and unique.

Btw.: We already said in the past that we will not accept some kind of a double taxation. Therefore, the United States Armed Forces and other federal institutions have to license our original and unique works of art titled Ontologic System and Ontoscope, and created by C.S. as well, like any other entity. This provision regulated by 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) applies for

04.October.2018
Ontonics OntoLab Vision Fund I #1

We are very pleased and more than proud to announce that we have begun with the activities for our

under the lead of our Hightech Office Ontonics.
Investors get the

08.October.2018
Ontonics Further steps
Since some few weeks we are working on an improvement of a system. Today, we concluded that its realization should be possible in two similar ways by slightly reconstructing the basic components and adapting their functionality.

As a side effect, we noticed that this improvemed first system can be utilized for the realization of a technology that is based on a similar second system and a third system, which works in a similar way like the second system but is utilized in a different way. In this way, we were able to unite the higher quality of the second system with the higher comfortability of the third system even in addition to the features and functionalities of the first system.

As a subsequent side effect, we noticed that this new technology can already be

which resulted in a solution that should be able to solve the serious foundational deficits of the third system in particular and its overall utilization in general, and therefore has the potential to become a worldwide standard.

Innovation happens.

09.October.2018

Investigations::Multimedia

*** Proof-reading mode ***

Besides the many typos, also note that the description uses terms to reflect our publications as well, such as components, architecture, models, simulations, concurrence, integrate, etc..
If we remember correctly, then a very similar solicitation was released by the Defense Advanced Research Projects Agency (DARPA) for its High-Assurance Cyber Military Systems (HACMS) program announced in 2012, that was also focused on an army aviation subsystem and based on the seL4 microkernel.
Nevertheless, we were exactly at that point discussed in the quoted solicitation around 16 years ago and came to the conclusion that

• network of telescopes,
• High Performance and High Productivity Computing Systems (HP²CSs) and Fault-Tolerant, Reliable, and Trustworthy Distributed Systems (FTRTDSs) based on it, such as for example our
  • universal ledger,

  as well as

• many other original and unique features and technologies of our Ontologic System (OS) and our Ontoscope (Os).

Even more incomprehensible is to

From our point of view, all these points only prove once again that the true goal is not the development of safe and secure open source hardware and software systems, but merely a political acting, or better said, a criminal acting: Lobbyists want to

In fact,

In this relation, we would like to repeat once again that any open source hardware and software, which is based on our original and unique works of art titled Ontologic System and Ontoscope, and created by C.S., as well as all other works directly connected with them require a licensing that is accredited by our Society for Ontological Performance and Reproduction (SOPR) and complies with its Articles of Association (AoA) and its Terms of Service (ToS) with the License Model (LM) and the End-User License Agreement (EULA) (see for example the issue SOPR #126 of the 10th of July 2018).
Even the federal agencies have to respect the international copyright law agreements, because

or otherwise face serious actions by the prosecutor.

Btw.: They and other decision makers have blocked us for nearly 2 decades, so that we had to document plagiarisms, foul plays, and other serious frauds with notes like this one, and eventually were unable to build up our companies and organizations for providing such opened source, or better said, disclosed source HASs. Now, they have to wait for us and comply with our regulations, because:
It is always better to collaborate with us.

10.October.2018

06:02 and 18:39 UTC+2
SOPR #143

*** Work in progress - some minor updates ***
Due to recent developments we would like to address the following topics (again):

Interoperability
We already suggested how interoperability could or should be realized from the point of view of the (operating systems based on) Ontologic System Components (OSC) by giving the explanation that we do not differentiate if interoperability is realized with an app, an application library, or an operating system service respectively an Ontologic System Component or an Ontologic Application (see the issue #139 of the 4th of September 2018).
Accordingly, the

will connect with the servers in the data centers managed and controlled by our SOPR for moderation.
In this way, an application for a smart device of a first manufacturer can work together with another smart device of a second manufacturer and an arbitrary cloud computing service of a service provider.

Convention of voice commands
We also would like to note that the convention of voice commands is ...

Nevertheless, a user can also use any other command.
If a specific virtual assistant does not provide a service, then either the moderator system begins a dialog for example by explaining that deficit and suggesting a solution, or by simply using an alternative service, though it has to be guaranteed that a service is truly an alternative (e.g. same quality, quantity, cost, etc.).
Needless to say, if (this) then (that) else (something other) commands will be handled by the OntoBot component included in the os, the mediator system, and the servers of the data centers and cloud computing platforms.

11.October.2018
Website update
In relation with the latest issue of U.S.American federal agencies (see the Investigations::Multimedia of the 9th of October 2018) we added the quotes of the related soliciation for convenience of our fans and readers.

We also added the friendly recommendation that an offerer has to provide all relevant informations, including the

or otherwise could face serious actions by the prosecutor.

19:51 and 21:4x UTC+2
SOPR #144

*** Work in progress - some beautifying ***
We thought about the following topics:

Introduction of discussed provisions
We thought once again about the introduction of the following provisions discussed in former issues:

• Ontologic System,
• Ontoscope, as well as
• all other works of C.S. based or connected with them

in accordance with the facts, interpretations, and explanations given by C.S. in relation with said works ***.

Discussion of new potential provisions
We also thought about the following new provisions to address recent developements and show which options were not chosen by us so far:

• ambivalent and ambiguous activities and
• the resistance to act against fake news providers,

of federal institutions and governments *,

• counter the observed increase of end user prizes,
• support start-ups and existing small businesses, and
• be more fair eventually,

Substitution of open source hardware and software
Members have to provide proposal how they substitute open source hardware and software with disclosed source or proprietary hardware and software licensed under Society for Ontological Performance and Reproduction (SOPR) End-User License Agreement (EULA) or alternatively under a license accredited by SOPR until 31st of December 2018 *.

*** definitely
** very likely
* potentially

12.October.2018
Preliminary investigation of Linux Foundation started
We found the following description on the website of the Civil Infrastructure Platform (CIP): "The Civil Infrastructure Platform ("CIP") is a collaborative, open source project hosted by the Linux Foundation. The CIP project is focused on establishing an open source "base layer" of industrial grade software to enable the use and implementation of software building blocks in civil infrastructure projects. [...] Hitachi's mission is to contribute to society through the development of superior, original technology and products."
We found the following description on the wiki of the Linux Foundation: "The Civil Infrastructure Platform (CIP) aims to establish a "base layer" of industrial-grade tooling using the Linux kernel and other open source projects. This base layer will be available for use by developers creating software building blocks that meet safety, security, reliability and other requirements that are critical to industrial and civil infrastructure projects."
For objectivity, we also note that the CIP Whitepaper was publicated in April 2017 and hence before we suggested our Society for Ontological Performance and Reproduction (SOPR).
We also found the following description on a website of a mimicking and participating company: "The Civil Infrastructure Platform (CIP) Initiatives is an open collaborative project hosted by the Linux Foundation and driven by the world's leading manufacturers of civil infrastructure systems, to establish a "base layer" of industrial-grade tooling using the Linux kernel and other open source projects. In addition, cybersecurity is a key element for CIP in order to secure civil infrastructure."
And we found the following section in a report on another website: ""The Civil Infrastructure Platform is the most conservative of The Linux Foundation projects," began Yoshitake Kobayashi [(head of Open Source Technology Department at Toshiba Corporation and Technical Steering Committee Chair of the Civil Infrastructure Platform (CIP) project)] at the recent Embedded Linux Conference in Portland. Yet, if any eyelids started fluttering shut in anticipation of an afternoon nap, they quickly opened when he added: "It may also be the most important to the future of civilization."" No, we do not think so, because these are already our original and unique, iconic works of art titled Ontologic System and Ontoscope, and created by C.S..

Obviously and doubtlessly, the Linux Foundation is copying our original and unique, iconic work of art titled Ontologic System and created by C.S., specifically its variant OntoLinux, as can be shown with the many causal links proven by all the evidences given for example with the parts of

and publicating and distributing the stolen elements of our Ontologic System under a new license, which

Remove those

• related parts of the OpenEmbedded framework and
• that asynchronous function,

as well as

• Verified Linux Package,

immediately if not done so far.
Alternatively, provide a license that can be accredited by our Society for Ontological Performance and Reproduction (SOPR) and use this for your open source respectively disclosed source hardware and software. The GNU is not Unix General Public License Version 3 (GNU GPLv3) and all those similar open source licenses are not accredited.

Furthermore, we highly recommend that the companies Hitachi, Toshiba, and Siemens, as well as Renesas, and the other CIP members begin to rethink their intentions and activities, because we all do want that their solutions are compatible with our Ontologic System and our Ontoscope, which have become mandatory already, as it is the case with solutions of other companies, such as for example LG Electronics. :)

Hopefully, companies like Google, Intel, Samsung, IBM, and some others are not participating in the CIP inititative as well.

15.October.2018

06:26 and 23:5x UTC+2
SOPR #145

*** Work in progress ***

In this issue we have the following matters as topics:

Maturity of AoA and ToS
After the last disturbances, that cost us 2½ months of precious time, we can see that the foundations of the Articles of Association (AoA) and the Terms of Service (ToS) with the License Model (LM) have been changed and extended (End-User License Agreement (EULA)), and will be changed and extended only in ways (see also the issue #144 of the 11th of October 2018) that constitute no obstacles for collaboration and operation (see also the section regulations of the European Parliament below), which inidcates that the AoA, ToS, and LM are becoming mature.
Accordingly, we will proceed as discussed during the last year, which comprised the writing of the inviting letter and its signing by the clever ones (see also the related note in issue #141 of the 16th of September 2018).

Regulations of the European Parliament
As already noted in a related comment of the 13th of October 2018, the European Commission and the European Parliament reflect the AoA and the ToS of our SOPR to rein in the online businesses, including

We came to the conclusions that

• data security and
• data privacy, and also
• handling and processing of
  • user data,
  • big data, and
  • virtual or digital estate

with

• can handle regulations like the proposed one, and
• provides some kind of a legal buffer between the members of our SOPR and governmental entities to compensate regulations,

which also shows the advantage of the SOPR once again.

General procedure of extension of moderator system
In the issue #xyz of the ??th of ?? 201v we already announced that other fields will be handled for guaranteeing interoperability as well. What we have not said in that issue is that we already follow a general procedure for deciding when a service requires the moderation which is give in the case when

• the opening and licensing of our our Ontologic System and our Ontoscope, and
• being neutral.

Extension of moderator system with mobility and transport services
We added

to the range of moderation system services after services related to

have been added.
A real or virtual entity can simple ask for a transport possibility and a suitable one will be ordered. Needless to say, she, he, or it can still order her, his, or its prefered transporation service as well.

Integration of moderator system with marketplace for everything
The integration of our moderator system with our marketplace for everything allows to delegate and account services provided by all members of our SOPR viewed as a pool.
For example, a real or virtual entity can demand a smart service contract of a first service provider, which would ideally be one of our related ON, OW, or OV platforms or another platform that should be hooked into our SOPR ledger, and guarantee the processing of data provided by a second provider with a service task or job (task of tasks) provided by a third provider of the field of SoftBionics (SB), the storing of the result on the platform of a fourth provider, and the accounting of every data and service provider for example by using a digital currency, which would ideally be one of our digital currencies of the Ontologic Bank (OntoBank). This can only be done in a superior and legal way on the platform of our SOPR or another platform that should be hooked into our SOPR ledger.
In another example, a real or virtual entity can demand a smart service contract of a first service provider, that orders a drone service of a first provider to make aerial pictures of a site, which is sent to a design service of a second provider with the model validated by an engineering service of a third provider and manufactured by a rapid production service of a fourth provider, and finally the manufactured item is transported to the site with a mobility service of a fifth provider.
At this point, it should have become obvious once again what great, astonishing, and sometimes even incredible opportunities we provide with our

• ON, OW, and OV, and also
• OAOS,

and

16.October.2018

00:25 UTC+1
Comment of the Day

06:03 UTC+2
Clarification

*** Work in progress - some corrections and beautifying related to SOC 1.0 and SOC 2.0, etc. ***
We would like to make clear that we had already

• the Semantic (World Wide) Web (SWWW) standards and technologies such as the Resource Description Framework (RDF) and the (nascent) Semantic Sensor Network (SSN) ontology, and
• our Caliber/Calibre

  a

• Semantic Sensor Net (SSN),
• Semantic Sensor Web (SSW),
• Ontologic Sensor Net (OSN),
• Ontologic Sensor Web (OSW), and
• Ontologic Sensor uniVerse (OSV),

and

before the World Wide Web Consortium (W3C), the Open Geospatial Consortium (OGC), and the National Institute of Standards and Technology (NIST) thought to be clever (not really) and jumped on the bandwagons of

• ontologic knowledge (Space, Time, and Theme or Topic (STT)),
• context, and
• provenance.

In addition, they also have not for example integrated the fields of

• Service Object-Oriented Architecture (SOOA 1.0) (enabled by Java Jini based on JavaSpaces and with Quality of Service (QoS)) and
• Service Protocol-Oriented Architecture (SPOA),

with the other existing fields of

and our contributions of the fields of

and also

• Semantic Net of Things (SNoT)
  • Semantic Sensor Network (SSN),

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

as well as

See also the Ontonics Further steps of the 15th of January 2018 and the notes Preliminary investigation of Michael Sobolewski started of the 3rd of October 2018 and the Investigations::Multimedia, AI and KM of today below, as well as all the other related statements, explanations, and clarifications of us.

Prominent applications of the SSN, SSW, OSN, OSW, and OSV are the fields of

• Industry 4.0,

We think that there is sufficient evidence to show a causal link with our OS and therefore we consider applications and services of the SSW as Ontologic Applications and Ontologic Services (OAOS), which requires proper licensing by our Society for Ontological Performance and Reproduction (SOPR). :)

12:59 and 17:26 UTC+2
Investigations::Multimedia, AI and KM

*** Work in progress - alignment with the matter of the field of Service-Oriented Computing and beautifying ***

Table of Contents (draft)
1 Basics and Vision
1.1 Living in a Digital World
1.1.1 Overview
1.1.2 Illustrative Ubiquitous Computing Applications
1.1.2.1 Personal Memories
[...]
1.1.3 Holistic Framework for UbiCom: Smart DEI
1.2 Modelling the Key Ubiquitous Computing Properties
1.2.1 Core Properties of UbiCom Systems
1.2.2 Distributed ICT Systems
1.2.2.1 Networked ICT Devices
[...]
1.2.3 Implicit Human Computer Interaction (iHCI)
[...]
1.2.3.3 Embodied Reality versus Virtual, Augmented and Mediated Reality
1.2.4 Context-Awareness
1.2.4.1 Three Main Types of Environment Context: Physical, User, Virtual
1.2.4.2 User-awareness
1.2.4.3 Active versus Passive Context Awareness
1.2.5 Autonomy
[...]
1.2.5.2 Easing System Maintenance versus Self-Maintaining Systems
1.2.6 Intelligence
[...]
1.3.2 ICT Device to Physical World Interaction (CPI)
1.4 Architectural Design for UbiCom Systems: Smart DEI Model
1.4.1 Smart Devices
1.4.1.1 Weiser's ICT Device Forms: Tabs, Pads and Boards
1.4.1.2 Extended Forms for ICT Devices: Dust, Skin and Clay
1.4.1.3 Mobility
[...]
1.4.1.5 Situated and Self-Aware
1.4.2 Smart Environments
1.4.2.1 Tagging, Sensing and Controlling Environments
1.4.2.2 Embedded versus Untethered
[...]
1.5.1 Interlinking System Properties, Environments and Designs
[...]
2.2.3 Smart Devices: CPI
2.2.3.1 Unimate and MH-1 Robots
2.2.3.2 Smart Dust and TinyOS
2.2.4 Smart Devices: iHCI and HPI
[...]
2.2.4.2 Things That Think and Tangible Bits
[...]
2.2.4.5 WearComp and WearCam
2.2.4.6 Cyborg 1.0 and 2.0
[...]
2.3 Everyday Applications in the Virtual, Human and Physical World
[...]
2.3.2.4 User-awareness and Personal Spaces
[...]
2.3.3.1 Transaction-based M-Commerce and U-Commerce services
[...]
2.3.4 Human-Physical World-Computer Interaction (HPI) and (CPI)
2.3.4.1 Physical Environment Awareness
[...]
2.3.4.3 Smart Utilities
2.3.4.4 Smart Buildings and Home Automation
2.3.4.5 Smart Living Environments and Smart Furniture
2.3.4.6 Smart Street furniture
2.3.4.7 Smart Vehicles, Transport and Travel
2.3.4.8 Pervasive Games and Social Physical Spaces
[...]
2.4.1 Smart Devices
2.4.2 Smart Physical World Environments
2.4.3 Context Awareness and Service Discovery
2.4.4 Wearable Smart Devices and Implants
[...]
3 Smart Devices and Services
3.2 Service Architecture Models
3.2.1 Partitioning and Distribution of Service Components
3.2.2 Multi-Tier Client Service Models
3.2.2.1 Distributed Data Storage
3.2.2.2 Distributed Processing
3.2.2.3 Client Server Design
[...]
3.2.3 Middleware
3.2.4 Service Oriented Computing (SOC)
3.2.5 Grid Computing
3.2.6 Peer-to-Peer Systems
3.2.7 Device Models
[...]
3.3.2.2 Semantic Web and Semantic Resource Discovery
[...]
3.3.3.2 Asynchronous (MOM) versus Synchronous (RPC) Communication Models
3.3.3.3 Reliable versus Unreliable Communication
3.3.3.4 Caches, Read Ahead and Delayed Writes
[...]
3.3.3.6 Event-Driven Architectures (EDA)
3.3.3.7 Shared Data Repository
[...]
3.3.4 Service Composition
3.3.4.1 Service Interoperability
3.4 Virtual Machines and Operating Systems
3.4.1 Virtual Machines
3.4.2 BIOS
3.4.3 Multi-Tasking Operating Systems (MTOS)
[...]
4 Smart Mobiles, Cards and Device Networks
[...]
4.2.4 Mobile Code
4.2.5 Mobile Devices and Mobile Users
4.3 Operating Systems for Mobile Computer and Communicator Devices
4.3.1 Microkernel Designs
[...]
5.1.3 Complexity of Ubiquitous Explicit HCI
[...]
5.2.2 Personal Computer Interface
5.2.3 Mobile Handheld Device Interfaces
[...]
5.2.4 Games Console Interfaces and Interaction
[...]
5.3.1 Multi-Modal Visual Interfaces
5.3.2 Gesture Interfaces
[...]
5.3.4.1 Touchscreens
5.3.4.2 Tangible Interfaces
5.3.4.3 Organic Interfaces
5.3.5 Auditory Interfaces
5.3.6 Natural Language Interfaces
5.4 Hidden UI via Wearable and Implanted Devices
5.4.1 Posthuman Technology Model
5.4.2 Virtual Reality and Augmented Reality
5.4.3 Wearable Computer Interaction
5.4.3.1 Head(s)-Up Display (HUD)
[...]
5.4.3.3 Virtual Retinal Display (VRD)
5.4.3.4 Clothes as Computers
5.4.4 Computer Implants and Brain Computer Interfaces
5.4.5 Sense-of-Presence and Telepresence
5.5 Human Centred Design (HCD)
5.5.1 Human Centred Design Life-Cycle
5.5.2 Methods to Acquire User Input and to Build Used[r] Models
5.5.3 Defining the Virtual and Physical Environment Use Context
[...]
5.5.5.1 Conceptual Models and Mental Models
[...]
5.6 User Models: Acquisition and Representation
[...]
5.6.4 Modelling Users'Planned Tasks and Goals
[...]
5.6.6 Situation Action versus Planned Action Models
[...]
5.7.2 User Context Awareness
[...]
5.7.4 Personalisation
5.7.5 Affective Computing: Interactions using Users' Emotional Context
[...]
6 Tagging, Sensing and Controlling
[...]
6.2.4 RFID Tags
[...]
6.3 Sensor Networks
6.3.1 Overview of Sensor Net Components and Processes
6.3.2 Sensor Electronics
[...]
6.3.5 Data Processing: Distributed Data Storage and Data Queries
6.4 Micro Actuation and Sensing: MEMS
[...]
6.4.4 Smart Surfaces, Skin, Paint, Matter and Dust
6.4.5 Downsizing to Nanotechnology and Quantum Devices
6.5 Embedded Systems and Real-time Systems
6.5.1 Application Specific Operating Systems (ASOS)
6.5.2 Real-Time Operating Systems for Embedded Systems
[...]
6.7 Robots
6.7.1 Robot Manipulators
6.7.2 Mobile Robots
6.7.3 Biologically Inspired Robots
6.7.4 Nanobots
[...]
7 Context-Aware Systems
[...]
7.2 Modelling Context Aware Systems
7.2.4 Context Aware Adaptation
7.2.5 Environment Modelling
7.2.6 Context Representation
[...]
7.3 Mobility Awareness
[...]
7.3.2 Mobile Phone Location Determination
[...]
7.4 Spatial Awareness
[...]
7.4.3.2 Geocoding: Mapping Location Contexts to User Contexts
[...]
7.5 Temporal Awareness: Coordinating and Scheduling
7.5.1 Clock Synchronisation: Temporal Context Creation
7.5.2 Temporal Models and Abstractions
7.5.3 Temporal Context Management and Adaptation to User contexts
[...]
7.6.1 Context-aware Presentation and Interaction at the UI
7.6.1.1 Acquiring the UI Context
7.6.1.2 Content Adaptation
7.6.2 Network-aware Service Adaptation
[...]
8 Intelligent Systems (IS)
[...]
8.3.1.1 Types of Architecture Model
[...]
8.3.1.3 Model Representations
8.3.1.4 How System Models are Acquired and Adapt
8.3.2 Reactive IS Models
8.3.3 Environment Model based IS
8.3.4 Goal-based IS
8.3.5 Utility-based IS
8.3.6 Learning-based IS
8.3.6.1 Machine Learning Design
8.3.7 Hybrid IS
8.3.8 Knowledge-based (KB) IS
8.3.8.1 Production or Rule-Based KB System
8.3.8.2 Blackboard KB System
[...]
8.4 Semantic KB IS
8.4.1 Knowledge Representation
[...]
8.4.2.1 Open World versus Closed World Semantics
8.4.2.2 Knowledge Life-cycle and Knowledge Management
[...]
8.5 Classical Logic IS
8.5.1 Propositional and Predicate Logic
8.5.2 Reasoning
[...]
8.6 Soft Computing IS Models
[...]
8.7.2 Classical (Deterministic) Planning
8.7.3 Non-Deterministic Planning
[...]
9 Intelligent System Interaction
[...]
9.2.1 P2P Interaction between Multiple Senders and Receivers
[...]
9.3.1 Designing System Interaction to be more Intelligent
9.3.2 Designing Interaction between Individual Intelligent Systems
9.3.3 Interaction Protocol Design
9.3.3.1 Semantic or Knowledge Sharing Protocols
9.3.3.2 Agent Communication Languages and Linguistic-based Protocols
[...]
9.3.5 Multi-Agent Systems
9.3.5.1 ACL and Agent Platform Design
9.3.5.2 Multi-Agent System Application Design
[...]
9.4.2 Recommender and Referral Systems
9.4.2.1 Recommender Systems
[...]
10 Autonomous Systems and Artificial Life
10.2.2 Self-* Properties of Intra-Action
10.3 Reflective and Self-Aware Systems
10.3.1 Self-Awareness
10.3.2 Self-Describing and Self-Explaining Systems
10.3.3 Self-Modifying Systems based upon Reflective Computation
10.4 Self-Management and Autonomic Computing
10.4.1 Autonomic Computing Design
10.4.2 Autonomic Computing Applications
10.4.3 Modelling and Management Self-* Systems
10.5 Complex Systems
10.5.1 Self-Organisation and Interaction
10.5.2 Self-Creation and Self-Replication
10.6 Artificial Life
[...]
10.6.2 Evolutionary Computing
[...]
11.7.8 Service-Oriented Networks
[...]
11.7.8.4 Overlay Networks
11.7.8.5 Mesh Networks
[...]
12 Management of Smart Devices
[...]
12.2.4 Configuration Management
12.2.5 Security Management
12.2.5.1 Encryption support for Confidentiality, Authentication and Authorisation
12.2.5.2 Securing the System and its Middleware
12.2.5.3 Securing Access Devices
12.2.5.4 Securing Information
12.2.6 Fault Management
12.2.7 Performance Management
[...]
12.2.8.2 Distributed Resource Management and the Grid
[...]
12.2.9 Information Management
12.2.9.1 Information Applications
[...]
12.2.9.4 Managing Multimedia Content
12.2.9.5 Managing Lean and Hard Data Using RDBMSs
12.2.9.6 Managing Metadata
[...]
12.3.2 Service Management Models for Human User and Physical Environments
[...]
12.3.4 Privacy Management
12.3.4.1 Biometric User Identification
[...]
12.4.1 Context-Awareness
12.4.1.1 Context-aware Management of Physical and Human Activities
12.4.1.2 Management of Contexts and Events
12.4.2 Micro and Nano Sized Devices
12.4.3 Unattended Embedded Devices
[...]
13.2.3 Evolution versus Revolution
[...]
13.6.3 Analogue to Digital and Digital Analogues
[...]
13.7.1 Posthuman: ICT Augments Human Abilities Beyond Being Human
13.7.2 Blurring of Reality: Mediated Realities

Chapter Summaries and Key Words
Chapter 1: Vision and Basic Concepts
Keywords [] Ubiquitous computing, pervasive computing, distributed system [(DS)], autonomous system, context-aware, artificial intelligence [(AI)], smart devices, mobile devices, smart environments, smart interaction, tabs, pads, and boards, smart dust, smart skin, smart clay, HCI.
[...] Chapter 2: Applications: Past And Present
Key Words [] Smart devices, smart environments, applications, everyware, smart vehicles, smart buildings, ebooks, ambient intelligence, cyborg, wearable computers, tangible interfaces, smart badge, calm computing, smart space, smart dust, Cooltown, pervasive games.
[...]
Chapter 3: Smart Devices and Services
Key Words [] Distributed system, abstraction, partitions, client-server, proxy, middleware, service oriented computing (SOC or SOA), [g]rid computing, peer to peer (P2P) [computing], service discovery, message-oriented middleware [(MOM)], remote procedure call (RPC), cache, delayed write, on-demand, event driven architecture [Event-Driven Architecture (EDA)], enterprise service bus [(ESB)], volatile service access, service composition, virtual machine [(VM)], multi-tasking, operating system (OS, MTOS), BIOS.
[...]
Chapter 4: Smart Mobile Devices, Device Networks and Smart Cards
Key Words [] Mobile devices, mobile code, mobile user, SMS, WAP, J2ME, .NET CF, microkernel, resource-constrained, power management, smart card, device network, device discovery, [Open Services Gateway initiative (]OSGi[)], X10.
[...]
Chapter 5: Human Computer Interaction
Keywords [] HCI, user interface, WIMPS, multi-modal, gesture, virtual reality [(VR)], augmented reality [(AR)], touchscreen, tangible interface, organic interface, posthuman,, wearable computers, heads-up display [(HUD)], virtual retinal display [(VRD)], brain computer interface [(BCI)], human centred design, user context, usability, conceptual model, mental model, user modelling, stereotype, task model, situated action, implicit HCI, personalisation, affective computing, interaction design patterns.
[...]
Chapter 6: Tagging, Sensing and Controlling
Keywords [] Tags, [Radio-Frequency IDentification (]RFID[)], virtual tags, sensors, sensor nets, controller, proportional integral differential (PID) controller, robot, embedded system, Micro-ElectroMechanical System (MEMS), nano technology, nanobots, operating system, Application Specific Operating System (ASOS) , Real-Time Operating System (RTOS), smart dust, smart paint, smart skins, smart matter,
[...]
Chapter 7: Context-Awareness
Key Words [] Context aware, adaptive system, composition, mobility-aware, location-aware, spatial-aware, trilateration, triangulation, [global positing system (]GPS[)], geographical information system (GIS), geocoding, user-context, ICT-aware, content-adaptation, temporal-aware.
[...]
Chapter 8: Intelligent Systems
Key Words [] Intelligent Systems, artificial intelligence (AI), software agent, knowledge-base (KB), semantic, ontology, machine learning [(ML)], reactive, goal-based, first-order logic [(FOL)], propositional logic, reasoning, inferencing, soft computing, probabilistic reasoning, Bayesian network, fuzzy logic, searching, planning, partial order planning, hierarchical task network.
[...]
Chapter 9: Intelligent Interaction
Key Words [] Interaction multiplicity, mediator, proxy, matchmaker, broker, cooperation, coordination, cohesion, joint-planning, norms, organisation, competitive, self-interested, electronic markets, micro-economic, agreements, consensus, convergence, negotiation, auction, voting, multi-agent system [(MAS)], speech act, interaction protocol, agent communication language [(ACL)], agent platform, agent-oriented software engineering, social network, Web 2.0, recommender system, referral, collaborative filtering, trust.
[...]
Chapter 10: Autonomous Systems and Artificial Life
Key words [] Autonomy, autonomic computing, automatic, self-star property, reflective systems, self-management, self-configuration, self-optimisation, self-healing and self-protection, complex, self-organising, replication, artificial finite state automata models, cell automata [(CA)], evolutionary computing [(EC)], genetic algorithm [(GA)].
[...]
Chapter 12: Smart Device Management
Key Words [] Process-oriented management, network oriented management, [fault, configuration, accounting, performance, security (]FCAPS[)], monitoring, accounting, [Internet Control Message Protocol (]ICMP[)], [Simple Network Management Protocol (]SNMP[)], configuration management, security, fault tolerance, performance, metrics, distributed resource management, Grid, Service level agreements (SLA), policy-based management, rich data, soft data, privacy, biometric user identification, privacy-invasive technologies, privacy enhanced technologies, regulation of user privacy, unattended embedded devices
[...]
Chapter 13: Challenges and Outlook
Key Words [] Challenges, future technologies, smart interaction, context awareness, low power, sustainable energy use, eco friendly, natural interaction, analogue to digital conversion, form factors, human intelligence, machine intelligence, posthuman, reality blurring, social issues, promise versus peril, virtual social interaction, accessibility, affordability, legislation, professional skills."

We are absolutely sure that neither reading the whole book nor showing the direct links to the true origins on our websites is required for proving that the overall structure and large parts of the content are plagiarizing our original and unique works of art titled Ontologic System and Ontoscope, and therefore infringing our copyright. Also note the jump on the bandwagon of the 3³ Theme of C.S..

As we mentioned in relation with other plagiarisms, especially interesting is the observation that the scientist must have recognized that our Ontologic System comprises the features and provides the functionalities of Ubiquitous Computing of the second generation (UbiC 2.0) as well, because otherwise there would not exist a

which also implies that the plagiarist has

Once again, another external entity has recognized and comfirmed that our iconic work of art titled Ontologic System and created by C.S. is original and unique.
Also, it is quite unbelievable how high the criminal energy truly is at research institutes.

At this point we would also like to recall that we also integrated all the other matters with our Ontologic System and its basic properties, integrating Ontologic System Architecture (OSA), Ontologic System Components (OSC), as well as Ontologic Applications and Ontologic Services (OAOS), so that we have

• cluster computing,

• Peer-to-Peer (P2P) computing,
• grid computing, cloud computing, and edge computing, and
• Fault-Tolerant, Reliable, and Trustworthy Distributed System (FTRTDS),

• Multi-Agent System (MAS),
• semantic computing,
• cognitive computing,
• etc.,

• Industry 4.0,

And that was already in 2006.

18.October.2018
Website review
We found a document about the Service-Oriented Computing Research Roadmap, that is based on spied out matter of us, suggests a "holistic approach", and was publicated in the beginning of 2006 at the same time when the other suspicious document about the cognitive grid was publicated. We knew all the time that much was done in the fields of Service-Oriented Architecture, Web Services (WS), and Semantic (World Wide) Web (SWWW) following our research and development all the years, but the hole is also much more deeper here than we thought at first.
This also shows once again that U.S.American and European entities have collaborated to steal our IPs all those years.
Nevertheless, we have to review the notes Preliminary investigation of Michael Sobolewski started of the 3rd of October 2018 and Preliminary investigation of Stefan Poslad started of the 16th of October 2018, and potentially other explanations, of us.

At least,

Furthermore, there is still so much missing in the prior art, so that eventually the legal situation does not change (much).
What JSON is to XML that is our OS to SOA with Java, SWWW, and all the other stuff, simply said, which is also the reason why we do not talk about an Ontology-Oriented System but an Ontologic System.

Clarification
Once again, we have done a quick look at some funny patents, such as for example

To clarify it short and sweet, (virtually) all those patents related to our iconic works of art titled Ontologic System and Ontoscope, and created by C.S. are void, specifically those filed after the October 2006 but also many of those filed before, because we can easily show by referencing and using prior art in the scope of the

• OntoLinux, specifically the webpages
  • Introduction,
  • Overview,
  • Feature-Lists,
  • Ontologic Applications,
  • Terms of the 21st Century,
  • Links to Software,
  • Links to Hardware,
  • Links to Organizations, and
  • Documents,
• Ontonics, specifically the webpage
  • Innovation-Pipeline,
• Style of Speed, specifically the webpages
  • Distributed Computing and
  • AutoSemantic,

  and

• OntomaX.

In fact, the ingenious inventors merely formulated specific combinations and integrations of said subject matters listed above, which we did before when developing the technical foundation for the realization of our Ontologic System and our Ontoscope and made very clear with our famous compositiong of said subject matters listed above and our statement that the OSA "integrates all in one" (see once again the webpage Overview).

Believe it now or face the truth later, but we stopped the whole Intellectual Property (IP) system, or so to say we killed the giant dragon, which shows

Furthermore, even if such patents would be valid then our Ontologic System and our Ontoscope are still required eventually.
Also, virtually all larger companies though to be clever by following and mimicking us and also attempting to block us due to the reason that they know we have found a solution that is not affected and protected by (other) copyrights and patents. But as discussed in the past, that does not work for various reasons due to the

so that we have elaborated around 10 different charges so far and most potentially this number of charges will increase.

Luckily, we have introduced our Society for Ontological Performance and Reproduction (SOPR) as an elegant solution for all entities. :)

Ontonics Further steps
We developed a new material that should be more suitable for a specific process.

We also developed two new processes.

19.October.2018
Clarification Announcement
We have begun to

• Jave technology,
• IBM Autonomic Computing,
• Federated Intelligent Product EnviRonment (FIPER) and Service ORiented Computing EnviRonment (SORCER),
• Service-Oriented Computing (SOC),
• IBM X10 programming language,
• Cognitive Grid Computing (CGC),
• Semantic Reality (SR or SemR),
• Ubiquitous Computing of the second generation (UbiC 2.0), and
• 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), as well as
  • Industry 4.0,

and

• show the many little and larger gaps between the different approaches and
• provide an even more precise foundation for multiple other activities eventually.

09:14 UTC+2
Investigations::Multimedia, AI and KM

*** Work in progress - NR vs. OV vs. SR; better epilog ***

Obviously, the authors knew our OS (see also the related Investigations::Multimedia, AI and KM of the 12th of October 2017, Clarification of the 4th of September 2018 and also the note Preliminary investigation of Stefan Poslad started of the 16th of October 2018).

This paper written by better known scientists in the field of the Semantic (World Wide) Web (SWWW) standards and technologies with Semantic Web Services (SWS) and Service-Oriented Computing (SOC) together with the other plagiarisms about our fields of

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

provides the next undenieable proof of the originality and uniquness of our OS and that our OS is indeed the original work of art, a revolutionary work of art, and already an inconic work of art.

Due to its

the protection by copyright and other rights should be obvious, as should be the multiple infringements of our rights with that investigated plagiarism.

21.October.2018
Clarfication
We have shown several times that nobody else than C.S. has envisioned our

• Ontoscope (e.g. modern versions of the Apple iPhone and iPad) and
• cybernetic extension of a user,

• electric vehicle platform,
• autonomous vehicle platform, and
• service platform providing
  • Ontologic Applications (OA) and
  • Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV) services, specifically
    • Mobility as a Service (MaaS) and Transport as a Service (TaaS),

• Synthetic Reality (SR or SynR) and
• Semantic Reality (SR or SemR),

Today, we would like to add that nobody else than C.S. has envisioned our

• Quality of Service (QoS) of networking becomes so high that (local area) cluster computing is possible over the Internet,
• cluster computing paradigm becomes a or even the foundation of the Internet,
• Internet becomes a supercomputer,
• Internet supercomputer becomes a SoftBionic (SB) supercomputing system respectively our Ontologic Net (ON),
• World Wide Wide (WWW) becomes a High Performance and High Productivity Computing System (HP²CS), and
• Semantic (World Wide) Wide (SWWW) becomes an Ontologic High Performance and High Productivity Computing System (OHP²CS) respectively our Ontologic Web (OW)

(see also the Clarification of the 4th of June 2018).

And no, Skynet has neither emotions nor other qualities and therefore is different to our ON, OW, and OV.
But nevertheless, this is only the beginning.

25.October.2018

16:14, 19:53, and 20:23 UTC+2
Too many have giant problem with facts and reality

In relation with a report about a car manufacturer it was reported that a short seller, who simply changed his strategy, said that

Obviously, that money juggler

• notes More evidences Schaeffler mimicking C.S. and C.S. GmbH of the 11th and 14th of October 2018, and
• Clarification of the 21st of October 2018,

and

But the documented facts are that

• SoftBionic (SB) functionalities for autonomous driving and
• service platform providing
  • Ontologic Applications (OA) and
  • Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV) services, specifically our original and unique
    • Mobility as a Service (MaaS) and Transport as a Service (TaaS),
    • Hyper Connectivity solutions,

and

And then we will cash up another time. :D

Preliminary investigation of Nextaxiom started

If we remember correctly we read already some years ago about the activities and the attempt of the company Nextaxiom to apply vodoo magic and some psychological tricks and semantic sleights of hand to make out of the field of Service-Oriented Programming of the first generation (SOP 1.0) the field of SOP of the second generation (SOP 2.0) respectively an essential part of our Ontologic(-Oriented) (OO 3) programming or simply Ontologic Programming (OP), but somehow forgot to make a complete investigation of it. Some days ago, we

• its suspicious website,
• its fabricated webpage in an online encyclopedia publicated in December 2007, which equals some content of its website and is already marked because "[t]his article does not cite any sources. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (February 2008)", and
• two reports about grid virtualization
  • one publicated on the 30th of January 2008 on a blog about a processor of the company Intel and
  • another one publicated on the 25th of February 2008 on a website about Service-Oriented Architecture (SOA),

and also

The preliminary results are that the company Nextaxiom is

• is merely describing an essential part of our original and unique, iconic work of art titled Ontologic System (OS) and created by C.S., specifically our integration of
  • multi-threading-based systems,
  • reflective and holonic systems,
  • model-driven approaches (e.g. Unified Modeling Language (UML), Agent-based Unified Modeling Language (AUML), Executable Unified Modeling Language (xUML), and Model-Driven Architecture (MDA)),
  • Semantic (World Wide) Web (SWWW) standards and technologies,
  • ontology-based programming,
  • Service-Oriented Architecture (SOA),
  • Autonomic Computing (AC),
  • Service-Oriented Computing (SOC), and
  • molecular systems (see CHemical Abstract Machine (CHAM)),

  and

  • Peer-to-Peer (P2P) computing, grid computing, and cloud computing,
  • virtualization, and
  • High Performance and High Productivity Computing Systems (HP²CSs),

  to our Ontologic Programming (OP) and Ontologic Computing (OC) (see also Kernel-Less Operating System (KLOS), Systems Programming using Address-spaces and Capabilities for Extensibility (SPACE), Apertos (Muse), L4, and so on),

• gives absolutely no explanations about how its system works in detail where such explanations are common and required,
• mentions its patents only very briefly once or twice,
• stops copying our OS where it was unable to understand and interpret our whole work of art and our related publications,
• made conceptual and technical mistakes, and
• has not updated its website since 2007,

• on the one hand there is no citation or other evidence publicated before the year 2007, and
• on the other hand its description of SOP 2.0 is merely an editing or rote, uncreative variation of our original and unique description of an essential part of our OS by substituting terms, using some more words, and rearranging terms, which does not constitute a new and own expressive creation and hence no derivative work or something else being eligible for copyright protection,

and

See also the related Clarification Industry 4.0 Special #1 of the 22nd of February 2017, the note Preliminary investigation of Michael Sobolewski started of the 3rd of October 2018, and our other related publications.

Stay away from that company and become a member of our Society for Ontological Performance and Reproduction (SOPR). We will give no allowance to use that SOP 2.0 in our OS without proper membership and proper licensing, if at all.

Btw.: This issue also shows where they all began to copy us once again by changing from Web Service Definition Framework (WSDL), Semantic Web Services (SWS), and SOA based on Web Service Definition Language (WSDL), RDF Schema, RuleML, and so on to metamodels, executable models, Web Service Modeling eXecution (WSMX), and so on. Too late. :)

Please do not confuse that plagiarism SOP 2.0 with works about SOP 1.0, as explained for example in the document titled "Service Oriented Programming: A New Paradigm of Software Reuse", which is about the Automated Information Router (AIR) and suggests to utilize languages that code semantic to integrate services.
In a much broader view, we already began to compare and show

• Java technology,
• model-driven approaches (e.g. UML, AUML, xUML, and MDA) (see also the book titled "Executable UML: A Foundation for Model-Driven Architecture"),
• SOP 1.0 and SOP 2.0,
• Autonomic Computing (AC),
• Service-Oriented Computing (SOC 1.0) (e.g. Service-Oriented Computing EnviRonment (SORCER) enabled by Java Jini),
• Service-Oriented Architecture (SOA), Semantic SOA, and SOC 2.0,
• Ubiquitous Computing (UbiC) or Pervasive Computing (PerC),
• and so on,

which were spied out and stolen from us to a large extent, fit togetther and

• closing the circle with
  • The Proposal,
  • our n-dimensional Reality (nR) or New Reality (NR) respectively Ontologic uniVerse (OntoVerse or OV),
  • etc.,

  and

• developing something totally new, unforeseeable, and unexpected, which nevertheless is compatible with our former works,

which led to their documented infringements of our rights (e.g. IBM X10 and Watson 2.0 with cloud computing and Internet of Things (IoT); Microsoft, Amazon, and Google business architectures; Nextaxiom SOP 2.0; Semantic Reality (SR or SemR), UbiC 2.0, Industry 4.0; General Electric GE Digital Predix, etc.).

27.October.2018

21:05 UTC+2
Oh, what ...?

We found on the website of the company IFS the following statement: "We are an enterprise software company that uses non-proprietary technology and a component-based service oriented architecture (SOA) built on open standards to deliver truly flexible, agile solutions with a great user experience to customers."
In addition, we also found contents copied from our websites as well as substantial and sufficient evidences that show a causal link with our original and unique, iconic work of art titled Ontologic System and created by C.S. respectively that essential parts of our unifying or integrating Ontologic System Architecture (OSA) and Ontologic System Components (OSC) are reproduced as well as Ontologic Applications and Ontologic Services (OAOS) are performed without allowance.
In this relation we would like to note that the field of Industrial Internet of Things (IIoT) is included in our 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) (see also the Clarification of today and other related publications of us).

According to the copyright law and other laws as well as international agreements proper licensing by our Society for Ontological Performance and Reproduction (SOPR) is required. Furthermore, the customers of IFS are also our customers, so to say, and also have to 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) as well.

22:28 UTC+2
Clarification

In this relation we would like to note that the field of Industrial Internet of Things (IIoT) is

• environmental monitoring,
• safe and secure (e.g. military grade) computing and communicating,
• intelligent analytics,
• and so on,

  where reliabile and accurate transfer, command, and control of mission critical information and responses are not optional,

and

• Distributed System (DS)
  • High Performance and High Productivity Computing System (HP²CS)
    • cluster computing,
  • overlay networking
    • Peer-to-Peer (P2P) computing,
  • grid computing, cloud computing, and edge computing, and
  • Fault-Tolerant, Reliable, and Trustworthy Distributed System (FTRTDS),
• Machine-to-Machine (M2M) communication,
• mobile technologies,
• Radio-Frequency IDentification (RFID) technologies,
• SoftBionics (SB)
  • Artificial Intelligence (AI),
  • Machine Learning (ML),
  • Computer Vision (CV),
  • Cognitive Vision (CogV),
  • Cognitive Agent System (CAS),
  • Cognitive Computing (CogC),
  • etc.,
• Autnomous System (AS) and Robotic System (RS),
• Big Data Processing (BDP),
• Cyber-Physical System (CPS), Internet of Things (IoT), and Networked Embedded System (NES),
• Computer-Aided Manufacturing (CAM)
  • 3D printing,

  and

• cybersecurity.

Therefore, IIoT is included in our 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), definitely.

28.October.2018

Comment of the Day

Investigations::Multimedia

*** Work in progress - some quotes of reflective (operating) systems and comparison with functional programming (LISP) and cognitive computing missing, correct comments, epilog, order, etc. ***

• XML

and

• Java (OO 1 with Virtual Machine (VM), concurrency, introspection, etc.),

the field of Resource-Oriented Computing (ROC) respectively an essential part of our Ontologic(-Oriented) (OO 3) programming or simply Ontologic Programming (OP) of our original and unique work of art titled Ontologic System based on (the integration of) the fields of

as well as the

that was even described in an online encyclopedia

and also described by the company itself

despite that

Also, the fact is very interesting that the fraudster, who manipulated the webpage about the NetKernel of said online encyclopedia on the

besides the other nonsense, is also the same person, who manipulated said online encyclopedia on the

Keep in mind that

We quote from its

We quote from the webpage titled "Introduction NetKernel" and publicated on the 27th of April 2005:
"1060 NetKernel is a software infrastructure, but it will generate misconceptions if I label it before describing its origins and essential architectural principles. []",
"Back in 1999 I was leading a small team of researchers at Hewlett-Packard Labs. We were exploring e-payment and e-contract systems - even back then we could see that the communicability of XML was going to transform business systems, and that XML message exchange was the route to interoperability.",
"Binding XML to procedural code destroys most of the flexibility promised by the XML. Procedural code is innately brittle with respect to changes in the business data model. [Somehow we have the impression that this is only a statement of its marketing.]",
"XML was cheaper than EDI but not cheap enough. [Indeed, but then came the companies Google and Amazon and used JavaScript Object Notation (JSON) instead.]",
"[...] writing procedural code to process XML is hideously painful - a pain that just won't go away. [Programming is hideously painful - a pain that just will not go away with NetKernel, but must go away or already went away with our OS.]",
"A challenge that had an historical parallel; replace "XML" with "RDBMS" in the statements above and you have a picture of the 1970s relational database before the introduction of the declarative SQL abstraction. Aha. Could we find an abstraction that encompassed the XML technology set and which decoupled the XML machinery from the XML process. [Indeed that resulting challenge had also a historical parallel; replace "Ontologic System" with "Java and XML processing engines" or "Java and NetKernel" and recall what we said about JSON in the Clarification #2 of the 5th of June 2016 and the related comment made to a quote before. These are also some of the reasons why we said in the Website review of the 18th of October 2018: "What JSON is to XML that is our OS to SOA with Java, SWWW, and all the other stuff, simply said, which is also the reason why we do not talk about an Ontology-Oriented System but an Ontologic System." But we did not throw away all the good features of XML, Java, SOA, and SWWW standards and technologies, and all the other stuff but integrated all in one. When putting this into the context of this investigation then we have to say that a NetKernel application can be faster than Java application but not fast enough. Aha (see also the Clarification of the 7th of June 2016).]",
"Our first experiments were to prototype XML pipeline frameworks. []",
"Language Diversity [...] a single language runtime is too limited for general applications [...] [But what they sell is a single runtime environment with NetKernel on top of Java.],
"XML Object Model Diversity. We built both SAX and DOM based engines, and both had limitations. [...] XML object models, just like languages, one size did not fit all [...] [But what they sell is an XML object model or XML resource model and our example related to JSON already showed that this approach is not very much accepted in practice. Furthermore, the NetKernel approach is a programming hell and an XML hell, that only shift problems and complexity around, but does not solve the issues in total contrast to what we do with our OS.]",
"Intrinsic Caching. To manipulate XML it has to be in some in-memory form and requires parsing. Parsing is expensive [...] [Everybody, who works with large or many XML files, as we did with data stores for XML files, knows exactly that very much Random Access Memory (RAM) is required to gain an acceptable performance. Caching is just a simple consequence when using much RAM.]",
"Libraries. Any general purpose processing environment scales efficiently when code reuse is encouraged. [...] It was also clear from our experience with vertical applications that domain-specific XML libraries would be an inevitable requirement. [This is not a new insight but common knowledge for true experts.]",
"Dynamic Discovery. [...] In order to use a technology in a high-level pipeline it has to be named and located. We tried using declarative registries, but realized that this led to management and maintenance complexity. We wanted dynamic discovery of components so that XML pipelines could rely on the environment to resolve the implementation. [This reminds us of the Java Jini framework.]",
"Exceptions. To be reliable and transactional, a processing model must enable exception management. Many of the XML technologies do not have an intrinsic exception model. [For sure, they do not have that, because it is the task of the underlying system layers, like a programming language with its runtime environment (e.g. operating system or Virtual Machine (VM)), to provide functionality related to exceptions.]",
"Debugging. It is very difficult to develop reliable software without the ability to stop and inspect the execution of the code. XML is generally very hard to debug at the object model level simply because the XML is dispersed through a collection of linked objects. [Could it be that someone did not understood for what XML was developed and how it has to be used?]",
"Over a number of years of investigation, we began to understand that "XML pipeline" was not an adequate expression of what we were encountering; we were specifying the requirements for "XML processes", process being defined as, "The execution of set of operations that is not linearly predetermined but is dynamically evaluated based upon the input data to the system [...] or [...] by exceptions." [And then they went on with reinventing the wheel, such as logic programming and metaprogramming, and we went away with creating and inventing something totally new. But after they saw our OS they began to bend their result, the NetKernel, so that it looks like our OS (see our quotes of its white paper and website and our comments below).]",
"We had a specification, but did the XML technologies have a unifying core foundation? For example, the technologies have an implicit relationship to the Web and are somewhat informed by Roy Fielding's description of the REST architecture. [The term unifying core foundation is highly suspicious. But more important is the close relation to the REST architecture.]",
"It seemed pretty clear that the [Uniform Resource Identifier (]URI[)] is the axiomatic starting point from which to develop an abstraction. The URI is the common factor that underpins the XML technologies and which provides the foundation of the Web model. From this the simple idea that a resource may be requested using a URI develops; the first principle of the Web. [So we have to note that already at that time they wanted to create something based on logics. Or should we better say based on Ontologics? Nevertheless, we have a graph or set as URI (see the Ontonics, OntoLix and OntoLinux Further steps of the 2nd of May 2016 and the Clarification #2 of the 5th of June 2016).]",
"What if software components were treated as URI-addressable services and invoked by making Web-like URI requests? [We are a little confused, because at that time the early Semantic (World Wide) Web (SWWW) standards and technologies already did exactly that and it is also the foundation of the fields of Service-Oriented Computing of the first generation (SOC 1.0) and Service-Oriented Architecture (SOA). Or does the author want to tell us that SWWW, SOC, and SOA have been invented by HPL as well?]",
"1060 NetKernel is the logical extrapolation of the simple idea of using URIs to dynamically locate and invoke software components. [The simple idea is also behind the Java Jini framework and the Collaborative Virtual Environment (CoVE) called Virtual Object System (VOS) integrated in our Ontologic System by its basic properties of Virtual Environments (VEs), specifically Augmented Reality Environment (ARE) and Virtual Reality Environment (VRE), and (mostly) being collaborative.]",
"NetKernel manages a dynamically populated virtual URI address space, composed by linking modules. Modules may expose software services and resources on their public URI interface and have a protected internal URI space which itself may consist of local and imported address spaces. The NetKernel URI address-space is analogous to the way Unix abstracts multiple file-systems into a uniform, logical file-system. The Unix abstraction treats everything as a file. In NetKernel everything is a URI-addressable resource. [So we have the NetKernel Virtual Machine (NKVM) (metalevel) on top of the Java Virtual Machine (JVM) (metametalevel) on top of the operating system Unix (metametametalevel).]",
"At NetKernel's heart is an asynchronous process scheduler which manages processes and low-level thread allocation. [But a scheduler is a service of an operating system.]",
"Most importantly, the kernel is a dynamic URI-resolver. URI requests issued to the kernel are resolved through the NetKernel URI address space where they ultimately connect with code. []",
"Requests are qualified by REST-like verbs; we have generalized from HTTP (GET, PUT, POST, etc) to a set of application protocol independent verbs: SOURCE, SINK, DELETE, EXISTS and NEW. [The term verb is highly suspicious. Note no verb META {compare with reflective Apertos}]",
"NetKernel is the URI addressing model of the Web combined with a Unix-like kernel. We sometimes describe NetKernel as a REST microkernel and, if we get ahead of ourselves, as a "virtual operating system". [We wonder why they have not taken an operating system like for example the Java Operating System (JOS) or a web server and added some reflective system properties like we did in the first development steps of our OS.]",
" [...] what emerges from this abstraction is a very simple, self-consistent way to treat software components as services. The URI address space provides the same horizontal and vertical scaling properties as the Web and results in general software systems which inherit Web-like adaptability and tolerance to change. []",
"NetKernel is a Web-like environment in which the URI address space can be treated as an executable program, but to accomplish this we have to think about URIs differently. []",
We have created a new URI scheme called the "Active URI" [4] which is fully compliant with the [Internet Engineering Task Force (]IETF[)] URI specification. An active URI is a URI which consists of a base part followed by any number of named arguments, and each named argument is also a URI. Here's an example: active:xslt+operator@file:///mytransform.xsl+operand@file:///mydoc.xml [The reflective operating system Apertos, which is the successor of the reflective operating system Muse, differences between passive objects and active objects.]",
"Since a named active URI argument is also a URI, it could be another Active URI (escaped appropriately). The active URI, in combination with the local NetKernel environment, is a functional program[...]. Issuing an active URI to the kernel results in the lazy evaluation of the program to compute the resource which it expresses. []",
"[...] every resource in NetKernel, even an intermediate computational result, has a unique URI and has the potential to be cached. [This sounds nice but has to be handled, becomes complex, and also has other problems.]",
"Since all resources are obtained through the kernel, the dependency chain of every resource is known. This allows the NetKernel cache to be "dependency-aware" such that changes to any given resource are automatically propagated to invalidate computed dependents. [This sounds nice but has to be handled, becomes complex, and also has other problems.]",
"Services are composed into processes and applications by using higher-order programming languages which abstract the underlying URI infrastructure. [???]",
"On NetKernel, a language runtime is just another type of service - a service for executing code for a given language. In turn, the code may execute other services by issuing further URI requests. [The reflective operating system Muse is also multilingual.]",
"You can think of NKF as a Posix-like abstraction layer around the kernel. Since NetKernel is asynchronous you can fork and join child processes, just like child processes on Unix. [So why not doing it directly as something like an operating system? As we said, we did it where it belongs to, that is on the highest metalevel. We knew at that time that nobody else than some companies in the field of operating systems was expecting that there could be a new operating system, a new programming system, and another totally new system.]",
"In addition to procedural languages, we have written two declarative language runtimes: Declarative Process Markup Language (DPML) is a very simple XML syntax for constructing active URIs. The DPML runtime simply dynamically compiles the XML syntax to a functional, active URI program. Our other declarative language is XML Recursion Language (XRL). [Once again, why not doing the same without XML the old-fashioned way without XML ballast and using XML for what it was developed and when it makes sense or even ditching XML entirely? And when already being at this point, why not ditching the World Wide Web and building something totally new that integrates all in one?]",
"Since language runtimes on NetKernel are simply services, it is very easy to add new ones, even application-specific languages such as custom workflow. We anticipate that there is the potential for several new languages that will intimately reflect the underlying NetKernel abstraction. []",
"Finally, we can return to the original motivating problem: can the economics of XML processing be made to add up? NetKernel provides a wide range of XML technologies as a set of modular service libraries. [Our answer is no if the context of the answer is a general computing model.]",
"Placing the XML technologies behind service interfaces encapsulates the API complexity and makes it very simple to compose genuine XML applications. Even more importantly, it provides an environment which is easily, even dynamically, reconfigurable to tolerate changes to the message syntax. []",
"When executed by the DPML runtime, the single instruction () in this script will be compiled down to the active URI shown earlier [(beginning with active:...)]. DPML is a service composition assembly language. Within DPML the URI address space this: is special; this:response is the resource which is returned by the DPML process. []",
"[...] neither of these processes has any need to understand the object model used by the underlying service. That is because NetKernel dynamically performs object model translation (this is just another service). []",
"You can think of NetKernel service composition as analogous to a generalization of the Unix-pipeline model, but since NetKernel exists on top of a Java virtual machine environment we are not limited to directing binary streams and can pass around higher order representational objects (streams or otherwise). [We ask once again why this is done with such a system stack comprising an operating system, the Java Virtual Machine (JVM), and another VM like the NetKernel Virtual Machine (NKVM) implemented in Java for doing something that the operating system has to do? This was the point where we began to change the whole technology with our integrating Ontologic System Architecture (OSA).]",
"NetKernel is a symmetric peer. It is both client and server. On the server side it supports pluggable transports including HTTP (REST), JMS, SOAP 1.1/1.2, POP, IMAP, and runs as a self-contained standalone application server. It also has an embeddable API and so can be deployed as a "co-processor", for example, within an existing J2EE application server. As a client it provides library services for HTTP (REST), SOAP 1.1/1.2, JMS, SMTP, RDMBS/SQL, etc. [But it is client-server and not Peer-to-Peer (P2P) computing or another type of Distributed System (DS). Furthermore, just look at the comment made to the related quotes before. The whole thing is a totally bloated and brittle thing. Imagine how complex the task becames in this way to make it only safe and secure to some extent or even to validate and verify the whole system stack.]",
"A transport on NetKernel is analogous to a device driver; its job is to receive external events and map them to service executions in the NetKernel URI space. [Once again we have to ask the question why the wheel was reinvented at all and even to run on top of the original wheel. How about taking a reflective microkernel with Virtual Virtual Machine (VVM), SoftBionics (SB), etc., and viewing the Internet respectively substituting it with a computer cluster, grid computer, or Peer-to-Peer (P2P) computer, and viewing the World Wide Web (WWW) respectively substituting it with a Peer-to-Peer (P2P) computer or grid computer, cloud computer, or edge computer as required and best suited? Independent of what will be the final architecture and configuration we call the result Ontologic Net (ON) and Ontologic Web (OW) by the way.]",
"As an example, we have written a "particle simulator" GUI application in which GUI events are issued as URI service requests to a service-oriented simulation model. The results of the model are then rendered in the GUI. [This statement is really a little strange.]",
"[...] another way to think of NetKernel is as a Web browser with pluggable rendering surfaces. [This is the same situation once again. A web browser is bloat and its function as well as the function of a rendering engine belongs into the layers of the operating system and the desktop or another Graphic User Interface (GUI) system when discussed in relation with the layout of the old or classic system stack.]",
"We started this article with a discussion of our early experience of building XML systems. We developed NetKernel to solve that problem. Along the way we discovered something quite general. Today we think of the XML technologies as like the lexical (line-based ASCII) tools which every flavor of Unix provides (sed, awk, grep, etc.)[.] To NetKernel, XML is the highest common denominator date type; it is flexible and, when combined with atomic service-based technologies, very powerful. But NetKernel has no dependence on XML. You may create your own application-specific object models, or add other standard data models. For example, it would be very straightforward to add an RDF tool set. [At this point we repeat that we still have that bloated system stack on the one hand and only a processing tool for files stored in the Resource Description Framework (RDF) format on the other hand but no Artificial Intelligence (AI), Machine Learning (ML), Computer Vision (CV), Cognitive Agent System (CAS), Natural Multimodal Processing (NMP), etc.. We also repeat that NetKernel without XML reduces to something that is similar to a very simple Java Virtual Machine clone combined with the Virtual Object System (VOS).]", and
"NetKernel is different but it is not a theoretical concept. It is used in real, large-scale production systems today[6 [Trimondo B2B portal, a joint venture of Deut[s]chse Poste and Lufthansa]]. [Interesting who collaborated at that time already.]".
We really like to see our original idea working but it was only a naive idea that we scrapped even before HPL decided what to steal from us. The bitter truth is that the XML was not developed for such a utilization respectively as a general processing model, but for others, and even for most of these other utilizations it is not really required or the best choice at all.
In addition, a reflective system remains a reflective system and using XML or WSs does not change this.

We quote from the white paper titled "Introduction to Resource-Oriented Computing [] Part I [] 1060 Research whitepaper series: [] Introduction to Resource-Oriented Computing - Part I", announced on the 29th of March 2007 and dated 12th of July 2007 as follows: "The paper introduces the foundational principles of ROC and discusses how they are a generalization of existing systems such as the Web and Unix.",
"The paper presents the axioms of ROC [...] [Before our publication of the OS based on logics there was no axiomatic system describing DEXTER and NetKernel but merely the statement that the "Uniform Resource Identifier (]URI[)] is the axiomatic starting point from which to develop an abstraction." Furthermore, the NetKernel was ... Therefore, there was no unifying compute engine, etc. at all.],
"It is likely that these principles will challenge your understanding of the nature of computation. [Obviously, that was not the case with the original DEXTER and NetKernel, but with our original and unqiue Evolutionary operating system (Evoos) described in The Proposal and our iconic Ontologic System (OS) integrating Evoos and much more.]",
"Resource-oriented computing is a new computing model with an old history. ROC is concerned first and foremost with information processing. It emphasizes logical information sources, uses, and transformation, ahead of physical code, data, and programming languages. The change of primary focus from languages to information represents a departure from an evolutionary path that has led from machine code to assembler, procedural, modular, and then object-oriented programming. Whilst this evolution has yielded significant improvements in productivity and expressiveness, ties to the physical computing layer (such as physical addresses) have restrained a leap forward to a truly simple logically-based computational model. [We have logics, Zero Ontology, Kernel-Less Operating System (KLOS), as well as the Resource Description Framework (RDF) for example in the Ontologic File System (OntoFS) software component, and obviously a general introduction of our original Ontologic Model and Ontologic Computing (OC) paradigm.],
"Resource-oriented computing offers this new simplified computing model. While it may seem that a model separated from direct association with the physical computing layer would be inefficient, hard evidence indicates the opposite. [Exactly, our OS comprise a special executable model-driven approach. But the hard facts are this is an essential part of our original and unique OS, and illegal infringement of our rights. Only the original artist has the exclusive right to give a work a title, and that is still C.S., who has not named it Resource-Oriented Computing but Ontology-Oriented Computing (OO 2 C) and Ontologic Computing (OC).]",
"This white paper provides a high-level introduction to the major concepts. [Needless to say, a white paper makes only sense when something new should be presented. Therefore, we have to understand that there was not that general resource-oriented computing paradigm in DEXTER and NetKernel, and a simple implication is that the NetKernel is not "World's first "Uniform Computation Abstraction"".]",
"Resource-oriented computing (ROC) is a simple fundamental model for describing, designing, and implementing software and software systems. Its simplicity derives from a small set of principles discovered through research initially started at Hewlett-Packard Laboratories and continued and expanded by 1060 Research. [The first sentence is true, the second is false. See also the webpage Overview of our Ontologic System OntoLinux, specifically its section Basic Properties and Integrating Architecture.]",
"Resource Oriented Computing Fundamentals [] A resource is a set of information. Specifically, in resource-oriented computing, resources are treated as abstracts; that is, a resource is a Platonic [1 [1 Harte, "Plato on Parts and Wholes"] concept of the information that is the subject of a computation process. At the physical level, a ROC system processes resource-representations, executes transformations and, in so doing, computes new resources. In this respect ROC is no different to any other computational model - computation is performed to collate and reveal new information. [Note the first reference of philosophy proper and the philosophical discussion of matter also related to a holon.],
"The shift in thinking introduced by ROC allows one to directly consider the abstract world of resources and in so doing, step-up and away from the physical implementation details of languages, object models and code. With ROC one designs and develops information processing systems by working on a new plane that is fundamentally logical and abstract. On first introduction such talk can sound like a bizarre and philosophical basis for a software development paradigm! [Note the second reference of philosophy proper and also logics, or better said in this context, ontologics.]",
"Our purpose in this white paper is to demonstrate that by placing computation on a solid and fundamental resource-centered foundation we can obtain huge practical returns and reveal a world of software development that lives in close harmony with the set-theoretic fabric of computation theory and that is unencumbered by the intricacies and escalating complexity of physical code. [As we said before, this was stolen from our OS because our OS is kernel-less reflective/fractal/holonic, and based on hyperset and hypergraph through the Topic Map (TM) standard for knowledge representation and interchange, which in fact are two of the revolutionary unforeseeable and unexpected steps, which also makes our OS original and unique.]",
"Having embarked on an apparently crazy philosophical mission [...] [Note the third reference of philosophy proper. Could it be that we are discussing a plagiarism here? And no, our ontological mission is not crazy but ingenious.]",
"In resource-oriented computing we have stepped off the physical plane of languages and their close ties to physical memory and onto a logical plane. [Indeed, it is only written "onto a logical" but not ontologics. What a cheap trick to confuse the public.]",
"Resource-oriented computing is concerned with constructing software systems which use fully resolve logical identifiers to obtain physical representations. In resource-oriented computing we can define a context as an information-space that contains a set of identifiable resources. [See the chapters 3.2 The Apertos Implementation and 3.3 Meta-Level Context Management as well as Figure 3 of the document titled "Kernel Structuring for Object-Oriented Operating Systems: The Apertos Approach".] It can be convenient to use the more intuitive term address-space and to think of resource-identifiers as addresses in the space - but be careful not to confuse these with the historic usage of the terms for physical-addressing within computing systems such as a pointer to a memory location; resource-oriented computing is concerned with logical identifiers and logical addressing. [Simply take a look at the reflective distributed operating system Apertos (Muse) and the Cognac system based on Apertos, the Systems Programming using Address-spaces and Capabilities for Extensibility (SPACE) (see the document titled "Building Fundamentally Extensible Application-Specific Operating Systems in SPACE"), and the interplay of metalevel and base level (or entity level), and metadata and data, and keep in mind that our integrating Ontologic System Architecture (OSA) also integrates SWWW standards and technologies, such as the RDF and OWL.]",
"Within the software realm, a resource-oriented system can use any suitable addressing system and, as we will see later, a particularly useful addressing system is the Uniform Resource Identifier (URI). [We would like to recall once again that our OS includes SWWW standards and technologies, such as the RDF, which again is based on URI. What we did with Ontologic Computing is to put away the XML of the original DEXTER and NetKernel and other formalization of the SWWW to get different unifying system, which is exactly a part of what that company has stolen from us and claims on its website as well (see the quotes of its website below).]",
"We have said that there may be many resource-identifiers for the same logical resource - therefore it is essential in a heterogeneous logical computing system that physical representations are immune to side-effects - that is, a resource's information-set cannot be changed by modifying a representation. [The same holds for our Ontologic Computing paradigm. It can be named Resource-Oriented Computing by fraudulent entities but it does not change the facts that is an original and unique element of our OS. We also note the term logical computing system, which the original DEXTER and NetKernel were not before 2007, but our original and unique, iconic Ontologic Computing System or simply Ontologic System.]",
"If there is a mismatch between the form preferred by the requestor and the form produced by the provider then a ROC system can intermediate and attempt to find a transformation that can change the representational form. This operation is a lossless, isomorphic conversion of the resource information from one representational type to another. To distinguish from a non-isomorphic transformation (i.e. a regular computational function that produces a new and distinct information resource), this lossless operation is called transrepresentation (or more commonly abbreviated to transreption). We can see that this is not unfamiliar in the real-world, when we perform a language translation of [a book] we endeavor to create a lossless transformation. Equally, this idea has always been at the heart of computer science, we are very familiar with the idea of losslessly transforming source-code into machine executable instructions - we call this compiling. Equally when we parse a file we losslessly transform the physical representation from disk to memory. [This reminds us of the multilingual and multiparadigmatic foundations of our OS (see also the case of the company Microsoft in the Investigations of the 27th of May 2009).]",
"Finally, and perhaps most importantly for a software system, new resources may be computed by applying operations to existing resources. Operations are themselves identified within the address space and they operate on the information/resource model with semantics that are relevant to that model. The identifier for the computed resource may be expressed as a combination of the operation identifier and the resources that are operated upon to create the new resource. [Instead of that, let us talk about metaprogramming and reflective programming with reification included in our OS.]",
"In summary, the [axioms presented before or] principles of resource-oriented computing are:
1. A resource is an abstract set of information [Our OS is based on the Topic Map (TM) standard and CHAM, and therefore on hyperset and hypergraph.]
2. Each resource may be identified by one or more logical identifiers [This is common practice in Logic Programming (LP).]
3. A logical identifier may be resolved within an information-context to a physical resource-representation [This is common practice in LP and web computing.]
4. Computation is the reification of a resource to a physical resource-representation [This is common practice in computing, Functional Programming (FP), Logic Programming (LP), the programming language C, metaprogramming, and reflective programming, where simply said a program or any other aspect of a programmig language is stored as data and data is used in a program. Reflection in the context of reflective operating systesm is defined as "the ability of an executing system of programmed objects to make attributes like the invocation, interface, inheritance and implementation of the objects to be themselves the subject of their computation. [...] The steps involved in reflection consists of: reification of an abstract object-oriented concept, reflective computation using the reified attribute as data, and reflective update that modifies the objects through reflective computation. We define reification as the representation of an attribute of an object-oriented program such as a member function dispatch, inheritance, and object structure as an object within that program. Such a reifying object provides member functions that support reflective computation of reflective update. [...] The dispatch of a member function of the reifying object corresponds to reflective computation.", from the chapter 2 Definitions of the document titled "Reification and Reflection in C++: An Operating System Perspective" about a reflective variant of the operating system Choices and μChoices, which also references the documents titled the documtents titled "Reflection and Semantics in a Procedural Language", which introduced the terms reification and reflection, "Concepts and Experiments in Computational Reflection", which is written by the same author who also wrote the document titled "Computational Reflection" referenced in The Proposal, and also "The Muse Object Architecture: A New Operating System Structuring Concept" and "A Reflective Architecture for an Object-Oriented Distributed Operating System". C.S. explained about the whole matter in our office as well, which is spied out since 2 decades now.]
5. Resource representations are immutable [unique existence and hence ontologic aspect]
6. Transreption is the isomorphic lossless transformation of one resource-representation to another [Blah blah blah, this common practice in computing.]
7. Computational results are resources and are identified within an address space [common practice in computing, LP, metaprogramming reflective programming, see also the reflective and distributed operating system Apertos (Muse) and the Cognac system based on Apertos]"],
"In this section we will look at three examples which exhibit, in varying degrees, some of the principles of a resource-oriented computing system. The first is the World Wide Web, the second is the set of Unix command line tools, and the third is Yahoo!Pipes, [...] The Unix command-line tools constitute the earliest example of a computing system demonstrating aspects of resource-oriented computing. []",
"Starting seven years ago, in Hewlett-Packard Laboratories and for the past five years at 1060 Research we have been pursuing the answer to a simple question "What if resource-oriented computing was applied to general software development?" [We do not buy but believe that the simple question was "What is C.S. building?", because DEXTER is of XML processing and therefore totally unrelated to that other question.]",
"In NetKernel all resources are abstract and are not directly manipulated. Instead a resource may be logically requested and resolved to a physical Accessor, a software endpoint, that can access (compute) a physical resource representation. [But this abstraction layer cannot be the reason for the increased performance.]",
"NetKernel uses the generalized Uniform Resource Identifier (URI) as one of its standard logical identifier models [...]. [Suddenly, that company claims to have more standard logical identifier models. We have graphs, specifically ontologies, and hypergraphs respectively hypersets, specifically Topic Maps (TMs) and CHAM programs.]",
"First, in-direction via a logical address ensures that all resources can be dynamically computed or substituted at run-ime. Second, uniformity ensures the abstraction is self-consistent [...] [First, the in-direction costs. Second, self-consistent reminds us of a reflective system property.]",
"Unlike object-oriented programming, where objects may hold direct physical references to other objects, resources in NetKernel refer to each other by a logical URI address. NetKernel implements indirect URI addressing by directing resource requests to a microkernel acting as an intermediary. [Let us talk instead about object-oriented metaprogrammig and reflective programming. And once again, that is not a microkernel but a Virtual Machine (VM).]",
"NetKernel modules contain this information context - they are a physical container for a logical resource address space. Modules are valuable as they allow developers to group resources that have similar capabilities or serve a common purpose. [In the reflective distributed operating system Apertos an object is a container of information,. The semantics of its behaviour is defined by a set of metaobjects (called a metaspace). We also heard that modular programming and object-oriented programming paradigms were developed to provide the same abstraction models and handle this and that. Somehow, we are getting more and more the impression that someone is reinventing the wheel and for sure our OS by selling an obsolete XML processing engine to the public.]",
"NetKernel modules include life-cycle management including live module updates, roll-back to previous configurations, and the simultaneous use of different module versions. [But these features require related abstractions, which some existing systems feature as well. Even more important, these functionalities are related to an extensible system and a reflective system. But the original DEXTER was different. See the reflective distributed operating system Apertos (Muse), ...]",
"The resource address space of a module is further partitioned. All resources reside in a private internal address space. A portion of the address space can be made public and exported. Modules may import the public exported address space of other modules into their own private internal address space - applications may therefore be composed out of cleanly separable logically-linked modular units. [This reminds us of our integration of KLOS, SPACE, and also Apertos (Muse) and the Cognac system based on Apertos, but not of an XML processing engine. The stupid thing is that it is based on the Java technology and that is exactly one of the abstraction model besided XML that we eliminated for the same reasons. At this point, it should become obvioius even for non-experts what the strategy of those plagiarists is, how they are trying to realize it, and why they failed in doing so.]",
"In NetKernel computation can take place behind any logical address. In fact, there is an important duality in NetKernel, resources are identified by URI addresses and computations are identified by URI addresses therefore the result of all computation is considered to be a resource. [But is not discussed here reflective programming eventually? The original DEXTER and NetKernel were not based on metaprogramming and reflective programming.]",
"Resources are abstract in NetKernel. They are also typeless. For example the resource "the list of people attending a conference", might have the URI ffcpl:/conference/attendance-list and the representation might be an array of Java String objects, a spreadsheet, or an XML document fragment. [Firstly, take a look at the Virtual Object System (VOS) that did this in 2002 already. Secondly, we have typed resources in our OS with the types being introduced by an index, thesaurus, taxonomy, topic map, ontology, knowledge graph, or other structure for knowledge representation. This and all the other semantic features are not included in NetKernel but tried to steal as well (see the related point listed in another section below).]",
"In NetKernel, all resource requests are handled through the intermediating microkernel [...] [Repeating false facts does not make them true. We are not doing politics or works of the press here.]",
"NetKernel's computational model is a proven resource-riented computing system for general software development. NetKernel has been used for a wide variety of systems including data analysis processing pipelines, cross-domain enterprise data integration, web-applications, service-oriented composition, discovery and fulfillment and even peer-to-peer autonomous network nodes in very large distributed systems. In every case, the proven benefits of ROC seen in Unix and the Web are found to translate to general software and have resulted in dramatically simpler and more performant projects. [Why not use the Java Jini framework? Furthermore, the proven benefits have been shown more than 20 years before with Kernel-Less Operating Systems (KLOSs), like for example KLOS and SPACE. But the right approach is to do it as we do by substituting the stack consisting of an operating system, the Java Virtual Machine (JVM), and an additional VM on top of the JVM in a simliar way and then add much more, specifically SoftBionics (SB), Service-Oriented Computing of the first and second generations (SOC 1.0 and SOC 2.0), a New Reality (NR), and so on (see also the Clarification of the 7th of June 2016). Obviously, those plagiarists do know these facts as well, as their misleading marketing activities and other illegal activities show.]",
"In a ROC system the implementation is anchored at the logical level - operations applied to resources are semantically relevant at that level of abstraction. And, since code to deal with type conversions and other such details are simply not needed in an ROC system [...] [So why not using terms like model and metalevel when talking about software architectures? Also, typing is required sooner or later, or otherwise we get neither semantics in symbol systems nor all the proven and wanted advantages of typed systems.]",
"NetKernel architects find that they can spend their time designing the information model for a system, the relationship between resources, the layering of their application and the flows along information channels instead of a myriad of tangential details. [But what is with the programming of the components or modules? NetKernel does not address this at all in total contrast to our OS, which also handles this down to the single bit, transistor, and atom as part of its truly holistic concept and architecture. Furthermore, the term information channel reminds us of the Channel Computing paradigm.]",
"Furthermore, because ROC works with sets of information, each connection and relationship established in NetKernel represents not individual datum but rather collections of data. [...] In NetKernel sets of information can be processed in their entirety with single instructions. [We already said, for example in a comment made before, that our OS is based on hyperset and hypergraph through the Topic Map (TM) standard and also the CHAM. Furthermore, our OS integrates Kernel-Less Operating Systems (KLOSs), such as for example KLOS and SPACE, and SPACE is used for the construction of paralled operating systems, computer clusters, and other Distributed Systems (DSs).]",
"Application server. NetKernel is a complete managed enterprise server platform. No application server product or technology is required. [] [We have not seen the management feature. And what is with its dependancy on the Java technology and its Java 2 Platforms, Enterprise Edition (J2EE)?]",
"Frameworks. The decision to use J2EE, Spring [(inversion of control container for Java)], [Apache] Struts [1 (application framework for Java EE web applications)], [JavaServer Pages (]JSP[) (dynamically generated web pages based on HTML, XML, or other document types)], [JavaServer Faces (]JSF[) (component-based user interfaces for web applications)], etc. is not required. NetKernel is a complete, extensible development and execution environment. [As we already said in a comment made before, its original DEXTER and NetKernel is presented as the integration of Kernel-Less Operating Systems (KLOSs), such as KLOS and SPACE, and Reflective Operating Systems (RefOSs), such as Apertos (Muse) and the Cognac system based on Apertos, Choices ("Reification and Reflection in C++: An Operating System Perspective") and μChoices, etc., as also done in the kernel-less, reflective language system called RbCL and described in the document titled "Reflective Object-Oriented Concurrent Language without a Run-time Kernel".]",
"REST vs SOAP vs WOA. NetKernel concurrently supports all popular SOA flavours for invoking and exposing web services. [But that is not the interesting point at all anymore. Also note the attempt to mislead the public about concurrent computing on the one hand and the fact that its field of application is Service-Oriented Architecture (SOA) and Web Services (WS) on the other hand. Web-Oriented Architecture (WOA) = SOA + World Wide Web (WWW) + Representational State Transfer (REST). WOA was presented on a blog with the Unified Resource Locator (URL) containing "2008/11/19" and not in the year 2006.]",
"Architects can view NetKernel system development as comprising three stages: construct, compose, constrain. [Do not confuse the third stage with Constraint Programming (CP), Constraint Logic Programming (CLP), Concurrent Constraint Programming (CCP), and so on, which are also interesting features of our OS.]",
"The application of constraints is last - this is when security, auditing, validation, or other restrictions are applied to the general software solution. As we will see later, this order is significantly different from object-oriented development in which constraints (in the form of typed classes) are applied first. [As software architects we do not buy this, because typing is done in the construction or modeling phase as well. Furthermore, constraints are also used in CP, CLP, CCP, and so on. By the way, the subject matter has been discussed by us in relation with the Investigations of the programming language X10 of the company IBM, that is used for cluster computing.]",
"Construct is the first stage in the ROC programming process.The purpose of this stage is to create resource models, which include physical resource representation formats and resource-level software functions, required by an application. [Once again, this can only be accomplished when some kind of semantics such as types are used. Compare this with the construction kit of the company Lego. What they say is that only the single stone with 1 knob and in 1 colour is available and a constructor can only connect single stones on top of each other and place the resulting columns side by side, across a plane like Mikado Sticks, or in a different arrangement. Obviously, that plagiarism works in a different way and hence there must be a typing in this phase as well, which assign a size, colour, function, and so on to the stones, as it is done with Object-Oriented (OO 1) paradigm.]",
"In most cases this stage is not actually required as NetKernel includes a rich modular library of resource models and functions. A resource model is a collection of related representation formats and software functions. [Oh, we have a library and a framework for component-based software development. And yeah, it is a wheel.]",
"NetKernel includes the industry-standard XML resource model and related functions. XML is a flexible and expressive resource model that is increasingly being used for intra and intersystems communication. NetKernel supports the representational types DOM, JDOM, SAX, and Stax, along with transreptors to convert between these types. Also included is a family of industry-standard software functions such as XSL transformation, XQuery processing, XPath support, etc. The mod-db module provides database connectivity functions that are able to process and return XML documents representing queried information. [So NetKernel is still based on XML processing. Our OS did this, the SWWW, and other abstraction models away for all the reasons that were given for the computing model of NetKernel. Obviously, we have presented the next evolution and revolution already 8 months before the publication of the investigated white paper.]",
"In situations where a new resource model is required, the supporting code can be designed and built using Java and traditional object-oriented development techniques. Once built, the resource model becomes a part of the overall capabilities of NetKernel and the resources can be composed and constrained just like others. [At this point, we are not sure anymore if we should cry or run away laughing. In addition, we have here a breach of paradigms on the one hand and a problem to understand its business strategy on the other hand.]",
"Just as in Unix, atomic service-based tools can be linked to together as functional pipelines via URI expressions. [Read for example the referenced documents about SPACE once again and find out what the true problem is. Hint it is related to pipelines, communication between address spaces, security, and so on.]",
"[...] it will be discussed below that the execution of dynamic code by language runtimes is treated in a uniform and consistent way. [But NetKernel is not a Virtual Virtual Machine (VVM).]",
"Whichever way the composition is assembled, the resulting information process is uniformly modeled in ROC as the source of new information resources. And since all resources are logically located in the address space then it is always possible to treat the composite assembly as a blackbox behind another logical address. In this way, at one layer of an application you can concentrate on the assembly of tools or resources to solve the problem - but at the next layer up, the composite can be conceptualized as a single dedicated tool or resource which itself can be incorporated into higher-order compositions. [So here we have an attempt to describe its component-based system as a system based on metaprogramming and higher-order logic.]",
"Constraints are the way in which we enforce integrity on an information process. They should not impact the overall structure or business validity of an architectural design. Constraints are rules that provide boundaries or limits on the processing potential that already exists. []",
"Constraints can be applied interactively at the application level - for example, to enforce semantic integrity on data inputs, by, for example, raising questions such as: is this a valid username? They may also provide quality assurance within and between parts of a composite solution. Used this way a resource validation constraint can ensure a developer has correctly implemented the specification. Validation constraints can be applied during runtime if necessary or for performance can be applied only during testing and deployment integrity checking. [Obviously, the basic properties of our OS of (mostly) being validated and verified (e.g. model checking) have have been copied from the webpage Overview. Besides this, many possibilities exist to handle such system constraints.]",
"Perhaps surprisingly, by allowing constraint to be applied in a decoupled manner, the overall integrity of an ROC information system is actually increased relative to that possible in the constraint-first world of traditional type-focused programming. [Not surprisingly, that statement is just only nonsense. We only refer to the basic property of our OS of (mostly) being proof-carrying and also to constrained types. In addition, all other advantages are thrown away with that approach for example type-safety.]",
"In NetKernel the computation of resources can be accomplished in a wide choice of languages. [So it is multilingual and multiparadigmatic indeed. But the original DEXTER and NetKernel were not.]",
"No matter which language is chosen, the purpose of all computation is to create new resources and their representations. As you can see from these three examples, the result of each computation is identified by the URI and can be used just as any other resource within NetKernel. [See also the document titled "Reification and Reflection in C++: An Operating System Perspective" of the Choices and its succesor μChoices.]",
"Transreptors and fundamental resource models are coded in Java [...] In the Construct phase developers will work with the NetKernel Foundation API (NKF). [We note that the NetKernel is bound to the Java technology and provides an own framework.]",
"For example, the address ffcpl:/index.html could be linked to a static resource located at ffcpl:/src/index.html [...] [We have already mentioned the VOS in a comment made to a quote above, so we refer directly to the example given in its description, which is exactly the same. And while already there, also take a look at the section Object Type Definitions.]",
"[...] a functional unit of a system can be validated using test resources. Validation constraints can provide proof of completion and also can later be used to provide long-term system quality assurance. [See the comment made to a related quote before.]",
"In the discussion so far, the broad theme of resource-oriented computing is the transition from static physically linked code to dynamic logically linked information processes. [...] [While program to data is reification, data to program is reflection, and therefore we are talking about reflective computing, as also described with our Evoos in The Proposal.]",
"However, and counter-intuitively, it is consistently found that ROC actually offers significant performance advantages. [See once again KLOS and SPACE as well as our integration of the fields of Kernel-Less Operating Systems (KLOSs) with reflective systems and Cognitive Agent Systems (CASs).]",
"Resource requests are issued to the kernel which, acting as an intermediary, resolves the address to a physical accessor endpoint and then invokes the accessor. When the accessor completes its task, it returns the physical resource representation to the kernel which forwards it to the initial requestor. Since requests are not coupled to the physical execution of the code in the endpoints, the kernel is free to manage the assignment of each computational task to a low-level thread of execution. [Taken the last quotes together we get once again the basic property of our OS of (mostly) being kernel-less reflective/fractal/holonic and due to the significance, originality and uniqueness of these OS property and its relation with The Proposal we have an evidence that show a causal link with our OS and a significant part of the characteristic expression of the OS in particular and the works of art created by C.S. in general and characterizes them as ontologic works.]",
"And, since the kernel is mediating all computation, it can use its global knowledge of the system to manage any individual process to ensure optimum efficiency of the whole software system. [This functionality was also not included in the original DEXTER and NetKernel, but in our OS, specifically in its integration of KLOSs, like KLOS and SPACE, and reflective systems, like the reflective and distributed operating system Apertos (Muse) and the Cognac system based on Apertos. We also have here a function of our OntoBot software component, which has global knowledge of our OS.]",
"[...] the logical system is inherently asynchronous. A thread must perform the computation but the kernel is free to use an optimal strategy to determine which thread to use and whether to use asynchronous or synchronous dispatch on the thread. [See the section Integrating Architecture of the webpage Overview once again. At this point, we get another evidence that provide the causal link with our OS.]",
"This flexibility allows for an optimization that minimizes computationally wasteful context switching in the CPU [...] [Avoiding context switching is one of the main focuses of KLOS and SPACE as well as the related part of our OS, specifically the OntoL4 and OntoCore software components. Furthermore, asynchronous system calls that avoid context switching are also exception-less system calls.]",
"An additional performance payback of logical indirection is in the scaling and optimal utilization of SMP or multi-core processor architectures. [...] In this case, ROC enables load balancing to be brought down to the finest granularity of software and the execution of physical CPU threads. [This was also no concern of the original DEXTER and NetKernel. See once again Apertos (Muse).]",
"Finally, the complexity and system-integrity challenges of developing thread-safe code is removed from the developer. For example, a new low-level piece of code and its associated OO library will by default be marked as UNSAFE_FOR_CONCURRENT_USE. The system architect integrating the new functionality can be confident that the system is safe to use immediately, knowing that the new code will never be scheduled concurrently. [actor-based or concurrent programming can also be found in the description of Apertos (Muse).]",
"After review and testing, this declarative constraint can be removed and the kernel will seamlessly parallelize and optimize the execution of the code. [See the chapter 7 A Kernel-less O/S for Parallel O/S Research of the document titled "Implementing Operating Systems without Kernels" of SPACE.]",
"To visualize the relationship, think of ROC as a logical level resting on top of a physical OO foundation. [...] Computations must ultimately be performed at the physical level, so it is easy to see that a logical model such as ROC must be implemented with, and must run on, a physical platform. In the case of NetKernel, the physical kernel is implemented in Java. [As we explained multiple times before, for example in a related comment made to a quote above, we have also substituted the whole brittle system stack consisting of an operating system, the Java Virtual Machine (JVM), and an additional VM on top of the JVM like that plagiarism, as well as a web browser in a simliar way with our OS as part of its truly holistic concept and architecture and even optimized the operating system and the VMs with for example our original and unique exception-less system call for asynchronous operations, the presentation systems with for example multimodal user interfaces, and so on. Furthermore, we can see here our OSA once again with the OntoL4, OntoCore, and OntoBot components. What is presented in the quoted white paper was definitely not the original DEXTER and NetKernel.]",
"Another way to visualize the relationship is to see that ROC is an independent, logical computing model. ROC is not an extension of OO nor is it a framework for OO. [What should we say? NetKernel is a copy of the related part of our Ontologic Computing (OC) model or paradigm, OSA, and OS.]",
"Even on a small scale, changes to an OO system, at a minimum, require a recompile, test, deploy, restart, and application state reload. [From the general point of view, this statement is also wrong because even the Virtual Machine (VM) of NetKernel is implemented as an OO system.]",
"With ROC information is abstract and typeless. In fact, information, operations and transformation and all aspects of a program's structure and rules are logically related. [First of all, our Evoos and OS have these properties as well. Somehow the development history of this third variant of NetKernel is not plausible anymore, because there is no conclusive development path from an XML processing engine to the NetKernel respectively the related parts of our OS. That story about the history has been fabricated much later.]",
"Note that ROC is not an example of a model being used to generate code, which would still result in mountains of brittle code, instead ROC is a logical model that is executed in real-time on top of a physical computing level. [The same holds for our OntoBot despite its foundation is able to generated code as well. But true experts will scratch their heads now about the description of a logical system that is inherently asynchronous and is executed in real-time. Together with that other nonsense we have here the proof that the whitle paper was written for marketing purposes, which tries convulsively and illegally but unsuccessfully to present its former XML processing engine NetKernel as our OS.]", and
"The model resides in a logical computing level fully divorced from the physical computing level. [As we said, our OS is based on the integration of kernel-less reflective operating systems, Multi-Agent Systems (MASs), and Cognitive Agent Systems (CASs), and therefore includes all features of ROC since its start with our reflective and cognitive Evolutionary operating system (Evoos) since the end of 1999 when those fraudsters learned to spell X-M-L.]".

With that white paper it stole (more) the logics and reflection of ontologics while with the two talks it stole (more) the ontology of our ontologic system.
In this respect, we would like to recall that we have put all the scientific and technologic aspects into the realization of our artistic aspects, which was self-created by C.S. in extensive parts as well and also has 1:1 reflections between the scientific and technologic aspects and the artistic aspects also based on a language symbiosis, so that they are covered somehow by the copyright protection of the artistic aspects as well, or said in other words, aspects cannot be used in science and technology without reproducing or performing our works of art.

"An object is a fundamental entity in Muse. All resources in Muse are abstracted as objects. There are no distinctions between processes and files, nor between active objects and passive objects. Interaction between objects is accomplished by message passing."
"Reflection essentially is a mechanism by which a program code or application becomes 'self-aware', checks its progress and can change itself or its behaviour [6 [Software Fault Tolerance, Reflection and the Ada Programming Language]]. This change can occur by changing data structures, the program code itself, or sometimes even the semantics of the language it[ i]s written in. To facilitate this, the application or program code has to have knowledge about the data structures, language semantics, etc. The process by which this information is provided to it is called 'Reification'. [...] The Reflection model consists of a base-level (which is the application code), and one or more meta-level forming a structure called Reflective tower. The code in the meta-level is responsible to intercept the necessary calls from or to the base level, analyse the reified information and affect any change if required.", [An Application Adaptive Generic Module-based Reflective Framework for Real-time Operating Systems]. See also"μChoices: An Object-Oriented Multimedia Operating System" and of course The Proposal once again

In the following we quote the content of its website:
"The Uniform Resource Engine: the power behind the Resource Oriented Computing revolution [The term Uniform Resource Engine is only correct in relation with the Uniform Resource Identifier but not with resources or information. Furthermore, there is not revolution at all, as shown above, but mereley a retrograde development that adapted a reflective operating system for a reflective Virtual Machine (VM), which is put on top of an operating system.]",
"Dig into the details of the science breakthroughs at the heart of Resource Oriented Computing", [We are very sorry to say (not really) that there is neither a revolution nor a science breakthrough to find here. But they can be found as well as the hearts at our Ontologic System OntoLinux.]",
"The Resource Engine Reinvented [] One of the pillars of Web architecture is the resource engine inside the Web browser. [...] Without this piece of intelligence, the Web is just a global jumble of dumb endpoints. [Pillars can be found in the logo of the C.S. GmbH. Furthermore, there is no intelligence in a simple data processor.]",
"So we freed the browser-based resource engine from its origins in publishing and hypermedia and turned it into a full-fledged distributed, highly-scalable computing engine. We created a resource engine as a standalone system with hundreds of modular features. [So what now, distributed computing engine or a standalone resource engine? We are very sure that it was only a standalone system and the distributed has been copied from the website of our OS OntoLinux. At this point keep we would like to already give the information that it is based on only the client-server architecture.],
"Resource-Oriented Computing with NetKernel: Taking REST Ideas to the Next Level [This is the title and subtitle of a book. Most interesting for us is the fact that its NetKernel is bound to the software architecture style called Web-Oriented Architecture (WOA) based on Service-Oriented Architecture (SOA), Web Services (WSs), and Representational State Transfer (REST), and also Simple Object Access Protocol (SOAP) and hence client-server architecture with stateless communication, and its very simple XML based Declarative Process Markup Language (DPML) and XML Recursion Language (XRL). One of the founders of that company said himself that they "sometimes describe NetKernel as a REST microkernel", as already document in a quote of the introductory webpage above. We have distanced us from that stateless communication of the Web, because we think it is a no-go, specifically for further developments and inventions related to a global and even a universal computing system. At this point we would like to give the additional information that the Resource Description Framework (RDF) was added to WOA after 2006, as far as we can see around 2008, and a web resource is not a physical item but merely the .]",
"NetKernel provides a highly scalable infrastructure platform for microservices. [This is statement is relative and we would be cautious with such a claim, because it is shifting complexity around. Our OS does not suffer from such problems due to its advanced idea, concept, design, and much more.]",
"The unique design of NetKernel eliminates the complexity, code-bloat and operational overhead commonly associated with enterprise-class frameworks, API management and middleware solutions such as distributed messaging or enterprise service bus. [We already have proven that its design is merely and basically an adaption of a reflective operating system for a reflective Virtual Machine (VM) on top of a VM of a programming language with rudimentary features related to introspection and reflection, and at the top of a completely bloated system stack. See also the chapter 8 Summary of the document titled "Implementing Operating Systems without Kernels" of the SPACE.]",
"In this context of web-scale service architectures, NetKernel is an ideal development and operations platform. [NetKernel is a platform for WSs and not and operating system and surely not an Ontology-Oriented (OO 2) computing system or even an Ontologic Computing (OC) system or simply an Ontologic System (OS).]",
"Enterprise architects can push through ambitious designs that rely on new levels of architectural integrity and clarity while working with significantly less project risk. [We would be cautious with such claims as well.]",
"Systems Administrators can analyze, roll out and fine tune entire complex distributed systems made from microservices; they can observe individual service work-loads and discover bottlenecks in real-time in order to reallocate resources for better performance. [In 1 sentence 3 keywords (fine tune, complex, and real-time) copied from the website of our OS OntoLinux to mislead the public.]",
"Developers can easily understand existing microservices and their environments to integrate them with new ones. [We would be cautious with such claims, too.]",
"We are motivated to get to the root causes of waste in information technology systems and to radically transform software economics. [If this would be true, thent that company would not put its VM on top of such a brittle system stack and sell old wine in new bottles.]",
"Through basic research we have discovered the way to step away from code and APIs and instead put information resources at the heart of evolvable architectures. [Since when is espionage called research? Also note heart once again and also evolvable architecture also taken from the website of our OS OntoLinux, specifically our Evolutionary operating system describted in The Proposal and integrated by our integrating Ontologic System Architecture of our OS.]",
"Over the years industry has discarded hundreds of billions of lines of code. Common sense alone would tell you there must be a better way to go about things? [But that company merely discarded even some more thousand lines of code on top that. We have also the next term copied from the website of our OS OntoLinux with common sense. Common Sense Computing (CSC) is referenced in the section Intelligent/Cognitive Agent of the webpage Links to Software, researched with the aid of the Roboverse, and mentioned on the webpage Ontologic Applications.]",
"Why Frameworks don't work [] Frameworks layer abstraction on top of abstraction leading to mountains of brittle, unmaintainable, unreadable code. Even Alan Kay, father of OO, says they don't work. [But as we said multiple times in the comments made before to quoted contents of the introduction and the white paper, they put its NetKernel VM on top of the Java Virtual Machine (JVM) and a web browser that are put on top of an operating system as part of a brittle system stack comprising to simulate some few operating system functions eventually.]",
"The Web is an Evolvable Architecture [] The Web has never been thrown away but has always evolved. The Web must be doing something different? The Web's process is two step: resolve-execute. What can we learn from this? [We do not understand what it wants to tell us. But what we do know is that this comparison is nonsense because hardware and software were not thrown away but have always evolved as well.]",
"Bring the Web's concepts Inside [] REST stops at the doorstep. We thought, let's take the two step resolve-execute process inside and step away from the APIs. Suddenly our systems demonstrate the same evolvable architecture as the web. [In addition, an image of a fractal structure is shown in correspondence to the basic porperty of our OS of (mostly) being kernel-less reflective/fractal/holonic. But there is a little problem with this statement because its book has the subtitle ]",
"Even though we were not motivated by technology, it turns out, counter-intuitively, that taking two-steps leads to higher performance! [This includes our slogan Two steps ahead, that we were 2006, for sure.]",
"And... the web is just the start. The destination is Resource Oriented Computing. [Totally wrong, obviously, because the web reached already its end and the destination is Ontology-Oriented (OO 2) computing and Ontologic Computing (OC), and a whole New Reality (NR) with a new universe called Ontologic uniVerse (OV), for sure.]",
"As a pioneer of next generation software infrastructure technology and products [...] [We have the impression that we do not have here a pioneer but a brain-less chicken that did not know where to run to.]",
"NetKernel has an inherent ability to integrate existing technologies in unique, creative, and exciting new ways. [We think that we have proven with this investigation where its true profession lies.]",
"If you share our vision of advanced software infrastructure and an integrated approach to creating business value, please contact us to discuss opportunities. [What should we say? Those fraudsters spied on us, bend their XML processing engine to an essential part of our OS and even claim to be visionary, that by the way reflects the slogon of our truly unique, creative, and exciting OntoLab, The Lab of Visions. When we contact them then only to discuss the stopping of that mess and closing that company through our legal team and potentially a prosecutor.]",
"1060 Research is proud to have Hewlett-Packard Company as a founding investor. [We come back to this information in a comment made to a quote below.]",
"NetKernel was started at Hewlett-Packard Labs in 1999. It was conceived [...] as a general purpose XML operating environment that could address the needs of the exploding interest in XML dialects for intra-industry XML messaging. NetKernel was originally called Dexter which stands for Declarative XML Transform Engine. Its emphasis on a declarative approach to manipulating XML has remained strong throughout the life of the product. [See also the introductory webpage quoted above.]",
"In early 2002 HP rethought it's software strategy. We can't discuss the details, but [...] the leader of HP Lab's XML research program, negotiated with HP to acquire the rights to the project and established 1060 Research with [...] a member of the HP Labs team. [What were the reasons that Hewlett-Packard Labs (HPL) did not want to continue the work on DEXTER? And what were the two founders of that company knowing but not telling HPL at that time? It is not comprehensible that HPL invested in DEXTER but was not interested in what DEXTER became with NetKernel. Maybe closer to the truth is that the two founders wanted the XML engine but not what we did at first but then changed their mind while observing us. Or what? Furthermore, all those explanations given later do not fit with the story of viewing the World Wide Web (WWW) as a quantum mechanical system, the story about a result of a common research and development process that suddenly jumped from XML pipeline frameworks and an XML processing tool to a reflective Virtual Machine (VM), and its other marketing stories. Hence, those plagiarists have to answer two more questions: 1. How did they get from an XML processing engine to a reflective Virtual Machine, which is based on reflective operating systems, like for example Apertos (Muse) and also μChoices"? 2. Why have they hidden these facts about the reflective properties and instead used totally unusual terms and explanations, and presented that white paper and all that other blah blah blah? We have given the answers already.]",
"1060 Research has refined and fully implemented the original concepts. These are now realised in the 1060 Research NetKernel architecture which has gone way beyond the original ideas, and now provides a general model for scalable and adaptive software development. [Even if it is becoming boring, but we would like to recall that the fields of metaprogramming and reflective computing in general and reflective operating systems and reflective virtual machines in particular are not new.]",
"A Hewlett Packard Research Report presents the Dexter Project, the project which seeded NetKernel. [The given link to the report HPL-2004-23 is dated "3/6/2004". At that time HPL was still speaking about DEXTER. This means that NetKernel was not started in 1999, which was only claimed because we presented The Proposal the first time in 1999 and is also falsified by the very clear explanation given in the introduction quoted above: "Our first experiments were to prototype XML pipeline frameworks." That trick does not work, because there are address spaces respectively metaspaces in NetKernel, that did not exist in DEXTER.]",
"NetKernel delivers a high performance, emergent and scalable platform to develop, integrate and operate complex service and data architectures. [Do not confuse the term high performance with High Performance Computing (HPC) because micro Web Services are not HPC. Furthermore, the term emergent was also copied from the website of our OS OntoLinux to mislead the public, as can be seen with the section Softbionics and Artificial Intelligence 3 on its webpage Terms of the 21st Century and also the basic property of our OS of (mostly) being self-organizing.]",
"By taking Micro-Services to the ultimate level, NetKernel delivers huge technical breakthroughs for development, operations and architecture engineering... [As we said before, both reflective computing and caching are very old stuff.]",
"Request Visualizer [] Time machine debugger/profiler. Capture and visually inspect every aspect of the two-step resolve/execute ROC process. Real-time with no overhead. [This was taken from the OntoScope software component of our OSA but was not included in DEXTER.]",
"Visual functional programming [] Simple drag and drop composition of existing tools to do functional programming without having to think about functional process flow. [This was taken from the OntoScope and OntoBlender software components of our OSA but was not included in DEXTER.]",
"Sandboxed design to provide fool-proof safe development environment even for end-users. [This is related to our operating systems and was not included in DEXTER.]",
"Space Explorer [] Visual exploration of architecture. Detailed architecture navigation featuring design discovery, relationship inspection, real time system state reporting, real time service description. Space Explorer: a unique tool for oversight of evolvable architecture. [This was taken from the OntoScope software component of our OSA but was not included in DEXTER.]",
"NetKernel's unique cache is multi-dimensional, contextually aware, dynamic, self managed. [The term multi-dimensional was copied from the website of our OS OntoLinux to mislead the public and most potentially the same holds for the terms contextual aware and self managed, the latter reflecting the basic property of our OS of (mostly) being self-organizing.]",
"Engineering Components [] Take control and balance the operational system-engineering levers. Tune with realtime feedback. [Do not confuse this with Computer Aided technologies (CAx) and Total Quality Management (TQM) listed in the section basic property of the webpage Overview.]",
"NetKernel implements the Resource Oriented Computing abstraction providing a Uniform Resource Engine. [It merely uses URIs, which does not make it a uniform resource engine at all. Furthermore, we have shown that said abstraction is the same as of reflective operating systems.]",
"Evolvable Architecture [] The NetKernel platform allows you to design for the enterprise, building emergently complex evolvable architectures through combination and recombination of a small set of simple components. [Obviously, we have here once again our reflective and cogntive Evolutionary operating system (Evoos) based on Evolutionary Computing (EC), such as for example Evolution Strategy (ES) (see also the document titled "Evolutionsbionik Fallbeispiel"), Genetic Algorithm (GA) and Genetic Programming (GP), as can be seen with the terms evolvable and emergently but even better with the additional terms combination and recombination which also suggest a genetic process (see once again The Proposal). This provides us an evidence that shows a causal link with our original and unique works of art.]",
"Interoperability [] To reduce the overhead associated with frameworks and libraries in increasingly complex IT systems, NetKernel's unique architecture provides you with a uniform approach to define, integrate and manipulate: [Sadly to say, an essential part of its NetKernel is merely an essential part of our original and unique Evoos, which is copyrighted at least when viewed as a cybernetic reflection, self-image, or self-portrait of C.S..]",
"Simplicity As an industry first, NetKernel separates information resources from code. This innovative approach allows you to simplify everywhere: [Sadly to say, but this not true or even nonsense. Our Evoos includes the working of a brain realized with a reflective operating system, which separates resources from code as well, obviously. Ooops, Gotcha!!! We also do not think that thoughts or the cognitive act of reflecting are physical?]",
"Versatility [] NetKernel can be configured as an Application Server, an Embedded Resource Engine in a legacy Java stack, as a tiny micro-server platform, as a massively distributed Cloud Platform... [As we know from its white paper NetKernel is not a microkernel but a Virtual Machine (VM), which is running on top of the Jave Runtime Environment (JRE) or Java Virtual Machine (JVM), which again is running on top of a common operating system, and therefore is not so tiny, as suggested here to mislead the public deliberately, but up to 10 times larger in comparison with our system stacks. In fact, making such claims is an act of unfair business practice, which is illegal. But there is another point that makes us wonder. How on Earth become XML pipeline frameworks developed further to an XML processing engine a cloud computing platform? Furthermore, a massively distributed cloud computing platform is something different than a computing system based on the client-server architecture because the single cloud computing systems communicate with each other and provide together a single task here the operation of a single platform. Therefore, it must be something else, like for example a Peer-to-Peer (P2P) computing system or a cluster computing system, and therefore must be a utilization that has been copied from the website of our OS OntoLinux as well. Last but not least, take a look into the Abstract and chapter 2.9 Summary of the document titled "The Muse Object Architecture: A New Operating System Structuring Concept" to find out yourself that the flexibility and versatility truly came from a reflective operating system.]",
"At its heart, NetKernel consists of a pure-Java microkernel that embodies the ROC abstraction, combined with a small core set of libraries, to provide a minimal ROC system. [See the comment made to the quote before and keep in mind that our OS has a Zero Ontology and does not consist of a specific programming language conceptually. This also reminds us of the OntoCore software component.]",
"The system is modular and is extensible [...] [See the section Integrating Architecture of the webpage Overview of the website of our OS OntoLinux.]",
"Modules are hot-swapable allowing for zero-downtime evolution of the software configuration. [Evolution of a software configuration at runtime means what? Exactly, it must be a reflective evolutionary system and because this is our Evoos we got the next evidence that shows a causal link with our original and unique, iconic work of art.]",
"[...] the core platform is accompanied by a set of modules which provides a complete self-contained application server [...] []",
"Sophisticated semantics [...] []",
"NetKernel Protocol (NKP) is the low-level client-server infrastructure that enables a NetKernel solution to be be seamlessly distributed across the cloud. NKP allows ROC solutions to be coherent between servers. [In a related message publicated in its forum on the 23rd of July 2010 we got the addtional information: "The recently released NetKernel 4 incorporates the NetKernel Protocol - a network client-server protocol that enables NetKernel''s ROC abstraction to seamlessly span the cloud. In this in-the-brain, [one of the leading plagiarists] will introduce NetKernel from the perspective of the NK protocol and show how it goes beyond HTTP/REST and offers a new dimension in scalable, cacheable resource oriented solutions." So only client-server computing but not P2P computing, cluster computing, (massively) parallel computing, or anything else. See SPACE once again to see that it has been copied from our website and is another evidence that shows a causal link with our original and unique works of art.]",
"The NKP Loadbalancer is an engineering component that allows systems using NKP to balance the distributed cloud load profile in realtime. It is fault tolerant [...] [See once again the reflective, fault-tolerant, reliable, and distributed operating system Apertos (Muse) and also ANTS-EOS and The Dresden Real-Time Operating System listed in the section Exotic Operating System of the webpage Links to Software of the website of OntoLinux.]",
"The State Machine Runtime enables the creation and operation of hierarchical state machines of arbitrary sophistication. [We are sorry for being borring. But what has such a state machine runtime in common with an XML processing engine?]",
"It connects to a secure, encrypted repository providing robust, stable and proven modules. [The term proven modules reflects the basic property of our OS of (mostly) being validated and verified, which again provides as the next evidence that shows the causal link with our original and unique works of art.]",
"Resource Oriented Computing is an elegant and extremely simple abstraction. [] Self-consistent. The NetKernel platform actually relies upon the ROC foundation to deliver ROC. [] Scale invariant. The way one treats large scale systems is identical to that used at the lowest level relationship between individual software components. [] Simple without being simplistic. Every ROC solution comprises just six simple concepts but their uniform combination leads to emergent manageably-complex architectures. []",
"Address spaces are a logical construct providing the resolvable context for abstract resources. []",
"Resolution is the process of "searching" address spaces to find an endpoint that will accept the request. []",
"An endpoint is a physical level executable software function that has accepted responsibility for computing the state of a resource. []",
"Breakthroughs [] Everything is a resource: code, information, configuration. World's first "Uniform Computation Abstraction". [],
"Two-phase resolution/execute cycle allows huge engineering efficiencies [Ah, what ...? resoluton==reification/execute cycle with results==reflection, metaprogramming, reflective programming, Ontologic System?]",
"Systemic caching automatically discovers and optimises natural statistical distribution of resource state [self-organization, self-adaption]",
"Execution decoupled from requests allows computation to be load-balanced on multicore ensuring linear scaling [accessor and requestor are not decoupled]",
"Resolution allows architecture to evolve - system is completely decoupled not simply loosly coupled. [Ah, what ...? Evolutinary operating system, Ontologic System?]",
"Hot swappable - all code is replaceable in real-time. Including hot rollback of changes. [Ah, what ...? reflective system, transactional system, Ontologic System?]",
A world of new simplifying patterns that lie above imperative/OO code become available. [Ah, what ...? Ontology-Oriented (OO 2) programming, mulit-paradigmatic programming, Ontologic(-Oriented) (OO 3) programming, Ontologic Computing (OC)]",
"What makes us different? Our industry leading research into the foundations of software systems design; the expertise we gained by reinventing software from the ground up; [...] [We call our original and unique work of art titled Ontologic System an iconic work because it is the true leading source into the foundations of computing, hardware, and software since 2 decades. And as far as we can see, we have reinvented software from the ground with our Evoos based on a simple model of a brain and its working as well as reflection in the senses of cognition and operation, while its NetKernel sits on top of a brittle system stack with an operating system and the JRE or JVM.]",
"ROC allows code and architecture to be cleanly decoupled, enabling more powerful and elegant solutions to be realized. NetKernel may be deployed as a standalone application server, embedded in an existing Java container or used as the foundation for a cloud computing system. [Keep in mind that at least JRE 5.0 and a common operating system are required as parts of the brittle overall system stack which is up to 10 times larger than our system stacks and therefore is not useable for various cases, such as many Cyber-Physical Systems (CPS), Internet of Things (IoT), and Networked Embedded Systems (NES). Also keep in mind that using NetKernel as the foundation for a cloud computing system or another Distributed System (DS) might infringe our copyright and other rights. There is definitely not much legal space to move, if at all and not in the way as done by those fraudsters.]",
"Unix and REST are actually closely related. NetKernel is related to both. It adds some new generalisations, some of which are new conceptual leaps. [First of all, NetKernel does not add some new generalizations and conceptual leaps. Either they came from reflective systems or from our Evoos and OS. That bold claim is also linked with a comparison of Unix, REST, and ROC in a chapter of the NetKernel News Volume 2 Issue 49, which we quoted separately in the subsequent chapter below for better oversight.]",
"The Resource Oriented Computing abstraction provides several very simple concepts - spaces, resources, endpoints, requests, which are used to compose the architecture of an application. [{what are the equivalents of reflective operating systems, e.g. Apertos and Cognac based on Apertos, RbCL, etc.?}]",
"Requests are processed by service endpoints dynamically discovered within spaces. Endpoints can issue their own requests which themselves discover their processing endpoints. [{what are the equivalents of reflective operating systems, e.g. Apertos and Cognac based on Apertos?}]",
"Dynamic discovery of endpoints for all requests enables architectural designs with flexibility not possible with object-oriented approaches [Ah, what ...? Take a look at the reflective, object-oriented distributed operating system Apertos with its metaspaces and object spaces. After this, imagine an object-oriented version of our reflective and cognitive Evoos. And then think about our Ontology-Oriented (OO 2) and Ontologic(-Oriented) (OO 3) programming paradigms and finally about our Ontologic Computing (OC) paradigm. Last but not least, the NetKernel is itself an Object-Oriented (OO 1) system implemented with the OO 1 programming language Java.]",
"In fact, NetKernel systems are as flexible and malleable as the World Wide Web. [The same old for our much older Evoos and our OS integrating Evoos.]",
"Each endpoint can be considered an object-oriented container and the spaces "containers of containers". These endpoint containers can host your existing code and then ROC can provide a new level of abstraction to your enterprise software, a new dimension in which you can step up from the low-level objects and APIs of traditional coding. [This explanation means at least that we have a metalevel and a base level, objects, and so on. Somehow we have an essential element of Apertos (Muse) once again. See also chapter 4.5 Relation to Apertos Meta-space of the document titled "Unification of Compile-time and Run-time Metaobject Protocols" of the Cognac system based on Apertos. "Apertos has a hierarchal meta-level architecture. A set of metaobjects is called a meta-space and the metaspace is managed by a special object called a reflector in Apertos."]",
"Fundamentally NetKernel and ROC offer a new way to do software. [As we said our much older Evoos has all the foundational properties as well. ]",
"New software with new higher-order qualities... [Compare this phrase with the basic property Total Quality Management (TQM).]",
"[...] generational stability of information and structure [Obviously, this is related to an evolutionary system as well.]",
"Dynamic type adaptation and pipelined conversion discovery [As we already said when investigating its white paper, there must be a typing system and a casting system. We use topic maps, ontologies, ontologics, and so on as part of our Ontology-Oriented (OO 2) and Ontologic(-Oriented) (OO 3) programming paradigms and Ontologic Computing (OC) paradigm for realizing and handling them and much more.]",
"Scale your solution - add more cores and see your system scale linearly [With this list point a link is provided to the webpage titled "Linear Scaling [] the power of a Uniform Resource Engine" quoted separately in the next chapter below for better oversight. At this point, we can already say that the demonstration of performance already provides more detailed evidence that proves the supiriority of our original and unique, iconic solutions once again even by such a fraudulent company.]",
"Faster development - less code, less coupling, more reuse. [First of all, loosly coupling does not mean less coupling. Furthermore, we would like to repeat once again our recommendation to be very cautious with all those claims of the company's marketing. In the last 4 decades of software technology much has been tried and developed, and not everything was for the dust bin.]",
"Hot deployment and transactional rollback [These are common features of newer operating systems also included in our OS.]",
"Legacy coexistence - new features never need to disturb existing functionality allowing for progressive evolutionary solutions. [These are common features of newer operating systems and their derivaties also included in our OS. Also note the term evolutionary solutions, which was copied from the website of our OS OntoLinux to mislead the public and to reflect our original and unique works of art once again.]",
"[...] our most compelling evidence is the World Wide Web; the most successful software system ever created. The Web succeeds because of its fundamental economic property: All information systems are compelled to change. [Then you can already guess what will happen with our replacement of the Web with our Ontologic uniVerse (OntoVerse or OV) which integrates the physical and the virtual worlds.]",
"You might not have realized it but the Web is an ROC system. [...] the Web is an instance of just one basic ROC pattern using a single ROC address space. [You might not have realized it but an ROC system is an Ontologic System. The ROC paradigm is just one more plagiarism of our Evoos and OS.]",
"[...] augment and evolve [...] [One more of the usual speech act steelings from the website of our OS OntoLinux.]",
"NetKernel is a generalization of the ideas behind the Web [...] [No NetKernel is not such a generalization. Also, as we said in a comment to a quote before the Web has been replaced by C.S. with our OntoVerse.]",
"[...] the new dimensions offered by ROC. [This was copied from our designation n-dimensional Operating System (nDOS) used in relation with our OS. See also the Clarification of the 4th of September 2018 for some of these dimensions.]",
"One of the beauties of ROC is that it allows architects to focus on what they do best - designing the structure of information systems. Because code is separate from architecture, the high-level design can be refined without concern for code details and if code is required, that development can be left to the coding experts - using which ever language they prefer. [One of the beauties of our original and unique OS is that it also supports the coding experts with the OntoBlender and even allows automatic programming based on Artificial Intelligence (AI) and Natural Multimodal Processing (NMP), specifically Natural Language Processing (NPL), as part of its truly holistic approach and architecture.]",
"Take the red pill and you will certainly see the world with new eyes. [Obviously, that reference of the Matrix saga should also reference our OntoVerse.]",
"How much you gain from this depends on what motivates you. Is your motivation to solve problems or to write code? [Note that the phrase solve problems was also copied from the section Basic Properties of the webpage Overview of the website of OntoLinux. In sum, this permanent copying of the terms found on this webpage also constitutes an infringement of our copryright and other rights, because the public is deliberately misled about the true origin of our works of art.]",
"NetKernel powers very large scale telecoms systems, very large online-retail web-properties, critical internet infrastructure such as purl.org, commercial publishing platforms etc.. [This statement is misleading because it is not said for what NetKernel is really utilized. In this relation, we also have to note that all the owners and operators of these very large systems have to migrate to our OS sooner or later anyway. By the way, PURL is the acronym for Permanent or Persistent Uniform Resource Locator (PURL).]",
"It's scale invariant nature means it can solve small workgroup problems, and yet seamlessly grow and scale to high-end architectural engineering systems. [The most important point of this statement are the phrases solve problems and architectural engineering systems which reflect the basic properties Computer Aided technologies (CAx) and Problem Solving Environment (PSE), and the section Integrating Architecture.]",
"NetKernel is ideally suited to information integration. Examples include HTTP (REST/WS), JMS, email, SMS and relational, xmldb, and semantic databases. [Specifically the latter feature related to semantic databases in combination with a reflective system is the next evidence that shows a causal link with our original and unique OS emphasizing the infringements of our rights.]",
"XML/RDF/xxx pipeline processes [See the comment made to the quote before.]",
"Perhaps one of the best examples of the use of NetKernel, is... NetKernel. All of the tools, services and systems of the NetKernel platform are themselves ROC applications dynamically composed into the framework you're using now. [As we said, NetKernel is not an XML processing engine anymore but has become a reflective system, which immitates or reproduces essential parts of our protected works of art.]",
"NetKernel and ROC is the result of over 10 years of hard-core computer science research, painstaking care over implementation and real-world production experience (NetKernel has been in production for mission critical customers, such as telecoms, for six years). [We already said that spying is not researching and developing, and add that copying is not caring. Also, it is not clear for what NetKernel is utilized by its mission critical customers. Maybe they should really think again if utilizing NetKernel is such a good idea.]",
"The foundational ideas were conceived back in 1999 when the founders of 1060 Research were in HP Labs. [Let us laugh around a little. In fact, one of its founder clearly explained in the introduction quoted as the first document above that both DEXTER and NetKernel were completely different things and definitely not our reflective and cognitive Evolutionary operating system (Evoos) described in The Proposal, namely at first an XML pipeline engine, as proven with the quote "Our first experiments were to prototype XML pipeline frameworks.", that was replaced by an XML processing engine later, and since the publication of our OS at the end of October 2006 it is bend to and described as our OS in illegal ways.]",
"You can find it powering Enterprise Service Bus architectures, the Permanent URL System, information gathering systems embedded deeply in telecom networks or powering web sites and web services. [Aha, not so mission critical as claimed before.]",
"NetKernel Standard Edition is the Open Source edition. [We consider this a breach of the copyright because only the original creator is allowed to decide if and how a work of art is reproduced and performed. Fact is, C.S. has not allowed to reproduce the Evoos and the OS under an open source license at all.]",
"[...] we had to write our own public license to meet our very specific intentions: we want you to be free to choose your own open source license for your own modules and not, as is often the case, have that choice imposed by the platform from below. [And we want that it stops that mess and removes the open source version as well as the illegal License Model (LM) of our Intellectual Properties (IPs) immediately.]",
"[...] NetKernel's ROC abstraction [...] [As far as we can see there exists no NetKernel's ROC abstraction at all but only prior art that has been copied in legal but also in illegal ways.]",
"Can I use the 1060 NetKernel for free? [] Yes, provided the applications and services you execute with the kernel are open sourced under an OSI certified license. [No, proper licensing is required for each reproduction of our Ontologic System and each performance of our Ontologic Applications and Ontologic Services (OAOS) in whole or in part.]",
"You must also display clear end-user visible attribution that your system is Powered By NetKernel. [No, proper licensing of our original and unqiue works of art does not require this.]",
"The 1060 Public License is carefully constructed to mandate that applications and services developed on top of NetKernel must also be open-sourced. [No, proper licensing is required for each reproduction of our Ontologic System and each performance of our Ontologic Applications and Ontologic Services (OAOS) in whole or in part.]",
"We require that remotely accessible code, or software as service as it is sometimes called, is equivalent to a full redistribution and so the usual distribution terms apply. Therefore you may freely use the 1060 NetKernel if you release the source code to your service - if you do not wish to release your source then you must obtain a closed license. [No, proper licensing is required for each reproduction of our Ontologic System and each performance of our Ontologic Applications and Ontologic Services (OAOS) in whole or in part. Also note that how it views remotely accessible code as Software as a Service (SaaS).]",
"No, you are free to use the 1060 NetKernel on as many machines as you wish at a single physical site. However if you require support you may need to purchase support licenses for each installation - please see the support packages for details. [No]", and
"For commercial reasons we must reserve the right to apply for patents in NetKernel technologies. Such patents as are granted will be used for defensive purposes both for ourselves and the broader open source community. We will create an open patent pool that will be free to license for legitimate open source projects. [Do not fall prey to the illusion that any part of our original and unique works of art titled Evolutionary operating system, Ontologic System and Ontoscope, and all created by C.S. can be patented legally.]".

The next quotes are from the webpage Linear Scaling [] the power of a Uniform Resource Engine of its website:
"Presented in this report are test results that demonstrate the NetKernel ROC architecture scaling linearly with CPU cores. This is achieved without requiring any use or knowledge of asynchronous threaded programming techniques. It can be seen that software on NetKernel is load-balanced across CPU-cores in the same way that a Web application can be load-balanced across an array of servers. [Our OS has these properties as well as can be seen easily with its basic properties of (mostly) being self-adaptive and self-organizing.]",
"Scaling Concurrent Requests issues an increasing number of concurrent root requests which invoke several thousand synchronous sub-requests that invoke an endpoint that performs a small computational task and returns a non-cacheable representation. The test named "Scaling Kernel Threads" issues 2000 asynchronous requests that invoke the test endpoint. The asynchronous load is executed on increasing numbers of kernel threads. [This is related to the content of the section Integrating Architecture of the weboage Overview and also with systems like the TUNES project listed in the section Exotic Operating System of the webpage Links to Software of the website of our OS OntoLinux. In addition, it addresses foundational features of the reflective and distributed operating system Apertos (Muse) once again, which we have developed further with our OS to provide the superior flexibility and higher performance.]",
"JVM Tuning [] This section demonstrates the impact of tuning the Java Runtime environment. [Obviously, the performance of the underlying Jave technology with its Jave Runtime Environment (JRE) or Java Virtual Machine (JVM) constitutes multiple technical and legal problems, which are the reason that we replaced Java as well and in the course of this the whole Internet and World Wide Web (WWW) with that stateless Hypertext Transfer Protocol (HTTP), Representational State Transfer (REST), and so on. NetKernel does not provide this technically with its client-server architecture and Web Services (WSs) or legally or both with its massively distributed cloud computing system.]",
"This suggests that using the NetKernel throttle with a concurrency of 8 and 8 kernel threads would lock the architecture at peak throughput and eliminate load dependent variability of the system performance. [Here we got concurrency and kernel threads, which leads us to the reflective and distributed operating system Apertos (Muse) once again.]",
"The 8-core [...] results are very close to the ideal. [The question in relation with this statement is what the marketing views as the ideal.]",
"Once concurrency fully utilizes the available cores, we see constant throughput and a linear rise in response time. These results show that the NetKernel architecture is linear. [Thank you very much for proving these superior properties and performances of our Evoos and OS.]", and
"These tests show that the NetKernel architecture provides a true linear scaling software solution for multi-core processing platforms without the need for thread or concurrent programming knowledge. Furthermore, these tests constitute a worst case scenario with no caching of resources. [See the comment made to the quote before.]",

The next quotes are from the NetKernel News Volume 2 Issue 49 publicated on the 14th of October 2011:
" Looking at "computer" in the broadest terms, we can therefore say that the majority of computers sold today use the "Unix Abstraction". It just goes to show that elegance and beauty will out. []",
"For the longest time we have said on our web site: "ROC combines the core ideas of Unix and REST into a new and general model for creating powerful software solutions." [We extended the core ideas of Unix and the World Wide Web (WWW), specifically the Hypertext Transfer Protocol (HTTP) and the Representational State Transfer (REST), in favour of advanced computing systems, specifically Fault-Tolerant, Reliable, and Trustworthy Distributed Systems (FTRTDSs) and High Performance and High Productivity Computing Systems (HP²CSs).]",
"When we first showed people NK back in the day, one of the ways I described it was as a "software operating system" - unfortunately back then I got responses like "you don't know what an operating system is - its an abstraction over physical hardware".
Today [...] we beg to differ: an operating system is a system that presents a self-consistent, uniform set of logical resources. Resources are in constant flux and an operating system must provide a highly efficient, consistent and sufficient approximation of their state.
I know Unix is an operating system. I hope this comparison goes some way to showing that NetKernel is itself a new type of operating system - one that stands on the shoulders of giants and extrapolates on from where Dennis Ritchie et al began 40 years ago. []",
"A resource can have one or more identifiers (grammars, mappings, rewrites) [At this point that company wants to jump on the rewriting logic comming with Maude and the CHemical Abstract Machine (CHAM), that are integrated in our OS.]",
"Unlimited representation models. State is embodied in object representations. [The point is that the binary stream, which is the only representation model of Unix and the WWW, matches the working of the underlying hardware.]",
"As much as is possible, state does not move, what we conceive of as "state transfer" is in fact a change of spacial context. Not moving state is very efficient. [Indeed, in Apertos we have migrating code but also a special type of object called reflector that manages a metaspace respectively spacial context. See also chapter 4.5 Relation to Apertos Meta-space of the document titled "Unification of Compile-time and Run-time Metaobject Protocols" of the Cognac system based on Apertos. "Apertos has a hierarchal meta-level architecture. A set of metaobjects is called a meta-space and the metaspace is managed by a special object called a reflector in Apertos." See also for example the chapter 3.3 Meta-level Context Management of the document titled "Kernel Structuring for Object-Oriented Operating Systems: The Apertos Approach". In the kernel-less, reflective language system RbCL we have "Level shifting, that is, switching the current name space of the system objects, can be efficiently implemented." described in chapter 3.5 Level Shifting by Level Managers of the document titled "Reflective Object-Oriented Concurrent Language without a Run-time Kernel".]",
"NetKernel has transreption, we can isomorphically transform state [(embodied in object representations)] into higher and higher order forms, when combined with caching this means we can constantly eliminate disorder (entropy) in the state of the system. [First of all, see for example chapter 4.2.1 Intermediate Representation of Method Code of the document titled "Unification of Compile-time and Run-time Metaobject Protocols" of the Cognac system based on Apertos, which is the successor of Muse. Furthermore, we use topic maps and ontologies to introduce for example types, structures, and models as part of metaspaces, semanitc spaces, and ontologic spaces, and to avoid all that ordering work and get safety and security, as well as trust for free, because we have order and trusted models already most of the time. While others were still thinking what to steal from us, we were already working on tuning that.]",
"All tools can be written to different heterogeneous representation models ([Application Programming Interfaces (]APIs[)]) - impedance matching transreptor chains are automatically discovered. [Everything that works automatically consums computing resources.]",
"Any number of logical address spaces. Spaces can have tree structured addressing models. But can model arbitrary sets of logical resources. Grammars allow identifiers to be mapped to structured set membership relations. Endpoints abstract away from physical level. [We refer once again to the document titled "The Muse Object Architecture: A New Operating System Structuring Concept", specifically its Abstract that says: These structuring concepts include layered structuring, hierarchical structuring, policy/mechanism separation, collective kernel structuring, object-based structuring, open operating system structuring, virtual machine structuring, and proxy structuring." We also said before that we use graphs describing for example topic maps, ontologies, and so on. The terms arbitrary sets and structured set membership relations were used instead of graphs and hypergraphs. We also have namespaces and even natural multimodalities.]",
"Spaces can be composed together to create architectures. Just as the Unix and ROC philosophy is for composable tools - so ROC takes this philosophy to the general conclusion: we can compose address spaces too. [See once again the document titled "The Muse Object Architecture: A New Operating System Structuring Concept", specifically the chapter 1 Introduction that says: "Reflection. To provide an open and self-advancing environment, Muse provides reflective computing that presents facilities for self-modifying an object with its environment and for inspecting the meta-computing environment of an object. In addition, to define meta-objects as objects, we introduce a meta-hierarchy composed of meta-spaces. Thus the relationship between an object and its meta-space is relative." As we said before we use graphs describing for example topic maps, ontologies, and so on. We also have name spaces and even natural multimodalities. Also note the term philosophy used in relation with ontology.]",
"Create simple well formed spaces containing well crafted simple tools and resources - compose them together to reveal emergently complex architectures. [A basic property of our OS is (mostly) being well-structured and -formed which has been stolen as well. In addition, note the term emergently complex architectures.]",
"Resolution is decentralized and delegated to address spaces (plural). Address spaces further delegate resolution to individual endpoints. Resources are always relative. Web's absolute model can be replicated with one monolithic address space as the relative context. [See once again the document titled "A Reflective Architecture for an Object-Oriented Distributed Operating System" and "The Muse Object Architecture: A New Operating System Structuring Concept", specifically the chapter 1 Introduction that says: "Reflection. To provide an open and self-advancing environment, Muse provides reflective computing that presents facilities for self-modifying an object with its environment and for inspecting the meta-computing environment of an object. In addition, to define meta-objects as objects, we introduce a meta-hierarchy composed of meta-spaces. Thus the relationship between an object and its meta-space is relative."]",
"All actions happen through one consistent component type "the endpoint". [...] Nobody cares what language endpoints are written in. [Meta-architecture]",
"Every endpoint is a symmetric server-client - it is always both an off-ramp and and on-ramp to the resource address space. []",
"Chained dependency model accumulation. Distributed state coherence. Virtual dependencies (golden thread pattern). [CHAM and Maude?]",
"In ROC there is more than one address space. NetKernel knows this and ensures consistency of caching in multiple-dimensions. []",
"Finds and tracks the systemic (multi-dimensional) thermodynamic Energy and Entropy minima. [But NetKernel is not a Caliber/Calibre. This was copied from our website of our OS as well, specifically in relation with the Softron and the Caliber/Calibre.]",
"When we first showed people NK back in the day, one of the ways I described it was as a "software operating system" - unfortunately back then I got responses like "you don't know what an operating system is - its an abstraction over physical hardware". [Exactly]",
"Today, [...], we beg to differ: an operating system is a system that presents a self-consistent, uniform set of logical resources. Resources are in constant flux and an operating system must provide a highly efficient, consistent and sufficient approximation of their state. [Okay, now give such a definition for a reflective operating system and for our reflective and cognitive Evolutionary operating system (Evoos), and then compare it with NetKernel. Oh, what a pity NetKernel is more or less a plagiarism of our Evoos.]", and
"I know Unix is an operating system. I hope this comparison goes some way to showing that NetKernel is itself a new type of operating system - one that stands on the shoulders of giants and extrapolates on from where Dennis Ritchie et al began 40 years ago. [Sorry, our Evoos was first, then came the DEXTER, then came our OS integrating Evoos, and then came that comparison of Unix and NetKernel.]".

Those fraudsters can tell their fairy tales to Santa Claus but not to a judge or us, as well as our fans and readers. Also, as newer the quoted materials are as more they are copied from our original materials.

See also chapter 4.5 Relation to Apertos Meta-space of the document titled "Unification of Compile-time and Run-time Metaobject Protocols" of the Cognac system based on Apertos. "Apertos has a hierarchal meta-level architecture. A set of metaobjects is called a meta-space and the metaspace is managed by a special object called a reflector in Apertos. Since Cognac is based on Apertos, the reflector which defines the interface to the meta-space for objects looks similar to the object cluster in Cognac. However, Apertos assumes that all objects are active, so that there is no direct invocation of passive objects." The reflector does the same ...

See for example chapter 4.2.1 Intermediate Representation of Method Code of the document titled "Unification of Compile-time and Run-time Metaobject Protocols" of the Cognac system based on Apertos, which is the successor of Muse.
See also the chapters 2 Related Work and 3.3 Kernel-less Operating System Services of the document titled "Implementing Operating Systems without Kernels" of the SPACE.
See also the chapters 2 Related Work, 3.3 Kernel-less Operating System Services, and 7 Conclusions of the document titled "Efficient Cross-domain Mechanisms for Building Kernel-less Operating Systems"of the SPACE.
See also the chapters 1 Introduction, 1.1 Operating System Performance, 1.2 Application-specific Operating Systems, 2.8 Fundamental Extensibility, 3 Related Work, and 6 Application-Specific Operating Systems in SPACE of the document titled "Building Fundamentally Extensible Application-Specific Operating Systems in SPACE" of the SPACE.

See also chapters 3.1.1 Reification "Reification is the process of making an implicit entity explicit. By reifying an entity, it can be accessed through function calls, replaced or otherwise manipulated.", 3.1.2 Self-representation "The Self-representation of a system is the reification of that system's static structure and dynamic behavior. For example, a communication subsystem can have a self-representation in the form of protocol stacks or graphs.", and 3.1.4 Reflection "In case of languages, a distinction between metacomputation and reflection is particularly important. Reflection is a special case of metacomputation" of the document titlte "Pi: A New Approach to Flexibility in System Software", which "uses a reflective architecture for flexibility. It utilizes a self-representation of a subsystem created using resource objects and contracts, which decide the subsystem's semantics."
See also the document titled "Object Orientation in Off++ [] A distributed adaptable 1μKernel". "The kernel interface is the set of interfaces implemented by resource containers and their respective resource units. Every object identifier is unique network-wide, providing the means for handling objects remotely. [...] Chains of responsibility [5] provide customizable per-application resource revocation mechanisms. [...] Both "processes" and the resources they need (e.g. address spaces) are modeled as resource unit objects. Resource implementors (e.g. address space managers) are also modeled as objects. [...] An execution context (termed "Shuttle" in Off++) is modeled as a container of identifiers (termed "properties" in Off++) for those objects or resources needed for that context to run. [...] Library code builds VM abstractions such as memory objects and address spaces using address translation facilities provided by the kernel."
"When implementing Apertos, the following is introduced: (1) MetaCore which is a metaobject which [again] has no metaspace of its own (it is the root of the metahierarchy) [and] can be regarded as a microkernel and the root of the meta-hierarchy. [] (2) Reflectors which represent the metacomputing defined by a metaspace (group of metaobjects).
μChoices adopt some of these ideas and use reflection to construct customisable operating system components [...].
[...] μChoices supports both declarative meta-protocols (client may choose between pre-defined implementation choices) and imperative meta-protocols (client can use scripts to implement their own algorithms).", [Oyvind Hanssen, FlexiNet - Extensible Kernel Investigation, 1996].

Another front line is the field of the so-called microservices.
In this respect, keep in mind once again that 1060 Research was talking about the XML processing engine DEXTER and "Software components are Micro-Web-Services"[15 [Service-Oriented Development on NetKernel - Patterns, Processes & Products to Reduce System Complexity, Web Services Edge 2005 East: CS-3, Cloud Computing Expo 2005]], but not about Java, the Unix way, or better said, Jave, the L4 way, Java, the micorkernel way, and Java, the kernel-less way, or being correct, the Ontologic System way.
From an online encyclopedia we got the following slightly confuse because fabricated explanation: ""Services are composed using Unix-like pipelines (the Web meets Unix = true loose-coupling). Services can call services (+multiple language run-times). Complex service-assemblies are abstracted behind simple URI interfaces. Any service, at any granularity, can be exposed." [A founder of 1060] described how a well-designed service platform "applies the underlying architectural principles of the Web and Web services together with Unix-like scheduling and pipelines to provide radical flexibility and improved simplicity by providing a platform to apply service-oriented architecture throughout your application environment".[16 [Service-Oriented Development on NetKernel - Patterns, Processes & Products to Reduce System Complexity, undated]] The design, which originated in a research project at Hewlett Packard Labs [called DEclarative Xml Transform Engine (DEXTER)], aims to make code less brittle and to make large-scale, complex software systems robust to change.[17 [Architecture and Design of an XML Application Platform, 2004] To make "Micro-Web-Services" work, one has to question and analyze the foundations of architectural styles (such as SOA) and the role of messaging between software components in order to arrive at a new general computing abstraction.[18 [Your Object Model Sucks, 2014]] In this case, one can think of resource-oriented computing (ROC) as a generalized form of the Web abstraction. If in the Unix abstraction "everything is a file", in ROC, everything is a "Micro-Web-Service". It can contain information, code or the results of computations so that a service can be either a consumer or producer in a symmetrical and evolving architecture. Microservices is a specialization of an implementation approach for service-oriented architectures (SOA) used to build flexible, independently deployable software systems.[19 [Microservices in Practice, Part 1: Reality Check and Service Design, 2017]]"
First of all, note the attempt to break away from micro-web-services over SOA and ROC to a general computing model. But obviously, ROC is not a generalized form of the Web abstraction, which was said to mislead the public about our Ontologic Web (OW), but merely a Web Service (WS)-oriented architecture in particular and a SOA in general.
Also note that the explanation "It can contain information [or data], code or the results of computations so that a service can be either a consumer or producer in a symmetrical and evolving architecture." should suggest that ROC is a computing model based on reification and reflection, as well as evolutionary principles, or simply said, our reflective and cognitive Evolutionary operating system (Evoos) described in The Proposal to mislead the public about our Ontologic Web (OW) another time.
Furthermore, if we are talking about operating systems in this relateion, then we are talking about a Distributed System (DS) based on a microkernel operating system or even a Kernel-Less Operating System (KLOS), but not a monolithic operating system like Unix. The latter proves once again that the true origin must be our OS.

A related clarification will show what microservices truly are, that Amazon has never used the term microservices and was not the source of inspiration at all but obviously our OS, and where our rights are infringed by other entities as well, such as Martin Fowler and James Lewis (yes, the design patterns and agile programming guys).
Some fraudsters have even tried to steal the part of our OS that is related to linguistics.

The microservice architecture and hence the naive ROC paradigm introduces additional complexity and new problems to deal with, such as network latency, message formats, load balancing and fault tolerance. We recognized and solved all of them with our OS already in 2006:

Obviously, we solved the problems already in 2006, which have not been recognized by those plagiarists at all.

See the chapters

of The Proposal.

In this view, Netkernel is a virus nested in the operating system with language symbiosis based on the resource and the pipeling.
Furthermore, 1060 Research clearifies itself in its comparison of Unix, the WWW, and NetKernel that "an operating system is a system that presents a self-consistent, uniform set of logical resources". As we already said in the comment made to this quote above, we added reification and reflection with the Evoos, which implies that obviously

The question is when this metamorphosis happened (see also its image showing butterflies publicated on its website) and the evidence is its white paper, where it was clearly said that the newer generation of NetKernel is based on reification viewed as computation, which eventually implies that it is based on reflection, metacomputing and reflective computing as well.

Chronology

The XML processing engine was

Defining an axiomatic system is an act of the fields of logics mimicking ontologics.
The resolution of an URI is not a reification and this:response is not a reflection, but the 2nd axiom given in the white paper the first time says "computation is reification".

The white paper is the first time that the company bend its NetKernel to a reflective system and to a superset of the operating system Unix respectively a large percentage of all operating systems.
But ROC or ROA is included in our reflective and cognitive Evolutionary operating system (Evoos) already since the end of 1999, which leads us back once again to its statement that "an operating system is a system that presents a self-consistent, uniform set of logical resources".
{no bending required?!} But if such a bending is legal then we are allowed to bend our reflective and cognitive Evolutionary operating system (Evoos) in the same way as well, which implies that ROC or ROA is included in our Evoos already since the end of 1999, which leads us back once again to its statement that "an operating system is a system that presents a self-consistent, uniform set of logical resources".

But eventually this is Ontologic Computing (OC) clearly described around 9 months before the publication of that white paper.

As we mentioned in relation with other plagiarisms, especially interesting is the observation that the scientists must have recognized that our Ontologic System comprises the features and provides the functionalities of the NetKernel as well.
This is emphasized by the fact that at least two more works related to Service-Oriented technologies (SOx) have added the basic property of our OS of (mostly) being reflective/fractal/holonic to their SOC 1.0 and SOP 1.0 in the year 2007:

with Resource-Oriented Computing (ROC) to see how the same serious criminal tricks are applied in relation with different solutions to steal essential parts of our iconic OS.

Even more curious and suspecious are the points that all three frauds

• technical foundation in NetKernel for the integration of the features and functionalitites of our Ontologic System missing in NetKernel nor
• plausible reason to copy and integrate said missing features and functionalitites,

A fourth related work is

Indeed, the SOC 1.0 plagiarists integrated AC and Multi-Agent System (MAS) around the year 2002, though the AC, Agent-Oriented Programming (AOP), and SOA plagiarists stole the SOC 2.0 around the end of the year 2005 and the beginning of the year 2006 and the SWWW plagiarist stole the AOP and the Semantic Web Services (SWS) around the year 2002.
But sadly to say, none of them had reflective computing, holonic computing, Ontology-Oriented (OO 2) programming, New Reality (NR), OntoVerse (OV), and holistic integrating OSA that integrates all in one.

But at least, another external entity has recognized and comfirmed that our iconic work of art titled Ontologic System and created by C.S. is original and unique.

The preliminary results and the results are that the company 1060 is

• is describing an essential part of our original and unique, iconic work of art titled Ontologic System (OS) and created by C.S., specifically our integration of
  • Algorithmic Information Theory (AIT),
  • reflective and holonic systems,
  • model-driven approaches (e.g. Unified Modeling Language (UML), Agent-based Unified Modeling Language (AUML), Executable Unified Modeling Language (xUML), and Model-Driven Architecture (MDA)),
  • Semantic (World Wide) Web (SWWW) standards and technologies, specifically
    • Resource Description Framework (RDF),
  • ontology-based programming,
  • Service-Oriented Architecture (SOA),
  • Service-Oriented Computing (SOC), and
  • molecular systems (see CHemical Abstract Machine (CHAM)),

  and

  • Peer-to-Peer (P2P) computing, grid computing, and cloud computing,
  • High Performance and High Productivity Computing Systems (HP²CSs),

  to our Ontologic Programming (OP) and Ontologic Computing (OC) (see also Kernel-Less Operating System (KLOS), Systems Programming using Address-spaces and Capabilities for Extensibility (SPACE), Apertos (Muse), L4, and so on), and

• made conceptual and technical mistakes,

• there is no citation or other evidence publicated about ROC utilized as a general computing model before the year 2007,
• its white paper about ROC was announced on the 20th of March 2007 and is dated 12th of July 2007,
• its description of ROC is merely an editing or rote, uncreative variation of our original and unique description of an essential part of our OS by substituting terms, using some more words, and rearranging terms, which does not constitute a new and own expressive creation and hence no derivative work or something else being eligible for copyright protection, and
• two talks were given in 2007 titled
  • Putting the Web Back into the Semantic Web and
  • Extending NetKernel for Semantic Web Processing,

and

It would be obvious for a Person of Ordinary Skill In The Art (POSITA) that the company has stolen essential parts of our original and unique work of art titled Ontologic System and created by C.S., specifically those parts related to our reflective and cognitive Evolutinary operating system (Evoos), in conjunction with substantially similar expressions of ideas and a significant part of the characteristic expression of the OS.

Stay away from that company and become a member of our Society for Ontological Performance and Reproduction (SOPR). We will give no allowance to use that NetKernel in our OS without proper membership and proper licensing, if at all. Furthermore, we also demand that the open source variant of its plagiarism has to be removed immediately.

Furthermore, there is a common denominator with all these serious frauds: Los Alamos National Laboratory (LANL).
We can also see once again that open source is misused to damage businesses but not used for a social cause.

Btw.: Put

together or integrate them, and you will see a little of the true magic of our OM, OP, and OC in particular and our whole OS in general.

31.October.2018

12:19 UTC+1
SOPR #146

*** Work in progress - some few links missing ***
In the last days we thought about the following topics:

Voice-based systems and virtual assistants
We would like to suggest that the individual voice-based systems and virtual assistants can be called

Calling an item by its typical name according to common sense connects it with the platform of our Society for Ontological Performance and Reproduction (SOPR) (see also issue SOPR #143 of the 10th of October 2018).
Maybe better ideas exist or will be developed.

Legal matters
We decided against the introduction of the provision related to a seat in the board of a company to avoid any legal issues (see the issues #138 of the 28th of August 2018, #141 16th of September 2018, and #146 of the 31st of October 2018).
But we would like to have a regulation that is still related to the ratio of the overall revenue or profit to the revenue or profit generated with our OS, Os, OAOS, and other works created by C.S., but only allows us to buy shares of a company and this even if

For sure, both activities must be allowed by a market regulator.

Next phase to ON, OW, and OV
In the meantime it should have become clear for every interested entity how the system stack of the Ontologic Net (ON), Ontologic Web (OW), and Ontologic uniVerse (OV) looks like. In this relation, we would like to submit the practical proposal, that providers of networking infrastructures and cloud computing platforms provide an environment comprising

so that providers and their customers can begin with prototyping, testing, and even implementing their technologies, systems, applications, and services based on

• Uniform Resource Identifier (URI),
• Virtual Object System (VOS), and
• hypergraph-based Ontologic System,

Those services, that have to be provided by our Society for Ontological Performance and Reproduction (SOPR) in accordance with the Articles of Association (AoA) and the Terms of Service (ToS) (see the issues #... of the ...), can be gradually migrated when more and more servers of the SOPR platform are set up or provisioned, and running.
Please keep in mind that no open source licensing of our OS, Os, and OAOS is allowed that has not been accredited by our SOPR. We recommend to use disclosed source licensing.