Message Format SIG
Charter
To define:
- the representation of message properties as set by end user applications for the purpose of processing by SQL92 message filters/selectors (which are a part of AMQP1.0)
- the logical type system of these properties
- the physical encoding of these properties
- the ability to use this encoding scheme for application message content; to be used for (but not limited to) a practical format that AMQP management can use this format for management commands
- approach to forward and backwards compatibility (AMQP0.9/0.10 etc)
Members
- Robert Godfrey - JPMorgan
- Rafi Schloming - Red Hat
- Robert Greig - Barclays
- David Ingham / Cliff Jansen - Microsoft
- Shawn McAlister - Solace
Logical Message
Logical Type System
Canonical Message Encoding
Must be archive quality, capable of standing alone and being decoded without access to message specific logic.
Name:Type:Value 3-tuples.
Message Signing
Application Properties must be encoded in canonical form if they will be signed by the sender.
If the Properties are not signed, an optimised encoding may be considered.
Optimised Transport Encoding
Backwards Compatibility
Language Mapping
Internal Transport Types and Application Message Types
No relationship.