add notes - sfeed_tests - sfeed tests and RSS and Atom files
(HTM) git clone git://git.codemadness.org/sfeed_tests
(DIR) Log
(DIR) Files
(DIR) Refs
(DIR) README
(DIR) LICENSE
---
(DIR) commit a30fb700148827fa5b920c5cc8e377df4d09d61f
(DIR) parent 6e8abd092570e12678e060e463fd289e42292e97
(HTM) Author: Hiltjo Posthuma <hiltjo@codemadness.org>
Date: Tue, 5 Nov 2024 20:59:06 +0100
add notes
Diffstat:
M notes/specs.txt | 32 +++++++++++++++++++++++++++++++
1 file changed, 32 insertions(+), 0 deletions(-)
---
(DIR) diff --git a/notes/specs.txt b/notes/specs.txt
@@ -78,3 +78,35 @@ Some notes about specs
- There were/are many bugs in time parsing implementations in the different
libcs in various platforms sfeed has a parser for most of the formats used by
RSS/Atom/etc and handles timezone offsets.
+
+- Lowercase or uppercase 't' separator and 'z' timezone:
+
+ The Atom Syndication Format RFC4287 references RFC3339 for timestamp but imposes/overrides
+ a stricter format.
+
+ For example strictly speaking timezone format separated should be with uppercase:
+
+ Allowed in RFC3339, but not for timestamps in Atom feeds, 't' and 'z' must be uppercase:
+
+ <updated>2003-12-13t18:30:02z</updated>
+
+ Correct:
+
+ <updated>2003-12-13T18:30:02Z</updated>
+
+ See RFC4287 section 3.3. Date Constructs:
+
+ "
+ A Date construct is an element whose content MUST conform to the
+ "date-time" production in [RFC3339]. In addition, an uppercase "T"
+ character MUST be used to separate date and time, and an uppercase
+ "Z" character MUST be present in the absence of a numeric time zone
+ offset."
+
+
+ See RFC3339 5.6. Internet Date/Time Format:
+
+ "NOTE: Per [ABNF] and ISO8601, the "T" and "Z" characters in this
+ syntax may alternatively be lower case "t" or "z" respectively."
+
+