This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The Framework spec says "Assertions within an alternative are not ordered, and thus aspects such as the order in which behaviors (indicated by assertions) are applied to a policy_subject are beyond the scope of this specification". However, the SecurityPolicy spec requires ordering between signing and encryption and defines assertions to control the order between such assertions. We feel that ordering between assertions may be required in other cases as well and request an ordering mechanism between such assertions. For example, consider an assertion that adds something to a message. Perhaps a timestamp. We may want to say that the timestamp is added before a log record is written.
Resolved at Sep F2F meeting: http://www.w3.org/2006/09/13-ws-policy-minutes.html Add the following text after the quoted text in 3638: "However, domain authors can write assertions that control the order in which behaviours are applied."