Hi all,
As promised, I have updated the Attachments for Change Requests draft to reflect my modest proposal, which we discussed in the last two working group meetings. Here is the draft: http://open-services.net/bin/view/Main/CmAttachments I'd appreciate if people could have a look and offer feedback. In writing it up, I tried to reflect the outcomes of last Wednesday's discussion, with one exception: I believe it was suggested by Steve, and generally agreed upon, that the new non-standard header (which I called Content-Name, but I'd appreciate input on the name) should be used only in the POST to create an attachment. However, it occurred to me that it could have an entirely symmetrical use on GET if the CM provider doesn't use the attachment's file name in the resource's URI. In that case, it could be very helpful for the consumer to have a hint as to what name to use if it wishes to save the file. So, I included that idea in the draft, with the intent of provoking discussion. A number of other issues came up while writing it up and reviewing the scenarios. I've marked small points with "???" and posed larger questions at the end of the appropriate sections. Cheers, Dave -- Dave Steinberg IBM Rational Software [email protected]
