This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section 2.2 of Framework states "If an Element Information item is not recognized, it SHOULD be treated as an assertion." This sentence is not necessary, but if kept should state MUST. The document is clear that an XML element contained within a Policy Expression is always an assertion (unless wsp:Policy, wsp:ExactlyOne, wsp:All) Proposed resolution: Change SHOULD to MUST.
In template format: Description - Change sentence in 2.2 to clarify that element information item in policy expression must be treated as an assertion Justification - Section 2.2 of Framework states "If an Element Information item is not recognized, it SHOULD be treated as an assertion." This sentence is not necessary, but if kept should state MUST. The document is clear that an XML element contained within a Policy Expression is always an assertion (unless wsp:Policy, wsp:ExactlyOne, wsp:All) Target - WS-Policy Framework [1] Proposal: Change SHOULD to MUST. Test: doc review. [1] http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-framework.html?content-type=text/html;%20charset=utf-8
Proposal adopted as editorial action. Minutes: http://www.w3.org/2006/09/14-ws-policy-irc#T17-28-05