-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ocrd-tool.json validator: too strict #848
Labels
Comments
Perhaps also:
|
kba
added a commit
to OCR-D/spec
that referenced
this issue
May 20, 2022
kba
added a commit
to OCR-D/spec
that referenced
this issue
May 20, 2022
kba
added a commit
to OCR-D/spec
that referenced
this issue
May 23, 2022
Newest release allows all these additional JSON-Schema constructs. |
Not all, it seems:
Can we get this to work, or should I create another issue, @kba? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In our ocrd-tool schema, for the parameters we only have
core/ocrd_validators/ocrd_validators/ocrd_tool.schema.yml
Lines 62 to 90 in ecdb840
This excludes perfectly sound data JSON qualifiers like
items
(for restrictions on the list items iftype==array
)minimum
,maximum
,exclusiveMinimum
,exclusiveMaximum
,multipleOf
(for numerical restrictions iftype==number
)^OCR-D-[A-Z0-9-]+$
(which should be allowed by spec now)The first two yield an error saying
Additional properties are not allowed
, the latter directly mocks the regex.The text was updated successfully, but these errors were encountered: