Nieman Foundation at Harvard
HOME
          
LATEST STORY
Is the future about one all-knowing AI or many? The new app Poe gets you ready to chat with them all
ABOUT                    SUBSCRIBE
March 13, 2012, 1 p.m.
Screen shot of Virginia Decoded

Virginia Decoded is the prettiest state code you’ve ever seen

Knight News Challenge winner Waldo Jaquith says a state code should be designed like a social network.

Screen shot of Virginia Decoded

Developer Waldo Jaquith has launched a public beta of Virginia Decoded, an astonishingly user-friendly presentation of his home state’s code. It’s the first iteration of Jaquith’s open-government platform, The State Decoded, a 2011 Knight News Challenge winner.

Because Virginia makes its code available as structured data — which puts it ahead of most states, Jaquith says — he can build a website that looks better than the official one. Compare Virginia’s entry for § 24.2-956, which regulates campaign ads in print media, to Jaquith’s implementation. The former offers no design and little context. Jaquith’s page provides understandable history information, a list of attempted amendments, cross-references to other provisions, and inline definitions that pop up for key terms.

“Think of a code as a social network,” Jaquith told me. “Every law is like a person. Every law is connected to every other law via court decisions, legislation, shared definitions, cross-citations, and a dozen other ways.”

When you start thinking about laws that way, the user experience changes dramatically. Jaquith said every official state code website in the United States is, without exception, “wretched,” in effect making public data inaccessible to the public. Jaquith plans to post his source code on GitHub and help implement the State Decoded platform in other states.

Jaquith explained four key features of the website to me in an email:

The first, and best (IMHO), is the built-in glossary. The software scrapes the text of the code to find definitions, which it extracts, figures out the scope of it, and then stores to apply in the relevant sections of the code. (For instance, “person” has 118 separate definitions in the Code of Virginia. The most relevant one must be applied each time that it is used.) The reason why this is so important is that definitions are wildly important in understanding a law. A law might say “No playing loud music on weeknights downtown,” but unless you know the definition of “loud,” “music,” “weeknights,” and “downtown,” it’s of no value whatsoever. The definitions of those four words might be scattered widely, throughout the code. The State Decoded puts them all in one place. You can see an example of definitions in this section of the code about the state’s FOIA law. The defined words have a subtle, dotted underline, designed to make it easy to ignore for people who have no interest in them, but noticeable by folks to whom they’re very important.

The second is the connection back to legislation. In the sidebar of another section of the FOIA law, § 2.2-3711, you can see “Amendment Attempts.” That’s being pulled via a JSON request to Richmond Sunlight (another website of mine), which is listing every bill that cites § 2.2-3711. That allows people to see how laws have built up over time, and what sort of interest that there is, at least among legislators, in amending it.

The third is the connection to other parts of the code. Keeping open § 2.2-3711, you’ll see “Cross References” farther down in the sidebar. That’s a listing of every other part of the code that cites § 2.2-3711. Sometimes there are connected parts of a code that are far, far apart—in different titles, hundreds of pages away (on paper). This is a first step towards integrating them, breaking down the sometimes artificial barrier of topical divisions and regrouping laws more meaningfully.

And the fourth and final feature that you won’t want to miss is the connection to case law. For any section of the code for which there have been state court decisions that cite that section, those decisions will appear in the sidebar, under “Court Decisions.” (See, for instance, § 18.2-33.)

POSTED     March 13, 2012, 1 p.m.
Show tags
 
Join the 60,000 who get the freshest future-of-journalism news in our daily email.
Is the future about one all-knowing AI or many? The new app Poe gets you ready to chat with them all
Poe lets you use ChatGPT alongside a new rival named Claude — which seems to work better in important ways.
Can journalism’s “reckoning” with racism progress to accountability — and redress?
“The magic — because magic can be good or bad — of narrative is that it can counteract your lived experience.”
Google now wants to answer your questions without links and with AI. Where does that leave publishers?
A dozen years ago, Eric Schmidt forecast the AI pivot that’s playing out this week. And the questions it prompts — around the link economy, fair use, and aggregation — are more real than ever.