7014 2009-06-11 19:38:20 +0000 Transfer: Define a "Resource Representation" ContentDescription URI 2009-08-18 21:13:41 +0000 1 1 1 Unclassified WS-Resource Access Transfer FPWD PC Windows XP CLOSED REMIND hasProposal P2 normal --- 1 dug dug public-ws-resource-access-notifications oldest_to_newest 25543 0 dug 2009-06-11 19:38:20 +0000 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. 25672 1 dug 2009-06-23 12:34:05 +0000 Add: http://.../ContentDescription/Literal 25829 2 dug 2009-06-30 13:42:31 +0000 more detailed proposal: http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jun/0060.html 25902 3 bob 2009-07-07 19:52:19 +0000 proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jul/0006.html 25907 4 bob 2009-07-08 06:08:48 +0000 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.