[Bug 4262] [Guidelines] Use of @wsp:optional and @wsp:Ignorable on the same assertion

http://www.w3.org/Bugs/Public/show_bug.cgi?id=4262





------- Comment #2 from monica.martin@sun.com  2007-03-26 22:45 -------
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.

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

Changes specific to Action 256 are as follows:

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, assertion 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 Monday, 26 March 2007 22:45:09 UTC