Slashdot Mirror


Copyright Status of Thermodynamic Properties?

orzetto writes "I work at a research institute, and programming models of physical systems is what I do most of the time. One significant problem when modeling physical processes is finding thermodynamic data. There are some commercial solutions, but these can be quite expensive, and to the best of my knowledge there are no open source efforts in this direction. In my previous job, my company used NIST's Supertrapp, which is not really that expensive, but is written in Fortran, and an old-fashioned dialect at that. As a result, it is a bit difficult to integrate into other projects (praised be f2c), and the programming interface is simply horrible; worse, there are some Fortran-induced limitations such as a maximum of 20 species in a mixture. I was wondering whether it would be legal to buy a copy of such a database (they usually sell with source code, no one can read Fortran anyway); take the data, possibly reformatting it as XML; implement a new programming interface from scratch; and publish the package as free software. Thermodynamic data is not an intellectual creation but a mere measurement, which was most likely done not by the programmers but by scientists funded with our tax money. What are your experiences and opinions on the matter? For the record, I am based in Germany, so the EU database directive applies."

154 comments

  1. FORTRAN by pilsner.urquell · · Score: 4, Funny

    FORTRAN awful? Give me a break.

    </sarcasm>

    1. Re:FORTRAN by Nefarious+Wheel · · Score: 4, Funny

      Integer*16 I

      Real*4 Still

      Real*4 Think

      Integer*16 In

      Real*4 Fortran

      C you insensitive clod!

      --
      Do not mock my vision of impractical footwear
    2. Re:FORTRAN by Anonymous Coward · · Score: 4, Informative

      Huh? Recent versions (ie, in the past couple decades) of Fortran are really very decent for scientific calculation, in many respects better than C. There's a ton of computational chemistry software, for example, written primarily in modern Fortran.

    3. Re:FORTRAN by Anonymous Coward · · Score: 0

      Fortran really is not that hard to read, it's just part of the reality of programming. We will always be moving forward but will always require the ability to understand how we got there in the first place. I'm starting to think that Indian guy was right. U.S. technology graduates really are worthless.

    4. Re:FORTRAN by Anonymous Coward · · Score: 0

      Yeah, but most stuff is written not in modern fortran where you can actually have variable names of a decent length, but in cruddy old fortran that's impossible to read.

    5. Re:FORTRAN by Anonymous Coward · · Score: 0

      Or in this case, German technology graduates.

    6. Re:FORTRAN by Anonymous Coward · · Score: 1, Funny

      FORTRAN awful? Give me a break.

      </sarcasm>

      break;

    7. Re:FORTRAN by orkybash · · Score: 2, Interesting

      Most stuff written *today* is written in modern fortran where you can actually have variable names of a decent length. Most legacy code that you have to rely on (e.g. linear algebra routines) are written in the cruddy old fortran. But it's solid code, works as a black box, and I would venture to guess that it's not a *whole* lot less readable than your average implementation of printf. Plus, if you want to update it to modern fortran, be my guest - hope you have a lot of time, patience, money, and a good set of unit tests....

    8. Re:FORTRAN by Anonymous Coward · · Score: 0

      It's silly.

    9. Re:FORTRAN by Anonymous Coward · · Score: 0

      Ahh, Slashdot ate my correctly formatted sarcasm XML tag! My "It's silly." post is just stupid now (or it could have been that before too).

    10. Re:FORTRAN by Anonymous Coward · · Score: 1, Funny

      switch (i)
      {
      case me: ....
              break; ....
      }

      oooops that's C not Fortran but have a break on me

    11. Re:FORTRAN by MaskedSlacker · · Score: 4, Informative

      I used to work solely in FORTRAN for simulation work. The big advantage of Fortran90/95 over C is that the compilers are heavily optimized for doing iterated operations over every value of an array. So for say, fluid dynamics, it really is the best. I suspect you might be able achieve a similar speed in C, but that you would have to hand optimise instead (ugh).

    12. Re:FORTRAN by tyrione · · Score: 1

      I used to work solely in FORTRAN for simulation work. The big advantage of Fortran90/95 over C is that the compilers are heavily optimized for doing iterated operations over every value of an array. So for say, fluid dynamics, it really is the best. I suspect you might be able achieve a similar speed in C, but that you would have to hand optimise instead (ugh).

      I'd mod these comments up but I don't have the points. It's clear this site lacks Mechanical Engineers who all learned Fortran and C.

    13. Re:FORTRAN by PitaBred · · Score: 1

      Should be a lot easier to transform cruddy old Fortran to modern Fortran than it is to transform it into some other language.

    14. Re:FORTRAN by plopez · · Score: 1

      fortran 95 is OO

      --
      putting the 'B' in LGBTQ+
    15. Re:FORTRAN by Anonymous Coward · · Score: 0

      XML awful? Give me a break.

    16. Re:FORTRAN by Anonymous Coward · · Score: 0

      The code written in ForTran for guiding submarine launched missiles built in Sunnyvale, California, went viral a long time ago. This code would be extremely difficult to re-qualify in some CS major's pipe dream language.

  2. Department by Anonymous Coward · · Score: 0

    What does the department line "consider-crown-copyright" mean? Is it a clever pun in relation to thermodynamics? Aside from any possible puns, I don't see how crown copyright could be relevant to Germany.

    1. Re:Department by morgan_greywolf · · Score: 3, Informative

      Anything produced by the United States Federal Government (which the National Institute of Standards and Technology certainly qualifies as), is in the public domain.

      That's what he meant.

  3. NIST - Public Domain by John+Hasler · · Score: 4, Informative

    If the NIST program is the product of the work of US Government employees it is in the public domain. I would not be surprised if many of the commercial closed-source programs for the same purpose are based on it. In any case, tabulated data is not protected by US copyright so someone in the US could certainly do as you suggest.

    --
    Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    1. Re:NIST - Public Domain by Odinlake · · Score: 1

      ...tabulated data is not protected by US copyright...

      What does that mean exactly? Seems to me any digital information could be called "tabulated data", more or less directly.

    2. Re:NIST - Public Domain by morgan_greywolf · · Score: 2, Informative

      OTOH, Maybe they just ripped off the Koreans.

      Looks like the same info to me.

      (But IANAP)

    3. Re:NIST - Public Domain by morgan_greywolf · · Score: 1

      P=Physicist. I am a Programmer. (Duh)

    4. Re:NIST - Public Domain by maxwell+demon · · Score: 1

      I think it means that you don't gain copyright by merely putting data which is not otherwise copyrighted into a table.
      Of course if you already have the copyright on the things in the table, you won't lose that copyright by putting it into the table.

      For example, the following table is probably not covered by copyright:

      List of decimal digits
       
      Digit Value
        0 0
        1 1
        2 2
        3 3
        4 4
        5 5
        6 6
        7 7
        8 8
        9 9

      IANAL, however.

      --
      The Tao of math: The numbers you can count are not the real numbers.
    5. Re:NIST - Public Domain by Anonymous Coward · · Score: 1, Insightful

      Duh? Why is it obvious that you are a programmer?

    6. Re:NIST - Public Domain by Anonymous Coward · · Score: 2, Interesting

      It appears that there is an exemption to the public domain status which applies here:

      15 U.S.C. Â 290e authorizes U.S. Secretary of Commerce to secure copyright for works produced by the Department of Commerce under the Standard Reference Data Act.[8]

    7. Re:NIST - Public Domain by Repossessed · · Score: 1

      It means you need to have some sort of creativity.

      So if I take tabulated data and arrange it in a pattern that I think looks neat, I can copyright that. But if its just arranged alphabetically, I can't.

      --
      Liberte, Egalite, Fraternite (TM)
    8. Re:NIST - Public Domain by budgenator · · Score: 0

      Facts can not be copyrighted in the US, when you purchase a Karaoke disk, the lyrics are a fact. they are the lyrics copyrighted by the author so only the author would hold the copyright, not the Karaoke disk publisher, so they always change at least one word, they then hold the copyright on the change, making it easier to protect their work. When you play Trivial Pursuit a similar situation exists, so when you think the game's answer is wrong, you might be right.

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
    9. Re:NIST - Public Domain by b4upoo · · Score: 1

      I think he should just go ahead and create the software. Just getting evaluations and considering all prevailing laws might be so expensive that it would ruin any hope of doing the work.
                      The idea that anyone can be legally safe in almost any profession is a thing of the past. My best notion is that a person simply take into account who would likely be offended or if it seems really likely that money could be made by a legal suit and then decide when to ignore all the nonsense.
                      In the US a lot of people are effectively, completely free of law suits threats even though they usually don't know it. For example would you spend a million bucks suing someone who would never have any way of coming up with enough money to pay for your lawyers?
                      Also individual states in the U.S. have different levels of protections. Florida is a great place to live if there are serious legal debts against you. You can own a mansion, a car, and receive your continuing funds in complete legal safety if you set it up correctly. What you can not do is own more than one home or land or boats. So the boats, land and other homes are generally put in the kids' names or another trusted party or even certain types of trust funds. The short story is that you can be a multi millionaire and never pay a penny of any law suit and be within the law.

    10. Re:NIST - Public Domain by morgan_greywolf · · Score: 1

      You must be .... This is slashdot, right? Oh, I get it.

    11. Re:NIST - Public Domain by Anonymous Coward · · Score: 0

      This begs the question of why NIST is charging $200 for the package.

    12. Re:NIST - Public Domain by lenehey · · Score: 1

      If the NIST program is the product of the work of US Government employees it is in the public domain.

      Not true. The Standard Reference Data Act provides an exception in the case of reference data to the general rule that the government cannot obtain a copyrights.

  4. IRTTALIYJ by Anonymous Coward · · Score: 3, Insightful

    I Recommend Talking To A Lawyer In Your Jurisdiction.

    HTH

    1. Re:IRTTALIYJ by Anonymous Coward · · Score: 0

      Surely one lawyer is no match for a myriad armchair law experts!

    2. Re:IRTTALIYJ by buchner.johannes · · Score: 1

      I on the other hand would start by reading the EULA/Terms of Service. Maybe twice.

      --
      NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
    3. Re:IRTTALIYJ by Minwee · · Score: 1

      And then talking to a lawyer so you can find out which part of "By clicking accept you irrevocably grant ownership of your DNA and all derivative works" is really enforceable, and what that means for the rest of it.

    4. Re:IRTTALIYJ by Anonymous Coward · · Score: 0

      EULA and Terms of Service usually claim the moon.

      That is, they make hugely exaggerated claims that might not stand up under the law. The point is to try to persuade people they have no rights, so they don't even try to sue.

  5. Wrote code in ForTran 77 for six years by Anonymous Coward · · Score: 4, Funny

    Let me tell you something: God speaks ForTran, and the guys who translated the bible from ForTran to Hebrew did a really really bad job.

    1. Re:Wrote code in ForTran 77 for six years by morgan_greywolf · · Score: 3, Funny

      Let me tell you something: God speaks ForTran, and the guys who translated the bible from ForTran to Hebrew did a really really bad job.

      Indeed. For example, here's the FORTRAN source code to Genesis.

    2. Re:Wrote code in ForTran 77 for six years by oldhack · · Score: 1

      Even worse, this King James guy used to work for Microsoft.

      --
      Fuck systemd. Fuck Redhat. Fuck Soylent, too. Wait, scratch the last one.
    3. Re:Wrote code in ForTran 77 for six years by Lawrence_Bird · · Score: 2, Insightful

      If this guy can't handle reading the FORTRAN code I seriously doubt he is capable of re-inventing it in a 'new' language. FORTRAN is not that hard to understand even "old" dialects.

  6. FAQ claims copyright by Mathinker · · Score: 2, Informative

    The FAQ claims that the US government has a copyright on the material. This could be possible if the material was not directly generated by the NIST itself --- for example, they paid a contractor to generate it and it is considered a "work for hire".

    The facts themselves probably can't be considered to be under copyright.

    OTOH, I agree with a previous poster that you should consult a lawyer if you want to actually do anything which isn't sheeple-ish with the data.

    1. Re:FAQ claims copyright by John+Hasler · · Score: 1

      > This could be possible if the material was not directly generated by the NIST itself ---
      > for example, they paid a contractor to generate it and it is considered a "work for hire".

      Which is why I wrote "if". Anyone who felt motivated could probably find out via FOIA requests (which also could get you unlicensed copies of the data).

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    2. Re:FAQ claims copyright by Alsee · · Score: 5, Informative

      The EU database law specifically does not protect foreign databases unless that foreign country also creates a database a law and establishes mutual protection. The US has no such protection, in fact it seems no country outside the EU has established reciprocal database protection. It should be possible to do this open source project based on data from the US or from anywhere outside the EU.

      The FAQ [nist.gov] claims that the US government has a copyright on the material.

      The factual data in that database cannot be protected by copyright, it is not protected as a database in the US, and is not covered under EU law. The only copyright they could claim on it is either if it contains creative images or creative text or the like, then those particular elements could be protected, or they could perhaps claim a copyright on the creative arrangement and formatting of the data in the database. Both of those issued can be avoided.

      What can be done is use this database and read out the needed factual data elements and then re-write it into the database for the open source project. Purely factual text-fields such as the name of an element or compound or whatever can be copied, just be careful not to copy any images or free-form text fields such as descriptive text or explanatory text. Then write the data out in your own arrangement. The best thing to do there is to arrange the data in some strict alphabetical or numerical order - there is no creativity and no copyrightability in that sort of unique ordering. That means not only storing the records in alphabetical order, but also order the data elements within each record in name-of-field alphabetical order. It might even be a good idea to rename any fields that care reasonably open to custom naming. There is no need to rename a field like "name" or "address" or "phone number", but a field like "work contact number" could easily be called "work phone".

      The best way to go about it would be to create a mostly-empty, but functioning, database before even looking at your intended source material, that way by definition there is no copying of the formatting of the database. Once there is a functioning database design then the factual data elements can be copied from the source to fill the already-designed database.

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    3. Re:FAQ claims copyright by Rockoon · · Score: 1

      This could be possible if the material was not directly generated by the NIST itself --- for example, they paid a contractor to generate it and it is considered a "work for hire".

      'They' in this case would be the American public. If the American public paid for a 'work for hire' then the American public owns it. Thats not to say that they necessarily have 'rights' to it.. but your arguement as it stands doesnt seem to qualify.

      --
      "His name was James Damore."
    4. Re:FAQ claims copyright by Throtex · · Score: 2, Insightful

      I wasn't expecting to find the correct answer to a legal question here on Slashdot, but, there it is. /thread. Too bad I don't have any mod points.

      One nit, though, just be careful with "renaming a field" as a solution ... that could still get you nailed as a derivative work. I do like the idea of building the framework from scratch, and only then populating it with the data.

    5. Re:FAQ claims copyright by jmcvetta · · Score: 1

      I wasn't expecting to find the correct answer to a legal question here on Slashdot, but, there it is.

      Wow, the copyright parasites must really be scraping bottom, if database field names count as "creative" work.

    6. Re:FAQ claims copyright by Repossessed · · Score: 1

      Its possible that the contractors retain copyright, or they licensed someone else's code (these tend to block open source releases), but the government itself can't have copyright under US law, regardless of who wrote it.

      --
      Liberte, Egalite, Fraternite (TM)
    7. Re:FAQ claims copyright by Anonymous Coward · · Score: 0

      Bzzzztttt!! Wrong. The government CAN own a copyright if said copyright has been transferred to it.

      US Code Title 17, Chapter 1, Section 105

      "Copyright protection under this title is not available for any work of the United States Government, but the United States Government is not precluded from receiving and holding copyrights transferred to it by assignment, bequest, or otherwise. "

    8. Re:FAQ claims copyright by Anonymous Coward · · Score: 3, Informative

      I am a federal worker and I oversee some contracts that involve writing Fortran codes for simulating nuclear reactors. That is not quite right. You need to consult the Federal Acquisition Regulation (FAR), Chapter 27. Specifically, see

      27.404-2 Limited rights data and restricted computer software.
      and
      27.404-3 Copyrighted works.

      http://www.acquisition.gov/far/current/html/Subpart%2027_4.html#wp1041836

      If you read those sections, and take the time to really understand the definitions they use, and read the appropriate appendices, etc, you will find that the legalese seems to indicate that the contractor IS allowed to copyright data generated in performance of the contract (with the government's permission), and that the goverment maintains an exclusive, irrevocable license to use such data for its purposes, but the government does not necessarily maintain an exclusive right to "redistribute" such data.

      It is my belief that the law is written this way so as to give potential contractors an incentive to do business with the government. If a company can't build a portfolio of intellectual property, then it has no means of distinguishing itself from the competition. In the long run, the government would not get the best value for its $.

    9. Re:FAQ claims copyright by Anonymous Coward · · Score: 0

      The best way to go about it would be to create a mostly-empty, but functioning, database before even looking at your intended source material,

      But he already admitted to the world that he looked at not only the database, but the program.

    10. Re:FAQ claims copyright by budgenator · · Score: 1

      United States Code; Title 17; Chapter 1; Â 105 Subject matter of copyright; United States Government works. Copyright protection under this title is not available for any work of the United States Government, but the United States Government is not precluded from receiving and holding copyrights transferred to it by assignment, bequest, or otherwise.US Code

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
    11. Re:FAQ claims copyright by Anonymous Coward · · Score: 0

      > The best way to go about it would be to create a mostly-empty, but functioning, database before even looking at your intended source material, that way by definition there is no copying of the formatting of the database.
      .
      too bad he already saw the database so the copying could be subconscious. copyright law is funtimes!

    12. Re:FAQ claims copyright by Anonymous Coward · · Score: 0

      One nit, though, just be careful with "renaming a field" as a solution ... that could still get you nailed as a derivative work.

      His argument is probably that the naming itself may be a creative act. Come up with your own names, and you've avoided that potential legal landmine. A verbatim copy would be worse than a derivative, except if someone claims the renaming was intended to disguise the source of the data. This again can be avoided by proper attribution, possibly even in the binary.

    13. Re:FAQ claims copyright by leuk_he · · Score: 1

      Under European law you might be correct and it might be possible to open source the database.

      However from a USA point of view, as soon al you sell the data in the USA they might sue you, claiming copyright and claim excessive statutory damages . Since there is not database law in USA it might fall under copyright there. Since neither me or you are USA copyright lawyer it is not safe to draw conclusions,

    14. Re:FAQ claims copyright by Alsee · · Score: 1

      Since neither me or you are USA copyright lawyer it is not safe to draw conclusions

      I am not a lawyer, however I do have a exceptional level of amature expertise in this subject. It is one of my fields of geek-interest and geek-expertise. I have read the entire Title 17 US Copyright law, and I have have read many US Supreme Court copyright rulings, I have read many lower court copyright rulings, and I have read many other sources on the subject, and I have spend a fair amount of time on the international aspects of copyright. One does not need to be a lawyer to understand the law. If one understands the law then one can draw pretty strong conclusions.

      Since there is not database law in USA it might fall under copyright there.

      The most relevant US Supreme Court ruling here is Feist Publications, Inc., v. Rural Telephone Service Co., 499 U.S. 340 (1991). Facts and information are *not* protected under US copyright law. Only creative expression can be protected by copyright, although the minimum threshold for a creative contribution is quite low. This is not only true under US law, but generally much the same internationally. The fact that the EU needed to pass a special law in order to extend protection to databases confirms that their own copyright law did not cover databases in this manner.

      The fundamental point is that the thermodynamic data we are talking about here is not protectable under copyright. Anyone wanting to claim copyright on it has to get creative. I spend most of my post addressing the available means to make such a claim. If the database contains something like free form descriptive text fields or graphical artwork, then those are protectable under copyright. If something (such as a database) has protected elements and unprotected elements, then the court has explicitly ruled that the unprotected elements can be extracted and freely copied. The next way to try to claim copyright on it s to claim some creative work in the selection, formatting, or arrangement of the contents. So again I explained how to extract the unprotectable data by stripping it out of the original arrangement and formatting. A unique ordering such as "alphabetical" has zero room for creativity, and it is explicitly excluded from protection under copyright.

      One thing I perhaps should have addressed is the selection of what data elements to include or exclude from the compilation. It is a bit of a stretch, but someone could try to claim creative judgment in which data to include or to exclude. Such a claim fails completely for a uniquely-complete list like a phone book, but this dataset is obviously incomplete. Trying to claim copyright here on that basis would be a real stretch, and particularly so as this database presumably has the non-creative goal of aiming towards completeness. The best way to deal with that is simply to find as much more data to add into your new database as you can.

      I'm not a lawyer, but I am analyzing it as a lawyer would. The basic point is that this sort of data is not protectable, and the analysis then turns to lawyerly-ways someone can try to work around that "problem" in order to claim copyright infringement. You do need to be careful to dodge any extra "hook" someone could use to claim copyright, but the final conclusion is that it can be done. Non-creative data cannot be protected by copyright, and it *can* be freely copied.

      The biggest complexity here is that the original question came from the EU. I have not spent much time on specifically EU law, but copyright is pretty tightly defined by international treaty. Most of copyright law works out the same in different countries, and I have a basic familiarity with where most such differences do crop up in international copyright. The most significant international issue here is the unique EU database directive. I checked, it explicitly excludes coverage for foreign databases unless that foreign country arrang

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    15. Re:FAQ claims copyright by lenehey · · Score: 1

      I posted this elsewhere, but in case you missed it:

      The Standard Data Reference Act provides an exception in the case of reference data to the general rule that the U.S. government cannot obtain a copyright.

  7. c by Anonymous Coward · · Score: 0

    I don't now about thermo, but I have the copyright to the speed of light...and I'm watching you.

  8. Ask NIST by Anonymous Coward · · Score: 0

    Ask NIST how they'd feel about you reimplementing the whole thing in XML and C++ or Python or whatever and making that open source. Tell them they won't even have to pay you for it. One or two of the TPOCs at NIST may die of shock, but there's a very good chance they'll give you permission to do it.

  9. Where did commercial solutions get data from? by Gnavpot · · Score: 2, Insightful

    I would assume that it would be difficult to sell a commercial solution for scientific purposes unless it is based on already documented and accepted data. Basing your scientific work on calculations made by a commercial solution with homegrown data would make it difficult to openly document your method to other scientists. So why not find the published version of those data instead of lifting them out of software?

    But what do I know? I am an engineer, not a scientist.

    In my work I do a lot of calculations of water and steam properties, and the available software I know of is strictly using the calculation methods published by IAPWS. So if I wanted to, I could buy the IAPWS documentation and make my own software.

  10. It Probably Wouldn't Be Legal by SwashbucklingCowboy · · Score: 4, Informative

    A database is copyrightable. See http://www.bitlaw.com/copyright/database.html

    1. Re:It Probably Wouldn't Be Legal by Anonymous Coward · · Score: 0

      But the data therein is not under copyright protection. One could pull the relevant information out of the commercial database into a new database since "In regard to collections of facts, O'Connor states that copyright can only apply to the creative aspects of collection: the creative choice of what data to include or exclude, the order and style in which the information is presented, etc., but not on the information itself. If Feist were to take the directory and rearrange them it would destroy the copyright owned in the data." Now if the commercial database owners would like to argue in court that their database is "creative", that is up to them.

      Or even from your link: "No Separate Protection for Underlying Data: Although databases may be protected as compilations under U.S. copyright law, the underlying data is not automatically granted protection. The Copyright Act specifically states that the copyright in a compilation extends only to the compilation itself, and not to the underlying materials or data. 17 U.S.C. 103(b). As a result, compilation copyrights cannot be used to extend copyright protection to ideas or facts that are otherwise unprotectable (it is a basic premise of copyright law that there is no copyright protection for ideas and basic facts, as is explained in the BitLaw section on unprotected works).

      Thus, a database of unprotectable works (such as basic facts) is protected only as a compilation. Since the underlying data is not protected, U.S. copyright law does not prevent the extraction of unprotected data from an otherwise protectable database. In the example of a database of presidential quotations, it would therefore not be a violation of copyright law to extract (copy) a quotation from George Washington from the database. On the other hand, it would be violation to copy the entire database, as long as the database met the Feist originality and creativity requirements."

      See also SCOTUS phone book ruling ( http://en.wikipedia.org/wiki/Feist_Publications_v._Rural_Telephone_Service ).

    2. Re:It Probably Wouldn't Be Legal by Anonymous Coward · · Score: 0

      A database is copyrightable. See http://www.bitlaw.com/copyright/database.html

      ... but FACTS are not copyrightable.

    3. Re:It Probably Wouldn't Be Legal by cpt+kangarooski · · Score: 1

      Or, if the database is itself non-creative in terms of its selection and arrangement of uncopyrightable information, the database would be uncopyrightable as well. This is the problem that telephone white pages ran into in Feist; they contained all the listed numbers (where the phone company doesn't decide which numbers are and are not listed), in alphabetical order by the last name or name of business associated with the number. That selection and arrangement was non-creative. OTOH, a directory of your favorite places to eat would likely be creative in selection, at least. Arrangements are tougher; there are really only so many in common use.

      Generally, any all-encompassing selection is apt to be non-creative (picking and choosing may be creative, but blanket inclusion never is), and many arrangements are non-creative too. This tends to hit databases rather hard.

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    4. Re:It Probably Wouldn't Be Legal by Wdi · · Score: 4, Interesting

      I do not know about this exact database, but many scientific databases are hand-curated and extensively reviewed. Many do not include every measurement published in the literature, but carefully and judiciously select those data points deemed, by expert opinion, most reliable. Thermodynamic databases do not contains "facts" per se, but measured data points which may or may not be close to the facts. The editing and review process, which is quite an investment, does often create a solid foundation for copyright. These databases are not just a routine business, like a reformatted dump of the data from a telephone company.

    5. Re:It Probably Wouldn't Be Legal by Dipster · · Score: 1
      Databases are indeed copyrightable, but the U.S. requires an element of creativity to do so as decided in the case of Feist Publications, Inc. v. Rural Telephone Service Company, Inc.

      From the parent's link:

      According to the Supreme Court, a compilation is not copyrightable per se, but is copyrightable only if its facts have been "selected, coordinated, or arranged in such a way that the resulting work as a whole constitutes an original work of authorship," citing the definition of a compilation in 17 U.S.C. 101.

      This holding overruled numerous lower courts that adopted a "sweat of the brow" or "industrious collection" test of copyrightability. Under this test, if a compilation was created as a result of a great deal of effort (such as the collection of thousands of names and addresses), copyright protection would extend to the compilation regardless of the creativity or originality in the selection, coordination, or arrangement of the facts.

      The Supreme Court expressly stated that this "sweat of the brow" analysis was faulty, and that copyright extended only to the original selection, coordination, and arranging of data, and not to any unprotected facts contained within the compilation.

    6. Re:It Probably Wouldn't Be Legal by Stormx2 · · Score: 1

      But the data in it isn't, if it's something like themodynamic properties.

      See: http://en.wikipedia.org/wiki/Merger_doctrine_(copyright_law)

    7. Re:It Probably Wouldn't Be Legal by Anonymous Coward · · Score: 0

      but is your name bob, or is it robert.
      there's always a choice.

    8. Re:It Probably Wouldn't Be Legal by pearl298 · · Score: 2, Informative

      A database is copyrightable, but the applicable case law from when I practised (YEARS AGO!) was the phone directory - it was held to be sufficient that the copier rearranged and reorganised the information to provide a "mere spark of creativity".

    9. Re:It Probably Wouldn't Be Legal by Anonymous Coward · · Score: 0

      Tricky realm in copyright law, really.

      Specific heat, mass, and physical properties of the compound are not copyrightable, like addresses and phone numbers are not copyrightable.

      But if the selection of elements on the card in the database are "creative" and not fully constrained by function (useful articles doctrine in copyright), then it may be copyrightable.

      What's likely is that their arrangement of the card is copyrightable: the selection of and order of properties.

      Not copying the copyrightable elements is a complete defense. My suggestion would be to come up with your own "card" and write a program to "strip" out the physical properties, then put them on your own independently created card.

    10. Re:It Probably Wouldn't Be Legal by cpt+kangarooski · · Score: 1

      I do not know about this exact database, but many scientific databases are hand-curated and extensively reviewed. Many do not include every measurement published in the literature, but carefully and judiciously select those data points deemed, by expert opinion, most reliable.

      That's tricky. On the one hand, the selection isn't obviously non-creative, but on the other, it is for the facts which are most factual, rather than an arbitrary creative standard, e.g. the best thermodynamic properties to read about at the beach. I would not want to bet on which way a court would go on copyrightability. Still, do remember that effort expended is not relevant for the analysis; only creativity is relevant. Otherwise, the phone book, which does take a lot of effort to compile, but which lacks creativity, would be copyrightable.

      Thermodynamic databases do not contains "facts" per se, but measured data points which may or may not be close to the facts.

      That's close enough for this purpose. No one is demanding a platonic ideal here. If the scientists who determine them are reporting on something they've found, rather than making up numbers out of thin air, it's going to be treated as factual.

      The editing and review process, which is quite an investment, does often create a solid foundation for copyright.

      Again, the investment of money or effort is irrelevant, at least under US copyright law. Editing and review (whether cheap and easy, or expensive and difficult) is what counts. But even then, in this case, it seems tricky since creativity and hard scientific data don't always go well together.

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    11. Re:It Probably Wouldn't Be Legal by eapache · · Score: 1

      Link for the Feist case referred to by parent:

      http://www.bitlaw.com/copyright/database.html#Feist

    12. Re:It Probably Wouldn't Be Legal by MaskedSlacker · · Score: 1

      the best thermodynamic properties to read about at the beach.

      I'd say the rate of heat transfer from sand to human skin.

    13. Re:It Probably Wouldn't Be Legal by sjames · · Score: 1

      One way around that would be to merge the data from multiple databases, effectively undoing the curator's "creative input"

  11. Re:Dead nigger storage by Anonymous Coward · · Score: 0

    Haha! That's pul fiction loesr

  12. Thermodynamics by BruceSchaller · · Score: 1

    I think that the biggest problem isn't intellectual property, but the people who administer it. I don't think that the demand is particularly great. As such, there isn't a great incentive to release it freely. There are costs to administering such a large DB. Furthermore, nobody wants their name on a database of all the fundamental properties because in that data there are bound to be mistakes. Caveat Emptor! Also, while mixtures of hydrocarbons are common because of oil refining business, many solutions don't have property listings because they are simply unknown. I am working on a project which involves CO2 and seawater... seawater has many components which vary depending on your location on the planet. So while there is data, the validity of it may be in question, it depends on where the data was collected. It's a bit of a nightmare.

    1. Re:Thermodynamics by vlm · · Score: 2, Interesting

      I think that the biggest problem isn't intellectual property, but the people who administer it. I don't think that the demand is particularly great. As such, there isn't a great incentive to release it freely. There are costs to administering such a large DB. Furthermore, nobody wants their name on a database of all the fundamental properties because in that data there are bound to be mistakes.

      You are looking at the liability issue for the creator/admin, the supply side. The bigger liability problem is on the engineer, demand side.

      Something that is missing from this discussion, is some Chemical Engineer specific knowledge that I can attempt to provide. The whole point of a "steam table" and similar products like discussed here, is there is no accurate formula for vapor pressure at various temps. The simplistic linear equations taught in high school don't work at the extremes, or don't give accurate enough results to design a safe and profitable plant. So, more than a century ago, physicist / chemist / engineers started making lab measurements, and selling graphs and tables of data. The modern version of that product is the expensive computer models discussed in the article, which optimistically try to answer any input conditions with correct and continuous answers based on a mixture of theory, optimism, and some distinct individual laboratory measurements.

      Because the data model is used to design multi-million dollar plants, and because the only way to verify the results is very expensive lab work, and is therefore often glossed over, a mistake in the data model could be a multi-million dollar mistake, assuming the losses are purely economic and no human victims. The creator/admin probably was intelligent enough to release under a license that removes all liability for data errors. The end user engineer will not be so lucky.

      On one far extreme of the provability / testability spectrum, you've got yet another word processor, where if the screen doesn't match what you typed in, literally a trained gorilla could figure out the word processor is broken, and act accordingly (throw poo at programmer? The more things change, the more they stay the same) Or maybe a crypto hash where a hundred programmers can write it in a hundred languages and all the outputs better match for a given input.

      At the other extreme of provability / testability, you've got a Chem-E basically having to take the program output on faith that it's correct. The program says the pressure of supercritical steam at 700 K is 230 atm, I know that is somewhat above critical temp and above critical pressure, so the best I can do is "sounds about right to me"? So specify plant components based on a 230 atm environment (adding appropriate safety factors, etc) Now steam pressure is old stuff, boring, and everyone knows about what to expect, but using really weird stuff under really weird conditions, who knows what crazy output from the data model might slip past, resulting in a disaster?

      Despite the dangers, it would be great for education, and cheap experimental research/simulation, even if it would be too legally dangerous to use in formal design work.

      --
      "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
  13. Unreadable? by dcw3 · · Score: 1

    "no one can read Fortran anyway"...you must be new here. It certainly wasn't designed to the standards young engineers expect today, but given the limitations of processors back in the 60's to early 80's, it served its purpose. I did my first college CS class in Fortran back in '83. Anyone can write illegible code, but with a little effort, one could write fairly readable Fortran.

    --
    Just another day in Paradise
    1. Re:Unreadable? by budgenator · · Score: 1

      Most languages are pretty easy to read, I'm assuming the problem is not knowing the gazillion supporting libraries inside out that's causing his problem.

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
  14. Pirate it by Anonymous Coward · · Score: 1, Insightful

    The law needs a major update anyway.

  15. It will be a very difficult project by Anonymous Coward · · Score: 5, Interesting

    I can't find my copy of Supertrapp at the moment, but as I recall there is some strange wording in the license. It's definitely NOT public domain as asserted by the uninformed.

    It's also not tabulated data. It's a collection of equations and empirical constants embedded in what may be the worst code I've ever seen.

    It may be easier to track down the original papers and work from those, though that too is difficult as lots of the original work was published in obscure journals.

    FWIW I am very comfortable w/ FORTRAN and prefer it for serious numerical work (default choice is C). I'm also quite skilled at interfacing FORTRAN to other languages.

    I'm interested in working on such a project and have quite a bit of experience w/ the problem, though only limited experience w/ Supertrapp because it is so bad I tended to avoid using it unless I absolutely had to. Please send me an email so we can discuss more. rhb acm.org

    Reg Beardsley

    1. Re:It will be a very difficult project by GPSguy · · Score: 3, Informative

      I tend to work in the atmospheric sciences, where, as one might guess we work with microphysical processes and thermodynamic data. I would second the recommendation that working from the original, authoritative publications would be a good approach. If you're well-versed in the field already, you're familiar with the seminal works. If you're not, your job is bigger than you realize, as programming for a scientific project is rarely just finding equations and re-coding them, or finding a database of physical constants and calling them. You've got to understand where in the domain in question they come into play and use appropriate equations and parameterizations.

      Fortran, even Fortran-66, is rarely unreadable. However, it often is written like a short story in a local dialect. The author has a method and style, and you have to understand it, or at least become conversant with it, before reading and understanding the flow of the code occurs. I should point out that this is really not different from any other language. Fortran, however, has been maligned because its roots were not in object-basis. Fortran 90 and Fortran 95 both, however, comply with the OO paradigm. The inherent problem is, CS departments often don't teach Fortran, and their faculty will tell you how horrid it is. Why? Because their discipline is COMPUTER science, not, say, solid earth geophysics, and they're conversant with a number of languages.and feel they can pick the best one for the job. The geophysicist, on the other hand, spent his time learning how and why those pesky tectonic plates move around, something the computer scientist never really studied unless, maybe, he took a rocks-for-jocks class and got really interested. Rather than mastering C, C++, Java and C#, the geophysicist learned just enough Fortran to get his work done, and proceeded down a different path. Since Fortran ("FORmula TRANslation") was developed to help discipline scientists transform their equations to operable code, this really makes sense.

      My first computer initiation was using Fortran (Fortran-II) on an IBM 1401 while I was still in junior high school. My first formal course in programming used SWIFT, BASIC and SNOBOL, over the course of a summer while in high school. Virtually every course in college I took (I was not a CS major, but could/should have been from my transcript) was in Fortran (plus a pair of assembly language courses) because the choices were Fortran, Cobol or assembly. Imagine, if you will, not having a "modern language around, and having to code decent I/O or even decent APIs with that choice.

      --
      Never ascribe to malice that which can adequately be explained by tenure.
    2. Re:It will be a very difficult project by orzetto · · Score: 1

      [Supertrapp] may be the worst code I've ever seen.

      Ok, so maybe my judgement of Fortran was a bit too harsh, Supertrapp was the only larger project in Fortran I have ever looked into... until my eyes started bleeding, that is.

      --
      Victims of 9/11: <3000. Traffic in the US: >30,000/y
    3. Re:It will be a very difficult project by orkybash · · Score: 1

      Fortran 90 and Fortran 95 both, however, comply with the OO paradigm.

      If only you were right, my life for the past two years would have been much easier. Give me inheritence, dynamic binding, and private members of derived types ("structs" or "classes" for everyone who doesn't speek fortran). THEN maybe I'll agree that these standards comply with the OO paradigm. 2003 certainly does, but point me to a single complier that fully implements it...

    4. Re:It will be a very difficult project by Noose+For+A+Neck · · Score: 1

      All of those can be accomplished in Fortran 90/95. There is even direct language support for the third requirement (private members of derived types), and I do it all the time; it works just like other public/private declarations, just placed inside the type definition. Inheritance and polymorphism (I'm guessing this is what dynamic binding means from a quick look at Wikipedia) are a bit trickier, but the techniques have been worked out and documented by these fellows (Viktor Decyk's page is also quite helpful). If you prefer to avoid typing out a certain necessary amount of boilerplate to do this, you could use Drew McCormack's forpedo preprocessor (described in detail on MacResearch). So, it's not necessary to wait for 2003, and in fact, many people haven't but have managed to write and maintain very large codes in Fortran 90/95. Good luck!

      --

      Software piracy is victimless theft.

    5. Re:It will be a very difficult project by Hurricane78 · · Score: 1

      Who cares what the license says, if the license goes against the law itself?
      I read in another comment, that it's from the NIST project, tax funded, and by definition public domain.
      I don't know how often I see things, that are completely free, but where someone slapped a copyright on it, and acts as if you have to have a license to do anything with it.
      People are that stupid, and that arrogant. People also often do not know laws, even when they write licenses for a living.

      I'd check that fact with NIST, it being tax funded, and that everything the government does belongs to the people by definition, and then go with it.

      People, stop buying into the delusional realities of other (loud but wrong) people. :)

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    6. Re:It will be a very difficult project by pmarini · · Score: 1

      maybe your eyes bled because of the green/amber screen you were looking at...

      --
      Can I put a spell on those who can't spell?
      Your wheels are loose and they're losing their grip, good you're there.
    7. Re:It will be a very difficult project by Roger+W+Moore · · Score: 1

      FWIW I am very comfortable w/ FORTRAN and prefer it for serious numerical work

      You might want to re-evaluate that position. Modern CPUs benefit enormously from 'hints' embedded in the machine code generated by compilers. My experience has been that this can have a significant impact on performance given the right circumstances - in fact I've even seen that compiling C with a C++ compiler can give significant performance increases simply because the C++ compiler was more mainstream and so better maintained and optimized. I cannot help but think that a Fortran compiler is so far off the mainstream that the performance of its code will be significantly worse than a C++ compiler.

      Of course there are lots of things you can do in C++ that will slow down your code so you have to be careful but given a level comparison of C++ vs. Fortran I would expect the C++ code to be no slower and potentially faster.

    8. Re:It will be a very difficult project by MaskedSlacker · · Score: 1

      I cannot help but think that a Fortran compiler is so far off the mainstream that the performance of its code will be significantly worse than a C++ compiler.

      Modern fortran compilers are generally maintained by the processor makers themselves. The big advantage over C (and C++ AAAAGH! I once made the mistake of writing a PDE solver in C++ in high school...never again) is that those fortran compilers are optimised for iterated operations over every value of an array (for say, when each array value is the value of a variable at a given spatial coordinate). This makes Fortran much better for at least some (most of the one's I've had to work on) calculations.

    9. Re:It will be a very difficult project by cdrguru · · Score: 1

      What law are you referring to? Sounds like the EU Database Directive pretty much means that NIST has a copyright on the program code and database in Germany.

      Almost nothing from NIST is free. Often what they are selling is virtually unobtainable from any other reputable source. They also charge what it costs them to produce, not as a profit center.

      What possible rights a German citizen (not a US taxpayer) might have over NIST products I wouldn't be able to say. But I suspect anyone just taking this and giving it away for free would find out that they are on the wrong side of both German and US law.

      You want to be a pirate? Find somewhere else to do it.

    10. Re:It will be a very difficult project by Winter+Lightning · · Score: 1

      You might want to re-evaluate that position. Modern CPUs benefit enormously from 'hints' embedded in the machine code generated by compilers. My experience has been that this can have a significant impact on performance given the right circumstances - in fact I've even seen that compiling C with a C++ compiler can give significant performance increases simply because the C++ compiler was more mainstream and so better maintained and optimized. I cannot help but think that a Fortran compiler is so far off the mainstream that the performance of its code will be significantly worse than a C++ compiler.

       

      This is quite wrong; modern FORTRAN compilers perform as well and often better than C++. Standards for parallelism, e.g., using multi-core processors, are often implemented first in FORTRAN.

      Of course, you can make any language perform slowly, but in languages such as C++ where there are often hidden system calls (e.g., malloc), it's easier to make such mistakes.

    11. Re:It will be a very difficult project by bwcbwc · · Score: 2, Interesting

      Items created/published by the U.S. government are in the public domain at least in the U.S. I'm not sure if the rights are granted abroad as well.

      However, items created under a contract to the U.S. government may or may not be in the public domain. There's a section of US law that companies have to invoke in their contract or the software license regarding U.S. government "limited rights" to keep their code or other work private. On the other hand, NIST DATA shouldn't be copyrightable in any case, although companies still like to test the theory that their databases are copyrighted fairly frequently.

      I am not a lawyer. Even if I were a lawyer, I'm not YOUR lawyer. The above discussion is mostly intended to point out that you're more likely to get a better deal for data out of the government than out of a private company. If you need pre-built software from a private firm, you're likely to be tied into a license agreement that affirms copyright over the data or its storage format (or both), which could be a source of disagreement with the software vendor if you decide to follow your plan of extracting the data for your own use.

      --
      We are the 198 proof..
    12. Re:It will be a very difficult project by Roger+W+Moore · · Score: 1

      This is quite wrong; modern FORTRAN compilers perform as well and often better than C++.

      That has not been my experience, so perhaps you are quite wrong. It is true that C++ is "dangerous" in that if you have no clue what you are doing it is easy to introduce dynamic memory allocation or indirect function calls. However, when I last compared the assembly generated with a Fortran compiler vs. that for a C++ compiler the Fortran code lacked some hints for conditionals and loops and was not as well optimized (compiled with optimization turned on) as a result the code executed 10-20% slower.

      I realize that the usual argument for Fortran is the it is supposedly faster than other languages but with modern CPUs and carefully written C++ that does not appear to be the case.

    13. Re:It will be a very difficult project by Anonymous Coward · · Score: 0

      Don't know if this helps anyone ... but I don't think I've seen anyone mention the Cantera project. Free, open-source ... it's mostly for chemical kinetics but has modules for thermodynamic properties. Worth a look - lots of people use it in the combustion simulation community ...

    14. Re:It will be a very difficult project by Shinobi · · Score: 1

      Then you must have intentionally crippled the Fortran code somehow. Modern Fortran compilers are just as advanced as C++. Just look at Intel's compilers, or the (now defunct) Pathscale compilers. Or compare XLC and XLF on PowerPC. The Fortran compilers blow the C and C++ ones out of the run. All the supercomputing facilities I've worked with here in Sweden recommend Fortran primarily, and C/C++ as fallbacks. (In severe cases, C/C++ and other software might even be ported to Fortran by personnel at the facilities, so execution times are kept down and don't disrupt other applicants and/or customers)

    15. Re:It will be a very difficult project by Winter+Lightning · · Score: 1

      ... when I last compared the assembly generated with a Fortran compiler vs. that for a C++ compiler the Fortran code lacked some hints for conditionals and loops and was not as well optimized (compiled with optimization turned on) as a result the code executed 10-20% slower.

      Which compiler/version was this? Did you request that the vendor fix this?

      My experience has been based on compilers such as Intel and Sun, but I understand others perform as well. Compiler vendors don't generally neglect FORTRAN, particularly since there is often a common back end for code generation and CPU-specific optimisation.

  16. Fortran not readable? by Anonymous Coward · · Score: 0

    Granted, I graduated EE school in 1987, but every student was required to learn Fortran 77. Not sure how long that remained a requirement but I can honestly say Fortran was one of the easiest languages to learn. Saying it's not readable is laughable.

    1. Re:Fortran not readable? by orzetto · · Score: 1

      Supertrapp uses pre-Fortran 90 syntax, meaning identifiers have 6 letter at maximum. This makes it sure that complex code will never be readable, because you can only use acronyms that are way too short to be clear. Point taken, however, that this is a fault of the implementation rather than the language's.

      --
      Victims of 9/11: <3000. Traffic in the US: >30,000/y
  17. A mere youngster... by RotateLeftByte · · Score: 1

    I worked on my first Fortran Prog in 1971 on a Honeywell DDP-124.
    It was for controlling a Boeing 727 Flight Simulator.

    I can still read fortran as can many people here. I'd bet many could read Cobol and Algol if pushed. Coral-66 baffles a lot of people though.

    --
    I'd rather be riding my '63 Triumph T120.
    1. Re:A mere youngster... by Anonymous Coward · · Score: 0

      1966 - using Fortran for audio filter design whilst at BBC - following year Atals Autocode (now thats a real language!) for RF filter work using printed circuit inductors.

  18. Free Software vs. Genuiness of Data by modrzej · · Score: 4, Informative

    People using this NIST data do it because it has NIST sign on it, so they don't risk being dependent on tabulated values from not exhaustively verified source. If you're rewritting the source code, you should take care to establish means by which users could check that data are unaltered with respect to what NIST servers contain. If you work for renowned institute, that should be easy, just store the database on your server and sync it with NIST, along with sources of data cited at NIST website.

    As it comes to Fortran programming, it's optimal language for scientific computing. Modern dialects have some of the power of C (allocatable arrays, long subourtine names, free format code, modules, interoperability with C), but, what is preferable in scientific computing, programmer isn't encouraged to tinker with machine-specific stuff. Many existing codes are written in Fortran, e.g. powerful LAPACK library and many computational chemistry packages, so for many physicists/chemists/engineers Fortran is the only language they know and care of. Moreover, Fortran in recent years has gained parallel-programming functionality thanks to OpenMP (it's provided with features eqivalent to that in C/Cpp).

    1. Re:Free Software vs. Genuiness of Data by GameGod0 · · Score: 1

      Many existing codes

      Spoken like a true physicist...

      P.S. C doesn't encourage you to tinker with machine-specific stuff either.

  19. Which database? by sugarmotor · · Score: 1

    It looks like they are selling some database

        http://www.nist.gov/srd/dblist.htm

    And providing others for free,

        http://srdata.nist.gov/gateway/gateway?dblist=0

    Which one are you after? Something like this?

        http://www.metallurgy.nist.gov/phase/solder/solder.tdb

    I imagine if you derive approximation formulas to the figures, and publish them packaged as software you
    would be able to license it whichever way you liked - sounds "transformative" to me. Might even qualify as proper research.
    Would that work?

    I don't think "it's only measurements" is enough to say they have no copyright. On the other hand, if the same
    numbers appear in different places / articles then if you establish that "these are the numbers", and you make your
    database in a different format, it would be a different story.

    Stephan

    --
    http://stephan.sugarmotor.org
  20. Misleading title, wrong question by Anonymous Coward · · Score: 0

    It doesn't matter what the data describes, it matters who compiled the database. Read the EULA, or talk to your lawyers and possibly the lawyers of the people who sell the database. Asking for legal advice here is... not smart.

      Also, why are you tossing in ``XML''? It isn't the best possible format for all things (for one because it isn't a format; merely a method to make your storage extremely verbose--the higher level structure is in the DTD, which is amazingly enough often missing for haphazardly thrown together``databases'') and from your description it isn't clear it is the best format for your application. As used here it's clearly a case of buzzworderitis. Something for you to think about.

  21. You're making things harder for yourself by stevel · · Score: 1

    I think you need to get over your dislike of Fortran and make use of the many good and modern Fortran compilers available to you, both freeware and commercial. Any of them has got to be a better solution than f2c - if you think Fortran is hard to read, that's nothing compared to the cryptic output of f2c, and then you're locked in to using the buggy and archaic f2c support library.

    I am not familiar with the application you're using, but the limits you describe are almost certainly not due to the coding language chosen. As for programming interface, it's easy to call Fortran from other languages and, in most cases, to call other languages from Fortran.

    One can write unreadable and unmaintainable code in any language. A big benefit of Fortran is that old code is still supported by modern Fortran compilers.

    1. Re:You're making things harder for yourself by Anonymous Coward · · Score: 0

      Why reimplement something that is already working and has a long history of use and testing? In estimating the effort, include the testing required. Is this a good use of your time?

      Supertrapp is written in ANSI standard FORTRAN 77. Fortran 90 / 95 / 2003 are much improved languages. Open source compilers are available, e.g., gfortran of the gcc collection. A Fortran 90 / 95 / 2003 compiler will compile standard FORTRAN 77 and provide the benefits of modern Fortran for newer code. One new feature is a standard interface to call C from Fortran, or Fortran from C (the ISO C Binding).

      If you really want to port the code to a modern language, there are commercial software for cleaning up FORTRAN source code and translating to Fortran 95, such as PlusFORT and VAST/77to90 -- if the source code license allows.

  22. buy a copy of such a database by nurb432 · · Score: 1

    Sounds proprietary to me.

    --
    ---- Booth was a patriot ----
  23. Mod parent up by Anonymous Coward · · Score: 0

    It is a well thought out, fact-based response.
    In the USA, facts are not copyrightable, this includes the facts in a database. Only expressive, original content is copyrightable, not the facts on which the expressions are based. Also, there is no originality in the practical ordering of a database, unless it can somehow be seen as rising above obviousness and can be considered creative.

  24. Crowdsourcing? by Alsee · · Score: 1

    Maybe you could crowdsource for the data points?

    Write your open source software to work with the data, and set up a website or something where people can contribute data points? There would obviously by no guarantee on any particular data contributed, but you could have some provision to flag data as wrong or dubious and store multiple conflicting values until you sort out the conflict somehow?

    -

    --
    - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
  25. Just put a wrapper around it by Will.Woodhull · · Score: 1

    You are not the first to encounter this kind of problem. The traditional answer is to not mess with the Fortran, but to put a wrapper around it in the language of your choice and leave the Fortran internals alone.

    From your description of the limitations of the Fortran code, I get the strong sense that this would be the best approach for you to take. It can be very difficult to tease out the reasoning behind some of those archaic Fortran constructions: they tended to be blends of methods to deal with hardware limitations that we don't have any more and also methods of dealing with computational limitations that are STILL present. E.g, when code was written to optimize buffering for a slow read-the-tape operation, it can be too easy to fail to see that it was also written to handle some kinkiness in the underlying differential expressions, or to exploit an edge case, or assure that some follow-on operation in another module would receive enough significant digits that its results would be better than garbage.

    Just treat the Fortran library as a black box object and wrap the interface you want around it. You will find it easier to do, much easier to debug, and vastly easier to convince your colleagues that what you've done can be relied upon. You will also develop skills in wrapping old code for new purposes that could become an important part of your career.

    --
    Will
  26. How i do it by bucuo · · Score: 1

    I'm a chemical engineer, and part of my job is to put together physical property packages for our simulator. I have no idea if you can legally do this by adapting something from another database, but I would contribute some of the information I have if you can get through the legal stuff.

    Mainly, I rely on NIST's JANAF publication for thermodynamic data (inorganics only), the DIPPR database, and the Yaw's Physical Property Handbook. For binary VLE data DECHEMA is the best references Of these, JANAF is freely available (in horrible PDF format) while the other two would require some sort of membership or purchase. These are mainly in the form of equations or data tables. From there, we simply bring it into excel or sometimes some curve refitting routines and then on to the simulator, which takes the equations directly. We're members of AIChE which gives us access to the online version of these databases.

    DIPPR was the result of a major effort of a consortium of companies who needed this data. I believe most of the serious big petrochemical companies are members of DIPPR. You will be trying to recreate this work, which is doable, but I think it will be harder than you think. I agree that this data shouldn't be locked away as tightly as it is.

  27. Mod Parent Up by Anonymous Coward · · Score: 0

    Interesting, something to think about.

  28. Don't take anyone's advice here unless... by LunarStudio · · Score: 2, Insightful

    ...they specialize in international copyright law. While a US Citizen may be able to "copy" or "rewrite" code US taxpayers paid for, don't assume other, non-contributing (non tax-paying to the US) foreigners can openly copy and redistribute code that is technically the property of US citizens. Personally, I don't care as your topic is of little interest to me, but unless someone is attorney/lawyer in these copyrights, I wouldn't listen to anyone here.

  29. duh by wasabii · · Score: 1

    As a lawyer. Duh. The lawyer will probably tell you that copyright applies.

  30. Definitely copyrightable by j.+andrew+rogers · · Score: 2, Interesting

    Empirical models of thermodynamic properties are definitely protected by copyright. There is a high-value market for these models, and different models of the same thermodynamic process will evaluate differently so it is a valuable creative product rather than a mere description of reality. For fields where tiny improvements in efficiency generate big cost savings, you want to use the most accurate model available where "most accurate" will be a function of the use case.

    Thermodynamic property models are not measurements of reality, they are mathematical models of a physical process derived from empirical data. They are what you use to predict reality when it is not possible or practical to measure it. Turning the empirical data points into continuous functions is a creative step and the value of the creative step is in minimizing the divergence between the model and reality over as broad a range as possible. There are companies that specialize in producing and selling ultra-accurate thermodynamic property models.

    1. Re:Definitely copyrightable by Anonymous Coward · · Score: 0

      P = rho R T is a thermodynamic model of a real gas using thermodynamic constant R. By your logic if this was invented today it would be copyrightable. If it is true or not, that such an equation could be subject to copyright, is only an anchor to the progress of scientific discovery.

    2. Re:Definitely copyrightable by Anonymous Coward · · Score: 0

      Thanks, was going to post pretty much exactly this, only in a more condensed form. The data are not "exact," they are the result of calculation and are highly idiosyncratic to that particular calculation method. In other words, the data are most definitely a creative work.

    3. Re:Definitely copyrightable by Anonymous Coward · · Score: 0

      While in (legal) practice this may be true, I'd like to point out that Newtons laws are only "fact" because they work to a certain number of decimal places. At a certain level both quantum mechanics and relativity demonstrate that Newton's laws are not the whole story. More to the point, they are a convenient method that we came up with for predicting certain things. They aren't exactly right, but unless you are very small or very large they are true to more decimal places than we normally can measure. So what is the fundamental difference between these copyrightable empirical models and Newton's laws? Or do you think that Newton's laws should be subject to copyright?

    4. Re:Definitely copyrightable by chthonicdaemon · · Score: 1

      Ya know, for a guy who worked in a Patent office, Albert really missed out on stunning opportunity on royalties on general relativity. I'm pretty sure most countries have exemptions on copyright and patents for mathematical formulae. Mine (South Africa) sure does, and so does America

      --
      Languages aren't inherently fast -- implementations are efficient
  31. Properties of nature copyrightable? by Anonymous Coward · · Score: 0

    As a chemical engineering student in college I had trouble finding thermodynamic data for my senior project (vinyl chloride production through oxychlorination of ethane) due to the tight lids on the research. I understand the reason for this though because it takes a lot of money to figure this data out.

    However, thermodynamic properties are those of nature. It would be like NASA obtaining a copyright for a map of the stars. If it is legal it shouldn't be.

  32. It's the fundamental sources you want by rlseaman · · Score: 1

    NIST presumably charges on a cost recovery basis. They keep the data updated (latest version appears to be v3.2 as of 2007) and have to pay for the due diligence of keeping up with the scientific literature. Presumably either the DB (STPLIB2) or the documentation or separate publications describes how the data are accumulated and vetted. The software appears to permit the values to be updated by users (undoubtedly also familiar with the appropriate journals and research) in between releases.

    You could consult the same papers and accumulate the same data. (And don't forget the subtle physical algorithms and numerical techniques embedded in the code.) This would not be a trivial exercise. More to the point, NIST exists precisely to serve as a reliable source of such information. Few other organizations have the resources to gain such trust. Should your customer trust you as much as NIST?

    There is a frequent disconnect in scientific programming between the science and computing requirements. Many of the comments here focus on the niceties of programming, but neglect the underlying scientific reasoning. It isn't enough to get an answer - or even the answer - one must also construct a chain of deduction from the peer reviewed scientific literature to the resulting decision-making (for whatever purpose).

    As far as choice of programming language, mature programmers appreciate the characteristics of each language like the bouquet of fine wines. Some languages are indeed "corked", but FORTRAN is not one of them. Think of a fine old brooding cabernet. C is a cheerful chianti, suitable for most situations - ideal (by design) for none.

    The technical issues here have nothing to do with programming, per se, but rather system architecture. Clearly what is needed amounts to a small multi-platform relational database - mySQL or what have you - along with a portable library with multi-language bindings to allow the algorithms to be accessed from tailored applications. The NIST could then continue to sell their own general purpose application. The marketing issue is whether it would turn out that everybody would continue to use the NIST's application even given its apparent limitations.

    But the real issue is sociology. One presumes that "Thermophysical Properties of Hydrocarbon Mixtures" implies a resource of interest to "Big Chem". Perhaps the reality is just that Exxon and Shell and BP and 3M and Monsanto and BASF create and maintain their own proprietary codes for such purposes?

    1. Re:It's the fundamental sources you want by puppet10 · · Score: 1

      Or in terms of people FORTRAN is the crabby old guy in the basement that knows where all the bodies are buried and all the bodges and bandaids applied over decades to make the project workable (also known as the FORTRAN Programmer ;).

      --
      -------- This space intentionally left blank --------
  33. Re:FEED ME by Anonymous Coward · · Score: 0

    Yeah, you wish, you efing tro!!

  34. Better yet... by pmarini · · Score: 1

    I would simply change your last step
    - and publish the package as free software
    with
    - and give back the restructured database to the copyright owner for them to publish just the data free from copyright

    If that doesn't sound right to them, then suggest that you will put it on a web page only accessible to yourself, leak the web link to Google and after it's indexed say "sorry for the mistake"...

    Most quality assurance processes also are "measurements" (with possibly a following remedy if non-conformant) but do you think that consulting companies would consider that their "measurements" should be available for free to amyone? (I do...)

    --
    Can I put a spell on those who can't spell?
    Your wheels are loose and they're losing their grip, good you're there.
  35. Re:FEED ME by causality · · Score: 4, Insightful
    Yes, I am deliberately replying to a top-level post to ask a question. A question about something that arguably doesn't belong in the summary (editors, anyone?).

    I was wondering whether it would be legal to buy a copy of such a database

    That's a legal question. The answer to that question might seriously complicate your life if you get it wrong. What would possess a person to ask this of Slashdot instead of contacting a lawyer? Better yet, why would a German expect a USA-based Web site to be familiar with the nuances of German (or EU) copyright law? I'm trying to picture a situation where I'd contact a German online forum to ask for legal advice pertaining to American law and I just can't come up with anything.

    I suppose next we'll see an Ask Slashdot which says "hi, I'm a diabetic and I forgot how much insulin I am supposed to inject myself with, please advise." And I'll have to scroll down significantly to see a partly-buried comment where someone finally suggests that perhaps he should be asking a doctor...

    --
    It is a miracle that curiosity survives formal education. - Einstein
  36. NIST Points of Contact by Anonymous Coward · · Score: 0

    As an alternative, a possibly more sane approach to your problem would be to proceed more in the fashion of the scientific world. Contact either NISTs SRM program, or Marcia Huber (the scientific lead on this SRM). You can find the contact information on the end of the page you posted in your link.

    What this will allow you to do, if you choose to use the SuperTrapp database and codebase, is establish a working relationship with NIST. More than likely you will still have to pay the cost recovery fee, but that's something that can be worked out between the NISTs lawyers, the US Dept of Commerce, and your company.

    To avoid the complexities of international copyright law, you may also wish to contact the Deutsches Institut fur Normung which is Germany's equivalent to the US NIST. Whether they have thermodynamic data to sell or not though is a different matter.

  37. Be very very careful by Fallen+Andy · · Score: 2, Insightful
    Three words: Don't do it. Here's a *real life* story as to why. Once upon a time (ok, about 13-14 years ago) there was a large Greek software company that wanted to make a property tax program. The problem was that they didn't have the data. Yours truly got to reverse engineer a competitors database. Yes, I extracted all of their pathetically encrypted DB (substitution cipher WTF?). Now, if you know anything about databases or mailing lists or even log tables, you know that there are often deliberately false entries so that it's easy to know your data is be ripped (a bit earlier in time I caught out a Cypriot company ripping off the english greek dictionary data I'd been involved in that way).

    I warned the project manager that sure go ahead and use the data as a basis for programming but not for the production program.

    A couple of months later, the competitors lawyers appeared and (cough) out of court (cough) settlement.

    Never did find out how much it cost "my" software house...

    In the end they had to employ a gaggle of impoverished undergrads to build their own DB.

    So, be very very careful. It might be a good idea to *ask* if you can re-use the data - often it's possible for non commercial purposes...

    Andy

  38. f2c? Don't do that! by Anonymous Coward · · Score: 0

    The one reason that programs are maintained in Fortran after all this years is that Fortran is wagonloads better for optimization. The compiler can take a lot more for granted than when using C with its pointers and one-dimensional arrays.

    So going via f2c costs performance. Try using extern "fortran" or similar to pull the code in.

  39. Re:FEED ME by mabhatter654 · · Score: 2, Insightful

    slashdot knows more than most IP lawyers. You have to remember, lawyering is essentially about either telling you what case law precedent has established (like don't rob banks), or arguing for your side, not about "truth" or "right and wrong". Most lawyers are more the type that will take the money, then figure out how to argue the way you want... they don't do good with "advice" not tied to rulings in court. Ask the right question and you'll pay the lawyers a bunch less money... nobody wants THAT!

    In regards to the question, he's looking to pull government funded data out of a program. Considering most countries in Europe allow the state to charge for everything it can and that they have "database aggregation" "copyrights". His plan would probably get him sued.

    So now that most of slashdot would agree on that outcome.... what other resources are available to obtain his desired outcome. This is where the slashdot crowd helps because they're in different countries and chances are pretty good somebody will know what government or research office he should talk to... There are still huge chunks of government services that aren't documented anywhere on the internet. Corporations that know who has the info freely available love to keep their sources opaque so the industry has to go thru them to get free information, and in many cases that means "handshake" deals so key offices never have time to get their web pages posted properly. You'd be surprised how many government services are still known only by the posting outside the office door (in the basement just above the beware of leopard sign) or maybe the phone book if you're lucky.

  40. SEE A LAWYER by Anonymous Coward · · Score: 0

    People never learn do they? Slashdot is news for nerds, not Q&A with lawyers.

    SEE A LAWYER. Don't expose yourself to a lawsuit based on the unauthorized practice of law so common on Slashdot. seriously. Perhaps you could contact NewYorkCountryLawyer directly - he probably knows enough and might be able to help you out.

    CASE IN POINT: everyone focuses on copyright but I wouldn't be surprised if the software has a license agreement that binds you to not copying the data - that's called a contract. Someone in Wisconsin tried that and got sued (ProCD v. Zeidenberg) and guess what? HE LOST. That may or may not be the case, but illustrates the problems with your approach to getting legal advice.

    Don't trust armchair lawyers especially when Copyright is concerned. There are so many myths out there you'd be surprised. (One that persisted until recently was: If I'm not doing this for commercial profit, its ok! WRONG)

    The practice of law is very fact intensive. No armchair lawyer and not even a real lawyer can answer your legal question on the basis of just your half paragraph "blurb." There are a lot of hidden factors that a lawyer is trained to look for and ask about.....
    I know lawyers can be expensive, and often have a bad rep, but they are highly trained individuals.

  41. Re:Crowdsourcing? Give me a break! by Anonymous Coward · · Score: 1, Insightful

    Uh, let's see now. You're going to expect all the idiots on the Internet to make precise measurements of (for example) the energy released in some chemical reaction at 357 Celcius temperature and 4.435 atmospheres of pressure?

    Are we reality-based here?

    What you want is a particular kind of crowdsourcing called "science". It tends to cost money because some people's thermomenters don't go up to 357C, so they need to buy better ones.

  42. Some background on why the problem is difficult by Anonymous Coward · · Score: 0

    So far as I know (I've not seen the most recent version) all the work in Supertrapp has been published somewhere. However, there is no comprehensive bibliography of the basic source material.

      I find the term "database" rather strange as I would not describe it as a database, but the authors chose to call it that. There's a similar program called Refprop which is much better but doesn't cover everything that Supertrapp does.

    Why this is really difficult:

    The fundamental problem for a pure fluid is intrinsically difficult. Google "Van der Walls" to get some basic idea.

    Supertrapp attempts to treat mixtures. This is much harder for a binary mixture and for arbitrary numbers of components becomes combinatorially complex.

    No measurements have ever been made for many possible combinations of fluids of interest. Interactions among the components are difficult to predict.

    Proprietary codes for major companies (e.g. big oil where I spent my career) tend to use either gross simplifications (i.e. Batzle-Wang, Han- Batzle) or are developed for a limited subset of the larger problem (i.e. process control problems for particular mixtures).

    The equations are a nightmare of complexity. After making the basic lab measurements, hundreds or even thousands of possible systems of equations are evaluated to see which best predicts the measurements (cf. R. Span, "Multiparameter Equations of State", Springer 2000).

    For those who think OO & inheritance are the answer, consider a class structure that attempts to mix fish, cars, plants, asteroids, & God in French, German, English & hieroglyphics.

    I've spent almost 20 years supporting large (e.g. 500,000+ line) FORTRAN codes for major oil companies. Supertrapp is probably the worst code I've seen.

    I considered doing this myself several years ago, however, after looking at the code, I realized it's a major undertaking just to figure out what the equations are from the code. It's also very difficult to create a sensible front end for the grammar implicit in the user input specification.

    Reg Beardsley

  43. Re:FEED ME by Anonymous Coward · · Score: 0

    HAHAHA, "slashdot knows more than most IP lawyers"

    You're joking right? You have to be..... because we all know how accurate slashdot is, especially on legal issues! ::rollseyes::

    If you are serious, then your ignorance is dangerous in that it is compounded by false confidence.

  44. Copyrightable by Anonymous Coward · · Score: 0

    http://en.wikipedia.org/wiki/Directive_on_the_legal_protection_of_databases

  45. Re:Crowdsourcing? Give me a break! by Alsee · · Score: 1

    Uh, let's see now. You're going to expect all the idiots on the Internet to make precise measurements

    No.

    I'm thinking that if there is a community interested in this kind of software then *those* people may already have this sort of data already lying around somewhere.

    -

    --
    - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
  46. Feist vs Rural.... by eee_eff · · Score: 1

    IANAL but, the issue of the copyright status of databases has come before the Supreme Court. The issue was: is an alphabetized list copyrightable? The court said no, because the database itself did not contain originality, it just was pure information. The key fact here is whether or not the database you describe is original, or it just contains facts. From wikipedia: "The ruling of the Court was written by Justice O'Connor. It examined the purpose of copyright and explained the standard of copyrightability as based on originality. It is a long-standing principle of United States copyright law that "information" is not copyrightable, O'Connor notes, but "collections" of information can be. Rural claimed a collection copyright in its directory. The court clarified that the intent of copyright law was not, as claimed by Rural and some lower courts, to reward the efforts of persons collecting information, but rather "to promote the Progress of Science and useful Arts" (U.S. Const. 1.8.8), that is, to encourage creative expression. Since facts are purely copied from the world around us, O'Connor concludes, "the sine qua non of copyright is originality". However, the standard for creativity is extremely low. It need not be novel, rather it only needs to possess a "spark" or "minimal degree" of creativity to be protected by copyright. In regard to collections of facts, O'Connor states that copyright can only apply to the creative aspects of collection: the creative choice of what data to include or exclude, the order and style in which the information is presented, etc., but not on the information itself. If Feist were to take the directory and rearrange them it would destroy the copyright owned in the data. The court ruled that Rural's directory was nothing more than an alphabetic list of all subscribers to its service, which it was required to compile under law, and that no creative expression was involved. The fact that Rural spent considerable time and money collecting the data was irrelevant to copyright law, and Rural's copyright claim was dismissed." . http://en.wikipedia.org/wiki/Feist_Publications_v._Rural_Telephone_Service . http://caselaw.lp.findlaw.com/scripts/getcase.pl?court=US&vol=499&invol=340

  47. Geek Skills by Nom+du+Keyboard · · Score: 1

    no one can read Fortran anyway

    You show yourself as a snob, Sir. Probably most any serious geek - including this one - will understand Fortran just fine. And given a little bit of time and money it can be rewritten into pretty much anything else since most other languages are supersets of Fortran.

    --
    "It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
  48. There exist open source steam functions at least by theanphibian · · Score: 1

    This would be easy for steam properties. XSteam: http://www.x-eng.com/Download_XSteam.htm They explicitly state that their functions are open source, substantiated by the fact... you can download the code real easy right there. I've been using their Excel visual basic code. No, they don't have any for Fortran, but their VBA stuff is not hard to figure out, and I've actually been able to change the code and use it in Fortran. It's not that different. If you desperately need free Fortran steam tables, I wouldn't even have a problem sharing what I have. As for the steam tables themselves, XSteam claims to use IAPWS IF97, which seems pretty thoroughly public domain. They have other options available on http://www.iapws.org/ as well. ...But now for Hydrocarbon Mixtures, I'm not sure what to tell you. A lot of people here are talking about the formulation of the tables constituting significant intellectual work, and that's true, but there is public domain government work and open source solutions for steam tables, and considering that the data for hydrocarbon stuff is also clearly public domain, I don't know. I'm just as lost as you are.

  49. Not even close by pestie · · Score: 2, Insightful

    I don't know if you're trolling or just grossly misinformed, but that's not even close to correct. Lyrics are the copyrighted creative works of the person/people who wrote them. "Changing one word" does not allow someone else to then distribute the lyrics legally. That would be considered a "derivative work," the creation of which is a right provided to copyright holders under copyright law.

    1. Re:Not even close by budgenator · · Score: 1

      I didn't say the karaoke publisher could distribute the original song writers lyrics without license because they do, but by changing a word or two it they own the changes and it's easier for them to litigate copying because they can more easily should that it was their disk that was copied and can bring the original song writer in as an additional injured party.

      If you submit a bug patch to a GPL'ed project, you own the copyright to the patch, the original programers own the copyright to their code.

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
  50. Re:FEED ME by Eivind+Eklund · · Score: 1

    Slashdot is an international website; while hosted in the US, there seems to be at least about the same amount non-US readers as US readers. (I believe there even was some statistics shown that indicated that there were more non-US readers, but I may be mixing up websites WRT those.)

    --
    Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
  51. You have to pay for DB, I think by HollyMolly-1122 · · Score: 0

    Anyway, I think you should have an agreement with those, who collected database entries at least. Somebody paid for a time to enter all this data, or paid to people who scanned and arranged that data into the database.

  52. What database? by ephraimhorse · · Score: 3, Informative

    All the formulation for the prediction of water properties are published by International Association for the Properties of Water and Steam (IAPWS) so that they can be used. It is often important to use exactly the same correlations so that that all the thermodynamic data are self-consistent. Therefore the formulations are standardized by an international body. I do not think that the use of this formulae is in any way restricted because such restriction would defeat the very purpose - standarization. See http://www.iapws.org/ for the collection of the current formulations. There may be a restriction for a particular implementation (computer program) or sets of tables ( "lookup tables" and interpolation are often used for performance). Not sure. Hope someone starts an extension to implement these kind of things in Gnumeric. Cheers. Ephraim the horse.

    1. Re:What database? by HollyMolly-1122 · · Score: 0

      Ok, if all the formulation for the prediction of water properties are published internationally free than it can be used. Let's start enter into own DB all this data by hand! Too much time needed ? Time costs money. Everybody can learn and make wonderful cookies at home, but still if it's too much hassle they go to the restaurant and pay money for already prepared dinner.

    2. Re:What database? by chthonicdaemon · · Score: 1

      No need to recode from the IAPWS standards (I've done it, but those equations are huge and a pain to type and debug). Just go use http://freesteam.sourceforge.net/

      --
      Languages aren't inherently fast -- implementations are efficient
  53. Compilers have come a long way by Nicolas+MONNET · · Score: 1

    The main perf advantage of Fortran however was that it could automagically make use of vector machines.

  54. It's either copyrighted or it isn't by Nicolas+MONNET · · Score: 1

    It's either copyrighted or it isn't. Nothing to do with the citizenship of the reader, ever. At least I have never seen anything like this. The only thing that comes close is reciprocity clauses where another country's copyrights are only recognized if it recognizes the other country's, but nothing based on the country of the *user*, just the work.

  55. Can't read fortran, too bad by Douglas+Goodall · · Score: 1

    What is the big deal? Fortran II was my first language (IBM 1620) and was very straightforward. It could have been algol or some other strange dialect.

  56. Re:FEED ME by rp · · Score: 1

    You're so wrong. Your comparison is flawed.

    This issue is clearly relevant to many Slashdot readers. The reason to bring up is to solicit suggestions from interested readers, many of whom may have relevant experience that they may be willing to share. The legal question is very important so it must be stated. The OP did *not* ask Slashdot to *answer* that question. Not all useful information gathering related to a legal question is legal advice.

    Imagine Stingdot, a forum for people with long-term medical conditions. On such a forum it would be perfectly appropriate for someone who has been diagnosed with diabetes to ask a question "Managing insulin injections" that really revolves around a concrete medical question, namely, how much insulin to inject and when. The goal of raising that subject would not be to obtain an answer to the question instead of asking a doctor, but rather, to seek comparisons with other people's cases, how they manage in practice, how critical to be of the doctor's orders, etcetera.

  57. Re:FEED ME by powerlord · · Score: 1

    HAHAHA, "slashdot knows more than most IP lawyers"

    You're joking right? You have to be..... because we all know how accurate slashdot is, especially on legal issues! ::rollseyes::

    If you are serious, then your ignorance is dangerous in that it is compounded by false confidence.

    QFT.

    However, I wouldn't be surprised if SashDot knows more about IP than most laymen, and than quite a few lawyers who do not practice IP law.

    --
    This space for rent. All reasonable inquiries will be entertained at proprietors discretion.
  58. Re:FEED ME by prefec2 · · Score: 1

    /. is not an US only web-site. However, you're absolutely right with your advice to ask a lawyer. Also I would recommend to read the license which comes with the data and code. And I want to add: Fortran is a readable language and it is not really hard to learn.

  59. Supertrapp vs. Refprop by EricLemmon · · Score: 1

    The Supertrapp program from NIST will soon be fully superseded by the REFPROP program. This newer program calculates REFerence PROPerties of nearly 100 fluids from equations of state in a user-friendly environment. The program can be found at www.nist.gov/srd/nist23.htm. Not all of the fluids that were available in Supertrapp are available in REFPROP, but our current work will soon make them all available, at which point the Supertrapp program will no longer be available for purchase.

    To clarify several issues that have been brought up here, although the word "database" is used to describe these products, they are in reality only programs that use equations of state to calculate thermodynamic properties. The equations of state are developed using high accuracy data as explained in Lemmon, E.W. and Jacobsen, R.T, "A New Functional Form and New Fitting Techniques for Equations of State with Application to Pentafluoroethane (HFC-125)," J. Phys. Chem. Ref. Data, Volume 34, Number 1, pp. 69-108, 2005. There is no data in the databases, but this generic word is used to describe all of the standard reference data products sold by NIST.

    Concerning the copyright, users of the programs should be aware of the Standard Reference Data Act, PL 90-396, Section 6, which states "The Secretary may secure copyright and renewal thereof on behalf of the United States as author or proprietor in all or any part of any standard reference data which he prepares or makes available under this Act." The SRD Act is online at http://www.nist.gov/srd/publiclaw90-396.pdf

    If you have further questions about the Refprop or Supertrapp programs, please feel free to contact me.

    Eric Lemmon (Eric.Lemmon@nist.gov)