title: RESTful Best Practices - How to name a report resource
body: <p>I am creating a RESTful API and following best practices for it and I became in a big doubt with this.</p>
  
  <p>I need to create a report (with charts, and data tables) that it's made of analyze another resources (evaluations), and many other params makes this report to be variable on the data that shows.</p>
  
  <p>So, looking for best practices, I don't know if I need to get all the data, and process it at Javascript, to make the report (client side) so the RESTful pattern is not a problem;</p>
  
  <p>Or how can I name a resource "report" that is made of many other resources. My <em>non restful mind</em> wants to create a <code>/api/rest/reports/executiveReport?evaluation=:id&amp;competences=:id&amp;competences=:id&amp;employee=:id</code> uri</p>
  
  <p>How can I achieve this in a beautiful RESTful pattern uri? I don't want to process the data at Javascript, as there are many errors, or exceptions that I can't catch. I prefer to deliver the report to be shown.</p>
  
  <p>Thanks!</p>