Release log

Summary :

The key elements to this release are a major breaking change to the tag type referencing in data / alarm message structures, and multiple corrections / consistency checks on json element data types in the schema, allowing better automated testing of messages.

See here for Tickets

Compatibility :

• this version introduces BREAKING CHANGES and is not compatible with the previous version

Updates / enhancements :

• Ticket #51 : Data type enhancements. Types ( ai, bi, ao, bo, c etc. ) are now 1st class entities and not attributes of a point. For example :
  • from : {“p”: [{“n”: “ai:1”,”v”: [10],”q”: [192],”ts”: [1728886224273]},
  • to : {“p”: [{“ai”: 1,”v”: [10],”q”: [192],”ts”: [1728886224273]},
• Ticket #45 : New ‘WhenUnableToRead‘ action on a point
• Ticket #44 : all times are now consistently in milliseconds from Epoch
• Various minor protocol document enhancements

Bug Fixes :

• Ticket #35 / #18 : corrections on data types for various message fields
• Various minor protocol document corrections

Deprecations and Removals :

• –

Summary :

This release consisted of a large number of detail changes, developed as a result of the various plugfests and one-to-one vendor tests using version 1.0, and moved the protocol from its original ‘prototyping / proof of concept’ release 1.0, to a more robust, proven implementation.

See here for Tickets

Compatibility:

• this version introduces BREAKING CHANGES and is not compatible with the previous version

Updates:

• various updates after multiple plugfests / workshops

Bug Fixes:

• –

Deprecations and Removals:

• –

Initial release for prototyping, proof of concepts etc.