RE: Guidelines Doc Review - By Prasad and Asir

Sorry, that should have been a1), a3) and a4).

 

________________________________

From: public-ws-policy-eds-request@w3.org
[mailto:public-ws-policy-eds-request@w3.org] On Behalf Of Prasad
Yendluri
Sent: Sunday, May 20, 2007 5:03 PM
To: Asir Vedamuthu; public-ws-policy-eds@w3.org
Subject: RE: Guidelines Doc Review - By Prasad and Asir

 

Hi,

 

I forgot to send a follow-up email on this but, I finished a10, a2) and
a3) on Friday. 

I also updated Appendix E (Major changes since last revision).

 

Regards,

Prasad

 

________________________________

From: public-ws-policy-eds-request@w3.org
[mailto:public-ws-policy-eds-request@w3.org] On Behalf Of Asir Vedamuthu
Sent: Sunday, May 20, 2007 11:05 AM
To: public-ws-policy-eds@w3.org
Cc: Prasad Yendluri
Subject: RE: Guidelines Doc Review - By Prasad and Asir

 

Fixed a5) and a6).

 

Added editors' note in Section 5.8 - To be re-structured to use the
format in the Architecture of the WWW doc.

 

Added editors' note in Section 5.5 - Looks incomplete - carries Good
Practices but there isn't any explanatory text.

 

Added editors' note in Section 5.1 - May 9th 07, an issue was opened
against G2 - issue 4566.

 

Regards,

 

Asir S Vedamuthu

Microsoft Corporation

 

From: public-ws-policy-eds-request@w3.org
[mailto:public-ws-policy-eds-request@w3.org] On Behalf Of Asir Vedamuthu
Sent: Friday, May 18, 2007 4:40 PM
To: public-ws-policy-eds@w3.org
Cc: Prasad Yendluri
Subject: Guidelines Doc Review - By Prasad and Asir

 

Prasad and I reviewed the Guidelines document and discovered a few
items.

 

a)   The following Good Practices from the IBM and MS contribution are
missing in the Guidelines document:

1)   G1 - An assertion author should reuse an existing assertion (rather
than create a new one) whenever possible.

Designated home: 5.3.4

2)   G2 - An assertion author should define policy assertions for
behaviors that are relevant to compatibility tests, such as web service
protocols that manifest on the wire.

Open issue: 4556

3)   G3 - An assertion author should use a unique QName to identify a
distinct behavior.

Designated home: 5.3.2

4)   G20 - An assertion author should start with a simple working
assertion that allows assertion parameter extensibility.

Designated home: 5.3.1

5)   G21 - An assertion description should clearly specify how the
assertion may compose with other related assertions, if any.

Designated home: 5.8

6)   G22 - An assertion author should not define policy assertions to
represent information that is necessary to understand a message.

Designated home: 5.3.3

b)   Section 5.5 looks incomplete - carries Good Practices but there
isn't any explanatory text.

 

Prasad is fixing items a1), a3) and a4). Asir is fixing items a5) and
a6).

 

Regards,

 

Asir S Vedamuthu

Microsoft Corporation