#512 Make @new obligatory attribute of <shift>

GREEN
closed-accepted
5(default)
2014-08-10
2014-06-26
No

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.

Discussion

  • Laurent Romary

    Laurent Romary - 2014-06-26

    While implementing this tick, we should revise the examples which do not have a @new attribute.

     
  • Lou Burnard

    Lou Burnard - 2014-06-26

    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?

     
  • Martin Holmes

    Martin Holmes - 2014-07-01

    Council discussion 2014-07-01: the option of leaving out @new should be deprecated, with deprecation implemented through a Schematron constraint.

     
  • Martin Holmes

    Martin Holmes - 2014-07-01
    • assigned_to: Lou Burnard
    • Group: AMBER --> GREEN
     
  • Laurent Romary

    Laurent Romary - 2014-07-01

    The corresponding examples without a @new attribute should be corrected ni the guidelines.

     
  • Lou Burnard

    Lou Burnard - 2014-08-10

    Examples changed to use new=normal; added schematron constraint to enforce presence of @new attribute [r12963]

     

    Related

    Commit: [r12963]

  • Lou Burnard

    Lou Burnard - 2014-08-10
    • status: open --> closed-accepted
     
  • Lou Burnard

    Lou Burnard - 2014-08-10

    Forgot to close ticket: now done

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks