RFC: Multiple extension to the nodequeue module

For my company's next project we are interested in developing multiple modules that extend the functionality of the Nodequeue module. We are interested in reading thoughts and other comments regarding our proposals. Which features would you like to see in the following proposed modules? Do you know of something similar that might provide us with a solid base to work on? Do you see any possible performance issues regarding these proposals?
We are, of course, interested in knowing if someone is working on similar extentions and/or would like to join forces.

Multiple nodequeues per user

This module will give users the ability to create their own nodequeues, multiple nodequeue per each user.
Proposed permissions: create nodequeues, edit own nodequeues, access user nodequeues

Nodequeue node

Similar to what Taxonomy node does for taxonomy pages, this module will create a node for each nodequeue. Browsing to a nodequeue's node displays the node's content followed by the nodequeue. This will allow nodequeue creators to write a description/prologue for each nodequeue, and append CCK fields, etc...

Nodequeue annotate

Append annotations to individual nodes inside a nodequeue. Best described with an example, imagine we have two nodequeues -NQ1- and -NQ2-, both containing the node -NOD1-. With this module a privileged user can annotate -NOD1- in -NQ1-, and then annotate -NOD1- in -NQ2-, without overriding the first annotation. Then, viewing -NQ1- will display the first annotation next to -NOD1- and viewing -NQ2- will display the second annotation next to -NOD1-.

We intend to decouple as much as possible. The most problematic decoupling is between Multiple nodequeues per user and Nodequeue node, which we thought to solve by simply assuming that when user -USR- creates nodequeue -NQ- (with Multiple nodequeues per user), the node that is automatically created for nodequeue -NQ- belongs to user -USR-. If a privileged user changes the ownership of either the node or the nodequeue, the other part will be changes automatically - this should be the only dependant piece of code between these two modules and it does not require full dependency.

Another possible coupling is between Multiple nodequeues per user and Nodequeue annotate - We can allow private annotations or multiple annotations, etc. This is beyond the scope of our own project, but depending on public interest we might develop some of this functionality.

As a side note, we also plan on exporting the entire content of each nodequeue's node as an OAI-ORE feed. I believe this is a side note as it's a very specific request that might not have a broad audience as the above might have, but still might interest some...