From talking to various people and looking at the state of play in US
State Legislatures, there appears to be a real need for a simple,
standardized expression of bill status information.
1 Lots of folks track bills - citizens, members, lobbyists etc.
2 Multiple commercial companies I know of struggle with "scraping"
bill information from Legislatures for use in their products (Eg.
Thomson Accela, LexisNexis StateNet, KnowWho, Legination etc)
3 Multiple not-for-profits struggle with it too: Sunlight's OpenStates
project for example
4 Legislatures are starting to provide Web APIs -
data.gov style
5 The time would thus seem to be right to look at standardizing what
comes out of those Legislature APIs for Bill Status so that downstream
consumers can do a single piece of integration work and reasonably
expect to get multiple State Legislatures covered
as a result
6 The Kansas website (
kslegislature.org) has an RESTian API that we
created. Rather than invent our own XML/JSON
schema for the information we provide, I would prefer to be able to
target a NIEM standard schema.
Some cautionary notes:
1 Legislatures are remarkably different in how they execute bill
workflows and in the terminology they use
2 We must avoid going down deep ratholes trying to standardize too
much
3 We must get input from people who work in the legislatures
themselves. No amount of reading the "How a bill becomes
a law" booklets often found on Legislative Websites will provide the
kind of information that is needed.
I will be approaching NALIT for their input on (3) above. Would love
to hear from downstream consumers about what information they would
like to see in the Bill Status schema. I have access to reasonably
good knowledge about KS, ND, PA and NV to get the ball rolling on
this...
Thoughts?