. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 8.3. Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . apache.unomi.api.Event,org.apache.unomi.api.Profile,org.apache.unomi.api.Session,org.apache .unomi.api.Item,org.apache.unomi.api.CustomItem,ognl.*,java.lang.Object,java.util.Map,java.lang.I nteger,org.mvel2 it might be due to this restrictive configuration. If you need, for example when adding a custom item type, to adjust these, please be careful as scripts may be called directly from the context.json

declaration, we’re referring to an already existing schema (https://unomi.apache.org/schemas/json/item/1-0-0) to validate the "source" and "target" properties. Apache Unomi ships with a set of predefined "$ref" : "https://unomi.apache.org/schemas/json/item/1-0-0" }, "target" : { "$ref" : "https://unomi.apache.org/schemas/json/item/1-0-0" }, "properties": { apache.unomi.api.Event,org.apache.unomi.api.Profile,org.apache.unomi.api.Session,org.apache.unomi.api.Item,org.apach e.unomi.api.CustomItem,ognl.*,java.lang.Object,java.util.Map,java.util.HashMap,java.lang

algorithms. 1.1.1. ITEMS AND TYPES Unomi structures the information it collects using the concept of Item which provides the base information (an identifier and a type) the context server needs to process in the form of key-value pairs. These properties are further defined by the Item’s type definition which explicits the Item’s structure and semantics. By defining new types, users specify which properties server to filter data to only see relevant data. Base Item structure: { "itemType": item>, "scope": , "itemId": <item identifier>, "properties": } Some