The content model of implications in the "plus" sublanguages interferes with stripe-skipping for the if and then edges in the XSD schema. Because stripe-skipping is currently implemented in an "all-or-nothing" fashion, this forced the generated XSDs for these languages to disallow stripe-skipping for "plus" sublanguages. However, stripe-skipping should be allowed for edges other than if and then, even in the "plus" sublanguages.
Option 1b has been accepted.
In particular
Split the stripe-skipping Relax NG module into two - one for the if and then edges, and another for all other skippable stripes. The "s" (serialization) component of the myng-code would be expanded to accommodate the module splitting.
Do not expose fine-grained stripe-skipping options in the MYNG GUI, but only allow it to be accessed through the REST interface (e.g. the myng-code URL), since it is only needed for the auto-generation of XSDs. The one existing stripe-skipping checkbox would be retained, corresponding when enabled to optional stripe-skipping for all skippable stripes (include both stripe-skipping modules) and when disabled to the fully-normalized syntax (include neither stripe-skipping module).
For the RuleML Wiki Issue http://wiki.ruleml.org/index.php/Stripe-Skipping_for_Plus_Sublanguages,
The content model of implications in the "plus" sublanguages interferes with stripe-skipping for the if and then edges in the XSD schema. Because stripe-skipping is currently implemented in an "all-or-nothing" fashion, this forced the generated XSDs for these languages to disallow stripe-skipping for "plus" sublanguages. However, stripe-skipping should be allowed for edges other than if and then, even in the "plus" sublanguages.
Option 1b has been accepted.
In particular
The issue http://wiki.ruleml.org/index.php/Backward-Incompatible_Change_in_Dis_Anchor_Languages_in_Version_1.01 will also be addressed in this branch, as they are closely related.