anchor.diff:      {[{<<"error">>, [<<"name and clientname must match">>]}]};
   malformed_request_message({bad_client_name, Name, Pattern}, _Req, _State) ->
       {[{<<"error">>, [iolist_to_binary(["Invalid client name '", Name,
  -				       "' using regex: '", Pattern, "'."])]}]};
  +                                       "' using regex: '", Pattern, "'."])]}]};
   
   %% Not sure if we want to be this specific, or just want to fold this into an 'invalid JSON'
   %% case.  At any rate, here it is.
  
positive.code:     {[{<<"error">>, [iolist_to_binary(["Field '", Field, "' contains invalid run lists"])]}]};
  malformed_request_message(invalid_num_versions, _Req, _State) ->
      {[{<<"error">>, [<<"You have requested an invalid number of versions (x >= 0 || 'all')">>]}]};
  malformed_request_message(Reason, Req, #base_state{resource_mod=Mod}=State) ->
      Mod:malformed_request_message(Reason, Req, State).
  
  forbidden(Req, #base_state{resource_mod=Mod}=State) ->
      %% For now we call auth_info because currently need the side-effect of looking up the
  
negative.code: %% "Grab Bag" functions that will also need to be implemented by other base resources
  -export([check_cookbook_authz/3,
           delete_object/3]).
  
  
  %% Can't use callback specs to generate behaviour_info because webmachine.hrl
  %% contains a function definition.
  