title: RESTful API design - /users/:userId/resourceType vs. /resourceType/?user=:userId
body: <p>I'm spinning my tires a bit and I'm curious to know what others have decided on given the same scenario.</p>
  
  <p>To get a list of <code>resourceType</code> for user identified by <code>:userId</code> from a RESTful API, what URI pattern makes the most sense, if I have resources that would be addressed as:</p>
  
  <blockquote>
    <p>/users/:userId/resourceType // Return list of resourceType for :userId</p>
  </blockquote>
  
  <p>versus:</p>
  
  <blockquote>
    <p>/resourceType/?userId=:userID // Query a list of the resourceType </p>
  </blockquote>
  
  <p>I keep thinking "do both" - but it feels impractical considering how many permutations are possible with complex resource models. </p>
  
  <p>Is it just 'pick one and move on' scenario or is there one that's pragmatically better than the other and I'm just not seeing it?</p>