Earlier quoted context omitted.
As the schema guide explains, in 1999 they picked XML based on the study from 1996: "Following a 1999 feasibility study on XML/SGML, the Committee on House Administration adopted XML as a data standard for the exchange of legislative documents" http://uscodebeta.house.gov/download/resources/USLM-User-Gui... It took the US Govt 17 years to release 200,000 pages of the US code in XML.
I think the most time consuming part of the conversion is from text to digital. That's what took so long. Interchanging formats should be relatively easy. Back in 1999, json wasn't even around. IMO in today's API centric, and javascript ruled world. json would be a lot more useful.
The entire US Code is now online in XML
51–60 of 244 posts
Re: The entire US Code is now online in XML
#52now if the same could be provided for bills(ideally before they are voted on), and that should go in github or something.
Maybe try to organize some tech-minded staffers on the hill? Get them to put bills onto a github repo when they are made public, maybe even XMLizing it to make it more exposed to machine analysis. It'd be a huge step in congressional transparency, especially now that bills are going into the high hundreds and thousands of pages (not a dig at the healthcare bill in particular, just a trend).
Whereas, I would like to see the drafts and how they progress behind closed doors with all the lobbying influence.
Re: The entire US Code is now online in XML
#53In short, that allows a lawyer to answer almost any question with "it depends," and start billing.
Re: The entire US Code is now online in XML
#54It's tragic that the United States (Federal) Legislative Model (USLM) is defined in terms of W3C XML Schema Definition language (XSD) instead of the comparably sane RELAX NG and its easily interpreted compact syntax. You would think that something this important ought to be made clear and understandable. EDITED TO CLARIFY: The tragic part isn't that the schema is given in XSD but that it's defined in XSD, which lacks…
Pretty much every popular & widely used language / platform has XSD support... hell, it's so commonplace there are probably schema aware xml parsers in Brainfuck, INTERCAL and Befunge.
RELAX NG may well be a better choice, but saying this is "tragic" strikes me as a bit of excessive hyperbole.
Re: The entire US Code is now online in XML
#55Re: The entire US Code is now online in XML
#56Earlier quoted context omitted.
Agreed, for long running data sets you really want schemas.
There are Json schema implementations out there.
Re: The entire US Code is now online in XML
#57Caveat for for many of us overly rational thinkers: the powers that be deliberately are allowed to 'interpret' this code nondeterministically by many different means including its 'spirit,' admissibility of relevant information, manipulation of venue and participants, apparently even extrajudicial proceedings lately. In short, that allows a lawyer to answer almost any question with "it depends," and start billing.
Re: The entire US Code is now online in XML
#58Earlier quoted context omitted.
I was under the impression law is essentially "append only". New laws override existing laws, but the text of the existing law never changes.
Laws are essentially diffs against the US code. The diff (slip law) is canonical. They are continually compiled into the US code, which can involve deleting or changing text just like a diff, and periodically an edited, annotated code is published. After a certain amount of time, Congress enacts a portion of the published code, making it canonical and overriding any prior slip law. See: http://en.wikipedia.org/wiki/U…
Re: The entire US Code is now online in XML
#59This actually makes law accessible to the technologically-savvy out there, and is going to launch a thousand apps giving specialized legal advice. This could in turn mean a reduction in the cost of litigation, which would hopefully be passed on to the rest of us. Hopefully I won't get sued for that statement.
Re: The entire US Code is now online in XML
#60This is pretty awesome, and if it were in git/hg would have the ability to write a 'blame' tool to figure out who voted on the part of the law that is pissing you off :-)
Many laws are passed jn bundles and require compromise. Just because your Senator voted to support farm subsidies, doesn't mean he likes them - it just means he wanted a minimum wage increase to pass more.