Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Date-time #810

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions csaf_2.1/prose/edit/etc/bind.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
1 change: 1 addition & 0 deletions csaf_2.1/prose/edit/src/conformance.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,7 @@ The entities ("conformance targets") for which this document defines requirement

A text file or data stream satisfies the "CSAF document" conformance profile if it:

* conforms to the syntax and semantics defined in section [sec](#date-time)
* conforms to the syntax and semantics defined in section [sec](#schema-elements).
* satisfies at least one profile defined in section [sec](#profiles).
* does not fail any mandatory test defined in section [sec](#mandatory-tests).
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -66,4 +66,4 @@ Section [sec](#distributing-csaf-documents) states how to distribute and where t
Safety, Security and Data Protection are considered in section [sec](#safety-security-and-data-protection-considerations).
Finally, a set of conformance targets describes tools in the ecosystem.

-------

13 changes: 13 additions & 0 deletions csaf_2.1/prose/edit/src/design-considerations-02-date-time.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
## Date and Time

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.

-------
Original file line number Diff line number Diff line change
@@ -1,5 +1,8 @@
## Normative References

ISO8601
: _Data elements and interchange formats — Information interchange — Representation of dates and times_, International Standard, ISO 8601:2004(E), December 1, 2004, https://www.iso.org/standard/40874.html.

JSON-Schema-Core
: _JSON Schema: A Media Type for Describing JSON Documents_, draft-bhutton-json-schema-00, December 2020, <https://datatracker.ietf.org/doc/html/draft-bhutton-json-schema-00>.

Expand All @@ -15,6 +18,9 @@ Relative-JSON-Pointers
RFC2119
: Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>.

RFC3339
: Klyne, G. and C. Newman, "Date and Time on the Internet: Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, <https://www.rfc-editor.org/info/rfc3339>.

RFC7464
: Williams, N., "JavaScript Object Notation (JSON) Text Sequences", RFC 7464, DOI 10.17487/RFC7464, February 2015, <https://www.rfc-editor.org/info/rfc7464>.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -51,9 +51,6 @@ GFMCMARK
GFMENG
: _GitHub Engineering: A formal spec for GitHub Flavored Markdown_, https://githubengineering.com/a-formal-spec-for-github-markdown/.

ISO8601
: _Data elements and interchange formats — Information interchange — Representation of dates and times_, International Standard, ISO 8601:2004(E), December 1, 2004, https://www.iso.org/standard/40874.html.

ISO19770-2
: _Information technology — IT asset management — Part 2: Software identification tag_, International Standard, ISO 19770-2:2015, September 30, 2015, <https://www.iso.org/standard/65666.html>.

Expand All @@ -66,9 +63,6 @@ OPENSSL
PURL
: _Package URL (purl)_, GitHub Project, https://github.com/package-url/purl-spec.

RFC3339
: Klyne, G. and C. Newman, "Date and Time on the Internet: Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, <https://www.rfc-editor.org/info/rfc3339>.

RFC3552
: Rescorla, E. and B. Korver, "Guidelines for Writing RFC Text on Security Considerations", BCP 72, RFC 3552, DOI 10.17487/RFC3552, July 2003, <https://www.rfc-editor.org/info/rfc3552>.

Expand Down
Loading