This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 7068 - Transfer: what's the schema of the resource
Summary: Transfer: what's the schema of the resource
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Transfer (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Doug Davis
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords: hasProposal
Depends on: 6694
Blocks:
  Show dependency treegraph
 
Reported: 2009-06-29 13:32 UTC by Doug Davis
Modified: 2009-12-08 22:11 UTC (History)
0 users

See Also:


Attachments

Description Doug Davis 2009-06-29 13:32:10 UTC
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.
Comment 3 Doug Davis 2009-10-20 19:51:48 UTC
minor tweak - per Ram:

When present, this OPTIONAL parameter .... (add OPTIONAL)
Comment 4 Robert Freund 2009-10-20 19:52:45 UTC
Resolved with Comment #2 with the following modification
When present, this OPTIONAL parameter .... (add OPTIONAL)
Comment 5 Doug Davis 2009-10-20 19:53:31 UTC
Add OPTIONAL to all specs/all optional policy parameters