usgpo / uslm Goto Github PK

Join our team in GPO's Office of Programs, Strategy, and Technology!
Program Planner (Recent Graduate) https://www.usajobs.gov/GetJob/ViewDetails/542252400
This job will close when we have received 100 applications which may be sooner than the closing date.
Please help spread the word!

Hello legislative data professionals,

I'm looking forward to getting in contact with someone in the GPO USLM xml team specifically Ms. LaPlant. I want to propose an initiative to the government of my country to stablish a standardized xml schema and ML for Mexican government legal statements and I would really appreciate some insights. I tried to contact you through the GPO support but was redirected to submit an issue here. My linkedin is https://www.linkedin.com/in/jorge-mancilla-462a63123/ thank you guys.

Looks like markdown is not formatted properly for the table in section 4.4:

I took some time to fix it, but later I saw that i should report an issue instead of creating the PR directly.

Also on section 3. Inhertiance, markdown for `<level role="chapter">`_ _is roughly analogous to `<chapter>
you missed the ` after <chapter>.

🆙🆙🆙₹

When pulling the data from the COMPS section of statutes there is an issue with the appropriations measures where the following coding are not being compiled rather are appearing as continued text.

• <compsdtd:subsubaccount commented="no" id="OF COURSE THIS VARYS" in-effect="yes" type="subsequent"><compsdtd:header bold="off" display-inline="yes-display-inline">

• <compsdtd:appropriations-para (Item 1)
  Additionally, where there are tables within the compilation the tables are unformed and show up as small continuous text. (Item 4)
  Finally, there are coding issues where >. shows up in the code, and when translated shows up on a separate line where it should be inline with the prior text. (Item 3)

Comps utilized for this example: COMPS-1422; COMPS-16716

16716

Hello! I am working to extract data from several collections from this location: https://www.govinfo.gov/app/collection/comps/w to database tables. I'm working to store key content for each law in one table as follows:

section identifier
section – subsection identifier
section – subsection – paragraph identifier
section – subsection – paragraph - subparagraph identifier
section – subsection – paragraph - subparagraph – clause identifier

section num
section – subsection num
section – subsection – paragraph num
section – subsection – paragraph - subparagraph num
section – subsection – paragraph - subparagraph – clause num

etc etc.

I am using open refine to extract data to css, then load to database. open refine does an ok job, but it a) does not seem able to get all content b) does not deal well with large files.

I wonder if I am reinventing the wheel here, and if the USLM team has any ideas for best practice extracting content from the xml.

thank you, and thanks for the good work!

-Joel

~~~~

[**~~```

~~**](

- [ ]

_Originally posted by @Youniqueli in https://github.com/openai/human-eval/issues/37#issuecomment-1918231138_

URL actually stands for Uniform Resource Locator.

Typo in #2 will be corrected in an upcoming release. Thanks!

Is the source code that converts USLM into plain text, as shown on the TXT view of congress.gov, open source? I've been unsuccessful in finding it.

@llaplant Why don’t these ReferenceItems in the table of contents (<toc>) include the identifier for the sections that exist later on in the document? e.g. identifier="/us/bill/116/hr/748/dA/tIII" - we are trying to link from the TOC to relevant sections, and this tagging would be helpful if included in the TOC section. Thanks!

<referenceItem` style="-uslm-lc:I651142" role="section">
   <designator>Sec. 1. </designator>
   <label>Short title.</label>
</referenceItem>

GPO’s office of Programs, Strategy, and Technology is hiring recent graduates. Be part of the high-performing team that is responsible for transformational technology initiatives such as GPO’s ISO-certified Trustworthy Digital Repository, govinfo; GPO’s new XML-based composition system, XPub; and the emerging XML schema for legislative and regulatory publications, USLM. See https://www.usajobs.gov/job/651949800 for more information and to apply.