News for hackers. Stuff that matters.
Re:Governments turn tables by suing public records requesters by pc86 on Monday September 18, 2017 @03:15PM (#15278660)
This "git for law" meme is a nearly constant refrain but it is simply not appropriate for legal text. Yes, for de minimus yet important changes, like changing a "shall" to a "may," it makes sense. For anything beyond that, trying to shoehorn legislation into a format and workflow design for software is a fool's errand at best.
Re:Governments turn tables by suing public records requesters by KingPrad on Monday September 18, 2017 @04:11PM (#15279104)
I disagree that version control is inappropriate. I worked for a company whose primary product was tracking government legislation through a database built on Subversion. (acted as a DB but used Subversion for a variety of reasons. I know it sounds strange).

It seemed to work fine to record incremental changes, tag specific revisions as being checkpoints for various stages of review and approvals. And anyone could search current and historical versions.

The overall legislation system needs flexibility to deal with complex and changing workflows, but storing documents (with change over time) and the links between them can be encoded just fine. As long as there are flexible ways to string them together, they can be represented in whatever structure makes sense: final law with all current amendments; original law, with amendments as annotations, separate pieces of legislation, linked by the overall law, etc. None of that has to be encoded in a super-strict heirarchy, but as long as it's all being stored in can be presented however one wants.

I don't see the fatal flaw. I see imperfections and compromises, but not the flaw so bad as to say "don't bother".

Re:Governments turn tables by suing public records requesters by jxramos on Monday September 18, 2017 @06:14PM (#15280155)
The key is incremental change I agree; if legislators only interact and record changes in final form with all the mass of changes dumped onto a user for review then such a project would be untenable. Small changes would really improve usefulness, and I daydream sometimes about what sort of dodgy log messages folks would use to obscure intent. Either way it could really empower a lot of analysis I'd imagine.

Do you mind sharing with us the company and the product you developed in this space?

Re:Governments turn tables by suing public records requesters by walshemj on Monday September 18, 2017 @06:49PM (#15280381)
Correct parliamentary procedure should track all motions changes and proposed changes (even those ruled out of order) to motions I certainly do as a member of a CBC / SOC (Conference Business Committee / Standing Orders Committee)
Re:Governments turn tables by suing public records requesters by adekok on Monday September 18, 2017 @05:09PM (#15279620)
The alternative is that we are unable to track changes in the law. Which to me, makes the law untrustworthy.

Untrustworthy laws are rather more foolish than doing revision tracking on English text. I mean... FFS how hard is it to track changes to English text? Really?

Re:Governments turn tables by suing public records requesters by KZeillmann on Monday September 18, 2017 @03:45PM (#15278889)
I'd at least like to see the diffs in a more readable format. Many laws are compilations of, "Amend [section of law] to read as follows: [new wording]"
Re:Governments turn tables by suing public records requesters by walshemj on Monday September 18, 2017 @06:53PM (#15280400)
yes that is how its done you normally produce an omnibus showing motions with the amendments next to them plus a list of Consequentials eg if motion 57 passes motion 63 falls.
Re:Governments turn tables by suing public records requesters by hueving on Monday September 18, 2017 @05:37PM (#15279847)
>trying to shoehorn legislation into a format and workflow design for software is a fool's errand at best.

It's not for software, it's for text. Is the law no longer written in text?

Re:Governments turn tables by suing public records requesters by walshemj on Monday September 18, 2017 @06:51PM (#15280389)
There are already "workflows" designed for parliamentary procedures Citrine's ABC of Chairmanship and Roberts rules are two examples.
Re:Governments turn tables by suing public records requesters by bobwaycott on Monday September 18, 2017 @08:44PM (#15280949)
The suggestion isn’t to use git or a git-like for procedures, but for tracking the text of laws.
Re:Governments turn tables by suing public records requesters by walshemj on Tuesday September 19, 2017 @12:26PM (#15286063)
Yes that is how Citrine and Roberts are used today in parliamentary systems I have been doing this for years for formal conferences.

The procedure is similar to they way git is used for code though with a greater or lesser amount of automation - in the old days you had multiple documents and you physically cut and pasted them together to produce the final document

Re:Governments turn tables by suing public records requesters by jxramos on Monday September 18, 2017 @06:25PM (#15280232)
Looks like some fellas in Germany took a stab at it. I'm interesting in seeing how they've carried on since this taping back in 2013, sounded very manual but some pirate party adopted the idea if I understand him correctly https://www.youtube.com/watch?v=-qql1Ess7qM
Re:Governments turn tables by suing public records requesters by petre on Tuesday September 19, 2017 @12:54AM (#15281893)
It's inappropriate if your goal is to obfuscate the law and make cross references to past laws, thus creating demand for more lawyers.