title: REST URL naming convention /items/{id} vs /items?id={id}
body: <p>I understand that in MVC pattern and in REST services it is common to use URIs like <code>/items/{id}</code> but what is bad thing about using query parameters in the URI?</p>
  
  <p><code>GET /items/{id}</code> vs <code>GET /items?id={id}</code></p>
  
  <p>Further, lets say an entity has 'referenceId' field that points to some related (say parent) entity, and I need to create REST service to get all items for parent entity, which way is better:</p>
  
  <pre><code>GET(POST) /items/parent/{parentId} 
  </code></pre>
  
  <p>or</p>
  
  <pre><code>GET(POST) /items?parent={parentId}
  </code></pre>
  
  <p>Will be grateful for insights that would help to resolve my subjective issues on constructing URLs for REST services.</p>