THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| No Format |
|---|
+-----+-----+-----+-------+-----------------------+
| 'A' | 'M' | '1' |'g/c/i'| seq |
+-----+-----+-----+-------+-----------------------+--------+
| packageName (str8) |
+----------------------------------------------------------+
| className (str8) |
+----------------------------------------------------------+
| class hash (bin128) |
+-----+-----+-----+-----+-----+-----+-----+-----+----------+
| timestamp of current sample (datetime) |
+-----+-----+-----+-----+-----+-----+-----+-----+
| time object was created (datetime) |
+-----+-----+-----+-----+-----+-----+-----+-----+
| time object was deleted (datetime) |
+-----+-----+-----+-----+-----+-----+-----+-----+
| objectId (uint64) |
+-----+-----+-----+-----+-----+-----+-----+-----+
| presence bitmasks (0 or more uint8 fields) |
+-----+-----+-----+-----+-----+-----+-----+-----+------------------------+
| config/inst values (in schema order) |
+------------------------------------------------------------------------+
|
All timestamps are uint64 values representing nanoseconds since the epoch (January 1, 1970). The objectId is a uint64 value that uniquely identifies this object instance.
If any of the properties in the object are defined as optional, there will be 1 or more "presence bitmask" octets. There are as many octets as are needed to provide one bit per optional property. The bits are assigned to the optional properties in schema order (first octet first, lowest order bit first).
For example: If there are two optional properties in the schema called "option1" and "option2" (defined in that order), there will be one presence bitmask octet and the bits will be assigned as bit 0 controls option1 and bit 1 controls option2.
If the bit for a particular optional property is set (1), the property will be encoded normally in the "values" portion of the message. If the bit is clear (0), the property will be omitted from the list of encoded values and will be considered "NULL" or "not present".
The element values are encoded by their type into the message in the order in which they appeared in the schema message.
...