ATBECHDEDKESFRGBGRITLILUNLSEMCPTIESILTLVFIROMKCYALTRBGCZEEHUPLSKBAHRIS..MTNORSMESMMAKHTNMD..........
J
BDM Ver 1.7.2 (20 November 2019) - 1100000/0
3805956
EUROPEAN PATENT APPLICATION
A1
20210414
EP
20200462.8
20201007
en
en
en
201916595324
20191007
US
20210414
202115
20210414
202115
G06F 16/906 20190101AFI20210223BHEP
G06F 16/25 20190101ALI20210223BHEP
de
COMPUTERIMPLEMENTIERTES UND COMPUTERGESTEUERTES VERFAHREN, COMPUTERPROGRAMMPRODUKT UND PLATTFORM ZUR DATENORGANISATION ZUR VERARBEITUNG UND SPEICHERUNG IN EINER DATENSPEICHERMASCHINE
en
COMPUTER IMPLEMENTED AND COMPUTER CONTROLLED METHOD, COMPUTER PROGRAM PRODUCT AND PLATFORM FOR ARRANGING DATA FOR PROCESSING AND STORAGE AT A DATA STORAGE ENGINE
fr
PROCÉDÉ MIS EN UVRE ET COMMANDÉ PAR ORDINATEUR, PRODUIT-PROGRAMME D'ORDINATEUR ET PLATE-FORME D'ORGANISATION DE DONNÉES POUR LE TRAITEMENT ET LA MÉMORISATION DANS UN MOTEUR DE MÉMORISATION
2
Dynactionize N.V.
101671017
62225EP9-3
Schillerstraat 8
2050 Antwerp
BE
BRANDS, Michael Rik Frans
Mereldreef 16
2980 Halle-Zoersel
BE
HEREMANS, Maarten
Oosthamsesteenweg 8
2491 Olmen (Balen)
BE
Algemeen Octrooi- en Merkenbureau B.V.
100061505
P.O. Box 645
5600 AP Eindhoven
NL
AL
AT
BE
BG
CH
CY
CZ
DE
DK
EE
ES
FI
FR
GB
GR
HR
HU
IE
IS
IT
LI
LT
LU
LV
MC
MK
MT
NL
NO
PL
PT
RO
RS
SE
SI
SK
SM
TR
BA
ME
KH
MA
MD
TN
A computer implemented and computer controlled method of arranging, in memory, data subsets retrieved from a single or from different data sources, and structured in accordance with a logical data model, for the processing of these data subsets by an action-based logical data model. The action-based logical data model comprises actions, data categories, including a subject data category, an object data category, a spatial data category and a temporal data category, action topology combinations, instance information supplemented to an action topology combination, and constructors. A constructor comprises a plurality of properties in accordance with a constructor topology combination. A property operates on action topology combinations matched to data subsets elements of data subsets in accordance with the action-based logical data model, for presenting structured relations between data subset elements of data subsets.

TECHNICAL FIELD
The present disclosure relates to data processing and data storage, more particular, to computer implemented and computer controlled processing and storage of computer readable data in accordance with a data structuring format.

BACKGROUND
In its most general form, a database refers to a set of data elements and the data model by which these data elements are interrelated. In conventional databases, the meaning or value of each data element is determined by its position in the data model. A data element representing the given name of a person in the database gets its proper meaning because it is stored under or allocated to a label such as 'Given_Name' in a table called 'People', for example. It is for this reason that in conventional database systems the first step in the implementation and deployment of the database is to produce a conceptual data model that reflects the complete structure of the information to be held in the database.
In conventional databases, a data element can not be stored if there is not provided a specific header or label to which the data element can be allocated. To state it differently, a data element can only be stored if a particular space to store the data element is addressed beforehand.
In a dynamic application environment, with large and larger data sets to be stored, creating such 'complete' data models is difficult, time consuming and requires frequent adaptations, as the number of items representing a new and not foreseen meaning of a data element readily expand over time. With the introduction of mobile telephony, for example, the need arose to expand the data model by the additional storage of a mobile telephone number next to a land line telephone number. Those skilled in the art will appreciate the difficulties that one encounters with the expansion of the items to be stored in a conventional data model, such as but not limited to data inconsistencies, ambivalent models, data multiplication, and so on, all potential harmful points of failure.
Having produced a conceptual data model, the next step is to translate this model into a form that actually implements the relevant items in the database. This process is often called the logical database design, and the output is a logical data model expressed in the form of a schema. Whereas the conceptual data model is (in theory at least) independent of the choice of database technology, the logical data model will be expressed in terms of a particular database technology.
At present, the most popular database model for general-purpose databases is the relational model, using a table-based format. The process of creating a logical database design using this model involves a methodical approach known as normalization. The goal of normalization is to ensure that each elementary 'item' is only recorded in one place, so that insertions, updates, and deletions automatically maintain consistency.
Besides the relational model, and without aiming to be complete, other known types of database models are designated a hierarchical database model, a network model, an object model, a document model, an array model, and a semantic model, for example.
Data that resides in a fixed field within a record or file is also called structured data. That is, data contained in relational databases and spread sheets, for example. Information that can not be readily classified and does not fit into a particular box or a traditional row-column database, is called unstructured data. Examples of unstructured data are photos, graphic images, presentations, emails, and word processing documents, for example. Unstructured data files often include text and multimedia content. Note that while these types of files may have an internal structure, they are still considered 'unstructured' because the data they contain does not fit neatly in a rigid data model structure.
Semi-structured data is a mix of structured and unstructured data. It is a type of structured data, but lacks the strict data model structure. With semi-structured data, tags or other types of markers are used to identify certain elements within the data, but the data does not follow a rigid structure. For example, word processing software now can include metadata showing the author's name and the date created, while the bulk of the document just being unstructured text.
While a particular database model may be optimal for storing one or another type of data, in practice, the known database modelling techniques all suffer to a greater or lesser extent the problems involved with the expansion in the amount and new types of data that is created over time in a dynamically evolving organization.
When querying a relational database, for example, that is when making a request to retrieve information stored in the database, no relations between data elements can be revealed other than defined by the data model structure. Further, many database systems require to make requests for information in the form of a stylized query that must be written in a special query language. This is the most complex method because it forces users to learn a specialized language.
With the advent of digitization, more and more data is created and stored in different types of databases, and in different types of data models. Plural different technologies are used to store all kinds of different data.
A challenge, while processing digital data, is how to combine the data stored in the different databases and data models, and how to combine and correlate such data to provide new insights and new useful combinations from the data.
To overcome the numerous technical challenges while trying to combine data from different data sources, a number of solutions are widely used.
A first set of solutions, focusing on structured data only, typically builds a data warehouse. That is, relevant data from existing available data sources are retrieved and stored into a new data model, that allows to process the data in a different manner than available from the existing or original data model by which the data were stored in a respective database. Typically, the retrieved data are processed by a number of operations before same have the appropriate format to be stored and used in a warehouse. This process is usually called ETL, Extract, Transform and Load.
Data warehouses are usually built to make data available for reporting, and most often they rely on a relational database to store the data, using specific techniques to design data models. The most commonly known and used ones of these techniques are the so-called star-shape data model and the snowflake data model.
As a consequence of the manner in which data are transferred into a data warehouse, i.e. the ETL process, and as a consequence of mostly applying relational databases to store the data, data warehouses possess a number of important limitations.
Data warehouses only contain structured data and fact data. Unstructured and semi-structured data have no place in a data warehouse. The star-shape or snowflake model is always built with a specific set of reports in mind, and allows data retrieval for only those reports in a fast and easy way. However, if new reports are required or new data need to be integrated in the data warehouse, usually programmatic changes to the data model are required.
Also for the warehouse technology, data that are not know upfront can not be stored in the model and only the links between the data that are encoded in the model by the designers will be made explicit, hence not all the links in the data itself will be made explicit.
These limitations, and others have led to the creation of a second kind of solutions to store data and to make it possible to reuse the stored data for other purposes.
This second kind of solutions mainly aims at overcoming two severe limitations of data warehouses namely the storage and use of semi-structured and unstructured data, to store the data without needing a fully qualified and predefined structure and without knowing upfront how the data will be used. These solutions are usually referred to as data lakes.
Data lakes aim at storing mainly unstructured data in its existing format. The principle used is store now, use later, which means a data lake is well suited to quickly store data of which one does not know the structure or data that do not have an explicit structure. The main advantage of a data lake is that it is a safe haven for all data one wants to store before a specific use of the data is known.
When a specific use for the stored data becomes necessary, the typical way of working is to create an ad-hoc model for the data in the lake, so that the data can be approached by structured queries.
A disadvantage of the approach is that every use of the data requires the conception of a model, specific to the use case. Another disadvantage is that for combining data stored in a data lake with data in a data warehouse, an overarching model that integrates the data from the two sources in a new structure needs to be created. This requires a lot of modelling effort, data transformations and data duplications, which often has a negative influence on data quality, data volumes and data consistency.

SUMMARY
It is an object of the present disclosure to provide a versatile computer controlled method of and a data processing platform for arranging in memory structured, unstructured or semi-structured computer readable data and for storage thereof, which method and platform can cope with the increase of data produced, both in terms of the amount and the content thereof, and for arranging in memory data stored in different data sources and data models, providing a universally applicable data model mapping platform. It is another object of the present disclosure to provide a computer implemented and computer controlled method of and a data processing platform for the retrieval of data stored in accordance with this versatile data storage method.
In a first aspect there is provided a computer implemented and computer controlled method of arranging data for processing and storage thereof at a data storage engine, wherein a computer performing the steps of:
- receiving data in a computer readable format, the data comprising a sequence of data elements;
- identifying data elements in the received data and allocating to each of the identified data elements a unique data element identifier representing a respective data element;
- assigning, to the received data, an action from a plurality of actions represented by a respective unique action identifier and a unique action topology identifier specifying an association between data elements of an action according to a respective topology comprised of an ordered plurality of data categories including a subject data category, an object data category, a spatial data category and a temporal data category, the topology being represented by a unique topology identifier and each data category being represented by a respective data category identifier;
- matching the identified data elements with the assigned action topology combination in accordance with the order of the action topology and the sequence of the data elements, such that one data element is matched with one data category of the topology;
- supplementing instance information to matched action topology combinations and allocating an action topology instance identifier to the supplemented action topology combination, and
- storing, in a computer readable format, at the data storage engine the identified data elements, the instance information and associations between identifiers resulting from the steps of identifying, assigning, matching and supplementing.
Rather than having to predefine a complete schema, consisting of tables with rows and columns and links or documents with fields and values, the present disclosure operates in accordance with a data structuring format essentially comprised of actions, topologies, action topology combinations, data categories and instance information, hereinafter referred to as action-based logical data model.
The action-based logical data model according to the present disclosure allows users to process data in the way they use same in their everyday life, by operating on unique pieces of data, called data elements, that are of interest to the user. The disclosure is based on the insight that such data elements - be it structured, unstructured or semi-structured data elements - each may be categorized in one or more data categories of a limited number of data categories, at least comprising a subject data category, an object data category, a spatial data category and a temporal data category.
That is, the subject data category refers to data elements retrieved by a 'who'-type query. Data elements that typically relate to a property, i.e. referring to a capacity or quality and the like, are to be allocated to the object data category. Data elements of the object data category are typically retrieved by a 'what'-type query. The spatial data category comprises data elements referring to a geographical position, a place, a space or the like and are retrieved by a 'where'-type query. Data elements generally referring to time are to be categorized in the temporal data category, and are the result of a 'when'-type query applied at the data to be stored.
Data elements are linked at the action level. An action specifies an association between data elements and may be defined as an intentional, purposive, conscious and subjectively meaningful activity. Generally an action involves an intention and a goal. Registering clients of a company, registering complaints, registering the constituents of a product, organizing/attending a meeting, filling a table, acting in a profession, are just a few examples of actions.
Although data elements may exist in isolation, in a scenario of use, however, data elements are always combined or associated with other data elements. It is such an association of data elements in an action that conveys full semantics of each data element for a particular use, and such association is expressed by a topology. A topology is comprised of an ordered plurality of data categories. That is a specific sequence and number of who's, what's, where's and when's. The number of data categories involved is defined by the length of a topology. Each topology is unique in the order of appearance and the number of the data categories of a respective topology.
For example, 'throwing' is an action that may involve a person, i.e. a subject, that performs the throwing, i.e. a 'who', an object that is to be thrown, such as a ball for example, i.e. a 'what', a place where the ball is thrown, such as at sports field, i.e. a 'where', possibly a receiver of the ball, i.e. again a subject expressed by the data category 'who', and perhaps the day that the ball is thrown, i.e. a 'when'. The topology template for this specific action is then constituted by the data categories | who, what, where, who, when |. One will appreciate that when the receiver of the ball is not of interest, the action involves a different topology, namely | who, what, where, when |.
A topology as such is not specific for an action. Different actions may share a same topology. However, same actions involving different topologies are distinguished from each other as specific action topology combinations. One will appreciate that the number of actions is virtually unlimited and depends on the number of category substituents and the number and length of the topology templates.
Action topology combinations may need further description that may not be qualified as part of an action that can be distinguished by a specific topology, such as that the 'where' data category of a particular topology refers to a city or refers to geographical co-ordinates, such as Global Positioning System, GPS, data, or in that the 'when' data category refers to 'years' or 'seconds', for example. However, other descriptive information may be supplemented to an action topology combination, like a timestamp indicating the time of matching, for example. Action topology combinations supplemented by descriptive information are referred to as action topology instances.
The disclosure involves storage of the data elements of the received data in association with at least one data category and at least one action. This effectively allows for storage of each data element just once, although a respective data element may be involved with different actions. Thereby providing vast storage space savings, and effectively avoiding duplications and inconsistencies in the data elements stored.
To this end, the identified data elements are matched with the assigned action topology combination in accordance with the respective action topology and the sequence of the data elements, such that one data element is mapped to one data category of the topology.
In accordance with the present disclosure, actions are represented by a respective unique action identifier. Topologies are represented by a respective unique topology identifier. An action topology combination is represented by a unique action topology identifier, and action topology instances are represented by a unique action topology instance identifier. Each data category is represented by a respective data category identifier, i.e. a subject data category identifier, an object data category identifier, a spatial data category identifier, and a temporal data category identifier. Data elements are represented by a unique data element identifier.
Using the respective identifiers when invoking the matching of the data elements, the present disclosure creates associations between the data element identifiers, action identifiers, action topology identifiers, topology identifiers, data category identifiers and action topology instance identifiers. Links between data elements, that in classical databases have to be predefined and expressed by table links or object-inheritance, come to light in the disclosure by the fact that a same data element may take part in different actions. Once a data element becomes part of one ore more actions it becomes automatically linked with other stored data elements, independent from the origin of the data element. In fact, one does not need to have knowledge beforehand about any data element stored, to retrieve information from it.
It will be appreciated that data elements. i.e. their identifiers, may be directly matched with a particular data category, i.e. a data category identifier, in a pre-defined manner, for example in case of a single action. Such that the step of assigning is implicitly performed by such direct matching.
By storing, in a computer readable format, at a data storage engine the identified data elements in connection with their respective data element identifier, the instance information in connection with a respective action topology instance identifier, and the associations between the identifiers resulting from the steps of identifying, assigning, matching and supplementing, the present disclosure allows to query data elements in the most flexible way, just from manipulating the respective identifiers independent of the respective data elements.
The disclosure fully separates the raw data, the descriptive or instance data, and the identifiers. This means that query resolution can be done data-less. Even more, this full separation adds a powerful protection or security to the data elements, because the data elements, the instance information and the linking identifiers may be spread among physically separated hardware, i.e. data storage engines, data query engines and other data analysis engines.
It is just with the results of a query or an analysis that the respective data elements have to be revealed and at this level too a data proprietor may decide which data elements may be revealed and which not. The present disclosure reduces manipulation of big data sets objectively to manipulations on anonymous identifiers, thereby providing optimal privacy.
Analysis on the identifiers as such may provide information on the nature and validity thereof and hence the data stored, even without having to reveal particular data elements, i.e. there value or meaning.
In an embodiment the step of storing comprises building, by the computer, in the storage engine, a plurality of binary n-dimensional arrays, in particular a plurality of two-dimensional arrays, each array having a unique name and indices formed by respective identifiers, wherein the identifiers are preferably represented by numerical identifiers, and wherein associations between identifiers are expressed by a binary value, such that presence of an association between identifiers of an array is expressed by a first binary value and absence of a relation between the identifiers of an array is expressed by a second binary value.
With a limited set of, for example, bit-matrices, all links between the available data elements can be represented. These matrices can be easily split in fixed-size sub matrices, that can be stored over a virtually unlimited number of servers making up the storage engine, without the need for complex map reduce mechanisms or the like. The fact that this limited set - less than about 30 - matrices allows to represent all of the links in the data also means that the indices don't grow exponentially in size or complexity just because the data becomes more complex.
The overhead of each unique data element and of each descriptive information is minimal - fixed to the size of its identifier, ID, and the number of bits referring to the ID within the matrices. The bit-matrices can be stored and retrieved easily on disc or other storage medium in a space-optimised format.
To this end, in an embodiment, the binary values are assigned by the computer to obtain sparse arrays or matrices, that is matrices of which the number of zero's is largest, requiring less storage space. It will be appreciated that this eventually may involve inversion of the bits that represent a link between the indices of the array or matrix.
In an embodiment, the computer stores the data element identifiers and the corresponding data elements, as well as the action topology instance identifiers and the corresponding instance information in lists. These lists, like the bit-matrices or arrays expressing links between the identifiers, may be split in sub-lists for storage over a number of servers making up the storage engine. Thereby adding another layer of security to the data storage.
The instance information, comprising descriptive information, in particular descriptive information pertaining to at least one data category of an action topology combination, may be structured in accordance with the data structuring format of the present disclosure used for the data elements, that is comprised of actions, topologies, action topology combinations, data categories and instance information.
The instance information, in particular, may comprise a so-called constraining action and a so-called applying action. A constraining action comprises a requirement that has to be fulfilled in connection with a particular data element. For example, for such data element an instance or instance information has to be available or defined. An applying action refers to data creation or triggering of an event or the like in connection with a particular data element.
By structuring the instance information also allocating respective identifiers in the manner as disclosed above in connection with the data elements, it will be appreciated that also links between the instance information can be revealed, providing a further layer of analysis.
A data element in accordance with the present disclosure is a piece of data such as a word in a sentence, a coded part or sample of a picture or a sound, a sensor value, and so on. In general, representing information or content of a text, a picture, sound, etc. Data elements of the digital data to be stored may be identified by comparing same with data elements stored at a data elements repository. However, data elements may also be identified by the computer from information received from manual user input or remote input from other data sources. A simple example is data in which the data elements are gathered in a specific prescribed order through a user interface or menu, or comma separated, or otherwise. Data elements may also be retrieved by the computer from applying a data elements identifying algorithm in relation to the digital data to be stored. Such a data elements identifying algorithm is, for example, based on statistical data element counting, pattern recognition, correlation and concepts detection algorithms.
An action to be assigned may be pre-defined and available for the computer from an actions repository, for example. However, actions may also be assigned dynamically by user input to the computer, generated by an action identifying algorithm, and/or based on pattern recognition by neural networks, for example, without suffering the problems of expanding the classical data model to cope with new types of and links between data elements to be stored.
An action topology combination may be assigned, by the computer, by retrieving a pre-defined topology from pre-defined topologies stored at a topologies repository, for example, or by a topology received by the computer through user input, for example, or from a suitable topology identifying algorithm, and combining same with the already assigned action. Data representing a text, a sentence, a clause, a scene, an event or the like can be structured by one or a plurality of topologies.
Unique identifiers may be allocated by the computer in accordance with a suitable algorithm as generally known to a person skilled in the art.
In a second aspect there is provided a computer implemented and computer controlled data query method, wherein a data query is performed by a computer on identifiers stored at a data storage engine in accordance with the action-based logical data model as elucidated in accordance with the first aspect of the present disclosure.
As disclosed above, data elements are linked at the action level, comprised by at least one instance of a respective topology, i.e. an action topology combination, and these links are expressed by the associations between the respective identifiers resulting from the steps of identifying, assigning, matching and supplementing in accordance with the first aspect of the present disclosure.
Accordingly, stored data elements, either alone or in combination, can be retrieved, in accordance with the present disclosure, by performing a data retrieving query at identifier level.
Any data element can be queried and all the links between any data elements can be discovered by three query types:
- an in-action query, identifying co-existence of data elements in a same action, based on the data element identifiers, action topology identifiers, action identifiers and topology identifiers;
- a common-action query, identifying data elements having a common set of actions, based on the data element identifiers, action topology identifiers, and action identifiers, and
- a correlation query, verifying data elements that are shared by different action topologies, based on the data element identifiers, action topology identifiers, action identifiers, and topology identifiers.
In an embodiment operating on the array or matrix representations of the associations between identifiers, a query matrix is generated based on data element identifiers of data elements in a query and binary expression matrices expressing a logical relationship between the data element identifiers at action, topology and action topology instance level. The query is resolved by overlaying the query matrix with any of the n-dimensional arrays or matrices expressing an association between identifiers, wherein the data element identifiers of data elements in a query are retrieved from stored data elements and corresponding data element identifiers.
Applying bit-logic operations available to a computer in overlaying the query matrix and any of the n-dimensional arrays or matrices, any query or question of whatever complexity can be solved with almost identical speed.
In addition to querying or searching data elements for an analysing purposes, the data retrieving query may be set such to mask data elements from being retrieved for selective displaying and data transfer, such as required in connection with data security applications.
The data structuring according to the present disclosure not only allows for a versatile and powerful mining of digital data including structured, semi-structured and unstructured data, to reveal unseen structure and information, simply by selecting or defining a proper data retrieving query, but also for the execution of operations.
Operations to be performed using the data stored, may be executed by defining a proper execution topology, comprised of execution categories. An execution category specifies a particular type of execution to be performed and an execution topology specifies a number and the order in which respective execution categories have to be executed, to eventually provide a specified operation.
By assigning to each execution topology a respective unique execution topology identifier and by assigning to each execution category a unique execution category identifier, operations can be performed in like manner as explained above in connection with resolving a query, by overlaying an execution matrix comprised of execution topology identifiers and execution category identifiers with any of the n-dimensional arrays or matrices expressing an association between identifiers, wherein the data element identifiers of data elements involved in an operation are retrieved from stored data elements and corresponding data element identifiers.
The method in accordance with the present disclosure is universally applicable for storing many different types of data, such as but not limited to text data, linguistic data, image data, video data, sound data, control data, measurement data, olfactive data and tactile data. Due to the structuring format of the present disclosure, data elements of all such data types are stored and retrieved in a standardized manner, such that same allows for combinations of different types of data which is not possible at all with presently known, conventional databases and database structures.
In a third aspect, there is provided a data processing platform, configured for arranging data for processing and storage thereof at a data storage engine in accordance with the action-based logical data model of the first aspect of the present disclosure, the platform comprising at least one computer and a data storage engine operatively configured for performing the steps of:
- receiving data in a computer readable format, the data comprising a plurality of ordered data elements;
- identifying data elements in the received data and allocating to each of the identified data elements a unique data element identifier representing a respective data element;
- assigning, to the received data, an action from a plurality of actions represented by a respective unique action identifier and a unique action topology identifier specifying an association between data elements of an action according to a respective topology comprised of an ordered plurality of data categories including a subject data category, an object data category, a spatial data category and a temporal data category, the topology being represented by a unique topology identifier and each data category being represented by a respective data category identifier;
- matching the identified data elements with the assigned action topology combination in accordance with the action topology and the order of the data elements, such that one data element is matched to one data category of the topology;
- supplementing instance information to matched action topology combinations and allocating an action topology instance identifier to the supplemented action topology combination, and
- storing, in a computer readable format, at the data storage engine the identified data elements, the instance information and associations between identifiers resulting from the steps of identifying, assigning, matching and supplementing.
The computer implemented and computer controlled data processing platform, in an embodiment thereof, may comprise a plurality of communicatively interconnected data processing devices operating a plurality of a data processing layers, such as comprising
- a first data processing layer arranged for providing at least one communication interface for exchanging data with the data processing platform;
- a second data processing layer arranged for implementing and controlling the data structuring format, and
- a third data processing layer arranged for providing access to a plurality of data storage devices, for storage and querying purposes.
The processing platform, i.e. the computer or data processing devices, in further embodiments thereof, is configured for performing the method in accordance with the first aspect of the present disclosure, disclosed above.
In a fifth aspect there is provided a computer implemented and computer controlled method of arranging, in memory, data subsets retrieved in a computer readable format from at least one data source, the data subsets comprising a plurality of data subset elements structured in accordance with a logical data model, for the processing of the data subsets by an action-based logical data model in accordance with the first aspect of the present disclosure, wherein a computer performing the steps of:
- retrieving, at least one data subset of data provided by a data source, each data subset comprising a plurality of data subset elements, each data subset element represented by a respective data subset element identifier;
- assigning, to each data subset, at least one action represented by a respective action identifier;
- assigning, to each assigned action, a data category of the plurality of data categories, represented by a respective data category identifier, and at least one action topology combination specifying an association between data subset elements of a respective data subset of an assigned action, represented by a respective action topology identifier;
- matching each data subset element of each data subset with a data category of a respective action topology combination assigned to a respective data subset;
- supplementing, from the data source, instance information of a respective data subset to a matched action topology combination, the supplemented action topology combination represented by a respective action topology instance identifier;
- assigning, to the matched action topology combinations supplemented by the instance information, at least one constructor identified by a unique constructor identifier, each constructor comprising at least one property;
- assigning, to each constructor, a data category of the plurality of data categories, represented by a respective data category identifier, and at least one constructor topology combination, identified by a unique constructor topology identifier, the constructor topology combination specifying an ordered plurality of properties of a constructor, a property operating on the matched action topology combinations supplemented by the instance information, each property represented by a unique property identifier, and each property comprising a data category corresponding to a respective data category of the constructor topology combination, and
- presenting structured relations between the data subset elements of the data subsets in accordance with at least one assigned constructor.
By assigning, to an action, a data category from the above-defined data categories comprising a subject data category, an object data category, a spatial data category and a temporal data category, i.e. a 'who', a 'what', a 'where' and a 'when' data category, respectively, an action itself may become part of an other action, specified by an action topology combination comprised of an ordered plurality of data categories.
In this manner it becomes possible to combine data subsets of one or several data sources to which actions are assigned in accordance with the present action-based logical data model, by introducing a constructor action, or in short a constructor, comprising a plurality of constructer properties that operate on the matched action topology combinations supplemented by the instance information relating to data subset elements of the data subsets.
A constructor, like an action, is represented by a unique constructor identifier, has a data category of the plurality of data categories assigned to it, identified by a respective data category identifier, and at least one constructor topology combination, identified by a unique constructor topology identifier. The constructor topology combination specifies an ordered plurality of properties of a constructor, each property represented by a unique property identifier. From a respective constructor topology combination, based on the order of a particular property, to each property there is also assigned a data category, such that also an action may be assigned to a property, etc.
Hence, the assignment of data category to an action, the introduction of a constructor action operating on an assigned action and having properties that also may be represented by an action, provides a universally applicable data model mapping platform, capable of presenting structured relations between the data subset elements of plural data subsets of plural data sources and plural data models, by executing a respective constructor in accordance with the fifth aspect of the present disclosure.
Properties may include one or more of a data property, referring to an action topology instance combination of an assigned action, a label property, referring to an action topology of an assigned action, a calculated property, referring to a data subset of an assigned action, a constructor property, referring to an other constructor, and a function property, referring to an action.
A data property, linking to an action topology instance combination of an action, describes mapped data for which an action topology instance has to be specified as a parameter when the constructor is used. Which means that different instances of the constructor can be associated with multiple action topology instances. The data property may refer to an action topology instance combination assigned to a matched data subset at retrieval thereof, also called a constant property, or to an action topology instance combination of an action assigned when applying a constructor.
A label property, linking to an action topology of an action assigned to a data subset allows for access to all action topologies instances linked to that action topology. As such, a label property can be considered as an array of objects, the objects being the linked action topology instances.
A calculated property links to a specific data subset of a data source. A calculated property does not refer directly to any actual data but describes to load a data subset at the moment of use or execution of the calculated property in an application.
A constructor property contains a link to a specific other constructor, and a function property contains a link to an action, i.e. an action identifier in which the code to be executed and the parameters to be filled at execution time are specified. The function property can operate only on the data referenced by the properties of the constructor.
In accordance with the fifth aspect of the present disclosure, the step of assigning, to each assigned action, at least one action topology combination specifying an association between data subset elements of a respective data subset of an assigned action, comprises assigning an action topology combination, each data category of the action topology combination being equal to the data category of the assigned action. That is, the data category assigned to a respective action may be inherited by the data subset elements when matching same.
In accordance with the action-based logical data model disclosed in the first aspect of the present disclosure arranging, in memory, data retrieved in a computer readable format from at least one data source may comprise building, by the computer, a plurality of binary n-dimensional arrays, in particular a plurality of two-dimensional arrays, each array having a unique name and indices formed by respective identifiers, and wherein associations between identifiers are expressed by a binary value, such that presence of an association between identifiers of an array is expressed by a first binary value and absence of a relation between the identifiers of an array is expressed by a second binary value, and in particular wherein the binary values are assigned by the computer to obtain sparse arrays.
In an embodiment of the disclosure according to the fifth aspect of the present disclosure, arranging, in memory, data retrieved in a computer readable format from at least one data source comprises building, by the computer, at least one of a list of data subset element identifiers and corresponding data subset elements, and action topology instance identifiers and corresponding instance information of a data subset. The data subset element identifiers may be allocated automatically, by the computer, according to a data subset identifier allocation algorithm, for example, or may be taken form the data source, if applicable.
In accordance with the action-based logical data model disclosed in the first aspect of the present disclosure, in the present fifth aspect the instance information of a data subset comprises descriptive information, in particular descriptive information pertaining to at least one data category of an action topology combination, the instance information being structured in accordance with a data structuring format comprised of actions, topologies, action topology combinations, data categories and respective unique identifiers.
Data subsets of a data source may comprise at least one of a table in a relational database; a subgraph in a graph database; a document from a document database; a set of documents from a document database; a list of Key-Value pairs from a Key-Value Store; and a result set of a query performed at data of a data source. It will be appreciated that data subsets may comprise a plurality of data subset elements.
As mentioned above, a constructor is a special action for revealing and presenting structured relations between data subset elements of different data subsets of the same or different data sources and a plurality of different data models. Accordingly, in a similar manner as disclosed for an action, in accordance with the present disclosure, a constructor may be assigned by the computer using at least one of pre-defined constructors stored in a constructors, i.e. actions, repository; a constructor received by the computer, and a constructor identifying algorithm.
In a similar manner as disclosed for an action topology combination in accordance with the first aspect of the present disclosure, a constructor topology combination may be assigned to a constructor by the computer by retrieving a topology from pre-defined topologies stored at a topologies repository; topologies received by the computer, and a topology identifying algorithm.
In an embodiment of the fifth aspect of the present disclosure, a property is represented by an action, comprising a data category equal to the data category of the property, and an action topology combination comprising an ordered plurality of action topology instance identifiers of matched data subsets and comprising the property identifier.
A constructor may be expressed as an instance of an action, which action is a predefined action having a data element comprising the constructor identifier, and an action topology referring to the data categories of properties of the actions corresponding to the constructor, and wherein data elements associated as data with respective topology data categories are action topology instance identifiers of a corresponding action of a respective property.
It is noted that the structure of a constructor may also be expressed as an action. That action may then have the name, i.e. the identifier, of the constructor. The action topology will be composed of the set of data categories of all the properties of the constructor. The names, i.e. the identifiers of its different properties will be the metadata associated with every topology position and the type of the property will then be associated as a data element with every topology position. This supplementary way of expressing a constructor can help to understand the model but is not necessary to make it work.
In a sixth aspect of the present disclosure there is provided a computer implemented and computer controlled data processing platform, configured for arranging, in memory, data subsets retrieved in a computer readable format from at least one data source, the data subsets comprising a plurality of data subset elements structured in accordance with a logical data model, for the processing of the data subsets by an action-based logical data model representing data comprising a plurality of data elements, by:
- actions, assigned to data, each action identified by a unique action identifier;
- data categories, including a subject data category, an object data category, a spatial data category and a temporal data category, each data category identified by a unique data category identifier;
- action topology combinations, specifying associations between data elements of data of an action in accordance with a topology comprising an ordered plurality of data categories, each action topology combination identified by a unique action topology identifier;
- instance information, supplemented to an action topology combination, identified by a unique action topology instance identifier, and
- each data element identified by a unique data element identifier,
the platform comprising at least one computer and memory configured for performing the steps of:
- retrieving, at least one data subset of data provided by a data source, each data subset comprising a plurality of data subset elements, each data subset element represented by a respective data subset element identifier;
- assigning, to each data subset, at least one action represented by a respective action identifier;
- assigning, to each assigned action, a data category of the plurality of data categories, represented by a respective data category identifier, and at least one action topology combination specifying an association between data subset elements of a respective data subset of an assigned action, represented by a respective action topology identifier;
- matching each data subset element of each data subset with a data category of a respective action topology combination assigned to a respective data subset;
- supplementing, from the data source, instance information of a respective data subset to a matched action topology combination, the supplemented action topology combination represented by a respective action topology instance identifier;
- assigning, to the matched action topology combinations supplemented by the instance information, at least one constructor identified by a unique constructor identifier, each constructor comprising at least one property;
- assigning, to each constructor, a data category of the plurality of data categories, represented by a respective data category identifier, and at least one constructor topology combination, identified by a unique constructor topology identifier, the constructor topology combination specifying an ordered plurality of properties of a constructor, a property operating on the matched action topology combinations supplemented by the instance information, each property represented by a unique property identifier, and each property comprising a data category corresponding to a respective data category of the constructor topology combination, and
- presenting structured relations between the data subset elements of the data subsets in accordance with at least one assigned constructor.
In an embodiment of the computer implemented and computer controlled data processing platform in accordance with the sixth aspect of the present disclosure, structured relations between the data subset elements of the data subsets are presented by at least one of displaying the structured relations at an electronic display, and storing the structured relations in a computer readable form at a storage engine.
Those skilled in the art will appreciate that the data processing devices and data storage devices of a processing platform in accordance with present disclosure need not be positioned in a single data room or the like. The platform is structured to allow remote processing and storage of data, in particular web-based processing and interfacing.
In a seventh aspect there is provided a computer implemented and computer controlled data query processing platform, comprising at least one computer configured for performing a data query on identifiers stored at the storage engine in accordance with the first aspect of the present disclosure, disclosed above.
The present disclosure also provides, in an eight aspect, a computer program product, comprising program code means stored on a computer readable medium, the code means being arranged to perform the method according to any of the first, second and fifth aspect of the present disclosure, when the program code is executed by a computer, in particular wherein the code means are arranged for being integrated in or added to a computer application for joint execution of the program code and the computer application by a computer.
A computer readable medium may comprise any of a transitory or non-transitory computer readable medium as known to those skilled in the art. Non-transitory computer readable media for the purpose of te present disclosure include but are not limited to any of optically, magnetically, solid state semiconductor or other media, such as designated Compact Discs, CDs, Digital Versatile Disks, DVDs, flash memory, memory sticks, Hard Disk Drives, HDDs, Solid State Drives, SDDs, etc.
The above-mentioned and other features and advantages of the present disclosure will be best understood from the following detailed description referring to the attached drawings. In the drawings, like reference numerals denote identical parts or parts performing an identical or comparable function or operation. The examples provided are for illustrative purposes only and may not be construed as limitative for the present disclosure, its use and the scope of protection conferred by the appending claims.

BRIEF DESCRIPTION OF THE DRAWINGS
- Fig. 1 shows, in a very schematic and illustrative manner, an entity relationship type diagram illustrating the relationships between the several entities of the data structuring format, in accordance with the present disclosure.
- Fig. 2 shows, in a schematic and illustrative manner, in a block diagram representation, an example of a logical design of a data processing platform, in accordance with the present disclosure.
- Figs. 3-8 show, in a schematic and illustrative manner, examples of items stored in the several stores of Fig. 2 with their respective IDs, in accordance with the present disclosure.
- Figs. 9-12 show some examples of two-dimensional matrices illustrating links between IDs of several items, in accordance with the present disclosure.
- Fig. 13 shows an example of a matrix based query expression for use with the two-dimensional matrices shown in Figs. 9-12 and the items disclosed in Figs. 3-8, in accordance with the present disclosure.
- Fig. 14 shows an enhanced entity relationship type diagram according to Fig. 1, for revealing and presenting structured relations between data subset elements of data subsets of data sources, in accordance with the present disclosure.
- Fig. 15 shows an example of a data source containing data subsets comprising a plurality of data subset elements structured in accordance with a logical data model.
- Fig. 16 shows, in a schematic and illustrative manner, matching of a data subset of the data source of the example shown in Fig. 15, in accordance with the present disclosure.
- Fig. 17 shows, in a schematic and illustrative manner, matching of a result set of a query executed on the data subsets of the data source of the example shown in Fig. 15, in accordance with the present disclosure.
- Fig. 18 shows, in a schematic and illustrative manner, a series of examples of actions matching data subsets of the data source of the example shown in Fig. 15, in accordance with the present disclosure.
- Fig. 19 shows, in a schematic and illustrative manner, several examples of constructors using actions mapping external data as properties, in accordance with the present disclosure.
- Fig. 20 shows, in a schematic and illustrative manner, examples of how constructors and their properties can be represented as actions, in accordance with the present disclosure.
- Fig. 21 shows, in a schematic and illustrative manner, examples of how usage of properties can be represented as actions, in accordance with the present disclosure.

DETAILED DESCRIPTION
In the entity relationship type diagram 10 of Fig. 1, reference numeral 11 represents data elements received by a computer in a computer readable format. To each of the data elements a unique data element identifier, DataElementID, is allocated. Besides its ID, data elements may additionally be identified by a respective name, if applicable.
An action or actions to be assigned to the received data and the unique action identifier, ActionID, representing a particular action, are indicated by reference numeral 12. Actions may also have a particular name.
The entity designated by reference numeral 13 represents topologies. Topologies are comprised of a plurality of ordered data categories, and each topology is represented by a unique topology identifier, TopologylD.
Data categories, represented by entity 14, include a subject data category, an object data category, a spatial data category and a temporal data category. Each data category is represented by a respective data category identifier, DataCategorylD. Suitable names for the data categories are 'who', 'what', 'where' and 'when', respectively representing the subject data category, the object data category, the spatial data category and the temporal data category.
The action topology entity 15 specifies combinations of actions of the plurality of actions 12 - an action represented by a respective unique ActionID - and a topology of the plurality of topologies 13 - a topology represented by a respective unique TopologylD. Each such action topology combination is represented by a unique action topology combination identifier, ActionTopologylD, which may be comprised of a respective ActionID and TopologylD.
In order to match data elements 11 with an assigned action topology combination 15, the sequence of the data elements, i.e. their DataElementID, and the order of the data categories 14 in a particular topology 13 have to be observed. To this end, an order identifier entity 16, OrderlD, is provided which represents the position of a particular data category identified by its DataCategorylD in a particular topology, represented by its TopologylD.
Based on this OrderlD, instance information from an instance information entity 17 may be supplemented or added to the matched action elements and data categories in an action topology, which instance information is represented by a unique instance information identifier, InstancelnformationlD.
The associations of the thus matched data elements, data categories and the instance information provided are expressed by a particular action topology instance of the action topology, having an action topology instance identifier, ActionTopologylnstancelD, as represented by entity 18.
That is, the action topology instance entity 18 represents the associations between DataElementlDs, InstancelnformationlDs, ActionTopologylDs, TopologylDs, DataCategorylDs, and the respective order or position thereof by the OrderlD. The associations between the respective IDs thus obtained may be stored in a plurality of arrays or matrices and may form a basis for data querying and for data execution, i.e. executing operations based on the data elements available.
In the example of the processing platform 20 in accordance with the present disclosure as shown in Fig. 2, a computer comprising a first processing layer 21 is arranged to provide the communication interface(s) between the platform 20 and the external world. The first processing layer 21 ensures the exchange of data between the data processing platform and external sources and consumers of data (not shown). Typically, the data processing platform communicates with other computer based applications via automated exchanges of data or via user driven exchanges.
Once a request for data or a request to store data arrives with the platform 20 via one of the communication interfaces of the first processing layer 21 of the platform, a second or data processing layer 22 of the computer is configured for identifying data elements and assigning an appropriate action and topology to the data. Data elements may be identified through a suitable data elements identifying algorithm, from information provided through the user interface layer 21, or other sources of data and applicable information. Furthermore, by the data processing layer 22, the corresponding data categories are matched with the data elements based on their respective order.
To execute the process of assigning, ordering and matching on the data received or requested in a query, for example, the data processing layer 22 interacts with a third or data access layer 23 of the computer.
The data access layer 23 logically comprises at least four different logical data stores 26, 27, 28, 29. The first store 26, being the data element store, is configured for assigning a unique DataElementID to each stored data element and for storing each unique data element at least once (or with a user requested degree of redundancy) in the data element store 26.
Those skilled in the art will appreciate that the data element store 26 may as such also consist of different sub-stores. The most common reason for having different stores will be the size and number of data elements to store. However one could also create a specific store for each different type of data elements to store. Examples of different data element types are string data, floating point numerical data, integer data, timestamp data, all of which can be stored in a common in-line store 31 or each have their own store. Larger data, like binary objects and many more, typically will be stored in a large object base, LOB, storage 32. One may also spread out the logical data element store over multiple geographically spread physical sub-stores or repositories or storage engines, to avoid potential latency and data losses that could occur if data has to travel over long physical distances or in case of a disaster occurring at one of the physical storage locations, such that data would no longer be available or becomes corrupted, for example.
The second logical store 27 is the action based data description store 27. This action based data description store contains all the elements needed to adequately describe the data elements and the relationships there between. These elements are data categories 33, each with a unique DataCategorylD, actions 34, each with a unique ActionID, topologies 35, each with a unique TopologylD and an ordered sequence of DataCategorylDs, and action topology combinations 36, that also each have a unique ActionTopologylD. In accordance with what has been remarked about the data element store 26 above, also the action based data description store 27 may consist of different sub-stores in function of the size of the data it needs to store or based on other criteria relevant to the specific purpose of the application using the data processing platform 20.
Instead of retrieving actions and topologies from a store or repository 34, 35, respectively, same may be inputted by a user, for example, through the first or interfacing layer 21 of the data processing platform. Action identifying algorithms and topology identifying algorithms may be executed by the second or data processing layer 22 of the platform 20.
The third logical store, namely the action topology instance store 28, actually establishes the link between the information in the action based data description store 27 and the data elements in the data element store 26, by using the respective IDs. The link is established by means of action topology instances. An action topology instance persists the way in which an action was assigned to an ordered sequence of data elements by matching its corresponding topology information expressed in the unique action topology combination with the ordered sequence of identified data elements. Moreover, for each action topology instance specific instance information is persisted. This instance information can be things like a status, extra information about the different data elements that can be derived from and associated with their position in the topology and the corresponding data category and the specific combination of the action and the topology.
As for all stores the action topology instance store may consist of multiple different sub-stores 37 in function of the size of the data it needs to store other criteria relevant to the specific purpose of the application using the data processing platform 20.
The fourth logical store 29 of the data access layer 23 is the action model based index store. This store contains all indices needed to describe and persist all the links between all the items present in the other stores of the data access layer 23, making use of their respective identifiers.
A particularly advantageous way of representing and persisting these links in the context of the present disclosure is by using sparse bit matrices. This, because every particular kind of item in the data processing platform 20 may be represented by a specific set of numerical identifiers and since the number of sets is very limited. A sparse bit matrix can be defined and populated for all the pairs of specific identifier sets, expressing for each identifier in the first set whether it is linked or not to each identifier in the second set, by using 0 or 1 Boolean values, without generating significant overhead.
There are specific sets of identifiers for data elements, actions, data categories, topologies, action topology combinations, action topology instances and all necessary positional information may be expressed by using the length of the longest defined topology as an upper boundary.
The action model based index store 29, which also can comprise different sub-stores 38, creates the unique advantage of making it possible to express links between data elements at the moment they are introduced to the data processing platform instead of having to predefine them as is required in most state-of-the art data management systems.
Another unique advantage of the index store 29 is that it allows to query all the data present in the data processing platform without having to know where in the platform same are stored and without having to explicitly join different parts of the data description model as is common practice in state-of-the-art data processing platforms.
Moreover the combination of numerical identifiers, sparse bit matrices and the separation between data elements, descriptive elements and indices enables the data processing platform 20 to execute a number of operations such as data quality control, duplicate data detection, data similarity calculations etcetera, on the data in the system without disclosing or touching the data itself, and just using the knowledge encapsulated in the sets of identifiers and the links between the members of those sets expressed in the sparse bit matrices.
The fourth layer 24 in the figure is the data execution layer of the computer. This layer enables the data processing platform to automatically execute operations to be performed using the data stored and may executed a proper topology comprised of execution categories such as triggering a signal, loading an application, stopping in application, sending data to an external system and any alike as represented by external process 25.
Fig. 3 shows a sample set of data elements, represented by their respective DataElementID as stored in the data element store 26 of the platform 20 of Fig. 2. Fig. 4 shows a sample of actions, represented by their ActionlDs as stored in or retrieved from the action store 34 of Fig. 2. Fig. 5 describes the subject data category, object data category, spatial data category and temporal data category, i.e. represented by the names Who, What, Where and When, respectively, and identified by their unique DataCategorylD, stored in repository or data category store 33 of Fig. 2.
Fig. 6 is a list of examples of topologies and their unique TopologylD. As disclosed, a topology is an ordered list of DataCategorylDs. In the figure, for clarity sake, the DataCategorylDs are also represented by their respective names. See also Fig. 5.
The list in Fig. 6 shows examples of combinations of actions of the plurality of actions 12 - an action represented by a respective unique ActionID - and a topology of the plurality of topologies 13 - a topology represented by a respective unique TopologylD. Each such action topology combination is represented by a unique action topology combination identifier, ActionTopologylD.
An example of action topology instance information, for a particular ActionTopologylnstancelD, is shown in Fig. 8. The instance information in this example comprises a timestamp, i.e. TimeStamp, a status, i.e. StatusID, applying actions, i.e. ApplyingActionlDs and constraining actions, i.e. ConstrainingActionlDs. and is stored in the action topology instances store 28 in Fig. 2. In the list, a '0'-value in the respective ActionlDs represents absence of a respective action for the corresponding position in the applicable topology.
The examples above are, of course, not exhaustive and merely provided for illustration purposes, while the IDs are shown as numerical identifiers. One will appreciate that other types of identifiers may be used for the same purpose.
Links between the respective IDs, expressed in bit matrices in accordance with the present disclosure, are shown in the examples of Figs. 9-12. These matrices shown are just a few of a plurality of matrices or multi-dimensional arrays that can be established based on the data structuring, processing and storage in accordance with the present disclosure. In the naming of the bit matrices, the item first mentioned represents the IDs of the rows and the last mentioned item represents the IDs of the columns. The matrices are stored in the action based index model store 29, as shown in Fig. 2.
The DataElementID to ActionID matrix shown in Fig. 9, expresses associations of data elements, denoted by their respective DataElementID, listed and bold printed in the left most column of the matrix, and actions, denoted by their respective ActionID, listed and bold printed in the upper row of the matrix. In the matrix, a '1'-value indicates that a respective data element is involved in a respective action, and a '0'-value indicates that a respective data element is not involved in a respective action.
The ActionID to TopologylD matrix shown in Fig. 10, expresses combinations of actions, denoted by their respective ActionID, listed and bold printed in the left most column of the matrix, and topologies, denoted by their respective TopologylD, listed and bold printed in the upper row of the matrix. In the matrix, a '1'-value indicates the presence of a respective action and topology combination, and a '0'-value indicates absence of such combination. As can be seen from the matrix, a topology as such is not specific for an action. For example, the different actions 1 and 2 share the same topology 6. Action 4 involves different topologies 1, 2, 3, 4. Such action topology combinations are distinguished from each other by specific action topology combinations.
The DataElementID to DataCategorylD matrix shown in Fig. 11 indicates to what data category or data categories, denoted by their respective DataElementID, listed and bold printed in the top row of the matrix, a particular data element, represented by its DataElementID, listed and bold printed in the left most column of the matric, pertains to. Thus, for example, data element 18 is of the 'What' category, while data element 22 may be both a Who and a What. See also Fig. 5.
The TopologylD to ActionTopologylnstancelD matrix in Fig. 12, shows that multiple action instances may be associated with a respective topology. In the matrix of Fig. 12 topologies are denoted by their respective TopologylD, listed and bold printed in the left most column of the matrix, and action topology instances are denoted by their respective ActionTopologylnstancelD, listed and bold printed in the upper row of the matrix. Again, in the matrix, a '1'-value indicates an association and a '0'-value indicates absence of an association.
The matrix representation shows the flexibility of the disclosed disclosure, as the links in the context of the disclosed disclosure result in sparse bit matrices requiring less storage space. A sparse bit matrix or multi-dimensional array can be defined and populated for all the pairs of specific identifier sets, expressing for each identifier in the first set whether it is linked or not to each identifier in the second set, by using 0 or 1 Boolean values, without generating significant overhead.
A query can be expressed, as shown in Fig. 13, by enumerating the data elements one is looking for. The logical links the user wants to specify between the data elements in the query can be expressed by filling out a simple binary matrix for each of the levels in the descriptive-model (actions, topologies, action-topology-instances).
These binary expression matrices have as many rows as there are data elements in the query. The number of rows in binary expression matrixes is fixed. The first row expresses the logical OR-relationship, the second row expresses the logical AND-relationship and the third row expresses the logical-NOT. A binary one, i.e. a '1'-value, at the corresponding position in the described row means that the query-result needs to fulfil the logical relation between that data element in the query and the other elements for the corresponding querying level. An additional row is provided in which the DataCategorylD for each data element in the query that is of interest to the user may be specified. Zero values in this row mean that any data category associated with the specified data element will be considered a valid result.
One will appreciate that instead of mentioning the data elements themselves, such as "Pete", "Lilly", "Antwerp", for example, the query-description can also start from the respective DataElementlDs of the data elements, in those cases where they are known upfront or the data elements themselves may not be disclosed for security reasons or otherwise.
Queries are resolved easily. In a first step an easy look-up in the data element store 26 is performed to find the IDs of the data elements mentioned as query-data. The second step is to create a query matrix by using the IDs resulting from the first step and the logical model described in the binary expression matrices, to generate the query matrix that can be overlaid with the set of index matrixes describing the links between the data and all descriptive elements. In a third step the set of IDs resulting from the expanding and overlay operations is then used to fetch the actual data elements into the query result.
Fig. 14 shows the addition of an a data category, represented by a DataCategorylD, to an action 12. That is, each action in the entity relation diagram 10 according to Fig. 14 additionally comprises a data category. Assigning a data category to an action provides the complete action to be used as one data element associated with a specific position of a topology in a specific action-topology combination. Expressed in a different way, this means that actions may become part of other actions, which provides a basis for an object-oriented inheritance mechanism or to avoid difficult joins as often needed in relational database queries.
Moreover, this mechanism allows to include actions in actions, which makes the model particularly fit for matching or mapping, combining and integrating complex data from different data sources. These sources can be of any kind or type, provided same represent their data in a structure model, such as a logic data model. Commonly known models to represent data in a structured way are, for example, a relational database model, a graph database, a document database, a key-value store, or, an object database.
Fig. 15 shows an example of a data source containing data 40 structured in accordance with a simple relational data model, developed for storing data about customers 41, products 42, orders 43 and shipments of orders 44. The goal of such a data model is to register which products are ordered by which customer and when they are shipped. Typically these models are constructed to answer questions like: 'which products were ordered by which customers and which of these products have already been shipped to the customer'.
A typical query to be performed on the data 40 would be: "Which products have already been shipped to customer X ?". An example of such a query may look like in the example below:
- SELECT
c.CompanyName, s.ID, p.Name, sp.Quantity, p.Price
- FROM
Customer c
- INNER JOIN Shipment s ON c.ID = s.CustomerlD
- INNER JOIN ShipmentProduct sp ON s.ID = sp.ShipmentID
- INNER JOIN Product p ON p.ID = sp.ProductID
- WHERE
s.ShipmentState = 'OutForDelivery'
Queries like the one above are difficult to write for an average user and need a good understanding of the data model.
The fifth aspect of the present disclosure presents a representation model by which the user gets an overview of the goods per customer that are already shipped, which can just be accessed as a property of a constructor without a need to write specific, ad-hoc queries to access the data of interest.
For completeness sake, besides for storing data about customers 41, products 42, orders 43 and shipments of orders 44, the data model shown in Fig. 15 allows storage of data relating to ordered products 45, shipment orders 46, communication means 47, communication categories 48, customer addresses 49, other addresses 50 and shipment products 51.
The steps according to the fifth aspect of the present disclosure are illustrated in a series of schematic representations, presented in the Figs. 16 - 20, based on the example data illustrated in Fig. 15.
In a first step data subsets, such as represented by reference numerals 41, 42, 43, 44, for example, of the data 40 are to be associated with actions in accordance with the action-based logical data model disclosed by the first aspect of the present disclosure. For the ease of the present explanation actions matching data from an external data source are called 'mapping actions'. These actions are regular actions, that defined in accordance with the present action-based data model, and the data elements these actions group are the structured data subset elements of the respective external data source.
Fig. 16 illustrates an action mapping of the data of one table, i.e. a data subset, in the data model of Fig. 15. Fig. 17 illustrates in similar manner as Fig. 16 a result set of a query shown in Fig. 17, that can be executed on the data model of Fig. 15, and mapped onto an action in accordance with the present disclosure. It will be appreciated by the person skilled in the art that any structured set of information can be mapped to an action.
An action may be composed in the following manner. The identifier of the action is associated with a name for the mapped table or query or, in general, a data subset. The topology associated with the action contains a data category for all columns in the table or in the result set of the query, for example, or for any recurring subpart of an other kind of data subset. The action topology instance will contain the data element identifiers of the specific parts of the mapped data, i. e. the names of the columns in the mapped table or the names chosen for the columns in the query result set.
If the part of the data structure that has to be mapped does not allow for easy association with data categories, one may also pass on the data category associated with the mapping action for each subpart of the mapped data structure. In object oriented data modelling language this would be described as an inheritance mechanism. In accordance with the present disclosure, the mapping actions actually do not directly contain data, but refer to data stored in the externa data source.
Fig. 18 shows further examples of mapping actions that can be created to link or map or integrate data subsets of the database model shown in Fig. 15.
A further step in accordance with the method of the fifth aspect of the present disclosure, comprises the creation of a constructor, which is a special kind of action that consists of a topology of properties of different types. A property has a name, or identifier, associated with a mapping action, and is associated with a position in a constructor topology combination and as such will be associated with the data category of the specific position within the constructor topology combination.
Fig. 19 shows three examples of conceptual constructor definitions. As illustrated, each property refers to an action topology instance identifier or an action topology identifier of a mapping action and, in accordance with the definition of an action, each property is associated with a datatype. This means in practice that a constructor is an action consisting of actions, is associated with a topology of data categories and each data category in the topology is associated with a property. A property then is a name for a link to a specific mapping action and, in accordance with the definition of an action, the name or identifier of each property will be a data element receiving a specific data element identifier. In this example, the data element identifier is special because it refers to the action topology instance identifier associated with the property action of the same type.
Fig. 20 shows an example of how constructors and properties can be represented as instances of a small set of predefined actions. The names of the actions, the definitions of the topologies, can vary from implementation to implementation. In Fig. 20 a representation for constructors and different kinds of properties is disclosed.
In this implementation, the WhoConstructor action is an example of an action that can contain all the definitions of constructors of data category 'who'. Each constructor of data category 'who' can then be represented as an action topology instance of this WhoConstructor action. A specific characteristic of the WhoConstructor action is that a topology associated therewith to represent a specific constructor, will represent all the data categories of the properties the specific constructor comprises of. On top of that, the topology will provide one fixed data category at a specific position, to have a space to represent the name of each property. In the example Fig. 20 it is the first position of the topology and the chosen data category is 'what'.
For the sake of readability, the name of a property in the example is used in the following. In an implemented system, instead of the name the data element identifier of the name of the property will be used as shown in Fig. 8. The other positions and data categories of the topology provide the space to represent the identifiers of the respective property actions, as shown by the lines linking the different parts of the action topology instance of the WhoConstructor action to respectively the DataProperty, the LabelProperty and the ConstructorProperty actions. These actions are predefined in the example, to enable to distinguish between data properties, label properties, and constructor properties.
The action called DataProperty is predefined to represent data associated with data properties. An action called LabelProperty is predefined to represent data associated with label properties and an action called ConstructorProperty is predefined to represent data associated with a property. In this example the three actions all are associated with a topology consisting of two what data categories.
In these three actions, the first position of the topology provides the link to the name of the property. Once again, the name of the property is used for the sake of readability, whereas in practice not the name but the data element identifier of the name will be represented, as shown in Fig. 8.
In the case of a data property, the second position of the topology of the DataProperty action will provide space for the identifier of the specific action topology instance of the mapping action, referenced by the specific data property. In Fig. 19 an example of a data property 'customer' is given. It has the identifier or id 1524 and the data category 'who'. That data property references a specific action topology instance of the mapping action IsCustomer with the identifier or id 19 as can be seen from Fig. 18.
In the case of a label property, the second position of the topology of the LabelProperty action provides space for the identifier of the specific action topology of the mapping action, referenced by the specific label property. Fig. 19 shows multiple examples of such associations. The first one being the label property ContactDetails, that has data category 'what' and refers to action topology id 24, which is the action-topology associated with the mapping action IsCustomerCommunication.
The difference between referencing an action topology instance by its identifier and referencing an action topology identifier is that an action topology instance identifier only references a single specific instance of an action and as such, whereas an action topology references all action topology instances associated therewith. Therefore, a data property may be called a value property in object oriented data modelling terminology and a label property may be considered an array or list property by object oriented analysts, because it references a series of instances of the property.
In the case of a constructor property the second position of the topology of the ConstructorProperty action provides space for the identifier of the specific action topology of the constructor referenced by the specific label property. Fig. 19 shows multiple examples of such associations. The first one being the constructor property Shipments, that has data category 'what' and refers to action topology id 1526, which is the action-topology associated with the constructor ShipmentDetails.
A constructor property allows to embed constructors into other constructors, which allows for very advanced data associations. In object oriented terminology, the constructor property referencing a constructor would be called class inheritance.
The modelling technique described above provides that the data associated with those predefined actions always refers to unique action topologies or action topology instances of mapping actions, and as such indirectly links to data, which allows to represent data in a completely different way without transforming or even touching it, and preparing it for use cases that are completely different then the purpose for which the original, external data model was built. The disclosed mechanism also allows to reuse external data for a variety of purposes without duplicating it, since every use of the data by means of a constructor always refers to mapping actions that only have to be created once.
Fig. 21 shows two examples of actions that can be predefined to describe how properties can be used in an application that uses the disclosed invention to support object oriented data access to all data from different data sources, mapped into an action based data model. This example shows a DataPropertyUsage, that describes how a specific data property can be used as an automated filter to select specific action topologies associated with the action topology identifier of a label property in the same constructor.
The DataPropertyUsage action contains references to the constructor in which the data property is used, the identifier of the property, and the name (once again for the sake of clarity) associated with the topology position in the action topology of the referenced mapping action. It also specifies on which property the data property has to be used as a filter, and 'what' represents the name (once again for the sake of clarity) associated with the action topology position to be filtered.
Fig. 22 also shows a predefined action Propertylteration, describing in what order the topology of the referenced action topology should be iterated by an implementation.
The present disclosure may be practiced otherwise than as specifically described herein, and the above mentioned embodiments and examples are merely intended as an illustration to the skilled reader.
1. A computer implemented and computer controlled method of arranging, in memory, data subsets retrieved in a computer readable format from at least one data source, said data subsets comprising a plurality of data subset elements structured in accordance with a logical data model, for the processing of said data subsets by an action-based logical data model representing data comprising a plurality of data elements, by:
- actions, assigned to data, each action identified by a unique action identifier;
- data categories, including a subject data category, an object data category, a spatial data category and a temporal data category, each data category identified by a unique data category identifier;
- action topology combinations, specifying associations between data elements of data of an action in accordance with a topology comprising an ordered plurality of data categories, each action topology combination identified by a unique action topology identifier;
- instance information, supplemented to an action topology combination, identified by a unique action topology instance identifier, and
- each data element identified by a unique data element identifier,
wherein a computer performing the steps of:
- retrieving, at least one data subset of data provided by a data source, each data subset comprising a plurality of data subset elements, each data subset element represented by a respective data subset element identifier;
- assigning, to each data subset, at least one action represented by a respective action identifier;
- assigning, to each assigned action, a data category of said plurality of data categories, represented by a respective data category identifier, and at least one action topology combination specifying an association between data subset elements of a respective data subset of an assigned action, represented by a respective action topology identifier;
- matching each data subset element of each data subset with a data category of a respective action topology combination assigned to a respective data subset;
- supplementing, from said data source, instance information of a respective data subset to a matched action topology combination, said supplemented action topology combination represented by a respective action topology instance identifier;
- assigning, to said matched action topology combinations supplemented by said instance information, at least one constructor identified by a unique constructor identifier, each constructor comprising at least one property;
- assigning, to each constructor, a data category of said plurality of data categories, represented by a respective data category identifier, and at least one constructor topology combination, identified by a unique constructor topology identifier, said constructor topology combination specifying an ordered plurality of properties of a constructor, a property operating on said matched action topology combinations supplemented by said instance information, each property represented by a unique property identifier, and each property comprising a data category corresponding to a respective data category of said constructor topology combination, and
- presenting structured relations between said data subset elements of said data subsets in accordance with at least one assigned constructor.
2. The method according to Claim 1, wherein said properties include a data property, referring to an action topology instance combination of an assigned action, a label property, referring to an action topology of an assigned action, a calculated property, referring to a data subset of an assigned action, a constructor property, referring to an other constructor, and a function property, referring to an action.
3. The method according to Claim 2, wherein said data property refers to one of an action topology instance combination assigned to a matched data subset at retrieval of said data subset, and an action topology instance combination of an action assigned when applying a constructor.
4. The method according to Claim 1, wherein said step of assigning, to each assigned action, at least one action topology combination specifying an association between data subset elements of a respective data subset of an assigned action, comprises assigning an action topology combination, each data category of said action topology combination being equal to said data category of said assigned action.
5. The method according to Claim 1, wherein arranging, in memory, data retrieved in a computer readable format from at least one data source comprises building, by said computer, a plurality of binary n-dimensional arrays, in particular a plurality of two-dimensional arrays, each array having a unique name and indices formed by respective identifiers, and wherein associations between identifiers are expressed by a binary value, such that presence of an association between identifiers of an array is expressed by a first binary value and absence of a relation between said identifiers of an array is expressed by a second binary value, and in particular wherein said binary values are assigned by said computer to obtain sparse arrays.
6. The method according to Claim 1, wherein arranging, in memory, data retrieved in a computer readable format from at least one data source comprises building, by said computer, at least one of a list of:
- data subset element identifiers and corresponding data subset elements, and
- action topology instance identifiers and corresponding instance information of a data subset.
7. The method according to Claim 1, wherein said instance information of a data subset comprises descriptive information, in particular descriptive information pertaining to at least one data category of an action topology combination, said instance information being structured in accordance with a data structuring format comprised of actions, topologies, action topology combinations, data categories and respective unique identifiers.
8. The method according to Claim 1, wherein data subsets of a data source comprise at least one of:
- a table in a relational database;
- a subgraph in a graph database;
- a document from a document database;
- a set of documents from a document database;
- a list of Key-Value pairs from a Key-Value Store;
- a result set of a query performed at data of a data source.
9. The method according to Claim 1, wherein an action is assigned by said computer using at least one of:
- pre-defined actions stored in an actions repository;
- an action received by said computer, and
- an action identifying algorithm.
10. The method according to Claim 1, wherein an action topology combination is assigned to an action by said computer by retrieving a topology from:
- pre-defined topologies stored at a topologies repository;
- topologies received by said computer, and
- a topology identifying algorithm.
11. The method according to Claim 1, wherein a constructor is assigned by said computer using at least one of:
- pre-defined constructors stored in a constructors repository;
- a constructor received by said computer, and
- a constructor identifying algorithm.
12. The method according to Claim 1, wherein a constructor topology combination is assigned to a constructor by said computer by retrieving a topology from:
- pre-defined topologies stored at a topologies repository;
- topologies received by said computer, and
- a topology identifying algorithm.
13. The method according to Claim 1, wherein a property is represented by an action, each action comprising a data category equal to said data category of said property and an action topology combination comprising an ordered plurality of action topology instance identifiers of matched data subsets and comprising said property identifier.
14. The method according to Claim 13, wherein a constructor is expressed as an instance of an action, said action being a predefined action having a data element comprising said constructor identifier, and an action topology referring to said data categories of properties of said actions corresponding to said constructor, and wherein data elements associated as data with respective topology data categories are action topology instance identifiers of a corresponding action of a respective property.
15. A computer implemented and computer controlled data processing platform, configured for arranging, in memory, data subsets retrieved in a computer readable format from at least one data source, said data subsets comprising a plurality of data subset elements structured in accordance with a logical data model, for the processing of said data subsets by an action-based logical data model representing data comprising a plurality of data elements, by:
- actions, assigned to data, each action identified by a unique action identifier;
- data categories, including a subject data category, an object data category, a spatial data category and a temporal data category, each data category identified by a unique data category identifier;
- action topology combinations, specifying associations between data elements of data of an action in accordance with a topology comprising an ordered plurality of data categories, each action topology combination identified by a unique action topology identifier;
- instance information, supplemented to an action topology combination, identified by a unique action topology instance identifier, and
- each data element identified by a unique data element identifier,
said platform comprising at least one computer and memory configured for performing the steps of:
- retrieving, at least one data subset of data provided by a data source, each data subset comprising a plurality of data subset elements, each data subset element represented by a respective data subset element identifier;
- assigning, to each data subset, at least one action represented by a respective action identifier;
- assigning, to each assigned action, a data category of said plurality of data categories, represented by a respective data category identifier, and at least one action topology combination specifying an association between data subset elements of a respective data subset of an assigned action, represented by a respective action topology identifier;
- matching each data subset element of each data subset with a data category of a respective action topology combination assigned to a respective data subset;
- supplementing, from said data source, instance information of a respective data subset to a matched action topology combination, said supplemented action topology combination represented by a respective action topology instance identifier;
- assigning, to said matched action topology combinations supplemented by said instance information, at least one constructor identified by a unique constructor identifier, each constructor comprising at least one property;
- assigning, to each constructor, a data category of said plurality of data categories, represented by a respective data category identifier, and at least one constructor topology combination, identified by a unique constructor topology identifier, said constructor topology combination specifying an ordered plurality of properties of a constructor, a property operating on said matched action topology combinations supplemented by said instance information, each property represented by a unique property identifier, and each property comprising a data category corresponding to a respective data category of said constructor topology combination, and
- presenting structured relations between said data subset elements of said data subsets in accordance with at least one assigned constructor.
16. The computer implemented and computer controlled data processing platform according to Claim 15, wherein said structured relations are presented by at least one of displaying said structured relations at an electronic display, and storing said structured relations in a computer readable form at a storage engine.
17. A computer program product, comprising program code means stored on a non-transitory computer readable medium, said program code means arranged to perform the method according to Claim 1, when said program code is executed by a computer.
18. A computer program product, comprising program code means stored on a non-transitory computer readable medium, said program code means arranged for being integrated in a computer application for joint execution of said computer application and said program code to perform the method according to Claim 1, when said program code and said computer application is executed by a computer.
62225EP9-3
EP
20200462.8
Dynactionize N.V.
2
BE
20210301
G06F
US
2007276787
A1
PIEDMONTE CHRISTOPHER M [US]
20071129
X
1-18
* abstract *
* paragraph [0007] - paragraph [0008] *
* paragraph [0033] *
WO
2017167628
A1
KONINKLIJKE PHILIPS NV [NL]
20171005
X
1-18
* abstract *
* page 4, line 3 - line 22 *
* page 8, line 5 - line 28 *
* page 9, line 21 - page 10, line 10 *
EP
2874080
A1
SAP SE [DE]
20150520
A
1-18
* abstract *
* paragraph [0007] *
* paragraph [0010] - paragraph [0012] *
* paragraph [0024] - paragraph [0029] *
Pose Rodríguez, J
Berlin
20210219
US
2007276787
A1
20071129
CN
101479697
A
20090708
US
2007276787
A1
20071129
WO
2017167628
A1
20171005
NONE
EP
2874080
A1
20150520
EP
2874080
A1
20150520
US
2015142836
A1
20150521