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 6975 - WS-Transfer needs to define the term 'literal resource representation'
Summary: WS-Transfer needs to define the term 'literal resource representation'
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Transfer (show other bugs)
Version: FPWD
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Gilbert Pilz
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords: hasProposal
Depends on:
Blocks:
 
Reported: 2009-05-28 20:56 UTC by Gilbert Pilz
Modified: 2009-08-18 21:14 UTC (History)
1 user (show)

See Also:

Attachments

Description Gilbert Pilz 2009-05-28 20:56:23 UTC 
In its description of the wst:Create operation, WS-Transfer makes use of the term 'literal resource representation' but there is no precise definition of this term anywhere within the spec. Experience has shown that this lack of definition may result in interoperability problems.
Comment 1 Robert Freund 2009-06-09 16:56:48 UTC 
Action of Gil due 2009-06-10
Comment 2 Robert Freund 2009-06-30 11:10:53 UTC 
Action 78
Comment 5 Robert Freund 2009-07-08 06:09:51 UTC 
2009-07-07 Resolved with the proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jul/0006.html
 amended with the text
"Use of this URI indicates that the contents of the Delete element should be processed as specified by the WS-Fragment [WS-Fragment] specification. to "Use of this URI indicates that the contents of the Delete element MUST be processed as specified by the WS-Fragment [WS-Fragment] specification.
applied as appropriate where the underlying text appears in all four operations.