Service Message Metadata

The group discussed message metadata for routing/filtering purposes

• During a recent trial SWIM participants had specified a particular way of using/encoding the AMPQ 1.0 application-properties to deal with the routing/filtering to relevant stakeholders without introducing custom code into the XML data stored in the body of the messages.

• We should explore the need to
  
  

  • add a section to the Pub/Sub implementation guidance on “How to use the AMQP message”

    • application.properties is AMQP specific

  • add best practice along the lines of “use protocol means to facilitate information distribution without having to rely on parsing the payload” while remaining protocol agnostic at standard level

  • add a field to service description to cover this information.