Author: ymartel Date: 2014-02-19 17:29:51 +0100 (Wed, 19 Feb 2014) New Revision: 406 Url: http://chorem.org/projects/chorem/repository/revisions/406 Log: some update on doc Modified: trunk/chorem-webmotion/src/doc/REST_API_Timer.txt Modified: trunk/chorem-webmotion/src/doc/REST_API_Timer.txt =================================================================== --- trunk/chorem-webmotion/src/doc/REST_API_Timer.txt 2014-02-19 16:15:27 UTC (rev 405) +++ trunk/chorem-webmotion/src/doc/REST_API_Timer.txt 2014-02-19 16:29:51 UTC (rev 406) @@ -45,10 +45,9 @@ Should the {user} parameter in URL or just as request parameter ? - If want to follow Restfull resources hierarchy, we should have projects > {project} > quotations > {quotation} > tasks > {task} > times (or workers) > {time} (or {worker}) In this, the user is more a kind of filter on the request, So, I prefer keep it as request parameter +As we have simple hierarchy, we can also simplify the URLs, and begin the hierarchy directly from a specific Task : - - +tasks > {task} > times (or workers) > {time} (or {worker})