Re: Revised proposal 3965: Clarify text surrounding PolicyReference and for usage of wsp:Name attribute (primer)

>Yalcinalp, Umit wrote: Hi Fabian, 
>I have a question. 
>
>In 2, it seems that this is not really a Primer issue but should be part
>of the Framework spec. I am curious why you targeted this point for the
>Primer. 
>  
>
mm1: Umit, perhaps we could separate concerns: policy retrieval, Policy 
Reference, and any related question on wsdl:import. Currently on the 
first, the Framework specifies in Section 4.3.4, Policy References 
(embedded in this section):

    "For an external policy expression, there is no requirement that the
    IRI be resolvable; retrieval mechanisms are beyond the scope of this
    specification."

Most of the new Section 3.6 in the Primer specifies examples of such.

On the second point, there are various references in the Framework on 
identification and reference (sections 4.2 Policy Identification, 4.3.4 
Policy References, and 4.3.5 Policy Inclusion). On final point, are you 
suggesting further specification regarding wsdl:import?

Note, 6 December is a Finnish holiday and Fabian won't be available 
until Thursday.  Thanks.

>>-----Original Message-----
>>From: public-ws-policy-request@w3.org 
>>[mailto:public-ws-policy-request@w3.org] On Behalf Of Fabian Ritzmann
>>Sent: Tuesday, Dec 05, 2006 7:38 AM
>>To: public-ws-policy@w3.org
>>Subject: Revised proposal 3965: Clarify text surrounding 
>>PolicyReference and for usage of wsp:Name attribute (primer)
>>
>>
>>I've updated the proposal for issue 3965 as discussed in last 
>>week's conf call.
>>
>>http://www.w3.org/Bugs/Public/show_bug.cgi?id=3965
>>
>>
>>
>>Title
>>
>>Clarify text surrounding PolicyReference and cover wsdl:import use
>>
>>
>>Description
>>
>>See Justification and Proposal
>>
>>
>>Justification
>>
>>The description of retrieving policy references seems 
>>mislocated in section 3.2
>>(normalization). wsdl:import is used frequently in real WSDL 
>>documents and
>>should be covered when policy references are discussed.
>>
>>
>>Target
>>
>>Primer
>>
>>Note: At some point, if section 5.1 of the Guidelines is extended, the
>>Guidelines may be affected.
>>
>>
>>Proposal
>>
>>1.a)
>>
>>Create a new section after section 3.5. Name the new section 
>>"3.6 Policy
>>Retrieval".
>>
>>Move the entire block of text in Section 3.2 to the newly 
>>created section 3.6:
>>
>>"Just as other service metadata languages, Web Services 
>>Policy does not mandate
>>any specific policy retrieval mechanism ... If the referenced 
>>policy expression
>>is in the same XML document as the reference, then the policy 
>>expression should
>>be identified using the wsu:Id (XML ID) attribute and 
>>referenced using an IRI
>>reference to this XML ID value."
>>
>>1.b)
>>
>>Add a reference to the end of section 3.2: "See section 3.6 
>>for more details
>>how to retrieve referenced policy expressions."
>>
>>2.
>>
>>Add to the end of the newly created section 3.6:
>>
>>WSDL 1.1 [WSDL 1.1] section 2.1 and WSDL 2.0 [WSDL 2.0 Core 
>>Language] chapter 4
>>allow to import or include WSDL documents into another WSDL 
>>document with the
>>wsdl11:import, wsdl20:import, and wsdl20:include statements. 
>>The importing and
>>imported WSDL documents constitute separate XML documents 
>>each. If e.g. the
>>importing WSDL document references a policy in the imported 
>>WSDL document, the
>>rules for policy references between separate XML documents 
>>apply as described
>>in section 2.8. 
>>
>>
>>
>>
>>
>>    
>>
>
>  
>

Received on Wednesday, 6 December 2006 00:05:28 UTC