Harden the schemas

[jviotti]

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

[augmentcode]

🤖 Augment PR Summary

Summary: This PR hardens and clarifies a broad set of JSON Schemas by tightening validation rules to better match their upstream specifications and the library’s intended constraints.

Changes:

• Scaled Celsius-prefixed schemas’ minimum values to preserve the absolute-zero bound under SI prefixes
• Adjusted POSIX path schemas to exclude exactly two leading slashes from absolute pathnames while still modeling them as valid paths with implementation-defined meaning
• GeoJSON: constrained bbox to 2D/3D and explicitly allowed nested GeometryCollection items
• HTTP/URI: tightened http/https URLs to reject empty-host authorities; simplified URL/relative-URI definitions using format assertions
• URN: refined the grammar to better align with RFC 8141 (e.g., disallow 1-char NIDs) and updated tests accordingly
• ISO 4217: expanded currency codes to include test/unknown entries and enriched historical metadata with x-withdrawal-dates
• ISO 8601 durations: simplified patterns and updated tests to reflect quantity semantics in alternative calendar formats
• JSON-RPC: broadened id to allow fractional numbers per “SHOULD NOT” guidance
• W3C XSD-derived types: relaxed/updated anyURI, base64Binary, and date/year patterns plus corresponding test expectations

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

[augmentcode]

Review completed. 1 suggestion posted.

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

[augmentcode]

pattern currently blocks most C0 controls and U+FFFE/U+FFFF, but it still permits surrogate code points (U+D800–U+DFFF); if the intent is the XML Char production, those should be excluded as well to avoid validating invalid XML character data.

Severity: medium

Other Locations

• schemas/2020-12/w3c/xmlschema/2001/any-uri.json:25

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