Date-time

- addresses parts of oasis-tcs#469
- correct format
- add filename to etc/bind.txt

csaf_2.1/prose/edit/etc/bind.txt

@@ -8,6 +8,7 @@ introduction-04-informative-references.md
 introduction-05-typographical-conventions.md
 design-considerations-00.md
 design-considerations-01-construction-principles.md
+design-considerations-02-date-time.md
 schema-elements-00.md
 schema-elements-01-definitions.md
 schema-elements-01-defs-01-acknowledgements.md

csaf_2.1/prose/edit/src/design-considerations-02-date-time.md

@@ -3,11 +3,11 @@
 This standard uses the `date-time` format as defined in JSON Schema Draft 2020-12 Section 7.3.1.
 In accordance with RFC 3339 and ISO 8601, the following rules apply:
 
-- The letter `T` separating the date and time SHALL be upper case.
-- The letter `Z` indicating the timezone UTC SHALL be upper case.
-- Fractions of seconds are allowed as specified in the standards mention above with the full stop (`.`) as separator.
-- Leap seconds are supported. However, they SHOULD be avoided if possible.
-- Empty timezones are prohibited.
-- The ABNF of RFC 3339, section 5.6 applies.
+* The letter `T` separating the date and time SHALL be upper case.
+* The letter `Z` indicating the timezone UTC SHALL be upper case.
+* Fractions of seconds are allowed as specified in the standards mention above with the full stop (`.`) as separator.
+* Leap seconds are supported. However, they SHOULD be avoided if possible.
+* Empty timezones are prohibited.
+* The ABNF of RFC 3339, section 5.6 applies.
 
 -------