Description
Format a validated proleptic Gregorian iCalendar basic date with year 1–9999; no time zone or floating date-time inference.
iCalendar separates content-line framing, property values, parameters and component nesting. TEXT escaping protects separators, while line folding is based on encoded octets. DATE, floating time, UTC and named-zone representations carry different information; a token-level operation does not resolve a timezone or expand recurrence rules.1
Format a validated proleptic Gregorian iCalendar basic date with year 1–9999; no time zone or floating date-time inference.
When to use this tool
Use this tool to format a validated proleptic Gregorian iCalendar basic date with year 1–9999; no time zone or floating date-time inference.
How to use the tool and how it works
- Enter year, month, day using the field definitions below.
- Run the operation. Correct input errors before interpreting an output.
- Read result.token. Use the ordering, boundary rules and absence conditions described below.
Validate a Gregorian date with year 1–9999 and format zero-padded YYYYMMDD.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| year | Gregorian year 1–9999. | A finite safe integer within the operation’s stated bounds. |
| month | Gregorian month 1–12. | A finite safe integer within the operation’s stated bounds. |
| day | Day valid for the supplied month and Gregorian leap-year rule. | A finite safe integer within the operation’s stated bounds. |
| Output field | Interpretation |
|---|---|
| result | Object containing the named fields below. |
| result.token | Formatted basic date/time token. |
{
"input": {
"year": 2024,
"month": 2,
"day": 29
},
"output": {
"result": {
"token": "20240229"
}
}
}Limitations and assumptions
- There is no timestamp or timezone component and no automatic date normalization.
- Content spans use zero-based UTF-16 offsets; fold limits use UTF-8 bytes including the continuation space. Token helpers handle the stated subset only, without a timezone database, recurrence engine or calendar import.
- Every declared top-level input field is required and unexpected fields are rejected. Ordinary strings are limited to 8,192 UTF-16 code units and lists to 128 entries, with tighter operation-specific bounds where stated. JSON text has bounded nesting and node counts.
- Numeric outputs must be finite and no larger in absolute magnitude than the safe-integer limit; operations returning exact large integers use decimal text. Positions are zero-based and spans end exclusively unless the operation explicitly states a different convention.
Alternative or Complementary methods
Keep content-line syntax, value escaping and timezone interpretation separate. Use a complete iCalendar implementation for recurrence expansion, timezone transitions and property-specific validation.
References
Similar or alternative tools
- iCalendar Basic Date Token Parser
Parse and calendar-validate one strict YYYYMMDD iCalendar basic date, including Gregorian leap rules; no timestamp conversion.
- iCalendar Basic Time Token Formatter
Format validated iCalendar HHMMSS with optional Z; second 60 is retained as explicit leap-second notation, not proof of a real leap second.