* ned.freed@mrochek.com wrote:
The fact that these subtypes of text are in widespread use leads me to suggest an alternate approach: Why not register them, but mark them as obsolete with a pointer to the type that should be used instead? The registration will then serve two purposes: To make it clear what the types contain when they are used and to also make it clear they should no longer be used.
The draft states that text/ecmascript is expected to be deprecated in a future version of the document.
There is no defined process for deprecation of a media type. The closest thing we have is marking the type as being obsolete, and the media types registration procedure specifically calls for this to be done "when use of the type is no longer appropriate". This IMO matches the present case exactly.
This basically means text/ecmascript should not be used in a context where application/ecmascript could be used as well. Marking text/ecmascript as obsolete does not allow making such a distinction as far as I can tell,
Actually, it makes exactly this distinction, one that deprecation does not make.
and I think the registration should acknowledge that users of the types do not have much of a choice at the moment.
That's exactly what registering the types as obsolete does. Ned