Skip to content

Commit

Permalink
Merge pull request #61 from ietf-wg-sedate/rd-iesg-review-1
Browse files Browse the repository at this point in the history
Editorial changes from Roman Danyliw's IESG review
  • Loading branch information
ryzokuken authored Oct 19, 2023
2 parents 839bd82 + 62bda5b commit 51a8d98
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions draft-ietf-sedate-datetime-extended.md
Original file line number Diff line number Diff line change
Expand Up @@ -193,7 +193,7 @@ information related to a given timestamp needs to be either handled
separately or attached to it in a non-standard manner.

This is a pressing issue for applications that handle each
instant with an associated time zone name, in order to take into account events
such instant in time with an associated time zone name, in order to take into account events
such as daylight saving time transitions.
Many of these applications attach the time zone to the timestamp in a
non-standard format, at least one of which is fairly well-adopted {{JAVAZDT}}.
Expand Down Expand Up @@ -240,7 +240,7 @@ For instance, inconsistencies might arise because of:
* political decisions as discussed above, or
* updates to time zone definitions being applied at different times
by timestamp producers and receivers, or
* errors in applications producing and consuming timestamps.
* errors in programs producing and consuming timestamps.

While the information available in an IXDTF string is not generally sufficient to resolve
an inconsistency, it may be used to initiate some out of band
Expand Down Expand Up @@ -427,7 +427,7 @@ timestamp extension suffix and defines the IXDTF format, which extends

## Format of Extended Information

The format allows implementations to specify additional
The format allows applications to specify additional
important information in addition to a bare {{RFC3339}} timestamp.

This is done by defining *tags*, each with a *key* and
Expand Down Expand Up @@ -704,18 +704,18 @@ Note that this is the same instant in time as `1996-12-20T00:39:57Z`, expressed
~~~~
{: #datetime-tzname title="Adding a time zone name"}

{{datetime-tzname}} represents the exact same instant as the previous example but
{{datetime-tzname}} represents the exact same instant in time as the previous example but
additionally specifies the human time zone associated with it
("Pacific Time") for time-zone-aware implementations to take into
("Pacific Time") for time-zone-aware applications to take into
account.

~~~~ ixdtf
1996-12-19T16:39:57-08:00[America/Los_Angeles][u-ca=hebrew]
~~~~
{: #date-time-hebrew title="Projecting to the Hebrew calendar"}

{{date-time-hebrew}} represents the exact same instant, but it informs calendar-aware
implementations (see {{calendar}}) that they should project it to the Hebrew calendar.
{{date-time-hebrew}} represents the exact same instant in time, but it informs calendar-aware
applications (see {{calendar}}) that they should project it to the Hebrew calendar.

~~~~ ixdtf
1996-12-19T16:39:57-08:00[_foo=bar][_baz=bat]
Expand Down

0 comments on commit 51a8d98

Please sign in to comment.