See Jacob's post here: http://jacobian.org/writing/rest-worst-practices/

Basically, it's a bad idea to couple something like django-piston too tightly to the underlying models because in any even moderately useful API there will be plenty of resources you want to expose that are actually cobbled together from various different models (or even other storage locations such as a search index or external web service).