proposed wording for Action item 10

So, I need to put more of the f2f context here, so I can understand the 
scope of this action item.......


cferris: 3.2 next
paul: asks ashok whether 3.2 is also relevant to Ashok action item
maryann: notes section 3.4 is also relevant to number and kinds of 
mechanisms
... contends 2 mechanisms rule them all
cferris: 3.3 comments?
... second group of paragraphs
paulcotton: yes, this is an example of the definition that should be 
linked to.
<scribe> ACTION: editors, improve Definition in 3rd paragraph concerning 
"policy subjects" and "subjects" [recorded in 
http://www.w3.org/2006/07/13-ws-policy-minutes.html#action10]
paulcotton: need to make it clear to domain specific specification writers 
what their responsibilities are -- a list of duties, maybe for primer, 
maybe in non norm. section

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

It's difficult to assess the current status of "second group of 
paragraphs" in relation to "policy subjects".......but this is the section 
from our latest draft


3.3 XML Element Attachment
It is often desirable to associate policies with the XML elements 
describing a subject;  this allows description formats such as WSDL to be 
easily used with the Web Services Policy Framework (see Section 4. 
Attaching Policies Using WSDL 1.1 for the specific details of WSDL 
attachment).

The precise semantics of how element policy is to be processed once 
discovered is domain-specific; however, implementations are likely to 
follow the precedent specified in the section below on WSDL [WSDL 1.1] and 
Policy.

This specification defines a global attribute that allows policy 
expressions to be attached to an arbitrary XML element. The following is 
the schema definition for the wsp:PolicyURIs attribute:
<xs:schema>
  <xs:attribute name="PolicyURIs" type="wsp:tPolicyURIs" />
</xs:schema>

The namespace URI [XML Namespaces] for this attribute is 
http://www.w3.org/@@@@/@@/policy.

The wsp:PolicyURIs attribute contains a white space-separated list of one 
or more URIs [IETF RFC 3986]. When this attribute is used, each of the 
values identifies a policy expression as defined by [Web Services Policy 
Framework]. If more than one URI is specified, the individual referenced 
policies need to be merged together to form a single element policy 
expression. The resultant policy is then associated with the element 
information item's element policy property. [Definition: The element 
policy is the policy attached to the policy subjects associated with the 
element information item that contains it.]

Note that the policy scope of the attachment is specific to the policy 
attachment Mechanism using it; accordingly, any policy attachment 
mechanism using this attribute MUST define the policy scope of the 
attachment.

An example of element policy through the use of this global attribute is 
given below using the sample policies stated in Section 2.4 Example.
If the policies referenced by the following XML element

<MyElement wsp:PolicyURIs="
   http://www.example.com/policies#RmPolicy
   http://www.example.com/policies#X509EndpointPolicy" />
 
have been processed and merged, it would result in an element policy whose 
XML 1.0 representation is listed in Example 3-1:
(01) <wsp:Policy
        xmlns:rmp="http://docs.oasis-open.org/ws-rx/wsrmp/200602"
        xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
        xmlns:wsp="http://www.w3.org/@@@@/@@/policy" >
(02)   <rmp:RMAssertion>
(03)     <rmp:InactivityTimeout Milliseconds="600000" />
(04)       <rmp:BaseRetransmissionInterval Milliseconds="3000" />
(05)       <rmp:ExponentialBackoff />
(06)       <rmp:AcknowledgementInterval Milliseconds="200" />
(07)     </rmp:RMAssertion>
(08)   <sp:AsymmetricBinding>
(09)     <wsp:Policy>
(10)       <!-- Details omitted for readability -->
(11)       <sp:IncludeTimestamp />
(12)       <sp:OnlySignEntireHeadersAndBody />
(13)     </wsp:Policy>
(14)   </sp:AsymmetricBinding>
(15) </wsp:Policy>

Note that this element policy has no meaningful URI.

The presence of the wsp:PolicyURIs attribute does not prohibit 
implementations from using additional mechanisms for associating policy 
expressions with XML-based constructs.

Alternatively, rather than using the global attribute, XML elements may 
use the wsp:Policy or wsp:PolicyReference elements directly as children, 
in order to support element policy, and the semantics for this are the 
same as for the use of the global attribute. For example, an alternative 
way of attaching the policies in the above example, using child elements, 
would be as follows: 
<MyElement>
  <wsp:PolicyReference
     URI="http://www.example.com/policies#RmPolicy" />
  <wsp:PolicyReference
     URI="http://www.example.com/policies#X509EndpointPolicy" />
<MyElement/>


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

so what do we do here for improving the definition of "subject" and 
"policy subject"?

I suggest we replace some of the text in 3.2 and the  first two paragraphs 
of text above with the following, since I think the issue of "subject" is 
really that we don't have a defintion of "web services subjects" and their 
corresponding representation in XML ( i believe this is coming up in other 
action items as well)  and this might be a way of showing the relationship 
between the two:


3.2 Policy Attachment Mechanisms
This section defines two general-purpose mechanisms for associating 
policies [Web Services Policy Framework] with one or more <Web Services>  
policy subjects <(web services requestors, web service providers, web 
service endpoints, etc) >. The first allows XML-based descriptions of 
resources to associate policy as part of their intrinsic definition. The 
second allows policies to be associated with arbitrary policy subjects 
independently from their definition.

3.3 XML Element Attachment and Web Services Subjects
It is often desirable to associate policies with <Web services policy 
subjects some of which can be represented as XML elements, i.e, WSDL 1.1 
element descriptions >
the XML elements describing a subject;  this allows description formats 
such as WSDL to be easily used with the Web Services Policy Framework (see 
Section 4. Attaching Policies Using WSDL 1.1 for the specific details of 
WSDL <1.1>attachment). <In this section we specify a general model for how 
to associate WS-Policy expressions with the XML elements that have been 
defined by the WSDL working group > 

<Since the Policy assertions are strongly typed by WS- policy domain 
authors, t>he precise semantics of how <each XML> element policy is to be 
processed once discovered is domain-specific; however, implementations are 
likely to follow the precedent specified in the section below <which 
describes the recommended method for >on WSDL [WSDL 1.1] and Policy.

Maryann