[FoRK] divegeek/uscode · GitHub
gstock at nexcerpt.com
Mon May 28 08:59:04 PDT 2012
The first and most important goal for /uscode: ALWAYS force a large
"NOT CURRENT" watermark (as unavoidable and undefeatable as possible)
beneath -- and multiple datestamps on (all four corners of) -- any
display object that is not ~purely~ current statute, now in force.
I have been watching a local township disintegrate politically over the
past several months, because one idiot with a grudge found a 30-year old
Attorney General opinion that once (long ago) could have been
interpreted to mean elected officials were in violation of State law.
I personally pointed him to later AG opinions ~reversing~ that finding,
as well as legislative action explicitly making such activities legal.
Still, he clings to the notion that -- since he can print out a 30-year
old ruling that the activity "is impermissible" -- he has the law on his
side. And, every few days, he convinces one more idiot that it's
somehow still true...
On 5/27/12 7:49 PM, Damien Morton wrote:
> Often laws are constructed as deltas to earlier laws. e.g. section xxxx
> supercedes section yyyy, or section xxxx alters section yyyyy by removing
> paragraph A and replacing it with paragraph B.
> It would be good to have unified flattened and flattened text which
> represents the law as-is.
> Perhaps a legal microformat for deltas is called for.
> On Sun, May 27, 2012 at 7:37 PM, Stephen D. Williams<sdw at lig.net> wrote:
>> Awesome. The US Congressional bills / laws site, last I looked a year or
>> two ago, was a terrible web app example: An opaque database search with no
>> way to link to a specific law or version of a law.
>> This is far, far better. Every law and bill at all levels of government
>> should be in this.
>> And it would be good to encode laws in increasing levels of metadata and
>> modeling so that you could at least find every law pertaining to a subject
>> On 5/25/12 2:05 PM, Jeff Bone wrote:
>>> Apologies for the naked link. Comments: English is a shitty programming
>>> language, USC is a bug-ridden behemoth legacy system, and much of the
>>> action happens elsewhere anyway (e.g., regulatory apparatus etc.)
>>> That said this is a powerful idea.
>>> Taken one step further - laws to be encoded in executable descriptions
>>> (say, arbitrarily, cf financial instruments / contracts, Python) and you'd
>>> have real transformative change. Profiling, bug elimination, absurd
>>> complexity reduction through refactoring, open source the whole project w
>>> legislators and their dev staffs responsible for pulling changes into trunk
>>> based on voting, etc.
>>> What are the (fucking!) domain objects, Kenneth?
>>> Pipe dream, sure. Model for replacement when the system finally breaks
>>> On May 25, 2012, at 15:56, Jeff Bone<jbone at place.org> wrote:
>> FoRK mailing list
> FoRK mailing list
More information about the FoRK