You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn't a technical ask, but something it'd probably help to just get out of the way. What should we use as an ID format for citing sections of the DC Code?
As I describe in unitedstates/uscode#3, the US Congress uses usc/[title]/[section] in their official bill XML, so I followed suit for the citation IDs I added to the JSON "spine" that @tauberer updated the uscode repo to produce.
Would dc/[title]/[section] work for DC? So for example: dc/5/201 for § 5-201. For § 24-221.01c, it would be dc/24/221.01a. (§ 24-221.01a is a full-blooded section, not a subsection, and is a peer with § 24-221 and § 24-271.) For a subsection like § 24-221.01a(a), the cite would be dc/24/221.01a/a.
Uses: I'm going to add DC Code support to unitedstates/citation, using the good work that @waldoj did in #4. I'd also suggest a citation field as useful in the general purpose JSON this repo produces.
The text was updated successfully, but these errors were encountered:
This isn't a technical ask, but something it'd probably help to just get out of the way. What should we use as an ID format for citing sections of the DC Code?
As I describe in unitedstates/uscode#3, the US Congress uses
usc/[title]/[section]
in their official bill XML, so I followed suit for the citation IDs I added to the JSON "spine" that @tauberer updated the uscode repo to produce.Would
dc/[title]/[section]
work for DC? So for example:dc/5/201
for§ 5-201
. For§ 24-221.01c
, it would bedc/24/221.01a
. (§ 24-221.01a is a full-blooded section, not a subsection, and is a peer with§ 24-221
and§ 24-271
.) For a subsection like § 24-221.01a(a), the cite would bedc/24/221.01a/a
.Uses: I'm going to add DC Code support to unitedstates/citation, using the good work that @waldoj did in #4. I'd also suggest a citation field as useful in the general purpose JSON this repo produces.
The text was updated successfully, but these errors were encountered: