Fix some XML Schema date/time/duration correctness issues

[jviotti]

Signed-off-by: Juan Cruz Viotti jv@jviotti.com

[augmentcode]

🤖 Augment PR Summary

Summary: Updates the xsd:dateTime, xsd:time, and xsd:duration JSON Schemas to better match XML Schema lexical rules (no leap seconds, allow 24:00:00, constrain timezones to ±14:00).
Also updates the associated JSON tests to reflect the corrected validity expectations.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 3 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

The regex here permits 24:00:00 with a trailing fractional part of only zeros (e.g. 24:00:00.0), but the file’s $comment says hour 24 is only valid as 24:00:00. Consider aligning the comment with the actual constraint to avoid misleading schema consumers.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[augmentcode]

Since the timezone offset range is now constrained to ±14:00 (and minutes must be 00 when the hour is 14), consider adding tests that +14:00 is valid and e.g. +14:01/+15:00 are invalid. This would better lock in the intended correctness fix.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[augmentcode]

The updated schema allows 24:00:00 with a fractional part of only zeros (e.g. 24:00:00.0), but the tests only cover 24:00:00 without fractional seconds. Adding a positive case for 24:00:00.0 (and a negative case like 24:00:00.1) would help prevent regressions around this edge case.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}