NetKernel was started at Hewlett-Packard Labs in 1999. It was conceived by Dr. Russ Perry, Dr. Royston Sellman and Dr. Peter Rodgers as a general purpose XML operating environment that could address the needs of the exploding interest in XML dialects for intra-industry XML messaging.2
Rodgers saw the web as an implementation of a general abstraction which he extrapolated as ROC, but whereas the web is limited to publishing information; he set about conceiving a solution that could perform computation using similar principles. Working in close partnership with co-founder Tony Butterfield, they discovered a method for writing software that could be executed across a logical model, separated from the physical realm of code and objects. Recognising the potential for this approach, they spun out of HP Labs.
Rodgers and Butterfield begun their company as "1060 Research Limited" in Chipping Sodbury, a small market town on the edge of the Cotsolds region of England in 2002, and over a number of years developed the platform that became NetKernel.
In early 2018, 1060 Research announced that it was appointing a new CEO, Charles Radclyffe.3 Radclyffe announced to the NetKernel community in February 2018 that the team were working on a new platform based on NKEE 6 which would be fully hosted, programmable and accessible via the web - NetKernel Cloud. Radclyffe resigned after six months.4
A resource is identifiable information within a computer system. Resources are an abstract notion and they cannot be manipulated directly. When a resource is requested, a concrete, immutable representation is provided which captures the current state of the resource. This is directly analogous to the way the World Wide Web functions. On the Web, a URL address identifies a globally accessible resource. When a browser issues a request for the resource it is sent a representation of the resource in the response.
A resource is identified by an address within an address space. In NetKernel, Uniform Resource Identifier (URI) addresses are used to identify all resources. Unlike the Web, which has a single global address space, NetKernel supports an unlimited number of address spaces and supports relationships between address spaces.
NetKernel supports a variety of URI schemes and introduces new ones specifically applicable to URI addressing within a software system.
The fundamental operation in NetKernel is a resource request, or request. A request consists of a resource URI address and a verb. Supported verbs include SOURCE, SINK, NEW, DELETE, EXISTS and META. Each request is dispatched to a microkernel which resolves the URI address to a physical endpoint and assigns and schedules a thread for processing. When the endpoint completes processing the microkernel returns the response to the initiating client.
The fundamental instruction in NetKernel is a resource request, specified by a URI. Mechanisms that sequence URI requests are located above the microkernel. In the current Java-based implementation, requests are dispatched using a Java API. This implies that any language that can call a Java API can be used to program NetKernel.
As of April 2013[update], the set of languages supported includes:
The active URI scheme was proposed by Hewlett-Packard as a means to encode a functional program within a URI.
For example, the following URI calls a random number generator
and the following uses an XSLT service to transform an XML document with an XSLT stylesheet:
Because the argument values may be URI addresses themselves, a tree-structured set of function calls can be encoded in a single URI.
Transports are a mechanism used to introduce requests from outside of NetKernel to the NetKernel address space. Transports are available for the HTTP protocol, JMS (Java Message Service), and CRON. Other transports can be easily added as they are independent from the rest of NetKernel.
The role of the transport is to translate an external request based on one protocol into a NetKernel request with a URI and a specific verb (SOURCE, SINK, etc.) and then to send the returned representation back to the client via the supported protocol.
Two mappings are handled by a transport. The first is between the address space of the externally supported protocol to the internal NetKernel address space. And the second is between the verb or action specified externally into a NetKernel verb.
For example, in the case of the HTTP transport, the external address space is a sub-space of a URL. The following mapping illustrates this point.
In addition, the HTTP protocol supports methods such as GET, PUT, HEAD, etc. which are mapped to NetKernel verbs.
A mechanism is needed to issue the URI requests, capture the returned representations, and communicate with clients.
Scripting languages are executed by their runtime engine, which is itself a service. For example, the Groovy language runtime will run a program contained in the file file:/program.gy with the following:
"1060 Public License v1.2". 1060 Research. http://www.1060research.com/license/ ↩
"About: History". 1060 Research. http://www.1060research.com/about/#history ↩
"Bristol startup NetKernel hires Deutsche Bank innovation lead as CEO". FinExtra. 7 February 2018. https://www.finextra.com/newsarticle/31641/bristol-startup-netkernel-hires-deutsche-bank-innovation-lead-as-ceo ↩
"Three Critical Lessons I Learned from My 6 Months as a Deep Tech CEO". https://www.forbes.com/sites/charlesradclyffe/2018/08/30/three-critical-lessons-i-learned-from-my-6-months-as-a-deep-tech-ceo/#310f15da5f88 ↩