Skip to content

2025 edition #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 25 commits into
base: main
Choose a base branch
from
Open

2025 edition #9

wants to merge 25 commits into from

Conversation

AndrewSales
Copy link
Contributor

This PR incorporates all changes required by the 2025 edition of the standard.

@AndrewSales
[MOD] new root element library, re Schematron/schematron-enhancement-…
58c1549 
…proposals#39

extends available at top level, enabling import of library etc
new element rules to group abstract rules, re Schematron/schematron-enhancement-proposals#3 and Schematron/schematron-enhancement-proposals#39
new element group for rule processing without if-then-else behaviour, re Schematron/schematron-enhancement-proposals#25
new attribute severity, re Schematron/schematron-enhancement-proposals#58
@AndrewSales
[MOD] new attribute as, re Schematron/schematron-enhancement-proposals#1
de1465c
@AndrewSales
[MOD] new element active-group, re Schematron/schematron-enhancement-…
b3b941d 
…proposals#25

new element error in (active-*), re Schematron/schematron-enhancement-proposals#47
new attribute severity, re Schematron/schematron-enhancement-proposals#58
@AndrewSales
[MOD] adds value-of and name to emph, dir and span, re Schematron/sch…
7b967bc 
…ematron-enhancement-proposals#37
@AndrewSales
[MOD] add name to model for diagnostic; common decl for message text
de35269
@AndrewSales
[MOD] add optional title to rule, to facilitate svrl:fired-rule/@name;
a532c83 
add optional role attribute to pattern and group, to facilitate svrl:active-*/@ROLE;
add optional role attribute to svrl:diagnostic-reference, in line with svrl:property-reference
re Schematron/schematron-enhancement-proposals#5, Schematron/schematron-enhancement-proposals#7
@AndrewSales
[MOD] new optional attribute schematronVersion, re Schematron/schemat…
7e3f659 
…ron-enhancement-proposals#42
@AndrewSales
[MOD] SVRL equivalent, re Schematron/schematron-enhancement-proposals#42
0d5fffc
@AndrewSales
[MOD] value of flag attribute is a list of tokens, re Schematron/sche…
61be2c9 
…matron-enhancement-proposals#12
@AndrewSales
[MOD] schema-level params, re Schematron/schematron-enhancement-propo…
f2ea42c 
…sals#34;

abstract pattern params, re Schematron/schematron-enhancement-proposals#8
@AndrewSales
[ADD] unit tests for schematron.sch
9a54584
@AndrewSales
[MOD] WIP, re Schematron/schematron-enhancement-proposals#8
f612212
@AndrewSales
[MOD] rules and unit tests in support of abstract pattern parameters,…
8e62512 
… re Schematron/schematron-enhancement-proposals#8
@AndrewSales
[FIX] typo
3410580
@AndrewSales
[MOD] require schema param value, re Schematron/schematron-enhancemen…
16efc79 
…t-proposals#34
@AndrewSales
[MOD] date
684253c
@AndrewSales
[FIX] typo, re Schematron/schematron-enhancement-proposals#42
147ec85
@AndrewSales
[MOD] svrl:error as child of root element, re Schematron/schematron-e…
bb90662 
…nhancement-proposals#69
@AndrewSales
[MOD] add attribute from, re Schematron/schematron-enhancement-propos…
574aba6 
…als#72
@AndrewSales
[MOD] mandatory svrl:error and human-text, for errors occurring befor…
9bff057 
…e validation begins
@AndrewSales
[MOD] attribute visit-each, re Schematron/schematron-enhancement-prop…
5456295 
…osals#75
@AndrewSales
[MOD] add optional params and lets; make patterns optional, re Schema…
3342fbd 
…tron/schematron-enhancement-proposals#39
@AndrewSales
[MOD] new optional attribute phase/@when
200f135
@AndrewSales
[FIX] align attribute name with DIS, re Schematron/schematron-enhance…
745c2f4 
…ment-proposals#42
@AndrewSales
[FIX] changes to reflect DIS comments
f12483d
@tgraham-antenna
Copy link
Member

We currently don't have a separate repository for the 2020 schemas.

Who, other than @AndrewSales, is able to confirm that the PR matches the DIS?

@AndrewSalesBMY
Copy link

AndrewSalesBMY commented Sep 24, 2025 •
edited
Loading

We currently don't have a separate repository for the 2020 schemas.

Can we just tag the current state of main before merging in?

Who, other than @AndrewSales, is able to confirm that the PR matches the DIS?

:-o

@tgraham-antenna
Copy link
Member

We previously made separate repositories by duplicating this repository as schema-2016, and so on. Their commit histories start at the same date, but they're not forks tracked by GitHub.

I suspect that someone either pushed an up-to-date clone of this repository to a new, dated repository on GitHub or renamed the schema repository to schema-year then pushed an up-to-date clone to a new schema repository. The second way would keep the issues and PRs with the schema version to which they (mostly) apply.

It would be possible to make this repository a 'template repository' for a new schema repository, but it wouldn't be possible to merge between branches in the new schema repository because branches created from a template "have unrelated histories".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@AndrewSales @tgraham-antenna @AndrewSalesBMY