I ended up extending DJRF to do nested collections, but I'd argue your REST topology would be better with one canonical resource and unique team IDs: /teams/<i

I ended up extending DJRF to do nested collections, but I'd argue your REST topology would be better with one canonical resource and unique team IDs: /teams/<id>/ It's fine to be able to add a user to a team by posting to a subcollection though, but there should only be one URL for the resource (IMHO).