├── .gitignore ├── California.md ├── Delaware.md ├── Florida.md ├── Illinois.md ├── LICENSE ├── Louisana.md ├── Maryland.md ├── Michigan.md ├── New York.md ├── Ohio.md ├── Oklahoma.md ├── Oregon.md ├── Pennsylvania.md ├── README.md ├── Texas.md ├── Virginia.md ├── Washington-DC.md ├── Washington.md └── Wyoming.md /.gitignore: -------------------------------------------------------------------------------- 1 | .DS_Store -------------------------------------------------------------------------------- /California.md: -------------------------------------------------------------------------------- 1 | California doesn't have unique section identifiers—the portion of the code (e.g., "Penal Code") must be specified prior to the section identifier in order to make a match. That is to say that same section numbers are reused in multiple "Codes," so knowing "section 8001" doesn't tell you much. 2 | 3 | Some laws are "laws," and some are "acts." There appears to be no difference. Section identifiers may end with letters, leading to the practice of writing "subdivision" between the cited section and the subsection, since 501b could be a law or it could be a subsection. 4 | 5 | Here are some of the ways that sections are cited within California Supreme Court decisions: 6 | 7 | * Penal Code section 1538.5 8 | * Code of Civil Procedure sections 377.20, 377.30, and 377.34 9 | * section 1237.5 10 | * sections 667.61, 12022 and 12022.3 11 | * § 1203 12 | * §6601.3 13 | * §§ 1025, 1158 14 | 15 | Those section identifiers lacking "Code" prefixes are within passages in which it is either stated explicitly at the outset which code they refer to (e.g. "all further statutory references are to the Penal Code unless otherwise indicated"), while in other cases it would be clear to a reader, but not inferable via machine. 16 | 17 | Find citations: 18 | 19 | ``` 20 | (((([A-Za-z\s]*)\sCode\s)([A-Za-z\s]*))?)(§|section|sections)(\s?)([0-9]{1})([0-9a-z\.]*) 21 | ``` 22 | -------------------------------------------------------------------------------- /Delaware.md: -------------------------------------------------------------------------------- 1 | Examples of how they appear within the code: 2 | 3 | * § 1410 4 | * § 6502 5 | 6 | Section numbers are not unique, but repeat for each title. The first two digits are the chapter number, they start at “01” (e.g., 1401). Because chapters start at 1, this means that section numbers can be 3–4 digits long. 7 | 8 | In court decisions, they are cited as such: 9 | 10 | * Del. Code Ann. tit. 18, § 6502 11 | 12 | Court PCRE: 13 | 14 | ``` 15 | Del.\sCode\sAnn.\stit.\s([0-9]{1,2}),\s§\s([0-9]{3,4}) 16 | ``` 17 | 18 | Code PCRE: 19 | 20 | ``` 21 | §\s([0-9]{3,4}) 22 | ``` 23 | -------------------------------------------------------------------------------- /Florida.md: -------------------------------------------------------------------------------- 1 | ``` 2 | s\.\s([0-9]{1,4})\.([0-9]{2,5}) 3 | ``` 4 | 5 | This is already in use in on [Sunshine Statutes](http://www.sunshinestatutes.com/), with great success. It may be employed without the `s\.\s` prefix, with risk of overmatching any time a decimal-bearing number is found within text. 6 | -------------------------------------------------------------------------------- /Illinois.md: -------------------------------------------------------------------------------- 1 | * 5 ILCS 170/01 2 | * 5 ILCS 170/1 3 | * 5 ILCS 220/3.2 4 | * 750 ILCS 36/209 5 | 6 | Chapters (the first segment) are 1–3 digits. ILCS always appears as the second segment. The third segment is 1–3 digits. And the final segment is 1–3 digits, plus an optional decimal. 7 | 8 | ``` 9 | ([0-9]{1,3})\sILCS\s([0-9]{1,3})\/([0-9\.]{1,3}) 10 | ``` 11 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Copyright 2012 by the contributors. 2 | 3 | 4 | GNU GENERAL PUBLIC LICENSE 5 | Version 3, 29 June 2007 6 | 7 | Copyright (C) 2007 Free Software Foundation, Inc. 8 | Everyone is permitted to copy and distribute verbatim copies 9 | of this license document, but changing it is not allowed. 10 | 11 | Preamble 12 | 13 | The GNU General Public License is a free, copyleft license for 14 | software and other kinds of works. 15 | 16 | The licenses for most software and other practical works are designed 17 | to take away your freedom to share and change the works. By contrast, 18 | the GNU General Public License is intended to guarantee your freedom to 19 | share and change all versions of a program--to make sure it remains free 20 | software for all its users. We, the Free Software Foundation, use the 21 | GNU General Public License for most of our software; it applies also to 22 | any other work released this way by its authors. You can apply it to 23 | your programs, too. 24 | 25 | When we speak of free software, we are referring to freedom, not 26 | price. Our General Public Licenses are designed to make sure that you 27 | have the freedom to distribute copies of free software (and charge for 28 | them if you wish), that you receive source code or can get it if you 29 | want it, that you can change the software or use pieces of it in new 30 | free programs, and that you know you can do these things. 31 | 32 | To protect your rights, we need to prevent others from denying you 33 | these rights or asking you to surrender the rights. Therefore, you have 34 | certain responsibilities if you distribute copies of the software, or if 35 | you modify it: responsibilities to respect the freedom of others. 36 | 37 | For example, if you distribute copies of such a program, whether 38 | gratis or for a fee, you must pass on to the recipients the same 39 | freedoms that you received. You must make sure that they, too, receive 40 | or can get the source code. And you must show them these terms so they 41 | know their rights. 42 | 43 | Developers that use the GNU GPL protect your rights with two steps: 44 | (1) assert copyright on the software, and (2) offer you this License 45 | giving you legal permission to copy, distribute and/or modify it. 46 | 47 | For the developers' and authors' protection, the GPL clearly explains 48 | that there is no warranty for this free software. For both users' and 49 | authors' sake, the GPL requires that modified versions be marked as 50 | changed, so that their problems will not be attributed erroneously to 51 | authors of previous versions. 52 | 53 | Some devices are designed to deny users access to install or run 54 | modified versions of the software inside them, although the manufacturer 55 | can do so. This is fundamentally incompatible with the aim of 56 | protecting users' freedom to change the software. The systematic 57 | pattern of such abuse occurs in the area of products for individuals to 58 | use, which is precisely where it is most unacceptable. Therefore, we 59 | have designed this version of the GPL to prohibit the practice for those 60 | products. If such problems arise substantially in other domains, we 61 | stand ready to extend this provision to those domains in future versions 62 | of the GPL, as needed to protect the freedom of users. 63 | 64 | Finally, every program is threatened constantly by software patents. 65 | States should not allow patents to restrict development and use of 66 | software on general-purpose computers, but in those that do, we wish to 67 | avoid the special danger that patents applied to a free program could 68 | make it effectively proprietary. To prevent this, the GPL assures that 69 | patents cannot be used to render the program non-free. 70 | 71 | The precise terms and conditions for copying, distribution and 72 | modification follow. 73 | 74 | TERMS AND CONDITIONS 75 | 76 | 0. Definitions. 77 | 78 | "This License" refers to version 3 of the GNU General Public License. 79 | 80 | "Copyright" also means copyright-like laws that apply to other kinds of 81 | works, such as semiconductor masks. 82 | 83 | "The Program" refers to any copyrightable work licensed under this 84 | License. Each licensee is addressed as "you". "Licensees" and 85 | "recipients" may be individuals or organizations. 86 | 87 | To "modify" a work means to copy from or adapt all or part of the work 88 | in a fashion requiring copyright permission, other than the making of an 89 | exact copy. The resulting work is called a "modified version" of the 90 | earlier work or a work "based on" the earlier work. 91 | 92 | A "covered work" means either the unmodified Program or a work based 93 | on the Program. 94 | 95 | To "propagate" a work means to do anything with it that, without 96 | permission, would make you directly or secondarily liable for 97 | infringement under applicable copyright law, except executing it on a 98 | computer or modifying a private copy. Propagation includes copying, 99 | distribution (with or without modification), making available to the 100 | public, and in some countries other activities as well. 101 | 102 | To "convey" a work means any kind of propagation that enables other 103 | parties to make or receive copies. Mere interaction with a user through 104 | a computer network, with no transfer of a copy, is not conveying. 105 | 106 | An interactive user interface displays "Appropriate Legal Notices" 107 | to the extent that it includes a convenient and prominently visible 108 | feature that (1) displays an appropriate copyright notice, and (2) 109 | tells the user that there is no warranty for the work (except to the 110 | extent that warranties are provided), that licensees may convey the 111 | work under this License, and how to view a copy of this License. If 112 | the interface presents a list of user commands or options, such as a 113 | menu, a prominent item in the list meets this criterion. 114 | 115 | 1. Source Code. 116 | 117 | The "source code" for a work means the preferred form of the work 118 | for making modifications to it. "Object code" means any non-source 119 | form of a work. 120 | 121 | A "Standard Interface" means an interface that either is an official 122 | standard defined by a recognized standards body, or, in the case of 123 | interfaces specified for a particular programming language, one that 124 | is widely used among developers working in that language. 125 | 126 | The "System Libraries" of an executable work include anything, other 127 | than the work as a whole, that (a) is included in the normal form of 128 | packaging a Major Component, but which is not part of that Major 129 | Component, and (b) serves only to enable use of the work with that 130 | Major Component, or to implement a Standard Interface for which an 131 | implementation is available to the public in source code form. A 132 | "Major Component", in this context, means a major essential component 133 | (kernel, window system, and so on) of the specific operating system 134 | (if any) on which the executable work runs, or a compiler used to 135 | produce the work, or an object code interpreter used to run it. 136 | 137 | The "Corresponding Source" for a work in object code form means all 138 | the source code needed to generate, install, and (for an executable 139 | work) run the object code and to modify the work, including scripts to 140 | control those activities. However, it does not include the work's 141 | System Libraries, or general-purpose tools or generally available free 142 | programs which are used unmodified in performing those activities but 143 | which are not part of the work. For example, Corresponding Source 144 | includes interface definition files associated with source files for 145 | the work, and the source code for shared libraries and dynamically 146 | linked subprograms that the work is specifically designed to require, 147 | such as by intimate data communication or control flow between those 148 | subprograms and other parts of the work. 149 | 150 | The Corresponding Source need not include anything that users 151 | can regenerate automatically from other parts of the Corresponding 152 | Source. 153 | 154 | The Corresponding Source for a work in source code form is that 155 | same work. 156 | 157 | 2. Basic Permissions. 158 | 159 | All rights granted under this License are granted for the term of 160 | copyright on the Program, and are irrevocable provided the stated 161 | conditions are met. This License explicitly affirms your unlimited 162 | permission to run the unmodified Program. The output from running a 163 | covered work is covered by this License only if the output, given its 164 | content, constitutes a covered work. This License acknowledges your 165 | rights of fair use or other equivalent, as provided by copyright law. 166 | 167 | You may make, run and propagate covered works that you do not 168 | convey, without conditions so long as your license otherwise remains 169 | in force. You may convey covered works to others for the sole purpose 170 | of having them make modifications exclusively for you, or provide you 171 | with facilities for running those works, provided that you comply with 172 | the terms of this License in conveying all material for which you do 173 | not control copyright. Those thus making or running the covered works 174 | for you must do so exclusively on your behalf, under your direction 175 | and control, on terms that prohibit them from making any copies of 176 | your copyrighted material outside their relationship with you. 177 | 178 | Conveying under any other circumstances is permitted solely under 179 | the conditions stated below. Sublicensing is not allowed; section 10 180 | makes it unnecessary. 181 | 182 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 183 | 184 | No covered work shall be deemed part of an effective technological 185 | measure under any applicable law fulfilling obligations under article 186 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 187 | similar laws prohibiting or restricting circumvention of such 188 | measures. 189 | 190 | When you convey a covered work, you waive any legal power to forbid 191 | circumvention of technological measures to the extent such circumvention 192 | is effected by exercising rights under this License with respect to 193 | the covered work, and you disclaim any intention to limit operation or 194 | modification of the work as a means of enforcing, against the work's 195 | users, your or third parties' legal rights to forbid circumvention of 196 | technological measures. 197 | 198 | 4. Conveying Verbatim Copies. 199 | 200 | You may convey verbatim copies of the Program's source code as you 201 | receive it, in any medium, provided that you conspicuously and 202 | appropriately publish on each copy an appropriate copyright notice; 203 | keep intact all notices stating that this License and any 204 | non-permissive terms added in accord with section 7 apply to the code; 205 | keep intact all notices of the absence of any warranty; and give all 206 | recipients a copy of this License along with the Program. 207 | 208 | You may charge any price or no price for each copy that you convey, 209 | and you may offer support or warranty protection for a fee. 210 | 211 | 5. Conveying Modified Source Versions. 212 | 213 | You may convey a work based on the Program, or the modifications to 214 | produce it from the Program, in the form of source code under the 215 | terms of section 4, provided that you also meet all of these conditions: 216 | 217 | a) The work must carry prominent notices stating that you modified 218 | it, and giving a relevant date. 219 | 220 | b) The work must carry prominent notices stating that it is 221 | released under this License and any conditions added under section 222 | 7. This requirement modifies the requirement in section 4 to 223 | "keep intact all notices". 224 | 225 | c) You must license the entire work, as a whole, under this 226 | License to anyone who comes into possession of a copy. This 227 | License will therefore apply, along with any applicable section 7 228 | additional terms, to the whole of the work, and all its parts, 229 | regardless of how they are packaged. This License gives no 230 | permission to license the work in any other way, but it does not 231 | invalidate such permission if you have separately received it. 232 | 233 | d) If the work has interactive user interfaces, each must display 234 | Appropriate Legal Notices; however, if the Program has interactive 235 | interfaces that do not display Appropriate Legal Notices, your 236 | work need not make them do so. 237 | 238 | A compilation of a covered work with other separate and independent 239 | works, which are not by their nature extensions of the covered work, 240 | and which are not combined with it such as to form a larger program, 241 | in or on a volume of a storage or distribution medium, is called an 242 | "aggregate" if the compilation and its resulting copyright are not 243 | used to limit the access or legal rights of the compilation's users 244 | beyond what the individual works permit. Inclusion of a covered work 245 | in an aggregate does not cause this License to apply to the other 246 | parts of the aggregate. 247 | 248 | 6. Conveying Non-Source Forms. 249 | 250 | You may convey a covered work in object code form under the terms 251 | of sections 4 and 5, provided that you also convey the 252 | machine-readable Corresponding Source under the terms of this License, 253 | in one of these ways: 254 | 255 | a) Convey the object code in, or embodied in, a physical product 256 | (including a physical distribution medium), accompanied by the 257 | Corresponding Source fixed on a durable physical medium 258 | customarily used for software interchange. 259 | 260 | b) Convey the object code in, or embodied in, a physical product 261 | (including a physical distribution medium), accompanied by a 262 | written offer, valid for at least three years and valid for as 263 | long as you offer spare parts or customer support for that product 264 | model, to give anyone who possesses the object code either (1) a 265 | copy of the Corresponding Source for all the software in the 266 | product that is covered by this License, on a durable physical 267 | medium customarily used for software interchange, for a price no 268 | more than your reasonable cost of physically performing this 269 | conveying of source, or (2) access to copy the 270 | Corresponding Source from a network server at no charge. 271 | 272 | c) Convey individual copies of the object code with a copy of the 273 | written offer to provide the Corresponding Source. This 274 | alternative is allowed only occasionally and noncommercially, and 275 | only if you received the object code with such an offer, in accord 276 | with subsection 6b. 277 | 278 | d) Convey the object code by offering access from a designated 279 | place (gratis or for a charge), and offer equivalent access to the 280 | Corresponding Source in the same way through the same place at no 281 | further charge. You need not require recipients to copy the 282 | Corresponding Source along with the object code. If the place to 283 | copy the object code is a network server, the Corresponding Source 284 | may be on a different server (operated by you or a third party) 285 | that supports equivalent copying facilities, provided you maintain 286 | clear directions next to the object code saying where to find the 287 | Corresponding Source. Regardless of what server hosts the 288 | Corresponding Source, you remain obligated to ensure that it is 289 | available for as long as needed to satisfy these requirements. 290 | 291 | e) Convey the object code using peer-to-peer transmission, provided 292 | you inform other peers where the object code and Corresponding 293 | Source of the work are being offered to the general public at no 294 | charge under subsection 6d. 295 | 296 | A separable portion of the object code, whose source code is excluded 297 | from the Corresponding Source as a System Library, need not be 298 | included in conveying the object code work. 299 | 300 | A "User Product" is either (1) a "consumer product", which means any 301 | tangible personal property which is normally used for personal, family, 302 | or household purposes, or (2) anything designed or sold for incorporation 303 | into a dwelling. In determining whether a product is a consumer product, 304 | doubtful cases shall be resolved in favor of coverage. For a particular 305 | product received by a particular user, "normally used" refers to a 306 | typical or common use of that class of product, regardless of the status 307 | of the particular user or of the way in which the particular user 308 | actually uses, or expects or is expected to use, the product. A product 309 | is a consumer product regardless of whether the product has substantial 310 | commercial, industrial or non-consumer uses, unless such uses represent 311 | the only significant mode of use of the product. 312 | 313 | "Installation Information" for a User Product means any methods, 314 | procedures, authorization keys, or other information required to install 315 | and execute modified versions of a covered work in that User Product from 316 | a modified version of its Corresponding Source. The information must 317 | suffice to ensure that the continued functioning of the modified object 318 | code is in no case prevented or interfered with solely because 319 | modification has been made. 320 | 321 | If you convey an object code work under this section in, or with, or 322 | specifically for use in, a User Product, and the conveying occurs as 323 | part of a transaction in which the right of possession and use of the 324 | User Product is transferred to the recipient in perpetuity or for a 325 | fixed term (regardless of how the transaction is characterized), the 326 | Corresponding Source conveyed under this section must be accompanied 327 | by the Installation Information. But this requirement does not apply 328 | if neither you nor any third party retains the ability to install 329 | modified object code on the User Product (for example, the work has 330 | been installed in ROM). 331 | 332 | The requirement to provide Installation Information does not include a 333 | requirement to continue to provide support service, warranty, or updates 334 | for a work that has been modified or installed by the recipient, or for 335 | the User Product in which it has been modified or installed. Access to a 336 | network may be denied when the modification itself materially and 337 | adversely affects the operation of the network or violates the rules and 338 | protocols for communication across the network. 339 | 340 | Corresponding Source conveyed, and Installation Information provided, 341 | in accord with this section must be in a format that is publicly 342 | documented (and with an implementation available to the public in 343 | source code form), and must require no special password or key for 344 | unpacking, reading or copying. 345 | 346 | 7. Additional Terms. 347 | 348 | "Additional permissions" are terms that supplement the terms of this 349 | License by making exceptions from one or more of its conditions. 350 | Additional permissions that are applicable to the entire Program shall 351 | be treated as though they were included in this License, to the extent 352 | that they are valid under applicable law. If additional permissions 353 | apply only to part of the Program, that part may be used separately 354 | under those permissions, but the entire Program remains governed by 355 | this License without regard to the additional permissions. 356 | 357 | When you convey a copy of a covered work, you may at your option 358 | remove any additional permissions from that copy, or from any part of 359 | it. (Additional permissions may be written to require their own 360 | removal in certain cases when you modify the work.) You may place 361 | additional permissions on material, added by you to a covered work, 362 | for which you have or can give appropriate copyright permission. 363 | 364 | Notwithstanding any other provision of this License, for material you 365 | add to a covered work, you may (if authorized by the copyright holders of 366 | that material) supplement the terms of this License with terms: 367 | 368 | a) Disclaiming warranty or limiting liability differently from the 369 | terms of sections 15 and 16 of this License; or 370 | 371 | b) Requiring preservation of specified reasonable legal notices or 372 | author attributions in that material or in the Appropriate Legal 373 | Notices displayed by works containing it; or 374 | 375 | c) Prohibiting misrepresentation of the origin of that material, or 376 | requiring that modified versions of such material be marked in 377 | reasonable ways as different from the original version; or 378 | 379 | d) Limiting the use for publicity purposes of names of licensors or 380 | authors of the material; or 381 | 382 | e) Declining to grant rights under trademark law for use of some 383 | trade names, trademarks, or service marks; or 384 | 385 | f) Requiring indemnification of licensors and authors of that 386 | material by anyone who conveys the material (or modified versions of 387 | it) with contractual assumptions of liability to the recipient, for 388 | any liability that these contractual assumptions directly impose on 389 | those licensors and authors. 390 | 391 | All other non-permissive additional terms are considered "further 392 | restrictions" within the meaning of section 10. If the Program as you 393 | received it, or any part of it, contains a notice stating that it is 394 | governed by this License along with a term that is a further 395 | restriction, you may remove that term. If a license document contains 396 | a further restriction but permits relicensing or conveying under this 397 | License, you may add to a covered work material governed by the terms 398 | of that license document, provided that the further restriction does 399 | not survive such relicensing or conveying. 400 | 401 | If you add terms to a covered work in accord with this section, you 402 | must place, in the relevant source files, a statement of the 403 | additional terms that apply to those files, or a notice indicating 404 | where to find the applicable terms. 405 | 406 | Additional terms, permissive or non-permissive, may be stated in the 407 | form of a separately written license, or stated as exceptions; 408 | the above requirements apply either way. 409 | 410 | 8. Termination. 411 | 412 | You may not propagate or modify a covered work except as expressly 413 | provided under this License. Any attempt otherwise to propagate or 414 | modify it is void, and will automatically terminate your rights under 415 | this License (including any patent licenses granted under the third 416 | paragraph of section 11). 417 | 418 | However, if you cease all violation of this License, then your 419 | license from a particular copyright holder is reinstated (a) 420 | provisionally, unless and until the copyright holder explicitly and 421 | finally terminates your license, and (b) permanently, if the copyright 422 | holder fails to notify you of the violation by some reasonable means 423 | prior to 60 days after the cessation. 424 | 425 | Moreover, your license from a particular copyright holder is 426 | reinstated permanently if the copyright holder notifies you of the 427 | violation by some reasonable means, this is the first time you have 428 | received notice of violation of this License (for any work) from that 429 | copyright holder, and you cure the violation prior to 30 days after 430 | your receipt of the notice. 431 | 432 | Termination of your rights under this section does not terminate the 433 | licenses of parties who have received copies or rights from you under 434 | this License. If your rights have been terminated and not permanently 435 | reinstated, you do not qualify to receive new licenses for the same 436 | material under section 10. 437 | 438 | 9. Acceptance Not Required for Having Copies. 439 | 440 | You are not required to accept this License in order to receive or 441 | run a copy of the Program. Ancillary propagation of a covered work 442 | occurring solely as a consequence of using peer-to-peer transmission 443 | to receive a copy likewise does not require acceptance. However, 444 | nothing other than this License grants you permission to propagate or 445 | modify any covered work. These actions infringe copyright if you do 446 | not accept this License. Therefore, by modifying or propagating a 447 | covered work, you indicate your acceptance of this License to do so. 448 | 449 | 10. Automatic Licensing of Downstream Recipients. 450 | 451 | Each time you convey a covered work, the recipient automatically 452 | receives a license from the original licensors, to run, modify and 453 | propagate that work, subject to this License. You are not responsible 454 | for enforcing compliance by third parties with this License. 455 | 456 | An "entity transaction" is a transaction transferring control of an 457 | organization, or substantially all assets of one, or subdividing an 458 | organization, or merging organizations. If propagation of a covered 459 | work results from an entity transaction, each party to that 460 | transaction who receives a copy of the work also receives whatever 461 | licenses to the work the party's predecessor in interest had or could 462 | give under the previous paragraph, plus a right to possession of the 463 | Corresponding Source of the work from the predecessor in interest, if 464 | the predecessor has it or can get it with reasonable efforts. 465 | 466 | You may not impose any further restrictions on the exercise of the 467 | rights granted or affirmed under this License. For example, you may 468 | not impose a license fee, royalty, or other charge for exercise of 469 | rights granted under this License, and you may not initiate litigation 470 | (including a cross-claim or counterclaim in a lawsuit) alleging that 471 | any patent claim is infringed by making, using, selling, offering for 472 | sale, or importing the Program or any portion of it. 473 | 474 | 11. Patents. 475 | 476 | A "contributor" is a copyright holder who authorizes use under this 477 | License of the Program or a work on which the Program is based. The 478 | work thus licensed is called the contributor's "contributor version". 479 | 480 | A contributor's "essential patent claims" are all patent claims 481 | owned or controlled by the contributor, whether already acquired or 482 | hereafter acquired, that would be infringed by some manner, permitted 483 | by this License, of making, using, or selling its contributor version, 484 | but do not include claims that would be infringed only as a 485 | consequence of further modification of the contributor version. For 486 | purposes of this definition, "control" includes the right to grant 487 | patent sublicenses in a manner consistent with the requirements of 488 | this License. 489 | 490 | Each contributor grants you a non-exclusive, worldwide, royalty-free 491 | patent license under the contributor's essential patent claims, to 492 | make, use, sell, offer for sale, import and otherwise run, modify and 493 | propagate the contents of its contributor version. 494 | 495 | In the following three paragraphs, a "patent license" is any express 496 | agreement or commitment, however denominated, not to enforce a patent 497 | (such as an express permission to practice a patent or covenant not to 498 | sue for patent infringement). To "grant" such a patent license to a 499 | party means to make such an agreement or commitment not to enforce a 500 | patent against the party. 501 | 502 | If you convey a covered work, knowingly relying on a patent license, 503 | and the Corresponding Source of the work is not available for anyone 504 | to copy, free of charge and under the terms of this License, through a 505 | publicly available network server or other readily accessible means, 506 | then you must either (1) cause the Corresponding Source to be so 507 | available, or (2) arrange to deprive yourself of the benefit of the 508 | patent license for this particular work, or (3) arrange, in a manner 509 | consistent with the requirements of this License, to extend the patent 510 | license to downstream recipients. "Knowingly relying" means you have 511 | actual knowledge that, but for the patent license, your conveying the 512 | covered work in a country, or your recipient's use of the covered work 513 | in a country, would infringe one or more identifiable patents in that 514 | country that you have reason to believe are valid. 515 | 516 | If, pursuant to or in connection with a single transaction or 517 | arrangement, you convey, or propagate by procuring conveyance of, a 518 | covered work, and grant a patent license to some of the parties 519 | receiving the covered work authorizing them to use, propagate, modify 520 | or convey a specific copy of the covered work, then the patent license 521 | you grant is automatically extended to all recipients of the covered 522 | work and works based on it. 523 | 524 | A patent license is "discriminatory" if it does not include within 525 | the scope of its coverage, prohibits the exercise of, or is 526 | conditioned on the non-exercise of one or more of the rights that are 527 | specifically granted under this License. You may not convey a covered 528 | work if you are a party to an arrangement with a third party that is 529 | in the business of distributing software, under which you make payment 530 | to the third party based on the extent of your activity of conveying 531 | the work, and under which the third party grants, to any of the 532 | parties who would receive the covered work from you, a discriminatory 533 | patent license (a) in connection with copies of the covered work 534 | conveyed by you (or copies made from those copies), or (b) primarily 535 | for and in connection with specific products or compilations that 536 | contain the covered work, unless you entered into that arrangement, 537 | or that patent license was granted, prior to 28 March 2007. 538 | 539 | Nothing in this License shall be construed as excluding or limiting 540 | any implied license or other defenses to infringement that may 541 | otherwise be available to you under applicable patent law. 542 | 543 | 12. No Surrender of Others' Freedom. 544 | 545 | If conditions are imposed on you (whether by court order, agreement or 546 | otherwise) that contradict the conditions of this License, they do not 547 | excuse you from the conditions of this License. If you cannot convey a 548 | covered work so as to satisfy simultaneously your obligations under this 549 | License and any other pertinent obligations, then as a consequence you may 550 | not convey it at all. For example, if you agree to terms that obligate you 551 | to collect a royalty for further conveying from those to whom you convey 552 | the Program, the only way you could satisfy both those terms and this 553 | License would be to refrain entirely from conveying the Program. 554 | 555 | 13. Use with the GNU Affero General Public License. 556 | 557 | Notwithstanding any other provision of this License, you have 558 | permission to link or combine any covered work with a work licensed 559 | under version 3 of the GNU Affero General Public License into a single 560 | combined work, and to convey the resulting work. The terms of this 561 | License will continue to apply to the part which is the covered work, 562 | but the special requirements of the GNU Affero General Public License, 563 | section 13, concerning interaction through a network will apply to the 564 | combination as such. 565 | 566 | 14. Revised Versions of this License. 567 | 568 | The Free Software Foundation may publish revised and/or new versions of 569 | the GNU General Public License from time to time. Such new versions will 570 | be similar in spirit to the present version, but may differ in detail to 571 | address new problems or concerns. 572 | 573 | Each version is given a distinguishing version number. If the 574 | Program specifies that a certain numbered version of the GNU General 575 | Public License "or any later version" applies to it, you have the 576 | option of following the terms and conditions either of that numbered 577 | version or of any later version published by the Free Software 578 | Foundation. If the Program does not specify a version number of the 579 | GNU General Public License, you may choose any version ever published 580 | by the Free Software Foundation. 581 | 582 | If the Program specifies that a proxy can decide which future 583 | versions of the GNU General Public License can be used, that proxy's 584 | public statement of acceptance of a version permanently authorizes you 585 | to choose that version for the Program. 586 | 587 | Later license versions may give you additional or different 588 | permissions. However, no additional obligations are imposed on any 589 | author or copyright holder as a result of your choosing to follow a 590 | later version. 591 | 592 | 15. Disclaimer of Warranty. 593 | 594 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 595 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 596 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 597 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 598 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 599 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 600 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 601 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 602 | 603 | 16. Limitation of Liability. 604 | 605 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 606 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 607 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 608 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 609 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 610 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 611 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 612 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 613 | SUCH DAMAGES. 614 | 615 | 17. Interpretation of Sections 15 and 16. 616 | 617 | If the disclaimer of warranty and limitation of liability provided 618 | above cannot be given local legal effect according to their terms, 619 | reviewing courts shall apply local law that most closely approximates 620 | an absolute waiver of all civil liability in connection with the 621 | Program, unless a warranty or assumption of liability accompanies a 622 | copy of the Program in return for a fee. 623 | 624 | END OF TERMS AND CONDITIONS 625 | 626 | How to Apply These Terms to Your New Programs 627 | 628 | If you develop a new program, and you want it to be of the greatest 629 | possible use to the public, the best way to achieve this is to make it 630 | free software which everyone can redistribute and change under these terms. 631 | 632 | To do so, attach the following notices to the program. It is safest 633 | to attach them to the start of each source file to most effectively 634 | state the exclusion of warranty; and each file should have at least 635 | the "copyright" line and a pointer to where the full notice is found. 636 | 637 | 638 | Copyright (C) 639 | 640 | This program is free software: you can redistribute it and/or modify 641 | it under the terms of the GNU General Public License as published by 642 | the Free Software Foundation, either version 3 of the License, or 643 | (at your option) any later version. 644 | 645 | This program is distributed in the hope that it will be useful, 646 | but WITHOUT ANY WARRANTY; without even the implied warranty of 647 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 648 | GNU General Public License for more details. 649 | 650 | You should have received a copy of the GNU General Public License 651 | along with this program. If not, see . 652 | 653 | Also add information on how to contact you by electronic and paper mail. 654 | 655 | If the program does terminal interaction, make it output a short 656 | notice like this when it starts in an interactive mode: 657 | 658 | SecureSmartCam Copyright (C) 2011, The Guardian Project & Witness 659 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 660 | This is free software, and you are welcome to redistribute it 661 | under certain conditions; type `show c' for details. 662 | 663 | The hypothetical commands `show w' and `show c' should show the appropriate 664 | parts of the General Public License. Of course, your program's commands 665 | might be different; for a GUI interface, you would use an "about box". 666 | 667 | You should also get your employer (if you work as a programmer) or school, 668 | if any, to sign a "copyright disclaimer" for the program, if necessary. 669 | For more information on this, and how to apply and follow the GNU GPL, see 670 | . 671 | 672 | The GNU General Public License does not permit incorporating your program 673 | into proprietary programs. If your program is a subroutine library, you 674 | may consider it more useful to permit linking proprietary applications with 675 | the library. If this is what you want to do, use the GNU Lesser General 676 | Public License instead of this License. But first, please read 677 | . 678 | 679 | 680 | 681 | The MIT License (MIT) 682 | Copyright (c) 683 | 684 | Permission is hereby granted, free of charge, to any person obtaining a copy of 685 | this software and associated documentation files (the "Software"), to deal in 686 | the Software without restriction, including without limitation the rights to 687 | use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of 688 | the Software, and to permit persons to whom the Software is furnished to do so, 689 | subject to the following conditions: 690 | 691 | The above copyright notice and this permission notice shall be included in all 692 | copies or substantial portions of the Software. 693 | 694 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 695 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS 696 | FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR 697 | COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER 698 | IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN 699 | CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. 700 | 701 | 702 | 703 | Apache License 704 | Version 2.0, January 2004 705 | http://www.apache.org/licenses/ 706 | 707 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 708 | 709 | 1. Definitions. 710 | 711 | "License" shall mean the terms and conditions for use, reproduction, and 712 | distribution as defined by Sections 1 through 9 of this document. 713 | 714 | "Licensor" shall mean the copyright owner or entity authorized by the copyright 715 | owner that is granting the License. 716 | 717 | "Legal Entity" shall mean the union of the acting entity and all other entities 718 | that control, are controlled by, or are under common control with that entity. 719 | For the purposes of this definition, "control" means (i) the power, direct or 720 | indirect, to cause the direction or management of such entity, whether by 721 | contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the 722 | outstanding shares, or (iii) beneficial ownership of such entity. 723 | 724 | "You" (or "Your") shall mean an individual or Legal Entity exercising 725 | permissions granted by this License. 726 | 727 | "Source" form shall mean the preferred form for making modifications, including 728 | but not limited to software source code, documentation source, and configuration 729 | files. 730 | 731 | "Object" form shall mean any form resulting from mechanical transformation or 732 | translation of a Source form, including but not limited to compiled object code, 733 | generated documentation, and conversions to other media types. 734 | 735 | "Work" shall mean the work of authorship, whether in Source or Object form, made 736 | available under the License, as indicated by a copyright notice that is included 737 | in or attached to the work (an example is provided in the Appendix below). 738 | 739 | "Derivative Works" shall mean any work, whether in Source or Object form, that 740 | is based on (or derived from) the Work and for which the editorial revisions, 741 | annotations, elaborations, or other modifications represent, as a whole, an 742 | original work of authorship. For the purposes of this License, Derivative Works 743 | shall not include works that remain separable from, or merely link (or bind by 744 | name) to the interfaces of, the Work and Derivative Works thereof. 745 | 746 | "Contribution" shall mean any work of authorship, including the original version 747 | of the Work and any modifications or additions to that Work or Derivative Works 748 | thereof, that is intentionally submitted to Licensor for inclusion in the Work 749 | by the copyright owner or by an individual or Legal Entity authorized to submit 750 | on behalf of the copyright owner. For the purposes of this definition, 751 | "submitted" means any form of electronic, verbal, or written communication sent 752 | to the Licensor or its representatives, including but not limited to 753 | communication on electronic mailing lists, source code control systems, and 754 | issue tracking systems that are managed by, or on behalf of, the Licensor for 755 | the purpose of discussing and improving the Work, but excluding communication 756 | that is conspicuously marked or otherwise designated in writing by the copyright 757 | owner as "Not a Contribution." 758 | 759 | "Contributor" shall mean Licensor and any individual or Legal Entity on behalf 760 | of whom a Contribution has been received by Licensor and subsequently 761 | incorporated within the Work. 762 | 763 | 2. Grant of Copyright License. Subject to the terms and conditions of this 764 | License, each Contributor hereby grants to You a perpetual, worldwide, 765 | non-exclusive, no-charge, royalty-free, irrevocable copyright license to 766 | reproduce, prepare Derivative Works of, publicly display, publicly perform, 767 | sublicense, and distribute the Work and such Derivative Works in Source or 768 | Object form. 769 | 770 | 3. Grant of Patent License. Subject to the terms and conditions of this License, 771 | each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, 772 | no-charge, royalty-free, irrevocable (except as stated in this section) patent 773 | license to make, have made, use, offer to sell, sell, import, and otherwise 774 | transfer the Work, where such license applies only to those patent claims 775 | licensable by such Contributor that are necessarily infringed by their 776 | Contribution(s) alone or by combination of their Contribution(s) with the Work 777 | to which such Contribution(s) was submitted. If You institute patent litigation 778 | against any entity (including a cross-claim or counterclaim in a lawsuit) 779 | alleging that the Work or a Contribution incorporated within the Work 780 | constitutes direct or contributory patent infringement, then any patent licenses 781 | granted to You under this License for that Work shall terminate as of the date 782 | such litigation is filed. 783 | 784 | 4. Redistribution. You may reproduce and distribute copies of the Work or 785 | Derivative Works thereof in any medium, with or without modifications, and in 786 | Source or Object form, provided that You meet the following conditions: 787 | 788 | You must give any other recipients of the Work or Derivative Works a copy of 789 | this License; and 790 | 791 | You must cause any modified files to carry prominent notices stating that You 792 | changed the files; and 793 | 794 | You must retain, in the Source form of any Derivative Works that You distribute, 795 | all copyright, patent, trademark, and attribution notices from the Source form 796 | of the Work, excluding those notices that do not pertain to any part of the 797 | Derivative Works; and 798 | 799 | If the Work includes a "NOTICE" text file as part of its distribution, then any 800 | Derivative Works that You distribute must include a readable copy of the 801 | attribution notices contained within such NOTICE file, excluding those notices 802 | that do not pertain to any part of the Derivative Works, in at least one of the 803 | following places: within a NOTICE text file distributed as part of the 804 | Derivative Works; within the Source form or documentation, if provided along 805 | with the Derivative Works; or, within a display generated by the Derivative 806 | Works, if and wherever such third-party notices normally appear. The contents of 807 | the NOTICE file are for informational purposes only and do not modify the 808 | License. You may add Your own attribution notices within Derivative Works that 809 | You distribute, alongside or as an addendum to the NOTICE text from the Work, 810 | provided that such additional attribution notices cannot be construed as 811 | modifying the License. You may add Your own copyright statement to Your 812 | modifications and may provide additional or different license terms and 813 | conditions for use, reproduction, or distribution of Your modifications, or for 814 | any such Derivative Works as a whole, provided Your use, reproduction, and 815 | distribution of the Work otherwise complies with the conditions stated in this 816 | License. 817 | 818 | 5. Submission of Contributions. Unless You explicitly state otherwise, any 819 | Contribution intentionally submitted for inclusion in the Work by You to the 820 | Licensor shall be under the terms and conditions of this License, without any 821 | additional terms or conditions. Notwithstanding the above, nothing herein shall 822 | supersede or modify the terms of any separate license agreement you may have 823 | executed with Licensor regarding such Contributions. 824 | 825 | 6. Trademarks. This License does not grant permission to use the trade names, 826 | trademarks, service marks, or product names of the Licensor, except as required 827 | for reasonable and customary use in describing the origin of the Work and 828 | reproducing the content of the NOTICE file. 829 | 830 | 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in 831 | writing, Licensor provides the Work (and each Contributor provides its 832 | Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY 833 | KIND, either express or implied, including, without limitation, any warranties 834 | or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 835 | PARTICULAR PURPOSE. You are solely responsible for determining the 836 | appropriateness of using or redistributing the Work and assume any risks 837 | associated with Your exercise of permissions under this License. 838 | 839 | 8. Limitation of Liability. In no event and under no legal theory, whether in 840 | tort (including negligence), contract, or otherwise, unless required by 841 | applicable law (such as deliberate and grossly negligent acts) or agreed to in 842 | writing, shall any Contributor be liable to You for damages, including any 843 | direct, indirect, special, incidental, or consequential damages of any character 844 | arising as a result of this License or out of the use or inability to use the 845 | Work (including but not limited to damages for loss of goodwill, work stoppage, 846 | computer failure or malfunction, or any and all other commercial damages or 847 | losses), even if such Contributor has been advised of the possibility of such 848 | damages. 849 | 850 | 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. 851 | -------------------------------------------------------------------------------- /Louisana.md: -------------------------------------------------------------------------------- 1 | Examples of how they appear within the code: 2 | 3 | * 1:16 4 | * 1:58.3 5 | * 2:131.1 6 | * 33:9681 7 | * 46:236.11.4 8 | * 47:287.663 9 | * 47:9081 10 | 11 | Often prefixed by "RS" or "R.S." 12 | 13 | ``` 14 | ((R(\.?)S(\.?)\s)?)([0-9]{1,2}):([0-9]{1,4})((\.[0-9]+)*) 15 | ``` 16 | 17 | May omit `((R(\.?)S(\.?)\s)?)` for broader matching with relatively high confidence that it will not result in overbroad matching. 18 | -------------------------------------------------------------------------------- /Maryland.md: -------------------------------------------------------------------------------- 1 | Example section numbers: 2 | 3 | * § 10A-101 4 | * § 5-7B-08 5 | * § 14-1012 6 | * § 14-102.1 7 | 8 | As used within citations within the code: 9 | 10 | * under § 2-205, § 4-205, or § 6-202 of this article 11 | * § 3-307 of the Criminal Law Article 12 | * § 5-202 of this subtitle 13 | * § 9-301 of the State Government Article 14 | * § 5-7B-03 of this subtitle 15 | * §§ 13-1101 and 13-1111 of the Financial Institutions Article 16 | * § 19-115 of this title 17 | 18 | As used within court decisions: 19 | 20 | * Section 10-222(c) of the State Government Article of the Maryland Code 21 | * Section 32(h) 22 | * Section 22(a)(9) of Article 49B of the Maryland Annotated Code 23 | * Code, Courts Article, § 12-603 24 | * Section 12-603 of the Courts and Judicial Proceedings Article, Maryland Code 25 | 26 | There's a citation translation guide in Md. Ann. Code art. 1, § 25. (I'd provide a link, but the Maryland Code is only available via LexisNexis' site, which has unlinkable, stateful URLs.) Here's a snippet: 27 | 28 | > (b) Agriculture Article. -- A section of the Agriculture Article may be cited as: "§ of the Agriculture Article". 29 | > 30 | > (c) Business Occupations and Professions Article. -- A section of the Business Occupations and Professions Article may be cited as: "§ of the Business Occupations and Professions Article". 31 | > 32 | > (d) Business Regulation Article. -- A section of the Business Regulation Article may be cited as: "§ of the Business Regulation Article". 33 | > 34 | > (e) Commercial Law Article. -- A section of the Commercial Law Article may be cited as: "§ of the Commercial Law Article". 35 | 36 | That provides a lookup table. 37 | 38 | Here's a pretty good PCRE: 39 | 40 | ``` 41 | (((§|Section)\s)?)([0-9]+)([a-zA-Z]?)-([0-9]+)([a-zA-Z]?)((-?)([0-9]+)([a-zA-Z0-9\.]*)?)((\sof th(e|is) ([A-Za-z ]+))?) 42 | ``` 43 | 44 | It fails to capture: 45 | 46 | * Section 32(h) 47 | * Section 22(a)(9) of Article 49B of the Maryland Annotated Code 48 | * Section 22(a)(9) of Article 49B of the Maryland Annotated Code 49 | 50 | And it only captures the final portion (§ 12-603) of: 51 | 52 | * Code, Courts Article, § 12-603 53 | -------------------------------------------------------------------------------- /Michigan.md: -------------------------------------------------------------------------------- 1 | Michigan court rulings' citations are fairly consistent. They all are prefixed with "MCL ". (Not to be confused with "MCR" (Michigan Court Rules) or "MCE" (Michigan Rules of Evidence), which are not laws, but rules established by the court system.) 2 | 3 | Here are some of the ways that I can find them used, both in court decisions and in cross-references within the MCL: 4 | 5 | * MCL 600.1060 to 600.1082 6 | * MCL 257.732 7 | * MCL 750.160b 8 | * MCL 324.76101 9 | 10 | ``` 11 | MCL\s([0-9]{1-3})\.([0-9a-z]{1-5})([a-z]?) 12 | ``` 13 | 14 | Michigan's section identifiers always have a decimal. Only one digit needs to exist on either side of the decimal. The first half of the identifier is the chapter number, the second is the section number. I have not identified any section identifier with more than five decimal digits, although some come precariously close (e.g., § 324.99921). 15 | 16 | Because any decimal-bearing number would be matched, it's probably best to match with 17 | -------------------------------------------------------------------------------- /New York.md: -------------------------------------------------------------------------------- 1 | Examples of citations within court decisions: 2 | 3 | * 1301 4 | * 130.10 5 | * 723.00 6 | * 104-A 7 | 8 | Often preceded with "section ". 9 | 10 | And citations within the Laws of New York: 11 | 12 | * one hundred five-a, two hundred forty-a or three hundred ninety-six-a of this chapter (*seriously*) 13 | * subdivisions one and two of section two hundred seven of this chapter 14 | * section 1303 (Violations) 15 | * section 1011 (Dissolution for failure to file certificate of type of Not-for-Profit Corporation Law under section 113) 16 | 17 | WUT. 18 | 19 | Section numbers are not unique -- they're reused between titles (or whatever they call their major sections.) 20 | 21 | Each title has both a title ("Civil Service") and an three-character abbreviation ("CVS"), but it does not appear that the abbreviations are used in cross-references within the laws. 22 | 23 | Here's a crude start: 24 | 25 | ``` 26 | ((section\s)?)([0-9]{1,4})((\.[0-9]{1,4})?)((-[A-Z]{1})?) 27 | ``` 28 | -------------------------------------------------------------------------------- /Ohio.md: -------------------------------------------------------------------------------- 1 | Example section numbers: 2 | 3 | * 105.25 4 | * 3111.211 5 | 6 | Cross-references: 7 | 8 | * sections 3111.01 to 3111.18 or 3111.20 to 3111.85 9 | * section 3111.211 or 5101.314 or section 2151.232 of the Revised Code 10 | 11 | Cross-references are prefixed with "section," rather than "§". 12 | 13 | The simplicity of Ohio's citations are tricky. They don't reliably use the word "section" beforehand, they never use the section symbol (§), and so all that we're left with is a string of 5–7 numbers, separated by a single hyphen. 14 | 15 | The titles are 1–2 digits. Chapters are 3–4 digits, with the first 1–2 digits consisting of the title number. And sections are the chapter number, a decimal, and then a 2–3 digit number. Section numbering generally begins at ".01" and increments sequentially. 16 | 17 | Here's a regular expression that works for vanilla uses and for cross-references: 18 | 19 | ``` 20 | ([0-9]{3,4})\.([0-9]{2,3}) 21 | ``` 22 | 23 | There will be some over-broad matches, but there's no getting around it. 24 | 25 | They sort with proper decimal sorting, rather than as if the decimals were whole numbers. For example, see [the order of Chapter 5727](http://codes.ohio.gov/orc/5727): they use proper decimal sorting—.10, .11, .111, .12. 26 | -------------------------------------------------------------------------------- /Oklahoma.md: -------------------------------------------------------------------------------- 1 | Examples as found within the Oklahoma Statutes: 2 | 3 | * §57-1 4 | * §57-4.1 5 | * §57-16a 6 | * §57-509.1 7 | * §27A-1 8 | * §27A-1-1-102 9 | * §27A-2-10-103 10 | * §27A-3-2-106b 11 | * Rule 257:1-1-1 12 | 13 | Cross-references as found within the Oklahoma Statutes: 14 | 15 | * Section 988.12 or 991a-2 of Title 22 16 | * Section 980 of Title 22 of the Oklahoma Statutes 17 | * Section 192 of Title 74 of the Oklahoma Statutes 18 | 19 | Clearly, two different regular expressions are going to be needed here. First, one to pick up non-xref citations: 20 | 21 | ``` 22 | (((§(\s?))?)|(Rule\s))([0-9]{1,3})((:?)([0-9A-Z]{1})?)-([0-9]{1,3})([a-z]?)((\.[0-9]{1,2})?)((-[0-9]{1,2})?)((-[0-9]{1,3})?)([a-z]?) 23 | ``` 24 | 25 | Then, one to pick up cross-references: 26 | 27 | ``` 28 | Section\s([0-9a-z\.-]{1,6})\sof\sTitle\s([0-9]{1,3}) 29 | ``` 30 | 31 | Both of those are going to need a lot more testing. 32 | -------------------------------------------------------------------------------- /Oregon.md: -------------------------------------------------------------------------------- 1 | These are preceded by an initialism (ORS, for "Oregon Revised Statutes"), followed by a unique identifier comprised of a title number and a section number, separated by a period. 2 | 3 | * ORS 18.455 4 | * ORS 813.100, 813.140 or 813.150 5 | * ORS 335.495 to 335.505 6 | 7 | ``` 8 | ORS\s([0-9]{1})([0-9A-Z]{0,3})\.([0-9]{3}) 9 | ``` 10 | 11 | The `ORS\s` prefix can be omitted to yield a higher match rate and (anecdotally) a low rate of false matches. That said, many decimal-bearing numbers would be matched. 12 | -------------------------------------------------------------------------------- /Pennsylvania.md: -------------------------------------------------------------------------------- 1 | Examples within the code: 2 | 3 | * § 149.9 4 | * § 138k.13 5 | * § 59.4a 6 | * Rule 1205 7 | 8 | Section identifiers are are the chapter number, a period, and then a unique identifier within that chapter. They are often (but not always) preceded by a §. Except when they’re “rules,” and then they’re simply an incremented number (with the first two characters representing the chapter number). Rules are found within titles with “rules” in their name (e.g., “Rules of Evidence,” “Minor Court Civil Rules”). 9 | 10 | Section identifiers are not unique within the code, only within the title. 11 | 12 | From court rulings: 13 | 14 | * Section 9543.1 of the Post Conviction Relief Act (“PCRA”), 42 Pa.C.S.A. § 9543.1 15 | * 42 Pa.C.S. § 702(b) 16 | * 18 Pa.C.S.A. § 907(a) 17 | * Section 314(a) of the Workers’ Compensation Act (“Act”), 77 P.S. § 651(a) 18 | * Section 704 of the Administrative Agency Law, 2 Pa.C.S. § 704 19 | * 1 Pa.C.S. § 1921(a) 20 | 21 | Subsequent references begin with “id. " 22 | 23 | Here's a fairly good regex: 24 | 25 | ``` 26 | ((\d{1,2}\sPa?\.(C\.)?S\.(A\.)?\s)?(§|Rule|Section)\s?\d{1,4}\(?[a-z]?\)?(\.\d{1,3}[a-z]?)?(\sof\sthe\s[A-Za-z “”’()]+)?(, )?){1,2} 27 | ``` 28 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Law Identifier 2 | 3 | A collection of regular expressions to identify references to state laws within the United States. 4 | 5 | There is one file for each state, containing both a regular expression and a textual description of what that regular expression does, and how it was derived. These are, by design, naïve regular expressions. For example, they make no attempt to recognize that `§ 18.2-100–18.2-105` describes a range of six sections in all, but instead would only pick up on `§ 18.2-100` and `§ 18.2-105`. 6 | 7 | Inevitable, some states are going to use identifiers that are not amenable to parsing with a single PCRE, or that require something more advanced than a regular expression in order to get a high rate of matches. A best effort will be made for every state. 8 | 9 | ## TO DO 10 | * Create a JSON file containing all PCREs, with the state's abbreviation serving as the key. 11 | -------------------------------------------------------------------------------- /Texas.md: -------------------------------------------------------------------------------- 1 | Examples of section identifiers: 2 | 3 | * Sec. 53.033 4 | * Sec. 52.0165 5 | * Sec. 3151.101 6 | * Art. 7621f 7 | * Art. 7808 8 | * Sec. 4A.101 9 | 10 | (Often "Section," sometimes "Sect." ) 11 | 12 | So there are article, and sections. I have no idea what the difference is—they seem to be used interchangeably. 13 | 14 | In court opinions, citations appear as: 15 | 16 | * Tex. Nat. Res. Code § 61.011 17 | * Tex. Nat. Res. Code § 61.011, .0161 18 | * Tex. Civ. Prac. & Rem. Code § 41.001 19 | * Tex. Prop.Code Ann. §§ 21.015-.015 20 | * Tex. Educ. Code § 21.307 21 | 22 | Note that "Prop.Code" is not a typo. That style was employed repeatedly. 23 | 24 | On second use, the major identifer is omitted, and replaced with "Id." 25 | 26 | Here's a PCRE that should work for the identifiers as used within the Texas Statutes: 27 | 28 | ``` 29 | (Sec\.|Section|Art\.|Article)\s([0-9]{1})([0-9a-z]{0,4})(\.([0-9]{0,4})?) 30 | ``` 31 | 32 | That requires a proper prefix, though—it won't detect citations without them. (That's because literally any number that's at least two digits would qualify under that PCRE, lacking the prefix.) The citation must start with a single digit, and then can have up to four more letters and/or numbers. As a final, optional, component, there can be a period followed by 0–4 digits. 33 | 34 | And here's a PCRE that should work for the identifiers as used within state court opinions: 35 | 36 | ``` 37 | Tex.\s([A-Za-z&\. ]+)\sCode\s§\s([0-9]{1})([0-9a-z]{0,4})(\.([0-9]{0,4})?) 38 | ``` 39 | 40 | The one catch is that it doesn't catch any of `Tex. Prop.Code Ann. §§ 21.015-.015` because of the presence of "Ann. ". The inclusion of that needs to be permissible. 41 | -------------------------------------------------------------------------------- /Virginia.md: -------------------------------------------------------------------------------- 1 | ``` 2 | ([[0-9]{1,})([0-9A-Za-z\-\.]{0,3})-([0-9A-Za-z\-\.:]*)([0-9A-Za-z]{1,}) 3 | ``` 4 | 5 | This is in use on [Virginia Decoded](http://vacode.org), with great success. The structure necessitates at least numbers separated by a hyphen, making overbroad matches uncommon, so this is best employed as written, without requiring a `§\s` prefix. 6 | -------------------------------------------------------------------------------- /Washington-DC.md: -------------------------------------------------------------------------------- 1 | Example section numbers: 2 | 3 | * § 9-812 4 | * § 24-201.19 5 | * § 24-211.01 6 | * § 24-221.01a 7 | * § 24-1105 8 | * § 50-1505.03 9 | * § 50-2201.04c 10 | * § 29A-101.76 11 | 12 | Example court ruling citations: 13 | 14 | * 47 D.C. SS 820, 47-830. 15 | * D.C. Code § 23-110 16 | * D.C. Code § 17-306 17 | * D.C. Code §47-1002(8) and §47-1002(18) 18 | * D.C. Code sections 1-2272(8) and (18) and 47-1002(8) and (18) 19 | 20 | Structure is title-chapter/section. That is, the first segment is the title number, then a hyphen. The second segment is the chapter number followed by the section number. § 9-812, for example, is Title 9, Chapter 8, the 12th section. 21 | 22 | This matches all example sections and all court citations, optionally matching the section symbol: 23 | 24 | ``` 25 | ((§\s)?)([0-9]{1,2})([A-Z]?)-([0-9]{3,4})((((\.)([0-9]{2}))?)([a-z]?)) 26 | ``` 27 | -------------------------------------------------------------------------------- /Washington.md: -------------------------------------------------------------------------------- 1 | Some example citations: 2 | 3 | * 3.46.015 4 | * 57.90.100 5 | * 71A.10.910 6 | * 35.102.900 7 | * 35.32A.900 8 | 9 | Three segments, separated by periods. The first segment is numeric, but may have an alpha suffix, one to three characters in all. The second is numeric, but may have an alpha suffix, two to four characters in all. And the third is numeric, always three digits. 10 | 11 | ``` 12 | ([0-9]{1,2})([A-Z]?)\.([0-9]{1,3})([A-Z]?)\.([0-9]{1,3}) 13 | ``` 14 | 15 | More accurate matches will result from using a prefix of `RCW\s`, but the structure of the identifiers is unusual enough that overbroad matches are not likely. 16 | -------------------------------------------------------------------------------- /Wyoming.md: -------------------------------------------------------------------------------- 1 | Wyoming's citations are quite consistent. In a (small) corpus of court decisions, sections are always preceded with `§ `, and are often preceded with a specification that it's the Wyoming statutes to which they're referring. These are all valid citations in court decisions: 2 | 3 | * Wyo. Stat. § 20-2-113 4 | * WYO. STAT. § 20-2-113 5 | * Wyo. Stat. Ann. § 20-2-204 6 | * § 34-14-208 7 | 8 | Here are some samples from the Wyoming Statutes: 9 | 10 | * 6-10-301 11 | * 12 | 13 | So that structure is Title-Chapter-Section. It looks like identifiers are always numeric, never have suffixes, and never have decimals. 14 | 15 | Here's a regular expression that captures things well enough: 16 | 17 | ``` 18 | ((§\s)?)([0-9]{1,4})-([0-9]{1,3})-([0-9]{1,4}) 19 | ``` 20 | --------------------------------------------------------------------------------