title: Using REST design properly - Categories and Subcategories
body: <p><em>I have two question on basic <code>REST</code> concepts.</em></p>
  
  <p><strong>QUESTION 1</strong>:  Categories</p>
  
  <p>So I have a list of Categories I want to show from a database.</p>
  
  <p><code>SELECT * from categories</code></p>
  
  <p>Currently, I use this REST desgin:  <code>/api/v1/categories/</code> </p>
  
  <p>Is that proper?  </p>
  
  <p>I have also seen <code>/api/v1/categories/list/</code>  -- or is this preferred?  (If so, then what would a simple <code>/categories</code> call display then?   (Or would the proper way then be <code>/api/v1/category/list</code> where <code>category</code> is singular and adding <code>list</code> will show you all categories -- this way a call to <code>/category</code> would allow veiwing info on just one?)</p>
  
  <p><strong>QUESTION 2</strong>:  Subcategories.  (Think "Seinfeld" as a subcategory of "Television".)</p>
  
  <p><code>SELECT * FROM subcategories" WHERE category_id = {id}</code> </p>
  
  <p>The <code>id</code> above might be the Television Category where I want to get specific shows listed.</p>
  
  <p>Would I do <code>/api/v1/categories/{id}/</code> for the Subcategory with the subcat_id? Would I have to use parameters instead like <code>/Categories?id={id}/</code></p>
  
  <p>How would this relationship work?</p>