title: Multiple endpoints to expose different views of the same resource
body: <p>I'm struggling to find an answer to this (perhaps because I'm not asking the question properly) ...</p>
  
  <p>I'm building API to expose resources for a basic social networking service I'm creating.
  My understanding is that the structure of URLs in an API is essentially a hierarchy, directory like structure. I think that means I can have multiple endpoints to reach the same resources or collections of resource links.
  For example:</p>
  
  <p>I have an endpoint</p>
  
  <p><code>www.domain.api.org/users/{:uid}/posts</code></p>
  
  <p>Which will return all posts sent by the user or that the user is tagged in. Seems ok, but what if I have an endpoint such as:</p>
  
  <p><code>www.domain.api.org/posts</code></p>
  
  <p>Which when hit with a http GET will return all public posts (i.e. all users' posts plus his friends' and public posts).</p>
  
  <p>The difference is that the first URL points to user owned resources whereas the second to public ones (of which the users posts are included of course)
  Are these okay or am I doing it the wrong / less sensible way? </p>
  
  <p>To reiterate, can I have multiple endpoints which point to different contexts/views of the same resource?</p>