tr:errorPI2svrl errorPI2svrl
htmlreports/xpl/errorPI2svrl.xpl
Import URI: errorPI2svrl.xpl
Input Ports
Name | Documentation | Connections |
---|---|---|
sourceⓅ |
Output Ports
Name | Documentation | Connections |
---|---|---|
resultⓅ | ||
reportⓈ | The errors that were encoded as PIs, now as SVRL documents. They may carry a @tr:rule-family attribute on the top-level element. It could be 'w2d' in the example above. The XSLT, ../xsl/errorPI2svrl.xsl, has to take care of proper result document generation for each of these virtual checking families. |
Options
Name | Documentation | Default |
---|---|---|
group-by-srcpath | 'yes' | |
debug | 'no' | |
debug-dir-uri | 'debug' | |
status-dir-uri | 'status' | |
pi-names | Space-separated names of processing instructions in the source document that carry error messages. The PI text may convey additional error classification information. Example: <?letex w2d-101 This is some error message.?> | 'letex' |
severity | message | warning | error | fatal-error | 'warning' |
Subpipeline
Step | Inputs | Outputs | Options | |
---|---|---|---|---|
tr:simple-progress-msg start-msg |
| result | file = 'error-pi2svrl-start.txt' status-dir-uri = $status-dir-uri | |
p:sink d202e51 | ||||
p:xslt create-svrls |
| result | ||
p:sink d202e74 |
| |||
p:for-each d202e75 | ||||
tr:store-debug d202e82 | result | pipeline-step = concat('schematron/pi2svrl/', replace(base-uri(), '^(.+/)(.+).xml', '$2')) active = $debug base-uri = $debug-dir-uri | ||
p:sink d202e91 | ||||
tr:simple-progress-msg success-msg |
| result | file = 'error-pi2svrl-success.txt' status-dir-uri = $status-dir-uri | |
p:sink d202e112 |
|