W3C home > Mailing lists > Public > public-ws-policy@w3.org > June 2007

[Bug 4662] [Guidelines] Proposal for AI 305 - Comments relative to Issue 4662

From: Monica J. Martin <Monica.Martin@Sun.COM>
Date: Fri, 22 Jun 2007 09:22:20 -0700
To: "'mhondo@us.ibm.com'" <mhondo@us.ibm.com>, "public-ws-policy@w3.org" <public-ws-policy@w3.org>
Message-id: <467BF73C.7040001@sun.com>

Following in the same stead as Asir, here are my comments relative to 
Issue 4662 [1] that have already been posted [2].

   1. Comments related to context found in Section 5.4.2 - attachment to
      this email shows changes:
      http://lists.w3.org/Archives/Public/public-ws-policy/2007Jun/0063.html
   2. Comment: Update text Best Practice 11 and the succeeding text to
      be consistent with recent Framework changes in Section 3.1. [3]
          * Change from: Best practice 11: Use Nested Assertions for
            Dependent Behaviors - "An assertion author should represent
            dependent behaviors that are relevant to a compatibility
            test and apply to the same policy subject using nested
            policy assertions."
          * Change to: Best practice 11: Use Nested Assertions for
            Dependent or Associated Behaviors - "An assertion author
            should represent dependent or associated behaviors that are
            relevant to a compatibility test and apply to the same
            policy subject using nested policy assertions.
   3. Comment: Related to comment above to account for either dependent
      or associated behavior.
          * Change from: "Therefore, when providers require dependent
            behaviors these behaviors should be explicitly specified as
            assertions in a nested policy expression. When the
            definition of an assertion allows for nested dependent
            behaviors, but the use of the assertion only contains an
            empty nested policy expression, this specific use indicates
            the specification of no nested dependent behaviors."
          * Change to: "Therefore, when providers require dependent or
            associated behaviors these behaviors should be explicitly
            specified as assertions in a nested policy expression. When
            the definition of an assertion allows for nested behaviors,
            but the use of the assertion only contains an empty nested
            policy expression, this specific use indicates the
            specification of no nested behaviors."
   4. Comment: Consistent with Asir's question, on first Best Practice
      in Section 5.7: "Best Practice: Preserve Context-Free Policies" 
      By default, context is part of policies. This should be specific
      to the attachment mechanism being independent of the policy 
      alternative.

[1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=4662
[2] http://lists.w3.org/Archives/Public/public-ws-policy/2007Jun/0069.html
[3] http://www.w3.org/Bugs/Public/show_bug.cgi?id=4579
Received on Friday, 22 June 2007 16:21:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:20:52 GMT