[Bug 7728] New: Attaching Policy to Indicate MEX/MEX Features Supported

http://www.w3.org/Bugs/Public/show_bug.cgi?id=7728

           Summary: Attaching Policy to Indicate MEX/MEX Features Supported
           Product: WS-Resource Access
           Version: FPWD
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: MetadataExchange
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: ashok.malhotra@oracle.com
         QAContact: public-ws-resource-access-notifications@w3.org


On the August 18 Telcon (see minutes
http://www.w3.org/2002/ws/ra/9/08/2009-08-18.html)
We agreed to a direction re. using Policy on endpoints based  on my  note:
http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Aug/0033.html
This note made 2 points:

1. Endpoint policy is contained within the Metadata child of the EPR as
recommended by WS-Addressing

<wsa:EndpointReference>
  <wsa:Address>xs:anyURI</wsa:Address>
  <wsa:ReferenceParameters>xs:any*</wsa:ReferenceParameters>
  <wsa:Metadata>
    *( <wsp:Policy ...> ... </wsp:Policy> |
        <wsp:PolicyReference ...> ... </wsp:PolicyReference> )?*
      ...
  </wsa:Metadata>
</wsa:EndpointReference>

2. In WS-RA the use of Policy is primarily to indicate Endpoint capabilities. 
To allow domain independent processing, each capability MUST be indicated by a
policy assertion with a unique QName i.e. the assertion QName indicates the
capability.

Now, we need to apply this direction to MEX to indicate whether MEX is
supported and which MEX features are supported.

Clearly, the above points need to be applied to other specs as well.  For
example, how RM assertions are attached to the NotifyTo EPR for eventing, but
these issues need to be raised independently.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

Received on Friday, 25 September 2009 18:48:56 UTC