Austin Wright

Indeed there's a great need to have a "format" keyword that validates. The difficulty of going about with this before has been a couple things: * Reverse compatibility, some usage...

> Could you clarify this? Are you saying that a validating "email" format would reject a number? I can't find such a requirement. In fact the (optional) [test suite](https://github.com/json-schema-org/JSON-Schema-Test-Suite/blob/main/tests%2Fdraft2020-12%2Foptional%2Fformat%2Femail.json) verifies...

The normative language could definitely be reviewed and streamlined for sure. The relevant specification is BCP 14. Though some amount of mixed language may be necessary. The most important purpose...

@mamadfar What environment are you using? There should be a built-in `require('url')`

I'm sorry not sure what's going on then, my Node.js v22.4.0 has the necessary function builtin: ``` > require('url') { Url: [Function: Url], parse: [Function: urlParse], resolve: [Function: urlResolve], resolveObject:...

'url' has been in Node.js core since the very beginning, or very near it. I'm really not sure what's going on, without more information.

I can speak to the code generation aspect: @bcherny > Is the right way to interpret this: > > 1. `SqlConnectionInfo` is an object which may declare keys `userName`, `password`,...

> When multiple schemas try to identify as the same URI, validators SHOULD raise an error condition I think SHOULD is appropriate because what it means to "raise an error...

@gregsdennis has a good suggested alternative. Your idea could be pursued as part of a generic mechanism for metadata (perhaps a variation on "$comment" that accepts a JSON-LD blob), but...

@gordielachance If the result invalid and has errors, you can filter the list of errors based on the property it was found within. Does that make sense?