-
Notifications
You must be signed in to change notification settings - Fork 2
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
Validator for schema #294
Comments
Added some domain-specific contexts and requirements files in PR #296 The idea is that the validator uses the requirements.yaml files when validating a schema. This way the the requirements become declarative and separated from the logics. The format of the requirements.yaml file can be discussed. We should also have a context validator that ensures that a keyword only is defined once. This should probably be a separate issue. |
Should we write schema as a SHACL? There exists validators for this |
Validators for DCAT-AP and DCAT-AP-NO exists. These are both based on SHACL. Are these a good starting point? Btw, the DCAT-AP-NO one is out-of-date. |
Web API for validator explained here https://github.com/ISAITB/validator-resources-dcat-ap/tree/master?tab=readme-ov-file |
Use some validator can be used for both DCAT-AP-NO and our custom schema to ensure data is schema-compliant.
This is to ensure that "illegal" datasets are not uploaded.
The text was updated successfully, but these errors were encountered: