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 7014 - Transfer: Define a "Resource Representation" ContentDescription URI
Summary: Transfer: Define a "Resource Representation" ContentDescription URI
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:
Blocks:
 
Reported: 2009-06-11 19:38 UTC by Doug Davis
Modified: 2009-08-18 21:13 UTC (History)
0 users

See Also:

Attachments

Description Doug Davis 2009-06-11 19:38:20 UTC 
Now that we have ContentDescription attribute we should define
a well-known URI for "literal resource representation" so that
it can be reused by multiple implementations. If each one defines
there own then we run into interop problems.
Comment 1 Doug Davis 2009-06-23 12:34:05 UTC 
Add:
 http://.../ContentDescription/Literal
Comment 2 Doug Davis 2009-06-30 13:42:31 UTC 
more detailed proposal:
http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jun/0060.html
Comment 4 Robert Freund 2009-07-08 06:08:48 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.