You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
While discussion the issue #6024 a solution / work around was presented in comment. Using this workaround to prevent the issue #6024 will result in a schema invalid ruleset file:
$ xmllint --noout --schema rulesets/ruleset.xsd rulesets/slub.xml
rulesets/slub.xml:2441: element restriction: Schemas validity error : Element '{http://names.kitodo.org/ruleset/v2}restriction', attribute 'division': '' is not a valid value of the atomic type 'xs:NMTOKEN'
The file slub.xml has the content in the mentioned line
<correlation>
<restrictiondivision=""unspecified="forbidden">
<!-- This is necessary to avoid the creation of a second dmdSec https://github.com/kitodo/kitodo-production/issues/6024 -->
<permitdivision="page"/>
</restriction>
The error message above will appear with the ruleset.xsd file from release 3.6.x, 3.7.x and current master.
Run a validation with the ruleset.xsd against the changed ruleset file.
Expected behavior
Even a workaround should not result in a schema invalid ruleset file. If a workaround even needs changes in the ruleset.xsd file then this file must be changed too.
Screenshots
Release
3.6.x
3.7.x
current master (2024-08-27)
The text was updated successfully, but these errors were encountered:
Describe the bug
While discussion the issue #6024 a solution / work around was presented in comment. Using this workaround to prevent the issue #6024 will result in a schema invalid ruleset file:
The file
slub.xml
has the content in the mentioned lineThe error message above will appear with the ruleset.xsd file from release 3.6.x, 3.7.x and current master.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Even a workaround should not result in a schema invalid ruleset file. If a workaround even needs changes in the ruleset.xsd file then this file must be changed too.
Screenshots
Release
The text was updated successfully, but these errors were encountered: