Datasets:
Update README.md
Browse files
README.md
CHANGED
|
@@ -52,26 +52,77 @@ dataset_info:
|
|
| 52 |
num_examples: 3027628
|
| 53 |
download_size: 2038476796
|
| 54 |
dataset_size: 5265441041
|
| 55 |
-
rai:dataLimitations:
|
| 56 |
-
- Coverage is not exhaustive. LOCUS v1.0 does not represent every U.S.
|
| 57 |
-
|
| 58 |
-
|
| 59 |
-
|
| 60 |
-
-
|
| 61 |
-
-
|
| 62 |
-
|
| 63 |
-
|
| 64 |
-
-
|
| 65 |
-
|
| 66 |
-
|
| 67 |
-
-
|
| 68 |
-
|
| 69 |
-
|
| 70 |
-
|
| 71 |
-
|
| 72 |
-
|
| 73 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 74 |
rai:hasSyntheticData: false
|
|
|
|
| 75 |
---
|
| 76 |
|
| 77 |
# LOCUS v1.0
|
|
|
|
| 52 |
num_examples: 3027628
|
| 53 |
download_size: 2038476796
|
| 54 |
dataset_size: 5265441041
|
| 55 |
+
rai:dataLimitations: >
|
| 56 |
+
- Coverage is not exhaustive. LOCUS v1.0 does not represent every U.S.
|
| 57 |
+
municipal or county jurisdiction, and jurisdictions vary in how completely
|
| 58 |
+
their local law is digitized and codified.
|
| 59 |
+
|
| 60 |
+
- The `function` and `topic` labels are model-assigned and have not been fully
|
| 61 |
+
human-validated. Label noise should be expected, particularly at taxonomy
|
| 62 |
+
boundaries (e.g., Rules vs. Process, Buildings vs. Zoning).
|
| 63 |
+
|
| 64 |
+
- The `is_substantive` field is derived deterministically from `function` and
|
| 65 |
+
inherits any errors in function labeling.
|
| 66 |
+
|
| 67 |
+
- The topic taxonomy is intentionally coarse (Buildings, Business, Nuisance,
|
| 68 |
+
Zoning, Other) and does not capture fine-grained subject matter important for
|
| 69 |
+
some downstream tasks.
|
| 70 |
+
|
| 71 |
+
- Header-only rows are retained in the dataset but are not appropriate inputs
|
| 72 |
+
for substantive classification and are explicitly excluded from model
|
| 73 |
+
inference.
|
| 74 |
+
|
| 75 |
+
- Local law changes over time. The dataset reflects a snapshot and may not
|
| 76 |
+
match the current law of any given jurisdiction.
|
| 77 |
+
rai:dataBiases: >
|
| 78 |
+
- Geographic and population skew: larger and more urbanized jurisdictions, and
|
| 79 |
+
jurisdictions that publish their codes through major codification vendors, are
|
| 80 |
+
likely overrepresented relative to small or rural municipalities.
|
| 81 |
+
|
| 82 |
+
- State-level legal regimes differ, so the distribution of functions and
|
| 83 |
+
topics is not uniform across states; aggregate label frequencies should not be
|
| 84 |
+
assumed to generalize to any individual jurisdiction.
|
| 85 |
+
|
| 86 |
+
- The taxonomy itself encodes choices about what counts as "substantive" law
|
| 87 |
+
(Rules and Enforcement) versus procedural, contextual, or structural
|
| 88 |
+
provisions. Alternative legal-theoretic framings would produce different
|
| 89 |
+
labels.
|
| 90 |
+
|
| 91 |
+
- Labels were produced by automated classifiers and may reflect biases of
|
| 92 |
+
those classifiers, including biases inherited from their training data.
|
| 93 |
+
|
| 94 |
+
- English-language only. Non-English text occasionally present in U.S. local
|
| 95 |
+
codes is not handled as a separate class.
|
| 96 |
+
rai:personalSensitiveInformation: >
|
| 97 |
+
LOCUS v1.0 is built from publicly enacted municipal and county law, which is a
|
| 98 |
+
matter of public record. However, local ordinances can incidentally contain
|
| 99 |
+
references to identifiable individuals (e.g., named officials, sponsors, or
|
| 100 |
+
parties to specific proceedings) and to specific properties or businesses
|
| 101 |
+
(e.g., addresses in zoning provisions, license holders, named establishments).
|
| 102 |
+
No effort has been made to redact such incidental references. The dataset does
|
| 103 |
+
not contain non-public personal data, biometric data, health data, financial
|
| 104 |
+
account information, or government-issued identifiers.
|
| 105 |
+
rai:dataUseCases: >
|
| 106 |
+
Intended uses include legal text classification research, analysis of
|
| 107 |
+
local-law structure and composition, substantive vs. non-substantive filtering
|
| 108 |
+
for downstream legal NLP pipelines, refinement of legal taxonomies, and weakly
|
| 109 |
+
supervised or human-in-the-loop annotation workflows. The dataset is not
|
| 110 |
+
appropriate as legal advice, as a substitute for human legal review, as a
|
| 111 |
+
complete census of U.S. local law, or as a fully validated benchmark in the
|
| 112 |
+
absence of additional human auditing.
|
| 113 |
+
rai:dataSocialImpact: >
|
| 114 |
+
Anticipated positive impacts include lowering the cost of empirical research
|
| 115 |
+
on local government law, supporting tools that help residents, journalists,
|
| 116 |
+
and researchers understand municipal regulation, and enabling reproducible
|
| 117 |
+
study of how local jurisdictions structure their codes. Anticipated risks
|
| 118 |
+
include over-reliance on automated classifications in settings with legal
|
| 119 |
+
consequences, misinterpretation of aggregated label frequencies as
|
| 120 |
+
authoritative statements about the law, and downstream tools surfacing model
|
| 121 |
+
outputs to end users as if they were vetted legal information. Users deploying
|
| 122 |
+
systems built on this dataset should clearly disclose the automated and
|
| 123 |
+
unaudited nature of the labels and should not present outputs as legal advice.
|
| 124 |
rai:hasSyntheticData: false
|
| 125 |
+
license: cc-by-nc-4.0
|
| 126 |
---
|
| 127 |
|
| 128 |
# LOCUS v1.0
|