Skip to toolbar

Community & Business Groups

Quick-fix support for XML Community Group

Sometimes an error reported against an XML document can be fixed automatically, for example if the error refers to an unexpected attribute then an automatic fix will be to delete that unexpected attribute. We want to explore the issues related to applying quick fixes (like preserving DOCTYPE declarations, entities, etc.) and determine what actions will be needed be able to apply quick fixes on a document as well as a representation language to describe these actions.

Quick fixes are especially interesting when we use Schematron for XML validation, as in this case the quick-fix should be specified by the schema author, so we have user-defined quick fixes. Imagine for example a business rule implemented in Schematron that says that a list should contain between 4 and 8 items. If we determine that there are two items then a quick fix will propose to add automatically two more items to the list or if the list has 10 items then a quick fix may propose to delete two items or to split the list in two lists, etc.

schematron-quickfix
Group's public email, repo and wiki activity over time

Note: Community Groups are proposed and run by the community. Although W3C hosts these conversations, the groups do not necessarily represent the views of the W3C Membership or staff.

Drafts / licensing info

Date Name
Schematron Quick Fixes Specification

Status Update 2023

The specification work of this group currently rests. The purpose of keeping the group open is:

  • to answer questions about SQF via the public mailing list.
  • act as an addressing point for new implementers
  • to synchronise the SQF-Specification with updates of other standards (e.g. Schematron, XSLT/XPath) if neccessary

Release Second Draft of Schematron QuickFix specification

Dear SQF users,

we are so happy to announce the release of the Second Draft of the Schematron QuickFix specification!

You find always the newest draft here: http://schematron-quickfix.github.io/sqf/

These are the main features of the Second Draft:

  • Generic QuickFixes
  • New content model of sqf:fix to be more flexible with sqf:call-fix
  • Introduction of a localisation concept
  • Added @flags attribute for sqf:stringReplace
  • Replaced sqf:keep by sqf:copy-of
  • Lots of “To be done”s was replaced by content.

An implementation is planed in:

  • Oxygen 20.0
  • Escali Oxygen Plugin 0.2.0

Have fun!
Octavian and Nico

First Draft of Schematron Quick Fixes Specification published by Quick-fix support for XML Community Group

On 2015-05-22 the Quick-fix support for XML Community Group published the first draft of the following specification:

Participants contribute material to this specification under the W3C Community Contributor License Agreement (CLA).

If you have any questions, please contact the group on their public list: public-quickfix@w3.org. Learn more about the Quick-fix support for XML Community Group.

Call for Participation in Quick-fix support for XML Community Group

The Quick-fix support for XML Community Group has been launched:


Sometimes an error reported against an XML document can be fixed automatically, for example if the error refers to an unexpected attribute then an automatic fix will be to delete that unexpected attribute.
We want to explore the issues related to applying quick fixes (like preserving DOCTYPE declarations, entities, etc.) and determine what actions will be needed be able to apply quick fixes on a document as well as a representation language to describe these actions.

Quick fixes are especially interesting when we use Schematron for XML validation, as in this case the quick-fix should be specified by the schema author, so we have user-defined quick fixes. Imagine for example a business rule implemented in Schematron that says that a list should contain between 4 and 8 items. If we determine that there are two items then a quick fix will propose to add automatically two more items to the list or if the list has 10 items then a quick fix may propose to delete two items or to split the list in two lists, etc.


In order to join the group, you will need a W3C account.

This is a community initiative. This group was originally proposed on 2014-02-20 by George Bina. The following people supported its creation: George Bina, Mohamed ZERGAOUI, Alain Couthures, Tobias Fischer, Manuel Montero Pineda, Nico Kutscherauer. W3C’s hosting of this group does not imply endorsement of its activities.

The group now has access to W3C-hosted services for email, blog, wikis, irc, tracking tools, and more. Read more about tools and services available by default and upon request.

If you believe that there is an issue with this group that requires the attention of the W3C staff, please send us email on site-comments@w3.org

Thank you,
W3C Community Development Team