I’m probably missing the boat here somewhere, but:
Say you’re modeling a beauty pageant (no pun intended). JUDGES fill out BALLOTS on CONTESTANTS. Each BALLOT has CATEGORIES: for example, “Poise”, “Swimsuit”, “Evening Gown”.
So far so good. Easy enough.
Let’s say you want to extend the model to include AUDITOR functions. The business rule is something like: “If a JUDGE returns a BALLOT that is missing entries for one or more CATEGORIES, the ballot is invalid and needs to be returned to the JUDGE.
So you’ve got a conceptual “bucket” that you can identify: bad ballots. How do you model that RESTfully?
??? Maybe this makes more sense the more I look at it. I was initially thinking I needed to make all sorts of funky prefix URIs like /bycategory/ and /bycompetitor/, but just putting it in the query string makes sense for filtering entities, with no controller involved.
Score another one for thinking out loud via the blog