> I hate to say it but your wrong Brandon. The content-type of a file > indicates what the file really is, independent of its encoding. Read the > HTTP spec some time. (Yes I know, not everyone is a web browser, don't > try that argument, but its not just specifying web browsers).
I see no relavence whatsoever of the HTTP spec to our metadata spec since our metadata spec is not based on HTTP. Our metadata spec does not, in fact, have anything to do with the HTTP spec whatsoever. I see no benefit to adding a ContentEncoding field which is not equally satisfied by adding a ContentDecoding field. Additionally, a ContentDecoding field allows for clients to optionally support it rather than being required to.
