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

[Bug 4695] Editorial Comments on Guidelines

From: <bugzilla@wiggum.w3.org>
Date: Fri, 22 Jun 2007 16:57:46 +0000
CC:
To: public-ws-policy-qa@w3.org
Message-Id: <E1I1mSA-0003Dh-RI@wiggum.w3.org>

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

           Summary: Editorial Comments on Guidelines
           Product: WS-Policy
           Version: CR
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Guidelines
        AssignedTo: fsasaki@w3.org
        ReportedBy: monica.martin@sun.com
         QAContact: public-ws-policy-qa@w3.org


Several editorial comments have been provided on the current draft of the
Guidelines in the discussions on Issues 4660-4664 and 4672.[1]

Here are the editorial comments that do not relate to the Issues referenced
above but are associated comments already logged. [2]

1. Comment: Minor editorial nits [3]

2. Comment: In Section 5.3.4, consider reiterating reuse: [2]
Change from: "New Assertion Authors should focus on creating assertions for
those specific constraints and capabilities that do not overlap with other
domains but that communicate new functionality."
Change to: "New Assertion Authors should focus on creating assertions for those
specific constraints and capabilities that do not overlap with other domains
but that communicate new functionality or reuse existing policy assertions
where possible."

3. Comment: Specify this important information earlier in Section 5.4 rather
than waiting until after Best Practice 12; suggested location for specifying
this is at the end of first paragraph in Section 5.4. Keep similar information
later after Best Practice 12. [2] Reference: 
"It is important to note that the main consideration for selecting parameters
or nesting of assertions is that the framework intersection algorithm processes
nested alternatives, but does not consider parameters in its algorithm."

Corresponding to this, provide similar guidance later (where text originally
occurred).[2] Comment: For text to be retained after Best Practice 12:
Change from: "The main consideration for selecting parameters or nesting of
assertions is that the framework intersection algorithm processes nested
alternatives, but does not consider parameters in its algorithm."
Change to: "As previously indicated, nested policy assertions in policy
alternatives are processed by the framework intersection algorithm while
assertion parameters are not."

4. Comment: In Section 5.4.1, make clear than an assertion parameter is
additional qualifying information consistent with the Framework. [2]
Change from: "An assertion author should represent useful (or additional)
information necessary for engaging the behavior represented by a policy
assertion as assertion parameters."
Change to: "An assertion author should represent useful additive information
necessary for engaging the behavior represented by a policy assertion as 
assertion parameters."

[1]
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4660
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4661
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4662
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4663
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4664
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4672
[2] http://lists.w3.org/Archives/Public/public-ws-policy/2007Jun/0069.html
[3] Two files on editorial nits found in
http://lists.w3.org/Archives/Public/public-ws-policy/2007Jun/0069.html with
files:
http://lists.w3.org/Archives/Public/public-ws-policy/2007Jun/att-0069/Web_Services_PolicyGuidelines-strawman-diff-editorial-comment.doc
http://lists.w3.org/Archives/Public/public-ws-policy/2007Jun/att-0069/Web_Services_PolicyGuidelines-strawman-diff-editorial-comment.pdf
Received on Friday, 22 June 2007 16:57:49 GMT

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