But I felt that I hadn’t captured its true spirit: the organization, the attention to detail.

So I went back on the 17th to document what I had missed:

Proposed Q&A site for lawyers, law librarians, law students, and others searching for primary sources, other than at the “big two”.

Stack Exchange

About me: I have a track record of making innovative, public service apps for attorneys and law students. I’ve also got years of Linux and Java development experience, and will be able to hit the ground running.

Here are some links to show that I’m serious about following through:

Screenshots of iPhone legal app

My biggest web app

Press I’ve received

My personal home page

(Originally posted on under my id dogweather on reddit)

He replied a few minutes later: the link wouldn’t work.  They never do; they expire after 10 minutes or so.  And so what happens?  Attorneys print out or create PDFs of the USPTO web pages in order to discuss them.

I immediately thought that there must be something that could be done here, and so I started the Trademark Permalink project:

Create links that don’t expire to trademarks at the U.S. Patent & Trademark Office. Use them in emails, on your website, or anywhere else you want to point someone to a trade/service-mark registration.

EDIT:

The story’s gotten a little more complicated:  In the past day or so, I discovered that it’s possible that my work might be superfluous: The “TARR” USPTO web app provides single-document retrieval via URLs that don’t time out.  Many (most?) practitioners seem to only know about the TESS service, though, which *does* time out.  Also, the TARR data seems to come from a different source, and is definitely a different format.  For example, the IBM registration I use as an example:

http://tarr.uspto.gov/servlet/tarr?regser=serial&entry=75871833

CivicApps.org in a nutshell

Back in the old days, i.e. 2008, cities like Portland would create apps (interactive websites) for us like this:

The old way of making apps

They’d get a team together, look at the Datasets available to it, come up with ideas, and then build the apps.  PortlandMaps, an awesome web app, was made this way.  But there’s a new trend and Portland’s setting an example for other cities.  First, the city adopts a policy of transparency, publishing all of its raw data in addition to the finished apps:

First, cities make their raw data available

Then, curious and entrepreneurial individuals, companies, and other organizations step in and independently create new apps.  This frees up city resources and results in more apps and services coming online:

Then, 3rd parties can step in and contribute

This is the entire purpose of the CivicApps.org project and website: to enable this creative environment.  By the way, this is the same idea behind the federal Data.gov project.

My idea: we can contribute data too

It occurred to me that many organizations have valuable data about the city.  And some even have the expertise to publish the data in “open formats” just like the city of Portland is doing:

My idea: We can provide datasets too

For example, my project, OregonLaws.org, publishes a glossary of legal terms specific to Oregon.  This is already up and running as a Dataset.

It will, though, take some work to implement my idea.  Some questions to answer are;  How will these 3rd party Datasets be integrated into the palette of “official” ones?  How will the data be authenticated or verified?

The near future

The end result of all this is that the city could become a nexus of information.  In addition to providing raw data about itself, it can act as a means of identification and authentication. There’s a precedent for the government acting in this role, e.g. the Secretary of State’s business registry performs a similar service.

Update

Oregon Business Magazine covered the CivicApps contest:  Keeping PDX a Hot Spot for App Development

I’m releasing a new open source library, HTTP-Assertions, that I use behind the scenes at OregonLaws.org.  It helps me keep the server running smoothly and make sure that my changes to the config files haven’t introduced new bugs.

It introduces these new assert methods to the Rails testing environment:

  assert_200
  assert_forbidden
  assert_temp_redirect_to
  assert_perm_redirect_to

Here’s an example:

  assert_200('https://www.oregonlaws.org/ors/161.360')

See the README on github for more details.

The Robb Report, of course, is “The Global Luxury Source”.  They’re a reliable destination for Rolls-Royce reviews.  We can all probably agree that my blog and the Robb Report travel in different circles.

I’ve known about the magazine for years, most likely from seeing it in doctors’ waiting rooms.  And when choosing this name for my blog, one of my reasons was the humor arising from the contrast of the two Robb Reports, for those who are familiar with the senior mark holder.

But I wonder, (1) is what I’m doing ethical? And (2) am I infringing on Robb Report’s mark?

I’ll think about these more after this never-ending final exam period is over.

Basically, software should be held to the same standards we have for people, especially in the field of law. Here’s what that might look like. This is, again, the “development” interface… an end-user would see something much fancier:

>> Abbreviation.abbreviate 'Chief Justice'
=> "C.J."
>> Abbreviation.rule
=> "Appendix 3"

It’s a start.

As far as the technical implementation, I’ve been considering rule-based systems, prolog-based systems and object-oriented decomposition.

>> Abbreviation.abbreviate 'Advance'

=> "Adv."

>> Abbreviation.abbreviate 'Advanced'

=> "Adv."

>> Abbreviation.abbreviate 'Advancing'

=> "Advancing"

So, this has been pretty interesting. Now I need to handle plurals well. This, though, means I’ll have to be able to identify plurals… but I have a couple of good ideas about how to do this.