Abstract: An array of registered entity property-value pairs representing a registered entity are stored in a data storage system. Each of the pairs includes a property label representing a property and a value range of the property. For each identifier property-value, an identifier property label, uniquely identifying the registered entity, and an identifier value representing a value of the identifier property are stored. A dataset is acquired with dataset property-value pairs for each of a first set of acquired dataset entities, where each pair includes a property label representing a property and a value representing a value range of the property. An identifier property-value pair matching an acquired dataset property-value pair for the acquired dataset entity is identified and then the acquired dataset property-value pairs are consolidated into the array of registered entity property-value pairs.

Abstract: A software service execution system includes: a software library storing software services, each obtaining and processing input data from a specified input URI (uniform resource identifier) and outputting the result to a specified output URI; a metadata graph representing the software services, each being identifiable by a predicate defining a relationship between a subject vertex and an object vertex, the subject vertex storing the specified input URI and being linked by a directed edge labelled with the predicate to the object vertex storing the specified output URI; a metadata graph query interface receiving a query requesting a queried vertex, linked by a defined traversal path along one or more edges to a source vertex; a software service execution controller controlling the execution of the software services identified by specified predicates labelling edges on the defined traversal path, in an order determined by the defined traversal path.

Abstract: A software service execution apparatus comprising a registry of software services, each service to execute a data processing function in the registry; a controller, to receive a processing request defining requested data processing functions, compose an execution schedule of software services from the software services identified, fulfill the data processing request by identifying a software service that matches the requested data processing function, include the identified software service in the execution schedule, and control execution of the schedule. The apparatus further comprises a machine learning mechanism configured to maintain a record of the composing.

Abstract: A microservice-based data processing apparatus, including: a type register, storing a list of types, a type being a semantic concept expression; and microservices each comprising an annotation of an input type and output types from the list; processing logic transforming input data expressed by the input type into output data expressed by the output types; and a messaging mechanism for inputting data, via a message, to a microservice, the mechanism defining a message format for structuring the messages. The format includes a first field specifying the data being input; and a second field specifying a type, from the list of types, semantically expressing the concept instantiated by the data. Each microservice includes a controller to receive a message from the mechanism having the format, and to respond by executing the logic when the type specified by the second field matches the input type of the microservice.

Abstract: A data processing apparatus including a library, storing software services, each executing a data processing function; a user interface receiving commands, expressed in a language and defining a data processing target and a data processing request; and a parser. The parser extracting from each command: the request from the language; and the target. A knowledge base maintaining a record of the request and the target; a scheduler obtaining the request from the parser, and compiling a schedule to fulfill the request; a controller controlling execution of the schedule, the target being the input data to the execution, and to output a result; and a result processor obtaining the result, and, based on records of requests and targets, to identify a request candidate, and to output to the user as a selectable command in the language, via the user interface, the candidate with the result defined as a data processing target.

Abstract: A data storage system a process including: storing an array of registered entity property-value pairs representing the registered entity where each of the pairs includes a property label representing a property and a value range of the property; storing an entry of one identifier property-value pair where each pair includes an identifier property label uniquely identifying the registered entity, and an identifier value representing a value of the identifier property; acquiring a dataset having acquired dataset property-value pairs for each of a first set of acquired dataset entities, where each pair includes a property label representing a property and a value representing a value range of the property; identifying an identifier property-value pair matching an acquired dataset property-value pair for the acquired dataset entity; and consolidating the acquired dataset property-value pairs into the array of registered entity property-value pairs.

Abstract: A microservice-based data processing apparatus, including: a type register, storing a list of types, a type being a semantic concept expression; and microservices each comprising an annotation of an input type and output types from the list; processing logic transforming input data expressed by the input type into output data expressed by the output types; and a messaging mechanism for inputting data, via a message, to a microservice, the mechanism defining a message format for structuring the messages. The format includes a first field specifying the data being input; and a second field specifying a type, from the list of types, semantically expressing the concept instantiated by the data. Each microservice includes: a controller to receive a message from the mechanism having the format, and to respond by executing the logic when the type specified by the second field matches the input type of the microservice.

Abstract: A software service execution system includes: a software library storing software services, each obtaining and processing input data from a specified input URI (uniform resource identifier) and outputting the result to a specified output URI; a metadata graph representing the software services, each being identifiable by a predicate defining a relationship between a subject vertex and an object vertex, the subject vertex storing the specified input URI and being linked by a directed edge labelled with the predicate to the object vertex storing the specified output URI; a metadata graph query interface receiving a query requesting a queried vertex, linked by a defined traversal path along one or more edges to a source vertex; a software service execution controller controlling the execution of the software services identified by specified predicates labelling edges on the defined traversal path, in an order determined by the defined traversal path.

Abstract: A software service execution apparatus, comprising: a registry of software services, each service to execute a r data processing function in the registry; a controller, to receive a processing request defining requested data processing functions, compose an execution schedule of software services from the software services identified, fulfill the data processing request by identifying a software service that matches the requested processing function, and including the identified software service in the execution schedule; and control execution.

Abstract: A data processing apparatus including a library, storing software services, each executing a data processing function; a user interface receiving commands, expressed in a language and defining a data processing target and a data processing request; and a parser. The parser extracting from each command: the request from the language; and the target. A knowledge base maintaining a record of the request and the target; a scheduler obtaining the request from the parser, and compiling a schedule to fulfill the request; a controller controlling execution of the schedule, the target being the input data to the execution, and to output a result; and a result processor obtaining the result, and, based on records of requests and targets, to identify a request candidate, and to output to the user as a selectable command in the language, via the user interface, the candidate with the result defined as a data processing target.