Skip to content

Added /core/date-time #252

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.

Sign up for GitHub

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

Open
wants to merge 4 commits into
base: develop
Choose a base branch
from
Open

Added /core/date-time #252

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
7eef086
Added `/core/date-time`
sanderke Jul 24, 2025
8b98d6f
markdownlint
sanderke Jul 24, 2025
c982b06
Apply suggestions from code review
sanderke Aug 13, 2025
00ae440
Update sections/designRules.md
sanderke Aug 22, 2025
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
16 changes: 16 additions & 0 deletions sections/designRules.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,6 +125,22 @@ A resource that corresponds to a single conceptual entity is referred to as a [=
</dl>
</div>

<div class="rule" id="/core/date-time" data-type="technical">
<p class="rulelab">Use ISO 8601 for date and time formats</p>
<dl>
<dt>Statement</dt>
<dd>
<p>All date and time fields in requests and responses MUST follow [[RFC9557]] and thus be in [[ISO8601]] format (e.g., <code>YYYY-MM-DD</code> for dates, <code>YYYY-MM-DDTHH:mm:ssZ</code> for timestamps). Fields in responses containing timestamps MUST be in UTC (e.g. <code>Z</code> as offset). APIs MUST accept fields with timestamps with any time offset in requests and servers SHOULD normalize to (and store in) UTC.</p>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ik zou expliciet maken welke onderdelen van ISO 8601 / RFC 3339 hier worden bedoeld, concreet:

  • full-date voor datum
  • date-time voor datum/tijd

<p>If the time portion is not relevant, only the date portion (e.g., <code>YYYY-MM-DD</code>) SHOULD be accepted, stored, and returned.</p>
</dd>
<dt>Rationale</dt>
<dd>
<p>Implementing ISO 8601 in UTC removes ambiguity in date handling between systems and timezones.</p>
<p>Inserting a default or irrelevant time can lead to interpretation errors in international contexts. A publish date of <code>2025-07-24T00:00:00Z</code> could for instance be rendered as July 23 in Ireland. A default time of 23:59 would in turn cause date confusion east of Greenwich.</p>
</dd>
</dl>
</div>

## HTTP methods

Although the REST architectural style does not impose a specific protocol, REST APIs are typically implemented using HTTP [[rfc9110]].
Expand Down
Loading