title: Aggregate data in RESTful API
body: <p>Have an interesting HTTP API question that I'd like some opinions on.  My API allows people to rate things on a 1-10 scale.  I have a <code>GET /ratings</code> endpoint that lists a user's ratings.  We also want a way to show the user's average rating per day.  So my question - should the summary be the same url, like <code>/ratings?data=summary</code>, or should it be its own url like <code>/ratingsummaries</code> or <code>/ratings/summary</code>?</p>
  
  <p>As is often the case, I don't think there is a right answer.  Is the summary just another view of ratings, in which case it would be the ratings resource and should be part of <code>/ratings</code>?  Or, is a summary of ratings its own resource, in which case it deserves its own url like <code>/ratingsummaries</code>?  <code>/ratings/summary</code> looks nice too but it isn't really a sub-resource of ratings.  </p>
  
  <p>Looking forward to your feedback.  Thanks all!</p>