James M Snell wrote:
The key problem I have with the ;type=param is that it's optional and
likely to be ignored by a good number of implementations (which ends up
buying us nothing in terms of interop). A separate media type is less
ideal but has greater practical value in that it addresses the problem
immediately.
Understood.
I don't think, however, that a separate media type for Entry Documents
will solve more problems than it causes:
Applications which adhere to RFC 4287 and accept both Feed and Entry
Documents labeled as "application/atom+xml" won't recognize
"application/atomentry+xml"; they will have to be updated.
But, honestly, I would rather see those buggy applications updated which
break whenever they encounter an Entry Document labeled correctly as
"application/atom+xml". That's a bug waiting to be fixed anyway, whether
we immediately deprecate the labeling of Entry Documents
"application/atom+xml" or not; some Entry Documents have already escaped
into the wild.
Regards,
Andreas Sewe
