Feature request: Better overview and access to different versions
The way I understand it, there are four relevant revisions of Schematron that people may have an interest in using:
- ISO 2016
- ISO 2020
- ISO 2025
- dev (latest development, which may turn into the next official ISO release, e.g. ISO 2028)
They can be found in these ways (I think):
- ISO 2016: has its own repo
- ISO 2020: can be found in this repo, if I find the right historical revision
- ISO 2025: this repo, branch
2025-edition
- dev: the
main branch
E.g.: I would like to compare 2025 to 2020, and I find it more difficult than it should be to find the 2020 version.
I don't know exactly what is the best way in general, but from my point of view it would be perfect if they were in the same repo but there was a folder for each version. Also, it would avoid some confusion with deployed files if the files included the version number. It could look like this:
schema
├── 2016/
│ ├── isoschematron_2016.rnc
│ ├── isoschematron_2016.sch
├── 2020/
│ ├── isoschematron_2020.rnc
│ └── isoschematron_2020.sch
├── 2025/
│ ├── isoschematron_2025.rnc
│ └── isoschematron_2025.sch
└── dev/
├── isoschematron_dev.rnc
└── isoschematron_dev.sch
Or even better, if there are revisions:
schema
├── 2016/
│ ├── isoschematron_2016.rnc
│ ├── isoschematron_2016.sch
│ └── isoschematron_2016-r2.sch
├── 2020/
│ ├── isoschematron_2020.rnc
│ └── isoschematron_2020.sch
├── 2025/
│ ├── isoschematron_2025.rnc
│ ├── isoschematron_2025-r2.rnc
│ ├── isoschematron_2025-r3.rnc
│ └── isoschematron_2025.sch
└── dev/
├── isoschematron_dev.rnc
└── isoschematron_dev.sch
Sincerely, Thomas
Feature request: Better overview and access to different versions
The way I understand it, there are four relevant revisions of Schematron that people may have an interest in using:
They can be found in these ways (I think):
2025-editionmainbranchE.g.: I would like to compare 2025 to 2020, and I find it more difficult than it should be to find the 2020 version.
I don't know exactly what is the best way in general, but from my point of view it would be perfect if they were in the same repo but there was a folder for each version. Also, it would avoid some confusion with deployed files if the files included the version number. It could look like this:
Or even better, if there are revisions:
Sincerely, Thomas