. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 8.4. Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . http://localhost:8181/cxs/rules \ --user karaf:karaf \ -H "Content-Type: application/json" \ -d @- <<'EOF' { "metadata": { "id": "setContactInfo", "name": "Copy the received contact info to the current profile" http://localhost:8181/cxs/rules \ --user karaf:karaf \ -H "Content-Type: application/json" \ -d @- <<'EOF' { "metadata": { "id": "exampleEventCopy", "name": "Example Copy Event to Profile", "description":

--header 'Content-Type: application/json' \ --data-raw '{ "itemId": "unomi-tracker-test", "metadata": { "id": "unomi-tracker-test", "name": "Unomi tracker Test Scope" } }' SHELL 'Authorization: Basic a2FyYWY6a2FyYWY=' \ --header 'Content-Type: application/json' \ --data-raw '{ "metadata": { "id": "viewEventRule", "name": "View event rule", "description": "Increments http://localhost:8181/cxs/rules \ --user karaf:karaf \ -H "Content-Type: application/json" \ --data-raw '{ "metadata": { "id": "setContactInfo", "name": "Copy the received contact info to the current profile"

Example JSON type definition: { "itemId": "tweetNb", "itemType": "propertyType", "metadata": { "id": "tweetNb", "name": "tweetNb", "tags": ["social"] }, "target": leverages OSGi to support plugins. A Unomi plugin is, thus, an OSGi bundle specifying some specific metadata to tell Unomi the kind of entities it provides. A plugin can provide the following entities to with Unomi by providing raw, uninterpreted contextual data in the form of events and associated metadata. That contextual data is then processed by the context server to be fed to clients once actionable