Voeg noot toe over opslaan van originele timezone

Author: TimvdLippe

sections/designRules.md

@@ -169,7 +169,7 @@ Handling date and time is tricky and can lead to confusion among clients. The da
       </dd>
       <dt>Rationale</dt>
       <dd>
-         <p>Implementing RFC9557 and ISO 8601 in UTC removes ambiguity in date handling between systems and timezones.</p>
+         <p>Implementing RFC9557 and ISO 8601 removes ambiguity in date handling between systems and timezones.
       </dd>
    </dl>
 </div>
@@ -184,6 +184,9 @@ Handling date and time is tricky and can lead to confusion among clients. The da
       <dt>Rationale</dt>
       <dd>
          <p>Allowing clients to use any timezone offset in requests results in flexibility and less complexity for users. Using UTC in responses results in clarity and removes ambiguity.
+         <p class="note">This specification does not state rules regarding storage in databases.
+         However, it is recommended to store the originally supplied timezone from the client request in the database, such that later the location of the client can be determined.
+         For example, an extra field in a response can contain the originally supplied timezone, if that's useful for the client.
       </dd>
    </dl>
 </div>