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

RE: Proposed solution for Issue 4141

From: Prasad Yendluri <prasad.yendluri@webmethods.com>
Date: Tue, 9 Jan 2007 12:31:46 -0500
Message-ID: <BDD4EF3331E8FB4EA19B677CDAD6302089ADCB@ca-exbe1.webm.webmethods.com>
To: Asir Vedamuthu <asirveda@microsoft.com>, public-ws-policy@w3.org
Hi Asir,

 

I agree with your proposed refinements. 

 

Leaving the guidelines part out pending resolution of issue
<http://www.w3.org/Bugs/Public/show_bug.cgi?id=3985> 3985, here is the
updated proposal:

 

1.       Framework Document

 

In section 3.1, 5th paragraph recast the first sentence as follows:

 {The XML Infoset of a policy assertion MAY contain a non-empty [attributes]
property and/or a non-empty [children] property. Such properties, excluding
Attribute and Element Information Items from the WS-Policy language XML
namespace name, are policy assertion parameters and MAY be used to
parameterize the behavior indicated by the assertion. }

2. Primer:

 

In section "3.3 Policy Data Model", in 3rd paragraph under Figure 3.1 change
the last sentence as follows:

 

            In the XML representation, the child elements and attributes of
an assertion excluding child elements and attributes from the WS-Policy
language XML namespace name are the assertion parameters. For example
@wsp:Optional and @wsp:Ignorable are not assertion parameters.

 

Regards,

Prasad

 

-----Original Message-----
From: public-ws-policy-request@w3.org
[mailto:public-ws-policy-request@w3.org] On Behalf Of Asir Vedamuthu
Sent: Tuesday, January 09, 2007 8:03 AM
To: Prasad Yendluri; Yalcinalp, Umit; public-ws-policy@w3.org
Subject: RE: Proposed solution for Issue 4141

 

 

>{The XML Infoset of a policy assertion MAY 

>contain a non-empty [attributes] property 

>and/or a non-empty [children] property. 

>Such properties, excluding Attribute and 

>Element Information Items from the WS-Policy 

>language XML namespace name, are policy 

>assertion parameters and MAY be used to 

>parameterize the behavior indicated by the assertion. }

 

Sounds okay to me.

 

>In the XML representation, the child elements 

>and attributes of an assertion excluding Attribute 

>and Element Information Items from the WS-Policy 

>language XML namespace name are the assertion 

>parameters. For example @wsp:Optional and 

>@wsp:Ignorable are not assertion parameters

 

I suggest that we use simple words in the Primer. That is,

 

s/Attribute and Element Information Items from the WS-Policy language XML
namespace name/child elements and attributes from the policy language XML
namespace name/

 

>Guidelines Doc:

>2.2 Section 4.4.1 Assertions with Parameters 1t paragraph

 

There is a related open issue, 3985 [1].

 

[1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=3985 

 

Regards,

 

Asir S Vedamuthu

Microsoft Corporation

 

 

 

 

From: public-ws-policy-request@w3.org
[mailto:public-ws-policy-request@w3.org] On Behalf Of Prasad Yendluri

Sent: Friday, January 05, 2007 12:49 PM

To: Yalcinalp, Umit; public-ws-policy@w3.org

Subject: RE: Proposed solution for Issue 4141

 

Hi Umit, Dan et al,

 

1. I like to suggest a small amendment. Change "policy language XML
namespace name" to "WS-Policy language XML namespace name". I think it would
be good to be clear here. The revised text as follows:

{The XML Infoset of a policy assertion MAY contain a non-empty [attributes]
property and/or a non-empty [children] property. Such properties, excluding
Attribute and Element Information Items from the WS-Policy language XML
namespace name, are policy assertion parameters and MAY be used to
parameterize the behavior indicated by the assertion. }

2. This change needs to be propagated to the Primer and Guidelines documents
also.

Instead of opening a new issue for those documents to address the same
problem, I suggest the following changes in them:

 

Primer:

 

2.1 In section "3.3 Policy Data Model", in 3rd paragraph under Figure 3.1
change the last sentence as follows:

 

            In the XML representation, the child elements and attributes of
an assertion excluding Attribute and Element Information Items from the
WS-Policy language XML namespace name are the assertion parameters. For
example @wsp:Optional and @wsp:Ignorable are not assertion parameters.

 

Guidelines Doc:

2.2 Section 4.4.1 Assertions with Parameters 1t paragraph says

"Note that parameters of assertions include the following:

* Complex elements with element children that cannot be policy assertions. 

* Elements that have attributes "

     This does not account for Attributes on the assertions themselves. I
suggest adding a new1st bullet that states, "Attribute Information Items on
the assertions, excluding the Attribute Information Items from the WS-Policy
language XML namespace name". 

Thanks.

 

Prasad

________________________________________

From: public-ws-policy-request@w3.org
[mailto:public-ws-policy-request@w3.org] On Behalf Of Yalcinalp, Umit

Sent: Friday, January 05, 2007 12:03 PM

To: public-ws-policy@w3.org

Subject: Proposed solution for Issue 4141

 

Dan and I had an action item [1] to resolve [Issue4141]. Here is the
suggested wording that resolves the issue which amends the proposed text in
[3]: 

{The XML Infoset of a policy assertion MAY contain a non-empty [attributes]
property and/or a non-empty [children] property. Such properties, excluding
Attribute and Element Information Items from the policy language XML
namespace name, are policy assertion parameters and MAY be used to
parameterize the behavior indicated by the assertion. }

[1] http://www.w3.org/2005/06/tracker/wspolicy/actions/180 

[2] http://www.w3.org/Bugs/Public/show_bug.cgi?id=4141 

[3] http://lists.w3.org/Archives/Public/public-ws-policy/2007Jan/0013.html 

---------------------- 

Dr. Umit Yalcinalp 

Research Scientist 

SAP Labs, LLC 

Email: umit.yalcinalp@sap.com Tel: (650) 320-3095 

SDN: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/u/36238 

-------- 
Received on Tuesday, 9 January 2007 17:32:05 GMT

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