Waldo Jaquith
Waldo Jaquith
PHP, Python, and Ruby all stand out as obvious choices. I think we'd want functions to retrieve a given law, a definition, or a given structural unit, and convert JSON...
If somebody discovers an error while watching the output of the parser, they have to await the completion of the parsing process to do something about it. That could be...
There is a great deal of interest in storing laws in GitHub. Provide the functionality to export laws to GitHub, presumably via plain-text export to the file system. The [glip...
Many people are going to want to use WordPress to run a blog on State Decoded sites. (In fact, the design is likely to facilitate this.) But there's nothing about...
The XML import system is swell, but XML is awful. For folks who don't want to deal with XML, but don't want to modify the parser just to import JSON,...
Storing all laws with each new release is totally reasonable for laws that are updated annually. But some legal codes are updated continuously. It's not reasonable to store a complete...
After piping everything through MySQL during the setup process, most of the data can really be stored anywhere. Save for the internal API—that presents its own challenges—we're basically just dealing...
Abstract the functionality that already exists for Virginia into a standard function that can be bundled with `class.State-sample.inc.php` and called within `law.php`. At the moment, it's necessary that each state...
After we can view old versions of a law (#362), then we'll want to be able to compare changes. Look to WordPress 3.6's revisions viewer. They've got a great little...
@boboroshi, one of the features that we'd discussed for the UI was the ability to provide preview data of the contents of structural units. So in a listing of titles...