We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The bucket utils file is a new reporting file from the scheduler.
This CSV document (example here: https://github.com/iodepo/odis-arch/blob/schema-dev-df/book/reporting.md#bucket-utils) holds the SHA hash for a file and it's URL.
This file may be the best location to place the results of the SHACL validation.
This file can be used both to drive the validation and also hold the results, or a simple quantitative value based on the SHACL process.
Note, it may still be better to just build a SHACL graph and use the bucket utils file just as the driver for the processing.
This should be added as a sensor trigger in the Scheduler the same way the SPARQL load process is a sensor trigger.
The text was updated successfully, but these errors were encountered:
fils
No branches or pull requests
The bucket utils file is a new reporting file from the scheduler.
This CSV document (example here: https://github.com/iodepo/odis-arch/blob/schema-dev-df/book/reporting.md#bucket-utils) holds the SHA hash for a file and it's URL.
This file may be the best location to place the results of the SHACL validation.
This file can be used both to drive the validation and also hold the results, or a simple quantitative value based on the SHACL process.
Note, it may still be better to just build a SHACL graph and use the bucket utils file just as the driver for the processing.
This should be added as a sensor trigger in the Scheduler the same way the SPARQL load process is a sensor trigger.
The text was updated successfully, but these errors were encountered: