<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi,<div><br><div><div>On Nov 3, 2014, at 4:29 AM, Paul Harrison wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div><blockquote type="cite"><br class="Apple-interchange-newline"> * When an XML document is submitted as single parameter, how must it be stored in the UWS service: as one parameter (with byReference=true) or as some individual parameters which has been extracted from the XML document?<br></blockquote><br>I think that it should be stored as a single “parameter” - there should be no attempt by the generic UWS to interpret the document.<br><br>I think that it would probably be a good convention that if the initial POST has a application/x-www-form-urlencoded encoding, then the UWS can assume that the parameter/value pair mechanism can be used.</div></span></blockquote></div><br></div><div>Except that the best practices is that application/x-www-form-urlencoded encoding is used with all POSTs, irrespective if it is a single XML document or parameterized. So you seem to be saying that if an XML document is submitted as a single "parameter" then some alternate encoding should be specified - would you care to suggest which one?</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Cheers,</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Matthew</div></body></html>