This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Transfer is silent on some key interoperability issue w.r.t. transfer data between the client and service: - how does the client know the schema of the resource(s) behind an EPR - how does the client know what instructions (QNames) are allowed in the create - how does the client know the schema returned on the Get (if its different from the first bullet) Since the Transfer wsdl/xsd only shows an xs:any, those metadata files are not really very useful in determining this information.
proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Oct/0018.html
minor tweak - per Ram: When present, this OPTIONAL parameter .... (add OPTIONAL)
Resolved with Comment #2 with the following modification When present, this OPTIONAL parameter .... (add OPTIONAL)
Add OPTIONAL to all specs/all optional policy parameters