Open Source Effort To Codify America's "Operating System" Online 98
Rubinstien writes "O'Reilly Radar is reporting on an effort to produce Law.gov, 'America's Operating System, Open Source.' The group Public.Resource.Org seeks to 'create a solid business plan, technical specs, and enabling legislation for the federal government to create Law.gov. [They] envision Law.gov as a distributed, open source, authenticated registry and repository of all primary legal materials in the United States.' According to its new website, 'Law.gov would be similar to Data.gov, providing bulk data and feeds to commercial, non-commercial, and governmental organizations wishing to build web sites, operate legal information services, or otherwise use the raw materials of our democracy.'"
Nice (Score:3, Interesting)
Anyone got an RSS feed for bribes accepted per politician?
It's open access to this information that democracy is built upon.
VOLUME! (Score:0, Interesting)
The sheer VOLUME of laws forms a sea within which lawyers swim. This effort sounds like more utopian mental masturbation.
Bills are patches (Score:5, Interesting)
Waiting for the User Model (Score:3, Interesting)
Re:Open source doesn't mean crap (Score:3, Interesting)
"Open Sourcing" the constitution and the laws really makes no sense. Creating a free service, built on open source technologies with open APIs for accessing data in open formats so that anyone can have access at any time to the text of laws makes a great deal of sense and is something which should have been done a long while ago, because thomas.loc.gov kind of pisses me off.
Re:Lexis and Westlaw? (Score:3, Interesting)
I concur. Lawyers care only tangentially about the code itself. What they are looking for is case law - not what did the law say, but what does the law mean? And what the law means isn't determined by what the law says, but what a judge says it means - how the judge interprets it.
And that interpretation is pretty static - when a judge gives a ruling on a code, other judges are reticent to overturn that ruling. Instead, they'll try to clarify or eliminate ambiguity in the earlier ruling.
In the '90s, I tried to do a 'net startup by making it easy to search through state codes. I built elaborate pattern matching algorithms to break up state statutes by article, section, and number, and build a huge, hyper-relational database (think wiki on steroids) back when a Pentium 90 was cutting edge. It took me some 4-6 months of long, hard work to get my prototype together for a few large states. (California and Texas)
I succeeded, the product worked fine, but no lawyers were interested - even for free. That was a very short-lived enterprise.
Re:Is this where we can read the health care bill? (Score:3, Interesting)
It'll be like digg -- you can vote a bill up or down and the most popular ones are passed :-P
It is outsourcing the reading process. And to those who don't like the system people will say -- similar to as they do now with wikipedia -- "if you don't like the bill, just vote it down'
Difference between Law and Code (Score:3, Interesting)
Laws can and must be broken. No government can survive the stringent enforcement of its own laws. This is the fundamental difference between law and procedural computer code. Law requires judgment while code merely requires execution.
On the level that this project seeks to work, however, the task might not be completely foolish.
Re:Bug Tracker? (Score:2, Interesting)