Verify large XML files using schematron

I am using schematron to validate large xml files (several megabytes). If the file is normal (if there are no errors), the validation is very fast. But when the error count increases, it increases Schematron validation time execution time.

Is there a way to stop schematron XSLT validation when 200 errors are found, for example. This will help, because if there are a large number of files containing hundreds of occurrences of the same Error, then it is enough to report the first error and ask the user to verify the file again after correction.

By combining Schematron Terminator Validator with Schematron Phases, you should be able to get very close to your requirements

The terminator validator allows schematron validation to fail when the first error hits.

Phases allow the verification to be broken down into phases and executed step by step.

One or two of these combinations should get you close to what you want-maybe all rule classes are carried out in phases, and then use Each stage of the terminator running will produce good results, allowing users to get multiple wrong information at once.

I am using schematron to validate large xml files (several Megabytes). If the file is normal (if there are no errors), the verification is very fast. But when the error count increases, it will increase the execution time of the schematron verification time.

Is there a way to find For example, stop schematron XSLT verification when there are 200 errors. This will help, because if there are a large number of files containing hundreds of times with the same error, it is sufficient to report only the first error and ask the user to verify the file again after correction.

By combining Schematron Terminator Validator with Schematron Phases, you should be able to be very close to your requirements

Terminator validation The controller allows schematron validation to fail when the first error hits.

Phase allows validation to be broken down into phases and executed step by step.

One or two of these should get you close What you want-it is possible to carry out all the rule classes in stages, and then use the terminator to run each stage will produce good results, allowing users to get multiple wrong information at once.

WordPress database error: [Table 'yf99682.wp_s6mz6tyggq_comments' doesn't exist]
SELECT SQL_CALC_FOUND_ROWS wp_s6mz6tyggq_comments.comment_ID FROM wp_s6mz6tyggq_comments WHERE ( comment_approved = '1' ) AND comment_post_ID = 6035 ORDER BY wp_s6mz6tyggq_comments.comment_date_gmt ASC, wp_s6mz6tyggq_comments.comment_ID ASC

Leave a Comment

Your email address will not be published.