One field gives the Schematron context Another one gives the Schematron text However, the so-called Schematron text is in fact only the xpath notation used within Schematron rules. The final Schematron code will need to include the given context and the given text within specific xml tags before a Schematron engine can make use of it. A macro included in a separate file can export the Schematron code in a to use’ format. “” ‘ready Usage : Open the .xlsm file (NB: do not rename the .xslm file!) Hit the Schematron generator” button “Run On first popup : Select a valid AIXM-Rules-Mgr.Export.xml file from which you want to extract the Schematron. (NB: valid means that you have no error when opening this file with excel!) attention: the Excel Macro is hard-coded to extract the Schematron code from column Q. Due to the new columns (B,...) that include the flag for profiles, the Macro will not work properly. The current workaround is to open the .xml file in Excel, remove the columns that contain the profile flags. Make sure that the Schematron code is in column Q and save the file in the original .xml format. On second popup : Save the output into an file “.sch” On alert, click on button “Delete” Close the .xslm file without saving The Schematron file you generated is ready-to-use in your validation engine. The character indicates carriage return in the UTF8 XML export file Practical verification of AIXM data sets Testing <oXygen/> XML Developer in Professional edition was used for testing the Schematron code <oXygen/> XML Developer is very interesting because, not only it allows testing the rules, but it also allows editing xpath code with auto-completion functions based on a provided xml or xsd Java extensions can be integrated in <oXygen/> XML Developer as well. The following picture shows an example of a rule checking result in <oXygen/> XML Developer AIXM Business Rules data set Excel file
One field gives the Schematron context Another one gives the Schematron text However, the so-called Schematron text is in fact only the xpath notation used within Schematron rules. The final Schematron code will need to include the given context and the given text within specific xml tags before a Schematron engine can make use of it. A macro included in a separate “” file can export the Schematron code in a ‘ready to use’ format. Usage : Open the .xlsm file (NB: do not rename the .xslm file!) Hit the “Run Schematron generator” button On first popup : Select a valid AIXM-Rules-Mgr.Export.xml file from which you want to extract the Schematron. (NB: valid means that you have no error when opening this file with excel!) attention: the Excel Macro is hard-coded to extract the Schematron code from column Q. Due to the new columns (B,...) that include the flag for profiles, the Macro will not work properly. The current workaround is to open the .xml file in Excel, remove the columns that contain the profile flags. Make sure that the Schematron code is in column Q and save the file in the original .xml format. On second popup : Save the output into an “.sch” file On alert, click on “Delete” button Close the .xslm file without saving The Schematron file you generated is ready-to-use in your validation engine. The character indicates carriage return in the UTF8 XML export file Practical verification of AIXM data sets Testing <oXygen/> XML Developer in Professional edition was used for testing the Schematron code <oXygen/> XML Developer is very interesting because, not only it allows testing the rules, but it also allows editing xpath code with auto-completion functions based on a provided xml or xsd Java extensions can be integrated in <oXygen/> XML Developer as well. The following picture shows an example of a rule checking result in <oXygen/> XML Developer AIXM Business Rules data set Excel file