Another Word For It Patrick Durusau on Topic Maps and Semantic Diversity

September 2, 2011

Federal Register (US)

Filed under: Data Source,Law - Sources — Patrick Durusau @ 7:53 pm

Federal Register (US)

From the developers webpage for the Federal Register (US):

Project Source Code

FederalRegister.gov is a fully open source project; on GitHub you can find the source code for the main site, the chef cookbooks for maintaining the servers, and the WordPress themes and configuration. We welcome your contributions and feedback.

API

While the API is still a work in progress, we’ve designed it to be as easy-to-use as possible:

  • It comes pre-processed; the data provided is a combination of data from the GPO MODS (metadata) files and the GPO bulkdata files and has gone through our cleanup procedures.
  • We’re using JSON as a lighter-weight, more web-friendly data transfer format
  • No API keys are needed; all you need is an HTTP client or browser.
  • The API is fully RESTful; URLs are provided to navigate to the full details or to the next page of results (HATEOAS).
  • A simple JSONP interface is also possible; simply add a `callback=foo` CGI parameter to the end of any URL to have the results be ready for cross-domain JavaScript consumption

See the webpage for Endpoints, Search Functionality, Ruby API Client and Usage Restrictions.

For those of you who are unfamiliar with the Federal Register:

The Office of the Federal Register informs citizens of their rights and obligations, documents the actions of Federal agencies, and provides a forum for public participation in the democratic process. Our publications provide access to a wide range of Federal benefits and opportunities for funding and contain comprehensive information about the various activities of the United States Government. In addition, we administer the Electoral College for Presidential elections and the Constitutional amendment process.

The Federal Register is updated daily by 6 a.m. and is published Monday through Friday, except Federal holidays, and consists of four types of entries.

  • Presidential Documents, including Executive orders and proclamations.
  • Rules and Regulations, including policy statements and interpretations of rules.
  • Proposed Rules, including petitions for rulemaking and other advance proposals.
  • Notices, including scheduled hearings and meetings open to the public, grant applications, administrative orders, and other announcements of government actions.

We recommend reading the “Learn” pages of this site for more on the structure and value of the Federal Register and for an overview of the regulatory process.

Or as it says on their homepage: “The Daily Journal of the United States Government.”

August 30, 2011

LC Name Authority File Available as Linked Data

Filed under: Law - Sources,Legal Informatics,Linked Data — Patrick Durusau @ 7:13 pm

LC Name Authority File Available as Linked Data

From Legal Informatics Blog:

The Library of Congress has made available the LC Name Authority File as Linked Data.

The data are available in several formats, including RDF/XML, N-Triples, and JSON.

Of particular interest to the legal informatics community is the fact that the Linked Data version of the LC Name Authority File includes records for names of very large numbers of government entities — as well as of other kinds of organizations, such as corporations, and individuals — of the U.S., Canada, the U.K., France, India, and many other nations. The file also includes many records for individual statutes.

Interesting post that focuses on law related authority records.

May 6, 2011

Building a better legal search engine, part 1: Searching the U.S. Code

Filed under: Law - Sources,Legal Informatics,Search Engines,Searching — Patrick Durusau @ 12:37 pm

Building a better legal search engine, part 1: Searching the U.S. Code

From the post:

As I mentioned last week, I’m excited to give a keynote in two weeks on Law and Computation at the University of Houston Law Center alongside Stephen Wolfram, Carl Malamud, Seth Chandler, and my buddy Dan from CLS. The first part in my blog series leading up to this talk will focus on indexing and searching the U.S. Code with structured, public domain data and open source software.

He closes with:

Stay tuned next week for the next part in the series. I’ll be using Apache Mahout to build an intelligent recommender system and cluster the sections of the Code.

It won’t pull the same audience share as the “Who shot J.R.?” episode of Dallas, but I have to admit I’m interested in the next part of this series. 😉

October 29, 2010

LII/Legal Information Institute

Filed under: Law - Sources,Legal Informatics — Patrick Durusau @ 6:05 am

LII/Legal Information Institute is an effort to make US and world law freely accessible.

Managed subject identity will be valuable in navigation of primary and secondary legal materials, binding of those materials to case specific content and mining of legal discovery materials.

For mapping primary legal materials, this is the place to start.

Questions:

  1. How would you manage subject identity to eliminate duplication in U.S. case research output?
  2. Is your test court or jurisdiction specific? Any thoughts on how to broaden that?
  3. Same questions but pick a non-U.S. jurisdiction.
  4. How would you manage subject identity with regard to statutory citations?
  5. Bonus Question: When a U.S. court says “in Brown” do they mean Brown vs. Bd. of Education or do they mean some other Brown case? Suggest some ways identify the “Brown” in question.

Please also consider contributing either funds or expertise to support this project.

« Newer Posts

Powered by WordPress