W3C home > Mailing lists > Public > public-ws-policy@w3.org > September 2006

RE: Issue 3703 - Clarify that element item always assertion in policy expression

From: Asir Vedamuthu <asirveda@microsoft.com>
Date: Thu, 14 Sep 2006 06:33:37 -0700
Message-ID: <4DF3D07B9910264B9470DA1F811D1A950B8FBAF3@RED-MSG-43.redmond.corp.microsoft.com>
To: Frederick Hirsch <frederick.hirsch@nokia.com>, <public-ws-policy@w3.org>

This change looks good. I request the WG to assign this change to the
editors.

Regards,
 
Asir S Vedamuthu
Microsoft Corporation

-----Original Message-----
From: public-ws-policy-request@w3.org
[mailto:public-ws-policy-request@w3.org] On Behalf Of Frederick Hirsch
Sent: Wednesday, September 13, 2006 8:10 AM
To: public-ws-policy@w3.org
Cc: Hirsch Frederick
Subject: Issue 3703 - Clarify that element item always assertion in
policy expression


Issue 3703 - <http://www.w3.org/Bugs/Public/show_bug.cgi?id=3703>

Description - Change sentence in 2.2 to clarify that element  
information item in policy expression must be treated as an assertion

Justification -

Section 2.2 of Framework states "If an Element Information item is not
recognized, it SHOULD be treated as an assertion."

This sentence is not necessary, but if kept should state MUST.

The document is clear that an XML element contained within a Policy  
Expression
is always an assertion (unless wsp:Policy, wsp:ExactlyOne, wsp:All)

Target - WS-Policy Framework [1]

Proposal:
Change SHOULD to MUST.

Test: doc review.

[1] http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy- 
framework.html?content-type=text/html;%20charset=utf-8

regards, Frederick

Frederick Hirsch
Nokia
Received on Thursday, 14 September 2006 13:34:30 GMT

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