Why has a Human Task only 1 UI?

Question

A little more abstract / philosophical discussion.
I'm not really comfortable with the rigid "1 Human Task (HT) corresponds to 1 screen (UI)", although it will be all right for 90% of the time. Could be that the BPMN spec itself is to blame for this.
Some cases:
>1 Humans are coorperating on 1 Task.
1 Human has a UI open (on the computer screen) displaying multiple Tasks.
1 Human has UI open displaying multiple Process instances for which he is responsible and drills down to a Human Task in an instance that is being performed by one of his colleagues. He opens the same task in read-only mode.
1 Human is performer of Tasks in sequence ("Road Map" or Wizard control) and doesn't want to go back to the UWL all the time. He must be able to go back to a previous step (~task) though.
1 Human breaks off his current Task (saves his work so far), and continues working on the Task later on on his mobile device.
1 Human has a generic UI screen (portal) open, and a Process token just moved into a Human Task for that Human. He doesn't have to go back to the UWL, search for that task and open it, but sees a nice UI-overlay-effect of that Task (just the title, or instance), just as Outlook displays incoming messages.
1 Human who "owns" a Process instance, checks the state of the instance, notices that a subprocess within is in error (or takes too long), overrides that subprocess by doing work manually (rolling back the already completed activities within the subprocess), and providing the subprocess output.
What are your thoughts? Are these cases too far-fetched?

Answer 1

You now have 2 site. Your own and the one by your son.
Since your son published last, iWeb created an index.html file in the root of the server (iDisk>Web>Sites) to redirect to his site.
That file first redirected to your site, now it redirects to his.
To make it redirect to your site again, simply move one of your pages to the top of the list and back. iWeb now thinks your default page has changed and will create a new index.html file when you publish.
Make sure your son does not update his Site.
Other solution. Buy the Family pack and give each member of the family his/her own MMe account. They have to manage that acount from their own useraccount on a Mac. Otherwise everybody interferes with each other.