In order to reduce the calamaties caused by it being a milestone element, the attribute @new
should be made obligatory for <shift>
element. This means that the current shortcut of leaving out the attribute in cases where it would read @new=normal
should be disallowed.
While implementing this tick, we should revise the examples which do not have a @new attribute.
Making @new mandatory and removing the shortcut implied by its absence is quite plausible (maybe @new="unmarked" would be better than @new="normal" though). The production process should check automatically (once it is mandatory) that all examples do supply a value, of course.
What other "calamities" do you identify as being a consequence of its being a milestone element?
Council discussion 2014-07-01: the option of leaving out @new should be deprecated, with deprecation implemented through a Schematron constraint.
The corresponding examples without a @new attribute should be corrected ni the guidelines.
Examples changed to use new=normal; added schematron constraint to enforce presence of @new attribute [r12963]
Related
Commit: [r12963]
Forgot to close ticket: now done