Decide and document how to handle vendor properties for content-type and content-encoding

Came from large discussion around wd6 section 4 on 06-October-2015. What are the valid combinations for content type and encoding, does the JMS client act on them or report them, how to design such that a non-JMS and a JMS participant can communicate common use cases (e.g. text message, in json or xml format).