title: REST - Canonical URI vs Relative URI (from a user point of view)
body: <p>I'm currently designing a service.
  It is a multi-tier service, that stores data from several clients using a REST interface.</p>
  
  <p>It's not clear to me how should I accept a resource id inside the URI.
  Let's say the user <code>001</code> creates a resource, the first for him, but the 100th for the system.</p>
  
  <p>What should I return when the user 001 makes a GET to <code>/resource/1</code> (<code>/resource/{id}</code>). Should I display his record thus making the URI relative to the user performing the request? Or should I return the 1st for the system (denying it because it's missing the permissions to see it)?</p>
  
  <p>I don't want to go deep inside the authorization stuff, but I'd like to know how should I handle this kind of situations. If I should prefer the latter then how can I make a user say "ok, give me the 1st resource I created" or "give me the 2nd ... ", "give me the last .. ", "give me the 100th resource I created"?</p>