I work with people from around the world on matters relating to legal informatics. One common issue we constantly face is the issue of terminology. We use many of the same terms, but the subtly of their definitions end up causing no end of confusion. To try and address this problem, I’ve proposed a number of times that we band together to define a common vocabulary, and when we can’t arrive at that, at least we can understand the differences that exist amongst us.
To get the ball rolling, I have started a wiki on GitHub and populated it with many of the terms I use in my various roles. Their definitions are a work-in-progress at this point. I am refining them as I find the time. However, rather than trying to build my own private vocabulary, I would like this to be a collaborative effort. To that end, I am inviting anyone with an interest in this to help build out the vocabulary by adding your own terms with definitions to the list and improving the ones I have started.
My legal informatics glossary of terms can be found in my public legal Informatics project at:
The wiki is a public project on GitHub. Right now, anyone can contribute. We’ll see how well this model works out. In order to contribute, you need to sign up for a free GitHub account and to master the basics of GitHub. For the purposes of managing a vocabulary, it’s quite simple. You will need to understand the markdown format of the text file that is behind the list. The builtin editor in GitHub makes editing the markdown quite simple. If you are so inclined, you can learn more about markdown at http://daringfireball.net/projects/markdown/syntax. GitHub will take care of all the versioning issues so feel free to edit the terminology file.
Eventually I would like to gather enough terms that common terms or clusters of terms can be identified. This will allow us to develop clearer and more understandable standards, tools, and documentation in the emerging areas of legal informatics.