> Consider GData apps. Their docs aren't clear (tsk, tsk!) about the > use of a media type when inserting entries[1], but if they're doing it > properly then their services should be keying off of > "application/atom+xml", and so will break if that's changed. >
And? Should a status quo be better on the long term? > Other server implementations should have the same issue, of course. So please explain me what a server currently does upon receiving an Atom feed on a POST to a collection that only (app:)accept (atom:)entry(ies)? Returning a 415 error code seems like the wrong option since the media-type is perfectly valid. So what should servers do? Should they pick-up randomly one of the entries part of the feed? How should UA deal with the returned message? > >> So I'm for James' option B) >> application/atom-entry+xml > > I'm -1 on that, but +1 on the type parameter. > I'm still +1 on the new media-type and +0.5 on the parameter type option. - Sylvain
