Additions to Chemical MIME Types

1. That a reasonably permanent source of information on the type proposed be indicated. This could be a formally published paper, or a URL pointer.
2. That a contact person or organisation for the proposal be clearly identified.
3. That you post your proposal to chemime@ic.ac.uk for discussion.
4. Several actions would then result;
   • A. A consensus to adopt the type in the draft to be presented to IUPAC and IETF
   • B. Agreement that the type is not put forward for "standards track" but will remain an "experimental" or "bilateral" type. This might be most appropriate for proprietary types, or less general types.
   • C. The proposal is not accepted, and the designation "chemical MIME" could not be applied.
   • We need to define an unambiguous mechanism for distinguishing between types A and B. The long term strategy is that chemical/foo (without the "x") is used for a ratified standard via IETF and chemical/x-foo (with the "x", as an experimental type) for proposed but unratified types, but this will depend on IETF accepting a primary chemical type (currently not yet acomplished).