. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 4. Profile import & export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 4.1.1. Import API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 4.2.1. Export API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

functionalities and robustness of the product. The introduction of tighter data validation with JSON Schemas required some changes in the product data model, which presented an opportunity for noticeable improvements JSON Schema (https://json-schema.org/specification.html) for all of its publicly exposed endpoints. Data received by Apache Unomi 2 will first be validated against a known schema to make sure it complies corresponding section of the documentation. 1.1.4. UPDATED DATA MODEL The introduction of JSON schema required us to modify Apache Unomi data model, One of the key differences is the removal of open maps

the base information (an identifier and a type) the context server needs to process and store the data. Items are persisted according to their type (structure) and identifier (identity). This base structure identifier and usually represents an application or set of applications from which Unomi gathers data, depending on the desired analysis granularity. In the context of web sites, a scope could, for example related sites being analyzed. Scopes allow clients accessing the context server to filter data to only see relevant data. Base Item structure: { "itemType": , "scope": , "itemId":