JSON Schema Validator dependency is in maintenance mode. Consider alternatives.

[Pfeil]

Is your feature request related to a problem? Please describe.

The current json schema validator we use is in maintenance mode. It is also not the one we use in other projects.

Describe the solution you'd like

We should consider using the fork which is proposed from the project or https://github.com/networknt/json-schema-validator

[Pfeil]

It also seems to not support the format = uri feature in the schema generated for this type like this:

curl -X 'GET' \
  'http://typeapi.lab.pidconsortium.net/v1/types/schema/21.T11969/cb371c93c5aa0e62198e' \
  -H 'accept: application/json'

{
    "@id": "21.T11969/cb371c93c5aa0e62198e",
    "type": "string",
    "format": "uri",
    "description": "Validation schema for type 'URI' with the PID '21.T11969/cb371c93c5aa0e62198e'",
    "title": "URI",
    "$schema": "http://json-schema.org/draft-04/schema#"
}

I did not test if it would have to, but we should make sure to have a feature-complete validator. The current validator just allows any string, given this schema.

[Pfeil]

Same for number, as it seems? We should do something about this soon, as the type api seems to rely on such features a lot.

[Pfeil]

Implemented in #272, merged into #264. Will be part of the 3.0.0 release.