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

June 1, 2013

6 Goals for Public Access to Case Law

Filed under: Law,Law - Sources,Legal Informatics — Patrick Durusau @ 3:30 pm

6 Goals for Public Access to Case Law by Daniel Lewis and Nik Reed.

From the post:

In March, Mike Lissner wrote for this blog about the troubling state of access to case law – noting with dismay that most of the US corpus is not publicly available. While a few states make official cases available, most still do not, and neither does the federal government. At Ravel Law we’re building a new legal research platform and, like Mike, we’ve spent substantial time troubleshooting access to law issues. Here, we will provide some more detail about how official case law is created and share our recommendations for making it more available and usable. We focus in particular on FDsys – the federal judiciary’s effort in this space – but the ideas apply broadly.

(…)

Goal

Metrics

1. Comprehensive Access to Opinions – Does every federal court release every published and unpublished opinion?
– Are the electronic records comprehensive in their historic reach?
2. Opinions that can be Cited in Court – Are the official versions of cases provided, not just the slip opinions?
– And/or, can the version released by FDsys be cited in court?
3. Vendor-Neutral Citations – Are the opinions provided with a vendor-neutral citation (using, e.g., paragraph numbers)?
4. Opinions in File Formats that Enable Innovation – Are opinions provided in both human and machine-readable formats?
5. Opinions Marked with Meta-Data – Is a machine-readable language such as XML used to tag information like case date, title, citation, etc?
– Is additional markup of information such as sectional breaks, concurrences, etc. provided?
6. Bulk Access to Opinions – Are cases accessible via bulk access methods such as FTP or an API?

OK, but with the exception of bulk access, all of these issues have been solved (past tense) by commercial vendors.

Even bulk access is probably available if you are willing to pay the vendors enough.

But public access does not mean meaningful access.

For example, the goals mentioned above would not enable the average citizen to:

Which experts appear on behalf of which parties, consistently?

Which attorneys appear before particular judges?

What is a judge’s history with particular types of lawsuits?

What are the judge’s past connections with parties or attorneys?

To say nothing of what are the laws, facts, issues and other matters in a case, which are subject to varying identifications?

Public access to case law is a good goal, but not if it only eases the financial burden for existing legal publishers.

And does not provide the public with meaningful access to case law.

An introduction to Emacs Lisp

Filed under: Authoring Topic Maps,Editor,Lisp — Patrick Durusau @ 10:30 am

An introduction to Emacs Lisp by Christian Johansen.

From the webpage:

As a long-time passionate Emacs user, I’ve been curious about Lisp in general and Emacs Lisp in particular for quite some time. Until recently I had not written any Lisp apart from my .emacs.d setup, despite having read both An introduction to programming in Emacs Lisp and The Little Schemer last summer. A year later, I have finally written some Lisp, and I thought I’d share the code as an introduction to others out there curious about Lisp and extending Emacs.

(…)

The Task

The task I set out to solve was to make Emacs slightly more intelligent when working with tests written in Buster.JS, which is a test framework for JavaScript I’m working on with August Lilleaas. In particular I wanted Emacs to help me with Buster’s concept of deferred tests.

Yesterday a graph programmer suggested to me some people program in Lisp and but the whole world uses Java.

Of course, most of the world is functionally illiterate too but I don’t take that as an argument for illiteracy.

Not to cast aspersions on Java, a great deal of excellent work is done in Java. (See the many Apache projects that use Java.)

But counting noses is a lemming measure, which is not related the pros or cons of any particular language.

What topic map authoring tasks would you extend Emacs to facilitate?

I first saw this in Christophe Lalanne’s A bag of tweets / May 2013.

A Trillion Dollar Math Trick

Filed under: Column-Oriented,Columnar Database,Data Structures,Database — Patrick Durusau @ 10:03 am

A Trillion Dollar Math Trick by Dick Lipton.

Dick reviews a presentation by Mike Stonebraker at TTI Vanguard meeting on “Ginormous Systems” in DC.

In part:

In Mike’s wonderful talk he made seven points about the past, present, and the future of database technology. He has a great track record, so likely he is mostly right on his guesses. One of his predictions was about a way of re-organizing databases that has several remarkable properties:

  • It speeds up database operations 50x. That is to say, on typical queries—ones that companies actually do—it is fifty times faster than classical database implementations. As a theorist we like speedups, especially asymptotic ones. But 50x is pretty cool. That is enough to change a query from an hour to a minute.
  • It is not a new idea. But the time is finally right, and Mike predicts that future databases will use this method.
  • It is an idea that no one seems to know who invented it. I asked Mike, I asked other experts at the conference, and all shrugged and said effectively: “I have no idea.” Curious.

Let’s look quickly at the way databases work, and then consider the trick.

I won’t spoil the surprise for you, see Dick’s post for the details.

BTW, read the comments on historical uses of the same idea.

Then think about how to apply to topic maps.

I first saw this in Christophe Lalanne’s A bag of tweets / May 2013.

SGIKDD explorations December 2012

Filed under: BigData,Data Mining,Graphs,Knowledge Discovery,Tweets — Patrick Durusau @ 9:29 am

SGIKDD explorations December 2012

The hard copy of SIGKDD explorations arrived in the last week.

Comments to follow on several of the articles but if you are not a regular SIGKDD explorations reader, this issue may convince you to change.

Quick peek:

  • War stories from Twitter (Would you believe semantic issues persist in modern IT organizations?)
  • Analyzing heterogeneous networks (Heterogeneity, everybody talks about it….)
  • “Big Graph” (Will “Big Graph” replace “Big Data?”)
  • Mining large data streams (Will “Big Streams” replace “Big Graph?”)

Along with the current state of Big Data mining, its future and other goodies.

Posts will follow on some of the articles but I wanted to give you a head’s up.

The hard copy?

I read it while our chickens are in the yard.

Local ordinance prohibits unleashed chickens on the street so I have to keep them in the yard.

« Newer Posts

Powered by WordPress