No; an update to a schema is not the same thing as a completely different schema.
The implications of what I am saying is we merge the PRs to master, tag 1.0.2, and are done.
As a style author, I can simply stay on master, and update the schema as needed.
The implications of a new 1.x for every minor changes means, most likely, one of two strategies:
- create separate
- create separate schema patterns on one
csl.rncfile to cleanly separate 1.0 and 1.1 validation, which means an already complex schema gets more complex.
What I mean by 2 is something like this conceptually:
style = style-1.0 | style-1.1
… where every place in the schema where we add stuff, we have to split off separate patterns for different 1.x releases.
So the PR’s I just submitted wouldn’t be the right path, I think; I’d need to refactor to explicitly separate out 1.0 and 1.1 variables.
I think I’m right here, and if I am, doesn’t that explain why this is a problem?
By “level” you mean x.x.x.x?
So in this case, you’d say the variable changes 1.0.2, and intext is 1.1, and rearrange some core CSL model structure would be 2.0?