While I am still concerned to some extent about this bill, as I read it the situation is not nearly as dire as the posting suggests. To begin with, the claim that the bill
...allows treble damages to be levied against anyone who uses information that's in a database that a corporation asserts it owns.
is untrue. It imposes no liability on users of a database. It deals only with people who
...make[s] available in commerce to others a quantitatively substantial part of the information in a database...
Unless I have missed something, you can make use of any data you can get your hands on. What you can't do is distribute to others the whole database or substantial chunks of it. Furthermore,
the owner of the database can't just claim to own it; it has the burden of showing that it generated the database through a substantial investment of money or time.
The bill is fairly restrictive. It exempts government databases, explicitly permits hyperlinking, and contains exceptions for news reporting and educational and research uses.
Furthermore, the restriction only applies if
the unauthorized redistribution "inflicts an injury", where this is defined as follows:
For purposes of subsection (a), the term `inflicts an injury' means serving as a functional equivalent in the same market as the database...
I'm not sure how this is to be interpreted, but it
seems to me that it may permit derivative works insofar as they are not functionally equivalent to the original. In sum, I'm nervous about restrictions on databases too, but this bill seems to be pretty narrow. Its possible it prohibits things I wouldn't want to see prohibited, but it doesn't seem to be nearly as awful as suggested.
I'd like to see a proper analysis of the intent and legal interpretation of this bill.
For the first example consider public records. Yes another database provider may manually reconstruct the entire set of public records each government entitiy creates. What happens when the government entity then enters into contract with the database provider to submit an electronic dataset. For example check out MuniCode [municode.com]. I could go down to my local city hall and get an entire copy of the municipal codes and manually type them and post them. However, this places me at a severe disadvantage over MuniCode. In fact this bill could prevent government agencies from selling electronic data submissions to multiple vendors since once the first vendor receives the data he may claim copyright on the collection and sue the government agency.
For the second example, consider telephone directories. The local telephone provider has a nice monopoly on this data since they are the creator and maintainer of the data. Once they publish the "phone book" it becomes a database. The only way another company can compete to produce directories would be to manually contact each home, business, etc. and collect the information from them. It would be illegal to simply copy the text of the phone book, rearrange it and publish with added value. BTW, check the link in the editorial linked to in the/. story post -- this happened!!! With this law it would be illegal!!!
Is this bill really so bad? (Score:4, Insightful)
While I am still concerned to some extent about this bill, as I read it the situation is not nearly as dire as the posting suggests. To begin with, the claim that the bill
is untrue. It imposes no liability on users of a database. It deals only with people who
Unless I have missed something, you can make use of any data you can get your hands on. What you can't do is distribute to others the whole database or substantial chunks of it. Furthermore, the owner of the database can't just claim to own it; it has the burden of showing that it generated the database through a substantial investment of money or time.
The bill is fairly restrictive. It exempts government databases, explicitly permits hyperlinking, and contains exceptions for news reporting and educational and research uses. Furthermore, the restriction only applies if the unauthorized redistribution "inflicts an injury", where this is defined as follows:
I'm not sure how this is to be interpreted, but it seems to me that it may permit derivative works insofar as they are not functionally equivalent to the original. In sum, I'm nervous about restrictions on databases too, but this bill seems to be pretty narrow. Its possible it prohibits things I wouldn't want to see prohibited, but it doesn't seem to be nearly as awful as suggested. I'd like to see a proper analysis of the intent and legal interpretation of this bill.
Re:Is this bill really so bad? (Score:4, Insightful)
For the first example consider public records. Yes another database provider may manually reconstruct the entire set of public records each government entitiy creates. What happens when the government entity then enters into contract with the database provider to submit an electronic dataset. For example check out MuniCode [municode.com]. I could go down to my local city hall and get an entire copy of the municipal codes and manually type them and post them. However, this places me at a severe disadvantage over MuniCode. In fact this bill could prevent government agencies from selling electronic data submissions to multiple vendors since once the first vendor receives the data he may claim copyright on the collection and sue the government agency.
For the second example, consider telephone directories. The local telephone provider has a nice monopoly on this data since they are the creator and maintainer of the data. Once they publish the "phone book" it becomes a database. The only way another company can compete to produce directories would be to manually contact each home, business, etc. and collect the information from them. It would be illegal to simply copy the text of the phone book, rearrange it and publish with added value. BTW, check the link in the editorial linked to in the