Open Source License For Databases?

Myddrin asks: "Recently there has been lot of discussion of databases, and who owns them. The US either is considering or passed a law saying a Database(and info contained there-in) is owned by the creating person/company. [I honestly can't remember.] At anyrate, this got me thinking of a the (possible) need for Database GPL (DGPL). Basically the same as the LGPL, but adding that the database host (i.e. the owner of the server hosting the specific instance of the db) can put restrictions on access allowing them to offset the cost of hosting the machine (administration, i'net connection, etc)." Any data in a database is content, just like information on a web page. Maybe an Open Content License might be a better idea? Thoughts? (More)

"...Examples of acceptable restrictions would be:

1. any program accessing this database must display the advert. provided,
2. a cost of $.000000001 per record returned
3. a nominal monthly subscription fee...

something like that. Very similar to the part of the (L)GPL that says you can charge a nominal fee for the materials of distrubution. The idea is that several competing servers could be set up, with multiple competing open and closed source clients running against it.

Is there a license that allows this kind of thing, or should I be working on one? "