Waldo Jaquith
Waldo Jaquith
I've retitled this from "Reconsider how to store new editions of laws" to "Improve the efficiency of how we store multiple copies of laws," because it's more understandable.
This is known as "recodification." It does happen, although not often. We've got a whole separate issue about that (#301), because it's definitely a thing that ought to be dealt...
You're working with codes that are updated frequently, while I'm not—if you don't think that this is a necessity right now, I'm not going to argue. :)
This has some non-trivial dependencies (recognizing subsection identifiers _in situ_ not the least of them) combined with being not a wildly exciting feature, so I'm moving it beyond v1.0.
I'm afraid that I just get a 500 error for that link. (Oh, American Legal.) Could you just give me a citation, so I can browse to it, since apparently...
So what's the problem with representing § 1 alongside § 1.1, § 1.2, etc., in the normal manner? Is it that § 1.1 lacks the context of being an implicit...
Well, there's American Legal's data format, there's American Legal's web-based representation of that data, and then there's how the data is _actually_ represented within the text of the law. I...
:) I really have found that bad online representations of laws can create real confusion, confusion that can be resolved easily by looking at the print version. I hope that...
@krues8dr, have you found anything more about this?