Creating repository for legal informatics stuff, part 2
prototyping some regex from xml machinery
adding readme
Gitignore for emacs autosave *~ and .pyc files.
Testing building regex parsing citations.
Starting the high level documentations
Tedium automation makefile

For cleaning the directory of temp files and such and more as the need arises.
Abbrev's for court docs

Found in the blue book. In the docstring for the module I tried to summarize what I read in the blue book about what should be done for abbrevations.
Enumeration and explanation of citation signals.

Signals give contextual info about the citation. Mainly whether it is a supporting or contradicting citation for the main proposition.
Decomposing signals
decomposing signals into logal files based on the BB rules.
updating comments to correct reference
adding order of signals

In accordance with BB rule 1.3
Add outline of Order of Authorities

In accordance with BB rule 1.4
updating src refs to be correct.
placeholder for parenthetical info
Starting the stub for us geographical abbrevations and such
parser generalization
cornell legal citation reference
Citation data from the cornell website.

With a parser that converts it to XML since, well, xml is usable in
any language.  I have a strong feeling that part of this project will
eventually be in C# or some other CLR language, hence the need for C#
serialization of data.