# Filled Date Interpretation Card

All records below are invented teaching inputs for a fictional craft-session article. They are not observed events, publication timestamps or an automatic date conversion.

Calendar for supported records: Gregorian. Supplied order for supported numeric values: year-month-day. Chosen English prose style: month name, day, four-digit year.

| Record | Original supplied value | Established meaning | Normalized value | Chosen English display | Decision |
| --- | --- | --- | --- | --- | --- |
| D01 | `2026-04-03` | Gregorian year 2026, month April, day 3; year-month-day order explicitly supplied | `2026-04-03` | April 3, 2026 | Supported; use this display |
| D02 | `2026-03-04` | Gregorian year 2026, month March, day 4; year-month-day order explicitly supplied | `2026-03-04` | March 4, 2026 | Supported; use this display |
| D03 | `03/04/26` | Unknown; calendar, numeric order and full year not supplied | None; unknown | None; unknown | Check the original record; do not guess from article language, house style or browser preference |

The paired CSV has exactly these three records. Blank normalized/display fields on D03 mean unknown, not a missing value to fill with a guess.

## Separate supplied range

This is an additional fictional workshop-span input, not a fourth row in the three-record CSV.

| Endpoint | Supplied Gregorian date, declared year-month-day order | Established meaning | English display |
| --- | --- | --- | --- |
| Start | `2026-04-03` | April 3, 2026 | April 3, 2026 |
| End | `2026-04-05` | April 5, 2026 | April 5, 2026 |

Completed span: **April 3 to April 5, 2026**. Keep both endpoint records when shortening a display.

## Reuse for an actual date

- Original value, copied exactly:
- Source location and any explicit meaning supplied there:
- Calendar, numeric order and full year, or unknown for each missing part:
- Supported normalized date, or unknown:
- Chosen prose display, or unresolved source string:
- For a span, separate supported start and end:
- Comparison outcome: every displayed day, month and year matches the source, or stop to resolve missing meaning.

If a record remains unresolved, a truthful statement is: The note contains `03/04/26`; the date has not been established. Do not turn that source string into a claimed event date.

## Guidance and limits

W3C's date-format guidance discusses numeric ambiguity, explicit month names, four-digit Gregorian years, and tradeoffs of a year-month-day form: https://www.w3.org/International/questions/qa-date-format

The card's US prose order is a declared house choice. It is not a W3C mandate or a claim of current ISO-standard compliance. This record does not convert calendars, determine time zones or establish parser, spreadsheet or CMS behavior.