title: URI of REST to reflect relationship of resources?
body: <p>I knew some <a href="http://microformats.org/wiki/rest/urls" rel="nofollow">name conversions of REST API</a>, for example resource name should be plural, using different HTTP method with same URI to perform different action on that resource, etc.</p>
  
  <p>But as <strong>URI should reflect relationship of resources</strong>, I am a little confused. Take SO as a example, when update a existed comment of a answer, URI should looks like:</p>
  
  <pre><code>PUT /{contextPath}/questions/{questionId}/answers/{answerId}/comments/{commentId}
  </code></pre>
  
  <p>But I feel awkward when using this <code>so-called standard</code> URI because:</p>
  
  <ol>
  <li>It's a little verbose, especially when the hierarchical is very
  deep. </li>
  <li>questionId and answerId is completely unnecessary here, since
  commentId is sufficient for server to identify a comment record.</li>
  </ol>
  
  <p>So what's the appropriate way to deal with this? should I always follow name conversions, or make some changes when the relationship hierarchical of resources is <strong>very deep</strong>?</p>