> I'm not following anything you've said about "content types".
Which amply demonstrates your complete lack of understanding of the subject "pontificate" about.
edit: you can downvote me all you want, does not change that fact. Here's what Fieldings has to say on the subject:
> A REST API should spend almost all of its descriptive effort in defining the media type(s) used for representing resources and driving application state, or in defining extended relation names and/or hypertext-enabled mark-up for existing standard media types. Any effort spent describing what methods to use on what URIs of interest should be entirely defined within the scope of the processing rules for a media type (and, in most cases, already defined by existing media types).
(I used "content types" for his "media types", that's about it).
Which amply demonstrates your complete lack of understanding of the subject "pontificate" about.
edit: you can downvote me all you want, does not change that fact. Here's what Fieldings has to say on the subject:
> A REST API should spend almost all of its descriptive effort in defining the media type(s) used for representing resources and driving application state, or in defining extended relation names and/or hypertext-enabled mark-up for existing standard media types. Any effort spent describing what methods to use on what URIs of interest should be entirely defined within the scope of the processing rules for a media type (and, in most cases, already defined by existing media types).
(I used "content types" for his "media types", that's about it).