-
Notifications
You must be signed in to change notification settings - Fork 21
StatusXML
Scripts may have a port annotated with media type application/vnd.pipeline.status+xml
which provides a succinct summary of the job status. It may be compared with the exit value of a process.
There are two use cases that come to mind.
-
A job may return documents even if the conversion can not be considered "successful". An example is a validation job which needs to return a validation report when the input document is invalid. With a status port the UI can quickly determine whether the validation passed or failed.
-
When a step is used in other steps, a status port can convey status information to the calling step.
<d:status xmlns:d="http://www.daisy.org/ns/pipeline/data" result="error"/>
The document root element
-
ok
: if there were no errors -
error
if there were any errors
TBD
At this moment, validators have only errors to report, not warnings. Therefore there is no mention of warnings here. However, this format will evolve if required to accommodate future developments.
One thing to consider is whether it would be useful to report the number of errors.
- Home
- Download
-
Help
-
User Guide
- Installation
- Desktop Application
- Web Application
- Pipeline as a Service
- Command Line
-
Scripts
- DAISY 2.02 Validator
- DAISY 2.02 to EPUB 3
- DAISY 3 to DAISY 2.02
- DAISY 3 to EPUB 3
- DTBook Validator
- DTBook to DAISY 3
- DTBook to EPUB3
- DTBook to HTML
- DTBook to ODT
- DTBook to PEF
- DTBook to RTF
- DTBook to ZedAI
- EPUB 2 to EPUB 3
- EPUB 3 Enhancer
- EPUB 3 Validator
- EPUB 3 to DAISY 2.02
- EPUB 3 to DAISY 3
- EPUB 3 to PEF
- EPUB to DAISY
- HTML to DTBook
- HTML to EPUB3
- HTML to PEF
- NIMAS Fileset Validator
- ZedAI to EPUB 3
- ZedAI to HTML
- ZedAI to PEF
- API Documentation
- Issue Tracker
- Troubleshooting
- Forum
- [[Contact|mailto:[email protected]]]
-
User Guide
- Contribute
- DAISY Home