{"id":1518,"date":"2013-07-31T20:45:32","date_gmt":"2013-07-31T20:45:32","guid":{"rendered":"http:\/\/garysieling.com\/blog\/?p=1518"},"modified":"2020-03-31T00:46:31","modified_gmt":"2020-03-31T00:46:31","slug":"u-s-code-available-in-xml-format","status":"publish","type":"post","link":"https:\/\/www.garysieling.com\/blog\/u-s-code-available-in-xml-format\/","title":{"rendered":"U.S. Code Available in XML Format"},"content":{"rendered":"

I saw today that the U.S. Code is available online now for download<\/a> in a structured format. Ideas for apps, anyone?<\/p>\n

It’s worth noting that this was available in some form already, e.g. through Cornell<\/a>. <\/p>\n

To give you a taste of what is there, I extracted a few interesting sections. The first part is some metadata about dc:creator is set to USCConverter 1.0, which would suggest that they built a custom tool to do this. <\/p>\n

\n\n  Title 50<\/dc:title>\n  USCTitle<\/dc:type>\n  50<\/docNumber>\n  Online@113-21<\/docPublicationName>\n  OLRC<\/dc:publisher>\n  2013-07-26T05:19:57<\/dcterms:created>\n  USCConverter 1.0<\/dc:creator>\n<\/meta>\n<\/pre>\n
Some of the headings are split up in this somewhat odd fashion. <\/p>\n
\nTitle 50\u2014<\/num>WAR AND NATIONAL DEFENSE<\/heading>\n<\/pre>\n
What I found most interesting is the ease with which you can extract citations. They seem to have used a GUID (or similar) structure for IDs. These have the nice property of making it easy to generate unique identifiers, without cross-referencing other locations. The downside is that they are not “natural” keys, meaning it looks like you can’t infer anything about where you are.<\/p>\n
An open question to investigate – how much text would have to change over time in a section to trigger a new ID? These also points out the lack of historical information – you have to manually get old values for this text. Even armed with this citation information, you need access to court records, as these clarify, amend, or remove sections of law. It’d also be interested to know how \/ when the text in these documents are updated if a court strikes down a law. Right now, the only way I know of to get access to court records easily is through PACER (or RECAP, which has an archive of a small fraction).<\/p>\n
\n\n(e)<\/num>\n Crediting of amounts collected<\/heading>\n\n
Amounts collected under this \nsection shall be credited to the account or accounts from which costs \nassociated with such amounts have been or will be incurred, to reimburse \nor offset the direct costs of the program referred to in subsection (a).<\/p>\n<\/pre>\n
Another selection – the interesting bit to me here is they’ve included all sorts of random formatting information. You could probably use this to train an NLP algorithm to extract some form of context, but it would be a lot of work.<\/p>\n
\n\n\n
\n401 note \n(Act July 26, 1947, ch. 343<\/a>,\ntitle III, \u00a7\u202f310, \n61 Stat. 509<\/a>)\n<\/p>\n<\/td>\n\n
3077<\/p>\n<\/td>\n<\/tr>\n<\/pre>\n","protected":false},"excerpt":{"rendered":"
I saw today that the U.S. Code is available online now for download in a structured format. Ideas for apps, anyone? It’s worth noting that this was available in some form already, e.g. through Cornell. To give you a taste of what is there, I extracted a few interesting sections. The first part is some … <\/p>\n
Continue reading “U.S. Code Available in XML Format”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[5,6],"tags":[335,385],"aioseo_notices":[],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.garysieling.com\/blog\/wp-json\/wp\/v2\/posts\/1518"}],"collection":[{"href":"https:\/\/www.garysieling.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.garysieling.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.garysieling.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.garysieling.com\/blog\/wp-json\/wp\/v2\/comments?post=1518"}],"version-history":[{"count":1,"href":"https:\/\/www.garysieling.com\/blog\/wp-json\/wp\/v2\/posts\/1518\/revisions"}],"predecessor-version":[{"id":6505,"href":"https:\/\/www.garysieling.com\/blog\/wp-json\/wp\/v2\/posts\/1518\/revisions\/6505"}],"wp:attachment":[{"href":"https:\/\/www.garysieling.com\/blog\/wp-json\/wp\/v2\/media?parent=1518"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.garysieling.com\/blog\/wp-json\/wp\/v2\/categories?post=1518"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.garysieling.com\/blog\/wp-json\/wp\/v2\/tags?post=1518"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}