Proceedings

Abstract:

When XML is used as a human-authored source language within an edit/process/test cycle, it becomes important to optimize the workflow involved in this cycle, and in particular, the reporting and recovery from errors. The XML specifications distinguish between well-formedness and validation, and between validation warnings, errors, and fatal errors. Unfortunately, neither of these distinction is optimal for an XML development workflow. This session presents a case study of a system designed to present document errors in a way that optimizes the development cycle, and discusses the challenges involved in building this system on top of standard tools and schemas.