From 4b2fc48897c3cd94b8cc83ca7fe11da62e488368 Mon Sep 17 00:00:00 2001 From: tkrop Date: Tue, 11 Jun 2024 13:41:11 +0000 Subject: [PATCH] deploy: 8ba7497021dfa0dcbc9409fc73d645cdda650458 --- index.html | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/index.html b/index.html index 951caba3..a6277cbd 100644 --- a/index.html +++ b/index.html @@ -4,7 +4,7 @@ - + Zalando RESTful API and Event Guidelines @@ -2770,14 +2770,14 @@

MUST

string

duration

-

RFC 3339 internet profile — subset of ISO 8601

-

"P1DT30H4S"

+

RFC 3339 — subset of ISO 8601, see also rule #127 for details.

+

"P1DT3H4S"

string

period

-

RFC 3339 internet profile — subset of ISO 8601

-

"2019-07-30T06:43:40.252Z/PT3H"

+

RFC 3339 — subset of ISO 8601, see also rule #127 for details.

+

"2022-06-30T14:52:44.276/PT48H" "PT24H/2023-07-30T18:22:16.315Z" "2024-05-15T09:48:56.317Z/.."

string

@@ -2969,7 +2969,7 @@

MUST

As a specific case of MUST use standard data formats, you must use the string typed formats date, date-time, time, duration, or period for the definition of date and time properties. The formats are based on the standard RFC 3339 internet profile -- a -subset of ISO 8601

+subset of ISO 8601.

APIs MUST use the upper-case T as a separator between date and time and @@ -3055,8 +3055,8 @@

SH

-

A time interval query parameters should use <time-property>_between instead -of the parameter tuple <time-property>_before/<time-property>_after, while +

A time interval query parameter should use <time-property>_between instead +of the parameter pair <time-property>_before/<time-property>_after, while properties providing a time interval should be named <time-property>_interval.

@@ -10995,7 +10995,7 @@

Rule Changes