- From: Monica J. Martin <Monica.Martin@Sun.COM>
- Date: Mon, 26 Mar 2007 17:16:05 -0700
- To: "public-ws-policy@w3.org" <public-ws-policy@w3.org>
Everyone, Another issue was to be opened as a result of resolution of Issue 4262 related to Primer and questions on understandability and mode. To optimize, this was combined with the complementary resolution to Issue 4393. There is currently no need to open a new issue. References: * Proposal (for Issue 4393 that includes minor change to resolve Action 256): * http://lists.w3.org/Archives/Public/public-ws-policy/2007Mar/0120.html * Issue 4393: http://www.w3.org/Bugs/Public/show_bug.cgi?id=4393 * Action 256: http://www.w3.org/2005/06/tracker/wspolicy/actions/256 * Update to Issue 4262 (see comment 2): http://www.w3.org/Bugs/Public/show_bug.cgi?id=4262#c2 As an additional comment, we may wish to consider a global change consistent with the correction in 2. below (to alleviate confusion which could exist). Changes specific to Action 256 are as follows (as outlined in email in 1. above): 1. Add at the end of Section 3.4.1, Primer just before the last statement on domain-specific processing (as a separate paragraph): Regardless of mode, the wsp:Ignorable marker does not affect the behavior of the client. If the resulting policy contains assertions marked with wsp:Ignorable, those assertions the client understands are not ignored. 2. Change/correct a bit of existing text in Section 3.4.1, Primer. Change from: When using the strict intersection mode ignorable assertions are part of the policy alternative vocabulary, so the |wsp:Ignorable| attribute does not impact the intersection result even when the |wsp:Ignorable| attribute value is “true”. Change to: When using the strict intersection mode, assertions marked with wsp:Ignorable are part of the policy alternative vocabulary, so the |wsp:Ignorable| attribute does not impact the intersection result even when the |wsp:Ignorable| attribute value is “true”.
Received on Tuesday, 27 March 2007 00:16:15 UTC