Add filename date requirement (yyyymmdd_) for request files

Author: wolfmcnally

.github/scripts/validate_community_kv.py

@@ -14,6 +14,7 @@
 import re
 import sys
 from dataclasses import dataclass, field
+from datetime import datetime, timedelta, timezone
 from pathlib import Path
 from typing import Any
 
@@ -52,6 +53,7 @@
 }
 
 CANONICAL_NAME_PATTERN = re.compile(r"^[a-zA-Z][a-zA-Z0-9_]*$")
+FILENAME_DATE_PATTERN = re.compile(r"^(\d{8})_.*\.json$")
 VALID_TYPES = {"class", "property", "datatype", "constant"}
 MIN_CODEPOINT = 100000
 
@@ -346,6 +348,48 @@ def validate_name_uniqueness_within_request(
             seen_names[name] = i
 
 
+def validate_filename_date(file_path: Path, result: ValidationResult) -> bool:
+    """V-006: Filename must start with date in yyyymmdd_ format (±1 day tolerance)."""
+    filename = file_path.name
+    
+    # Skip the example template
+    if filename.startswith("_"):
+        return True
+    
+    match = FILENAME_DATE_PATTERN.match(filename)
+    if not match:
+        result.add_error(
+            "V-006",
+            str(file_path),
+            f"Filename must start with date in yyyymmdd_ format (e.g., 20260107_myrequest.json), got: {filename}",
+        )
+        return False
+    
+    date_str = match.group(1)
+    try:
+        file_date = datetime.strptime(date_str, "%Y%m%d").date()
+    except ValueError:
+        result.add_error(
+            "V-006",
+            str(file_path),
+            f"Invalid date in filename: {date_str}",
+        )
+        return False
+    
+    # Allow ±1 day tolerance for timezone differences
+    today = datetime.now(timezone.utc).date()
+    delta = abs((file_date - today).days)
+    if delta > 1:
+        result.add_error(
+            "V-006",
+            str(file_path),
+            f"Filename date {date_str} is more than 1 day from today ({today.strftime('%Y%m%d')})",
+        )
+        return False
+    
+    return True
+
+
 def validate_request_file(
     file_path: Path,
     assigned_codepoints: set[int],
@@ -354,6 +398,9 @@ def validate_request_file(
     result: ValidationResult,
 ):
     """Validate a single request file against all rules."""
+    # V-006: Filename date format
+    validate_filename_date(file_path, result)
+
     # V-001: Parse JSON
     data = validate_json_syntax(file_path, result)
     if data is None:

community-known-values/README.md

@@ -4,7 +4,7 @@ This directory manages community-submitted Known Value assignments. Known Values
 
 ## How to Submit a Request
 
-1. **Create a JSON file** in the `requests/` directory following the naming convention: `<submitter>_<description>.json`
+1. **Create a JSON file** in the `requests/` directory following the naming convention: `yyyymmdd_<description>.json` (e.g., `20260107_myproject.json`)
 2. **Choose your code points** — each entry must specify a `codepoint` value ≥ 100,000 that is not already assigned
 3. **Submit a Pull Request** with your request file(s)
 

community-known-values/Spec.md

@@ -38,15 +38,19 @@ community-known-values/requests/
 
 ### 2.2 File Naming Convention
 
-Request files should follow the pattern:
+Request files must follow the pattern:
 
 ```
-<submitter>_<short_description>.json
+yyyymmdd_<short_description>.json
 ```
 
+Where `yyyymmdd` is the submission date (e.g., `20260107` for January 7, 2026). This ensures request files are sorted chronologically.
+
 Examples:
-- `alice_credential_types.json`
-- `myorg_payment_terms.json`
+- `20260107_credential_types.json`
+- `20260115_payment_terms.json`
+
+**Note:** The date is validated with ±1 day tolerance to account for timezone differences.
 
 ### 2.3 JSON Schema
 
@@ -170,6 +174,7 @@ The workflow must validate each request against the following rules. A PR is rej
 | V-003   | `canonical_name` must match `^[a-zA-Z][a-zA-Z0-9_]*$`              |
 | V-004   | `type` must be one of: `class`, `property`, `datatype`, `constant` |
 | V-005   | `description` must be at least 10 characters                       |
+| V-006   | Filename must start with date in `yyyymmdd_` format (±1 day)       |
 
 ### 3.2 Code Point Rules