{"id":17247794,"url":"https://github.com/joshdata/dc-code-prototype","last_synced_at":"2026-01-07T04:03:10.135Z","repository":{"id":11515928,"uuid":"13996889","full_name":"JoshData/dc-code-prototype","owner":"JoshData","description":"Unofficial Code of the District of Columbia in XML, produced under contract with the Council of the District of Columbia. Last updated in 2014.","archived":false,"fork":false,"pushed_at":"2015-08-12T13:47:34.000Z","size":30930,"stargazers_count":7,"open_issues_count":3,"forks_count":6,"subscribers_count":6,"default_branch":"gh-pages","last_synced_at":"2025-01-31T07:21:38.594Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"cc0-1.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/JoshData.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2013-10-30T19:14:49.000Z","updated_at":"2019-08-13T15:29:09.000Z","dependencies_parsed_at":"2022-09-23T21:40:43.171Z","dependency_job_id":null,"html_url":"https://github.com/JoshData/dc-code-prototype","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/JoshData%2Fdc-code-prototype","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/JoshData%2Fdc-code-prototype/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/JoshData%2Fdc-code-prototype/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/JoshData%2Fdc-code-prototype/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/JoshData","download_url":"https://codeload.github.com/JoshData/dc-code-prototype/tar.gz/refs/heads/gh-pages","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":245598311,"owners_count":20641884,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-10-15T06:38:59.710Z","updated_at":"2026-01-07T04:03:05.117Z","avatar_url":"https://github.com/JoshData.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"DC Code XML\n===========\n\nThis repository contains the Code of the District of Columbia in XML format.\n\nThe DC Code in XML makes use of a custom schema that draws on ideas from [Akoma Ntoso](http://www.akomantoso.org/) and [United States Legislative Markup](http://uscodebeta.house.gov/download/download.shtml).\n\nThe schema can almost entirely be seen in the following four examples.\n\n(1) Root element. The root element is a `\u003clevel\u003e` element. It contains some metadata and nested `\u003clevel\u003e` elements for the first level divisions of the code.\n\n\t\u003clevel type=\"document\"\u003e\n\t\t\u003cheading\u003eCode of the District of Columbia\u003c/heading\u003e\n\n\t\t\u003cmeta\u003e\n\t\t\t\u003crecency\u003e\n\t\t\t\t\u003clast-act\u003eDC Act 20-101\u003c/last-act\u003e\n\t\t\t\t\u003ceffective-date\u003e2014-09-09\u003c/effective-date\u003e\n\t\t\t\t\u003cpublication-date\u003e2014-09-24T17:03:41-04:00\u003c/publication-date\u003e\n\t\t\t\u003c/recency\u003e\n\t\t\u003c/meta\u003e\n\n\t\t\u003c!-- \u003clevel\u003e elements as shown below --\u003e\n\n\t\u003c/level\u003e\n\n(2) \"Big\" levels that appear in the Table of Contents (`toc`). These are divisions, titles, chapters, and so on above the level of a section.\n\n    \u003clevel type=\"toc\"\u003e\n\t\t\u003cprefix\u003eTitle\u003c/prefix\u003e\n\t\t\u003cnum\u003e1\u003c/num\u003e\n\t\t\u003cheading\u003eGovernment Organization\u003c/heading\u003e\n\n\t\t\u003c!-- other \u003clevel\u003e elements nested here --\u003e\n\n    \u003c/level\u003e\n\n(3) Sections and annotations.\n\n\t\u003clevel type=\"section\"\u003e\n\t\t\u003cnum\u003e2-531\u003c/num\u003e\n\t\t\u003cheading\u003ePublic policy.\u003c/heading\u003e\n\n\t\t\u003ctext\u003eThe public policy of the District of Columbia is that all persons are entitled\n\t\tto full and complete information regarding the affairs of government and the official\n\t\tacts of those who represent them as public officials and employees. To that end,\n\t\tprovisions of this subchapter shall be construed with the view toward expansion of public\n\t\taccess and the minimization of costs and time delays to persons requesting information.\u003c/text\u003e\n\n\t\t\u003clevel type=\"annotations\"\u003e\n\t\t  \u003clevel\u003e\n\t\t    \u003cheading\u003eHistory\u003c/heading\u003e\n\t\t    \u003ctext\u003e(Oct. 21, 1968, Pub. L. 90-614, title II, ...\u003c/text\u003e\n\t\t  \u003c/level\u003e\n\t\t\u003c/level\u003e\n\t\u003c/level\u003e\n\n(4) \"Little\" levels which are rendered as paragraphs (often numbered).\n\n\t\u003clevel\u003e\n\t\t\u003cnum\u003e(c)\u003c/num\u003e\n\t\t\u003cheading\u003eUnited States\u003c/heading\u003e\n\n\t\t\u003ctext\u003eThe United States, its officers, employees, and agents, and its agencies shall not:\u003c/text\u003e\n\n\t\t\u003clevel\u003e\n\t\t\t\u003cnum\u003e(1)\u003c/num\u003e\n\t\t\t\u003ctext\u003eBe responsible for the payment of any judgments, liabilities or costs resulting\n\t\t\tfrom any action or proceeding against the District of Columbia or its agencies,\n\t\t\tofficers, employees, or agents;\u003c/text\u003e\n\t\t\u003c/level\u003e\n\n\t\t\u003c!-- other \u003clevel\u003e elements nested here --\u003e\n\t\u003c/level\u003e\n\nXIncludes\n---------\n\nThe Code is one logical XML document (approximately 75 megabytes), but it has been broken apart into approximately 26,000 smaller files to make it more manageable. The Code begins in [index.xml](index.xml) and [XInclude](http://www.w3.org/TR/xinclude/) tags stitch all of the documents together. All XIncludes target `\u003clevel\u003e` elements at or above the section level. We have split the code at titles, chapters, subchapters, and so on down to sections.\n\nEach XInclude element has an `href` attribute with a relative path to the file that is logically included at that point.\n\nThe top-level `index.xml` file looks like this:\n\n\t\u003clevel type=\"document\"\u003e\n\t  \u003cheading\u003eCode of the District of Columbia\u003c/heading\u003e\n\t  \u003cmeta\u003e\n\t    ...\n\t  \u003c/meta\u003e\n\t  \u003clevel type=\"toc\"\u003e\n\t    \u003cprefix\u003eDivision\u003c/prefix\u003e\n\t    \u003cnum\u003eI\u003c/num\u003e\n\t    \u003cheading\u003eGovernment of District\u003c/heading\u003e\n\t    \u003cns0:include xmlns:ns0=\"http://www.w3.org/2001/XInclude\" href=\"Title-1/index.xml\"/\u003e\n\t    \u003cns0:include xmlns:ns0=\"http://www.w3.org/2001/XInclude\" href=\"Title-2/index.xml\"/\u003e\n\t    \u003cns0:include xmlns:ns0=\"http://www.w3.org/2001/XInclude\" href=\"Title-3/index.xml\"/\u003e\n\t    ...\n\t  \u003c/level\u003e\n\t  \u003clevel type=\"toc\"\u003e\n\t    \u003cprefix\u003eDivision\u003c/prefix\u003e\n\t    \u003cnum\u003eII\u003c/num\u003e\n\t    \u003cheading\u003eJudiciary and Judicial Procedure\u003c/heading\u003e\n\t    \u003cns0:include xmlns:ns0=\"http://www.w3.org/2001/XInclude\" href=\"Title-11/index.xml\"/\u003e\n\t    \u003cns0:include xmlns:ns0=\"http://www.w3.org/2001/XInclude\" href=\"Title-12/index.xml\"/\u003e\n\t    ...\n\t\u003c/level\u003e\n\nThe namespace prefix `ns0` is subject to change.\n\nDocument Element\n----------------\n\nThe root element is a `\u003clevel\u003e`, like most other nodes in the schema, with `type=\"document\"`. We are not using namespaces.\n\nThis document element contains a `\u003cmeta\u003e` element with document metadata.\n\nThe `\u003cmeta\u003e` element is followed by `\u003clevel\u003e` elements representing the Divisions of the Code. In the actual root file `index.xml` in this repository some of the `\u003clevel\u003e` elements shown below are replaced by XIncludes, but we show them replaced with their referenced content here to highlight the intended semantics.\n\n\t\u003c?xml version='1.0' encoding='utf-8'?\u003e\n\t\u003clevel type=\"document\"\u003e\n\n\t  \u003cheading\u003eCode of the District of Columbia\u003c/heading\u003e\n\n\t  \u003cmeta\u003e\n\t    ...\n\t  \u003c/meta\u003e\n\n\t  \u003clevel type=\"toc\"\u003e\n\t    \u003cprefix\u003eDivision\u003c/prefix\u003e\n\t    \u003cnum\u003eI\u003c/num\u003e\n\t    \u003cheading\u003eGovernment of District\u003c/heading\u003e\n\n\t    \u003clevel type=\"toc\"\u003e\n\t      \u003cprefix\u003eTitle\u003c/prefix\u003e\n\t      \u003cnum\u003e1\u003c/num\u003e\n\t      \u003cheading\u003eGovernment Organization\u003c/heading\u003e\n\n\t      \u003clevel type=\"toc\"\u003e\n\t        \u003cprefix\u003eChapter\u003c/prefix\u003e\n\t        \u003cnum\u003e1\u003c/num\u003e\n\t        \u003cheading\u003eDistrict of Columbia Government Development\u003c/heading\u003e\n\n\t        \u003clevel type=\"toc\"\u003e\n\t          \u003cprefix\u003eSubchapter\u003c/prefix\u003e\n\t          \u003cnum\u003eI\u003c/num\u003e\n\t          \u003cheading\u003eDistrict of Columbia Establishment\u003c/heading\u003e\n\n\t          \u003clevel type=\"section\"\u003e\n\t            \u003cnum\u003e1-101\u003c/num\u003e\n\t            \u003cheading\u003eTerritorial area.\u003c/heading\u003e\n\t            \u003ctext\u003eThe District of Columbia is that portion of the territory\n\t            of the United States ceded by the State of Maryland for the\n\t            permanent seat of government of the United States, including the\n\t            river Potomac in its course through the District, and the islands\n\t            therein.\u003c/text\u003e\n\nMetadata\n--------\n\nThe document's metadata describes the recency of the DC Code publication:\n\n\t\u003crecency\u003e\n\t  \u003clast-act\u003eDC Act 20-101\u003c/last-act\u003e\n\t  \u003ceffective-date\u003e2014-09-09\u003c/effective-date\u003e\n\t  \u003cpublication-date\u003e2014-09-24T17:03:41-04:00\u003c/publication-date\u003e\n\t\u003c/recency\u003e\n\n\nThe `last-act` field is a textual field describing, in human-readable form, the last act that has been codified in the document. For corresponding machine-readable data, see the file `update-chart.csv` at the root of the repository.\n\nThe `effective-date` field contains an ISO 8601-formatted date corresponding to the effective date of the most recently codified act. The DC Code is expected to accurately reflect the law on this date.\n\nThe `publication-date` field contains an ISO 8601-formatted date indicating when the document was published by the DC Council. The publication date may be before or after the effective date.\n\nLevels\n------\n\nAll hierarchy of the Code is represented by `\u003clevel\u003e` elements. This includes both \"big\" levels (titles, chapters, etc.), sections, and \"little\" levels (subsections, paragraphs, and so on).\n\n### Type Attribute\n\nThe `type` attribute indicates the type of the level, as follows:\n\n* `document`: The root of the entire document. There is one such element and it is at the top of the hierarchy.\n* `toc`: These are divisions, titles, chapters, and so on above the level of a section. `toc` is a mnemonic for Table of Contents. These levels appear in the Table of Contents of the code.\n* `section`: Sections of the code (e.g. § 1-101), the primary level at which text and annotations occur and what citations target.\n* `placeholder`: The level is section-like but it represents Code sections that no longer exist. They are documented specifically in a section below.\n* `annotations`: Annotation blocks.\n* `appendices`: Appendices to a section (see [Title-16/Chapter-9/16-916.01.xml](Title-16/Chapter-9/16-916.01.xml)).\n* `form`: Blocks that are rendered with internal whitespace preserved. These elements contains quoted language that the Code is directing to be used on government forms.\n* When `type` is omitted, the level is a numbered paragraph (i.e. `(1) The public policy....`) or an unnumbered block with a heading. Inside annotations, subheadings are represented this way.\n\n### Level Numbering\n\nA `\u003clevel\u003e` element must contain at least one of `\u003cprefix\u003e`, `\u003cnum\u003e`, or `\u003cheading\u003e`.\n\n`\u003cprefix\u003e` is used only in `type=\"toc\"` levels to provide the text that appears before the level's number.\n\n* The inner text of this element is one of `Article`, `Chapter`, `Division`, `Part`, `Subchapter`, `Subdivision`, `Subpart`, `Subtitle`, `Title`, and `Unit`.\n\n`\u003cnum\u003e` indicates the level's number.\n\n* For `toc` levels, this usually is a number, letter, or roman numeral.\n* For sections, the number is roughly in the form `1-101` (title, hyphen, section number). It never includes the §-symbol.\n* For \"little\" levels, this is the paragraph's numbering including any parenthesis around the numbering. An example would be `(12A-i)`.\n* When `\u003cnum\u003e` is omitted, the level is simply unnumbered. `document` and `placeholder` levels never have `\u003cnum\u003e` elements. For placeholders, see below.\n\n`\u003cheading\u003e` contains the level's name or heading.\n\n* For `toc` levels, sections, placeholders, and subheadings in annotations, this is the level's title or heading, such as `Government Organization`.\n* A heading can also appear on \"little\" levels and would appear as something like italicized text.\n\n### Content Elements\n\nFollowing the `\u003clevel\u003e`'s numbering elements described just above, a `\u003clevel\u003e` must contain one or more `\u003clevel\u003e` or `\u003ctext\u003e` (see below) elements.\n\n* These elements must be rendered in document order.\n* For \"little\" levels, the level's `\u003cnum\u003e` and/or `\u003cheading\u003e` are typically rendered inside and at the start of the first `\u003ctext\u003e` paragraph.\n\nText\n----\n\nText content is contained within `\u003ctext\u003e` elements inside `\u003clevel\u003e`s. \n\n* Each `\u003ctext\u003e` element is a separate paragraph.\n* `\u003ctext\u003e` may be interleaved with other `\u003ctext\u003e` and `\u003clevel\u003e` elements and must be rendered in document order.\n* `\u003ctext\u003e` elements contain a subset of HTML.\n\nThis is an example of a typical `\u003ctext\u003e` element:\n\n\t\u003ctext\u003eOne \u003cspan style=\"font-style: italic; \"\u003eex officio \u003c/span\u003eCommissioner,\n\tthe Deputy Mayor for Planning and Economic Development;\u003c/text\u003e\n\nAn optional `class` attribute can be one of:\n\n* `centered`: The paragraph is rendered with centered text alignment.\n\nInside the `\u003ctext\u003e` element is HTML conforming to the following restrictions:\n\n* Only bare text, `\u003cspan\u003e`, and `\u003ctable\u003e` elements may appear.\n* `\u003cspan\u003e` elements may have a style attribute containing only the following CSS:\n * `font-weight: bold;`\n * `font-style: italic;`\n * `text-decoration: underline;`\n * `font-family: monospace;`\n* `\u003ctable\u003e` elements may contain `thead`, `tr`, `th`, and `td` elements. `th` and `td` elements may have `colspan` attributes (as in HTML), and their content is restricted to the same subset of HTML as for `\u003ctext\u003e` elements. When a `\u003ctable\u003e` element appears inside a `\u003ctext\u003e` node, it is the only content in the the `\u003ctext\u003e` node (because each `\u003ctext\u003e` node represents a paragraph).\n\nPlaceholders\n------------\n\nPlaceholder levels are similar to levels with `type=\"section\"` but represent Code sections that have been repealed, omitted, etc. Here is an example:\n\n\t\u003clevel type=\"placeholder\"\u003e\n\t  \u003creason\u003eNot funded\u003c/reason\u003e\n\t  \u003csection\u003e1-136.01\u003c/section\u003e\n\t  \u003cheading\u003eEstablishment of the 51st State Commission.\u003c/heading\u003e\n\t  \u003ctext\u003e[Not funded].\u003c/text\u003e\n\t  \u003clevel type=\"annotations\"\u003e\n\t    ...\n\nThese levels do not have a `\u003cnum\u003e` element. The `\u003cheading\u003e` element typically contains the name of the section that was removed. These levels may also have these other child elements:\n\n* `\u003creason\u003e`: The reason for the placeholder.\n * When present, one of `Expired`, `Not funded`, `Omitted`, `Repealed`, `Reserved`, and `Transferred`.\n * When not present, the reason for the placeholder is not indicated in the code.\n* `\u003csection\u003e`: The number of the omitted section (e.g. `1-136.01`).\n\nIn place of `\u003csection\u003e`, a placeholder may instead contain:\n\n* `\u003csection-start\u003e`: The number of the first omitted section in a range of omitted sections.\n* `\u003csection-end\u003e`: The number of the last omitted section in a range of omitted sections.\n* `\u003csection-range-type\u003e`: This element contains the text `range` if all sections between start and end are omitted (usually rendered as \"A to B\") or `list` if the start and end name two sections but a range is not implied (usually rendered as \"A, B\").\n\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fjoshdata%2Fdc-code-prototype","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fjoshdata%2Fdc-code-prototype","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fjoshdata%2Fdc-code-prototype/lists"}