3 ms·
Tbh I feel like something like this would greatly benefit from being compiled in a documentation repo, like as a wiki or structured like obsidian or logseq docs
by CuriousCosmic 3y ago
Tbh I feel like something like this would greatly benefit from being compiled in a documentation repo, like as a wiki or structured like obsidian or logseq docs.
The information is all important but compiled as one big document it's obviously going to tough to crack into and digest. But structuring it into a bunch of smaller sections that you can easily jump between relevant/interconnected bits would make this kind of thing so much more transparent for people.
- avs733 3y agoUnder the enhanced content developer tools you can download it as: * A JSON (https://www.federalregister.gov/api/v1/documents/2024-06526?publication_date=2024-04-04 https://www.federalregister.gov/api/v1/documents/2024-06526?...) * An XML (https://www.federalregister.gov/documents/full_text/xml/2024/04/04/2024-06526.xml https://www.federalregister.gov/documents/full_text/xml/2024...) * A standardized government metadata format called MODS (https://www.govinfo.gov/metadata/granule/FR-2024-04-04/2024-06526/mods.xml https://www.govinfo.gov/metadata/granule/FR-2024-04-04/2024-...) They also have developer resources for all of the above: https://www.federalregister.gov/reader-aids/developer-resources https://www.federalregister.gov/reader-aids/developer-resour...