Skip to content

Commit 23d0778

Browse files
author
ietf-corpus-bot
committed
auto-ingest: ietf-elements backfill — 120 new elements (2026-07-12)
1 parent 61a5b56 commit 23d0778

120 files changed

Lines changed: 741 additions & 90 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎corpus/elements/rfc-3339__design-rationale-an-offset-of-00-00-indicates-the-utc.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-3339
2+
kind: design-rationale
3+
summary: An offset of "-00:00" indicates the UTC time is known but the local offset is unknown, distinguishing it semantically from "+00:00" or "Z" which imply UTC is the preferred reference point.
4+
section: "4.3"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-3339__design-rationale-components-are-ordered-from-least-precise-year-to.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-3339
2+
kind: design-rationale
3+
summary: Components are ordered from least precise (year) to most precise (second/fraction), so that timestamps sharing the same time zone string and fractional-second precision can be correctly sorted using a simple lexicographic string comparison (e.g., strcmp()).
4+
section: "5.1"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-3339__design-rationale-day-of-week-is-deliberately-excluded-from-the.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-3339
2+
kind: design-rationale
3+
summary: Day-of-week is deliberately excluded from the format because it is redundant (computable from the date) and its inclusion would introduce the possibility of inconsistency between the day-of-week field and the calendar date.
4+
section: "5.4"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-3339__design-rationale-fractions-of-a-second-are-the-sole-rarely.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-3339
2+
kind: design-rationale
3+
summary: Fractions of a second are the sole rarely-used option retained in the format, expected only for applications requiring strict ordering or unusual precision. Rarely used options are avoided because they are less likely to be tested and bugs in parsing are more likely to remain undiscovered.
4+
section: "5.3"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-3339__design-rationale-the-full-iso-8601-grammar-is-too-complex.yaml‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
document: rfc-3339
2+
kind: design-rationale
3+
summary: The full ISO 8601 grammar is too complex for Internet use; this profile achieves simplicity by making most fields and punctuation mandatory, leaving fractions of a second as the only optional element.
4+
section: "5.5"
5+
extracted_by: claude-sonnet-4-6
6+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-3339__design-rationale-utc-is-preferred-over-local-time-because-daylight.yaml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
document: rfc-3339
22
kind: design-rationale
3-
summary: UTC is preferred over local time because daylight saving rules are convoluted and can change unpredictably based on local law; true interoperability is best achieved with UTC. This specification explicitly does not address local timezone rule handling.
3+
summary: UTC is preferred over local time because daylight saving rules are convoluted and can change at unpredictable times based on local law, making true interoperability unachievable with local time zones alone.
44
section: "4.1"
55
extracted_by: claude-sonnet-4-6
6-
extracted_at: "2026-07-05"
6+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-3339__interoperability-note-attempts-to-label-local-utc-offsets-with-alphabetic.yaml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
document: rfc-3339
2+
kind: interoperability-note
3+
summary: Attempts to label local UTC offsets with alphabetic timezone strings (as in old RFC 822) resulted in poor interoperability. RFC 2822 made numeric offsets mandatory; this profile follows the same approach.
4+
section: "4.2"
5+
topics:
6+
- email
7+
extracted_by: claude-sonnet-4-6
8+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-3339__interoperability-note-historical-time-zones-that-differ-from-utc-by.yaml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
document: rfc-3339
22
kind: interoperability-note
3-
summary: Historical time zones that differ from UTC by a non-integral number of minutes (e.g., Netherlands mean time, +00:19:32.13) cannot be represented exactly in the HH:MM numeric offset format; applications must convert to the closest representable offset.
3+
summary: Historical time zones that differ from UTC by a non-integral number of minutes (e.g., the Netherlands in 1937, at +00:19:32.13) cannot be represented exactly in HH:MM format; applications must convert such timestamps to the closest representable UTC offset.
44
section: "4.2"
55
extracted_by: claude-sonnet-4-6
6-
extracted_at: "2026-06-21"
6+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-3339__interoperability-note-internet-clients-should-be-prepared-to-transform-rfc.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
document: rfc-3339
2+
kind: interoperability-note
3+
summary: Internet clients SHOULD be prepared to transform RFC 3339 timestamps into a display format suitable for the user's locality, including translating UTC to local time, because no single date/time format is readable according to the conventions of all countries.
4+
section: "5.2"
5+
rfc2119_level: SHOULD
6+
extracted_by: claude-sonnet-4-6
7+
extracted_at: "2026-07-12"

‎corpus/elements/rfc-3339__interoperability-note-leap-seconds-occur-simultaneously-in-all-time-zones.yaml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
document: rfc-3339
22
kind: interoperability-note
3-
summary: Leap seconds occur simultaneously in all time zones; in non-UTC zones the leap second point is shifted by the zone offset so that it happens at the same instant globally.
3+
summary: Leap seconds occur simultaneously in all time zones; in non-UTC zones the leap second point is shifted by the zone offset. A leap second in UTC (XXXX-MM-DDT23:59:60Z) appears at a different local clock time but represents the same instant.
44
section: "5.7"
55
extracted_by: claude-sonnet-4-6
6-
extracted_at: "2026-05-23"
6+
extracted_at: "2026-07-12"

0 commit comments

Comments
 (0)