RE: text/xml for SOAP is incorrect

> -----Original Message-----
> From: David Orchard [mailto:orchard@pacificspirit.com]

> [...] So should the name be 
> application/getStockTicker+SAML10+crypto+dsig+soap+xml?   
> We're going to have to crack the message to get the information we need 
> anyways, so let's not warp content type just for our particular need.

You don't have to use a single name ('content-type') to encapsulate all the
values.
SOAP should have a defined mechanism for identifying within the Envelope
these values that you may want to route.

There should also be a binding specific way to identify these outside the
XML envelope - for those who believe this is the way to rapid/efficient
parsing and routing. For example, in HTTP, define new headers or use the
excellent suggestion from Graham K. (from RFC 2912)
 Content-features: (schema="http:/www.example.com/Schema-name")

Just as HTTP has headers to identify the content-encoding, etc. of the HTTP
message itself, this HTTP header can be used to identify the features
(encryption, schema/model, method, etc.) of the content specific message
within the entity body. 

This would be different for each binding, but MIME based bindings (HTTP,
SMTP) may be similar.

mike