Hacker News new | past | comments | ask | show | jobs | submit login

The relevant quotes in tzdata are in the files (tzcode and tzdata are public domain):

northamerica:

  # From Paul Eggert (2006-03-22):
  # A good source for time zone historical data in the US is
  # Thomas G. Shanks, The American Atlas (5th edition),
  # San Diego: ACS Publications, Inc. (1991).
  # Make sure you have the errata sheet; the book is somewhat useless without it.
  # It is the source for most of the pre-1991 US entries below.
europe:

  # From Paul Eggert (2006-03-22):
  # A good source for time zone historical data outside the U.S. is
  # Thomas G. Shanks and Rique Pottenger, The International Atlas (6th edition),
  # San Diego: ACS Publications, Inc. (2003).
As far as I know, even if the book is copyrighted, the raw information contained in it shouldn't be?



> the raw information contained in it shouldn't be?

That's correct. Supreme Court decision. Said decision is the reason why you occasionally read news articles about the U.S. considering some form of database protection laws - to make those databases protectable under law (and therefore to make this lawsuit legitimate).


Most European nations have database protection laws. Although limited in scope and doesn't prevent you from compiling an identical database from other sources, it has insane side-effects. In the Netherlands for instance, the zip-code database is copyright protected.


As is the train timetable info for the bizarre reason to block competition for a new tender.


So that's why the journey planners in NL are a complete fail (ns, 9292ov). Always wondered, since NL is quite up to date in general when it comes to IT.


Actually, there's a lot of work being done, as we speak to change the situation on various levels. In 2013 I believe there will be a public tender for a "National Public Transport Data Warehouse", 9292ov will be supervising it I think, not bidding though.

Then there's the openOV project, a new project bringing together data from lots of sources and talking to lots of transport companies and agencies. Most transport tenders include a clause requiring data to be supplied to "national journey planners", so there's hope. Just today they're working on GTFS feeds for most of the Netherlands.

The Dutch Railways (NS) now has an API but it's mainly consumer facing data, and nothing truely helpful.

tl;dr: Our transit APIs are stuck in 2005 but making headway.


The complaint is worded to indicate that the atlas contains interpretations based on extensive original historical research. I suppose they are arguing that these aren't published facts that exist anywhere in the historical record. They reconstructed what was possibly in effect during many time periods based on possibly anecdotal historical documentation. I'm no lawyer, but I suspect some concrete examples of this would come up during the trial.

  These atlases set forth interpretations of historical
  time zone information pertaining to innumerable locations
  throughout the world, based upon the compilation of
  historical research and documentation regarding 
  applicable time zones officially and/or in actuality in 
  effect, given the actual latitude and longitudes of 
  specific locations throughout the world.


tzdata and tzcode are also interpretations of the data where the decision to accept Shanks' info or not is made for every entry in the database, for example:

  # Austria

  # From Paul Eggert (2006-03-22): Shanks & Pottenger give 1918-06-16 and
  # 1945-11-18, but the Austrian Federal Office of Metrology and
  # Surveying (BEV) gives 1918-09-16 and for Vienna gives the "alleged"
  # date of 1945-04-12 with no time.  For the 1980-04-06 transition
  # Shanks & Pottenger give 02:00, the BEV 00:00.  Go with the BEV,
  # and guess 02:00 for 1945-04-12.


That wouldn't be relevant though. No one disputes the fact that Olson would have the copyright to his own work.


I believe the issue is that copying the Atlas directly would not be permitted, but using it as a research source would be allowed.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: