{
  "context": "This criteria evaluates the engineer's ability to use dnslib's zone file parsing capabilities, including RR.fromZone() for parsing zone data, handling of $TTL and $ORIGIN directives, and extracting information from DNS resource records.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Uses RR.fromZone()",
      "description": "Uses the RR.fromZone() method to parse zone file content into resource record objects. This is the primary API for zone file parsing in dnslib.",
      "max_score": 30
    },
    {
      "name": "Handles origin parameter",
      "description": "Properly passes the origin parameter to RR.fromZone() or ZoneParser when provided, enabling correct handling of relative domain names in zone files.",
      "max_score": 15
    },
    {
      "name": "Handles TTL parameter",
      "description": "Properly passes the ttl parameter to RR.fromZone() or ZoneParser when provided, enabling correct default TTL values for records.",
      "max_score": 15
    },
    {
      "name": "Extracts record types",
      "description": "Accesses the rtype attribute or uses the QTYPE mapping to determine the type of each resource record (e.g., A, AAAA, MX, TXT, CNAME).",
      "max_score": 15
    },
    {
      "name": "Extracts domain names",
      "description": "Accesses the rname attribute of RR objects to extract domain names from resource records.",
      "max_score": 10
    },
    {
      "name": "Handles parsing errors",
      "description": "Catches and handles exceptions that may be raised during zone file parsing when invalid syntax is encountered.",
      "max_score": 10
    },
    {
      "name": "Returns correct types",
      "description": "Returns the data structures specified in the API (list of records from parse_zone_file, dict with 'valid' and 'errors' keys from validate_zone_records, dict with 'record_counts' and 'unique_domains' from generate_zone_summary).",
      "max_score": 5
    }
  ]
}