The OpenMessaging Community has recently approved and submitted the specification for 30-days public:
OpenMessaging Specification Version: 1.0.0-preview
2018/09/05
OpenMessaging is vendor-neutral and language-independent, provides industry guidelines for areas of finance, e-commerce, IoT and big-data, and aimed to develop messaging and streaming applications across heterogeneous systems and platforms.
- Changed OpenMessaging model to queue based model. Queue based model is more flexible than the previous model, and queue is a logic destination of messaging.
- Added a type system.
- Made the definition of message schema, improved the message attribute definition.
More details can be found: spec.
- Removed some unclear routing method in resourceManager interface, and replaced it by more clearly defined routing and filtering operations.
- Merged pullconsumer and pushconsumer interface.
- Merged BatchProducer and Producer interface.
- Defined error codes and openmessaging exceptions.
- Temporarily removed the Streaming related interface.
- Redefined the transaction interface.
- Modified message interface, removed key-value header and added a Header interface.
- Removed most of the key-value attributes.
- Renamed some interfaces.
More details can be found: API