Hoekstra: Dataset: A Network Analysis of Dutch Regulations

Dr. Rinke Hoekstra of the Leibniz Center for Law has posted a dataset entitled A Network Analysis of Dutch Regulations.

Here is the description:

This fileset contains two networks (CSV files) of citations between Dutch regulations stored on the MetaLex Document Server, at the document level, and at the article level. We ran several network analysis measures over these networks (stored again in two CSV files) and provide two visualisations of the networks (size is PageRank, color is given by Module).

This is an accompaniment to a submission to the Network Analysis in Law workshop of ICAIL 2013.

Jaquith launches Open Virginia data portal, providing access to legal data

Waldo Jaquith today launched Open Virginia, an open data platform for the U.S. state of Virginia.

Open Virginia is built with the CKAN open source data portal software.

Here is a description of Open Virginia:

Open Virginia is an effort to document the open government data published about the Commonwealth of Virginia—APIs, bulk downloads, and links to third-party data sources that provide much-needed information about how our government works.

Open Virginia currently offers access to legal data, including:

• the state’s legislative code
• code sections affected by bills 2006-
• a list of Virginia Court of Appeals decisions that cite a given law
• data on members of the state legislature

HT @shevski

Bulk Access to Law-Related Linked Data: LC & VIAF Name Authority Records and LC Subject Authority Records

Linked Data versions of Library of Congress name authority records and subject authority records are now available for bulk download from the Library of Congress Linked Data Service, according to Kevin Ford at Library of Congress.

In addition, VIAF, the Virtual International Authority File, now provides bulk access to Linked Data versions of name authority records for organizations, including government entities and business organizations, from more than 30 national or research libraries. VIAF data are also searchable through the VIAF Web user interface.

Together, these services provide bulk access to Linked Data versions of a very large number of authority records for names of government entities in many countries–names which play a prominent role in many kinds of legal data. Moreover, the Library of Congress Subject Authority records service provides access to a very large set of Linked Data versions of records for legal subjects from many different legal systems; the coverage provided by those records varies from legal system to legal system, but is often very broad and is in some instances comprehensive.

These Linked Data resources can be downloaded and incorporated into new or existing legal information systems that employ Linked Data technology. In addition, because each authority record in these data sets contains a unique URI and is publicly accessible on the Web, legal information systems that employ Linked Data technology can link out to relevant authority records at VIAF or the Library of Congress, as part of the development of the legal portion of the Semantic Web.

Click here for a list of additional law-related Linked Data resources.

HT @3windmills here and here

Colorado and Baltimore statutory codes posted free on the Web

The Colorado statutory code and the Baltimore, Maryland statutory code have been posted free on the Web by Public.Resource.Org.

Public.Resource.Org appears to be communicating with entities that assert copyright in those codes, about whether those entities will take legal action to prevent posting of those codes on the free Web and the use of those codes by developers to create new information resources.

HT @carlmalamud here and here

Ford: Law Classification Added to Library of Congress Linked Data Service

Kevin Ford of the Library of Congress has posted Law Classification Added to Library of Congress Linked Data Service, at In Custodia Legis.

Here are excerpts from the post:

The Library of Congress is pleased to make the K Class – Law Classification – and all its subclasses available as linked data from the LC Linked Data Service, ID.LOC.GOV. K Class joins the B, N, M, and Z Classes, which have been in beta release since June 2012. With about 2.2 million new resources added to ID.LOC.GOV, K Class is nearly eight times larger than the B, M, N, and Z Classes combined.[...]

Please explore the K Class for yourself at http://id.loc.gov/authorities/classification/K or all of the classes at http://id.loc.gov/authorities/classification. [...]

As always, your feedback is important and welcomed. [...] we are particularly interested in how the data available from ID.LOC.GOV is used and continue to encourage the submission of use cases describing how the community would like to apply or repurpose the LCC data. [...]

For more details, please see the complete post.

Click here for other law-related Linked Data resources.

HT @atweber

Freeing the DC Code: An Update

There have been several developments in recent weeks in the effort to make the District of Columbia statutory code freely available.

The project began in February 2013 when Tom MacWright posted You Cannot Have the DC Code, complaining that no free and open version of the DC Code was available for developers or the public to use.

Discussion then occurred regarding how to make the DC Code publicly available online in a version that was free of copyright.

In March 2013, Public.Resource.Org posted a digital version of the DC Code.

Last week, the DC Council said that they would not sue Public.Resource.Org for copyright infringement for posting a digital version of the code.

This week, the DC Council posted an unofficial digital version of the DC Code, licensed with the Creative Commons CC0 license.

This week it was announced that a hackathon to hack the DC Code will be held on 14 April 2013: Open DC Code Hackathon, in Washington, DC.

Click here for archived Twitter tweets from the Open DC Hackathon 2013, in .cvs format.

The Twitter hashtag for the Open DC Code Hackathon 2013 was #openlawdc

IRC discussion during the Open DC Code Hackathon 2013 occurred on Freenode under #openlawdc

Among the notable aspects of this project are that it demonstrates how members of the legal informatics and open-government-data communities can use the Internet to coordinate their efforts to make legal data publicly available, address challenging policy issues, and realize several of the principles of the open government data movement.

Here are selected articles and posts about the effort to make the DC Code publicly available on the Web and free of copyright restrictions:

• Tom MacWright: DC’s laws aren’t yours
• Cory Doctorow: Municipal codes of DC, free for all — liberated without permission
• Waldo Jaquith: Washington D.C. and the Work Ahead
• Steve Schultze: The District of Columbia Claims Copyright on the Law
• Martin Austermuhle: Breaking the Law to Publish the Law: Open Government Advocate Digitizes Entirety of D.C. Code
• Tom MacWright: The Open Code
• Tom Lee: The D.C. Code is Open–Come Hack on It!
• Dr. Joshua Tauberer: DC opens its “code”, embracing principles of open laws

For additional news about development of the Open DC Code, please see the comments to this post.

Thanks to Eric Mill and the members of the Legal Informatics Research Network for helping to gather the sources cited in this post.

CanLII launches API

Colin Lachance of the Canadian Legal Information Institute (CanLII) tells us that CanLII, which provides free access to Canadian law, has opened an application programming interface (API).

A description appears below.

Colin has a new post at Slaw.ca that provides context for the API launch: Unbundling legal information.

Description of CanLII API:

This document describes the specifications of the CanLII API. The API provides over a million court judgments, tens of thousands of statutes and regulations and covers all the major courts and legislatures, as well as over 150 specialized courts and tribunals.

How it works

Let’s dig into the more technical information:

- The technical guidelines provide details about encoding, formats, error management and content negotiation.
- The technical guideline will give you detailed information on how to develop your client and interact with the API.

Supported Resources:

Currently, the API supports following services:

Legislation browse: Regulations and statutes from all Canadian federal, provincial and territorial jurisdictions,
Case browse: Judgments from all courts and tribunals accessible on CanLII.

On top of the complete documentation, you can also access directly to the content of the API thanks to the I/O Docs module. [...]

For the API key and for other details, please see the description.

HT @sglassmeyer

Glassmeyer: Electronic Legal Copyright, Citation, and Preservation Information Integrated with Open States Legislative Data Report Card

Sarah Glassmeyer, JD, MLS, of CALI, has posted a spreadsheet that integrates the Open States Open Legislative Data Report Card ratings with the National Inventory of Legal Materials (NILM).

The NILM, compiled by the American Association of Law Libraries, lists data about each U.S. state’s online legal materials regarding copyright assertion, authentication, preservation, official status, permanent public access, uniform citation, and enactment of the Uniform Electronic Legal Material Act.

For more information on the NILM, please see:

• Emily Feltren‘s December 2012 AALL Washington Blawg post, Update on the National Inventory of Legal Materials
• Emily Feltren and Tina S. Ching‘s February 2012 VoxPopuLII post, Protecting Access One Entry at a Time: An Update on the National Inventory of Legal Materials.

HT @sglassmeyer

Lissner and Carver on CourtListener: Where we are and where we’d like to go

Michael Lissner and Professor Dr. Brian Carver of University of California, Berkeley, have posted CourtListener: Where we are and where we’d like to go, at VoxPopuLII.

Here is an excerpt:

At CourtListener, we are making a free database of court opinions with the ultimate goal of providing the entire U.S. case-law corpus to the world for free and combining it with cutting-edge search and research tools. We–like most readers of this blog–believe that for justice to truly prevail, the law must be open and equally accessible to everybody.

It is astonishing to think that the entire U.S. case-law corpus is not currently available to the world at no cost. Many have started down this path and stopped, so we know we’ve set a high goal for a humble open source project. From time to time it’s worth taking a moment to reflect on where we are and where we’d like to go in the coming years. [...]

The post discusses the development and current technology of CourtListener, which includes email alerts of new cases, automatic identification and cross-linking of citations, a set of scrapers called Juriscraper for gathering court decisions from court Websites, and bulk access to court decisions in XML.

The post also describes future plans for development, which include:

adding oral argument audio, case briefs, and data from PACER. Adding these new types of information to CourtListener is a must if we want to be more useful for research purposes, but doing so is a long-term goal, given the complexity of doing them well.

We also plan to build an opinion classifier that could automatically, and without human intervention, determine the subsequent treatment of opinions. Done right, this would allow our users to know at a glance if the opinion they’re reading was subsequently followed, criticized, or overruled, making our system even more valuable to our users. [...] You can see our plans on our feature tracker, our bugs in our bug tracker, and can get in touch in our forum.

For more details, please see the complete post.

HT @caminick

Strause et al.: How Federal Statutes Are Named, and the Yale Database of Federal Statute Names

Renata E.B. Strause of Yale Law School, and colleagues, have published How Federal Statutes Are Named, Law Library Journal, 105, 7-30 (2013).

Here is a summary of the article:

The naming of [U.S.] federal statutes for individuals has received surprisingly little systematic attention. The purposes of this article are to trace the history of federal statutory naming conventions and to identify as authoritatively and as completely as possible the persons and political issues Congress has decided to honor or highlight in this fashion, as well as the proliferation of abbreviations as a further shortening of the short title.

In their research the authors used the Yale Law School Library’s Database of Federal Statute Names.

Jason Eiseman of the Yale Law School Library told us that, according to Strause et al. (2013), page 12, a key source of data for the Database of Federal Statute Names was the U.S. House of Representatives’ Office of the Law Revision Counsel’s Table of Popular Names (HT also Thom Neale of the Sunlight Foundation).

Other sources of popular name data for U.S. federal statutes include:

• The Legal Information Institute’s Table of Popular Names, developed by LII Director Tom Bruce
• the united states GitHub repository’s Bill Nicknames database, created by Eric Mill of the Sunlight Foundation
• THOMAS’s List of Bill Popular and Short Titles (HT Daniel Schuman of the Sunlight Foundation)
• Professor Richard Leiter of the University of Nebraska and Adrian White‘s Concordance of Federal Legislation (HT Richard Leiter)

Stephane Cottin of Secrétariat général du Gouvernement and ADIJ tells us that Legifrance publishes a similar list of popular names for French statutes, the Lois Dites….

The Yale Database of Federal Statute Names includes the following fields:

• Popular Name Statutized?:
• Type:
• Date Enacted:
• Short Title:
• Public Law citation:
• Statute At Large citation:
• Named For?:
• Link/Source:
• Notes:

According to Jason, the library does not currently provide an API or bulk access to the database, but is considering providing them in the future.

HT @maricheney and @jeiseman here and here, and the members of the Legal Informatics Research Network