Tony Graham
Tony Graham
One stumbling block (other than the people) for making changes to the Schematron code, such as #48, is the absence of a comprehensive test suite for making sure that changes...
This moves everything in `trunk` up one level and removes the `trunk` directory. It also removes `.svn`, `CVS`, `.hgignore`, and `.DS_Store` files/directories left over from previous incarnations. (It's also a...
Also removed `.hgignore`.
`xsd2sch` should be moved to a separate repository under the Schematron organisation. Subversion lets you checkout part of a project -- e.g., just the `xsd2sch` part -- but Git doesn't....
`converters` should be moved to a separate repository under the Schematron organisation. Since the code under `converters` does three different things -- or more than three, depending on how finely...
@phax commented in #55 that Schematron should use semantic versioning for releases. I agree that semantic versioning should be used. The current single release -- https://github.com/Schematron/schematron/releases/tag/2017-02-09 -- exists because we...
Should use regex for these instead of just checking they are not empty.
E.g., for `fo:retrieve-marker`, checking that there could be a matching `fo:marker` within current or previous `fo:page-sequence`.
Currently will complain unless value is `empty` or `string`, which is so wrong in so many ways.
REx can also generate a parser as a Saxon extension function. It should be possible, and it should be faster, to use the expression parser as a Saxon extension function...