Re: [Bug 4211] WSDL WG Editorial comments on Attachment

Thanks for your comments. The WS-Policy Working Group tracked this as a Last Call Issue 4211 [1].

The Working Group agreed to fix the problems as detailed in-line below [3].

Please let us know if you have any difficulty with these resolutions. 

[1] http://lists.w3.org/Archives/Public/public-ws-policy/2007Jan/0099.html
[2] http://www.w3.org/Bugs/Public/show_bug.cgi?id=4211
[3] IRC Anchor: http://www.w3.org/2007/01/16-ws-policy-irc#T19-14-27

On Saturday, January 13, 2007, at 12:10AM, "Paul Cotton" <Paul.Cotton@microsoft.com> wrote:
>
>-----Original Message-----
>From: public-ws-policy-qa-request@w3.org [mailto:public-ws-policy-qa-request@w3.org] On Behalf Of bugzilla@wiggum.w3.org
>Sent: January 12, 2007 6:58 PM
>To: public-ws-policy-qa@w3.org
>Subject: [Bug 4211] WSDL WG Editorial comments on Attachment
>
>
>http://www.w3.org/Bugs/Public/show_bug.cgi?id=4211
>
>           Summary: WSDL WG Editorial comments on Attachment
>           Product: WS-Policy
>           Version: LC
>          Platform: All
>        OS/Version: All
>            Status: NEW
>          Severity: minor
>          Priority: P2
>         Component: Attachment
>        AssignedTo: fsasaki@w3.org
>        ReportedBy: jonathan@wso2.com
>         QAContact: public-ws-policy-qa@w3.org
>
>
>8. Effective Policy (3.1)
>- The second paragraph is very cumbersome. The first phrase in the first
>sentence should be broken out into its own sentence, to read, "When multiple
>attachments are made, their relevant policies can be combined."
>- The third paragraph has the same problem. The first phrase in the first
>sentence should be broken out into its own sentence, to read, "This combination
>can be achieved through a merge."

[cbb] The WG resolved to make these editorial changes as above.

>9. XML Element Attachment (3.3)
>- Element Information Item should reference its definition in XML Infoset [3].

[cbb] The first usage of 'element information item' is in WS-Policy Attachments Section 3.3. 
http://www.w3.org/TR/2006/WD-ws-policy-attach-20061117/#XMLElementAttachment

The WG proposed to resolve this with the following editorial change:
 s/The resultant policy is then associated with the element information item's element policy property./The resultant policy is then associated with the element information item's (as defined in [XML Information Set]) element policy property./
The WG agreed to adopt this resolution. 

>10. Security Considerations (7)
>- Policy attachments "signing" is RECOMMENDED but there is no reference to what
>is indicated by "signing" or to any standards work (W3C or other) around any
>such signing. Does this refer to WSS signatures [6]? The use of "signing"
>itself in this language should reference any such standard(s).

[cbb] The WG proposed to make the following editorial change to resolve this:
Replace: "It is RECOMMENDED that policies and assertions be signed to prevent tampering", 
the first sentence of Section 7 Security Considerations with: 
"It is RECOMMENDED that policies and assertions be integrity protected to permit the detection of tampering. This can be done by using a technology such as [XML D-Sig], [SSL/TLS], or [WS-Security 2004]. 
The WG agreed to adopt this resolution.

Received on Tuesday, 16 January 2007 20:25:44 UTC