Comment 1 Konstantin Komissarchik 2012-03-19 18:51:29 EDT

Could you describe why controlling the order is important? The possible types are put in a sorted set at pretty low level in the model. Supporting preserving the original order isn't trivial. I want to make sure that it is worth it.

Comment 2 Ling Hao 2012-03-19 19:23:39 EDT

I have a case in which 2 of the elements are short, ie <short-elem/>, but 1 one
of the element <long-elem> .... </long-elem> is very complex. The 2 short elements should be grouped together. 

Lowering priority to P5.

Comment 3 Konstantin Komissarchik 2012-03-19 19:28:01 EDT

I don't see why complexity of the options should dictate the relative order of these options. Please try again. :)

... Cause this isn't about the priority of this task... If there isn't a good justification to be found, this will end up as a won't fix...

Comment 4 Ling Hao 2012-03-19 19:34:53 EDT

In my particular schema, the 2 short elements are predefined and have a specific meaning, or you can select the third option which is for customization. The 2 predefined elements should go together.

Comment 5 Konstantin Komissarchik 2012-03-21 00:57:09 EDT

Ok. I think I understand the requirement here. This one is kinda tricky. From model standpoint, the order isn't relevant, so it feels rather wrong to force preservation of order through the model API. That leaves specifying explicit order in sdef. Maybe a sorting service. This needs more thought...