core 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 "apache" scope can be created using the following API call. 1.1.3. JSON SCHEMAS Apache Unomi 2 introduces support for JSON Schema (https://json-schema.org/specification.html) for all of its publicly exposed registered. More details about JSON Schemas implementation are available in the corresponding section of the documentation. 1.1.4. UPDATED DATA MODEL The introduction of JSON schema required us to modify

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.3.2. Retrieving a context as a JSON object.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . list of available RESTful services or retrieve an initial context at http://localhost:8181/context.json (which isn’t very useful at this point). You can now find an introduction page at the following location: way to retrieve profile data for the current profile is to simply send a request to the /context.json endpoint. However you will need to send a body along with that request. Here’s an example: Here

profiles) they can be affected to. For example, the following Apache Unomi 1.1.x - Documentation - 1 JSON document can be passed to Unomi to declare a new property type identified (and named) tweetNb, tagged tagged with the social tag, targeting profiles and using the integer value type. Example JSON type definition: { "itemId": "tweetNb", "itemType": "propertyType", "metadata": { "id": for example when a rule is triggered. Events are sent to Unomi from client applications using the JSON format and a typical page view event from a web site could look something like the following: Example