Discussion: Choosing routes for tag related resources

[NamesJ]

Direct routes for tags

/api/tag [DELETE] : delete a tag directly
/api/tag [GET] : get tag info directly
/api/tag [POST] : create a tag directly

Entity-specific paths (i.e. /api/<entity_type>/tag):

/api/offer/tag [DELETE] : remove a tag from an offer
/api/offer/tag [POST] : add a tag to an offer

/api/user/tag [DELETE] : remove a tag from a user
/api/user/tag [POST] : add a tag to a user

Note: I think the above convention for entity specific resources is a good fit as it matches the expectations of the average client (i.e. a normal user). Examples: a user wants to add a tag to their account, or wants to delete a tag from their offer, etc.

Route for searching tags directly:
/api/tag/search [GET]