> I don't think the versioning data nodes is a good idea. > I have seen entire REST APIs be versioned, but not individual parameters > within the API.
FWIW, I have seen individual resources versioned within a REST API, in lieu of a version number in the beginning of the URL. The REST API presented resources for versioned "objects", each having a distinct media type for content negotiation (e.g., application/vnd.<company>.<object>+[xml/json];v=2). Clients asked for what they could support (including older versions, in case the server didn't support the latest). Server's up/down-converted objects through a chain of converters. Each release only had converters to/from the previous release, but only for the objects that changed. It worked well. The API was stable. Clients did not have to support all the new object versions in one go. Incremental transition was common. Kent
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
