01 Data in StreamPipes | Event Properties

How Data is handled in StreamPipes

Real-time Example Primitive

Real-time Example List

Data Layer

Stored as a LinkedTreeMap:

A map of comparable keys to values. Unlike `TreeMap`, this class uses insertion order for iteration order. Comparison order is only used as an optimization for efficient insertion and removal.

key: s0::name
value: value

Time

Timestamp is always required → See Time in StreamPipes

is stored as Unix Timestamp.

What happens if YYY-MM-DD as data sourceo be converted internally to Unix timestamp?

Description Layer

Event schema; describes each individual attributes of an event. The three most important and required fields are:

• Runtime Name. The runtime name indicates the key of the property at runtime, e.g., if our JSON message contains a structure such as {"plateNumber" : "KA-F 123"}, the runtime name must be plateNumber.

• Runtime Type. An event property must have a primitive type (we will later see how to model more complex properties such as lists and nested properties). The type must be an instance of XMLSchema primitives, however, the SDK provides convenience methods to provide the property type.

• Domain Property. The domain property indicates the semantics of the event property. For instance, the latitude property is linked to the http://www.w3.org/2003/01/geo/wgs84_pos#lat property of the WGS84 vocabulary. The domain property should be an URI as part of an existing or domain-specific vocabulary. The SDK provides convenience methods for popular vocabularies (e.g., Schema.org, Dolce or WGS84).