JSON Schema validation for ISO 8601 date strings

JSON lacks a native date data type, necessitating the use of strings or numbers to represent temporal data. While ISO 8601 is the industry standard for string-based date representation, the core JSON specification does not enforce a specific format for these values.

When implementing strict validation using JSON Schema, there is a need to ensure that date strings remain consistent across different language implementations (such as Python's json module and Java's Jackson) without relying on non-standard extensions.

• How can a JSON Schema be configured to validate the specific structure of an ISO 8601 date string?
• What are the constraints when using the format keyword for dates across different schema versions?