{
  "context": "This criteria evaluates how well the engineer uses the oauth-sign package to handle international characters and Unicode content in OAuth 1.0 signatures. The focus is on proper usage of the package's encoding and signing functions to ensure non-ASCII characters are correctly processed in OAuth authentication flows.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Uses hmacsign function",
      "description": "Uses oauth-sign's hmacsign function to generate HMAC-SHA1 signatures with the correct parameters: httpMethod, base_uri, params object, consumer_secret, and token_secret",
      "max_score": 30
    },
    {
      "name": "Proper parameter structure",
      "description": "Passes parameters (including OAuth parameters and status text with Unicode) as a properly structured object to the signing function, ensuring all parameters are included in the signature base string",
      "max_score": 20
    },
    {
      "name": "RFC 3986 encoding",
      "description": "Uses oauth-sign's rfc3986 function to properly encode Unicode characters in parameter values, or relies on the package's internal encoding to handle international characters correctly",
      "max_score": 25
    },
    {
      "name": "Correct secrets usage",
      "description": "Correctly passes the consumer_secret ('consumer_secret_123') and token_secret ('token_secret_456') to the signing function in the proper parameter positions",
      "max_score": 15
    },
    {
      "name": "Handles all test cases",
      "description": "The implementation successfully generates valid signatures for all Unicode test scenarios: basic English, Japanese characters, emoji, and Arabic text",
      "max_score": 10
    }
  ]
}