title: WCF REST : Case insensitive Query String Parameters, suggested naming convention - use underscore or?
body: <p>It appears the query string parameters you can pass to a rest method in WCF REST is case insesitive - actually this makes sense.</p>
  
  <p>What the best naming convention for parameters with 2 words, using an _ (underscore) ?? I never liked this, i prefered to use camelCasing but if its insensitive what other options to do i have?</p>
  
  <p>for example here is my method's WebGet </p>
  
  <pre><code>  [WebGet(UriTemplate = "?skip={skip}&amp;top={top}&amp;unansweredOnly={unansweredOnly}")]
  </code></pre>
  
  <p>Notice i have the word  <strong>unansweredOnly</strong>, so i could do this unanswered_only.... or of course i could leave it like unansweredOnly (camelcasing) but of course unansweredonly would also work...  but i could show it as UnansweredOnly in the documentation for the service.</p>
  
  <p>Now something surprising is that in the help page of wcf rest service it shows it as camelcasing :-)</p>
  
  <pre><code>  (from help page)  ?skip={skip}&amp;top={top}&amp;unansweredOnly={unansweredOnly}
  </code></pre>
  
  <p>I suppose i am trying to get an idea what everyone is doing, aand whats the recommended way of doing things.</p>
  
  <p>I would really apprecaite some feedback.</p>
  
  <p>I don't want to get into a bad habit </p>
  
  <p>Thanks in advance</p>